Agenda:
parent/hasPart (FHIR-32271, FHIR-39332)
- Proposal to remove parent from DeviceDefinition; leaving DeviceDefinition.hasPart, and Device.parent
- DeviceMetric vs. Device.property (FHIR-39322, also FHIR-39303, FHIR-20857, FHIR-39357)
- Propose to leave DeviceMetric and Device.property as is, cleaning up definitions as per FHIR-39322
- Rationale
- Need ability to reference specific metrics from Observation; not a good way to do this for an element of a resource
- Observation.device reference(Device | DeviceMetric) is normative; not clear what changes to normative content are allowed
- A device may support hundreds of metrics, representing metrics in Device.property means significant increase in size of Device, challenges managing large lists of properties, and frequent updates to Device whenever any metric changes (not the value of the metric, but any of the information around the metric).
- Does not complicate Device.property leading to potential confusion over which elements to use for simple property values, and which to use to represent metrics (which should not have a value in the Device). Eliminates extraneous elements from use cases that don't require DeviceMetric.
- ...
- specialization/conformsTo
- WGM Agenda development
- Meeting schedule until WGM.