Monday, February 27, 2017
EDI 270–5010 Documentation–2000A Hierarchical Level
EDI 270–5010 Documentation–2000A Hierarchical Level
HL – 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.
| 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 | See above for information | |
| Element Separator | AN | 1 | * | ||||
| HL02 | Hierarchical Parent ID Number | 0 | 1/12 | 734 | Not Used | ||
| Element Separator | 1 | * | |||||
| HL03 | Hierarchical Level Code | ID | 1/2 | 735 | R | 20 | |
| Element Separator | 1 | * | |||||
| HL04 | Hierarchical Child Code | ID | 1/1 | 736 | R | 1 | |
| Segment Terminator | ~ | ||||||
Sample:
HL*1**20*1~
Segment Structure
Available link for download
Thursday, February 9, 2017
EDI 270–5010 Documentation–BHT – Beginning of Hierarchical Transaction
EDI 270–5010 Documentation–BHT – Beginning of Hierarchical Transaction
BHT – Beginning of Hierarchical Transaction
| Loop | Seg ID | Segment Name | Format | Length | Ref# | Req | Value |
| Header | BHT | Beginning of Hierarchical Segment | 3 | R | BHT | ||
| Element Separator | AN | 1 | * | ||||
| BHT01 | Hierarchical Structure Code | ID | 4/4 | 1005 | R | 0022 | |
| Element Separator | AN | 1 | * | ||||
| BHT02 | Transaction set purpose Code | ID | 2/2 | 353 | R | 13 | |
| Element Separator | AN | 1 | * | ||||
| BHT03 | Reference Identification | AN | 1/50 | 127 | R | See below for more information | |
| Element Separator | AN | 1 | * | ||||
| BHT04 | Date | DT | 8/8 | 373 | R | Current date in YYYYMMDDD format | |
| Element Separator | AN | 1 | * | ||||
| BHT05 | Time | TM | 4/8 | 337 | R | Print time in HHMM Format | |
| Segment Terminator | ~ | ||||||
Code identifying purpose of transaction set
| Code | Definition |
| 13 | Request |
| 01 | Use this code to cancel a previously submitted 270 transaction. Only 270 transactions that used a BHT06 code of either ‘RT’ or ‘RU’ can be cancelled. The cancellation 270 transaction must contain the same BHT06 code as the previously submitted 270 transaction. |
BHT03 – Reference Identification
Just for tracking purpose, Software should generate unique EDI File Batch Number.
Available link for download