visit the hl7 website The Demo site for our new HL7 Version 2+ (plus) Standard

18.4.113 ORG - general clinical order acknowledgement message (event O20) (4.4.5)

The function of this message is to respond to an OMG message. An ORG message is the application acknowledgment to an OMG message. See Chapter 2 for a description of the acknowledgment paradigm.

In ORG the PID and ORC segments are optional, particularly in case of an error response. However, ORC segments are always required in ORG when the OBR is present. For example, a response ORG might include only the MSH and MSA.

The function (e.g., cancel, new order) of both OMG and ORG messages is determined by the value in ORC-1-order control. (See the table of order control values for a complete list.)

Segment Cardinality Implement Status
ORG^O20^ORG_O20
MSH

Message Header

[1..1] SHALL
MSA

Message Acknowledgment

[1..1] SHALL
ERR

Error

 
SFT

Software Segment

 
UAC

User Authentication Credential Segment

[0..1]  
NTE

Notes and Comments

 
RESPONSE [0..1]  
PATIENT [0..1]  
PID

Patient Identification

[1..1] SHALL
NTE

Notes and Comments

 
PRT

Participation Information

 
ARV

Access Restriction

  B
ORDER [1..*] SHALL
ORC

Common Order

[1..1] SHALL
PRT

Participation Information

 
TIMING  
TQ1

Timing/Quantity

[1..1] SHALL
TQ2

Timing/Quantity Relationship

 
OBSERVATION_GROUP [0..1]  
OBR

Observation Request

[1..1] SHALL
PRT

Participation Information

 
NTE

Notes and Comments

 
CTI

Clinical Trial Identification

 
SPECIMEN  
SPM

Specimen

[1..1] SHALL
SAC

Specimen Container detail

 

 

ORG_O20

MSH-15 MSH-16 Immediate ACK Application Ack
Blank Blank ACK^O20^ACK -
NE NE - -
AL, ER, SU NE ACK^O20^ACK -
We need some ER7 examples...
We need some XML examples...

There is not supposed to be an Application Level acknowledgement to an Application Level Acknowledgement message. In Enhanced Mode, MSH-16 SHALL always be set to NE (Never).