HL7 BPX Blood product dispense status
HL7 field reference BPX 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 |
|---|---|---|---|---|---|
| BPX.1 | Set ID - BPX | Yes | No | SI | |
| BPX.2 | BP Dispense Status | Yes | No | CWE | 0510 |
| BPX.3 | BP Status | Yes | No | ID | 0511 |
| BPX.4 | BP Date/Time of Status | Yes | No | TS | |
| BPX.5 | BC Donation ID | No | No | EI | |
| BPX.6 | BC Component | No | No | CNE | |
| BPX.7 | BC Donation Type / Intended Use | No | No | CNE | |
| BPX.8 | CP Commercial Product | No | No | CWE | 0512 |
| BPX.9 | CP Manufacturer | No | No | XON | |
| BPX.10 | CP Lot Number | No | No | EI | |
| BPX.11 | BP Blood Group | No | No | CNE | |
| BPX.12 | BC Special Testing | No | Yes | CNE | |
| BPX.13 | BP Expiration Date/Time | No | No | TS | |
| BPX.14 | BP Quantity | Yes | No | NM | |
| BPX.15 | BP Amount | No | No | NM | |
| BPX.16 | BP Units | No | No | CE | |
| BPX.17 | BP Unique ID | No | No | EI | |
| BPX.18 | BP Actual Dispensed To Location | No | No | PL | |
| BPX.19 | BP Actual Dispensed To Address | No | No | XAD | |
| BPX.20 | BP Dispensed to Receiver | No | No | XCN | |
| BPX.21 | BP Dispensing Individual | No | No | XCN |
BPX reports the dispense or status state of a blood product unit, tying the product, unit identifiers, disposition, timing, and responsible parties together.
The standard describes BPX this way: In the processing of blood products, it is necessary for the transfusion service and the placer system to communicate information. The status messages need to contain additional information regarding the blood products requested, such as the unique donation ID, product code, blood type, expiration date/time of the blood product, and current status of the product. This segment is similar to an OBX segment, but contains additional attributes.
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 BPX in BPS_O29 - BPS - Blood product dispense status and BRP_O30 - BRP - Blood product dispense status acknowledgment. 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.
BPX-1 is the sequence number for this BPX segment within its repeating group. It keeps multiple BPX lines in order; it is not the business identifier for the blood product workflow.
BPX-2 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 0510 or the narrower table in the local profile.
BPX-3 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.
BPX-4 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.
BPX-5 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.
BPX-6 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.
BPX-7 qualifies the blood product workflow rather than identifying it. This is the sort of field receivers often use for branching, filtering, or display grouping.
BPX-8 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.
BPX-9 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.
BPX-10 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.
BPX-11 carries BP 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.
BPX-12 carries BC Special Testing 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.
This field can repeat. Use repetitions for separate real-world values, not as a workaround for putting several unrelated ideas in one field.
BPX-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.
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.
BPX-14 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.
BPX-15 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.
BPX-16 supplies the units that make the companion numeric field meaningful. Units should be coded consistently, especially for medication, lab, specimen, and billing quantities.
BPX-17 identifies the BP Unique 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.
BPX-18 places the blood product workflow in an organization, facility, department, room, bed, or location group. Keep physical location, owning department, and receiving facility separate when the datatype allows it.
BPX-19 carries contact details. Use the datatype components for use code, equipment type, address type, country, and other qualifiers rather than squeezing everything into one formatted string.
BPX-20 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.
BPX-21 carries BP Dispensing Individual 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.