The Qvera Interface Engine (QIE) is a healthcare integration engine from Qvera, which has worked in healthcare interoperability since 2008. It receives, routes and transforms messages between clinical, imaging and administrative systems for hospitals, health systems, imaging centers, and software vendors who embed QIE in their own products.
A single engine covers HL7 v2 and v3, FHIR, DICOM including native DIMSE, X12, NCPDP, ASTM, CDA and IHE profiles, over MLLP, REST, SFTP, file, database, message queue and SMB network share transports. Imaging and clinical interfaces do not need separate tools.
Three capabilities set it apart. DICOM networking is built into the engine itself: store, query, retrieve and modality worklist, with header de-identification, alongside the HL7 and FHIR interfaces. Existing Mirth Connect channels, including their JavaScript, convert into QIE channels from the product menu, with a report of anything worth checking. And high availability, with several QIE nodes sharing one database, is available on every licensing model.
Interfaces are scripted in JavaScript with a built-in Code Wizard, and a built-in AI Companion helps build and troubleshoot them. The datastore is your own choice of MSSQL, MySQL or MariaDB, so there is no proprietary datastore to adopt. The Remote Management Hub monitors and controls QIE instances deployed inside separate customer networks from one console.
Deployment is on-premise, in containers, or in your own cloud. More than 600 sites run QIE in production today, carrying more than 25,000 interfaces and processing more than 50 million messages a day. SOC 2 Type 2 attested.