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 74: Line 74:
  
 
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the Profiles. -->
 
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the Profiles. -->
[[YourCommitteeName]]
+
[[Health Care Devices (DEV) WG]]
  
 
===Contributing or Reviewing Work Groups===
 
===Contributing or Reviewing Work Groups===

Revision as of 18:20, 3 October 2014



DeviceAlertList

Profile Details

Parent Resource

Constraints to be Applied

  • source = Resource(Device)
  • subject = Resource(Device | Patient)
  • ordered = True
  • mode = snapshot
  • entry = Resource(DeviceAlert)

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

  • Work Group Name
  • or link
  • or "None"

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