Configuring the System-Level Voice Integration

The system-level voice integration allows EVS to send Vocera device users auto-generated reminders about updating the status of cleaning requests; it also sets up system-level defaults for the voice integration. You can optionally override these defaults in the vendor-specific sections of the integration.

Specify any parameters for the system-level voice integration in the <voice> section of the evs.xml file. You can customize the following main features of the voice integration:

• Completion query

  When a device user indicates that a cleaning request is in progress, Vocera waits a configurable amount of time and then asks if the user wants to mark it as complete (the "Completion query"). If the user says "Yes", Vocera updates the Epic system with the new status; if the user says "No" or does not respond, Vocera waits a designated amount of time and then re-sends the query to the user.

  The configuration parameters for the completion query allow you to customize the behavior of this feature.

• In-progress query

  When a user receives a cleaning request, Vocera immediately asks if the user wants to mark it in progress (the "In-progress query"). If the user says "Yes", Vocera updates the Epic system with the status; if the user says "No" or does not respond, Vocera waits a designated amount of time and then re-sends the query to the user.

  The configuration parameters for the in-progress query allow you to customize the behavior of this feature.

• Retry settings for message deletion attempts

  Vocera attempts to delete a message from a user's device after every successful state transition. Device users initiate a state transition by acknowledging messages that they receive. For example, when a user responds with a "Yes" to the prompt "Do you want to mark this request in progress", Vocera attempts to delete this message from the user's device. If the deletion fails, the values in the <delete><retry> section determine how often Vocera attempts to retry the deletion.

  The <voice><delete> section of evs.xml specifies system-level defaults for the delete retry feature. You can optionally override these settings in the pluginproperties.xml file for each vendor.

• Retry settings for message send attempts

  Vocera sends cleaning requests and status queries to a user's device as part of the Environmental Services integration. If the first delivery attempt for one of these messages fails due to a potentially recoverable error (for example, the user is not logged in), the values in the <voice><send> section determine how often Vocera attempts to re-send the message.

  The <voice><send> section of evs.xml specifies system-level defaults for the message retry feature. You can optionally override these settings in the pluginproperties.xml file for each vendor.

• Message escalation settings

  In the EVS integration, an escalation is a message that is sent to an administrator's Vocera device when an unrecoverable error occurs. The following events result in an escalation during the voice integration:

  • Sending a message to an invalid user ID
  • A timeout that occurs as a result of a message retry failure
  • A timeout that occurs as a result of a message delete failure

  The <voice><escalation> section of evs.xml specifies system-level defaults for message escalations. You can optionally override these settings in the pluginproperties.xml file for each vendor.

• Message settings

  In the EVS integration, a message is a cleaning request or reminder that is sent to the Vocera device of an Environmental Services employee. You can customize the tone that the device plays when this message arrives, as well as the priority of the message.

  The <voice><message> section of evs.xml specifies system-level defaults for the message customizations. You can optionally override these settings in the pluginproperties.xml file for each vendor.