Epic EHR Integration
Connect an Epic environment with Qvera Interface Engine (QIE) to support healthcare data exchange.
Bring the systems and data flows around your Epic environment together.
How does QIE support Epic integration?
Use QIE to build and operate the connections between Epic and the systems and workflows that matter to your organization.
Epic publishes API and interface specifications through open.epic, but each Epic customer operates an independent instance and determines which applications and connections are authorized. The available path depends on those decisions and the specific workflow.
Which Epic integration paths are available?
The appropriate path depends on the systems, data flows, interface specifications, and authorized access available in your environment.
HL7 interfaces
QIE can receive, transform, route, and deliver the HL7 messages made available for your implementation.
FHIR APIs and open.epic
Where an authorized endpoint and required access are available, QIE can support FHIR and API integration patterns for approved workflows. Epic’s open.epic resources provide specifications and tools that help determine the appropriate customer-level path.
Implementation scope
Confirm the source and target systems, interface specifications, transport and security requirements, testing responsibilities, and ongoing operating model before implementation.
Which Epic data flows can QIE support?
Integration patterns can include the following. The final scope depends on the licensed products, configured interfaces, data model, workflow, and approved access in your environment.
- Patient and encounter updates. Exchange available patient identity, registration, and encounter information with the systems that need it.
- Results exchange. Connect available results transactions between Epic and the connected information systems or repositories that rely on them.
- Clinical documents and reports. Route the documents and reports needed by connected clinical and operational processes where the available interfaces support them.
- FHIR-based data access. Support authorized data-access workflows through available FHIR R4 resources and APIs.
Related Epic case studies: QuadMed: Epic interoperability made easy and The Oregon Clinic: Bi-directional Epic integration alleviates physician burden.
Build, monitor, and maintain Epic interfaces
Build and test
Configure routing, mapping, transformation, and destination behavior for the interfaces your organization needs.
Operate and troubleshoot
Monitor interface activity and queues, investigate errors, and replay or resolve affected messages from one operational platform.
Choose the service approach
Use QIE with your own integration team, or add training, fixed-scope integration work, dedicated engineers, or fully managed integration services. Explore Integration Services for the approach that fits your team.
Continue evaluating QIE: Security and compliance and licensing and pricing.
