Type 5 validation best practices

It is recommended that when adding multiple Type 5 validations, such as State, ICD-9, etc., that a map be created based upon the example provided for each validation.

These maps should be saved and used anytime new versions of the Pack for HIPAA EDI are received. This will allow easy integration of Type 5 validation specific to the environment with new versions.

The choice of when to place the validation in a restriction list vs. component rule vs. database table depends upon the environment and the code set. If the code set changes frequently, database tables should make validation easier as the trees do not have to change frequently.

However, there will be a performance penalty when validating against an external database or file as opposed to a restriction list.

The original hipaa_x12_segment tree and hipaa_x12 tree should be backed up and kept safe. If performance problems are found when using updated Type 5 trees, the same benchmark should be run with the original trees to determine if the difference is in the Type 5 validation. In addition, the original trees allow for debugging of possible problems independent of any changes.