HL7 VXR_V03 (Vaccination Record Response) | Integration Soup HL7 Reference Guide

HL7 VXR_V03 Vaccination Record Response

The older response shape for returning immunization history.

HL7 message structure VXR_V03 groups and segments from HL7 v2.5.1 Hide structure

These are the generated groups and segments for the version selected at the top of the page. The article explains the workflow, and this panel follows the chosen HL7 version.

Message Structure

Segment	Name	Required	Repeatable
MSH	Message Header	Yes	No
MSA	Message Acknowledgment	Yes	No
SFT	Software Segment	No	Yes
QRD	Original-Style Query Definition	Yes	No
QRF	Original style query filter	No	No
PID	Patient Identification	Yes	No
PD1	Patient Additional Demographic	No	No
NK1	Next of Kin / Associated Parties	No	Yes
VXR_V03.PATIENT_VISIT	Patient Visit group	No	No
PV1	Patient Visit	Yes	No
PV2	Patient Visit - Additional Information	No	No
GT1	Guarantor	No	Yes
VXR_V03.INSURANCE	Insurance group	No	Yes
IN1	Insurance	Yes	No
IN2	Insurance Additional Information	No	No
IN3	Insurance Additional Information, Certification	No	No
VXR_V03.ORDER	Order group	No	Yes
ORC	Common Order	Yes	No
VXR_V03.TIMING	Timing group	No	Yes
TQ1	Timing/Quantity	Yes	No
TQ2	Timing/Quantity Relationship	No	Yes
RXA	Pharmacy/Treatment Administration	Yes	No
RXR	Pharmacy/Treatment Route	No	No
VXR_V03.OBSERVATION	Observation group	No	Yes
OBX	Observation/Result	Yes	No
NTE	Notes and Comments	No	Yes

VXR_V03 is a vaccination record response message. It commonly appears as the response side of older VXQ-style immunization query workflows. It can acknowledge the query, identify the matched patient, and return vaccination event groups with ORC, RXA, RXR, and OBX detail.

Like VXQ, this is a legacy-leaning shape in many environments. Modern immunization interfaces often use QBP/RSP patterns under CDC/AIRA-style v2.5.1 guides. Still, VXR shows up in older systems and local reference data, so it is worth knowing how to read it.

A small VXR response example

MSH|^~\&|IIS|STATE|EHR|CITYCLINIC|20260715172100||VXR^V03^VXR_V03|VXR00001|P|2.5.1 MSA|AA|VXQ00001 QRD|20260715172000|R|I|VXQ00001|||1^RD|123456^^^CITYCLINIC^MR|VXI^Vaccine Information^HL70471|T PID|1||123456^^^CITYCLINIC^MR||Smith^Jamie^^^^^L||20190514|F ORC|RE||IMM20250301001^IIS RXA|0|1|20250301100000||140^Influenza, seasonal injectable^CVX|0.5|mL||01^Historical information^NIP001|^Historical^Source RXR|C28161^Intramuscular^NCIT|LA^Left arm^HL70163 OBX|1|CE|30956-7^Vaccine type^LN||140^Influenza, seasonal injectable^CVX||||||F

What systems do with it

The sender is the immunization registry or vaccination record system. The receiver is the querying system. The receiver matches the response to the query through MSA and query identifiers, then imports or displays the returned immunization history according to local rules.

Patient matching remains central. A VXR response may represent a single match, no useful match, or a response constrained by local privacy and matching policies. Do not assume every response can be filed directly into the chart without review or reconciliation.

How to read the structure

The message starts with MSH, MSA, query echo segments, patient identity, and optional visit, guarantor, and insurance context. The order group repeats for vaccination events. ORC groups the event, RXA carries the administered or historical vaccine, RXR carries route/site, and OBX carries additional immunization observations.

Implementation traps

Be careful importing historical doses. Historical records may have weaker provenance than administered records, and guides often distinguish them through RXA and OBX values. If your receiver turns every returned RXA into an administered-in-clinic vaccine, it will distort the patient's chart.

Also keep response matching deterministic. The response should be tied to the outbound query control ID and patient-matching context, not just the first patient identifier that looks familiar.

Reference notes

The local v2.5.1 structure includes VXR_V03 for vaccination record responses. For current implementation choices, compare the receiving registry's guide with CDC IIS HL7 guidance, because modern IIS profiles often use QBP/RSP instead.