HL7 v2.5.1 Specificationsv2.5.1

to moveEnter to openTry PID-5, ADT, 0004

VXU: Unsolicited vaccination record update

This page lists the structures and trigger events VXU defines, taken from the standard. The written commentary that theADT page carries has not been written for VXU.

Recognising VXU messages

VXU announces itself in MSH-9 like this:

MSH-9VXU^V04^VXU_V04
  1. MSH-9.1VXUmessage code: what kind of message this is
  2. MSH-9.2V04trigger event: what happened in the real world: unsolicited vaccination record update
  3. MSH-9.3VXU_V04message structure: which segments to expect, and in what order

How to use these specifications explains MSH-9 in full, with a worked example.

Message structures

VXU takes 1 structure.

VXU_V04: Unsolicited Vaccination Record Update

Sent when one thing happens: V04: Unsolicited Vaccination Record Update.

You must always send: MSH, PID. Everything else is optional, or required only inside a group you chose to send.

SegmentNameOPTCardinality
MSHR1..1
SFTO0..*
PIDR1..1
PD1O0..1
NK1O0..*
PATIENTa group of 2 segments, repeated togetherO0..1
PV1in PATIENTR1..1
PV2in PATIENTO0..1
GT1O0..*
INSURANCEa group of 3 segments, repeated togetherO0..*
IN1in INSURANCER1..1
IN2in INSURANCEO0..1
IN3in INSURANCEO0..1
ORDERa group of 5 segments, repeated togetherO0..*
ORCin ORDERR1..1
TIMINGin ORDERa group of 2 segments, repeated togetherO0..*
TQ1in TIMINGR1..1
TQ2in TIMINGO0..*
RXAin ORDERR1..1
RXRin ORDERO0..1
OBSERVATIONin ORDERa group of 2 segments, repeated togetherO0..*
OBXin OBSERVATIONR1..1
NTEin OBSERVATIONO0..*

R inside a group means required of that group. Send the group and you must include that segment; leave the group out and it never appears. This structure has 5 such groups: PATIENT, INSURANCE, ORDER, TIMING, OBSERVATION.

Trigger events

The trigger event is the real-world thing that made the message get sent. VXU defines 1.

EventNameStructure
V04Unsolicited Vaccination Record UpdateVXU_V04