HL7 v2.5.1 Specificationsv2.5.1

to moveEnter to openTry PID-5, ADT, 0004

ADR: ADT response

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

Recognising ADR messages

ADR announces itself in MSH-9 like this:

MSH-9ADR^A19^ADR_A19
  1. MSH-9.1ADRmessage code: what kind of message this is
  2. MSH-9.2A19trigger event: what happened in the real world: patient query
  3. MSH-9.3ADR_A19message 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

ADR takes 1 structure.

ADR_A19: Patient Query

Sent when one thing happens: A19: Patient Query.

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

SegmentNameOPTCardinality
MSHR1..1
SFTO0..*
MSAR1..1
ERRO0..1
QAKO0..1
QRDR1..1
QRFO0..1
QUERY_RESPONSEa group of 19 segments, repeated togetherR1..*
EVNO0..1
PIDR1..1
PD1O0..1
ROLO0..*
NK1O0..*
PV1R1..1
PV2O0..1
ROLO0..*
DB1O0..*
OBXO0..*
AL1O0..*
DG1O0..*
DRGO0..1
PROCEDUREa group of 2 segments, repeated togetherO0..*
PR1in PROCEDURER1..1
ROLin PROCEDUREO0..*
GT1O0..*
INSURANCEa group of 4 segments, repeated togetherO0..*
IN1in INSURANCER1..1
IN2in INSURANCEO0..1
IN3in INSURANCEO0..*
ROLin INSURANCEO0..*
ACCO0..1
UB1O0..1
UB2O0..1
DSCO0..1

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 3 such groups: QUERY_RESPONSE, PROCEDURE, INSURANCE.

Trigger events

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

EventNameStructure
A19Patient QueryADR_A19