Loop 2000A |
|
||||||
|
Pos |
Id |
Segment Name |
Req |
Max Use |
Repeat |
Usage |
|
010 |
HL |
Utilization Management Organization (UMO) Level |
M |
1 |
|
Required |
|
170 |
|
Loop 2010A |
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 segment to indicate the information source hierarchical level. For a request transaction, this segment corresponds to the identification of the payer, HMO, or other utilization management organization who will be the source of the decision/response. |
Example: |
HL*1**20*1~ |