Running the NCPDP validation utility

Edit online

The NCPDP validation utility uses the existing NCPDP Telecom schemas in the pack for initial validation, with the restriction list checking disabled. The base ncpdp_vd_0.mtt and ncpdp_vf6.mtt (schema if using Design Server) are used for this.

About this task

Code values are checked against the input file element_restriction_list.json, using the codeListDate in the ncpdp_parameter.json file to determine the start date for code list values that may have been added in recent standard updates. This file has values for both F6 and D0 versions, using a new field version at all levels to distinguish any segments, fields, or values that are only used in F6 or D0.

The situational and field format rules are defined in segment_rules.json and segment_rules_f6.json. In this case both files are needed to support the two different versions, but the initial processing in the validation map will determine the version of the NCPDP input file, and select the correct segment rules input appropriately.

Failures from component rules or cardinality in the schema will be reported by error checking in the NCPDP validation utility through map rules and/or the Java exit that is invoked.

Follow these steps to run the NCPDP validation utility:

Procedure

  1. Update ncpdp_parameter.json with the code list date.
    For example, to enforce the code values from External Code lists that correspond to the set published in 2017 for activation in 2018, use the following:
    1. "codeListDate":"201710"
  2. Update ncpdp_parameter.json with the Medicaid option as desired. If validation per the Medicaid Subrogation rules is needed, use true. The default is false.
    1. "medicaidSub":true
  3. Ensure ncpdp_jexit.jar is available in the Java Classpath during validation utility execution by one of the following methods:
    1. Copy from <pack_install_dir>\ncpdp\jars to <tx_install_dir> directory on Windows or <install_dir>/libs directory on Unix.
    2. Add a jar reference in the [External Jar Files] section of the <tx_install_dir> dtx.ini file to the location of the jar file in <pack_install_dir>\ncpdp\jars.
    3. If running on the design server, edit the <pack_install_dir>\ncpdp\jars\ncpdpsetup.bat or ncpdpsetup.sh to point to your design server install, and execute the batch or shell script.
  4. Open the ncpdp_validation map.
  5. If validating data at the message level, perform the following steps:
    1. Update Input card 1 of ncpdp_message_validation to select the NCPDP input data for validation.
    2. Build all maps.
    3. Execute ncpdp_message_validation.
    4. Output files produced:
      • data/message_response.dat contains the Response message or the NCPDP proscribed format.
      • data/message_validation_report.xml contains XML formatted report
  6. If validating data at the batch level, perform the following steps:
    1. Update input card1 of the ncpdp_batch_validation map to select NCPDP data for validation.
    2. Build all maps.
    3. Execute ncpdp_batch_validation.
    4. Output files produced:
      • data/batch_response.dat contains the Response message or the NCPDP proscribed format.
      • data/batch_validation_report.xml contains XML formatted report