Caregivers use the Vocera Edge application to perform and document clinical activities, including assigning and un-assigning patients, receiving and responding to notifications and reminders associated with assigned patients' medication or lab orders, administering medications, collecting lab orders, and collecting clinical data.
This Vocera Edge Clinical for iOS release is compatible with Vocera Edge System 4.12.x, 4.14.x., and 4.15.x.
Use this document in conjunction with the following Release Notes:
The following devices have been certified to be compatible with Vocera Edge Clinical 4.15:
All of these devices can be used as shared devices and for BYOD. However, Vocera recommends the latest iPhone SE or later for voice (VoIP).
The following Apple iOS operating systems are certified:
Vocera has tested and approved of the Mophie Juice Pack Air and Apple Battery Case for all listed devices.
Vocera has tested and approved of the following compatible power solutions:
This section summarizes the new features in this release.
The following list displays new features in this version of
No new features or functionality in this release.
The following list displays new features in this version of
Unified Messaging: Integration with Vocera Voice 5.10.4
Description: Vocera Edge users can initiate and receive text messages between the Vocera Edge app, Vocera Edge Web Messenger, and a Vocera Badge (SmartBadge, MiniBadge, and B3000N). Unified messaging supports:
One-on-one messages with badge users
Group messages with Vocera Voice groups
NOTE: When sending a message to an Edge or Voice group, the subject line is required. Users cannot add or remove users in a group after the message is sent.
Patient-tagged conversations
NOTE: You can tag one patient in a conversation. Adding a new patient opens a new conversation. When tagging a patient in a message, the subject line is required.
Image and audio attachments
NOTE: If you are sending the message to the Vocera Voice server, image attachments are not displayed on the badges. The badge receives a notification only. The image is still visible when you view the message in the app or Web Messenger web client.
Emojis
NOTE: If you are sending messages to the Vocera Voice server, emojis are removed from the messages before they are sent to a Badge. The emoji is still visible when you view the message in the app or Web Messenger web client.
Acknowledge requests
Read receipts
Quick texts
Simultaneous Login (see Simultaneous Login details below for more information.)
Configuration and Maintenance: N/A
Simultaneous Login between Vocera Edge and Vocera Badge: Integration with Vocera Voice 5.10.4
Description: Vocera Edge users can log into the Vocera Edge mobile app (iOS and Android) and one Vocera Badge (SmartBadge, MiniBadge, and B3000N) at the same time and send and receive text messages and alerts on both the app and device. Simultaneous login allows one Badge connection only. If the user logs in to a second Badge, then they are logged out of the first one.
This release contains the following updates from the previous Simultaneous Login release (available in Vocera Edge 4.14.1):
Messaging: Users can send and receive text messages and alerts on both the Vocera Edge Mobile app and the Vocera Badge.
The Vocera Badge serves as the primary voice device and performs all voice service activities: calls, voicemail, playing alerts, and genie sessions. The Vocera Edge mobile app serves as the secondary device and performs data service activities: messaging and receiving call logs.
Configuration and Maintenance: To use this feature, the Vocera Edge 4.15
environment must be connected to a Vocera Voice 5.10.4 Server. No further
configuration is needed. Simultaneous login is active and working upon installation
of the Vocera Edge 4.15 app and Vocera Voice 5.10.4 Server. When you log in to a
badge and the
Unified Alerting: Integration with Vocera Voice 5.10.4 and Vocera Engage 7.2.1
Description: Vocera Edge users can receive alerts on the Vocera Edge app, Vocera Edge Web Messenger, and a Vocera Badge (SmartBadge, MiniBadge, and B3000N).
Configuration and Maintenance: Alert configuration is completed using Engage Rules 1.5 and later. To use this feature, the Vocera Edge 4.15 Server must be connected to a Vocera Voice 5.10.4 Server and a Vocera Engage 7.2.1 Server. The Engage Server must have a configured Outgoing WCTP 2.8.0.1 adapter. Vocera Engage sends messages to the Vocera Edge 4.15 Server using the Outgoing WCTP Adapter, then Vocera Edge Server delivers the message to the Vocera Edge Mobile app and the Vocera Badge.
NOTE: Starting with this release, the Outgoing VMI Adapter is no longer required for sending alerts from Engage to Voice Server. Alerts between Engage, Edge, and Voice are sent through the Outgoing WCTP adapter. If you configured the Outgoing VMI Adapter in a previous version of Engage to send alerts to Voice, then you can continue to use this configuration if you are only using Engage and Voice. If you are using Engage, Edge, and Voice together, then configure and use the Outgoing WCTP Adapter to send alerts from Engage to Edge, then Edge to Voice.
Call Forwarding to an Extension in BYOD Mode
Enable Call Forwarding in Enterprise Manager:
This section contains fixes and improvements made to Vocera Edge.
The following list includes items fixed or improved in this version of
EDGEM-7243 The app no longer closes unexpectedly after a user receives a new group message when the conversation is already open and the network connectivity is unstable. This issue occurred when the iOS device's Wi-Fi connectivity was unstable and the app loaded new group messages after the Wi-Fi connection reconnected after being offline.
The following list includes items fixed or improved in this version of
EDGEM-6051 The sort function now works correctly when trying to sort results in the To-Do list.
This section provides information about known product defects and limitations in Vocera Edge Clinical - iOS 4.15.1.
EDGEM-6601 Starting in Vocera Edge 4.15.0, patients cannot be untagged from existing one-on-one conversations. If a patient-tagged one-on-one conversation was created on an earlier version of Edge (4.14 or earlier), then the patient is still tagged in the conversation after Edge is upgraded to 4.15.0, but the patient cannot be untagged. To continue the one-on-one conversation without the tagged patient, create a new conversation, and then select the conversation recipient from the Contact Directory in the app. The new conversation will contain the existing conversation history, but will not have the tagged patient.
Version Introduced: Vocera Edge for iOS 4.15.0
Workaround: This issue is seen only during an upgrade cycle. In the iOS app, the tagged patient details are retained in one-on-one conversations and the untag option is not listed after the app and server are upgraded. Any new messages sent in the conversation will continue to tag the patient. When a user searches for the same caregiver in the directory and tries to send a new one-on-one conversation, the previously tagged patient is untagged automatically and the user can continue with the new conversation. Thereafter, any new patient tagging continues to open up a new patient-tagged conversation (as expected with the new patient-tagging updates in Vocera Edge 4.15.0).
EDGEM-5183 There is no call audio when both users are on a cellular network and when Edge is connected to a Vocera Voice Server.
Version Introduced: Vocera Edge for iOS 4.14.0
Workaround: This issue affects calls through a cellular network only. Call audio works when the users are connected to a Wi-Fi network.
EDGEM-3579 If a user ends a call while it is on hold, the call still appears as on hold to the other call participants.
Version Introduced: Vocera Edge for iOS 4.14.0
Workaround: Transferring or merging the call prompts the appropriate information about the hold call status.
EDGEM-2936 Edge may end an Edge voice call immediately when a user transfers a call using the Assisted Transfer option.
Version Introduced: Vocera Edge for iOS 4.12.0
Workaround: This issue affects iOS 15.x and earlier. To correct this issue, upgrade your iOS device to iOS 16.x or later.
EDGEM-2010 The app may have no audio when a broadcast or urgent broadcast is automatically answered while the app is in Do Not Disturb. The broadcast is answered with the speaker disabled and no audio can be heard.
Version Introduced: Vocera Edge for iOS 4.14.0 configured with a Vocera Voice 5.10.2 server
Workaround: Tap the Push-to-talk button to set up the audio on the handset.