This wiki has undergone a migration to Confluence found Here
Difference between revisions of "DeviceChannel FHIR Profile Proposal"
Jump to navigation
Jump to search
| Line 104: | Line 104: | ||
<!-- 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 22:01, 29 October 2014
This page documents a Pending FHIR Resource Proposal
DeviceChannel
Profile Details
Parent Resource
Constraints to be Applied
- parent = Resource(VirtualMedicalDevice)
Extensions to be Applied
- None
Example Scenarios
- A primary channel from an infusion pump containment tree.
Scope of coverage
The DeviceChannel profile describes the characteristics, operational status and capabilities of 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 DeviceChannel profile is only applicable to describe a single Channel 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 DeviceChannel.
gForge Users
TBD
FHIR Profile Development Project Insight ID
TBD
Plans
Timelines
- This proposal will not be addressed in the current DSTU cycle. It is provided as guidance to our intended overall architecture for device communications and will be implemented in the future.
