Dashboards—Display data based on defined metrics and key performance indicators (KPIs) that you can analyze and track.
Reports—Provide logs that the
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
Before you install
The details on the hardware requirements for the Vocera Analytics Server database are as follows:
Small | Medium | Large | |
---|---|---|---|
Memory | 32 GB | 64 GB | 128 GB |
CPU | Octa-core | Octa-core | 12 Core |
Disk Space | 500 GB HDD (per year) with SSD Cache | 1 TB HDD (per year) with SSD Cache | 2 TB HDD (per year) with SSD Cache |
Operating System |
|
|
|
Browser Support | Firefox version 121.0 or later, Safari version 17.5 or later, Google Chrome version 125.0.6422.142 or later (JavaScript must be enabled), Microsoft Edge version 125.0.2535.92. | ||
Database (provided) | MariaDB (MySQL) | MariaDB (MySQL) | MariaDB (MySQL) |
Validation Metrics: Performance Expectations
Data Inputs | Small | Medium | Large |
---|---|---|---|
Vocera Voice Server Users | 450 | 2000 | 5000-20000 |
VMP Users | 200 | 3000 | 10000 |
Beds | 293 | 500 | 1000 |
Engage users | 450 (225 per shift) | 1000 (500 per shift) | 2000 (1000 per shift) |
Clinical Alarms | 2200 | 5000 | 9500 |
Nurse Call Alerts | 3200 | 11000 | 22000 |
Orders | 400 | 1200 | 2400 |
Lab Alerts | 24 | 75 | 150 |
VMI Messages | 2000 messages/day | 10000 messages/day | 60000 messages/day |
Calls Per Day | 2000 calls/day | 10000 calls/day | 60000 calls/day |
VCS Messages | 9000 messages/day | 40000 messages/day | 400,000 messages/day |
To use the Vocera Analytics Server database, you must have the necessary software version available:
Other Considerations
To use Vocera Analytics, you must consider the following product requirements:
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)
This section summarizes the new features and enhancements in this release.
This release includes the following new features and enhancements:
The following third-party software versions are included in this release:
3rd-party Software | Version |
---|---|
Java | Azul Zulu JDK 8.78.0.19 |
MariaDB | 10.6.17 |
Node.js | 20.12.2 |
Tomcat Version | 9.0.88 |
This release includes the following new features and enhancements:
You can now upgrade from the following Vocera Analytics versions:
The following third-party software versions are included in this release:
3rd-party Software | Version |
---|---|
Java | Azul Zulu JDK 8.74.0.17 |
MariaDB | 10.6.16.0 |
Node.js | 18.19.0 |
Tomcat Version | 9.0.83 |
This release includes the following new features and enhancements:
For more information on Response dashboard, see https://pubs.vocera.com/platform/va/1.4.1/help/va_admin_help/index.html#platform/va/1.4.1/topics/va_int_user_response.html.
You can now upgrade from the following Vocera Analytics versions:
The following third-party software versions are included in this release:
3rd-party Software | Version |
---|---|
Java | Azul Zulu JDK 8.62.0.19 |
MariaDB | 10.6.8.0 |
Node.js | 16.15.1 |
Tomcat Version | 9.0.68 |
This release includes the following new features and enhancements:
This release includes the following new features and enhancements:
For information on What's Fixed in this release, see What's Fixed in Vocera Analytics 1.3.1.
This release includes the following new features and enhancements:
For information on What's Fixed in this release, see What's Fixed in Vocera Analytics 1.3.0.
The following list contains fixes and improvements made to the
The following issues are fixed in
The following issues are fixed in
The following list is specific to Vocera Analytics 1.4.3:
The following list is specific to Vocera Analytics 1.4.2:
The following list is specific to Vocera Analytics 1.4.0:
The following list is specific to Vocera Analytics 1.3.1:
The following list is specific to Vocera Analytics 1.2.4:
The following list is specific to Vocera Analytics 1.2.0
The following list of known issues are existing from Vocera Analytics release 1.0.0
Vocera Analytics has a few limitations. For more information, refer to Vocera Analytics Limitations.
This section describes the database schema changes from
anl_dim_tiername_mapping: Stores tier name mapping values for the escalation tiers used in the Vocera system. The value used are 0 for primary, 1 for secondary, and 2 for tertiary.
The following section lists the modified columns to the existing table.
Table Name | Column Name | Description |
---|---|---|
evtcontext |
DeviceId UserName CC_CallWith CC_CallWithId PC_CallWith PC_CallWithId HC_CallWith HC_CallWithId WC_CallWith WC_CallWithId LC_Flat MC_Flat GC_Flat CC_Flat MC_Context CC_ProcessingEvents IC_Cur_Context IC_Pre_Context IC_Flat_Context |
Modified character set to utf8mb4. |
anl_conversation_message_history | nick | Modified character set to utf8mb4. |
summarymessages | unit | Modified to varchar (10240) |
summaryvmpconversations | unit | Modified to varchar (10240) |