The intent of this segment is to describe the actual donation procedure.
| Seq# | DataElement | Description | Must Implement | Flags | Cardinality | Length | C.LEN | Vocabulary | DataType |
|---|---|---|---|---|---|---|---|---|---|
DON
|
|||||||||
1
|
03340 | Donation Identification Number - DIN |
MAY
True:
False:
|
C |
[1..1] [0..1] |
EI | |||
|
2
|
03341 | Donation Type |
MAY
True:
False:
|
C |
[1..1] [0..1] |
CNE | |||
|
3
|
03342 | Phlebotomy Start Date/Time | SHALL | [1..1] | DTM | ||||
|
4
|
03343 | Phlebotomy End Date/Time | SHALL | [1..1] | DTM | ||||
|
5
|
03344 | Donation Duration | SHALL | [1..1] | NM | ||||
|
6
|
03345 | Donation Duration Units | SHALL | [1..1] | CNE | ||||
|
7
|
03346 | Intended Procedure Type | SHALL | [1..*] | CNE | ||||
|
8
|
03347 | Actual Procedure Type | SHALL | [1..*] | CNE | ||||
|
9
|
03348 | Donor Eligibility Flag | SHALL | [1..1] | ID | ||||
|
10
|
03349 | Donor Eligibility Procedure Type | SHALL | [1..*] | CNE | ||||
|
11
|
03350 | Donor Eligibility Date | SHALL | [1..1] | DTM | ||||
|
12
|
03351 | Process Interruption | SHALL | [1..1] | CNE | ||||
|
13
|
03352 | Process Interruption Reason | SHALL | [1..1] | CNE | ||||
|
14
|
03353 | Phlebotomy Issue | SHALL | [1..*] | CNE | ||||
|
15
|
03354 | Intended Recipient Blood Relative | SHALL | [1..1] | ID | ||||
|
16
|
03355 | Intended Recipient Name | SHALL | [1..1] | XPN | ||||
|
17
|
03356 | Intended Recipient DOB | SHALL | [1..1] | DTM | ||||
|
18
|
03357 | Intended Recipient Facility | SHALL | [1..1] | XON | ||||
|
19
|
03358 | Intended Recipient Procedure Date | SHALL | [1..1] | DTM | ||||
|
20
|
03359 | Intended Recipient Ordering Provider | SHALL | [1..1] | XPN | ||||
|
21
|
03360 | Phlebotomy Status | SHALL | [1..1] | CNE | ||||
|
22
|
03361 | Arm Stick | SHALL | [1..1] | CNE | ||||
|
23
|
03362 | Bleed Start Phlebotomist | SHALL | [1..1] | XPN | ||||
|
24
|
03363 | Bleed End Phlebotomist | SHALL | [1..1] | XPN | ||||
|
25
|
03364 | Aphaeresis Type Machine | SHALL | # | [1..1] | 75 | ST | ||
|
26
|
03365 | Aphaeresis Machine Serial Number | SHALL | # | [1..1] | 25 | ST | ||
|
27
|
03366 | Donor Reaction | SHALL | [1..1] | ID | ||||
|
28
|
03367 | Final Review Staff ID | SHALL | [1..1] | XPN | ||||
|
29
|
03368 | Final Review Date/Time | SHALL | [1..1] | DTM | ||||
|
30
|
03369 | Number of Tubes Collected | SHALL | [1..1] | NM | ||||
|
31
|
03370 | Donation Sample Identifier | SHALL | [1..*] | EI | ||||
|
32
|
03371 | Donation Accept Staff | SHALL | [1..1] | XCN | ||||
|
33
|
03372 | Donation Material Review Staff | SHALL | [1..*] | XCN | ||||
|
34
|
00816 | Action Code | [0..1] | [2..2] | ID | ||||
Definition: This field contains a unique identifier, Donation Identification Number (DIN), for the specific donation and is therefore mandatory except when using an eligibility message type in which only DON-9, DON-10, and DON-11 are populated. DON-2 Donation Type (CNE) 03341
Definition: The type of donation. This element is mandatory except when using an eligibility message type in which only DON-9, DON-10, and DON-11 are populated. The values for this field are defined in Table RT008 - Type of Donation or Collection in 6th Position of Product Code in the ISBT 128 Standard Technical Specification, which is maintained by ICCBBA. Link: http://iccbba.org/technicalspecification.pdf. Table 5 Data Structure 002.
Definition: The start date and time of the phlebotomy.
Definition: The end date and time of the phlebotomy.
Definition: The duration of the phlebotomy or the length of time that elapsed between the phlebotomy start date and time and the phlebotomy end date and time.
Definition: The duration units. The duration units and duration are restricted to minutes and seconds. Concepts are pulled from the UCUM code system (www.unitsofmeasure.org). Refer to HL7-Defined Table 0932 – Donation Duration Units in Chapter 2C, Code Tables, for valid entries.
Definition: The procedure(s) intended to be performed on the donor. Refer to HL7-Defined Table 0933 – Intended Procedure Type in Chapter 2C, Code Tables, for valid entries.
Definition: The actual procedure(s) performed on the donor. Refer to HL7-Defined Table 0933 – Intended Procedure Type in Chapter 2C, Code Tables, for valid entries.
Definition: Is the Donor eligible for donation? Yes or No. Refer to HL7 Table 0136 -Yes/No Indicator as defined in Chapter 2C, Code Tables.
Definition: The procedure(s) for which the donor is eligible. Refer to HL7-Defined Table 0933 – Intended Procedure Type in Chapter 2C, Code Tables, for valid entries.
Definition: The date and time on which the donor is eligible to donate.
Definition: Was the donation process interrupted after it began? Refer to HL7-Defined Table 0923 – Process Interruption in Chapter 2C, Code Tables, for valid entries.
Definition: Reason that the donation process was interrupted. Refer to HL7-Defined Table 0935 – Process Interruption Reason in Chapter 2C, Code Tables, for valid entries.
Definition: Indicates whether there is a problem or issue with the phlebotomy itself. This may be due to an incorrect needle procedure, needle defect, tube blockage, problem with the apheresis machine, or improper action by the phlebotomist. Refer to HL7-Defined Table 0925 – Phlebotomy Issue in Chapter 2C, Code Tables, for valid entries.
Definition: If this donation has an intended recipient (directed, dedicated, designated), is the intended recipient a blood relative of the donor? Yes or No. Refer to HL7 Table 0136 -Yes/No Indicator as defined in Chapter 2C, Code Tables.
Definition: If this is donation has an intended recipient (autologous, directed, dedicated, designated), the intended recipient’s name.
Definition: If this donation has an intended recipient (autologous, directed, dedicated, designated), the intended recipient’s date of birth.
Definition: If this donation has an intended recipient (autologous, directed, dedicated, designated), the facility where the intended recipient is expected to receive the transfusion.
Definition: If this donation has an intended recipient (autologous, directed, dedicated, designated), the date the intended recipient is expected to receive the transfusion.
Definition: If this is donation has an intended recipient (autologous, directed, dedicated, designated), the provider who ordered the directed donation for the intended recipient.
Definition: Whether the phlebotomy was successful, not drawn, or unsuccessful, and if unsuccessful, the extent to which it was unsuccessful. Refer to HL7-Defined Table 0926 – Phlebotomy Status in Chapter 2C, Code Tables, for valid entries.
Definition: The arm(s) stuck for the donation. Refer to HL7-Defined Table 0927 – Arm Stick in Chapter 2C, Code Tables, for valid entries.
Definition: The Phlebotomist who starts the blood flow into the container.
Definition: The Phlebotomist who ends the blood flow into the container.
Definition: The type of aphaeresis machine, if used, for the donation. It will be the specific product name of the machine (e.g. Trima, Amicus, Alyx, Symal, etc.).
Definition: The serial number of the aphaeresis machine, if used, for the donation.
Definition: Did the donor have any adverse reaction during the donation procedure? Yes or No. Refer to HL7 Table 0136 -Yes/No Indicator as defined in Chapter 2C, Code Tables. If this element is valued "Y"es, there should be OBX segments following the Donation segment which details the adverse reactions.
Definition: The Staff member conducting the final review and reconciliation of all documentation created during the collection process.
Definition: The date and time a final review of all documentation and labeling of the blood material is completed.
Definition: The number of samples collected during the donation which will be used for subsequent testing.
Definition: The sample identifier for the sample collected during a donation for the purpose of testing. This is a field for sample or specimen identifiers.
Definition: The staff member who reviewed all the intake materials, assessments and determined the donor can undergo a donation procedure at this time.
Definition: The staff member who performs review on all documentation subsequent to donation procedure.
(Definition from OH1.2 in Ch. 3)
Definition: This field contains a code defining the action to be taken for this segment. It allows this segment to be sent to delete or update, for example, previously sent information. Refer to HL7 Table 0206 – Segment Action Code in Chapter 2C, Code Tables, for valid values.
(Definition from OH2.2 in Ch. 3)
Definition: This field contains a code defining the action to be taken for this segment. It allows this segment to be sent to delete or update, for example, previously sent information. Refer to HL7 Table 0206 – Segment Action Code in Chapter 2C, Code Tables, for valid values.
(Definition from OH3.2 in Ch. 3)
Definition: This field contains a code defining the action to be taken for this segment. It allows this segment to be sent to delete or update, for example, previously sent information. Refer to HL7 Table 0206 – Segment Action Code in Chapter 2C, Code Tables, for valid values.
(Definition from OH4.2 in Ch. 3)
Definition: This field contains a code defining the action to be taken for this segment. It allows this segment to be sent to delete or update, for example, previously sent information. Refer to HL7 Table 0206 – Segment Action Code in Chapter 2C, Code Tables, for valid values.
(Definition from ORC.35 in Ch. 4)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when either ORC-2 and/or ORC 3 is valued with a unique identifier in accordance with Chapter 2, Section 2.10.4.2.
(Definition from OBR.55 in Ch. 4)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when either an OBR-2 and/or OBR-3 is valued with unique identifier in accordance with Chapter 2, Section 2.10.4.2.
(Definition from IPC.10 in Ch. 4)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when the combination of IPC-1, IPC-2, IPC-3, and IPC-4 represents a unique identifier according to Chapter 2, Section 2.10.4.2.
(Definition from BPX.22 in Ch. 4)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when an BPX is uniquely identified sufficiently within the specific implementation using BPX-17 or BPX-6 as agreed to by the trading partners and in accordance with Chapter 2, Section 2.10.4.2.
(Definition from BTX.21 in Ch. 4)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when an BTX is uniquely identified sufficiently within the specific implementation using BTX-20 or BTX-3 as agreed to by the trading partners in accordance with Chapter 2, Section 2.10.4.2.
(Definition from DON.34 in Ch. 4)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when an DON is uniquely identified sufficiently within the specific implementation using DON-1 in accordance with Chapter 2, Section 2.10.4.2.
(Definition from BUI.13 in Ch. 4)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when an BUI is uniquely identified sufficiently within the specific implementation using BUI-2 in accordance with Chapter 2, Section 2.10.4.2
(Definition from RXV.22 in Ch. 4A)
Definition: The intended handling by the receiver of the infusion order is represented by this segment. Refer to HL7 Table 0206 – Segment Action Code in Chapter 2C, Code Tables, for valid values.
(Definition from CDO.2 in Ch. 4A)
Definition: The Action Code indicates whether the cumulative dosage segment is intended to be added, deleted, updated, or did not change. If the field is not valued in any CDO segments for the order, the segments are considered to have been sent in snapshot mode. If some but not all CDO segments for the order do not have the action code valued, the default value is Add. Refer to HL7 Table 0206 - Segment Action Code in Chapter 2C, Code Tables, for valid values.
(Definition from OBR.55 in Ch. 7)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when an either OBR-2 and/or OBR-3 is valued with unique identifier in accordance with Chapter 2, Section 2.10.4.2.
(Definition from OBX.31 in Ch. 7)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when an OBX-21 is valued in accordance with guidance in Chapter 2, Section 2.10.4.2.
(Definition from SPM.35 in Ch. 7)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when an SPM-2 or SPM-31 is valued in accordance with the guidance in Chapter 2, Section 2.10.4.2.
(Definition from PRT.2 in Ch. 7)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0287 – Problem/goal action code for valid values.
(Definition from CSR.17 in Ch. 7)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when CSR-1 and CSR-4, or CSR-2 and CSR-5 are valued as agreed to by the trading partners in accordance with the guidance in Chapter 2, Section 2.10.4.2.
(Definition from CTI.4 in Ch. 7)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when CTI-1 is valued in accordance with the guidance in Chapter 2, Section 2.10.4.2.
(Definition from SHP.12 in Ch. 7)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when SHP-1 is valued in accordance with the guidance in Chapter 2, Section 2.10.4.2.
(Definition from PAC.9 in Ch. 7)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when PAC-2 is valued in accordance with the guidance in Chapter 2, Section 2.10.4.2.
(Definition from GOL.1 in Ch. 12)
Definition: The action code field gives the intent of the problem or goal. Refer to HL7 Table 0287 – Problem/Goal Action Code in Chapter 2C, Code Tables, for valid values.
(Definition from PRB.1 in Ch. 12)
Definition: This field contains the intent of the message. Refer to HL7 Table 0287 – Problem/Goal Action Code in Chapter 2C, Code Tables, for valid values.
(Definition from PTH.1 in Ch. 12)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0287 – Problem/Goal Action Code in Chapter 2C, Code Tables, for valid values.
(Definition from DEV.1 in Ch. 17)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0287 – Problem/goal action code for valid values.
®© HL7.org 2019+. HL7 v2+ generated on December 11, 2020
Links:
Version History
|
Propose a change
|
License
The Demo site for our new HL7 Version 2+ (plus) Standard
