EDI 5010 Documentation–837 - BHT - Beginning of Hierarchical Transaction

BHT – Beginning of Hierarchical Transaction

        

Loop Seg ID Segment Name Format Length Ref# Req Value
  BHT Beginning of Hierarchical Segment 3 R BHT
Element Separator AN 1 *
BHT01 Hierarchical Structure Code ID 4/4 1005 R 0019
Element Separator AN 1 *
BHT02 Transaction set purpose Code ID 2/2 353 R 00
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 YYYYMMDD Format
Element Separator AN 1 *
BHT05
Interchange ID Qualifier
TM 4/8 337 R Current time in HHMMSS Format
Element Separator AN 1 *
BHT06 Transaction Type Code ID 2/2 640 R CH
Segment Terminator ~
               
Sample:
BHT*0019*00*000000223*20120105*1104*CH ~

BHT02 – Transaction set Purpose Code.
Code identifying purpose of transaction set
Code Definition
00 Original
18 Reissue


BHT03 – Reference Identification
Just for tracking purpose, Software should generate unique EDI File Batch Number.
BHT06 – Transaction Type Code
Code identifying purpose of transaction code
Code Definition
31 Subrogation Demand
CH Chargeable – Use this code when the transaction contains only fee for service claims or claims with at least one chargeable line item. if it is not clear whether a transaction contains claims or encounters, or if the transaction contains a mix of claims and encounters, the developers of this implementation guide recommend using code CH.
RP Reporting – Use RP When the entire ST-SE envelope contains encounters. Use RP When the transaction is being sent to an entity.

        

 
Questions or feedback are always welcome. You can email me at vbsenthilinnet@gmail.com