Beginning this release, the upgrade and install sections are documented in a separate guide—Vocera Analytics Installation Guide. This new guide provides an installation workflow, a step-by-step installation procedure, and the corresponding configuration information for different scenarios based on your setup.

You can access the Vocera Analytics Installation Guide here: Vocera Analytics Installation Guide.

Vocera Analytics provides a comprehensive view of all interruptions encountered by caregivers. Interruptions include voice calls, text messages, and alarms and alerts from clinical and operational systems. Vocera Analytics enables clinical leaders to review performance metrics, conduct comparisons, measure success rates, and identify areas for improvement. Based on this information, dashboards and reports can be constructed to monitor and drive continuous improvement.

Vocera Analytics comprises the following functionalities:

• Dashboards—Display data based on defined metrics and key performance indicators (KPIs) that you can analyze and track.

• Reports—Provide logs that the Vocera Voice Server supplies. These reports allow you to understand your usage of the Vocera products and optimize the deployment of your organization.

You can find documentation for this version of the product by clicking the question mark (?) in the header pane on all the pages of the Analytics console.

You can also access the following Vocera Analytics documentation directly from a web browser without being logged in:

• Vocera Analytics Installation Guide

• Vocera Analytics Administration Guide

• Vocera Analytics Gallery User Guide

• Vocera Analytics Database Schema Guide

Before you install Vocera Analytics, your environment must contain the necessary prerequisites. The size of your server normally depends on the number of users that reference it and the number of beds at your site.

Vocera Analytics hardware prerequisites:

The details on the hardware requirements for the Vocera Analytics Server database are as follows:

Validation Metrics: Performance Expectations

• Reports and Dashboards: One month of data displays in 10-15 seconds
• Data Exports: 30–45 seconds

Vocera Analytics software prerequisites:

To use the Vocera Analytics Server database, you must have the necessary software version available:

• Vocera Voice Server version 4.4.4 and later.
• Engage Platform version 5.5 and later, with EMDAN version 1.9x and later.
• Vocera Messaging Platform version 5.2.2 and later.
  Note: All three systems (Voice Server, Engage Platform, VMP) are not required. Standalone Voice Server and standalone Engage Platform are supported. However only VMP as a source is not supported. Minimum system level versions are only applicable if previously installed or an installation is pending. Vocera Analytics will collect data from each of these systems only if installed.
• Vocera Platform 6.0 and later.
• Data Export Adapter 1.4.1 SR1
• Crystal Reports 2016 and MySQL Connector or ODBC 3.51 driver.
  Important: Do not install Crystal Reports Server on the same machine as Vocera Analytics Server. Vocera Analytics Server has not been certified to work on computers where Crystal Reports Server is also installed. You must also set up an ODBC data source.

Other Considerations

To use Vocera Analytics, you must consider the following product requirements:

• A license SKU.

  You can order the SKU from your Vocera Account Representative.

Vocera Analytics is the upgrade path for both Vocera Reporting Services and Engage Reporting. It is available for all Vocera systems (Standard or Enterprise License) and includes data migration for both VRS and Engage.

Infrastructure Considerations

To use Vocera Analytics, you must consider the following infrastructure requirements:

• New VM or physical server. You cannot re-purpose the Vocera Reporting Server (VRS)

  Third-party licensing: Windows 2016 OS only (No SQL Server)

  Note:

  • New Crystal Reports desktop license is included.
  • You can use the previous reporting systems (VRS and Engage) side by side. Vocera recommends that you move to Vocera Analytics to use all the enhanced features.

This section summarizes the new features and enhancements in this release.

The following list contains fixes and improvements made to the Vocera Analytics in this release.

This release includes the following known issues:

Vocera Analytics Release 1.2.0

The following list is specific to Vocera Analytics 1.2.0

• VA-8838 - Mariadb and Reporting Service of the Visualization Server displays the message Port is not configured for this service after upgrading from Vocera Analytics 1.0 to Vocera Analytics 1.2.
• VA-8819 - Invalid Up Time is displayed for services after upgrading from Vocera Analytics 1.0 to Vocera Analytics 1.2. Workaround: Clearing the browser cache resolves the issue.
• VA-8801 - Login and Logout events are not captured if the user is off-prem.
• VA-8765 - When a VMI message is sent to a group, the group site is displayed instead of user site in Integration Message User Activity Report. ()
• VA-8729 - In Vocera Vina, data loss occurs for Device Inventory when the user updates the status of multiple devices at the same time.
• VA-8719 - Date format is not displayed as expected in reports for English-Canada locale.
• VA-8711 - The Department field displays No Department Assigned when the user updates any group or creates a buddy on Voice Server User Console in Tiered Administration Audit report.
• VA-8680 - For date range filter that do not have a time part, "Last x days" will consider current day + previous x days. For example, Last 7 days will be considered as current day + previous 7 days.
• VA-8668 - No user record available! message is displayed in Import Users page when only few users are selected and assigned roles from the displayed list.
• VA-8535 - Due to a firmware issue, user activity for certain users are displayed as Inactive in Login dashboard.
• VA-8219 - Communication between de-coupled servers fails when the servers are not on the same domain.

Vocera Analytics Release 1.1.0

The following list of known issues are existing from Vocera Analytics 1.1.0

• VA-7044 - In Vocera Platform 6.0, receiver device details are not displayed when a call to address book is made.
• VA-6906 - Calls made to an extension using the keypad from Vocera Vina application is not captured.
• VA-6699 - Failed jobs are not generated and hence the user is not notified when Flume is down after Flume and Spark are started.
• VA-6531 - Restarting service monitor service requires logout and login to the configuration user interface.
• VA-6450 - Vocera logo and menu are not displayed when the user refreshes the Web browser in Report Scheduler and User Management screens.
• VA-6421 - In Vocera Platform 6.0, the Device Types filter in visualization server does not include Vocera Vina.
• VA-6361 - Date format is not displayed as expected in dashboards for English-Singapore, Australia and Malaysia locale.

Vocera Analytics Release 1.0.0

The following list of known issues are existing from Vocera Analytics release 1.0.0

• VA-5433 - Calls from a telephone and to a telephone will be shown in Unknown facility and Unknown unit in dashboards and reports of Interruptions and Systems Usage.
• VA-5409 - In User Interruptions and Group Interruptions page, the group ID is displayed instead of group name for email messages.
• VA-5392 - If two users with the same first name and last name exist and both users belong to the same facility and unit but are in different groups, a data count error occurs. The database and the dashboard counts the data as one instead of two when a group call or broadcast to the unit is done.
• VA-5373 - Broadcasts calls made from telephones do not have group information and are displayed as Unknown or Null in dashboards and reports.
• VA-5207 - The Unit Summary widget does not sort alphabetically for units of the same name from different facilities in Interruption Summary dashboard.
• VA-5179 - The Day field displays 31 days irrespective of the month selected in Schedule section of Add Package page.
• VA-5154 - The Summary by Owner Facility widget considers device activity with time but Details widget considers only the date for device use status in Inventory Status dashboard.
• VA-5117 - Login activity for users with same first name and last name in same or different facilities might not be accurate in User Activity Details dashboard and report, Login dashboard, and Inactive Users report.
• VA-5102 - In situations where two users with the same name are logged in, and one user logs out, then the logout information is displayed incorrectly in User Activity Detail dashboard.
• VA-5074 - The Source Details widget displays Interrupt Type, Priority, and Description even for data with 0 count in Unit Interruption Report.
• VA-5073 - Reports cannot be scheduled after the current session expires. Workaround: Log out and log in again to schedule a report.
• VA-5064 - Filter selection is carried forward from one dashboard to another even when a filter is not applied.
• VA-5022 - Mobile User Activity and Mobile Unit Activity Reports show a lower text message count when events escalate.
• VA-5008 - In certain scenarios, an error message is displayed in a pop-up window in Unit Summary Report. However, you may ignore the error message and close the pop-up window.
• VA-5004 - Sending a voice message to group or unit with similar names in same or different facilities might not be accurate in Group Usage dashboard and Group Activity report.
• VA-4983 - In the Vocera Analytics Server, after an Engage source is setup with an invalid database hostname, it cannot be updated to a new value. Workaround: Remove the Flume agent and rebuild it.
• VA-4873 - Report and Dashboard filters do not maintain dependencies. In certain scenarios, even if a filter is available and selected, the generated report may not display any data.
• VA-4784 - While sending a text message from an email to Voice Server users or groups, the user ID or group name (created in Voice Server) mentioned in email subject line must be case sensitive for Vocera Analytics to process the data correctly. Else the message interrupts will be missing.
• VA-4720 - Incorrect data is displayed for calls made to Groups with same name from a different facility.
• VA-4719 - The warning pop up window in Reports does not close automatically even after you navigate to other pages.
• VA-4667 - The option Unknown is not available in Access Point Locations filter in Speech Recognition Location Details Report.
• VA-4398 - In certain scenarios, Reports display http error. Workaround: Refreshing the Web page resolves the issue.
• VA-4304 - The name of the user appears three times instead of once when a desktop message is sent to a selected user that is associated to a group and a unit associated with the respective group.
• VA-4301 - The Add package page is displayed from the middle of page if you scroll down the Report package page and click Add package.
• VA-3798 - In Vocera Messaging Interface (VMI), if a client uses the same message ID for different messages, dashboards may show inconsistent data. Workaround: For every client ID, ensure that the message or alert sent through VMI has a unique message ID.
• VA-256 - The Call Forward functionality is not entirely supported.
• VA-241 - Panic broadcasts are not supported.

Vocera Analytics has a few limitations. For more information, refer to Vocera Analytics Limitations.