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

Difference between revisions of "DeviceComponent FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
 
(18 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<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:Approved FHIR Resource Proposal|Approved]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
 
</div>
 
</div>
 
</div>
 
</div>
 
[[Category:FHIR Resource Proposal]]
 
[[Category:FHIR Resource Proposal]]
[[Category:Pending FHIR Resource Proposal]]
+
[[Category:Approved FHIR Resource Proposal]]
  
  
Line 40: Line 40:
  
 
<!-- 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 -->
 +
[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=1103 Project Insight 1103]
  
 
==Scope of coverage==
 
==Scope of coverage==
Line 53: Line 54:
 
As a rule, resources should encompass all of these aspects.
 
As a rule, resources should encompass all of these aspects.
 
  -->
 
  -->
 +
The DeviceComponent resource is used to describe the characteristics, operational status and capabilities of a medical-related component of a medical device. It can be a physical component that is integrated inside the device, a removable physical component, or a non-physical component that allows physiological measurement data and its derived data to be grouped in a hierarchical information organization.
 +
 +
Note:
 +
 +
For the initial scope, this DeviceComponent resource is only applicable to describe a single node (such as MDS, VMD, or Channel) represents in the containment tree that is produced by the context scanner in any medical device that implements or derives from the ISO/IEEE 11073 standard.
  
 
==RIM scope==
 
==RIM scope==
  
 
<!-- Identify the formal RIM mapping for the root concept of the resource.  The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. -->
 
<!-- Identify the formal RIM mapping for the root concept of the resource.  The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. -->
 +
TBD
  
 
==Resource appropriateness==
 
==Resource appropriateness==
Line 72: Line 79:
 
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document  
 
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document  
 
  -->
 
  -->
 +
This DeviceComponent resource is solely used to describe a single node (such as MDS, VMD, or Channel) represents in the containment tree that is produced by the context scanner in any medical device that implements or derives from the ISO/IEEE 11073 standard. Refer to MedicalDeviceSystem, VirtualMedicalDevice, and DeviceChannel profiles for a more appropriate usage.
  
 
==Expected implementations==
 
==Expected implementations==
  
 
<!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. -->
 
<!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. 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 resource definition for DeviceComponent.
  
 
==Content sources==
 
==Content sources==
Line 82: Line 91:
  
 
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? -->
 
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? -->
 +
* ISO/IEEE 11073-10201
 +
* ISO/IEEE 11073-20601
  
 
==Example Scenarios==
 
==Example Scenarios==
  
 
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource.  They should demonstrate the full scope of the resource and allow exercising of the resources 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 resource.  They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) -->
 +
* A simple MDS from a pulse oximeter containment tree.
 +
* A plugin module for a patient monitoring system containment tree.
 +
* A primary channel from an infusion pump containment tree.
  
 
==Resource Relationships==
 
==Resource Relationships==
Line 97: Line 111:
 
Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording)
 
Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording)
 
  -->
 
  -->
 +
Uses
 +
* [http://hl7.org/implement/standards/fhir/device.html Device] (by MedicalDeviceSystem profile)
 +
* [http://hl7.org/implement/standards/fhir/patient.html Patient] (by MedicalDeviceSystem profile)
 +
* [http://hl7.org/implement/standards/fhir/location.html Location] (by MedicalDeviceSystem profile)
 +
* [http://hl7.org/implement/standards/fhir/devicecomponent.html DeviceComponent]
  
 
==Timelines==
 
==Timelines==
  
 
<!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting -->
 
<!-- Indicate the target date for having the resource 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
  
 
==gForge Users==
 
==gForge Users==
  
 
<!-- Identify the userids who will require commit access to gForge to maintain the resource.  (Ensure all users have registered for gForge.) -->
 
<!-- Identify the userids who will require commit access to gForge to maintain the resource.  (Ensure all users have registered for gForge.) -->
 +
TBD

Latest revision as of 20:13, 5 December 2014



DeviceComponent

Owning committee name

Health Care Devices (DEV) WG

Contributing or Reviewing Work Groups

Health Care Devices (DEV) WG

FHIR Resource Development Project Insight ID

Project Insight 1103

Scope of coverage

The DeviceComponent resource is used to describe the characteristics, operational status and capabilities of a medical-related component of a medical device. It can be a physical component that is integrated inside the device, a removable physical component, or a non-physical component that allows physiological measurement data and its derived data to be grouped in a hierarchical information organization.

Note:

For the initial scope, this DeviceComponent resource is only applicable to describe a single node (such as MDS, VMD, or Channel) represents in the containment tree that is produced by the context scanner in any medical device that implements or derives from the ISO/IEEE 11073 standard.

RIM scope

TBD

Resource appropriateness

This DeviceComponent resource is solely used to describe a single node (such as MDS, VMD, or Channel) represents in the containment tree that is produced by the context scanner in any medical device that implements or derives from the ISO/IEEE 11073 standard. Refer to MedicalDeviceSystem, VirtualMedicalDevice, and DeviceChannel profiles for a more appropriate usage.

Expected implementations

  • Center for Medical Interoperability will be in collaboration with Dräger Medical to work on the resource definition for DeviceComponent.

Content sources

  • ISO/IEEE 11073-10201
  • ISO/IEEE 11073-20601

Example Scenarios

  • A simple MDS from a pulse oximeter containment tree.
  • A plugin module for a patient monitoring system containment tree.
  • A primary channel from an infusion pump containment tree.

Resource Relationships

Uses

Timelines

  • Ready for Draft for Comment ballot: January 2015
  • Complete for DSTU 2.0: August 2015

gForge Users

TBD