Anne Arundel Medical Center Case Study
www.aahs.org Annapolis, MD
“Corepoint Health’s positive impact on our migration to EPIC was huge.”
Anne Arundel Medical Center, part of Anne Arundel Health System, provides inpatient and outpatient care to the residents of Anne Arundel County, Calvert and Prince George’s counties, the Eastern Shore of Maryland and nearby Washington, D.C., and Baltimore. The medical center employs a workforce of more than 3,400, and has a medical staff of more than 750 members who provide world-class acute inpatient and outpatient care.
Healthcare Interfacing Challenges
Anne Arundel Medical Center’s mission is to enhance the health of the people they serve. To build upon their tradition of excellence, they wanted to establish a better clinical data exchange environment with community physicians and patients. As a result, they decided to migrate to Epic’s hospital information system (Hospital Information System (HIS) is the main system in a hospital used by most caregivers. Sends ADT broadcasts to all ancillary applications. The HIS is typically the patient administrative system and order entry system for a hospital. Synonyms: Ho... More) to better facilitate a connected community of care.
An enterprise-wide, multi-year, two-phased plan was developed that initially included creating over 70 connections. “We had an extremely large number of point-to-point HL7 is a Standards Developing Organization accredited by the American National Standards Institute (ANSI) to author consensus-based standards representing a board view from healthcare system stakeholders. HL7 has compiled a collection of message form... More interfaces that needed to be rewritten as we migrated to Epic,” said Systems Analyst, Ramona Skinner. “The legacy process of developing those interfaces required individual programming and was extremely labor intensive. Considering the magnitude of the migration we were about to undertake, we simply did not have the staff on hand to dedicate to rewriting and customizing each interface connection. We also needed the ability to replicate interfaces feeds to provide data for testing new systems.”
To efficiently implement a higher capacity HIS and establish greater integration with physician offices, a flexible and user-friendly interface engine was needed.
With its ease of use, high performance, industry ratings and customer referrals, Corepoint Integration Engine was selected to help facilitate the migration to Epic’s HIS and establish their goal of greater physician office integration. Corepoint Integration Engine’s role was to connect legacy and other systems while supporting key processes such as registration and transcription.
Some key interfaces Anne Arundel Medical Center uses Corepoint Integration Engine for include:
- Epic (HIS, Radiant Radiology, Willow Pharmacy Module, Cadence Scheduling, OpTime, Lab Orders)
- MEDITECH ADT to Epic
- Epic demographic data to MEDITECH
- Physician office demographic and scheduling to Epic
- Create MEDITECH Pre-registration from Epic ASAP and OpTime triggers
- Transcription reports to Epic
- Epic Lab orders to MEDITECH Lab
- MEDITECH Lab Status Updates and Results to Epic
- Epic billing to Physician office system
- Epic billing to MEDITECH BAR
- MEDITECH MM Item dictionary edits to Epic
- Epic surgery depletions to MEDITECH MM
- Epic Pharmacy orders to Dispensing system
- Dispensing system issues to Epic
- Device and fetal monitoring data sent to Epic through engine
- Reference Lab interfaces
- Epic Radiant integration with Picture Archiving Communication Systems (PACS) are devoted to the storage, retrieval, distribution, and presentation of images. The medical images are stored in an independent format, most commonly DICOM. Synonyms: Picture Archiving Communication Sys... More system
Anne Arundel Medical Center Insights
Evaluating Interface Engines
After an evaluation process that included two demonstrations and customer referrals conversations with four vendors, Corepoint Integration Engine was selected to help facilitate their migration to Epic.
“Ultimately, we preferred Corepoint Health the most – it was very user friendly with a nice user interface, plus there was no programming language to have to learn.” With such a daunting task ahead of them, it was absolutely critical to work quickly and efficiently. A conclusion was reached that selecting the other vendors would have meant longer, more tedious interface development. “Upon giving our recommendation to our CIO, Doug Abel, in favor of Corepoint Health, he referred to the KLAS® survey report, which helped to confirm our selection showing high marks with regards to ease of use and overall customer satisfaction.”
“Our team took the 3-day online training workshop which gave us a great foundation to build upon. We also purchased a bulk of consulting hours ‘just in case’ we needed assistance. Our overall migration project to Epic has two phases. Phase one included integrating several of our physician offices with the Athena Physician system. Phase two was to bring up our inpatient hospital and clinical systems on Epic. Included in these initiatives was an ambitions migration plan to go live with an estimated 70 connections. We met that goal. In fact, after 18 months we are live with 74 connections. To accomplish that in a year and a half, to me, is amazing. We’re ecstatic with the way in which we can create and manage our interface environment.”
“Corepoint Health’s positive impact on our migration to EPIC was huge. Creating interfaces is so much simpler with Corepoint Integration Engine. Our previous ADT interfaces required a separate purchase and custom programming for each individual interface. With Corepoint Integration Engine, it was simple and efficient to replicate a master interface and subtly modify each one as needed. We were able to save a substantial amount of money by leveraging the ability of Corepoint Integration Engine to replicate feeds. It’s hard to quantify how much time we saved, but looking back, we simply could not have accomplished what we did so quickly and efficiently without Corepoint Integration Engine.”
“We are going to implement the Corepoint Health high-availability solution, A2, soon. The integration engine is so critical to the overall function of our environment that we decided having backup capability that is native to Corepoint Integration Engine was the direction we needed to go.”
The Corepoint Health Difference
“One task that could have been far more difficult was moving historical ADT data into Epic. We were able to take over a million records in files and load them into the interface engine in small batches, where the Corepoint Integration Engine was able to convert them into HL7 ADT messages. It might seem like a small thing, but Corepoint Integration Engine is filled with tools and features that show just how much they understand interfacing from the hospital’s perspective.Corepoint Health’s customer support is fabulous. If I get stuck, I don’t have hours to spend figuring something out… I know I make a call and get things resolved in a few minutes. That kind of peace of mind is just wonderful.”