Qvera Information

Qvera has built healthcare integration software since 2008. Our flagship Qvera Interface Engine (QIE) connects clinical, imaging and administrative systems for hospitals, health systems, imaging centers, ambulatory and specialty practices, and healthcare software vendors. Qvera DICOM Router (QDR) does the same job for imaging: DICOM routing, PACS and VNA connectivity, and a bridge from legacy DIMSE to the cloud. One engine handles HL7 v2 and v3, FHIR, DICOM including native DIMSE, X12, NCPDP, ASTM, CDA and IHE profiles, so imaging and clinical interfaces run on the same platform instead of separate tools. Transports include MLLP, REST, SFTP, file, database, message queue and SMB network share. Three things set QIE apart: DICOM networking (store, query, retrieve and worklist) and header de-identification in the same engine as your HL7 and FHIR interfaces, a built-in converter for Mirth Connect channels, and high availability on every licensing model. Interfaces are scripted in JavaScript, and the built-in AI Companion helps your team build and troubleshoot them. The Remote Management Hub manages QIE sites on separate networks from one console; each site connects outward, so there is no VPN into every network. QIE runs on MSSQL, MySQL or MariaDB. Deploy on-premise, in containers, or in your own cloud. We sell directly to healthcare organizations and license QIE to software vendors who embed it in their own products. 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. Individual deployments range from a single clinic to more than 10 million messages a day in a single QIE instance. Customers consistently rate our support highly, citing fast response times and issues resolved first time, with 24/7 coverage for system-down emergencies. Qvera is SOC 2 Type 2 attested.