HL

Information Receiver Level

Pos: 010	Max: 1
Detail - Mandatory
Loop: 2000B	Elements: 4

Ref

Id

Element Name

Req

Type

Min/Max

Usage

HL01

628

Hierarchical ID Number
Description: A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
Use this sequentially assigned positive number to identify each specific occurrence of an HL segment within a transaction set. It should begin with the number one and be incremented by one for each successive occurrence of the HL segment within that specific transaction set (ST through SE).
An example of the use of the HL segment and this data element is:
HL*1**20*1~
NM1*PR*2*ABC INSURANCE COMPANY*****PI*842610001~
HL*2*1*21*1~
NM1*1P*1*JONES*MARCUS***MD*SV*0202034~

M

AN

1/12

Required

HL02

734

Hierarchical Parent ID Number
Description: Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
Use this code to identify the specific hierarchical level to which this level is subordinate.

O

AN

1/12

Required

HL03

735

Hierarchical Level Code
Description: Code defining the characteristic of a level in a hierarchical structure
All data that follows an HL segment is associated with the entity identified by the level code; this association continues until the next occurrence of an HL segment.

M

ID

1/2

Required

Code

Name

21

Information Receiver

HL04

736

Hierarchical Child Code
Description: Code indicating if there are hierarchical child data segments subordinate to the level being described
Use this code to indicate whether there are additional hierarchical levels subordinate to the current hierarchical level.
Because of the hierarchical structure, and because an additional HL always exists in this transaction, the code value in HL04 at the Loop 2000B level will always be “1".

O

ID

1/1

Required

Code

Name

1

Additional Subordinate HL Data Segment in This Hierarchical Structure.

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 identify the hierarchical or entity level of information being conveyed. The HL structure allows for the efficient nesting of related occurrences of information. The developers’ intent is to clearly identify the relationship of the patient to the subscriber and the subscriber to the provider.
Additionally, multiple subscribers and/or dependents (i.e., the patient) can be grouped together under the same provider or the information for multiple providers or information receivers can be grouped together for the same payer or information source.
2. In a batch environment, only one Loop 2000B (Information Receiver) loop is to be created for each unique information receiver within an Loop 2000A (Information Source) loop. Each Loop 2000C (Subscriber) loop that is subordinate to an information receiver is to be contained within only one Loop 2000B loop. There has been a misuse of the HL structure creating multiple Loop 2000Bs for the same information receiver with in an information source loop. This is not the developer’s intended use of the HL structure, and defeats the efficiencies that are designed into the HL structure.
3. An example of the overall structure of the transaction set when used in batch mode is:
Information Source (Loop 2000A)
Information Receiver (Loop 2000B)
Subscriber (Loop 2000C)
Dependent (Loop 2000D)
Eligibility or Benefit Inquiry
Dependent (Loop 2000D)
Eligibility or Benefit Inquiry
Subscriber (Loop 2000C)
Eligibility or Benefit Inquiry

Example:

HL*2*1*21*1~