Message Routing for Linked Users

For linked profiles, message routing to end-user devices differs depending on whether your on-premises solution includes both a Vocera Voice Server and the Vocera Messaging Platform, or if it is a VS-only solution.

• If you have both the VS and VMP in your on-premises solution, text messages initiated by users of any application (for example, VST, VCS, Staff Assignment, the User Console, and so forth) are sent to the VST handheld client; text messages initiated by systems are sent to the badge.

  Because integrations (such as nurse call or patient monitoring integrations) frequently take advantage of specific voice capabilities of the badge, all messages initiated by a system are delivered only to the badge, and not to the VST client. In addition, the badge continues as the sole recipient of email messages sent by the Vocera Voice Server, because those messages are also a critical component of certain integrations, such as the Vocera Environmental Services Integration. All user-initiated text messages are delivered to the VST client only.

• If you have a VS-only on-premises solution, text messages initiated by the VST client are sent to the VST handheld client; text messages initiated by all other means are sent to the badge.

  Note: If the user has never logged into the VST handheld client, messages are sent to both the handheld client and the badge, to ensure delivery. After a user has logged in for the first time, the device is considered active and messages are sent as described above.

  Text messages initiated by users of other applications, such as Staff Assignment and the User Console, as well as messages initiated by systems, are sent to the badge.