Message types can be configured for externally 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 externally escalated message types are messages where the facility tells Vocera Platform to whom the message is sent. Please see Configuring Internally Escalated Message Types for messages that are to be routed by Vocera Platform.
This section contains information about creating externally escalated alerts; see the Configuring a Vocera EarlySense Adapter configuration 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. |
| Pager ID Regex |
Pager ID Regex and Pager ID Regex Mapping specify a pattern that the pager id must match to be saved with the message, and how to map the pager ID into an attribute of a dataset linked to the starting dataset. The assumption is that the attribute paths reference a "to-many" link so that multiple matching pager IDs can be saved. This is not available if Save Pager IDs is not set. |
| Pager ID Mapping |
Pager ID Regex and Pager ID Regex Mapping specify a pattern that the pager ID must match to be saved with the message, and how to map the pager ID into an attribute of a dataset linked to the starting dataset. The assumption is that the attribute paths reference a "to-many" link so that multiple matching pager IDs can be saved. This is not available if Save Pager IDs is not set. |
Understanding Repeated Alerts in Externally 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 EarlySense is being used to manage the escalation of an alert, then a delivery should be made to the appropriate caregivers for each notification received. In this deployment scenario, the easiest way to manage the data is to record each notification as a new alert. In this case, 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. This approach works well for legacy devices where each device receives the message independently.
Create a Reproducible Key
If the facility is using XMPP devices, then aggregating the repeated alerts into a single event and conversation may be desirable. In this deployment scenario, 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 may also be set. See Understanding DataUpdate Reset in Alert Escalations below for guidance on making the key of the alert unique. The XMPP rule used for delivery of the alert should set the "Re-Alert" flag to ensure that the primary caregiver is alerted each time that a notification is received.
