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 65: | Line 65: | ||
--> | --> | ||
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. | 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: | 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. | 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. | ||
Revision as of 18:34, 3 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
gForge Users
FHIR Profile Development Project Insight ID
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
