Instructions for running the Configurable rules application
- Determine which extended level 2, 3, and level 4 rules must be changed from their default on
and off states. These defaults might not have to be changed, but they must be changed if either
of the following conditions occur:
- If an unwanted rule failure exists on an acknowledgment. Note the rule number and investigate. After investigation, it might be determined that validation might not be required for that rule.
- If an expected failure is not observed upon acknowledgement. If an investigation determines that the rule is in the mini qualifier file, but has not been enabled.
- Back up installed files to a safe location. During the process of configuring the rules, a
new qualifier data file and a new set of HIPAA EDI schemas are generated. Save these files in a safe
location:install_dir\packs_healthcare_vn.n.n\hipaa\configurable_rules\data\
- configurable_rules_mini_qualifier.dat
install_dir\packs_healthcare_vn.n.n\hipaa\data\- hipaa_x12_qualifier.dat
install_dir\packs_healthcare_vn.n.n\hipaa\trees\
- hipaa_x12.mtt
- hipaa_x12_type_2.mtt
- hipaa_x12_ruleless.mtt
If the Configurable Rules application is run multiple times, save both of the out-of-the-box pack files, as well as interim versions of the files created.
- Modify the mini qualifier file to change the on and off states of the rules that are
identified in step 1 of this procedure. To change the usage of the rules, you must edit the
configurable_rules_mini_qualifier.dat file at this directory
location:
install_dir\packs_healthcare_vn.n.n\hipaa\configurable_rules\data\
The configurable_rules_mini_qualifier.dat file is organized as follows:
- One rule (record) per line, delimited by "^."
- Field 1: Rule number, internal Transformation Extender reference
- Field 2: Transaction version reference, matching the GS08.
- Field 3: Transaction ID
- Field 4: WEDI/SNIP validation level
- Field 5: ON/OFF indicator. 0 (zero) indicates off, and 1 (one) indicates on. This is the only information that can be changed in this file. Save the file after changes are made.
- Field 6: Description of Rule
- Run the configurable rules map file, configurable_rules.mms, in the map
source. This file is located at this directory
location:
install_dir\packs\healthcare_vn.n.n\hipaa\configurable_rules\maps\
The executable map is configurable_rules. Run the map as follows:- Open configurable_rules.mms in the Design Server.
- Build all of the maps.
- Run the configurable_rules map.
- Verify the results by viewing the qualifier_report.html file at this
directory
location:
install_dir\packs\healthcare_vn.n.n\hipaa\configurable_rules\data\
- Verify the results and ensure that the type tree script files listed in this step are
created in this
directory:
install_dir\packs\healthcare_vn.n.n\hipaa\configurable_rules\trees- hipaa_x12.mts
- hipaa_x12_type_2.mts
- hipaa_x12_ruleless.mts
- hipaa_x12_master_rule_updated.mts
- If you are running the Command Server, execute the
import_trees.bat file. This file imports the type trees that are required
by the Compliance Check application. It is located in the following
directory:
install_dir\packs\healthcare_vn.n.n\hipaa\configurable_rules\master
This file can be executed by using a command prompt or by double-clicking on the file name in the Windows directory. Verify that the files listed in this step are generated in this directory:
install_dir\packs\healthcare_vn.n.n\hipaa\configurable_rules\trees- hipaa_x12.mtt
- hipaa_x12_type_2.mtt
- hipaa_x12_ruleless.mtt
- If you are not running the Command Server, the type trees must be imported one at a time using the Design Server. See the Design Server documentation for instructions on importing type trees.
- Move the type trees generated in Step 7 of this procedure to the following
directory:
install_dir\packs\healthcare_vn.n.n\hipaa\trees\
- Rename the hipaa_x12_qualifier_updated.dat file, which is located in
the directory to hipaa_x12_qualifier.dat. Move the renamed file to:
install_dir\packs\healthcare_vn.n.n\hipaa\data - Rebuild all of the executable maps in the compliance_check.mms file.