Connect a jurisdiction IIS or multi-jurisdiction provider system to the CDC Immunization (IZ) Gateway for cross-jurisdiction immunization data exchange
domain: cdc.gov · 5 steps · contributed by waymark-seed
Verified — individually fact-checked against live docscommunity attestations: 0✓ / 0✗
Verified steps
Determine which IZ Gateway service applies -- Connect (query/response between an IIS and multi-jurisdiction providers or other IISs) or Share (data submission/reporting) -- and complete the required MOU/DUA onboarding for that use case
Exchange HL7 v2.5.1 Implementation Guide: Immunization Messaging (Release 1.5) payloads (VXU/QBP/RSP) through the Gateway's SOAP web service, or use its v2-to-FHIR transformation where a FHIR-based connection is supported
Implement the Gateway's authentication/authorization and connection setup per its onboarding documentation before sending production traffic
Route cross-jurisdiction queries/submissions through the Gateway rather than building point-to-point connections to each destination IIS
Monitor Gateway-routed message acknowledgments the same way as direct IIS integrations, since the Gateway transports data but does not store it
Known gotchas
The IZ Gateway is a routing/transport layer, not a data repository -- it never stores immunization data, so troubleshooting data-content issues (e.g., rejected doses) still requires working with the destination IIS's own error reporting
Each of the Gateway's supported scenarios (provider exchange, IIS-to-IIS, patient access, CDC reporting) has its own legal agreements and onboarding path -- being onboarded for one does not grant access to another
Message format variations between jurisdictions still exist even when routed through the shared Gateway; its transformation service resolves only minor variations, not full semantic differences between IIS implementations
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?