search

AudaciousInquiry / fhir-saner

Situation Awareness for Novel Epidemic Response (COVID-19 driven project to track resource availability)
17 stars 0 forks source link

Clarify relationships between Group characteristics and Location properties #8

Closed jmandel closed 4 years ago

jmandel commented 4 years ago

Right now a Group must point to a Location that it is "partOf": image

  1. That Location is presumably support to meet the saner-bed-location profile; the IG should specify this.

  2. That Location will include details about details like status, operationalStatus, mode, type, and physicalType; these same details are also modeled directly as Group characteristics. Do we allow these details to get out of sync (e.g., is okay for a Group's characteristics to indicate an operationalStatus of "occupied" when the location the Group points to has an operationalStatus of "unoccuplied", or if the location omits operationalStatus?) Where there's overlap between what we can say in Group characteristics vs Location properties, we should provide guidance to prevent conflicting information.

jmandel commented 4 years ago

Even though we're now using MeasureReport, the same question stands, if we're conveying detaid characteristics in strata.

keithboone commented 4 years ago

We switched to MeasureReport, I think we can skip for now.