Difference between revisions of "DeviceComponent FHIR Resource Proposal"
| Line 7: | Line 7: | ||
</div> | </div> | ||
[[Category:FHIR Resource Proposal]] | [[Category:FHIR Resource Proposal]] | ||
| − | [[Category: Approved FHIR Resource Proposal]] | + | [[Category:Approved FHIR Resource Proposal]] |
Revision as of 20:08, 5 December 2014
This page documents a Pending FHIR Resource Proposal
Contents
- 1 DeviceComponent
- 1.1 Owning committee name
- 1.2 Contributing or Reviewing Work Groups
- 1.3 FHIR Resource Development Project Insight ID
- 1.4 Scope of coverage
- 1.5 RIM scope
- 1.6 Resource appropriateness
- 1.7 Expected implementations
- 1.8 Content sources
- 1.9 Example Scenarios
- 1.10 Resource Relationships
- 1.11 Timelines
- 1.12 gForge Users
DeviceComponent
Owning committee name
Contributing or Reviewing Work Groups
FHIR Resource Development Project Insight ID
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
- Device (by MedicalDeviceSystem profile)
- Patient (by MedicalDeviceSystem profile)
- Location (by MedicalDeviceSystem profile)
- DeviceComponent
Timelines
- Ready for Draft for Comment ballot: January 2015
- Complete for DSTU 2.0: August 2015
gForge Users
TBD
