Cerner EHR Integration
Connect a Cerner environment with Qvera Interface Engine (QIE) to support healthcare data exchange.
Bring the systems and data flows around your Cerner environment together.
How does QIE support Cerner HL7 integration?
Use QIE to build and operate the connections between Cerner and the systems and workflows that matter to your organization.
Cerner is now part of Oracle Health. Oracle uses both Oracle Health Millennium Platform and Oracle Health EHR, formerly Cerner Millennium, in different contexts. This page retains Cerner as the familiar platform term; it does not imply support for every Oracle Health product or connection path.
For Cerner HL7 integration, QIE can receive HL7 messages on an MLLP socket, optionally secured with TLS, and send HL7 messages to other systems over MLLP.
QIE is in production today at more than 600 sites, running more than 25,000 interfaces and processing more than 50 million messages a day.
Which Cerner 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 R4 and EHR APIs
Where an authorized endpoint and required access are available, QIE can support FHIR and API integration patterns for the approved workflow.
Implementation scope
Confirm the source and target systems, interface specifications, transport and security requirements, testing responsibilities, and ongoing operating model before implementation.
Oracle publishes FHIR R4 APIs for the Millennium platform, secured with SMART authorization, and no longer supports its older DSTU 2 version. The FHIR web address differs for each customer environment, which Oracle calls a tenant, and the tenant identifier comes from that customer. For server to server work, some Oracle APIs accept a system account that signs in with a key and secret or with a signed JSON Web Token. QIE web service connections support both: OAuth2 with Credentials, which can send the key and secret in a Basic header, and OAuth2 with JWT. Oracle also supports FHIR bulk data export for Millennium through its Group Export and Patient Export operations, and QIE can run those exports.
Which Cerner 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 Cerner 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.
Build, monitor, and maintain Cerner 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.
