	Ref	Id	Element Name	Req	Type	Min/Max	Usage
	BHT01	1005	Hierarchical Structure Code Description: Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set	M	ID	4/4	Required

BHT02

353

Transaction Set Purpose Code
Description: Code identifying purpose of transaction set
Alias: Transaction Set Purpose Code
NSF Reference: AA0-23.0
BHT02 is intended to convey the electronic transmission status of the 837 batch contained in this ST-SE envelope. The terms “original” and “reissue” refer to the electronic transmission status of the 837 batch, not the billing status.
ORIGINAL: Original transmissions are claims/encounters which have never been sent to the receiver. Generally nearly all transmissions to a payer entity (as the ultimate destination of the transaction) are original.
REISSUE: In the case where a transmission was disrupted the receiver can request that the batch be sent again. Use “Reissue” when resending transmission batches that have been previously sent.

2/2

Required

BHT03	127	Reference Identification Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier Industry: Originator Application Transaction Identifier NSF Reference: AA0-05.0 The inventory file number of the tape or transmission assigned by the submitter’s system. This number operates as a batch control number. It may or may not be identical to the number carried in ST02.	O	AN	1/30	Required
BHT04	373	Date Description: Date expressed as CCYYMMDD Industry: Transaction Set Creation Date NSF Reference: AA0-15.0 Identifies the date that the submitter created the file.	O	DT	8/8	Required
BHT05	337	Time Description: Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99) Industry: Transaction Set Creation Time NSF Reference: AA0-16.0 Use this time to identify the time of day that the submitter created the file.	O	TM	4/8	Required
BHT06	640	Transaction Type Code Description: Code specifying the type of transaction Industry: Claim or Encounter Identifier Alias: Claim or Encounter Indicator Although this element is required, submitters are not necessarily required to accurately batch claims and encounters at this level. Generally CH is used for claims and RP is used for encounters. However, if an ST-SE envelope contains both claims and encounters use CH. Some trading partner agreements may specify using only one code.	O	ID	2/2	Required

Code

Name

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.

Reporting

Use RP when the entire ST-SE envelope contains encounters.
Use RP when the transaction is being sent to an entity (usually not a payer or a normal provider-payer transmission intermediary) for purposes other than adjudication of a claim. Such an entity could be a state health data agency which is using the 837 for health data reporting purposes.

1.	BHT03 is the number assigned by the originator to identify the transaction within the originator's business application system.
2.	BHT04 is the date the transaction was created within the business application system.
3.	BHT05 is the time the transaction was created within the business application system.

	Code	Name
	0019	Information Source, Subscriber, Dependent