Schedule a demo
Segment

Blood product transfusion/disposition

Reports the actual transfusion or final disposition (such as transfused, wasted, or returned unused) of a blood product, including the volume transfused, date and time, and administering individual. It is sent by the clinical or nursing application to the transfusion service or EHR in blood product transfusion and disposition messages. BTX provides the final clinical outcome for each blood product unit.

21fields
5required
v2.9HL7 version
btx.py
from zato.hl7v2 import BTX, CWE

btx = BTX()
btx.bp_quantity = '1'
status = CWE(identifier='COMP', text='Completed')
btx.bp_transfusion_disposition_status = status

Build BTX segments in Python

How to construct and work with real-world BTX segments.

1

Disposition recorded for community allocation

Required quantity, disposition status, message status, and status time

from zato.hl7v2.v2_9 import BTX
from zato.hl7v2.v2_9 import CWE

btx = BTX()
btx.set_id_btx = '1'
btx.bp_quantity = '1'
btx.bp_transfusion_disposition_status = CWE(
    identifier='ALLOC',
    text='Allocated to community program',
)
btx.bp_message_status = 'CO'
btx.bp_date_time_of_status = '20240415120000'
2

Plasma unit with donation traceability and staff

Donation id, component, group, product, timing, administrator, and verifier

from zato.hl7v2.v2_9 import BTX
from zato.hl7v2.v2_9 import CNE, CWE, EI, XCN, XON

btx = BTX()
btx.set_id_btx = '1'
btx.bc_donation_id = EI(
    entity_identifier='DON2024',
    universal_id_type='BBANK',
)
btx.bc_component = CNE(
    identifier='PLAS',
    text='Plasma unit',
)
btx.bc_blood_group = CNE(
    identifier='OPOS',
    text='O Rh positive',
)
btx.cp_commercial_product = CWE(
    identifier='PLASMA01',
    text='Plasma preparation',
)
btx.cp_manufacturer = XON(organization_name='Heartland Plasma',)
btx.cp_lot_number = EI(
    entity_identifier='LOT88',
    universal_id_type='LOT',
)
btx.bp_quantity = '1'
btx.bp_amount = '300'
btx.bp_units = CWE(identifier='ML', text='mL')
btx.bp_transfusion_disposition_status = CWE(
    identifier='COMP',
    text='Completed for wellness event',
)
btx.bp_message_status = 'CO'
btx.bp_date_time_of_status = '20240415123000'
btx.bp_transfusion_administrator = XCN(
    person_identifier='660011',
    family_name='BROOK',
    given_name='CASEY',
    suffix='RN',
)
btx.bp_transfusion_verifier = XCN(
    person_identifier='770022',
    family_name='STONE',
    given_name='RILEY',
    suffix='MD',
)
btx.bp_transfusion_start_date_time_of_status = '20240415120000'
btx.bp_transfusion_end_date_time_of_status = '20240415121500'
3

Documentation with optional follow-up and unique id

Observation categories, pause reason, unique id, and action code

from zato.hl7v2.v2_9 import BTX
from zato.hl7v2.v2_9 import CNE, CWE, EI, XCN, XON

btx = BTX()
btx.set_id_btx = '1'
btx.bc_donation_id = EI(
    entity_identifier='DON2024',
    universal_id_type='BBANK',
)
btx.bc_component = CNE(
    identifier='PLT', text='Platelet unit')
btx.bc_blood_group = CNE(
    identifier='APOS', text='A Rh positive')
btx.cp_commercial_product = CWE(
    identifier='PLT01', text='Platelet preparation')
btx.cp_manufacturer = XON(organization_name='Heartland Plasma',)
btx.cp_lot_number = EI(
    entity_identifier='LOT90',
    universal_id_type='LOT',
)
btx.bp_quantity = '1'
btx.bp_amount = '250'
btx.bp_units = CWE(
    identifier='UNIT', text='Apheresis unit')
btx.bp_transfusion_disposition_status = CWE(
    identifier='DOC', text='Documentation complete')
btx.bp_message_status = 'CO'
btx.bp_date_time_of_status = '20240415124500'
btx.bp_transfusion_administrator = XCN(
    person_identifier='660011',
    family_name='BROOK',
    given_name='CASEY',
    suffix='RN',
)
btx.bp_transfusion_verifier = XCN(
    person_identifier='770022',
    family_name='STONE',
    given_name='RILEY',
    suffix='MD',
)
btx.bp_transfusion_start_date_time_of_status = '20240415120000'
btx.bp_transfusion_end_date_time_of_status = '20240415123000'
btx.bp_adverse_reaction_type = CWE(
    identifier='ROUTINE',
    text='Routine quality documentation'
)
btx.bp_transfusion_interrupted_reason = CWE(
    identifier='SCHED',
    text='Schedule adjustment',
)
btx.bp_unique_id = EI(
    entity_identifier='UID02',
    universal_id_type='WELL',
)
btx.action_code = 'A'

Learn by building

Step-by-step guides for working with HL7 v2 in Zato.

Frequently asked questions

BTX documents quantity, disposition and message status, timing, optional product and donation identifiers, staff involved, and optional follow-up categories for blood bank workflows. It complements BPO and BPX and aligns with ORC, OBR, PID, and PV1.

Fields 1, 8, 11, 12, and 13 are required: set_id_btx, bp_quantity, bp_transfusion_disposition_status, bp_message_status, and bp_date_time_of_status.

from zato.hl7v2.v2_9 import BTX, CWE

btx = BTX()
btx.set_id_btx = '1'
btx.bp_quantity = '1'
btx.bp_transfusion_disposition_status = CWE(
    identifier='COMP', text='Completed')
btx.bp_message_status = 'CO'
btx.bp_date_time_of_status = '20240415120000'

Field 18 may repeat in ER7 using ~ between coded entries. In Python, assign a list of CWE instances to bp_adverse_reaction_type when your interface profile uses this position for supplementary documentation codes.

from zato.hl7v2.v2_9 import BTX, CWE

btx = BTX()
btx.bp_adverse_reaction_type = CWE(
    identifier='ROUTINE',
    text='Routine quality documentation'
)

BPX records dispense-oriented status times, while BTX records disposition milestones and optional start and end times for the same unit in stewardship workflows. Your integration guide should specify which timestamp is authoritative for reporting.

When present, field 19 carries a coded reason for a pause or schedule change using table HL70515. Populate it only when your message profile requires that detail for community allocation or event logistics.

Zato connects to any system that speaks HL7v2 over MLLP or FHIR over REST. This includes Epic, Cerner, Meditech, Allscripts, and other EHR platforms.

Yes, Zato has built-in MLLP support for sending and receiving HL7v2 messages. MLLP channels handle the framing protocol automatically.

Zato supports HL7 v2.9, which is backward compatible with earlier versions including v2.3, v2.5, and v2.7. Standard segments and datatypes are available as typed Python classes.

Yes. Zato handles both HL7v2 and FHIR natively, so you can parse v2 messages and build FHIR resources with IG-specific extensions in the same service. Typed Python classes are available for both protocols, including extensions from US Core, UK Core, Da Vinci, and other Implementation Guides.

BTX field reference

Complete list of fields in the BTX segment, HL7 v2.9.

#Python nameDatatypeUsageRepeatableTable
1set_id_btxSIRequiredNo-
2bc_donation_idEIOptionalNo-
3bc_componentCNEOptionalNoHL70582
4bc_blood_groupCNEOptionalNoHL70583
5cp_commercial_productCWEOptionalNoHL70512
6cp_manufacturerXONOptionalNo-
7cp_lot_numberEIOptionalNo-
8bp_quantityNMRequiredNo-
9bp_amountNMOptionalNo-
10bp_unitsCWEOptionalNoHL70584
11bp_transfusion_disposition_statusCWERequiredNoHL70513
12bp_message_statusIDRequiredNoHL70511
13bp_date_time_of_statusDTMRequiredNo-
14bp_transfusion_administratorXCNOptionalNo-
15bp_transfusion_verifierXCNOptionalNo-
16bp_transfusion_start_date_time_of_statusDTMOptionalNo-
17bp_transfusion_end_date_time_of_statusDTMOptionalNo-
18bp_adverse_reaction_typeCWEOptionalYesHL70514
19bp_transfusion_interrupted_reasonCWEOptionalNoHL70515
20bp_unique_idEIOptionalNo-
21action_codeIDOptionalNo-

Ready to build integrations?

Get started with Zato and connect your systems in minutes.

Open source In Python