HIPAA Validation Error Severity

By default, any validation errors that occur cause a transaction to be rejected. When a transaction is rejected, the 997 generated contains the AK5 segment with a Transaction Set Acknowledgement Code of 'R' for the transaction. When validating HIPAA transactions, it is desirable to be able to control whether a validation error should cause the rejection of the entire transaction or not.

Sometimes we might want the error reported and the transaction rejected. At other times we might want to report the error in the 997 but to accept the transaction anyway (for example, the generated 997 would have a Transaction Set Acknowledgment Code of 'E' for accepted with errors). We might want validation errors ignored altogether or we might want only some validation errors ignored.

In conjunction with TIBCO Foresight® HIPAA Validator® Desktop, BusinessConnect Container Edition - EDI Protocol HIPAA Edition powered by Instream provides the ability to configure the severity of validation errors that occur in HIPAA transactions.

Controlling the severity of validation errors is done through the use of validator profile files. For more information about creating and configuring validator profile files to use with X12 transactions, see the "Configuring Validation Profile (.apf) Files" section in TIBCO BusinessConnect™ Container Edition - EDI Protocol powered by Instream® X12 Configuration. The remainder of this section contains information on validator profile files that is specific to HIPAA transactions.