HL7 v2.5.1 Specificationsv2.5.1

to moveEnter to openTry PID-5, ADT, 0004

BRT: Blood product transfusion/disposition acknowledgement message

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

Recognising BRT messages

BRT announces itself in MSH-9 like this:

MSH-9BRT^O32^BRT_O32
  1. MSH-9.1BRTmessage code: what kind of message this is
  2. MSH-9.2O32trigger event: what happened in the real world: blood product transfusion/disposition acknowledgment
  3. MSH-9.3BRT_O32message 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

BRT takes 1 structure.

BRT_O32: Blood Product Transfusion/Disposition Acknowledgment

Sent when one thing happens: O32: Blood Product Transfusion/Disposition Acknowledgment.

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

SegmentNameOPTCardinality
MSHMessage HeaderR1..1
MSAMessage AcknowledgmentR1..1
ERRErrorO0..*
SFTSoftwareO0..*
NTENotes and Comments (for Response Header)O0..*
RESPONSEa group of 2 segments, repeated togetherO0..1
PIDin RESPONSEPatient IdentificationO0..1
ORDERin RESPONSEa group of 4 segments, repeated togetherO0..*
ORCin ORDERCommon OrderR1..1
TIMINGin ORDERa group of 2 segments, repeated togetherO0..*
TQ1in TIMINGTiming/QuantityR1..1
TQ2in TIMINGTiming/Quantity Order SequenceO0..*
BPOin ORDERBlood Product OrderO0..1
BTXin ORDERBlood Product Transfusion/DispositionO0..*

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 3 such groups: RESPONSE, ORDER, TIMING.

Trigger events

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

EventNameStructure
O32Blood Product Transfusion/Disposition AcknowledgmentBRT_O32