Implementation

Type 7 Rules specified in the Qualifier file

Type 7 validation with a custom user exit

The HIPAA data compliance application is not a full trading partner application, but the new features allow for basic customization based on the value in the data’s functional group Application Receiver ID (GS03).

For each “Institution” in the hipaa_x12_type_7_value.json input file to hipaa_data_compliance, if the Type 7 rule in the hipaa_x12_qualifier.json contains this same keyword, AND the GS03 value of the transaction being validated matches the “GS03Value” field in the hipaa_x12_type_7_value.json input file, then hipaa_data_compliance will validate the rest of the rule as defined in the hipaa_x12_qualifier.json.

Type 7 validation with a custom user exit

In addition to Type 7 rules that are defined in the hipaa_x12_qualifier.json file, you can also provide a custom user exit in Java or C++

The custom user exit must be designed to use HIPAA data and delimiters in a specific format. The custom user exit must conform to the format of the data that is generated during run time by the hipaa data compliance application, which is only available during run time.

The string of HIPAA EDI starts with the segment identifier that is followed by the loop ID. For example:

ST**270*1235*005010X279A1~

BHT**0022*13*10001235*20060501*1320~

HL*2000A*1**20*1~

NM1*2100A*PR*2*ABC COMPANY*****PI*842610001~

HL*2000B*2*1*21*1~

NM1*2100B*1P*1*PENWISE*MARCUS****XX*0202034209~

REF*2100B*JD*178583840~

REF*2100B*EO*477563928~

SE**22*1235~