This wiki has undergone a migration to Confluence found Here
Difference between revisions of "DeviceMetricObservation FHIR Profile Proposal"
Jump to navigation
Jump to search
(migrate to Confluence) |
|||
| (10 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
<div class="messagebox cleanup metadata"> | <div class="messagebox cleanup metadata"> | ||
| − | <div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | + | Current version: https://confluence.hl7.org/display/FHIR/DeviceMetricObservation+FHIR+Profile+Proposal<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> |
<div style="background:#F0F0F0"> | <div style="background:#F0F0F0"> | ||
This page documents a [[:category:Pending FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]] | This page documents a [[:category:Pending FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]] | ||
| Line 34: | Line 34: | ||
<!--Put a link to the resource/datatype (or group of resources) that will be profiled here.--> | <!--Put a link to the resource/datatype (or group of resources) that will be profiled here.--> | ||
| − | * [http://hl7.org/implement/standards/fhir/observation.html Observation] | + | *[http://hl7.org/implement/standards/fhir/observation.html Observation] |
====Constraints to be Applied==== | ====Constraints to be Applied==== | ||
<!--Describe how the current resource will be constrained.--> | <!--Describe how the current resource will be constrained.--> | ||
| − | * performer = Resource([http://hl7.org/implement/standards/fhir/device.html Device]) | + | *performer = Resource([http://hl7.org/implement/standards/fhir/device.html Device]) |
| − | * subject = Resource([http://hl7.org/implement/standards/fhir/device.html Device]| [http://hl7.org/implement/standards/fhir/patient.html Patient]) | + | *subject = Resource([http://hl7.org/implement/standards/fhir/device.html Device]| [http://hl7.org/implement/standards/fhir/patient.html Patient]) |
| − | * method = Measure mode ValueSet | + | *method = Measure mode ValueSet |
| − | * applied[x] = DateTime | + | *applied[x] = DateTime |
| − | * Remove encounter | + | *Remove encounter |
| + | |||
====Extensions to be Applied==== | ====Extensions to be Applied==== | ||
<!--Describe how the current resource will be extended.--> | <!--Describe how the current resource will be extended.--> | ||
| − | * relatedDeviceMetric = Resource([http://hl7.org/implement/standards/fhir/ | + | *relatedDeviceMetric = Resource([http://hl7.org/implement/standards/fhir/devicemetric.html DeviceMetric]) [1..1] |
===Example Scenarios=== | ===Example Scenarios=== | ||
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this Profile. They should demonstrate the full scope of the Profile and allow exercising of the Profiles capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) --> | <!-- Provide a listing of the types of scenarios to be represented in the examples produced for this Profile. They should demonstrate the full scope of the Profile and allow exercising of the Profiles capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) --> | ||
| + | *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=== | ===Scope of coverage=== | ||
| Line 65: | Line 69: | ||
As a rule, Profiles should encompass all of these aspects. | As a rule, Profiles should encompass all of these aspects. | ||
--> | --> | ||
| + | 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== | ==Ownership== | ||
| Line 70: | Line 79: | ||
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the Profiles. --> | <!-- The name of the committee that is proposed to have responsibility for developing and maintaining the Profiles. --> | ||
| − | [[ | + | [[Health Care Devices (DEV) WG]] |
===Contributing or Reviewing Work Groups=== | ===Contributing or Reviewing Work Groups=== | ||
<!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the Profile (optional) --> | <!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the Profile (optional) --> | ||
| − | + | [[Health Care Devices (DEV) WG]] | |
| − | |||
| − | |||
===Expected implementations=== | ===Expected 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. --> | <!--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=== | ||
<!-- Identify the userids who will require commit access to gForge to maintain the Profile. (Ensure all users have registered for gForge.) --> | <!-- Identify the userids who will require commit access to gForge to maintain the Profile. (Ensure all users have registered for gForge.) --> | ||
| − | + | TBD | |
===FHIR Profile Development Project Insight ID=== | ===FHIR Profile Development Project Insight ID=== | ||
<!-- Please specify the id of your work group’s PSS for doing FHIR work. (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc --> | <!-- Please specify the id of your work group’s PSS for doing FHIR work. (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc --> | ||
| + | TBD | ||
==Plans== | ==Plans== | ||
| Line 96: | Line 106: | ||
<!-- Indicate the target date for having the Profile complete from a committee perspective and ready for vetting and voting --> | <!-- Indicate the target date for having the Profile complete from a committee perspective and ready for vetting and voting --> | ||
| − | * | + | *Ready for Draft for Comment ballot: January 2015 |
| + | *Complete for DSTU 2.0: August 2015 | ||
===Balloting Requirements=== | ===Balloting Requirements=== | ||
| Line 102: | Line 113: | ||
<!-- Indicate the intended method of balloting by choosing one of the options below, or propose alternative. If Realm Specific or No Ballot indicate the amount of informal review required by the FHIR community.--> | <!-- Indicate the intended method of balloting by choosing one of the options below, or propose alternative. If Realm Specific or No Ballot indicate the amount of informal review required by the FHIR community.--> | ||
| − | |||
*Ballot with next FHIR DSTU or Normative Edition | *Ballot with next FHIR DSTU or Normative Edition | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 16:10, 31 October 2019
Current version: https://confluence.hl7.org/display/FHIR/DeviceMetricObservation+FHIR+Profile+Proposal
This page documents a Pending FHIR Resource 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(DeviceMetric) [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
TBD
Plans
Timelines
- Ready for Draft for Comment ballot: January 2015
- Complete for DSTU 2.0: August 2015
Balloting Requirements
- Ballot with next FHIR DSTU or Normative Edition
