PCD Profile Alarm Communication Management Overview: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
← Older editNewer edit →
Jrhoads (talk | contribs)
editor
1,861 edits
m a
Jrhoads (talk | contribs)
editor
1,861 edits
a
Line 39: Line 39:
''<If the user might have an appreciation for the problems addressed in the profile, you can mention them here, but keep it short.  E.g. Mapping HL7 Order fields to DICOM Modality Worklist attributes can be inconsistent in the marketplace, so Scheduled Workflow provides vendors with more detailed instructions.>''
''<If the user might have an appreciation for the problems addressed in the profile, you can mention them here, but keep it short.  E.g. Mapping HL7 Order fields to DICOM Modality Worklist attributes can be inconsistent in the marketplace, so Scheduled Workflow provides vendors with more detailed instructions.>''
-->
-->
This profile extends the Device Enterprise Communication profile of the IHE Patient Care Devices domain to further specify the communication of alarm data describing states and events significant to patient care from patient care devices to alarm manager systems (systems which route alarms to end devices for notification of caregivers, or to other systems that record patient care information).
These alarms may be physiological, that is, representing the physiological state of the patient (such as a heart rate above or below a caregiver-specified safe range for the patient), or technical, reflecting conditions in the patient care devices themselves that may require action from caregivers (such as ECG leads off the patient).
The intent of this profile is to give a uniform way of representing such common alarm conditions in HL7 messages to facilitate interoperability of systems from different vendors.


:*Defines the interfaces needed to mediate between a patient care device and a system communicating with a smart phone or other portable device.
:*Defines the interfaces needed to mediate between a patient care device and a system communicating with a smart phone or other portable device.

Revision as of 14:28, 6 April 2011

Alarm Communications Management (ACM) allows a patient care device to send a notification of an alert or alarm condition to a portable device such as a smart phone.

Summary

The Alarm Communications Management profile defines an HL7 V2 message for communicating detailed information about an alarm from a patient care device to an information system which then causes a message to be transmitted to a portable device. If the device is able to provide an acknowledgment, the alarm managing system or alarm originating system can be notified that the message was received, and (depending on the capabilities of the device) acted on. The profile also supports an alarm archiving system.


Benefits

  • Provides a secondary means for notifying the appropriate person of a condition needing timely human intervention.
  • Automates otherwise manually initiated workflow notification for greater speed, improved content consistency, better record keeping.
  • Improves workflow notification efficiency by notifying the right person at the right time on the right device.Automates who to notify, on what device, how to do it. Telephony dial back for consultation and read back
  • May allow a clinician in a large or noisy unit to more quickly and accurately identify the source, nature, and action needed for an alarm.
  • Provides an escalation mechanism designed to eliminate notification "black holes". Offers work task accept/escalate using two-way devices. Reduces “left a message”, “call back later” issues.


Details

This profile extends the Device Enterprise Communication profile of the IHE Patient Care Devices domain to further specify the communication of alarm data describing states and events significant to patient care from patient care devices to alarm manager systems (systems which route alarms to end devices for notification of caregivers, or to other systems that record patient care information).

These alarms may be physiological, that is, representing the physiological state of the patient (such as a heart rate above or below a caregiver-specified safe range for the patient), or technical, reflecting conditions in the patient care devices themselves that may require action from caregivers (such as ECG leads off the patient).

The intent of this profile is to give a uniform way of representing such common alarm conditions in HL7 messages to facilitate interoperability of systems from different vendors.


  • Defines the interfaces needed to mediate between a patient care device and a system communicating with a smart phone or other portable device.
  • Defines an interface for a system archiving the details of alarms.

Systems Affected

Patient care devices and intermediary (device concentrator) systems

Portable personnel notification systems (pagers, smart phones, and the like)


Actors & Transactions:

Alarm Reporter – The Alarm Reporter (AR) actor sources the alarm to Alarm Manager (AM).

Alarm Manager – The Alarm Manager (AM) actor receives the alarm from the Alarm Reporter (AR), potentially analyzes the alarm, and dispatches the alarm to the Alarm Communicator (AC).

Alarm Communicator – The Alarm Communicator (AC) actor receives the alarm from the Alarm Manager (AM) and sends the alarm to the client application in the endpoint device.

Alarm Archiver – The Alarm Archiver (AA) actor sends alarm subscription requests to the AM actor and receives report alarm responses from the AM actor.

Specification

Profile Status: Trial Implementation

Documents:

ACM Documents Page


Underlying Standards:

See Also

Related Profiles


This page is based on the Profile Overview Template

Retrieved from "http://wiki.ihe.net/index.php?title=PCD_Profile_Alarm_Communication_Management_Overview&oldid=49779"