This wiki has undergone a migration to Confluence found Here
Difference between revisions of "VirtualMedicalDevice FHIR Profile Proposal"
Jump to navigation
Jump to search
(→Plans) |
|||
| Line 98: | Line 98: | ||
<!-- 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 104: | Line 105: | ||
<!-- 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 | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 00:46, 4 October 2014
This page documents a Pending FHIR Resource Proposal
VirtualMedicalDevice
Profile Details
Parent Resource
Constraints to be Applied
- parent = Resource(MedicalDeviceSystem)
Extensions to be Applied
- None
Example Scenarios
- A plugin module (virtual medical device) from a patient monitoring system containment tree.
Scope of coverage
The VirtualMedicalDevice profile describes the characteristics, operational status and capabilities of a medical-related subsystem. It can either be a physical hardware piece or a pure software plugin component of a medical device.
Note:
For the initial scope, this VirtualMedicalDevice profile is only applicable to describe a single VMD node 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.
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 VirtualMedicalDevice.
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
