- Corepoint Health - https://corepointhealth.com -

Interoperability Success Story: Anne Arundel Medical Center

In this Interoperability [1] Success story featuring Anne Arundel Medical Center (AAMC), we’ll highlight how the organization successfully connected the hospital’s main Epic system to the athenahealth system shared by their 49 separate, affiliated ambulatory physician offices.

Creating a connected health system directly supports AAMC’s strategic plan, titled AAMC’s Vision 2020 [2], which includes building a “System of Care” where the local physician offices, ambulatory healthcare providers, and the community are closely aligned to provide a coordinated and cost-effective approach to improving patient care.

The AAMC Interface Team had to overcome many challenges to build a modern, connected health system, including patient and provider identification and filtering out specific HL7 [3] message types from connected, yet unaffiliated physician groups.  We spoke with Jay Marquez, an Integration Analyst at AAMC.

Request a demo of Corepoint Integration Engine [4]

Some key AAMC facts about this project:


Jay: “In athenahealth messaging to Epic, Corepoint Integration Engine [8] allows us to build a Patient ID Type on the fly by populating the PID-3.5 (Patient ID Type) ​HL7 field with a concatenated string of ‘ATH_’ + [value in MSH-4.3 (Sending Facility ID Type)]. These ID types are created in Epic so that the specific athenahealth Provider Group patient ID can be added to the Epic Master Patient Index (MPI) when either an ADT or scheduling message files.”


Jay:This was resolved in Corepoint Integration Engine by linking Epic provider IDs with athenahealth provider group IDs to create unique provider group-specific provider IDs on messaging from Epic to athenahealth.”


Jay: “Corepoint [8] Integration Engine [8] provides group ID for context in the HL7 messages to athenahealth so the messages map to the appropriate provider records in the athenahealth system for the individual. For the caregivers without an NPI ID, Corepoint allows us to evaluate the provider ID type sent by athenahealth to appropriately handle references to non-credentialed caregivers in messaging to both athenahealth and Epic.”


Jay: “Corepoint Integration Engine allows us to evaluate HL7 field MSH-4.3 (Sending Facility ID Type) and filter out/suppress all unwanted encounter-level HL7 messages such as A04 (Arrival), A08 (Encounter Update), S12 (New Appointment), S14 (Update Appointment), and S15 (Cancel Appointment) for those athenahealth groups that are not live on our hospital’s Epic EMR.”


Additional Reading: Anne Arundel Medical Center Case Study [9]