HL7 v2.5.1 Specificationsv2.5.1

to moveEnter to openTry PID-5, ADT, 0004

BTS: Blood product transfusion/disposition message

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

Recognising BTS messages

BTS announces itself in MSH-9 like this:

MSH-9BTS^O31^BTS_O31
  1. MSH-9.1BTSmessage code: what kind of message this is
  2. MSH-9.2O31trigger event: what happened in the real world: blood product transfusion/disposition message
  3. MSH-9.3BTS_O31message 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

BTS takes 1 structure.

BTS_O31: Blood Product Transfusion/Disposition Message

Sent when one thing happens: O31: Blood Product Transfusion/Disposition Message.

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

SegmentNameOPTCardinality
MSHR1..1
SFTO0..*
NTEO0..*
PATIENTa group of 4 segments, repeated togetherO0..1
PIDin PATIENTR1..1
PD1in PATIENTO0..1
NTEin PATIENTO0..*
PATIENT_VISITin PATIENTa group of 2 segments, repeated togetherO0..1
PV1in PATIENT_VISITR1..1
PV2in PATIENT_VISITO0..1
ORDERa group of 5 segments, repeated togetherR1..*
ORCR1..1
TIMINGa group of 2 segments, repeated togetherO0..*
TQ1in TIMINGR1..1
TQ2in TIMINGO0..*
BPOR1..1
NTEO0..*
PRODUCT_STATUSa group of 2 segments, repeated togetherO0..*
BTXin PRODUCT_STATUSR1..1
NTEin PRODUCT_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 5 such groups: PATIENT, PATIENT_VISIT, ORDER, TIMING, PRODUCT_STATUS.

Trigger events

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

EventNameStructure
O31Blood Product Transfusion/Disposition MessageBTS_O31