This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "DeviceMetricObservation FHIR Profile Proposal"

From HL7Wiki
Jump to navigation Jump to search
Line 88: Line 88:
  
 
<!--Key Profiles are justified by CCDA, for Profiles not deemed "key", what interest is there by implementers in using this particular Profile. Provide named implementations if possible - ideally provide multiple independent implementations. -->
 
<!--Key Profiles are justified by CCDA, for Profiles not deemed "key", what interest is there by implementers in using this particular Profile. Provide named implementations if possible - ideally provide multiple independent 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===
 
===gForge Users===

Revision as of 18:58, 3 October 2014



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

Health Care Devices (DEV) WG

Contributing or Reviewing Work Groups

Health Care Devices (DEV) WG

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

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