Engage™ Mobile is the smartphone application companion for Vocera Engage™, the next-generation patient alarm safety and event response platform. Engage Mobile provides a unique user experience optimized for the demands of healthcare delivery.

Vocera Engage can help you manage clinical alarms and alerts, in coordination with the Engage Mobile app. You can apply advanced rules within Engage to filter and rank patient events by urgency. The system then sends only actionable notifications, accompanied by relevant context about the patient, caregiver, and event, to the appropriate care team recipients. Care team members receive the messages on their Android or iOS device using Engage Mobile, Vocera Collaboration Suite, via desktop, Vocera Badge, or VoIP device.

Warning: Engage Mobile 5.X will not work properly without XMPP 3.X. Failure to install the correct versions will result in missed alarms and system failures.

Requirements for iOS Devices on Engage Mobile

Below are the minimum requirements for an Apple Device, including models and iOS versions supported.

System	Requirements
Vocera	Engage Server (Compatible with Engage Server 5.2 and higher) XMPP Adapter (Compatible with X<PP 3.0 and higher)
Network	802.11 a/b/n/ac wireless network (Wireless standards support varies based on the device) Engage Edge 1.0 as a reverse proxy server to enable connectivity when outside Wi-Fi
Cellular Network	GSM CDMA LTE
Enterprise Devices*	Apple iPhone 6s, 7, 8, and X, 11, and 12
Apple**	iOS 12 and higher Apple iPhone SE, 6, 6S Plus, 7Plus, 7, 8, and X, Xr, Xs, Xs Max, 11, 11 Pro, 11 Pro Max, 12, 12 Pro, and 12 Pro Max

* Enterprise Devices have gone through extensive device performance testing for voice quality and wireless connectivity by Vocera. Vocera recommends using these devices in an enterprise environment.

** These devices or OS versions meet the minimum specifications for our product. Quality of experience may vary based on manufacturer and device model.

What's New

This section summarizes the new features in this release.

What's New in Engage Mobile for iOS 5.3.4

Engage Mobile5.3.4 provides no new features. This is a required update in anticipation of Apple making the PushKit requirements mandatory in 2021.

This release modifies the use of Apple's iOS PushKit for device notifcations to be in compliance with changed Apple requirements.
- This has been tested and is compatible with both Vocera Platform 5.5.X and 6.X.

What's New in Engage Mobile for iOS 5.3.3

The Engage Mobile 5.3.3 solution provides the following new feature:

Version 5.3.3 is a maintenance release to ensure compatibility with iOS version 13, there are no new features in this release.

What's New in Engage Mobile for iOS 5.3.2

The Engage Mobile 5.3.2 solution provides the following new feature:

Version 5.3.2 is a maintenance release to fix a defect. There are no new features in this release.

What's New in Engage Mobile for iOS 5.3.1

The Engage Mobile 5.3.1 solution provides the following new feature:

NEC MLC Dialer (MOB-7323)
Vocera is pleased to announce that mobile users can select the NEC MLC dialer to place VoIP calls.

What's New in Engage Mobile for iOS 5.3.0

The Engage Mobile 5.3.0 solution provides the following new features:

User Inactivity timeout for Engage Mobile Users based on role. (PFM-8929)
The facility can now decide when a user must re-authenticate after a specified time of inactivity. The specified time is in minutes and can be from 1 to 10,080 minutes. Because this number is set in the Security Policy, different roles can have different timeout lengths. The application is considered inactive when it is in the background and/or when the device is asleep. Messages will continue to be delivered while the user is timed out and will be available once the user re-authenticates into the application. This features requires XMPP 3.4.
Patient Information access is now determined by role. (PFM-8828)

The facility can now decided, based on role, which employees have access to Patient Information. This is also set in the Security Policy. There are two choices, either Full or Restricted. It is important to know that if a facility sets a role to restricted access, users will not be able to do the following:
- Cannot search for patients in the roster.
- Cannot create conversations that have a patient linked.
- Cannot see patient information, (Names, MRN's, etc.) in conversations that have a patient linked. This includes alarms.
- Do not have access to the More Info screen in any type of conversation, regardless of whether a patient is linked or not.
- Cannot launch AirStrip in Clinical Alarms.
If the facility choses Full access then the user will be able to see anything that contains Patient Information. This feature requires XMPP 3.4.

New Ringtones
- We are pleased to announce the addition of 6 new ringtones for messages.
- These ringtones will play for a minimum of 5 seconds, but can be configured to play longer.
  This feature requires XMPP 3.4

What's Fixed

What's Fixed in the Engage Mobile 5.3.4 Release

Engage Mobile 5.3.4 does not fix any defects. The release modifies the use of Apple's iOS PushKit for device notifcations to be in compliance with changed Apple requirements.

What's Fixed in the Engage Mobile 5.3.3 Release

The following issues are fixed in Engage Mobile 5.3.3:

MOB-7578: When a user is disconnected from the network, the red notification banner is not at the top of the screen on notch devices.
This issue has been corrected. There were instances where the red notification banner was not fully appearing on notch devices.
MOB-7586: On notch devices, when logging in with a PIN, the Engage icon disappears from the login screen.
This issue has been corrected.

What's Fixed in the Engage Mobile 5.3.2 Release

The following issues are fixed in Engage Mobile 5.3.2:

MOB-6626: If a user had Engage Mobile in the background of their iPhone, did not interact with an alert notification, and the alert expired, the user was presented with an empty chat room when logging back into the application.
This issue has been corrected. Regardless of whether a user interacts with a notification, when an Alert expires the user is no longer shown an empty chat room.

What's Fixed in the Engage Mobile 5.3.1 Release

The following issues are fixed in Engage Mobile 5.3.1:

There are no issues fixed in this release of Engage Mobile.

What's Fixed in the Engage Mobile 5.3.0 Release

There were no issues to fix in this release.

Known Issues

This section provides information about known product defects and limitations in the current release.

The following issues occur when the facility is using Vocera Platform 6.2:
- The facility is using both Vina and Engage Mobile. If a user creates a favorite in Vina and then logs back into Engage Mobile, these favorites will show as offline in Engage Mobile only.
- If a user receives their first message as a missed call, then the internal XMPP ID (JID) will display instead of the users name.
- Both Vina and Engage Mobile users are in a Multi User Chat. If using web based Vina and the user selects a tab outside of the conversation, the Engage Mobile user will receive a notification that the Vina user has left the chat. Similarly, when the Vina web user selects the chat, the Engage Mobile user will receive notification that the user has entered the chat.

Engage Mobile for iOS

Release Notes - Version 5.3.4.48

Updated: April 19, 2021

About Engage Mobile