Configuring Internally Escalated Message Types

Message types can be configured for internally escalated alerts. Repeated alerts require understanding the key configuration for internal escalations.

The Vocera EarlySense Adapter message types include a regex mapping for the event data from the message received. The regex mapping stores the event data as an alert.

Although only one message type is required to create the adapter, Implementation Specialists may add, remove, or modify message types as needed. See Understanding Regular Expressions for additional information.

Remember that internally escalated message types are messages where Vocera Platform controls to whom the message is sent. Please see Configuring Externally Escalated Message Types for messages that are to be routed by the facility to Vocera Platform.

This section contains integration details about creating internally escalated alerts; see the Configuring a Vocera EarlySense Adapter description for the full context.

Field Description
Regex Enter a regular expression that will be used to match a message value to this type. When processing a message value, the first message type whose regular expression matches the value is chosen.
Regex Mapping

Enter a list of mapping expressions which map alert attributes to values from the location based on capture groups from the regular expression. This value is only available if the message type does not specify to discard matching messages.

Specify one or more attributes, or attribute paths, one per line, to be filled with data from the above regex. See Understanding Regular Expressions for additional information.

The regex mapping on the message type is designed to strip out the excess information in the message, which was the location information in our testing. This may need to be updated depending on the information Vocera Platform is receiving from EarlySense, and can be similar to TAP and HL7.

Save Pager IDs Save Pager IDs is not used for internally escalated messages. Leave this box unchecked.

Understanding Repeated Alerts in Internally Escalated Alerts

Because EarlySense will send repeated notifications if the alert remains unacknowledged at the bedside monitor, some consideration is required on how to store and manage the data. Work with the clinical staff at the facility to determine the proper approach based on their needs.

Create a Unique Key

If notifications are spaced sufficiently to allow deliveries to the entire escalation path based on the alert type before an alert notification is repeated, then the alert should be stored as unique upon creation. The unique key for the alert should be composed from the alert location, alert type, and the current date/time. The timestamp for the alert may also be set.

Create a Reproducible Key

If notifications are not spaced sufficiently to allow deliveries to the entire escalation path based on the alert type before an alert notification is repeated, then the alert should be stored with a reproducible key and then made unique after a delay. The key for the alert should be composed from just the alert location and alert type. The timestamp for the alert should not be set as this may cause an unexpected updates that could disrupt the escalation path. See Understanding DataUpdate Reset in Alert Escalations for guidance on making the key of the alert unique.