HL7 BTX Blood Product Transfusion/Disposition
HL7 field reference BTX fields from HL7 v2.5.1 Show fields
These are the generated fields for the version selected at the top of the page. The document stays the same, but the reference panel follows that version.
Fields
| Field | Name | Required | Repeatable | Type | Table |
|---|---|---|---|---|---|
| BTX.1 | Set ID - BTX | Yes | No | SI | |
| BTX.2 | BC Donation ID | No | No | EI | |
| BTX.3 | BC Component | No | No | CNE | |
| BTX.4 | BC Blood Group | No | No | CNE | |
| BTX.5 | CP Commercial Product | No | No | CWE | 0512 |
| BTX.6 | CP Manufacturer | No | No | XON | |
| BTX.7 | CP Lot Number | No | No | EI | |
| BTX.8 | BP Quantity | Yes | No | NM | |
| BTX.9 | BP Amount | No | No | NM | |
| BTX.10 | BP Units | No | No | CE | |
| BTX.11 | BP Transfusion/Disposition Status | Yes | No | CWE | 0513 |
| BTX.12 | BP Message Status | Yes | No | ID | 0511 |
| BTX.13 | BP Date/Time of Status | Yes | No | TS | |
| BTX.14 | BP Administrator | No | No | XCN | |
| BTX.15 | BP Verifier | No | No | XCN | |
| BTX.16 | BP Transfusion Start Date/Time of Status | No | No | TS | |
| BTX.17 | BP Transfusion End Date/Time of Status | No | No | TS | |
| BTX.18 | BP Adverse Reaction Type | No | Yes | CWE | 0514 |
| BTX.19 | BP Transfusion Interrupted Reason | No | No | CWE | 0515 |
BTX records the transfusion or disposition of a blood product, including what happened to a unit and when.
Blood product segments are about tightly controlled inventory and patient-safety workflow. The same unit may be ordered, prepared, dispensed, transfused, returned, wasted, or otherwise dispositioned.
Keep product identifiers, unit numbers, status, timing, and responsible staff precise. A receiver should never have to guess whether a field describes the requested product, the issued product, or what actually happened to it.
The v2.5.1 structures show BTX in BRT_O32 - BRT - Blood product transfusion/disposition acknowledgment and BTS_O31 - BTS - Blood product transfusion/disposition. That tells you where it can appear, but the implementation guide still decides which optional fields are meaningful.
For practical interface work, read the generated field panel for datatype, required, repeatable, and table details, then use the notes below to decide what the field should mean in the receiving workflow.
BTX-1 is the sequence number for this BTX segment within its repeating group. It keeps multiple BTX lines in order; it is not the business identifier for the blood product workflow.
BTX-2 identifies the BC Donation ID for this blood product workflow. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
BTX-3 carries BC Component for this blood product workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
BTX-4 carries BC Blood Group for this blood product workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
BTX-5 carries CP Commercial Product for this blood product workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
The generated panel links this to HL7 table 0512; many real interfaces narrow that list further, so follow the receiver's implementation guide.
BTX-6 helps identify the product, software, device, or equipment involved. It is particularly useful when support needs to trace behaviour back to a specific build, lot, instrument, or manufacturer.
BTX-7 identifies the CP Lot Number for this blood product workflow. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
BTX-8 carries a measured, counted, priced, or dosed value. A number without the expected unit, currency, or companion qualifier is much easier to misread than an empty field.
BTX-9 carries a measured, counted, priced, or dosed value. A number without the expected unit, currency, or companion qualifier is much easier to misread than an empty field.
BTX-10 supplies the units that make the companion numeric field meaningful. Units should be coded consistently, especially for medication, lab, specimen, and billing quantities.
BTX-11 tells the receiver the state of this blood product workflow. Status fields often drive workflow branches, so use the agreed code and do not infer a status just because another field looks complete.
The coded value should follow HL7 table 0513 or the narrower table in the local profile.
BTX-12 tells the receiver the state of this blood product workflow. Status fields often drive workflow branches, so use the agreed code and do not infer a status just because another field looks complete.
The coded value should follow HL7 table 0511 or the narrower table in the local profile.
BTX-13 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
BTX-14 belongs to the medication/treatment workflow. Be explicit about whether the value describes the original order, encoded order, dispense event, scheduled give, or actual administration.
BTX-15 carries BP Verifier for this blood product workflow. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
BTX-16 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
For effective and end dates, make the boundary rule explicit. Receivers need to know whether the value is inclusive, exclusive, planned, actual, or merely informational.
BTX-17 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
For effective and end dates, make the boundary rule explicit. Receivers need to know whether the value is inclusive, exclusive, planned, actual, or merely informational.
BTX-18 says what action is being taken for this segment or record: add, update, delete, cancel, clear, or another profile-defined operation. It needs to agree with the message trigger and the previous state.
The generated panel links this to HL7 table 0514; many real interfaces narrow that list further, so follow the receiver's implementation guide.
BTX-19 qualifies the blood product workflow rather than identifying it. This is the sort of field receivers often use for branching, filtering, or display grouping.
Use the agreed value set, starting from HL7 table 0515. A local code without an agreed coding system is a small ambiguity that becomes a mapping problem later.