Linking Epic With a Variety of Third-party Systems

A health system that has locations throughout a city in the Western United States; and includes a general hospital medical center, a hospital, a rehabilitation center, and over 15 primary care health centers.

Key Challenges

The client was replacing its legacy Invision and eClinicalWorks EHRs with Epic, and it faced the following challenges:

• The choice to retain the behavioral health and Jail health EHRs
• The decision to switch the interface engine from OpenLink to Rhapsody
• The need to retire all existing interfaces and move to the functionalities of Epic

Solution Approach

314e was responsible for building and implementing interfaces in Rhapsody and Epic Bridges between Epic and all the ancillary systems. To manage this effort, the key activities performed by 314e were:

• Discovery of the full scope of interface implementation
• HL7 v2 analysis for each interface
• Rhapsody interface development
• Interface configuration in Bridges
• Interface error work-queue build in Epic
• Training client staff on Epic interfaces
• Cutover planning and migration to production
• Go-live support

314e ensured rigorous interface testing of all Rhapsody and Bridges interfaces at various levels with the third-party vendors and SMEs by using communication testing, primary and full functional testing, mapped record testing, and integrated testing.