Record Validation

Overview

When Particle queries for a patient's clinical records via the HIEs, Particle is reliant on the patient matching algorithm that exists between the networks and the providers' EMR systems to pull those clinical records. This matching algorithm from the providers' EMR will return the data it believes it has for that specific patients. In some [small] instances, incorrect clinical records may be returned i.e. Particle queried for John Smith and received records are for Jane Jones.

What does Record Validation do?

To minimize [even the low] likelihood of Particle's customers receiving incorrect patient records from the EMRs, Particle built out Record Validation. Record Validation is Particle's logic that evaluates whether the queried patient data matches the received patient data.

How does it work?

Particle compares the patient demographics provided by the customer at the time of query against the patient demographics included in the CCDA documents received from the EMRs via the networks. We evaluate and compare using all available demographic values, including: first name, last name, DOB, gender, city, state, zip, telephone, email, and ssn.

In the event that Particle evaluates the records do not match, Particle removes the mismatched files from further processing by Particle and does not deliver them to the customer. This record validation applies to all customer data workflows, CCDA, FHIR, and Flat.

This implemented logic is sound but even so Particle cannot ensure that this logic will be accurate in all instances as some small fraction of mismatched patient files could still make their way to the customer. In the event that this occurs, Particle is committed to working with customers to further hone the Record Validation logic to account for edge cases.

Who is it for?

This free feature is available to all Particle customers!