This wiki has undergone a migration to Confluence found Here
DeviceChannel FHIR Profile Proposal
Revision as of 18:35, 3 October 2014 by Ctran (talk | contribs) (→FHIR Profile Development Project Insight ID)
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
- 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