Before installing this firmware, ensure that the following Vocera products are installed:
Perform the following prerequisites before performing the installation instructions for the Vocera version 5.1.1 Firmware release.
Configure
Configure
Update
The BPE is installed on both the configuration computer and the
To update the
The Badge Properties Editor appears.
The V5000
For specific instructions on how to configure your badge using BPE, refer to
Following are the properties required for the Badge Property Editor:
Mandatory Settings
Wireless Settings
Wireless settings are dependent on the configuration settings of your environment.
Custom Settings
There are few settings to control specific functions that can be applied through the Custom Settings fields. For information on the custom setting appropriate for your environment, contact Vocera Technical Support.
This section includes installation instructions for the Vocera version 5.1.1 Firmware
release. This release applies to
Vocera provides the core software needed to run the
SSH into the client VM.
Log into the virtual machine (VM) using the address of the machine and tpx-admin credentials:
ssh tpx-admin@<IP of VM>
Update the repository to the latest software versions
Close any open sessions. Run YUM clean all:
sudo yum clean all
Update the list of all available RPM packages for adapters and devices. Run YUM check updates to update the RPM package list:
sudo yum check-updates
View the list of updated software
Input the command below to view the available software for a particular
adapter or device. Below, we are viewing the RPM package for the
sudo yum list available | grep "V5000"
Install the RPM package
Select the correct file from the list. Update the command to reflect the appropriate file. Run the YUM command to install the software:
sudo yum install vocera-FW-V5000.x86_64
Reboot the VM.
sudo reboot
After the reboot completes, verify that Glassfish and the Voice Service are running.
Input the following command at the ssh prompt. The first command is to verify Glassfish (sudo systemctl status extension-glassfish) and the second command is to verify the Voice Service (sudo systemctl status vocera-voice.service). The remaining text shows either service running.
sudo systemctl status extension-glassfish ... [tpx-admin@nextgen ~]$ sudo systemctl status extension-glassfish ● extension-glassfish.service - Glassfish Appliance Server Loaded: loaded (/usr/lib/systemd/system/extension-glassfish.service; enabled; vendor preset: disabled) Active: active (running) since Thu 2019-08-20 14:34:12 EST; 1 months 5 days ago
sudo systemctl status vocera-voice.service ● vocera-voice.service - Voice Server Launcher Loaded: loaded (/usr/lib/systemd/system/vocera-voice.service; enabled; vendor preset: disabled) Active: active (running) since Wed 2019-08-21 11:59:58 EDT; 1h 49min ago Aug 21 11:59:54 sc-platform656l3 java[5048]: 2019-08-21 11:59:54.899 [I] [39] ServerState changed to 'Server started'. Aug 21 11:59:58 sc-platform656l3 java[5048]: 2019-08-21 11:59:58.514 [I] [36] Vocera Server : Ready. Aug 21 11:59:58 sc-platform656l3 java[5048]: 2019-08-21 11:59:58.514 [I] [36] ------------------------------------------------------------------------------------------------- Aug 21 11:59:58 sc-platform656l3 java[5048]: 2019-08-21 11:59:58.514 [I] [36] ** The Vocera system is ready ** Aug 21 11:59:58 sc-platform656l3 java[5048]: 2019-08-21 11:59:58.514 [I] [36] -------------------------------------------------------------------------------------------------
To verify the firmware build on the
The default settings screen with the status is displayed.
The firmware build loaded on your
This section summarizes the new features in the
The
This section summarizes the new features in the
Placing Direct Calls from Vocera Devices
As part of the Vocera care team connect solution, the new direct call feature enables the communication between the patient and the caregiver in bed locations that lack nurse call. This feature reduces the need to don and doff PPE (Personal Protective Equipment) and improve the patient experience.
When the direct call feature is enabled on Vocera Platform and Vocera devices, the user can press the Call button to immediately place a call to a predefined recipient without having to interact with the genie. The direct call recipient can be another user, group, or a contact in the system.
To enable this feature, set the custom badge property V5.DirectCallEnabled true by using the BCU or through the VCB menu only. Do not add this property to the Badge.Properties of the Vocera Platform. The default value of the badge property is false.
Vocera recommends the following:
For information on Vocera device usage guidelines for the Direct Call feature, refer to the Vocera V-Series Smartbadge User Guide, Vocera B-Series Badge User Guide, and Vocera Device Configuration Guide available on Vocera Documentation Portal.
This section summarizes the new features in the
OK Vocerato initiate a Genie call without having to touch the Call button for a true, hands-free calling experience. This feature is enabled through the badge property V5.EnableHotword [True|False]. The default value of the property is False.
This section summarizes the new features in the
PIN Authentication for Logging in
An authentication PIN can be enabled to identify the user logging into the
Home Screen Features
The Home screen has the following filters:
Directory Screen
Messages and Alerts
Patient Context
Provides the ability to access information about a patient to understand the real-time situation of the patient. Patient context has the following features if a patient is assigned to a user:
Flexible DND
Options available to select preset custom messages.
The following list contains fixes and improvements for firmware release and the V5000 product.
There are no new fixes in this release.
The following section lists the known issues in this firmware release and the V5000 Smartbadge product.
As part of the resistance to dust and water ingress, the removable battery is a snug fit when
initially deployed with the
The following list provides information about known product issues in the 5.1.1.51 [15.3]
firmware and the