Optional: Add HIPAA Level 5 Code Lists to Sterling B2B Integrator

Edit online

About this task

HIPAA level 5 validation includes code lists that are maintained by external suppliers. To use HIPAA level 5 code lists with the Map Editor, you must obtain them from a third party, translate them into a format that can be validated by the SI_IE_Resources.xsd schema (as required by the Sterling B2B Integrator), and import them into the Sterling B2B Integrator.

Sterling B2B Integrator supplies a command line utility that you use to add the external HIPAA level 5 code lists to the Sterling B2B Integrator. Using the utility automatically converts the code lists to the required format. There is a Windows (.cmd) and a UNIX (.sh) version of the command line utility. After the import, the Map Editor validates against these new code lists.

To add a code list:

Procedure

  1. Download or save the code list you want to import to the tp_import directory where Sterling B2B Integrator is installed.
  2. From a command line, go to the tp_import directory.
  3. Type the following command to start the conversion and import process, where <map name> is the name of the map to use during translation (without the file extension) and <code list path and filename> is the fully qualified name of the code list to translate, including filename extension, if any:
    • If you are using Windows, hipaaconvert.cmd [-import] <map name> <code list path and filename>
    • If you are using UNIX, hipaaconvert.sh [-import] <map name> <code list path and filename>

      Do not specify the file extension for the map name when importing a code list—just indicate the base name of the map. Select the appropriate map for the code list that you are importing. See the table HIPAA Level 5 Code Lists Supported in Sterling B2B Integrator for more information on the map names.

      The [-import] parameter is optional. You can convert the code list file without importing it. If you do not use the [-import] parameter during conversion, you can import the resulting XML file into the Sterling B2B Integrator using the import utility.

  4. Once the utility completes, a translation report (hipaaconvert.rpt) and an input file (hipaaconvert.xml) are created. If no translation errors are reported, the code list was successfully generated (and imported if you used the [-import] parameter). A code list will not be imported if there are translation errors.
    Note: The code list conversion utility can also be used to run maps without creating a business process.