Vocera Analytics
Release Notes - Version 1.3.0
Updated: March 30, 2023
About Vocera Analytics
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:
Prerequisites
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:
Note: The requirements are different for small, medium, and large servers.
|
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 |
- Windows Server 2019
- Windows Server 2016
- Windows Server 2012
|
- Windows Server 2019
- Windows Server 2016
- Windows Server 2012
|
- Windows Server 2019
- Windows Server 2016
- Windows Server 2012
|
| Browser Support |
Internet Explorer 11, Firefox version 45.0.1.0
or later, Safari 11.1.2 or later, Google Chrome version 70 or
later (JavaScript must be enabled). |
| Database (provided) |
MariaDB (MySQL) |
MariaDB (MySQL) |
MariaDB (MySQL) |
Note: To run properly, the Vocera Analytics Agent running on a Vocera Voice Server (VS) / Vocera
Platform 6.x will require 2 GB of RAM when interacting with a small or medium Vocera Analytics
Server database and 4 GB of RAM when interacting with a large Vocera Analytics Server
database. If the VS does not have sufficient memory to meet the mandated minimum memory for
the VS plus the needs of the Vocera Analytics Agent, memory will need to be added to the VS.
For example, a VS running version 5.2.3 requires a minimum of 8 GB of RAM. If the Vocera
Analytics Agent will be interacting with a large Vocera Analytics Server database requiring 4
GB of RAM, the server running the VS and the Vocera Analytics Agent must have a minimum of 8 +
4 or 12 GB of RAM installed. If it does not, sufficient RAM to meet or exceed the 12 GB
requirement should be added. If the VS is running in a virtual environment, Memory Over
Subscription is not supported and the Host Server should have sufficient physical RAM to
support the memory allocated to the Guest Servers plus the Hypervisor.
Validation Metrics: Performance Expectations
- Reports and Dashboards: One month of data displays in 10-15 seconds
- Data Exports: 30–45 seconds
| 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 |
Hardware Requirements for Microsoft Azure Platform
The details on the hardware requirements for the Vocera Analytics Server on Microsoft Azure
Platform are as follows:
| Requirement |
Large Deployments |
| Memory |
224 GB |
| CPU |
16 Core (with CPU speed 2.5 GHz or above) |
| Disk Space |
2 TB HDD (per year) with SSD Cache |
| Operating System |
- Windows Server 2019
- Windows Server 2016
- Windows Server 2012
|
| Browser Support |
Internet Explorer 11, Firefox 45.0.1.0 or later, Safari 11.1.2 or later, Google
Chrome version 70 or later (JavaScript must be enabled) |
| Database Provided |
MariaDB (MySQL) |
| VM Size |
Standard H16m_Promo |
| Virtual Memory (Pagefile.sys) |
256 GB |
| IOPS |
> 20000 (not less than 20000) |
Vocera Analytics software
prerequisites:
To use the Vocera Analytics Server database, you must have the necessary software version
available:
- Vocera Voice Server version 5.1 -
5.5.
- Engage Platform version 5.5 and later, with EMDAN version 1.9x and later.
- Vocera Messaging Platform version 5.2.2
- 5.5.
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.1 - 6.3
- 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:
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 and Enhanced Features
This section summarizes the new features and enhancements in this release.
New and Enhanced Features in Vocera Analytics 1.3.0
This release includes the following new features and enhancements:
New Features
- Platform Support—Vocera Platform 6.3.3 is added in this release.
- Tomcat Version Support—Tomcat version 9.0.37 is added in this
release.
Enhancements
- Event Index Dashboard—Five new widgets are added, namely Saved
Events, Interruptions, Top 10 Event
Description Trend, Top 10 Interruption Description
Trend and Event Details by Department. Also two
existing widgets % Accepted and % Declined are
removed.
- Inventory Status dashboard—Optimized the performance by considering data only for
the last 6 months.
- User Interruption Dashboard—Two new fields Bed and
Description are added in Details widget. The
Bed field displays both the room and bed number. The
Description is for alert and alarm data. Both fields are searchable
through the Search option in the Details
widget.
- Pipeline Enhancements—
- For Voice Server source: Improved database query failure to avoid data loss.
- For Engage source: By default, the SetJobProcess is set to
Min.
- Email notification with problem description—Whenever all reports/dashboards in a
scheduled package fail, the corresponding package recipients now receive information about
the issue in the email instead of blank emails.
- Improvements to User Name Filter—Login id is displayed to differentiate two
identical user names. To identify inactive users, [X] is suffixed to
the user name. Data populated for this filter is lazy-loading enabled.
- Asset Tracking Improvements—Improved device activity for better tracking.
For information on What's Fixed in this release, see Fixed Issues in Vocera Analytics 1.3.0.
New and Enhanced Features in Vocera Analytics 1.2.4
This release includes the following features:
New Features
Enhancements
- Release Version Identification—Installed Vocera Analytics Release Version is now
available in Database table and Vocera Analytics log files.
- Processor Improvements:
- The processor execution duration is now displayed in Vocera Analytics log files.
- When a processor aborts, the record is closed along with the timestamp when the error
was detected.
- Improved connectivity between Flume service and Voice Server—Manually copying of
Jar files are no longer required for Voice Server upgrade.
- Installer Improvements—Users can now upgrade from any version of Vocera Analytics
(1.2.0, 1.2.1, 1.2.3) to the latest version (1.2.4).
- Pipeline Optimization—Optimized the mechanism of few processors for increased
stability and performance of the pipeline.
- Sorting of Scheduled Packages—A new field Next Run at is
added to the Scheduler page to sort the packages based on the package scheduled
time.
- Improvements to Events Captured—Few events were captured from both active and
passive Voice Servers. With VA 1.2.4, these will be processed only from active Voice
Server.
- Wildcard Mask Support—Wildcard Mask feature is enhanced in affected dashboards and
reports.
New and Enhanced Features in Vocera Analytics 1.2.3
Vocera Analytics 1.2.3 is a maintenance release only. It contains no new features.
New and Enhanced Features in Vocera Analytics 1.2.0
This release includes the following features:
New Features
- Data Purge—Allows the administrator to reduce the storage footprint of the Vocera
Analytics database and delete fact data beyond the number of months being retained. The
Vocera Analytics 1.2.0 suite includes an admin script that purges data from both Landing
(ldg) and Vocera Analytics (vocera_analytics) databases. By default, the script is
configured to retain data for 36 months but it can be modified.
- PDF export for Dashboards—Dashboards can be exported to PDF format.
- Platform Support—Vocera Platform 6.1 is added in this release.
- Role Management—Allows you to create new roles and add dashboards and reports to
the role. You can also assign these roles to users based on the activities each user
performs.
- Schedule Dashboards—Dashboards can be scheduled in addition to reports.
- VMP License information—Added VMP license information to License
Dashboard.
Enhancements
- LDAP—Vocera Analytics now supports LDAP over SSL.
- Messaging Entities—Added support for new messaging entities such as Smartbadge,
Vocera Vina, and Web console.
- Smartbadge—Smartbadge with M2 and M3 modes are now supported.
- Speech Recognition Algorithm—The formula to calculate speech recoginition is
modified. For more information, refer to Speech Recognition Calculations Overview.
- Terminology Update—To be consistent with the terminology used across Vocera
products, Unit is replaced with Department and Nurse is replaced with
User in the respective dashboards and reports.
New and Enhanced Features in Vocera Analytics 1.1.0
This release includes the following features:
New Features
- Platform Support—Vocera Platform 6.0 is added in this release.
- Dashboards—Three new dashboards are added in this release. Following are the
details:
- Conversation Summary—Provides the summary of conversation for users in a Vocera
system.
- Conversation Activity—Lists the details of every conversation that had activity for
the selected date range.
- Message Details—Provides the message count and message details categorized by
facilities or units within an organization.
- Instant Conference—Added instance conference as a call type in the following
dashboards and reports:
- Dashboard
- Call Details
- Call Summary
- Group Interruptions
- Interruption Summary
- Location Call Summary
- Unit Interruption Summary
- User Activity Details
- User Call Details
- User Interruptions
- Voice Index
- Reports
- Outgoing Calls Details
- User Activity
- Engage Support—Multi-site Engage server support is added in this release.
Enhancements
New and Enhanced Features in Vocera Analytics 1.0.0
Version 1.0.0 is the initial release of Vocera Analytics. This release
includes the following features:
- 30 dashboards and 33 reports.
- 360° view of calls, broadcasts, texts, alarms, alerts in a single location that is
represented visually for all Vocera solutions.
- New Vocera performance metrics.
- Usage analysis for system improvements and executive return on investment for all Vocera
products.
- Modern infrastructure that provides:
- Simple User Interface (UI) for both clinical and technical personnel.
- Improved performance.
- Enterprise scalability for multiple facilities.
- Three years of data storage.
- Database schema availability for custom reporting.
Fixed Issues
The following list contains fixes and improvements made to the Vocera Analytics in this release.
Fixed Issues in Vocera Analytics 1.3.0
The following issues are fixed in Vocera Analytics 1.3.0:
- VA-10144 - Location name is not displayed on dashboards and reports if the access
point was provided in upper case in Vocera Platform.
- VA-10133 - Device details such as Owner Group, Owning Facility, Label, Status,
Notes, Serial Number were missed as the device MAC address was provided in upper case in
Vocera Platform.
- VA-9908 - Event Index dashboard did not display data for specific days.
- VA-9902 - The search operation in Description filter takes
a longer time to populate the values in Event Index dashboard and reports in Interruption
folder.
- VA-9808 - Data too long for column 'MC_Flat' exceptions' error resulted in
broadcast call data missing in analytics.
- VA-9782 - Tomcat error displayed on the Analytics Server upon logout and login
and upon reboot.
- VA-9743 - Critical vulnerability scan issue noticed on Vocera Platform servers
that use admin/admin login credentials for Service Monitor.
- VA-9649 - While executing group dimensions, pipeline crashed and stopped.
- VA-9648 - Inadequate warning message was displayed when Spark failed to connect
to flume.
- VA-9602 - Flume starts reading data from the beginning when status files query
and conf file query does not match.
- VA-9601 - VMP Flume status files were not updated after upgrading to VA 1.2.4.
- VA-9591 - Engage Flume status files were not updated after upgrading to VA 1.2.4.
- VA-9586 - Pipeline is not processing data.
- VA-9561 - While loading dimension data, plugin error occurred.
- VA-9560 - In certain scenarios, receiver name was empty on Messaging dashboard.
- VA-9550 After failure, Clinical Report processor processes data from the default
date of 1970-02-01.
Fixed Issues in Vocera Analytics 1.2.4
The following issues are fixed in Vocera Analytics 1.2.4:
- VA-9650 - When pipeline and database backup are running simultaneously, both
pipeline and database backup failures were noticed in the log file.
- VA-9649 - While executing group dimensions, pipeline crashed and stopped.
- VA-9601 - VMP Flume status files were not updated after upgrading to VA 1.2.4.
- VA-9591 - Engage Flume status files were not updated after upgrading to VA 1.2.4.
- VA-9586 - Pipeline is not processing data.
- VA-9561 - While loading dimension data, plugin error occurred.
- VA-9550 - After failure, Clinical Report processor processes data from the
default date of 1970-02-01.
The following issues are fixed in Vocera Analytics 1.2.4:
Fixed Issues in Vocera Analytics
1.2.3
The following issues are fixed in Vocera Analytics 1.2.3:
Fixed Issues in Vocera Analytics 1.2.0
The following issues are fixed in Vocera Analytics 1.2.0:
- VA-8825 The max file size limit for scheduler package email attachment was 8000 KB.
The user could not attach any package beyond 8000 KB. This issue is resolved as
administrators can now configure the max file size limit.
- VA-8724 The Vocera Analytics Flume agent default port conflicted with Voice Server
Nuance port. The default port for Vocera Analytics Flume agent is now reassigned to
7780. This issue is fixed.
- VA-8646 When the Vocera Analytics Checkpoint Directory on the Voice Server is too
large, Flume agent stops sending data and Vocera Analytics services stop subsequently.
- VA-8481 The MariaDB Temp Directory consumed approximately 30% of hard disk drive
when the environment was in Low on Disk Space state. This issue is fixed.
- VA-8299 A VMP source gets added into pipeline.json every time the
user clicks the Add button in the service monitor, when there is an issue in the
service monitor interface. This issue is fixed now and is no longer seen.
- VA-8188 Flume agent failed to pick the latest valid license file. This issue is
resolved.
- VA-7904 Trusted URLs given in uppercase were not working. This issue is fixed now.
- VA-7822 The Vocera Analytics installer accepted passwords beginning with special
characters that caused login errors. This issue is fixed as the installer does not accept
passwords starting with special characters.
- VA-7805 Due to filter restrictions to display only 25 entries, not all filtered
data was displayed for search criteria-based filters, such as Owner Group filter. The filter
restrictions are now expanded to display 50 entries and this value is also configurable.
Hence this issue is now resolved.
- VA-7691 Platform Health Index dashboard displayed B2000 data despite the facility
not having any B2000 badge. This issue is fixed now.
- VA-7583 An error Recursion of EVENT DDL statements is forbidden is displayed
in the install log while upgrading Vocera Analytics 1.0 to Vocera Analytics 1.1. This issue
is fixed.
- VA-7171 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. This issue is fixed now.
- VA-7126 Data loading error is displayed on unit-related dashboards when a unit is
mapped using Manage Sites and crosswalk tables are not updated. This issue is fixed and is
no longer seen.
- VA-7060 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. This issue
is fixed now. Incorrect port numbers are no longer seen after an upgrade or unplanned
restart.
- VA-7046 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. This issue
is fixed now. Login event now gets updated accordingly.
- VA-6735 In certain situations, an error Could not start
process is displayed in the monitoring log. This issue is fixed and is no
longer seen.
- VA-6594 In Vocera Platform 6.0, Status Tracking dashboard does not display any
data. This issue is fixed now. Status tracking dashboard now displays data.
- VA-4905 Date range was missing in exported Engage reports. This issue is fixed and
is no longer seen.
Fixed Issues in Vocera Analytics 1.1.0
The following issues are fixed in Vocera Analytics 1.1.0:
- VA-5379 In Manage Users, after a user is imported successfully, the imported user
is not displayed. You no longer need to refresh the browser to display the imported user.
This issue is fixed now.
- VA-5309 Instant Conference (Push To Talk) functionality is not supported. This
issue is fixed now. Instant conference is now supported.
- VA-5067 Breadcrumbs are not supported in Group Interruption dashboard in Firefox
browser. This issue is fixed now.
- VA-4976 The Report Scheduler does not send emails even to the correct email address
if one of the recipient emails has an invalid email address. This issue is fixed now.
- VA-4971 The drop down filters that contain multiple values with the same name are
not differentiated to the user. This issue is fixed now.
- VA-4915 Data migration is not supported for Simultaneous User
Login report. This issue is fixed now and historical data are displayed.
- VA-4706 The Location column is blank when the Access Point
is not mapped to the location name in Asset Usage page. This issue is fixed and is no longer
seen.
- VA-4689 To display large datasets that include data for 1 month or all users, some
dashboards or reports may take several minutes. Some of the dashboards that may take longer
to display data are Integration Details, Location Statistics, User Activity Details, and
User Call Details. This issue is fixed now.
- VA-4065 Refreshing the browser incorrectly loads the landing page of Vocera
Analytics. This issue is fixed and is no longer seen.
Known Issues
This release includes the following known issues:
Vocera Analytics Release 1.3.0
The following list is specific to Vocera Analytics 1.3.0:
- VA-10655 - Broadcast call entry is missing when call is placed via VCS device
without using voice command (VCS device menu options)
- VA-10288 - Filters do not work as expected, if the
Description filter contains comma.
- VA-10212 - Event Index dashboard might take more time to display data. For
example, to display data for 1 day, it takes approximately 20 seconds.
- VA-10210 - If the device MAC address is provided in upper case in Vocera
Platform, the fields Serial Number, Label
are blank and Owner Facility, Owner Group
display Unknown in Status Tracking dashboard even if Owner Group
and Owner Facility are added.
- VA-10173 - Receiver Device ID and
Name are displayed as IP address when a broadcast is done from
Telephone.
- VA-10167 - Receiver Device Details are Null in
fctcalls table when a broadcast is done from telephone.
- VA-10140 - User Names filter in Dashboards and Reports
does not display names in sorting order.
- VA-10127 - Data is displayed for default date range instead of selected date
range and filter if the description selected contains a percentage value in exported PDF.
- VA-10124 - From VMP 5.3.3 onwards, the MaxInUse value in
License dashboard will not match with In Use value in VMP reports.
- VA-10120 - In License Dashboard, values for Latest
Assigned and Max In Use fields are incorrect, if more
than 10000 users are assigned to VMP License.
- VA-10078 - In certain scenarios, blank entry is displayed for lazy-loading
filters in Filter Summary in few dashboards and reports.
- VA-10045 - Exported PDF of reports that have User Name filter do not display
[X] for deleted user and username.
- VA-10023 - In exported CSV of Department Interruption Summary dashboard, if the
same event has accepted or declined responses, then Others category
entry will not be found.
- VA-10016 - In User Interruptions dashboard, response data will not be accurate
when user received multiple deliveries and provided different response for the same event.
- VA-10010 - Filter Summary bar is blank or takes more time to display if any of
the filters have more data to load.
- VA-9958 - In Interruption dashboards, when Clinical Alert is sent, duplicate
entries are displayed.
Vocera Analytics Release 1.2.4
The following list is specific to Vocera Analytics 1.2.4.2 patch:
- VA-9794 - In certain scenarios VA 1.2.4.2 patch might fail to complete
successfully Workaround: Re-run the VA 1.2.4.2 patch.
The following list is specific to Vocera Analytics 1.2.4:
- VA-9524 - When a user logs in first to the Smartbadge and then the VCS device,
Smartbadge Logout in User Activity Details Dashboard and Report is
displayed after the user presses the Genie button on the Smartbadge. Also, the logout time
displayed is incorrect.
- VA-9522 - The User Activity Details Dashboard and Report display an additional
(login and logout) entry for the same user when the user logs in through the Vocera Vina
device.
- VA-9517 - In User Activity Details dashboard, the values in
Duration column is not displayed in sorted order.
- VA-9419 - Incorrect data for user call is displayed when the receiver user gets
an urgent call while the receiver user is already in another call and the call is in
progress.
- VA-9418 - Rejected call entry is also considered as a dropped call when the first
user rejects the call, second user accepts the call, and call gets dropped from the caller
side.
Vocera Analytics Release 1.2.3
The following list is specific to Vocera Analytics 1.2.3:
- VA-9170 - The Vocera Analytics 1.2.3 HF installer fails while taking a
configuration backup when upgrading Flume Agent VA 1.2.0 to VA 1.2.3 on Voice Server.
Workaround: To rectify this issue, refer to KA 8054.
- VA-9043 - The department name in Department Summary and Mobile Activity
Department reports is displayed beyond its column length.
- VA-9021 - Call duration data is incorrect for the first call when the user puts
the first call on hold and accepts the second call when Vocera Platform 6.2 is the source.
- VA-9020 - An additional call is shown when a call is made to a group and
Member Name - Singular is provided for that group when Vocera
Platform 6.2 is the source.
Vocera Analytics Release 1.2.0
The following list is specific to Vocera Analytics 1.2.0
- VA-8801 - Login and Logout events are not captured if the user is off-prem.
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-6450 - Vocera logo and menu are not displayed when the user refreshes the Web
browser in Report Scheduler and User
Management screens.
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-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-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-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-4719 - The warning pop up window in Reports does not close automatically even
after you navigate to other pages.
- 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.
Vocera Analytics has a few limitations. For more information, refer to Vocera Analytics Limitations.
Database Schema Changes in Vocera Analytics 1.3.0
This section describes the database schema changes from Vocera Analytics 1.2.4.2 to Vocera Analytics 1.3.0 release:
New tables added in this release
summary_events_interruptions: A new table added in Vocera Analytics 1.3.0 release.
Stores summary of interruptions by all events along with other event specific
information.
The following section lists the column added to
summary_events_interruptions table and its description:
| Column Name |
Description |
| event_id |
bigint
The id of the event.
|
| source_id |
bigint
The source id of the appliance providing data.
|
| event_class_name |
varchar
The source of the alarm/alert. For example: NURSE CALLS, PATIENT MONITOR.
|
| event_updated_at |
datetime
The event updated date.
|
| event_created_at |
datetime
The event creation date.
|
| facility |
varchar
The site or facility from which the data was collected.
|
| unit |
varchar
The unit from which the data was collected.
|
| description |
varchar
The alert/alarm description. For example: APNEA, ASYSTOLE.
|
| isDelivered |
bit
Displays 1 if delivered, or 0 otherwise.
|
| interruptions |
int
Count of delivered deliveries of the event.
|
Columns added to existing tables
The following section lists the columns added to existing tables.
| Table Name |
Column Name |
Description |
| fctdeviceactivity |
ActivitySource |
Displays device activity source information |
| TxMillis |
Stores epoch time of activity Started At column |
| |
|
Datatype changes of existing columns
The following section lists the datatype changes made to existing columns.
| Table Name |
Column Name |
Old Datatype |
New Datatype |
| anl_event_detail_history |
event_care_team_name |
Text |
Medium Text |
Primary Key changes to existing table
The following section lists the primary key changes made to existing table.
| Table Name |
Old Primary Key |
New Primary Key |
| fctdeviceactivity |
DeviceOnlineSessionId |
DeviceId, TxMillis |
For information on Database Schema changes in Vocera Analytics 1.2.4 release, see https://pubs.vocera.com/rnotes/ReleaseNotes_va_124.html#unique_21.