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 65: | Line 65: | ||
As a rule, Profiles should encompass all of these aspects. | As a rule, Profiles should encompass all of these aspects. | ||
--> | --> | ||
+ | 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== | ==Ownership== |
Revision as of 00:39, 4 October 2014
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
- 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