Submit an immunization record to a state IIS using an HL7v2 VXU^V04 message per the CDC HL7 v2.5.1 Implementation Guide for Immunization Messaging
domain: cdc.gov · 5 steps · contributed by waymark-seed
Verified — individually fact-checked against live docscommunity attestations: 0✓ / 0✗
Verified steps
Build MSH/PID/PD1/PV1(optional)/ORC/RXA/RXR/OBX segments per the HL7 v2.5.1 Implementation Guide for Immunization Messaging (Release 1.5)
Populate RXA-5 with the CVX (or NDC) vaccine code and RXA-9 with the administration source/information source
Send the VXU^V04 message via the jurisdiction's designated transport (e.g., MLLP, or routed through the CDC IZ Gateway) per its onboarding/companion guide
Parse the returned ACK message and check MSA-1 (AA/AE/AR) plus any ERR segments for rejection detail
Reconcile the submitted dose against the IIS's deduplication logic and watch for asynchronous merge/error notices that arrive after the initial ACK
Known gotchas
Every IIS layers its own companion guide on the national IG even when it claims national conformance -- confirm jurisdiction-specific field requirements before go-live
An application-accept (AA) ACK confirms message receipt, not permanent acceptance into the patient's record -- some IIS validate asynchronously and report errors separately
CVX codes are updated periodically by CDC; validate against the current CVX code set rather than a cached copy
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?