This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "DeviceChannel FHIR Profile Proposal"

From HL7Wiki
Jump to navigation Jump to search
Line 40: Line 40:
 
<!--Describe how the current resource will be constrained.-->
 
<!--Describe how the current resource will be constrained.-->
 
* parent = Resource(VirtualMedicalDevice)
 
* parent = Resource(VirtualMedicalDevice)
 
  
 
====Extensions to be Applied====
 
====Extensions to be Applied====

Revision as of 18:35, 3 October 2014



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

Health Care Devices (DEV) WG

Contributing or Reviewing Work Groups

Health Care Devices (DEV) WG

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

  • 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