eClinicalWorks EHR Integration

Connect an eClinicalWorks environment with Qvera Interface Engine (QIE) to support healthcare data exchange.

Use QIE to build and operate the connections between eClinicalWorks and the systems and workflows that matter to your organization.

How does QIE support eClinicalWorks integration?

eClinicalWorks documents HL7 interfaces across clinical, practice-management, and public-health workflows, along with FHIR APIs for third-party applications. QIE can receive, transform, route, and send data through the interfaces available in your eClinicalWorks environment.

The right connection path depends on the workflow, the systems involved, the interface specifications, and the access enabled for your organization.

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 eClinicalWorks integration paths are available?

eClinicalWorks documents HL7 interfaces and FHIR APIs for different clinical, operational, and patient-access workflows. Availability and implementation requirements vary by environment.

HL7 interfaces

Use the message types eClinicalWorks documents for the workflow, including ADT, SIU, ORM, ORU, MDM, and MFN where applicable.

FHIR APIs

Connect through provider-facing, backend or bulk, or patient-facing FHIR services when the appropriate eClinicalWorks or healow API access is enabled.

Implementation scope

Confirm the source and target systems, interface specifications, transport and security requirements, testing responsibilities, and ongoing operating model before implementation.

Which eClinicalWorks data flows can QIE support?

Integration patterns can include the following. The final scope depends on the systems, data model, workflow, and interface access in your environment.

Patient demographics, registration, and encounters. Exchange identity, registration, and encounter updates with the systems that need them.
Appointments and scheduling. Connect appointment and scheduling updates with the operational applications that rely on them.
Laboratory and imaging orders and results. Move clinical requests and results between connected systems and workflows.
Clinical documents and reports. Route the reports and documents needed by connected clinical and operational processes.
Provider-directory and MPI workflows. Exchange provider and patient-identity information where the available interfaces support it.
FHIR-based data access. Support patient, provider, or population data access through enabled FHIR services.
Public-health exchange. Connect approved public-health workflows when they are part of the implementation scope.

Build, monitor, and maintain eClinicalWorks interfaces

Build and test

Configure routing, mapping, transformation, and destination behavior for the interfaces your organization needs.

Operate and troubleshoot

Monitor channels 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.

Ready to discuss your eClinicalWorks integration?

Tell us which eClinicalWorks environment, systems, workflows, and interface access you are evaluating. We can help you consider the available connection paths and the QIE deployment and service approach that fits.

Discuss your eClinicalWorks integration

Explore other platforms.