The Vocera Platform is a next generation breakthrough in connecting patients to caregivers. This platform unites two premiere services within the industry; the Vocera Voice Server and the Engage Server, thereby giving your facility access to a comprehensive solution to meet your needs.

Documentation for the most recent released version of the Vocera Platform is available online in the Vocera Documentation Portal.

This section provides information about getting started for the current release. Vocera Platform 6.0.0 is the initial product release, and these are the tips for getting started.

Upgrade and Installation This initial release contains specific upgrade and installation paths that are listed below.

• Supported Upgrade Paths
  • You can upgrade if your facility is currently running Engage Server 5.5
  • You can upgrade if your facility is currently running Vocera Voice Server 5.X
• Upgrade Considerations
  • Upgrades are also allowed for Vocera Voice Server migrating from Windows to Linux

Features Not Supported In This Release This initial release is not compatible with the Voice Web Console, the Vocera Messaging Platform, and some Smartphone Applications. The following items are not available:

• Voice 5.X Web Console
  • Staff Assignment
  • User Console
  • Tiered Administration
• VMP 5.X Web Console
  • On-Call Scheduling
  • Messaging Console
• Smartphone Applications
  • Vocera Collaboration Suite
  • Vocera Secure Texting

This section summarizes the new features in this release.

The following list contains fixes and improvements made to the Vocera Platform.

This section provides information about known product defects and limitations in the current release. Vocera Platform 6.0.0 is the initial product release and these are the known issues.

Administration Console Issues

• When editing a user, an Administrator cannot select a contact where the user's calls will be forwarded to. (WEB-2596)

  Workaround: Users may configure their own forwarding to a contact through the voice commands on a badge, rather than in the Admin Console directly.

• Security policies may not be editable via a Remote Support connection. (WEB-2971)

  Workaround: None.

• A user created with Data Update appears to have a password when the field is actually null. (WEB-2789)

  When creating a user with a Data Update rule, the password fields do not display on editing the user. If attempting to save or delete the user, an error will occur until the reset password option is used.

• When the client proxy is in a bad state, the UI may infinitely redirect if the user previously had a valid login token. (WEB-2271)

  Workaround: Using the location bar in the browser, navigate to a valid URL with /ei/ after the domain.

  For example, check the state of the Client Proxy service:

  https://<ip>/ei/services/interfaces

  When an appliance is restarting or services fail over from one node to another in a cluster, this situation will typically resolve itself once the client proxy has had an opportunity to be started.

• When you delete a user in the Vocera Platform Web Console, the user is not logged out on the Unified Android client. If that deleted user tries to initiate a call, the Voice service on the Vocera Platform will fail. (SIV-2194)
• When using the Internet Explorer (IE) to access the Web Console, the preview sounds for Genie Voice, Greetings, and Ringtone options are not played. These options are available in the Genie Settings under Settings > User Defaults. (WEB-8149)

Platform Issues

• If you update the Network Settings of the server through the Web Console, the Timezone may reset to EST. (CASE-1012, PFM-11613)

  Workaround: Contact Vocera Customer Support and request the patch attached to CASE-1012.

• When a package is imported incorrectly, instead of providing an informative message, the system will give the user a "Page not Found" error. (PFM-6205)

  Workaround: Correct the errors in the import and reload the package.

• Messages received by the HL7 adapter and acknowledged as received prior to fail-over are lost during the fail-over. Additionally, any HL7 messages sent during the fail-over are also lost. (PFM-9009)

  Workaround: There is no workaround at this time.

• Any upgrade that initially was deployed using Engage 5.0 will not have a "Listen 443" statement in its Apache configuration. Platform 6.0.0 requires port 443 for desktop web clients. (PFM-10947)

  Workaround: Manually create the "ports.conf" file with the following statements:

  Listen 443
  NameVirtualHost *:443

• During periods of heavy I/O, replication may stop for a short time and the cluster may display a Failed status, although the database status is in the Ok state. When the replication occurs, alert/alarm delivery can be delayed. (PFM-11100)

• Attempting to delete a site fails when users are associated with the site. (PFM-11104)