If you are having problems getting Vocera Clinical Workflow Engine working, the following troubleshooting tips may be useful to you.
CWE should have unique site names.
To add sites, units, and user groups, you must import them using the vsa_data.txt file, which is obtained from the Vocera Voice Server. Beds are added using the CWE Console.
CWE 3.1.0 does not support Clinical Analytics.
CWE does not support or grant site-wide or unit-wide user permission to access the CWE Console.
Users imported from the Vocera Voice Server cannot log into the CWE Console.
Site and unit cannot be deactivated.
Alarm reason cannot be deactivated.
Workflow cannot be deactivated.
Once a bed is added, it cannot be deleted but can be deactivated or renamed.
When a bed name is renamed, not all the alarms generated for the bed are listed in the View Alarms list.
Workaround: In Advanced Search, select the All option for the Unit field to display all the alarms.
A maximum of 50 characters are allowed in Alarm Reason field.
An administrator user added through the CWE Console can access the CWE Console only.
In Nurse Call Connector, the normalizer port number should be unique to map the site name.
In the Vocera Voice Server, if a new site, unit, or user group is added that needs to be included in CWE, the vsa_data.txt file needs to be imported again to include this new entry. No automatic synchronization is available between CWE and the Vocera Voice Server.
If an entry is modified in the Vocera Voice Server, it is updated in the CWE server after the vsa_data.txt file is imported.
If any entity gets deleted from the Vocera Voice Server, it is not deleted from the CWE server after the vsa_data.txt file is imported.
When specifying the Vocera Voice Server in the CWE Console, you must provide the IP address of the Vocera Voice Server and not the host name.
In a load balancer environment, the server status shown in the CWE Console is not accurate, as the URL being specified is the load balancer URL and not the URL of the server that is currently active.
In a load balancer environment, the CWE Console is accessed using the load balancer's IP address or DNS name, and any CWE server may process the CWE Console request.
Workaround: In order to see the server status of a specific server, the actual server IP address needs to be provided when accessing the CWE Console.
In a load balancer environment, the server log download option may download the log files from any of the active servers.
Workaround: To download an individual server log, the actual server IP address needs to be provided when accessing the CWE Console.
In the Alarm Levels configuration section of the CWE Console, new ring tone names cannot be added.
To add ring tone names to the database, connect to the database using SQL Management Studio, select the MVisumAlerts database, and run the following query:
INSERT INTO [MVisumAlerts].[dbo].[RingTones] ([RingName],[RingPath]) VALUES ('ring tone name','')
In the CWE Console, the Locked Beds option in the Change Assignment dialog is not in use.
In the CWE Console Voice Server configuration, the VS Client ID field must be set to CWE. This prevents enunciation on the badge.
When a service is modified in the configuration file, it must be restarted.
You must configure Alarm Reasons in the Workflow Configuration before sending alarms for those reasons.
You must configure staff assignment before generating alarms for the beds that staff members are assigned to. Site-level and unit-level assignment should be saved before generating any alarms.
The default value for DataArchiveInterval in monitoring service is 15 minutes. Hence every 15 minutes it will archive the data from the main table. Alternately, the SQL job is added to archive the data from the main table. The flag IsToDataArchive is used to enable or disable this archiving. The default value of this flag is false. When the flag is false, SQL job does the first level archiving.
The DownloadMinutes configuration parameter specifies the amount of time during which the CWE Console server keeps data in the live data table before moving it to archive data tables. This parameter is used in the first-level archive, and is not configurable in the CWE Console. It is provided in the HandHeldCustomSettings table of the MVisumAlerts database. The default value for DownloadMinutes is 30 minutes.
The .JSON files from the processed folder get archived at the time interval configured. By default the IsToMove flag is set to false. This means the .JSON files will not be deleted from the processed folder but will be archived. In order to delete these .JSON files, change the flag in database to true using following query.
UPDATE [MVisumAlerts].[dbo].[MVisumFilesArchive] SET [IsToMove] = 1; GO
If CWE Console is not reflecting the latest data, you must refresh your browser. If the problem persists, clear your cache and restart your browser.
For example, you must refresh your browser if the Charge Nurse role is unassigned at the unit level but, in the Workflow screen, you are able to configure the Send to Charge Nurses(Unit) workflow action.
All JSON-related messages now contain a unique alarm ID along with the date and timestamp generated in all log files. Based on an alarm ID, further tracking can be done. The alarm ID can be found in the following services:
If Bed level assignment is done as None, the workflow will be stopped for that alarm even if there is further escalation action available.
When a new user is added in the Voice Server, it will take at least 15 minutes for the new user to be synced with CWE. In the intervening time, if any alarm is generated for the new user, and the same is acknowledged by the new user, then the Acknowledged By field will be blank.
Workaround: Reduce the VoceraSyncSleepTime to a lesser value in Vocera Alarm Monitoring Service and restart the service.
In HA mode, canceled alarms will not be deleted from the badge if the client ID is different while sending an alarm to the badge.
For example, in HA mode, assume an alarm Code Blue is generated on node 1 and sent to user group1 with client ID CWE1. Now the alarm is escalated to second level (user group2) by the Vocera Message Escalator service from the second node (node 2) with client ID CWE2. If the alarm is canceled (assuming the canceled alarm is received on node 1), only messages with client ID CWE1 is deleted from the badge. Messages sent/escalated with client ID CWE2 from the second node (node 2) will not be deleted from the badge.