Working of PeraHealth HL7 Alarms

This topic explains how PeraHealth HL7 alarms work.

Alarms (PeraTrend warning alarm) are generated in the form of HL7 by leveraging the Rothman Index (RI) score. PeraTrend warning alarm is the aggregation of multiple alarms generated from the PeraHealth system.

PeraTrend generates three types of alarms based on the severity level as shown in Table 1.

Table 1. PeraTrend Alarm Severity Type and Severity Level
Severity Type Severity Level
Medium Risk 2
High Risk 3
Very High Risk 4

In PeraHealth, alarm reasons are called as rule descriptions. These are completely configurable based on customer requirements. The alarm reason is mapped with severity.

In CWE and PeraHealth integration, the severity of PeraHealth is added as an alarm reason in ‘Manage Alarm Reasons’ section of the CWE admin console. When CWE receives an alarm from PeraHealth, the alarm text is sent to the client (badge or VCS client) and the severity type is displayed in View Alarm section of the admin console.

PeraHealth severity is mapped in CWE with Vocer Voice Server severity (Urgent, High, Normal)

If the alarm reason in PeraHealth HL7 is 'Adults Drop 30% in 24 hours' then in View Alarm section of admin console it will be displayed as 'VERY HIGH RISK' and in the badge it will be displayed as 'Adults Drop 30% in 24 hours'.

PeraHealth HL7 alarm for Very High Risk Severity Level

Below is a HL7 alarm message format:

MSH|^~\&|PERATREND|PERAHEALTH|||20170302T133944Z||ORU^R01|1488461984442|P|2.5.1
PID|1||32456^EIN^Lincoln Med~8478590^MRN^Lincoln Med||john^Doe|||||||||||||1345323432|
PV1|1||1EST^410^1^Lincoln Med||||||||||||||||532022000000|||||||||||||||||||||
OBR|1|||^WARNING^PERAHEALTH|||20170123T130000Z|
OBX|1|NM|WARNING^^PERAHEALTH||4||||||F|||20170123T130000Z|182874|||Adult Drop 30% in 12 hours|

In this example ‘Adult Drop 30% in 12 hours’ is the rule description or alarm reason and 4 is the alarm severity level.

When CWE receives this HL7 alarm from PeraHealth, it displays 'Adults Drop 30% in 24 hours' in the client (badge or VCS client) and in View Alarm section of the CWE admin console, it displays 'VERY HIGH RISK'.

PeraHealth HL7 alarm for Very High Risk Severity Level

Below is a HL7 alarm message format:

MSH|^~\&|PERATREND|PERAHEALTH|||20170302T133944Z||ORU^R01|1488461984442|P|2.5.1
PID|1||32456^EIN^Lincoln Med~8478590^MRN^Lincoln Med||john^Doe|||||||||||||1345323432|
PV1|1||1EST^410^1^Lincoln Med||||||||||||||||532022000000|||||||||||||||||||||
OBR|1|||^WARNING^PERAHEALTH|||20170123T130000Z|
OBX|1|NM|WARNING^^PERAHEALTH||3||||||F|||20170123T130000Z|182874|||HIGH RISK|

In this example ‘HIGH RISK’ is the rule description or alarm reason and 3 is the alarm severity level.

When CWE receives this HL7 alarm from PeraHealth, it displays ‘HIGH RISK’ in client (badge or VCS client) and in View Alarm section of the CWE admin console, it displays 'HIGH RISK'.