These are the steps to map your XML message to an EDI message:

1. Create a DTD or W3C Schema using your XML file.
2. Import the DTD or W3C Schema.
3. Create a message definition using the EDI standard. You can create a new message definition by going to the Message|New menu item, and then select the "Using the EDI Standard" option.
4. Create a new map, i.e., XML to message, in the Mapper area.
5. Do the drag and drop operations.

Users can print a map report by going to Mapper|Reporter. When the Map Report screen appears, select a map name, and then click on the Report button to preview the report.

Go to View > Global Settings. The Settings Window is a tabbed dialog with four panes. The table below lists each pane by its title and function:

The list on the left allows you to select which element you want to define. You may select Report titles, headers, or footers. In the Report title, for example, you can enter the title of the map, followed by any specific tag, such as <ddd> defined below.

The STYLE button is a shortcut that switches the Styles pane so that you can set the font, color, and spacing for the text on which you are working.

The SPECIAL button allows you to insert special tags into the string being edited. When the report is generated, the tags are translated into report information. The table below lists the available tags:

By default, when an IFD is generated for an X12 message using the Redix GUI Mapper, the ST segment is not defined as a loop. In other words, only one ST/SE segment is allowed in an incoming X12 message. If you need to support multiple ST/SEs, you will have to define the ST segment as a loop header and increment the loop level for all of the segments between the ST and SE segments by one.

You can use the Redix GUI to easily accomplish this. Please follow the instructions below to change the ST segment to a loop header.

1. Open the GUI. In the Message area, select the message that you want to modify. Right click on the mouse and select the option "Edit This Message Definition".
2. In the Edit Message Definition screen, go to the Message tab. Press the button . In the Convert Message Definition screen, press the OK button as shown below.

To support external code lookups, Redix provides a high-performance codebase engine that allows users to store the code values in Redix-provided storage files. This help topic instructs users how to first build the Redix codebase storage files, then later use them in conjunction with the Redix Format Converter Engines.

Before the user builds a Redix codebase storage file, the user should have the raw data in a text file. Two types of raw data are acceptable. If the user simply wants to store the code values in a text file, then the input file must follow the correct syntax, that is, each code value in a line must not be more than 20 bytes in size.

However, if the user wants to store a description of each code value in the Redix codebase storage files, then each line must have two or three fields. Each field must be separated by a tab. The first field should contain the code values, and its size must not be greater than 20 bytes. The second field should contain a description of the code value, and its size must not be greater than 80 bytes. The third field is optional; it can be used to store a short description of the code. The size of the third field must not exceed 40 bytes. Some examples of the raw data text files are shown below. The first file below does not have a description, but the second file has both long and short descriptions.

File 1:
00501
00544
00601
00602

File 2:

AA ANESTHESIA SERVICES PERFORMED PERSONALLY BY ANESTHESIOLOGIST
Anesthesia perf by anesgst

AD MEDICAL SUPERVISION BY A PHYSICIAN: MORE THAN FOUR CONCURRENT
MD supervision, >4 anes proc

AH CLINICAL PSYCHOLOGIST
Clinical psychologist

The user can then use the Redix codebase load utilities (loadrcb or loadrcbext) to load the raw data into a codebase file. If the raw data file does not have a description field, then the user should use loadrcb. Otherwise, loadrcbexet should be used.

1) Load codebase files with code values only

If the filename of the first file above (File 1) is ZIP.txt and the user wants to name the codebase file as ZIP.dbf, then the user should enter the following command line:

loadrcb ZIP.txt ZIP

After a successful load, the output file will contain two storage files: one with the file extension ".cdx" for the index file and the other with the file extension ".dbf" for the data file. The user should place the outputted codebase files in the PATH, so that they can be used by the Redix Format Converter Engines.

The user can update the code value by using the updatercb command line. This utility allows users to perform an operation, i.e. an addition, a deletion, an update, or a find, on a code value in a given codebase file.

updatercb a ZIP 09999
The above example will add the code value "09999" to the codebase file "ZIP.dbf". updatercb

updatercb f ZIP 07728
The above example will attempt to find the code value "07728" in the codebase file "ZIP.dbf".

updatercb u ZIP 09999 07728
The above example will update the code value from "09999" to "07728" in the codebase file "ZIP.dbf".

updatercb d ZIP 09999
The above example will delete the code value "09999" from the codebase file "ZIP.dbf".

2) Load codebase files with codevalues and descriptions

If the filename of the second file (File 2) above is HCPCS.txt and the user wants to name the codebase file as HCPCS.dbf, then the user should use the following command line:

loadrcbext HCPCS.txt HCPCS

After a successful load, the output file will contain two storage files: one with the file extension ".cdx" for the index file and the other with the file extension ".dbf" for the data file. The user should place the outputted codebase files in the PATH, so that they can be used by the Redix Format Converter Engines.

The user can update the code value by using the updatercb command line. This utility allows users to perform an operation, i.e. an addition, a deletion, an update, or a find, on a code value in a given codebase file.

updatercb a HCPCS V5364 "DYSPHAGIA SCREENING" "Dysphagia screening" The above example will add the code value "V5364" with the long description "DYSPHAGIA SCREENING", and the short description "Dysphagia screening" to the codebase file "HCPCS.dbf".

updatercb f HCPCS AA
The above example will attempt to find the code value "AA" in the codebase file "HCPCS.dbf".

updatercb u HCPCS AA AB
The above example will update the code value from "AA" to "AB" in the codebase file "HCPCS.dbf".

updatercb d HCPCS AA
The above example will delete the code value "AA" from the codebase file "HCPCS.dbf".

3) Use codebase files in the IFD

After the codebase files are built, the user can use the values strored in the codebase files to validate an incoming data value. The data validation using the codebase files is called "D:" type. The following example uses the ZIP codebase files to validate an EDI message. In the EDI X12 standard, the ZIP code is defined as the element "116". The user can enter "D:ZIP" in the fifth element of the EMTDEFS section for element "116".

#EMTDEFS
100|3|3|ID||
1000|2|2|AN||
...
116|15|3|ID|D:ZIP|
...

The user can also use the Redix GUI to accomplish the same thing. In the Element Structure screen of the element number "116", the user can enter "D:ZIP" in the Code Check field as shown below:

Example D1:

D:CodebaseFileName (D:Taxonomy)

This case (type "D:") uses a Redix codebase storage file for validation. Each codebase storage file has two storage files: one with the file extension ".cdx" for the index file and the other with the file extension ".dbf" for the data file. Appending the file extension, ".dbf" or ".cdx", is optional. If the file extension is omitted, the Redix Format Converter Engine will automatically append ".dbf" or ".cdx" to the file name. In the above example, the file name of the codebase storage file is "Taxonomy".

When creating “D:” type statements, the user will need to use the executables, “loadrcb”, “updatercb”, and exportrcb”, to create the Redix codebase storage files.

Example D2:

D:CodebaseFileName:ElementNo (D:Health:1328)

This case (type "D:") uses a Redix codebase storage file and an element number to validate a given code value. The Example D1 has code values for a single element, i.e. each codebase storage file represents a single element number. (Each element allows multiple code values.) However, in Example D2, a single codebase storage file has multiple element numbers. As before, each element allows multiple code values. If a codebase storage file has multiple element numbers, then the data stored in the codebase file will have the following format:

ElementNumber:CodeValue

Note that there is a ":" between the element number and the code value.

Example D1 uses a codebase file for each element number. Therefore, for multiple element numbers, the user will need to prepare multiple codebase files. Example D2 uses a single codebase file for multiple element numbers.

Again, when creating “D:” type statements, the user will need to use the executables, “loadrcb”, “updatercb”, and exportrcb”, to create the Redix codebase storage files

Example D3:

D:CodebaseFileName:ElementNo (D:Health:1328:1322:1336)

This case (type "D:") uses a single codebase storage file and three element numbers to validate a given code value. The Redix engine will first validate a given code value against the values in element number 1328. If a match is found, then the given code is deemed valid. If a match is not found, then the system will use the values in the next element number, i.e. 1322, for the purpose of validation. If a match is still not found, then the system will use the values in the next element number, 1336, for the validation.

There is no limit as to how many element numbers may be entered in a given "D-type" code check statement.

4) Use codebase files in the OFD

Two OFD functions that a user can use to interface with the Redix codebase files are rcbcodecheck and rcbgetdesc. rcbcodecheck is used to validate a code value from a Redix codebase file. If the searchable code value is in the Redix codebase file, the integer 1 will be returned. Otherwise, 0 will be returned. rcbgetdesc returns the code description for a given codebase file. Two examples that use the functions rcbcodecheck and rcbgetdesc are shown below:

Example 1:

i = rdbcodecheck("HCPCS-2004", "J2275");
if (i=1)
writeln(of1, "Find it", 0,0,LEFT, " ");
else
writeln(of1, "Not find", 0,0,LEFT, " ");
end if;

Example 2:

writeln (of1, rcbgetdesc ("HCPCS-2004", "J2275", 1), 1, 80, LEFT, " ");
# the following long description will be returned.
# INJECTION, MORPHINE SULFATE (PRESERVATIVE-FREE STERILE SOLUTION), PER 10 MG

writeln (of1, rcbgetdesc ("HCPCS-2004", "J2275", 2), 1, 80, LEFT, " ");
# the following short description will be returned.
# Morphine sulfate injection

The NPI is a numeric 10-digit identifier, consisting of 9 numbers plus a check-digit in the 10th position. The check-digit is used to avoid any potential conflicts the NPI may have with other identification numbers used in the health care industry (patients, health plans, employers, etc).

Typically, the NPI is used in the ninth field of the NM1 segment. According to the HIPAA standard, when the eighth field is "XX", then the ninth field must be an NPI. The Redix engine provides two ways to validate an NPI value. One way is through the IFD, while the other way is through the OFD. When the IFD approach is used, the user should enter the following in the SEGCOND section:

NM1|J(ALL,8^XX,9^rdxNPI)

"rdxNPI" is a reserved word that is used internally by the Redix engine. The above statement means that if the value of the eighth field is "XX", then the ninth field must be a valid NPI. If it is not, then a non-terminating error is thrown.

The user can also use the OFD function isvalidNPI() to validate an NPI. A description of the NPI's validation scheme can be found in isvalidNPI() as well.

The following steps will help users set up the Command Line Interface using the GUI.

STEP 1:
Select a map to test in the Map Definitions Screen.

STEP 2:
Go to the Configuration Tab and fill in the fields for the file to be created.

STEP 3:
Configure the IFD and OFD by unchecking "Use Dynamically Generated IFD and OFD".  Then enter the IFD File Name, and OFD File Name.

STEP4:
Save the configuration.

STEP 5:
Generate the IFD and OFD for the map definition.  Click  from the Test Tab or the toolbar, or select "Generate IFD and OFD" from the Tools dropdown menu.  From the Generate IFD and OFD dialog box, select the map:

STEP 6:
Generate the interface commands for the "Command-Line" by going to the Integration Tab and selecting "Command-Line". The statements in the configuration file will be generated. For example:

STEP 7:
Save the setting to a configuration file.

STEP 8:
Run the map from the Command-line. Start a MS-DOS session, and change to the Redix directory. Type the following: redix [the configuration file]

HINT: This procedure may be used for all of the other types of interfaces on the Integration Tab. The other choices are examples of how to set up objects or function calls, and there should not be a need for a configuration file.