This section summarizes the new features in this release.
Documentation for the most recent released version of EVS is available online at Vocera EVS Integration Deployment Guide.
Support for the Epic February 2019 release.
EVS now passes the Epic Client ID in its web services call, allowing EVS to integrate with the Epic February 2019 release. (EVSCTS-4130)
Support for authentication with Epic now available.
If you specify a user name and password to the <epicRestWebService> element
in the pluginproperties.xml file for the Epic configuration,
Cancel request messages from Epic are now passed through to the end user's device.
If an Epic request is canceled for any reason,
EVS 1.1.0 is a maintenance release. It picks up the features that were implemented for the internal EVS 1.0.2 release and packages them into a product that is generally available.
Start Break, End Break, and End Shift voice commands added.
When Vocera device users are engaging in voice interactions, they can now use the Start Break, End Break, and End Shift voice commands.
Backup and restore script now available.
You can use a provided script to set up scheduled full and incremental backups of your EVS server. If necessary, you can then restore the EVS server from one of these saved backups.
New configuration parameters are available in the <configuration><voice><completion-query> section of evs.xml.
<ack-timeout/> specifies the amount of time (in seconds) to wait before sending an escalation to the administrator’s Vocera device (group) when a user responds to the completion query with a "No".
<nack-timeout/> specifies the amount of time (in seconds) to wait before sending an escalation to the administrator’s Vocera device (group) when a user fails to acknowledge the completion query with either "Yes" or “No”.
New configuration parameters are available in the <configuration><voice><inprogress-query> section of evs.xml.
<ack-timeout/> specifies the amount of time (in seconds) to wait before sending an escalation to the administrator’s Vocera device (group) when a user responds to the inprogress query with a "No".
<nack-timeout/> specifies the amount of time (in seconds) to wait before sending an escalation to the administrator’s Vocera device (group) when a user fails to acknowledge the inprogress query with either "Yes" or “No”.
EVS 1.1.1 requires one of the following Vocera components (in production and staging environments):
One of the following versions of Vocera Voice Server:
Vocera Voice Server versions 5.0.1 or greater (to support the Start Break, End Break, and End Shift voice commands)
An available VMI port to allow the Voice Server to connect to the Vocera Integration Platform server.
EVS requires the following ADT components:
Epic Systems 2014 (Production and staging environments)
The Epic Environmental Services module
A web services end point dedicated to the Vocera Environmental Services Integration in your Epic system.
In addition, EVS requires a dedicated email service account on your mail server. If you already have a Vocera Voice Server, do not re-use its existing email account.
To set up your EVS system:
This section summarizes the known issues that have been fixed in this release.
This release includes the following fixes:
No defect fixes.
This release of
This release includes the following fixes:
No defect fixes.
This release of
This release includes the following fixes:
DE10232 - Long email sent using VMI is now truncated if needed.
Email that is too long to be sent using VMI is now stripped of duplicate spaces and other unnecessary repeated characters and then truncated.
EVS 1.1.1 has no known defects or limitations.