Troubleshooting Cross Walk

The information provided in this section helps you understand the scenarios that you must consider to troubleshoot cross walk mapping.

The considerations are as follows:

• Many to many or many to one mappings can lead to Cartesian products which may replicate the data and render the results unusable.
  Note: It is important to configure cross walk mapping correctly in the first instance.
• When ManageSites is configured to a workflow, the cross walk mapping is exported to the Vocera Analytics landing database through the Data Export Adapter. The ManageSites workflow facilitates changes to facility/site and unit/department mappings within the Engage appliance, but these changes are not replicated in the database cross walk tables.

  For example:

  • Unit NICU is mistakenly mapped to department g-cardio using the ManageSites workflow.
  • This mapping is exported to the landing database tables.
  • Unit NICU is then removed from g-cardio using the ManageSites workflow.
    Note: Changes are not made in the database cross walk tables.
  • Unit NICU is then remapped to department g-nicu using the ManageSites workflow.
  • This new mapping is exported to the landing database tables.
  • The system is now erroneously configured with a one-to-many relationship. The unit NICU is mapped in Vocera Analytics to both g-cardio and g-nicu, even though it may appear that the correction was made in the Engage appliance.
• Corrections to the cross walk tables must be made at the database level and cannot be made through the Engage appliance.
• Corrections should be performed by Vocera Technical Support only.

Verifying Cross Walk Configuration

Cross walk configurations should be verified to avoid configuration errors.

Run the following query in the Vocera Analytics database to detect incorrect configuration:

SELECT
  '' || attr_name AS test_description,
  CASE WHEN actual_count = expected_count
       THEN 'PASS'
       ELSE 'FAIL'
  END AS result,
  actual_count AS actual,
  expected_count AS expected
FROM (
  SELECT
    'CWFACILITY' AS attr_name,
    COUNT(*) AS actual_count,
    COUNT(DISTINCT common_facility_name) as expected_count
  FROM vocera_analytics.cwfacility
  UNION ALL
    SELECT
      'CWUNIT' AS attr_name,
      COUNT(*) AS actual_count,
      COUNT(DISTINCT common_unit_name) as expected_count
    FROM vocera_analytics.cwunit
) crosswalk_summary

The following is the result of the above query:

Note that the Result column specifies PASS to indicate that the cross walk table configuration is correct.