Loop 2000D |
|
||||||
|
Pos |
Id |
Segment Name |
Req |
Max Use |
Repeat |
Usage |
|
010 |
HL |
Dependent Level |
O |
1 |
|
Situational |
|
020 |
TRN |
Patient Event Tracking Number |
O |
2 |
|
Situational |
|
070 |
DTP |
Accident Date |
O |
1 |
|
Situational |
|
070 |
DTP |
Last Menstrual Period Date |
O |
1 |
|
Situational |
|
070 |
DTP |
Estimated Date of Birth |
O |
1 |
|
Situational |
|
070 |
DTP |
Onset of Current Symptoms or Illness Date |
O |
1 |
|
Situational |
|
080 |
HI |
Dependent Diagnosis |
O |
1 |
|
Situational |
|
155 |
PWK |
Additional Patient Information |
O |
10 |
|
Situational |
|
170 |
|
Loop 2010DA |
O |
|
1 |
Required |
1. |
The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data. |
2. |
The HL segment defines a top-down/left-right ordered structure. |
3. |
HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction. |
4. |
HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate. |
5. |
HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information. |
6. |
HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment. |
Notes: |
1. Use this hierarchical loop only if the patient is someone other than the subscriber and the patient does not have a unique (different from the subscriber) member ID.
|
Example: |
HL*4*3*23*1~ |