ISErrorRefiner Configuration File

The ISErrorRefiner Configuration File is used to specify the changes that ISErrorRefiner is to make.

For complete information on ISErrorRefiner Configuration files, see the ISErrorRefiner PDF document.

ISErrorRefiner Configuration File Format

The ISErrorRefiner Configuration File is a text file containing two sections, which can occur in any order.

[Settings] Section

The Settings Section starts with the line [Settings], and contains the optional StopErrors entry.

StopErrors is used to identify errors that, when encountered, cause the severity of any and all other errors at the same level (i.e., loop/segment/element) to be set to zero (ignore); in effect, causing just the Stop Error to appear.

This results in fewer extraneous errors such as those generated by unused loops or segments, where the contents of those loops and segments contain additional errors that are unimportant when compared to the main error.

The StopErrors entry is a comma-separated list of one or more five-digit error numbers.

StopErrors=Error#{,Error#,Error#,...}

Example

StopErrors=11003,11302,11323,11324,10808,10811,10812,95171,95111,95236,95237,95238,95120,95121,95239,95240,95241,95242,95235,95211,95233

[Extended Warning Levels] Section

The Extended Warning Levels Section contains instructions about the modifications ISErrorRefiner is to make. Each line in this section corresponds to one Error/Location, and is structured as follows:

Error+Location=New Data

When ISErrorRefiner encounters an error (DTL) line in the input Detail File, it consults the table for an entry that has the same Error Number and Location (Loop, Segment, Element). If it finds a match, it replaces the fields in the DTL line with the data from the New Data portion of the instructions.

  • Error+Location
    Error+Location is comprised of four fields separated by the vertical bar character '|':
    • Field 1 = Error Number
    • Field 2 = Loop ID
    • Field 3 = Segment ID
    • Field 4 = Element Number (followed by a dash and sub-element number for Composite sub-elements)
  • New Data

    New Data is comprised of 12 fields separated by the comma character, and represents the data that is to replace various fields in the Input DTL record. Each field is optional, and should contain data only when that field is to be changed.

New Data Replacement Fields
Field # Description Valid Values
1 Severity Single digit 0 through 6
2 HIPAA Type Single digit 0 through 8
3 997 AK3-04 Code One or two character string
4 997 AK4-03 Code One or two character string
5 824 TED-01 Code One, two, or three character string
6 824 TED-02 Code One, two, or three character string
7 277 STC-01.02 Code One through five character string
8 999 IK3-04 Code One, two, or three character string
9 999 IK4-03 Code One, two, or three character string
10 Application Data String no longer than 20 characters
11 (Not Used)
12 Additional Replacement Values String of additional replacement fields separated by periods. See the Table Additional New Data Replacement Fields.
Additional New Data Replacement Fields
Field # Description Valid Values
1 (Not Used)
2 Loop ID 1 - 6 characters
3 Segment ID 1 - 4 characters
4 Element ID 1 - 4 characters
5 Composite ID 1 - 4 characters
6 Segment Position 1 - 10 digits
7 Element Position 1 - 6 digits or "none"
8 Sub-Element Position 1 - 2 digits or "none"
9 - 15 (Not Used)
16 Segment Ordinal Number 1 - 5 digits

Example

This example shows an ISErrorRefiner Configuration File entry.

41652|2330A|N4|4=3,,,,,,,,,,,......2.................
If a DTL record is found for Error 41652 in Loop 2330A on the fourth element of the N4 segment, then the following fields in the DTL record are changed:
  • Severity set to '3'
  • Element Position set to '2'.