Platforms and systems Qvera connects

Use Qvera Interface Engine (QIE) and Qvera DICOM Router (QDR) to connect healthcare systems and imaging workflows. Explore platform-specific integration options and examples of the systems Qvera connects.

Explore integration options for your platform

Epic

Build and operate connections using the HL7 interfaces and FHIR APIs available and authorized in your Epic environment.

Altera Digital Health (formerly Allscripts)

Connect TouchWorks EHR with the systems around it using QIE to build, transform, and monitor interfaces.

athenahealth and athenaOne

Exchange HL7 data, transform messages, monitor interfaces, and resolve errors across your athenaOne integration workflows.

Cerner / Oracle Health

Connect your Cerner environment through available HL7 interfaces, FHIR resources, and EHR APIs.

eClinicalWorks

Connect clinical, practice-management, and public-health workflows through the HL7 interfaces and FHIR APIs available in your environment.

MEDITECH

Support HL7 data exchange, FHIR patient access, and scheduling workflows through the interfaces available in your MEDITECH environment.

PointClickCare

Transform, route, and monitor PointClickCare data through the API connection path enabled for your organization.

The available connection depends on the platform, workflow, interface specifications, and authorized access in your environment.

More systems QIE connects

These examples illustrate the range of systems QIE connects and are not an exhaustive list.

 
AdvancedMD
NextGen Healthcare
Qualifacts CareLogic
RLDatix
Greenway Health
TruBridge

Imaging systems

QIE and Qvera DICOM Router (QDR) connect imaging systems, including PACS and VNAs. Examples include Intelerad, Sectra, and RamSoft Gateway DICOM Router.

 
GE HealthCare
Change Healthcare
Philips
Fujifilm
IBM
Agfa HealthCare
Novarad
Sectra
Carestream
Infinitt
Intelerad
Siemens Healthineers
Canon
Bayer in Radiology
Hologic
Konica Minolta
Mindray
RamSoft

Immunization registries

QIE connects EHRs and practice systems to state immunization information systems (IIS) in all 50 states: VXU submissions, QBP and RSP history and forecast queries, and the transport each registry requires, including the CDC IZ Gateway. Qvera has worked with state registries since 2012 and can build the connection, onboard it with the registry, or host and manage it for you.

Where QIE runs

QIE can run on-premise, in containers, or in your own AWS, Azure, or Google Cloud environment.

Explore Qvera Interface Engine

What do you need to connect?

Tell us which systems you use and what data needs to move between them.

Need help building, supporting, or managing your interfaces? Explore Qvera Integration Services.

Security and compliance · Pricing

© Copyright 2026 - Qvera - All rights reserved  |  Privacy Policy