Immunization registry integration

Qvera brings expertise in connecting to immunization registries across all 50 states.

Tell us about your systems and the connection you need.

Experience connecting to state registries since 2012

Qvera has worked with state immunization registries since 2012, building and supporting registry connections for healthcare organizations from single practices to multi-state health systems. The connections run on Qvera Interface Engine (QIE), and Qvera integration services handle as much of the work as your team wants to hand off: onboarding, registry validation, production troubleshooting, and keeping the exchange working as registry requirements change.

Registries we have connected include ImmTrac (Texas), CAIR (California), MIIC (Minnesota), WAIIS (Washington), I-CARE (Illinois), PA-SIIS (Pennsylvania), WebIZ (Arkansas, Kansas, Nevada), CIIS (Colorado), GRITS (Georgia), Florida SHOTS, MIIS (Massachusetts), NJIIS (New Jersey), WIR (Wisconsin), CHIRP (Indiana), MCIR (Michigan), ASIIS (Arizona), ALERT IIS (Oregon), NYSIIS (New York), ImmuNet (Maryland), ShowMeVax (Missouri), IRIS (Iowa), TennIIS (Tennessee), VacTrAK (Alaska), ImpactSIIS (Ohio), NCIR (North Carolina), KYIR (Kentucky), DelVAX (Delaware), ImmPact (Maine), VaxNH (New Hampshire), USIIS (Utah), and the CDC IZ Gateway.

Which HL7 messages and transports do immunization registries use?

Nearly every registry follows the CDC HL7 2.5.1 Implementation Guide for Immunization Messaging, but each one applies it differently. QIE handles the common building blocks and the local variations:

VXU submissions to report administered and historical immunizations, including the observation segments registries require for VIS dates, vaccine funding source, and eligibility.
QBP queries and RSP responses to retrieve a patient’s immunization history and evaluated forecast, and return it to the connected EHR or application.
Acknowledgment handling for application accepts, errors, and rejects, so a rejected record is surfaced and corrected instead of lost.
Transports the registries actually use: SOAP web services on the CDC WSDL, HTTPS, SFTP batch files, and MLLP sockets, with certificate and credential management for each.
Code tables for CVX, MVX, and NDC, maintained as registries update them.

Expertise throughout the connection lifecycle

Registry requirements and onboarding

Registry-specific message profiles, transport and authentication setup, per-facility credentialing, test submissions, and certification through to production.

Data quality and troubleshooting

Rejected submissions traced to their cause: missing or retired CVX and MVX codes, eligibility and funding-source values, route and site codes, consent flags, and facility identifiers.

Bidirectional exchange

Immunization submissions plus history and forecast queries, returned to the connected application in the form it expects.

Ongoing operations

Patient-matching issues, expired credentials and certificates, registry timeouts, and specification changes handled before they interrupt data flow.

How can you work with Qvera on registry connections?

Three ways, depending on how much your team wants to own:

Run it yourself in QIE. Your team builds and operates the registry channels with Qvera support included in the license.
Have Qvera build and onboard it. Qvera configures the channels, works through registry testing and certification, and hands over a production connection.
Have Qvera host and manage it. Qvera runs the registry platform, monitors every connection, resolves rejections, and adds registries as your footprint grows.

In every model, the agreement to submit to or query a registry is between the registry and your organization. Qvera manages the technical onboarding under that agreement and cannot take its place.

See integration services for the service levels and pricing for how QIE is licensed.

What does a Qvera-managed registry platform look like in practice?

One large healthcare organization was reporting to five state registries and needed to reach registries in states where it has no physical presence. Qvera now hosts and manages its connections to 26 state immunization registries, some direct and some through the CDC IZ Gateway.

QIE receives HL7 feeds from the organization’s Epic environment and from a second occupational-health system, validates and transforms each record, routes it to the right registry, submits it, and returns the registry response to the system that sent it. Qvera onboards each registry, manages the per-state and per-facility credentialing, and works the rejections.

Qvera Interface Engine (QIE) in production today

600+Sites running QIE

25,000+Interfaces in production

50 million+Messages processed daily

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.

Tell us about your integration

Tell us about your EHR or application, the registries you need to connect to, and your intended data exchange.

Discuss your integration

Explore Qvera Interface Engine (QIE) · Explore integration services