VXU^V04 is the HL7 v2 message used to send vaccination records to immunization information systems, the state and local registries that track vaccines across a population. Clinics, pharmacies, hospitals and EHR vendors depend on it to meet reporting requirements and give providers complete vaccination histories. Rejected or incomplete VXU messages leave gaps in registry records and create compliance problems. This guide explains the VXU structure, RXA fields, a full example and best practices for reliable reporting. It supports our immunization registry integration services. Facing registry rejections? Request a free HL7 interface review.
What VXU^V04 Is Used For
VXU stands for Unsolicited Vaccination Record Update, and the V04 trigger event means a vaccination record is being sent without a query. Providers push records to registries as vaccines are administered or historical records are entered.
Reporting administered vaccines
Every vaccine administered in many jurisdictions should be reported to the immunization information system. VXU carries the patient, vaccine, dose, lot number, manufacturer and administering provider, allowing registries to maintain complete, accurate records across providers and settings. Timely reporting keeps registries current.
Reporting historical immunizations
Providers also report vaccines given elsewhere when patients bring records from other clinics or countries. These historical records are marked differently from newly administered doses, so registries know the reporting provider did not administer them personally. Map historical records carefully to avoid duplicates.
Refusals and contraindications
VXU can record vaccine refusals, contraindications and immunity evidence, depending on jurisdiction requirements. This information helps registries and providers understand why a patient has not received a recommended vaccine and supports appropriate follow-up conversations with patients and families. Confirm local requirements first.
Updates and deletions
When a reported record contains errors, providers send updates or deletions using the RXA action code. Registries apply these changes to the existing record. Accurate correction workflows keep registry data trustworthy for providers relying on it for clinical decisions. Test corrections carefully.
The National Implementation Guide
Most US registries follow the CDC’s HL7 Version 2.5.1 Implementation Guide for Immunization Messaging, plus local requirements. This guide tightens base HL7 rules considerably, specifying required fields, code systems and conformance profiles that senders must meet.
Why the guide matters
Base HL7 leaves many fields optional, but the immunization guide makes many required and specifies vocabularies such as CVX and MVX. Messages that follow base HL7 alone are often rejected by registries that enforce the guide’s stricter conformance rules. Build validation around it.
Message profiles in MSH-21
VXU messages identify the conformance profile they follow in MSH-21, such as the profile for sending immunization updates. Registries use this to apply the correct validation rules. Missing or incorrect profiles can cause rejections even when content is otherwise valid.
Local jurisdiction requirements
Each state or local registry may add requirements beyond the national guide, such as specific identifiers, facility codes or additional observations. Review each jurisdiction’s local implementation guide and onboarding process before connecting, because requirements differ meaningfully. Document differences for each registry.
Onboarding and testing
Registries typically require onboarding steps, including registration, test message validation and production approval. Plan time for these steps. Our public health reporting integration team helps organizations navigate onboarding across jurisdictions efficiently. Approval timelines vary widely between jurisdictions, so start these conversations as early as possible.
VXU^V04 Message Structure
A VXU message contains patient information, optional related persons and insurance, then one or more order groups. Each order group contains ORC, RXA describing the vaccine administration, RXR for route and site, and OBX for supporting observations.
| Segment | Name | Usage | Purpose |
| MSH | Message Header | Required | Sender, receiver, version, profile |
| PID | Patient Identification | Required | Patient identifiers and demographics |
| PD1 | Additional Demographics | Optional | Registry status and publicity |
| NK1 | Next of Kin | Optional, repeating | Parents or guardians |
| PV1 | Patient Visit | Optional | Visit context |
| IN1 | Insurance | Optional | Coverage details |
| ORC | Common Order | Required per order group | Order identifiers |
| TQ1 | Timing/Quantity | Optional | Timing details |
| RXA | Pharmacy/Treatment Administration | Required per order group | Vaccine administration details |
| RXR | Pharmacy/Treatment Route | Optional | Route and site |
| OBX | Observation/Result | Optional, repeating | Eligibility, funding and other observations |
| NTE | Notes and Comments | Optional | Comments |
RXA Segment: Key Fields
RXA carries the core vaccination details. Registries validate it closely, so accurate mapping of these fields is essential. The fields below are those most commonly required under the national immunization implementation guide.
| Seq | Field name | Notes |
| RXA-1 | Give Sub-ID Counter | Usually 0 |
| RXA-2 | Administration Sub-ID Counter | Usually 1 |
| RXA-3 | Date/Time Start of Administration | Date vaccine was given |
| RXA-4 | Date/Time End of Administration | Often same as RXA-3 |
| RXA-5 | Administered Code | Vaccine, usually CVX code |
| RXA-6 | Administered Amount | Dose amount, 999 if unknown |
| RXA-7 | Administered Units | e.g. mL |
| RXA-9 | Administration Notes | New administration or historical record |
| RXA-10 | Administering Provider | Who gave the vaccine |
| RXA-11 | Administered-at Location | Where it was given |
| RXA-15 | Substance Lot Number | Vaccine lot |
| RXA-16 | Substance Expiration Date | Lot expiration |
| RXA-17 | Substance Manufacturer Name | Usually MVX code |
| RXA-18 | Substance/Treatment Refusal Reason | For refusals |
| RXA-20 | Completion Status | e.g. CP complete, RE refused |
| RXA-21 | Action Code | A add, U update, D delete |
Example VXU^V04 Message
The example below shows a newly administered seasonal influenza vaccine, with CVX and MVX codes, lot details, route and site. Data is fictional. Use examples like this to validate parsing and mapping before sending test messages to registries.
MSH|^~\&|EHR|CLINIC|IIS|STATEIIS|20261016110000||VXU^V04^VXU_V04|MSG00004|P|2.5.1|||ER|AL|||||Z22^CDCPHINVS
PID|1||MRN123456^^^HOSP^MR||Doe^Jane^Marie||19850214|F
ORC|RE||IZ7788^CLINIC
RXA|0|1|20261016103000|20261016103000|141^Influenza, seasonal, injectable^CVX|0.5|mL^mL^UCUM||00^New immunization record^NIP001||||||LOT12345|20270630|SKB^GlaxoSmithKline^MVX|||CP|A
RXR|C28161^Intramuscular^NCIT|LD^Left Deltoid^HL70163
Reading the header
MSH shows the EHR sending to the state registry, message type VXU^V04 and version 2.5.1. MSH-15 and MSH-16 set acknowledgment preferences, and MSH-21 identifies the CDC conformance profile the message follows. Registries validate these header values before processing any vaccination content in the message.
Reading the administration
RXA-3 records the administration date, RXA-5 CVX code 141 for seasonal injectable influenza vaccine, RXA-6 and RXA-7 a 0.5 mL dose, and RXA-9 marks a new administration rather than a historical record. Registries validate each of these values carefully against the national guide.
Reading lot, manufacturer and status
RXA-15 and RXA-16 give the lot number and expiration date, RXA-17 the manufacturer using MVX code SKB, RXA-20 a complete status and RXA-21 an add action. RXR records intramuscular route in the left deltoid. Accurate lot data supports recalls. Validate them carefully.
Implementation Best Practices
Registry interfaces succeed when messages conform to national and local guides, use current vocabularies and handle acknowledgments properly. These practices reflect lessons from building immunization interfaces for clinics, health systems and EHR vendors.
Keep vocabularies current
CVX and MVX code sets are updated as new vaccines and manufacturers appear. Outdated codes cause rejections. Assign ownership for monitoring updates and refreshing mappings, especially during seasonal or emergency vaccine rollouts when new products arrive quickly. Test new codes before production use.
Process acknowledgments carefully
Registries return ACK messages that may contain errors or warnings, even when messages are accepted. Review acknowledgment details, not just accept or reject status. Warnings often reveal data quality issues that affect record completeness in the registry. Assign owners for follow-up.
Report eligibility and funding
Many registries require observations describing vaccine funding and patient eligibility, especially for publicly funded vaccine programs. Include these OBX segments when required, and validate values against current guidance to avoid rejections and reporting gaps. Requirements vary by jurisdiction and program.
Support history and forecasts
Beyond sending records, many organizations query registries for patient histories and forecasts. Plan for query and response messages alongside VXU. Our vaccination management software work combines reporting and querying in practical clinical workflows. Forecasts help clinicians identify due or overdue vaccines quickly.
How Taction Helps With Immunization Reporting
Taction has delivered 200+ healthcare projects, including immunization registry, public health and HL7 interfaces. We help clinics, health systems and vendors build VXU interfaces that pass registry validation and keep vaccination records complete.
Free HL7 interface review
Share sample VXU messages, acknowledgments and registry guides. We review conformance, vocabularies, required observations and error handling, then flag risks and fixes. You get clear recommendations. Request your free review. We also flag quick fixes you can apply immediately to reduce registry rejections and warnings.
Registry interface development
We build VXU and query interfaces through integration engines, with conformance validation, vocabulary mapping, acknowledgment processing and monitoring. Our HL7 integration services support reporting across multiple jurisdictions. Each interface is monitored after go-live, so rejected records are caught and corrected quickly before reporting gaps grow.
Multi-jurisdiction onboarding
Organizations serving patients across states face different local requirements. We manage onboarding, testing and production approval with each registry, documenting differences so future changes are faster and production reporting stays reliable. This saves significant time for organizations expanding into new states.
HL7 engineers on demand
Need experienced interface engineers? Hire HL7 integration engineers who understand immunization messaging, public health requirements and engine development. They join your team quickly and document interfaces thoroughly. Engagements scale with your roadmap, from a single registry connection to reporting across many jurisdictions and facilities.
Frequently Asked Questions
These answers cover common questions about HL7 VXU messages. Because registries apply national and local requirements, always confirm details with each jurisdiction’s implementation guide and onboarding team.
What is a VXU^V04 message?
VXU^V04 is the HL7 v2 unsolicited vaccination record update. Providers use it to send administered and historical immunization records to immunization information systems, along with refusals, updates and deletions where jurisdictions support them. Most registry reporting relies on it. Accuracy matters.
What is the RXA segment in VXU?
RXA, the Pharmacy/Treatment Administration segment, carries vaccine details such as administration date, CVX code, dose, lot number, manufacturer, administering provider, completion status and action code. Registries validate it closely against implementation guide rules. Accurate mapping prevents most rejections. Validate every field.
Which implementation guide do registries use?
Most US registries follow the CDC’s HL7 Version 2.5.1 Implementation Guide for Immunization Messaging, plus local jurisdiction requirements. Review both before building interfaces, because local guides often add identifiers, observations or onboarding steps. Requirements differ meaningfully. Plan for both early.
What are CVX and MVX codes?
CVX codes identify vaccines, while MVX codes identify vaccine manufacturers. Both are maintained by the CDC and updated as products change. Using current codes in RXA-5 and RXA-17 is essential for registry acceptance. Monitor updates regularly. Outdated codes cause rejections.
How are VXU errors returned?
Registries return ACK messages indicating acceptance, errors or rejection, often with detailed error segments. Review every acknowledgment, including warnings on accepted messages, because they reveal data quality issues affecting registry completeness. Assign clear owners for every follow-up action. Track trends.