Purpose

This document explains how to identify and correct a census discrepancy when a patient in the Broker is showing an incorrect location.

What is a Census Discrepancy?

A census discrepancy is any mismatch, inconsistency, or missing element between:

  • Enumerated HL7 messages
  • Prior records
  • Authoritative registries

Discrepancies can occur due to:

  • HL7 message mismatches
  • Broker and Performance/Raven DB mismatches 



Broker Patient Has Incorrect Location

This issue occurs when a patient’s visit is available in the Broker, but the location shown is incorrect compared to the latest HL7/census information.



Steps to Investigate the Issue

Step 1: Log in to the Server

  • Log in to the relevant server.
  • Check the census feed.
  • Verify whether the patient visit is available in the most recent census feed.

Step 2: Check HL7 History

  • Review the HL7 History for the affected patient visit.
  • Look for the most recent transfer message (A02).
  • Confirm whether the transfer message contains the correct patient location.

Resolution

If the patient's location in the Broker is incorrect:

  • Identify the latest A02 (Transfer) HL7 message in the HL7 History.
  • Reprocess the latest A02 HL7 message.
  • This should update the patient’s location in the Broker and correct the discrepancy.

Expected Outcome

After reprocessing the latest A02 HL7 message:

  • The patient’s location in the Broker should be updated correctly.
  • The discrepancy between the Broker and the latest HL7/census data should be resolved.

Important Note

Before reprocessing the message, always confirm:

  • The patient visit exists in the latest census feed
  • The latest A02 transfer message is the correct and most recent location update
  • No newer HL7 message overrides the transfer information