Blood product order messages require additional information that is not available in other standard HL7 order messages. Blood product order messages need to contain accompanying details regarding the blood product component, such as special processing requirements (e.g., irradiation and leukoreduction) and the amount of the blood product to be administered.
The following table presents various use cases surrounding blood product orders.
Universal Service ID [ISBT-128 Product Code] | Blood Product Processing Requirements | Quantity | Blood Product Amount | Units |
002^Red Blood Cells | Leukoreduced | 2 | Ml | |
002^Red Blood Cells | Leukoreduced | 1 | 60 | Ml |
002^Red Blood Cells | Irradiated | 2 | 15 | Ml |
002^Red Blood Cells | Leukoreduced | 1 | ||
020^Platelets | Leukoreduced Irradiated | 6 | ||
024^ Apheresis Platelets | Irradiated | 1 | ||
002^Red Blood Cells | 1 | |||
Factor VIII | 2 | 910 | IU |
| Seq# | Data Element Name | DataType | Usage | Vocabulary | Cardinality | Item # | Length | C.LEN | Flags |
|---|---|---|---|---|---|---|---|---|---|
BPO
|
|||||||||
1
|
Set ID – BPO | SI | R | [1..1] | 01700 | [1..4] | |||
|
2
|
BP Universal Service Identifier | CWE | R | [1..1] | 01701 | ||||
|
3
|
BP Processing Requirements | CWE | O | [0..*] | 01702 | ||||
|
4
|
BP Quantity | NM | R | [1..1] | 01703 | 5 | # | ||
|
5
|
BP Amount | NM | O | [0..1] | 01704 | 5 | # | ||
|
6
|
BP Units | CWE | O | [0..1] | 01705 | ||||
|
7
|
BP Intended Use Date/Time | DTM | O | [0..1] | 01706 | ||||
|
8
|
BP Intended Dispense From Location | PL | O | [0..1] | 01707 | ||||
|
9
|
BP Intended Dispense From Address | XAD | O | [0..1] | 01708 | ||||
|
10
|
BP Requested Dispense Date/Time | DTM | O | [0..1] | 01709 | ||||
|
11
|
BP Requested Dispense To Location | PL | O | [0..1] | 01710 | ||||
|
12
|
BP Requested Dispense To Address | XAD | O | [0..1] | 01711 | ||||
|
13
|
BP Indication for Use | CWE | O | [0..*] | 01712 | ||||
14
|
BP Informed Consent Indicator | ID | O | [0..1] | 01713 | [1..1] | |||
Definition: This field contains the sequence number for the BPO segment within the message. For the first order transmitted, the sequence number shall be 1; for the second order, it shall be 2; and so on.
Definition: This field contains the identifier code for the requested blood product. This can be based on local and/or "universal" codes. We recommend the "universal" procedure identifier. The structure of this CWE data type is described in the control section. The preferred coding system is the ISBT 128 Product Code. Refer to Table 0575 - BP Universal Service Identifier in Chapter 2C for valid values.
Blood Product Orders for commercial products, such as Rh Immune Globulin or Factor VIII concentrate, are not at this time defined in an international or national coding system as are blood products. Therefore, locally defined codes can be used for the Universal Service Identifier for commercial products.
Definition: This field contains additional information about the blood component class associated with the Universal Service ID. The placer of the order can specify any required processing of the blood product that must be completed prior to transfusion to the intended recipient. Refer to User-Defined Table 0508 - Blood Product Processing Requirements in Chapter 2C, Code Tables, for suggested values.
Definition: This field contains the number of blood products ordered.
Definition: This field contains the ordered amount (volume) associated with each quantity of blood product.
Definition: This field contains the units of measure for the blood product amount. (See Chapter 7 for more details about reporting units.) This field specifies the units of measure for volume of a blood component (i.e., 50 ml) or the units of measure or dosage of a commercial product (i.e., 910 I.U. - International Units - of Factor VIII Concentrate). Use of UCUM is strongly recommended as one of the delivered units (could be in addition to the local units). Refer to Table 0576 - BP Units in Chapter 2C for valid values.
Definition: This field specifies the date/time that the placer intends to use the blood product that is being ordered.
This is the time when the placer expects the product to be available within the transfusion service. For example, the product should be available for use, but not dispensed, on this date/time.
Definition: This field contains the location from which the blood component is to be dispensed.
Definition: This field contains the actual address of the location from which the blood component is to be dispensed.
Definition: This field specifies the date/time that the requested blood products must be ready to dispense. This date/time may be different from the intended use date/time. For example, the patient may be scheduled to come in for a transfusion at a specified time. However, the placer would request that the blood product be ready to dispense prior to that time in order to have the blood component ready for transfusion at the scheduled time. The field may also be used to indicate that the placer is now ready to pick up the ordered blood product and is requesting the blood product be ready to dispense at that time.
Definition: This field contains the inpatient or outpatient location to which the blood component is to be dispensed. The default dispense to location is the current census location for the patient.
Definition: This field contains the actual address of the location to which the blood component is to be dispensed. The default dispense to location is the current census location for the patient.
Definition: This is a coded optional field. The value indicates the reason that the blood product was ordered. This information is helpful for prospective review or retrospective studies of blood product ordering practices of the ordering provider by the Quality Assurance Department and/or Transfusion Committee. Refer to User-Defined Table 0509 - Indication for Use in Chapter 2C, Code Tables, for suggested values.
This field indicates whether consent for the transfusion has been obtained. Refer to HL7 table 0136 -Yes/No indicator as defined in Chapter 2C, Code Tables.
®© HL7.org 2019+. HL7 v2+ generated on March 23, 2022
Links:
Version History
|
Propose a change
|
License
The Demo site for our new HL7 Version 2+ (plus) Standard
