HL7 v2.5.1 Specificationsv2.5.1

to moveEnter to openTry PID-5, ADT, 0004

BRP: Blood product dispense status acknowledgement message

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

Recognising BRP messages

BRP announces itself in MSH-9 like this:

MSH-9BRP^O30^BRP_O30
  1. MSH-9.1BRPmessage code: what kind of message this is
  2. MSH-9.2O30trigger event: what happened in the real world: blood product dispense status acknowledgment
  3. MSH-9.3BRP_O30message 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

BRP takes 1 structure.

BRP_O30: Blood Product Dispense Status Acknowledgment

Sent when one thing happens: O30: Blood Product Dispense Status 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 1 segments, repeated togetherO0..1
PATIENTin RESPONSEa group of 2 segments, repeated togetherO0..1
PIDin PATIENTPatient IdentificationR1..1
ORDERin PATIENTa 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
BPXin ORDERBlood Product dispense statusO0..*

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

Trigger events

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

EventNameStructure
O30Blood Product Dispense Status AcknowledgmentBRP_O30