This wiki has undergone a migration to Confluence found Here
DeviceMetricObservation FHIR Profile Proposal
DeviceMetricObservation
Profile Details
Parent Resource
Constraints to be Applied
- performer = Resource(Device)
- subject = Resource(Device| Patient)
- method = Measure mode ValueSet
- applied[x] = DateTime
- Remove encounter
Extensions to be Applied
- relatedDeviceMetric = Resource(Patient) [1..1]
Example Scenarios
- An observation of diastolic blood pressure indicates 60 mmHg.
- An observation of systolic blood pressure indicates 111 mmHg.
- A ventilation mode setting value from a ventilator.
Scope of coverage
The DeviceMetricObservation profile describes the direct or derived, qualitative or quantitative physiological measurement, setting, or calculation data produced by a medical device or a device component.
Note:
For the initial scope, this DeviceMetricObservation profile is only applicable to describe a measurement that is produced by any medical device that implements or derives from the ISO/IEEE 11073 standard.
Ownership
Owning committee name
Contributing or Reviewing Work Groups
Expected implementations
- Center for Medical Interoperability will be in collaboration with Dräger Medical to work on the profile definition for DeviceMetricObservation.
- Other Enterprise systems (such as EHR, PHR, or EMR) might be interested in consuming DeviceMetricObservation data for their data analytic module.
gForge Users
TBD
FHIR Profile Development Project Insight ID
Plans
Timelines
- TargetDateForInternalReview
Balloting Requirements
Choose one:
- Ballot with next FHIR DSTU or Normative Edition
- or Ballot independently as DSTU
- or Realm specific ballot
- or No Ballot
Desired Ballot Date
- PutDesiredBallotDateHere