This wiki has undergone a migration to Confluence found Here
Difference between revisions of "VirtualMedicalDevice FHIR Profile Proposal"
Jump to navigation
Jump to search
Line 73: | Line 73: | ||
<!-- 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 VirtualMedicalDevice. | |
===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== |
Revision as of 00:45, 4 October 2014
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
- 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