HL7 v2.5.1 Specificationsv2.5.1

to moveEnter to openTry PID-5, ADT, 0004

OSR: Query response for order status

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

Recognising OSR messages

OSR announces itself in MSH-9 like this:

MSH-9OSR^Q06^OSR_Q06
  1. MSH-9.1OSRmessage code: what kind of message this is
  2. MSH-9.2Q06trigger event: what happened in the real world: query response for order status
  3. MSH-9.3OSR_Q06message 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

OSR takes 1 structure.

OSR_Q06: query response for order status

Sent when one thing happens: Q06: query response for order status.

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

SegmentNameOPTCardinality
MSHR1..1
MSAR1..1
ERRO0..*
SFTO0..*
NTEO0..*
QRDR1..1
QRFO0..1
RESPONSEa group of 2 segments, repeated togetherO0..1
PATIENTin RESPONSEa group of 2 segments, repeated togetherO0..1
PIDin PATIENTR1..1
NTEin PATIENTO0..*
ORDERin RESPONSEa group of 5 segments, repeated togetherR1..*
ORCin ORDERR1..1
TIMINGin ORDERa group of 2 segments, repeated togetherO0..*
TQ1in TIMINGR1..1
TQ2in TIMINGO0..*
CHOICEin ORDERa group of 0 segments, repeated togetherR1..1
NTEin ORDERO0..*
CTIin ORDERO0..*
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 5 such groups: RESPONSE, PATIENT, ORDER, TIMING, CHOICE.

Trigger events

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

EventNameStructure
Q06query response for order statusOSR_Q06