Resources

Export citation:

Statistics

  • Views: 1031
  • Aggregate Downloads: 108

Information

Share

This article was migrated. An archived version is available here.

Data Reconciliation Engine



Please use this identifier to cite or link to this publication: http://hdl.handle.net/10909/166
Submitted by Matt Mccall on 06-01-2014.
Federal legislation and national programs, including the Affordable Care Act and Meaningful Use, compel health service providers of all sizes – from small clinics to large hospitals – to adopt and integrate electronic health records into their clinical practice.

This migration to digitized health information has highlighted a critical issue: unlike other automated electronic systems in other sectors – like banking, travel, and wireless communications – the walled garden of health data formats has never focused on data (or system level) interoperability. Sending data from one place to another is not as simple as dialing a number, booking a flight, or retrieving cash from any bank's ATM. This is because health data is stored in proprietary formats and in closed systems – think of this as not-quite comprehensible dialects of a common language – and the ability to reliably parse, normalize, and match data between systems is difficult, or even impossible right now.

To address this problem, Amida has built the Data Reconciliation Engine.

The Data Reconciliation Engine (DRE) takes data from a variety of formats and reconciles them into a common data model. The DRE is made up of four components – parsing and normalization, matching and de- duplication, data reconciliation, and master record storage.

The parser and normalization component takes incoming data and maps it into a simplified, homogeneous data model. Then new data is compared to the master health record in order to detect redundant entries and partial matches. Patients can review their records and add or discard partial matches with an intuitive interface. All match types – new, duplicate, and partial – are clearly identified so that an end-user can incorporate and reconcile data as they choose. Master record storage supports the persistence and validation of data to a central repository.

The DRE can be integrated with other health IT solutions. For example, a more robust, third-party user interface can be connected to the DRE through APIs to provide a client-customized look and feel.

The first supported input for the DRE is the CCDA format, which is the content standard recommended by the Blue Button Initiative. The DRE supports all five required sections of the Continuity of Care Document template (allergies, medication, problems, procedures, lab results) and three of the optional sections (encounters, immunizations, and vitals), and is easily extendable to other formats.

Reviews (Phase: Peer)

There is no review at this time.
To submit one, please log in.

Comments

COMMENTS

Powered by Midas