HL – Billing Provider Hierarchical Level
Use the Billing Provider HL to identify the original entity who submitted the electronic claim/encounter to the destination payer
Hierarchical ID Number
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure.
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. HL01 must begin with “1" and be incremented by one each time an HL is used in the transaction. Only numeric values are allowed in HL01.
Example:
For the first Claim, Start the counter as 1. For the subsequent claims, increase the counter and print that value. The following picture shows the hierarchy for the EDI File that contains only one claim. You can download the EDI File here.
The following Picture shows the hierarchy if the claim contains two claims. You can download the EDI File here.
The following Picture shows the hierarchy if the claim contains three claims. You can download the EDI File here.
The following Picture shows the hierarchy if the claim contains Four claims. You can download the EDI File here.
Loop | Seg ID | Segment Name | Format | Length | Ref# | Req | Value |
2000A | HL | Billing Hierarchical Level | 2 | R | HL | ||
Element Separator | AN | 1 | * | ||||
HL01 | Hierarchical ID Number | AN | 1/12 | 628 | R | 1 | |
Element Separator | AN | 1 | * | ||||
HL02 | Hierarchical Parent ID Number | 0 | 1/12 | 734 | Not Used | ||
Element Separator | AN | 1 | * | ||||
HL03 | Hierarchical Level Code | ID | 1/2 | 735 | R | 20 | |
Segment Terminator | ~ | ||||||
HL04 | Hierarchical Child Code | ID | 1/1 | 736 | R | 1 | |
Segment End | ~ |
Sample:
HL*1**20*1~
------------------------------------------------------------------------------------------------------------------
0 comments:
Post a Comment