|
|||
Quick StartBefore you begin working with Clinical Edits Module for XEServer, follow the steps below: Crosswalks facilitate interoperability between code sets of different standards. A crosswalk is a correlation table that consists of source and target columns with equivalent elements that are mapped and used for translations of one code set to another. To get replacements/transformations for code, the module uses a crosswalk with a value available in the source column and a corresponding value in the target column.
To register crosswalks, you must add a path to each crosswalk to the configuration file CrosswalkRegistry.xml that is located at %ECRootPath%\Common. You can also use Edifecs SpecBuilder to register crosswalks.
After you install HIPAA Crosswalks, you get a set of crosswalk tables with pre-defined columns located at %ECRootPath%\repository\User\Crosswalks\HIPAA\ClinicalEdits. You must define a required set of clinical edits (provide code combinations) by adding the corresponding values to the crosswalk tables. You can use crosswalks provided at the Samples folder as templates that are based on CMS edits located at %ECRootPath%\STANDARDS\HIPAA\Crosswalks\ClinicalEdits\Samples. Note that these crosswalks are not used in rules, you can only use them for your reference. To fill in the crosswalk, use Edifecs SpecBuilder that provides a powerful user interface to build the crosswalk tables with great flexibility – several lookup columns, descriptive fields for the codes, date ranges support, and so on. For detailed crosswalks descriptions, click here.
In HIPAA guidelines, crosswalks are referenced by script rules. By default, crosswalk code transformations are disabled. To enable them, in the script rule, you must set the corresponding variable that works with the required crosswalk file to true.
For a complete scenario that shows you how to set up sample clinical edits, click here. |