Crosswalk Table Overview

The Crosswalk tables provide a mechanism to crosswalk between Voice Server and Engage Appliance schemas to apply filtering on Dashboards and Reports.

Note: For Vocera Platform 6.1, the sites and departments should already exist for crosswalks. You may not be required to create sites and departments manually.

Reports and Dashboard filters are dependent on the information contained in the cwfacility and cwunit Crosswalk tables. The Crosswalk tables provide a mechanism to crosswalk between Vocera Voice Server (VS) and Engage Appliance schemas and maintain the relationship between Site-Facility and Department-Unit for applying filter criteria on Dashboards and Reports.

Note: If Crosswalk table is not populated correctly, dashboards and reports may show inaccurate data.

Note: Ensure that cwfacility and cwunit tables do not have duplicate entries.

Automatic Updates: For the following configurations, the records for VS only or Vocera Engage Appliance only are updated automatically every day at 12:05 am. Configurations that contain both VS and Engage Appliance require that Site-Facility and Department-Unit be configured utilizing the site management workflow in the Vocera Engage appliance.

Manual Updates: To manually update the crosswalk table, you can use any SQL client tool such as HeidiSQL or MySQL Workbench using the following Call statement:

CALL vocera_analytics.UpdateCrosswalkTable();

The configuration setup that contains both VS and Engage Appliance has the following limitations:

Supports only Site-Facility relationship (One-to-One)
Requires maintenance on every Vocera Engage Appliance
Requires internal Voice Server ID of the department
Supports only case sensitive mapping for Site-Facility and Department-Unit names

Note: Mapping of One-to-Many and Many-to-Many are not supported in this release.

Engage Appliance workflow pages allow you to select from a list of existing sites, or create new sites that can then be associated with Engage Facilities. This will improve the quality of the relationships since it contains known facilities and units.

Currently, the Dashboard and Report UI filters use the common unit name field for displaying departments, that is mapped by default to the Engage facility. Mapping vs_department_name requires the internal name of the Voice Server Department. No placeholder names can exist without this format. Otherwise, dashboard data may display multiple records for each unit.

Note: If your configuration contains both VS and Engage Appliance integration, the Implementation Engineer must explicitly set up the relationship between Site-Facility and Department-Unit on the Vocera Engage Appliance utilizing the available workflow pages.