Vocera Care Team Sync

Release Notes - Version 2.6.0.28

Updated: April 19, 2021

About Vocera Care Team Sync

The Vocera Care Team Sync (CTS) application integrates the care team role assignments of the Vocera Voice Server (and optionally the Vocera Staff Assignment application) with a foreign clinical care team assignment system.

CTS allows you to choose a "source of truth" for your assignments—either the assignments in the Vocera Voice Server database or a foreign clinical assignment system—and optionally synchronize the care team assignments of the two systems.

Documentation for the most recent released version of VCTS is available online in the Care Team Sync Configuration Guide .

What's New

Documentation for the most recent released version of VCTS is available online in the Care Team Sync Configuration Guide.

The rest of this section summarizes the new features in this release.

What's New in Vocera Care Team Sync 2.6.0

This section summarizes the new features in the 2.6.0 release.

What's New in Vocera Care Team Sync 2.6.0.28

Vocera Care Team Sync 2.6.0.28 is a maintenance release that does not introduce any new features.

What's New in Vocera Care Team Sync 2.6.0.25

Vocera Care Team Sync 2.6.0.25 is a maintenance release that does not introduce any new features.

What's New in Vocera Care Team Sync 2.6.0.24

The CTS 2.6.0 solution provides the following new features:

  • Logging of both inbound and outbound requests for the Hill-Rom connection. (EVSCTS-4028)

    See the Care Team Sync Configuration Guide for complete information.

  • Automatic synchronization of user RTLS devices from the Vocera Voice Server to the Hill-Rom system. - (EVSCTS-4025)

    Specify the device assignments in the Cost Center field of the Vocera Voice Server user profile, and CTS replicates the assignments in Hill-Rom.

    See the Care Team Sync Configuration Guide for complete information.

  • Support for ADT messages that do not contain a ROL segment in the HL7 integration. - (EVSCTS-4026)

    Not all ADT messages include a ROL segment. For example, ADT 12 (Cancel Transfer) and ADT 13 (Cancel Discharge) do not include a ROL segment in accordance with the HL7 specification. CTS now correctly handles these ADT messages without updating assignments.

What's New in Vocera Care Team Sync 2.5.1

This section summarizes the new features in the 2.5.1 release.

What's New in Vocera Care Team Sync 2.5.1.38

Vocera Care Team Sync 2.5.1.38 is a maintenance release that does not introduce any new features.

What's New in Vocera Care Team Sync 2.5.1.35

The Vocera Care Team Sync 2.5.1.35 solution provides the following new features:

  • Purge HL7 records from the database to prevent it from growing excessively large and causing performance issues. (EVSCTS-2945)

    You configure the range of data to preserve and the interval at which the purge runs on every HL7 connection.

  • DNS name support for adapters (EVSCTS-3100).

    CTS now allows you to specify fully qualified domain names as well as IP addresses when you configure an HL7 connection.

What's New in Vocera Care Team Sync 2.5.0

This section summarizes the new features in the 2.5.0 release.

What's New in Vocera Care Team Sync 2.5.0.261

Vocera Care Team Sync 2.5.0.261 is a maintenance release that does not introduce any new features.

What's New in Vocera Care Team Sync 2.5.0.258

The CTS 2.5.0.258 solution provides the following new features:

  • The CTS Console user interface has received a major upgrade. Following is a list of the most significant changes; full documentation on the new user interface is available in the Care Team Sync Configuration Guide.

    • The CTS Console now supports Rauland, Hill-Rom, and HL7 adapters.

      The interface has been reorganized so it is no longer focused exclusively on HL7 connections. The navigation bar has replaced the link to the dedicated HL7 Interface page with a link to a new Connections page that lets you manage all connections.

    • The Patient Census page is no longer available.

    • The navigation bar has replaced the link to the Backup & Maintenance page with a link to a new Tools page. Backup & Maintenance is now available as a tab on the Tools page.

    • New features on the Tools page include the ability to map users between CTS and the foreign system, the ability to define units, and the ability to configure email alerts.

    • You no longer need to create SQL scripts to update the database. All configuration that was previously done directly in the MySQL database is now done through the user interface.

    • Credentials to access the VAI API on the Vocera Voice Server are now entered through the user interface, instead of being entered in the vcts.properties file. You no longer need to obfuscate credentials manually; instead, credentials are stored and obfuscated in the CTS database.

      Important: Credentials provided in vcts.properties are no longer supported. If you are upgrading from a previous version, enter your credentials in the user interface.
  • The 3rd-party Java Runtime Engine has been upgraded to JRE 1.8.0_51.

What's New in Vocera Care Team Sync 2.4.0

The CTS 2.4.0 solution provides the following new features:

What's New in Vocera Care Team Sync 2.3.0

The CTS 2.3.0 solution provides the following new features:

The CTS 2.3.0 solution also includes the following upgraded third-party components:

What's New in VCTS 2.2.0

The Vocera Care Team Sync 2.2.0 solution is primarily a maintenance release to address known issues. It also includes the following upgraded third-party components:

What's Fixed

This section provides information about fixes and improvements made to the Vocera Care Team Sync product.

What's Fixed in the CTS 2.6.0 Release

This section summarizes what is fixed in the 2.6.0 release.

What's Fixed in the CTS 2.6.0.28 Release

  • The Hill-Rom adapter incorrectly rejects roles that do not have assignments during reconciliation. (EVSCTS-4131)

    The adapter now properly handles unmapped roles during reconciliation.

  • If the CTS system restarts for any reason, it incorrectly re-processes HL7 messages it has already processed in addition to the new messages it has received. CTS should only process new messages after a restart. (EVSCTS-4139)

    CTS now sets the "last processed time" to the time of the first message received after startup, preventing duplicate processing.

    As a consequence of this fix, any messsages CTS has received but not yet processed when it shuts down will not be processed after restart; there is a small likelihood that this situation will occur. Workaround: after restart, manually remove any unprocessed messages from the MESSAGE table in the database and re-send these messages from the HL7 source.

What's Fixed in the CTS 2.6.0.25 Release

  • The Hill-Rom system rejects assignments from CTS when the publisher connection sends the staff ID without the first and last name of the user. This situation occurs unless a Hill-Rom subscriber connection is configured along with the publisher connection. (EVSCTS-4118)

    The requirement to configure a Hill-Rom subscriber connection has been lifted, and the publisher connection now works as expected.

What's Fixed in the CTS 2.6.0.24 Release

  • Extended the character limit for Rauland logging to minimize the likelihood of truncation. - (EVSCTS-4028)

    CTS logs inbound and outbound requests for Rauland. See the Care Team Sync Configuration Guide for complete information.

What's Fixed in the CTS 2.5.1 Release

This section summarizes what is fixed in the 2.5.1 release.

What's Fixed in the CTS 2.5.1.38 Release

  • The CTS reconciliation fails with a null pointer exception if CTS receives an assignment from Rauland that does not have an associated role. (EVSCTS-4029)

    The initial reconciliation from Rauland (run during CTS start up) may fail if a role is not provided, leaving all assignments empty. With this hot fix, CTS now ignores assignments with a null role instead of failing.

What's Fixed in the CTS 2.5.1.35 Release

  • CTS may create duplicate null locations and units, affecting system resources. (EVSCTS-453)

    In this defect, if CTS fails to find a location or unit for any reason, it creates a "null" value in the database. In some situations, CTS creates multiple null values in the unit or location tables, potentially affecting the Java heap. This defect has been fixed, and the situation no longer occurs.

    Important: To implement this fix, the update script removes duplicate null locations and units from the database; as a consequence, however, the upgrade also removes any existing care team assignments for an HL7 adapter from the database. After the upgrade, the CTS system requires extended runtime—essentially the same amount of runtime that is required for a new deployment—to allow all assignments to propagate completely. If you are using an HL7 adapter, make sure to plan for this extended runtime before upgrading to CTS 2.5.1.
  • CTS may append a newline character to the last segment of an HL7 message, incorrectly delimiting it. (EVSCTS-451)

    CTS now correctly uses a carriage return to terminate an HL7 message.

  • The Last Updated column on the Sync Settings page is not currently in use. (DE14099/EVSCTS-460)

    The Last Updated column has been removed from the product. Use the Last Processed Time column on the Connections page to view the date and time that the most recent data was received from the associated system.

What's Fixed in the CTS 2.5.0 Release

This section summarizes what is fixed in the 2.5.0 release.

What's Fixed in the CTS 2.5.0.261 Release

  • CTS fails with a null pointer exception if it receives a delta of an HL7 ROL segment. (DE14441)

    This situation no longer occurs.

What's Fixed in the CTS 2.5.0.258 Release

  • The CTS Console does not display site information. If you support multiple sites that have one or more units with identical names, you cannot disambiguate the units in the Patient Census and Sync Settings screens of the CTS Console. (US21243)

    You can now specify site information when you define a unit, and it is displayed on the Sync Settings page.

  • You must define an ADT feed before specifying an IP address for the Vocera Voice Server. Failure to specify the feed causes the VCTS database to be purged of assignments, patient locations, and unit roles. (DE8039/US15903)

    The workaround of defining a feed before specifying an IP address for the Vocera Voice Server is no longer necessary.

  • Assignments are removed from the CTS database and the Staff Assignment console if the connection between CTS and the Hill-Rom system is interrupted. (DE12988)

    Assignments are no longer removed if the connection is lost for any reason.

  • CTS does not load the VSI properties from the vcts.properties file; consequently, the VSI default values cannot be overridden. (DE12156)

    The vsi.property.event.service.client.ip property now lets you override this default behavior.

What's Fixed in the CTS 2.4.0 Release

What's Fixed in the CTS 2.3.0 Release

Known Issues

This section provides information about known product defects and limitations in the current release.