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
Enhanced XMPP to support delivery to Vocera badges:
Added additional rule configuration fields to allow badge delivery.
Changed XMPP messages and added additional content to reflect updates in the Unified Client.
Enhance the Presence feature to allow the ability to set an optional duration limit for an unavailable presence.
Changed workflows and rules to support the
Updated workflows and rules to handle DM's and Nurse Calls as a consequence of changes in groups and places.
Updated additional workflows, rules, and conditions for changes in the Users and Groups data model.
Updated various workflows, rules, and conditions for changes in the Places, Patients, and Assignments data model.
Added default rules to link a group to a TargetGroup, which is necessary for Nurse Calls and other alerts using the To dataset.
Removed workflows such as ManageFacility and ManageUsers that the WebUI handles in
Added default aliases to support some adapters that were not updated for the
Made the following changes to Staff Assignment:
Added the ability to associate one or more units to a location. This allows assignments for groups through a unit location.
Added the ability to associate a group with a required functional role.
Updated the Manage Locations workflow to ensure you can only have one Unit linked at a time.
Implemented the following changes to procedures for making Group Assignments:
Instead of using hard-coded links for first_unit, second_unit, etc, you now make group assignments to a location using functional roles. That is you create a location and link it to a required functional role with the desired group and a functional role. Use the role name for conditions in rules in the default solution and take care to ensure the correct functional role name is chosen. Then associate that location with every unit for which that group covers alerts.
Finally, ensure the conditions on the send rules are set to expect the correct group(s) at the correct level(s). This setting enables a group to respond at different levels in different units (as in previous versions of EMDAN), while only requiring a one-time setup of links.
This section provides information about fixes and improvements made to the
The following issues are fixed in
A condition was added to the contact detail rules to only fire for groups, and prevent key conflicts. (SOL-2621)
The SEND rules for XMPP at the secondary and tertiary escalation levels no longer display the wrong level description in the Additional Content field. (SOL-2615)
Rules have been added to ensure that groups are now linked to target groups based on the Vocera Phone Number field, under contacts in the WebUI. (SOL-2508)
The CREATE AND LINK ENDPOINT rule has been moved back to the DataUpdate adapter, so it is on all sites by default. This ensures that DMs work correctly. (SOL-2462)
The Manage Locations workflow, which allows Locations to be linked to Units, now allows a user to link (and unlink) one or more Units to a Location. (SOL-2430)
This section provides information about known product defects and limitations in the current release.
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)
No workaround is required as only an administrator or support engineer observes this behavior.
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.
CUCM users receive a workflow error message when they accept NurseCalls. (SOL-2257)
Users are not prevented from trying to remove a required functional role, but receive a workflow error without explanation. (SOL-2421)
Accept messages are not sent to legacy devices after an alert has escalated in some cases. (SOL-2562)
The ESCALATE TO PRIMARY rule for a group does not have conditions checking the devices for users in the assigned group. (SOL-2481)
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)