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

Difference between revisions of "DeviceAlertList FHIR Profile Proposal"

From HL7Wiki
Jump to navigation Jump to search
Line 100: Line 100:
  
 
<!-- Indicate the target date for having the Profile complete from a committee perspective and ready for vetting and voting -->
 
<!-- Indicate the target date for having the Profile complete from a committee perspective and ready for vetting and voting -->
* Ready for Draft for Comment ballot: January 2015
+
* 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.
* Complete for DSTU 2.0: August 2015
+
 
  
 
===Balloting Requirements===
 
===Balloting Requirements===
  
 
<!-- 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.-->
 
*Ballot with next FHIR DSTU or Normative Edition
 

Revision as of 22:03, 29 October 2014



DeviceAlertList

Profile Details

Parent Resource

Constraints to be Applied

Extensions to be Applied

  • None

Example Scenarios

  • Fluid line occlusion and low battery technical alarms from an infusion pump.
  • Multiple alarms with highest priority severity that have a defined order at the generating device.

Scope of coverage

The DeviceAlertList profile is used to group and communicate the status of multiple alarm condition checks that a medical device is able to detect in a severity sorted order.

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 DeviceAlertList.

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.


Balloting Requirements