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 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
• 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 and limitations:

Vocera Analytics Release 1.1.0

The following list is specific to Vocera Analytics 1.1.0

• Only one unit is displayed for the user in User Interruptions dashboard and exported CSV file when the user is assigned to more than one unit with the same unit name in different facilities. (VA-7171)
• Data loading error is displayed on unit-related dashboards when a unit is mapped using Manage Sites and crosswalk tables are not updated. Workaround: Manually run UpdateCrosswalk stored procedure after mapping facilities. (VA-7126)
  Note: Crosswalk data is automatically updated every 1 hour, and crosswalk information gets corrected.
• Incorrect port numbers are displayed for Flume agents of Engage, VMP, and Voice Server after an upgrade or an unplanned restart of Vocera Analytics server. (VA-7060)
• Login event does not get updated when the user is already logged in to the badge and the same user is logged in to Vina without logging out from the badge. (VA-7046)
• In Vocera Platform 6.0, receiver device details are not displayed when a call to address book is made. (VA-7044)
• Integration Group Activity report takes a longer time to load data with facility filter applied. Workaround: Apply unit filter in addition to facility filter to load data within a few minutes. (VA-6974)
• Voice message canceled by the user gets counted and is displayed as sent and received in the User Activity Details dashboard. (VA-6946)
• Calls made to an extension using the keypad from Vocera Vina application is not captured. (VA-6906)
• If a user is removed from a department or moved to any other department, it still considers the department from which the user is removed. (VA-6862)
• Recipient details are incorrect for instant conference when multiple users with similar first name and last name are present in different facilities even though they are not part of instant conference. (VA-6817)
• In certain situations, an error Could not start process is displayed in the monitoring log. (VA-6735) Workaround: To stop seeing this error message, exclude the following files from your antivirus/malware scan:
  • <InstallDrive>\VoceraAnalytics\jdk\jre\bin\java.exe
  • <InstallDrive>\VoceraAnalytics\MariaDB\bin\mysqld.exe
• Failed jobs are not generated and hence the user is not notified when Flume is down after Flume and Spark are started. (VA-6699)
• Talking duration is displayed for incomplete telephone calls and telephone calls not received by a user are considered complete. (VA-6688)
• Speech count does not match in Speech Statistics and User Statistics dashboards when a unit is selected and the user-initiated genie from phone and device. (VA-6612)
• In Vocera Platform 6.0, Status Tracking dashboard does not display any data. (VA-6594)
• Restarting service monitor service requires logout and login to the configuration user interface. (VA-6531)
• Number format is not displayed as expected in reports for English-Germany locale. (VA-6530)
• Utilization dashboard CSV file does not display the date in ISO format. (VA-6523)
• Vocera logo and menu are not displayed when the user refreshes the Web browser in Report Scheduler and User Management screens. (VA-6450)
• In Vocera Platform 6.0, the Device Types filter in visualization server does not include Vocera Vina. (VA-6421)
• Data is not displayed as expected on User Activity Details dashboard when a message is sent to one user, and one group and the same user's group is added in the conversation. (VA-6369)
• Date format is not displayed as expected in dashboards for English-Singapore, Australia and Malaysia locale. (VA-6361)
• Data is not displayed as expected for Conversation Type and Conversation Subject columns in VMP messages table when another user is added to the conversation or subject is changed before normalization is run. (VA-6353)
• Number format does not display as expected in reports for English-South Africa locale. (VA-6352)
• Special characters such as double quotes and backslash used in the subject field of VCS conversation are not displayed appropriately in the Vocera Analytics database. (VA-6349)
• CSV file of dashboards that contain trends does not display the date in ISO format. (VA-6330)
• Message text from VMI is not fully parsed to Vocera Analytics as expected when [CR] is included in the message text. (VA-6161)
• When a new user is added to an existing conversation, Sent At time is displayed incorrectly for the newly added user for existing chat messages in Message Details dashboard. (VA-6090)
• In certain scenarios, call duration of a broadcast might not be accurate, if receiver of the broadcast disconnects before the broadcast ends. (VA-5791)
• The Finished At time displays incorrectly when a broadcast or normal call is initiated for group or user in an instant conference. (VA-5733)

Vocera Analytics Release 1.0.0

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

• 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-5433)
• In User Interruptions and Group Interruptions page, the group ID is displayed instead of group name for email messages. (VA-5409)
• 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-5392)
• Broadcasts calls made from telephones does not have group information and will display as Unknown or Null in dashboards and reports. (VA-5373)
• The Unit Summary widget does not sort alphabetically for units of the same name from different facilities in Interruption Summary dashboard. (VA-5207)
• The Day field displays 31 days irrespective of the month selected in Schedule section of Add Package page. (VA-5179)
• 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-5154)
• 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-5117)
• 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-5102)
• The Source Details widget displays Interrupt Type, Priority, and Description even for data with 0 count in Unit Interruption Report. (VA-5074)
• Reports cannot be scheduled after the current session expires. Workaround: Log out and log in again to schedule a report. (VA-5073)
• Breadcrumbs are not supported in Group Interruption dashboard in Firefox browser. (VA-5067)
• Filter selection is carried forward from one dashboard to another even when a filter is not applied. (VA-5064)
• Mobile User Activity and Mobile Unit Activity Reports show a lower text message count when events escalate. (VA-5022)
• 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-5008)
• 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-5004)
• 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-4983)
• Data migration is not supported for Simultaneous User Login report. Hence, historical data are not displayed. (VA-4915)
• Date range is missing in exported Engage reports. (VA-4905)
• 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-4873)
• 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-4784)
• Incorrect data is displayed for calls made to Groups with same name from a different facility. (VA-4720)
• The warning pop up window in Reports does not close automatically even after you navigate to other pages. (VA-4719)
• The option Unknown is not available in Access Point Locations filter in Speech Recognition Location Details Report. (VA-4667)
• In certain scenarios, Reports display http error. Workaround: Refreshing the Web page resolves the issue. (VA-4398)
• 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-4304)
• The Add package page is displayed from the middle of page if you scroll down the Report package page and click Add package. (VA-4301)
• Opening two or more reports in the same Web browser displays a random report. Workaround: Use different browsers to view multiple reports simultaneously. (VA-4007)
• 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-3798)
• The Call Forward functionality is not entirely supported. (VA-256)
• Panic broadcasts are not supported. (VA-241)