This wiki has undergone a migration to Confluence found Here
Difference between revisions of "MedicalDeviceSystem FHIR Profile Proposal"
Jump to navigation
Jump to search
(→Plans) |
|||
| Line 100: | Line 100: | ||
<!-- 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 --> | ||
| − | * | + | * This proposal will not be addressed in the current cycle. It is provided as guidance to our intended overall architecture for device communications and will be implemented in the future. |
| − | |||
===Balloting Requirements=== | ===Balloting Requirements=== | ||
<!-- 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.--> | ||
| − | |||
| − | |||
Revision as of 21:58, 29 October 2014
This page documents a Pending FHIR Resource Proposal
MedicalDeviceSystem
Profile Details
Parent Resource
Constraints to be Applied
- parent = Resource(MedicalDeviceSystem)
Extensions to be Applied
Example Scenarios
- A simple MDS from a pulse oximeter containment tree.
Scope of coverage
The MedicalDeviceSystem profile describes the characteristics, operational status and capabilities of a particular device specialization.
Note:
For the initial scope, this MedicalDeviceSystem profile is only applicable to describe a single MDS 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 MedicalDeviceSystem.
gForge Users
TBD
FHIR Profile Development Project Insight ID
TBD
Plans
Timelines
- This proposal will not be addressed in the current cycle. It is provided as guidance to our intended overall architecture for device communications and will be implemented in the future.
