Acknowledging an Alarm

This topic describes the various scenarios on alarm acknowledgement from the Mindray patient monitor.

In Mindray eGateway 6.2, when an alarm gets acknowledged from the patient monitor, it sends an alarm-acknowledge event (HL7) to CWE. The alarm acknowledgement event from Mindray is considered as ‘Cancel’ event. It means when Mindray eGateway sends an alarm-acknowledge event, CWE generates a JSON with action as ‘Cancel’.

Scenario 1 (Alarm acknowledged from patient monitor after user acknowledges from client)

When an alarm is generated and sent to CWE, the CWE subsequently sends it to the client with responses such as acknowledge, escalate or call-back. In the CWE admin console, this alarm status is shown as sent. When the user acknowledges the alarm from the client, the status in the admin console is changed to ‘Acknowledged’.

Now, if the same alarm is acknowledged from the patient monitor, then CWE will receive an Alarm-Acknowledge event and will cancel the alarm. As a result, the alarm status in the admin console changes to 'Cancel' and further workflow stops.

In this case, the workflow of the alarm will be Generated, Sent, Acknowledged, and Cancelled.

Scenario 2 (Alarm acknowledged from patient monitor before user acknowledges from client)

When an alarm is generated and sent to CWE, the CWE subsequently sends it to the client with responses such as acknowledge, escalate or call-back. In the CWE admin console this alarm status is shown as sent.

Now assume that the user does not respond to this alarm and acknowledges the alarm from the patient monitor. In this case CWE will receive an Alarm-Acknowledge event and will cancel the alarm. As a result the alarm status in the admin console changes to 'Cancel' and further workflow stops.

In this case, the workflow of the alarm will be Generated, Sent, and Cancelled.