HL7 v2.5.1 Specificationsv2.5.1

to moveEnter to openTry PID-5, ADT, 0004

RDY: Display based response

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

Recognising RDY messages

RDY announces itself in MSH-9 like this:

MSH-9RDY^K15^RDY_K15
  1. MSH-9.1RDYmessage code: what kind of message this is
  2. MSH-9.2K15trigger event: what happened in the real world
  3. MSH-9.3RDY_K15message 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

RDY takes 1 structure.

RDY_K15

2 different trigger events send this structure:

The segments below are the same for all 2. HL7 varies the meaning, not the shape: there is no separate RDY_Z98 layout. What changes is MSH-9, which tells the receiver which of the 2 happened and therefore what to do with the message.

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

SegmentNameOPTCardinality
MSHR1..1
SFTO0..*
MSAR1..1
ERRO0..1
QAKR1..1
QPDR1..1
DSPO0..*
DSCO0..1

Trigger events

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

EventNameStructure
K15K15RDY_K15
Z98Z98RDY_K15