HL7 v2.5.1 Specificationsv2.5.1

to moveEnter to openTry PID-5, ADT, 0004

SRR: Scheduled request response

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

Recognising SRR messages

SRR announces itself in MSH-9 like this:

MSH-9SRR^S01^SRR_S01
  1. MSH-9.1SRRmessage code: what kind of message this is
  2. MSH-9.2S01trigger event: what happened in the real world
  3. MSH-9.3SRR_S01message 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

SRR takes 1 structure.

SRR_S01

No trigger event in the standard names this structure.

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

SegmentNameOPTCardinality
MSHR1..1
MSAR1..1
ERRO0..*
SCHEDULEa group of 5 segments, repeated togetherO0..1
SCHin SCHEDULER1..1
TQ1in SCHEDULEO0..*
NTEin SCHEDULEO0..*
PATIENTin SCHEDULEa group of 4 segments, repeated togetherO0..*
PIDin PATIENTR1..1
PV1in PATIENTO0..1
PV2in PATIENTO0..1
DG1in PATIENTO0..*
RESOURCESin SCHEDULEa group of 5 segments, repeated togetherR1..*
RGSin RESOURCESR1..1
SERVICEin RESOURCESa group of 2 segments, repeated togetherO0..*
AISin SERVICER1..1
NTEin SERVICEO0..*
GENERAL_RESOURCEin RESOURCESa group of 2 segments, repeated togetherO0..*
AIGin GENERAL_RESOURCER1..1
NTEin GENERAL_RESOURCEO0..*
LOCATION_RESOURCEin RESOURCESa group of 2 segments, repeated togetherO0..*
AILin LOCATION_RESOURCER1..1
NTEin LOCATION_RESOURCEO0..*
PERSONNEL_RESOURCEin RESOURCESa group of 2 segments, repeated togetherO0..*
AIPin PERSONNEL_RESOURCER1..1
NTEin PERSONNEL_RESOURCEO0..*

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 7 such groups: SCHEDULE, PATIENT, RESOURCES, SERVICE, GENERAL_RESOURCE, LOCATION_RESOURCE, PERSONNEL_RESOURCE.

Trigger events

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

EventNameStructure