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
(migrate to Confluence)
 
(8 intermediate revisions by one other user not shown)
Line 1: Line 1:
  
 
<div class="messagebox cleanup metadata">
 
<div class="messagebox cleanup metadata">
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
+
Current version: https://confluence.hl7.org/display/FHIR/DeviceAlertList+FHIR+Profile+Proposal<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<div style="background:#F0F0F0">
 
<div style="background:#F0F0F0">
 
This page documents a [[:category:Pending FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
 
This page documents a [[:category:Pending FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
Line 34: Line 34:
  
 
<!--Put a link to the resource/datatype (or group of resources) that will be profiled here.-->
 
<!--Put a link to the resource/datatype (or group of resources) that will be profiled here.-->
* [[http://hl7.org/implement/standards/fhir/list.html| List]]
+
*[http://hl7.org/implement/standards/fhir/list.html| List]
  
 
====Constraints to be Applied====
 
====Constraints to be Applied====
  
 
<!--Describe how the current resource will be constrained.-->
 
<!--Describe how the current resource will be constrained.-->
* source = Resource(Device)
+
*source = Resource([http://hl7.org/implement/standards/fhir/device.html Device])
* subject = Resource(Device | Patient)
+
*subject = Resource([http://hl7.org/implement/standards/fhir/device.html Device]| [http://hl7.org/implement/standards/fhir/patient.html Patient])
* ordered = True
+
*ordered = True
* mode = snapshot
+
*mode = snapshot
* entry = Resource(DeviceAlert)
+
*entry = Resource([http://hl7.org/implement/standards/fhir/devicealert.html DeviceAlert])
  
 
====Extensions to be Applied====
 
====Extensions to be Applied====
  
 
<!--Describe how the current resource will be extended.-->
 
<!--Describe how the current resource will be extended.-->
* None
+
*None
  
 
===Example Scenarios===
 
===Example Scenarios===
  
 
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this Profile.  They should demonstrate the full scope of the Profile and allow exercising of the Profiles capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) -->
 
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this Profile.  They should demonstrate the full scope of the Profile and allow exercising of the Profiles capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) -->
* Fluid line occlusion and low battery technical alarms from an infusion pump.
+
*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.
+
*Multiple alarms with highest priority severity that have a defined order at the generating device.
  
 
===Scope of coverage===
 
===Scope of coverage===
Line 84: Line 84:
  
 
<!--Key Profiles are justified by CCDA, for Profiles not deemed "key", what interest is there by implementers in using this particular Profile. Provide named implementations if possible - ideally provide multiple independent implementations. -->
 
<!--Key Profiles are justified by CCDA, for Profiles not deemed "key", what interest is there by implementers in using this particular Profile. Provide named implementations if possible - ideally provide multiple independent implementations. -->
* Center for Medical Interoperability will be in collaboration with Dräger Medical to work on the profile definition for DeviceAlertList.
+
*Center for Medical Interoperability will be in collaboration with Dräger Medical to work on the profile definition for DeviceAlertList.
  
 
===gForge Users===
 
===gForge Users===
  
 
<!-- Identify the userids who will require commit access to gForge to maintain the Profile.  (Ensure all users have registered for gForge.) -->
 
<!-- Identify the userids who will require commit access to gForge to maintain the Profile.  (Ensure all users have registered for gForge.) -->
 
+
TBD
  
 
===FHIR Profile Development Project Insight ID===
 
===FHIR Profile Development Project Insight ID===
  
 
<!-- Please specify the id of your work group’s PSS for doing FHIR work.  (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc -->
 
<!-- Please specify the id of your work group’s PSS for doing FHIR work.  (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc -->
 +
TBD
  
 
==Plans==
 
==Plans==
Line 99: 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 -->
*TargetDateForInternalReview
+
*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===
 
===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.-->
 
Choose one:
 
*Ballot with next FHIR DSTU or Normative Edition
 
*or Ballot independently as DSTU
 
*or Realm specific ballot
 
*or No Ballot
 
 
<!-- Indicate the desired ballot date.-->
 
Desired Ballot Date
 
*PutDesiredBallotDateHere
 

Latest revision as of 16:08, 31 October 2019



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