HL7 v2.5.1 Specificationsv2.5.1

to moveEnter to openTry PID-5, ADT, 0004

ORF: Query for results of observation

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

Recognising ORF messages

ORF announces itself in MSH-9 like this:

MSH-9ORF^R04^ORF_R04
  1. MSH-9.1ORFmessage code: what kind of message this is
  2. MSH-9.2R04trigger event: what happened in the real world
  3. MSH-9.3ORF_R04message 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

ORF takes 1 structure.

ORF_R04

Sent when one thing happens: R04: R04.

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

SegmentNameOPTCardinality
MSHR1..1
SFTO0..*
MSAR1..1
QRDR1..1
QRFO0..1
QUERY_RESPONSEa group of 2 segments, repeated togetherR1..*
PATIENTa group of 2 segments, repeated togetherO0..1
PIDin PATIENTR1..1
NTEin PATIENTO0..*
ORDERa group of 7 segments, repeated togetherR1..*
ORCO0..1
OBRR1..1
NTEO0..*
TIMING_QTYa group of 2 segments, repeated togetherO0..*
TQ1in TIMING_QTYR1..1
TQ2in TIMING_QTYO0..*
CTDO0..1
OBSERVATIONa group of 2 segments, repeated togetherR1..*
OBXO0..1
NTEO0..*
CTIO0..*
ERRO0..*
QAKO0..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 5 such groups: QUERY_RESPONSE, PATIENT, ORDER, TIMING_QTY, OBSERVATION.

Trigger events

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

EventNameStructure
R04R04ORF_R04