The
This section summarizes prominent features and functionality for each release.
Here is the summary of a few release-defining new features in the 5.3.4 version of the
This section highlights new features, enhancements, and changes for voice commands, voice prompts, and feature behaviors.
Vocera care team connect
The new direct call feature as part of the Vocera care team connect solution enables patients and their care team to communicate with each other in bed locations lacking nurse call. Use of this feature can reduce the need to don and doff Personal Protective Equipment (PPE) and improve the patient experience.
When the direct call feature is enabled for a Vocera Smartbadge or B3000n device users, a patient can press the Call button to immediately place a call to a predefined care team recipient without having to interact with the Genie.
The Direct Call feature is disabled by default. Using the Administration Console, Administrators can enable it from the new Direct Call section in the User > Add/Edit User > Phone tab and add a direct call recipient (User, Group, or Address Book Entry) to the user profile. To create user profiles in bulk with care team connect features, Administrators can update Direct Call and Direct Call Target columns in the user-template.csv file and import it.
For information on Vocera device usage guidelines for the care team connect feature, refer to the Vocera V-Series Smartbadge User Guide and Vocera B-Series Badge User Guide available on Vocera Documentation Portal.
This section highlights administrator configuration requirements for new features, enhancements, and behavior changes that appear in the voice user interface for badges, smartphones, and the Vocera User Console.
The following third-party software versions are included in this release and provide 64-bit compatibility or security enhancements:
Third-party Software | Version |
---|---|
Apache HTTP Server | 2.4.41 |
Apache Tomcat | 9.0.20 |
JRE (Zulu built on OpenJDK) | 1.8.0_232 (Zulu 8.42.0.21) |
MySQL Server | 8.0.17 |
Here is the summary of a few release-defining new features in the 5.3.3 version of the
This section highlights new features, enhancements, and changes for voice commands, voice prompts, and feature behaviors.
On the Administration Console, administrators set up the call options from Defaults > Miscellaneous tab and then enable Hide Forwarded Number option from Users > Add New/Edit User > Forward tab. Administrators and users enable Hide Forwarded Number from the Call Forwarding tab in the User Console.
This section highlights administrator configuration requirements for new features, enhancements, and behavior changes that appear in the voice user interface for badges, smartphones, and the Vocera User Console.
The following third-party software versions are included in this release and provide 64-bit compatibility or security enhancements:
Third-party Software | Version |
---|---|
Apache HTTP Server | 2.4.41 |
Apache Tomcat | 9.0.20 |
JRE (Zulu built on OpenJDK) | 1.8.0_232 (Zulu 8.42.0.21) |
MySQL Server | 8.0.17 |
Here is the summary of a few release-defining new features in the 5.3.2 version of the
This section highlights new features, enhancements, and changes for voice commands, voice prompts, and feature behaviors.
This section highlights administrator configuration requirements for new features, enhancements, and behavior changes that appear in the voice user interface for badges, smartphones, and the Vocera User Console.
Third-party Software | Version |
---|---|
Apache HTTP Server | 2.4.38 |
Apache Tomcat | 8.5.40 |
JRE (Zulu built on OpenJDK) | 1.8.0_212 (Zulu 8.38.0.13) |
MySQL Server 5.7 | 5.7.25 |
This is a maintenance release only.
There are no new features for this release.
This is a maintenance release only.
There are no new features for this release.
This is a maintenance release only.
There are no new features for this release.
Here is the summary of a few release-defining new features in the 5.3.1 version of the
This section highlights new features, enhancements, and changes for voice commands, voice prompts, and feature behaviors.
Vocera Badge User Guideand
Vocera Badge Configuration Guidefor details.
This section highlights administrator configuration requirements for new features, enhancements, and behavior changes that appear in the voice user interface for badges, smartphones, and the Vocera User Console.
Third-party Software | Version |
---|---|
Apache HTTP Server | 2.4.29 |
Apache Tomcat | 8.5.24 |
JRE (Zulu built on OpenJDK) | 1.8.0_152 (Zulu 8.25.0.1) |
MySQL Server 5.7 | 5.7.21 |
Here is the summary of a few release-defining new features in the 5.3.3 version of the
This section highlights new features, enhancements, and changes for voice commands, voice prompts, and feature behaviors.
You have a message for <Group Name> from <Sender>
Code Lavender is considered an integrative medicine service and a vital tool to ensure that individuals are able to continue after being presented with a difficult case, diagnosis, or loss. Hospital staff, patients, and family members often fall victim to fatigue, despair, and generally negative feelings that may impact all attempts of healing. A Code Lavender event ensures that hospital employees, patients, and patient families feel that they have the mental and emotional strength and energy to cope with challenging situations.
Refer to the Vocera Voice Server Administration Console Guide
for details about configuring Code Lavender. See the Vocera Badge User Guide for
usage guidelines and command descriptions. New voice commands include Schedule Code
Lavender for <group name>
, Start Code Lavender for <group
name>
, Delete Code Lavender Reminder for <group name>
, and
Delete All Code Lavender Reminders
.
Doctorprefix when the name is announced.
Command Backoff triggers on when the Vocera Genie fails to recognize the names of recipients (individual or group) used with some commonly used voice commands such as, Call, Broadcast to <group name>, Add Me to <group name>, and Record a Message for <user name>. See the Vocera Voice Server Administration Console Guide for details.
Record a reminder for <myself | user, user, user, … | group>and
Record a recurring reminder for <myself | user, user, user, … | group>.
This section highlights administrator configuration requirements for new features, enhancements, and behavior changes that appear in the voice user interface for badges, smartphones, and the Vocera User Console.
Third-party Software | Version |
---|---|
Apache HTTP Server | 2.4.29 |
Apache Tomcat | 8.5.24 |
Java™ Java Runtime Environment (JRE) | 1.8.0.152 |
MySQL Server 5.7 | 5.7.21 |
For example, if a message is sent to Trauma Team A from Site A, and a user who is a member of that Group is working at a different site, the user who is offsite should not receive the message. The exception is that users and groups in the Global Site will always receive messages.
If your Voice Server is behind a firewall
that prevents it from accessing the Internet, you may optionally download a Doc
Pack
that will install the documentation on your Voice Server machine. Contact
Customer Support for access to the Doc Pack; After installation, you will need to
restart Tomcat.
Before you install
Prerequisites for
Verify that you have the update required Windows 2012 server: KB2919442 and KB2919355.
Verify that you have one of the following Vocera products installed, if you are upgrading from an earlier version of Vocera:
Follow these instructions to install
Installation prerequisites
Re-install the Sync Connector after you complete the Vocera Server upgrade.
See How to Uninstall the Vocera Secure Texting Sync Connector in the VST Administrator Guide.
To install or upgrade
The server updates your database and removes any settings for deprecated features.
The following list contains fixes and improvements made to the
This release has no fixed issues.
The following list includes nothworthy issues fixed in this release.
The following list includes nothworthy issues fixed in this release.
Offer to Learn a Namecommand was being issued before the system was prompting for the action.
The following list includes nothworthy issues fixed in this release.
The following list includes nothworthy issues fixed in this release.
The following list includes nothworthy issues fixed in this release.
The following list includes nothworthy issues fixed in this release.
The following list includes nothworthy issues fixed in this release.
In a rare case, a customer experienced a failover and network event that kept a number of badges from communicating with the server. AutoLogout was done with a time value of 10 min rather than the configured value of 120 min. Resulting in 3500 users being logged out.
Instructions for Vocera license upgrades have been updated to cover all upgrade scenarios for cluster and stand-alone environments, and include the new Refresh option when adding users or telephone lines.
Messages sent to multiple recipients were interpreted as a broadcast and the callback option was not appended to the enunciation. The call back option was added to the badge menu prompt for the message, but the user must scroll through the message to select the Call option.
The Callback option must be checked and the phone number provided.
Who Calledcommand failed to list callers that attempt to reach a user when the user was not in DND mode.
A rare race condition can occur when a user tries to conference two parties while one of the users has put the caller on hold and is rejoining the call during the conference operation. This situation is now properly handled.
The Vocera User Console allows a user to set call forwarding to another user even when the permission has not been granted. Forwarding options have been added to allow Vocera Administrators to define forwarding permissions for individual users and groups.
A few issues are known to exist in the
This section summarizes known product defects and limitations, including any
workarounds we may have, for the
Workaround: None.
Workaround: Initiate a three-way conference call using the Conference command or invite another party to an existing call using the Invite command.
Workaround: Install the doc pack after upgrading if you are using local documentation.
Workaround: None.
Workaround: Select BPE > Security Settings > Authentication Type > EAPTLS, uncheck Use Custom EAP-TLS Certificates, configure all the required fields, and click Submit.
Workaround: None.
Workaround: None.
Workaround: Restart VMP.
Workaround: None.
Workaround: Do not reboot when prompts are displayed. Wait until the installation or uninstall process is complete to reboot.
Workaround: None
Workaround: None
Workaround: None
Workaround: None.
Workaround: Only alerts with urgent priority allow return calls.
Workaround: Spell group names using lowercase letters.
Workaround:
If you encounter this issue, use the Learn a Name
command as
usual to ensure speech recognition performance.
Workaround: Correct the email configuration or disable the data load notification email.
Workaround: None
Workaround: Use the Staff Assignment User Console User Interface to navigate.
Workaround: None
Workaround: Export to a Microsoft Excel format instead of CSV.
Workaround: To disable the direct call feature, clear the Enable Direct Call checkbox and remove the direct call recipient from the Direct Call to Another Badge, Group, or Address Book Entry field before saving the changes made to the user profile.
Workaround: None
Workaround: Enable the Announce Caller's Name setting.
Workaround: None.
Contact customer support if your Vocera Voice Server environment interoperates with CWE and you are upgrading to Vocera Voice Server 5.2.3. CWE is not compatible with VS versions newer than VS 5.2.2.
Workaround:
Two property name-and-value pairs are required. The properties are
comma-separated, so if you use more than one CWE client ID, separate them
with commas. The client ID must appear in both lists, and VMP must be in the
SuppressAlertClientID list. Two flags have been added to the
properties.txt file; The alerts are now being
delivered in the VCS client and all alerts appear in the Secure
Messages
list.
SuppressAlertClientID={CWE client id},VMP CWEClientIDs={CWE client id}
Starting with VS 5.0, the following features and components are no longer supported unless noted otherwise.