HL7 BTS Messages: Blood Product Transfusion / Disposition Status

HL7 BTS messages communicate the status of blood product transfusions or dispositions. A BTS message is sent from the blood bank information system (BBIS) or laboratory application back to the clinical ordering system (such as an EHR) to report that a blood product (like red blood cells or platelets) has been successfully transfused to the patient, or disposed of (e.g., wasted or returned to inventory). This page explains what a BTS message represents, the trigger event that carries it, every segment the message can contain and what each one holds, and how a BTS message relates to FHIR. Sample content is constructed for illustration with fictional identifiers.

What a BTS message represents

A BTS message — BTS stands for Blood Product Transfusion/Disposition — communicates the clinical outcome of a blood product order. While the BPO segment outlines the requested product type and quantity, the core of the BTS message is the BPX segment, which reports the actual transfusion details: the action performed (transfused, wasted, returned), the unique blood bag barcode identifier, the volume administered, the dates and times of the event, and the practitioners who performed and witnessed the transfusion.

The sender is the blood bank system, bedside transfusion verification application, or LIS, and the receiver is the EHR or patient record repository that maintains the patient's longitudinal history. BTS provides the final loop-closure in the blood supply chain, moving a blood product from "dispensed" to "administered."

When a BTS message is sent

A BTS message is sent immediately after a blood transfusion is completed at the bedside, or when a blood bag is disposed of. Common triggers include:

• A nurse completes the transfusion of a unit of packed red blood cells and scans the bag as transfused.
• A blood bag is returned to the blood bank unused but exceeds the safe temperature window, requiring it to be wasted and recorded as disposed.

Trigger event

The BTS message type carries a single trigger event:

• BTS^O31 – Blood product transfusion/disposition status message.

The receiver updates the clinical chart and inventory records based on the action code in BPX-2 and product ID in BPX-5.

Integration topology

The diagram shows the transfusion verification application or blood bank system sending a transfusion status update through the integration engine to the clinical EHR.

{{diagram: blood bank / bedside app → BTS message → integration engine → clinical system (EHR)}}

Typical senders: bedside transfusion verification system, blood bank information system (BBIS), LIS.

Typical receivers: EHR, clinical documentation system, patient registry.

Direction: unidirectional notification reporting the final administration or disposition status of a blood product.

Segments in an BTS message

The BTS_O31 message is organized into a header block, an optional patient group, and one or more repeating order groups. The BPX segment is required within each repeating group to report transfusion outcomes. Cardinality follows HL7 notation: [X] optional, {X} repeating, [{X}] optional and repeating; a bare code is required. Each segment code links to its canonical field-by-field reference.

[ ] = optional, { } = repeating

Sample BTS message

Note. Constructed for illustration. Blood product codes, unit identifiers, and patient IDs are fictional.

MSH|^~&|BARCODEAPP|MERCY|EHRSYS|MERCY|20260604143000||BTS^O31^BTS_O31|MSG00049|P|2.5.1
PID|1||MR98765^^^MERCY^MR||SMITH^PATRICIA^A||19720315|F
PV1|1|I|3N^301^A^MERCY
ORC|RE|REQ20260604-004^EHRSYS|FIL20260604-004^BLOODSYS
BPX|1|TX^Transfused^HL70511|PC^Packed Cells^L|20260604140000|UNIT-A9918231|||1^Unit||OP100^DOE^JOHN^RN|WIT99^SMITH^SARAH^RN|G^Good^HL70512
NTE|1||Transfusion completed over 2 hours. No immediate reaction noted.

What this sample shows

The BTS^O31 in MSH-9 identifies the message as a transfusion status update. PID identifies patient MR98765 and PV1 places her in bed 3N-301-A. ORC carries order control code RE (Refilled/Released) to update the status of placer order REQ20260604-004. The BPX segment reports the outcome: action code TX (Transfused) in BPX-2, product type Packed Cells in BPX-3, transfusion time 20260604140000 in BPX-4, unit barcode UNIT-A9918231 in BPX-5, volume of 1 unit in BPX-8, transfusion operator OP100 in BPX-10, witness WIT99 in BPX-11, and status code G (Good) in BPX-12. The NTE adds free-text details about the transfusion duration.

Working with BTS messages

Reconcile Blood Bag Barcodes

BPX-5 carries the unique blood bag number (often using ISBT-128 barcode format). Receiving systems must match this identifier against the inventory records of dispensed products to ensure the correct unit is marked as transfused, supporting strict hemovigilance audits.

Monitor Transfusion Status and Actions

The action code in BPX-2 determines the clinical and inventory outcome. Action code TX (Transfused) records the successful clinical event, while code DI (Disposed) indicates waste. Waste reasons (like contamination, clotting, or temperature violations) should be parsed from BPX-12 (Transfusion Status) to support blood bank quality control metrics.

Vendor variance. Bedside verification systems differ in how they report vital signs. Some systems include pre- and post-transfusion vitals as nested OBX segments within the BTS message, while others transmit vital signs separately via standard ORU^R01 messages. Check your bedside software specification to configure vitals routing correctly.

FHIR equivalent

A blood product transfusion status maps conceptually to the FHIR Procedure resource with category set to transfusion, or a BiologicallyDerivedProduct administration record.

The HL7 v2-to-FHIR Implementation Guide publishes no message map for BTS_O31 and no ConceptMap for the BPX segment. Therefore, any FHIR translation must be mapped manually, generating a Procedure resource with status completed (or stopped if the transfusion was aborted due to a reaction), linking it to the Patient from PID and Encounter from PV1, and adding the blood product barcode from BPX-5 as a device reference or part of the procedure's usedCode.

Common pitfalls

Pitfall. Flattening the message and dropping the witness ID in BPX-11. Clinical compliance regulations require double-signing for blood transfusions. Failing to capture the witness operator code from BPX-11 will result in incomplete audit trails for clinical compliance.

Pitfall. Failing to distinguish between Transfused (TX) and Disposed (DI) actions. Treating all BTS messages as successful transfusions will lead to incorrect patient charts, showing wasted units as administered to the patient.

How Vorro handles BTS messages

Vorro ingests BTS messages over MLLP, validates the transfusion action in BPX, and correlates the transfusion line item to its order through the placer order number in ORC. Vorro routes the bedside outcomes to the clinical chart and updates inventory records. Where a FHIR destination is configured, Vorro maps the event to a FHIR Procedure resource manually, since the HL7 v2-to-FHIR guide provides no published map for this message.

Related messages

• OMB — the blood product order message.
• ORB — the blood product order response.
• BPS — the blood product dispense status message.

Sources

• HL7 v2-to-FHIR IG — message maps index
• HL7 Messaging Standard Version 2.5.1 product brief