The
The solution receives alarms from patient monitors and uses staff assignment information to
deliver ancillary alarm notifications of critical alarms to clinician's mobile devices and
desk phones (fixed devices).
This section summarizes the new features in this release.
The
EMDAN solution now consists of multiple packages; one core package containing the most often used components, and several supplemental packages containing less frequently used components. This ensures that facilities do not have unwanted or unneeded adapters.
Improved and simplifed Admin Workflows including:
New View Role-based Staff Assignment workflow
New Mass Notification workflow. Enhancements in efficient delivery of notifications with more than 250 recipients.
Support for including physiological values in alarm notifications text descriptions.
Improved workflow and responsiveness for Monitor Tech (TeleTech) via Cisco Desktop phones.
Improved Datasets for Implementation Engineers, such as Clinicals, Nurse Calls, and Monitor Techs.
Improved and redesigned Rules for easier installation and alarm notification:
Support for Epic Treatment Team.
Support for Vocera Collaboration Suite (VCS) and Patient Context integration.
New adapter support:
HL7 enhanced support (multiple results in a single Lab Test result).
This section provides information about fixes and improvements made to the
The following issues are fixed in
A prefix of 'q' has been added to all Vocera Callback Numbers with either a path or default number to enable the callback function. (SOL-453)
Declining a Nurse Call alert no longer re-triggers the send rule, which would re-deliver the alert. A new 'Alert has not been responded to' condition is now used for the send rules. (SOL-526)
An NTE segment definition in the HL7 message definition for Orders is no longer marked as a required segment for the ORM-O01 messages. (SOL-847)
The EMDAN solution no longer marks the NTE segment as required on HL7 Orders. (SOL-847)
Preprocessor rule on Alarm Notifications HL7 adapter is now more efficient. (SOL-547)
Removed the (.) wildcard from the regex, and $1 and $2 from the replacement string.
Previously, only the last note received for an order was stored. (SOL-545)
Results are now mapped as "Linked child record per segment", instead of "Add to parent record".
$$hashkey values for HL7 configuration elements are now unique. (SOL-440)
Cloned the AlarmNotification message types, thereby creating new and unique $$hashKeys for each message type, segment definition, and field definition.
In NurseCall integrations, the DataUpdate rule "Adds the current date/time" no longer updates the object causing Tertiary rule to trigger again. (SOL-353)
This section provides information about known product defects and limitations in the current release.
Cisco 8821 device pages do not refresh when navigating with the Back softkey, which results in outdated information displaying if the page includes dynamic content. (SOL-2314)
Workaround: Update the content by navigating forward to the page using other links or softkeys. Most pages include an option to access the application Menu. All content in the application may be reached by navigating forward from the Menu.
If there is no monitor tech assigned and no caregivers online, then the No Caregiver Online rule will not fire. The default caregiver for the No MT rule will get an alert, but the person who is supposed to get the No Caregiver Online alert will not get it. (SOL-2120)
The 'Send an error message if there is no monitortech' rule fires multiple times at every escalation level. (SOL-2119)
Installations of CAN solutions fail to rotate monitor.log due to ownership and permission issues with the directories. (SOL-497)
Workaround: Ensure the directories /opt/EXTENSION/solutions, /opt/EXTENSION/solutions/CAN, and /opt/EXTENSION/solutions/CAN/logs are all owned by extension by executing the command 'sudo chown extension.extension' on each directory. Verify that the file /opt/EXTENSION/solutions/CAN/monitor-log-rotate.conf is still owned by root.
If the site requires the lower severity alarm and the higher severity alarm as part of their workflow, they will receive the higher severity alarm twice until they can move to HL7 1.1 and eliminate Mirth. (SOL-438)
Workaround: Configure the system to trigger on the higher severity alarm. Sites which trigger alerts based on the lower severity alarms usually find they occur too often.
Externally escalated nurse calls register multiple deliveries to the same recipient. (SOL-69)