TPA-Parameter Setup File Contents

The section containing general options and items that map to command line options.

Specify the 864 description field.

Equivalent to the command line option: -dcd

Specify the 864 MIT description field.

Equivalent to the command line option: -dcm

Specify the 864 purpose code.

Equivalent to the command line option: -dcp

Causes 997s and 999s to have AK1 and AK9 segments only (no AK2/AK3/AK4/AK5). 

Equivalent to the command line option: -f997_group_only

Suppresses the ST03 in cases where the response document is greater than 4060.

Equivalent to the command line option: -f997_no_ST03

Produces a 277CA that includes patient-level errors (2000D).

Append the generated EDI data to the specified output file.

Equivalent to the command line option:  -a

Specify an Application Receiver ID (GS03) for the outbound GS.

Value is 2 to 15 alphanumeric characters; default is the first Application Sender ID (GS02) in the inbound EDI file

Equivalent to the command line option: -dar

Example: ApplicationReceiverID=PURCH1256

Specify an Application Sender ID (GS02) for the outbound GS.

Value is 2 to 15 alphanumeric characters; default is the first Application Receiver ID (GS03) in the inbound EDI file

Equivalent to the command line option: -das

Example: ApplicationSenderID=PURCH1256

Specify an Application Version (GS08) for the output EDI’s GS08. If the transaction has an ST03, this will be populated with the same value.

Value is a string of 1 to 12 characters; default is 004010

Equivalent to the command line option:  -dav

Example: ApplicationVersion=005010

Specify an optional configuration file (see Appendix D: Z-Parameter Setup File on page Appendix D: Z-Parameter Setup File. Indicates the configuration files ErrMsgTrans.txt and ErrRespXref.txt are located in the specified directory.

Do not use with UseBaseroot.

Equivalent to the command line options: -z and -cd

Example: ConfigFile=c:\configs\RG824config.ini

Specifies a contact phone number, which is needed for L2 report trailers.

Equivalent to the command line option: - dcc

Specifies the contents of the custom report; only use if GenerateCustomReport is enabled.

Value must be 0, 1, 2, or 3; default is 1.

Equivalent to the command line option: -te

Specifies which error types are included in the report.

Equivalent to the command line option:  -tel

Example: CustomReportErrorTypes=123

Specifies which severity levels are included in the report.

Equivalent to the command line option: -tev

Example: CustomReportSeverityLevels=34

Path to a custom report template; only use if GenerateCustomReport is enabled.

Equivalent to the command line option: -tpl

Should Response Generator remove zero length output files?

Equivalent to the command line option: -nz

Examples:

DeleteZeroLengthResults=true

DeleteZeroLengthResults=false

Create a 277 that conforms to the 3070x070A standard.

Equivalent to the command line option:  -fdo277x070

Create a 277 that conforms to the 4050x167 standard.

Equivalent to the command line option:  -fdo277x167

Create an 824 that conforms to the 824x166 standard.

Equivalent to the command line option:  -fdo824x166

Create an 824 that conforms to the 824x186 standard.

Equivalent to the command line option:  -fdo824x186

This creates an 864 wrapper around a custom report.

Equivalent to the command line option:  -fdo864Wrapper

If set to true (1), a non-errata version of the 999 is generated. If set to false (0), an errata version is generated.

Equivalent to the command line option: -fdo999ne

For warnings (severity of 2), generate:

• AK3/AK4 values in 997s

• IK3/IK4 values in 999s

Equivalent to the command line option:  -fak3

Should Response Generator use E in the 997  AK901 to indicate Accepted with Errors when all AK501s generated for the functional group are set to A or E?

(Default behavior is the AK901 contained an A under these circumstances.)

Equivalent to the command line option: - fAK901E

Example: DoAK901E=1

If set to true, ISA, GS, and ST1 control numbers are passed through to the response document.

Equivalent to the command line option: 
-fdo_ctrlnum_passthrough

Passes GS06 through to the 864 and the MIT01.

Equivalent to the command line option:  -fdo_gs06_passthrough

For created 997, GS08 mirrors the GS08 of the source document.

This option is incompatible with the -dav (ApplicationVersion) option, and Response Generator fails if both are set.

Equivalent to the command line option:  -fdo_gs08_passthrough

If set to true (1), an 824 is generated that conforms to either the 824x166 or 824x186 standard, based upon the version of the source document.

Equivalent to the command line option: -fdo_HIPAA_824

If set to true (1), 277CA, 277H, and 277U responses will have one loop per provider, even if the incoming document had multiple 2000A loops for a single provider. Default is false (0).

Equivalent to the command line option:  -fdo_loop_rollup.

Note that setting this value to true (1) can cause differences in the interpretation of bad claims between the response document and DocSplitter/Importer.

If set to any of these, EDI277FilePath creates a 277CA:

EDI277CA=1
EDI277CA=true
EDI277CA=yes
EDI277CA=on

Default is for EDI277FilePath to create a 277U

Requires EDI277FilePath

Equivalent to the command line option:  -0277 with -fca277

Output a 277

By default, this creates a 277U. To create a 277CA, see EDI277CA

Equivalent to the command line option: -o277

Example: EDI277FilePath=C:\Output\*_277.txt

Output an 824

Equivalent to the command line option: -o824

Example: EDI824FilePath=C:\Output\*824.edi

Output a 997

Equivalent to the command line options: -o997 and -octl

Example: EDI997FilePath=C:\Output\

Output a 999

Equivalent to the command line option: -o999

Example: EDI999FilePath=C:\Output\

Specify a new UNH02.05 association agency code value.

Equivalent to the command line option:  -dea

Specify a new UNH02.04 controlling agency code value.

Equivalent to the command line option:  -dec

Generate a UNA segment in the EDIFACT CONTRL response.

Equivalent to the command line option:  -fedifact_gen_una

Cause EDIFACT CONTRL document to generate a response for the status of the Interchange only.

Equivalent to the command line option:  -fedifact_ic_only

Suppress generation of UCM segments in EDIFACT CONTRL documents.

Equivalent to the command line option:  -fedifact_no_ucm

Specify a new UNH02.03 release number value. 

Equivalent to the command line option:  -der

Specify a new UNH02.02 version number value.

Equivalent to the command line option:  -dev

Output a TA1

Equivalent to the command line option: -oTA1

Specify the element delimiter for the output files.

This can be an actual character surrounded by double quotes, or an ASCII number representing the character.

An ASCII number may be hexadecimal, by starting the number with 0x, octal by starting the number with a zero or decimal.

The default delimiter is *.

Equivalent to the command line option: -l

Examples:
ElementDelimiter=”^”

If this is set to 1, the generated 277u will use the value in a ZZKPA custom record that has been inserted into the validation detail file via business rules. Typically, the business rule that generates this record would be in the 837’s claim loop. It will put it in the 277u’s REF02 at 2200D or 2200E (REF01=1K).

If the detail file does not contain the ZZKPA record, this setting is ignored.

Equivalent to the command line option: -fno_AIS

Example: GenerateAIS=1

Output a custom report; requires other settings too

Equivalent to the command line option: -otext

Example: ElementDeGenerateCustomReport=C:\Output\textout.txt

Specify whether to generate interchange and functional groups (the TA1 response does not need functional groups).

Value is True or False; default is True.

Equivalent to the command line option: -ge

Example:

GenerateInterchangeAndFunctionalGroup=false

This determines the conditions under which a TA1 segment will be created. See gTA1 Command section.

Value is 0, 1, 2, 3, or 4; default is 0.

Equivalent to the command line option: -gTA1

Example: GenTA1=3

If set to true (1), the format of the GS05 is set to four characters (HHMM). If set to false (0), the default value is used (HHMMSS).

Equivalent to the command line option: -fdo_gs05_hhmm

Example: GS05_HHMM=1

If set to true (1), the format of the GS05 is set to six characters (HHMMSS). If set to false (0) and no other format is specified, this remains the default value.

To use a different format, set one of these options to true (1): GS05_HHMM, GS05_HHMMSSD, or GS05_HHMMSSDD

Equivalent to the command line option: -fdo_gs05_hhmmss

Example: GS05_HHMMSS=1

If set to true (1), the format of the GS05 is set to seven characters (HHMM). If set to false (0), the default value is used (HHMMSSD).

Equivalent to the command line option: -fdo_gs05_ hhmmssd

Example: GS05_HHMMSSD=1

If set to true (1), the format of the GS05 is set to eight characters (HHMMSSDD). If set to false (0), the default value is used (HHMMSSD).

Equivalent to the command line option: -fdo_gs05_hhmmssdd

Example: GS05_HHMMSSDD=1

Allows you to specify a GS Control Number. This user-specified GS Control Number should be thought of as a GS-level trace number; it is not the same as the GS06 number.

Equivalent to the command line option: -dcg<gs control number value>

InterchangeControlControlPath allows you to use a file to specify a starting interchange control number. This method allows Response Generator to “remember” the last interchange control number used and increment by one each time it encounters an ISA, no matter how many files are processed. There is no maximum number.

Example:

File 1 is run through Response Generator – The first ISA within the file is assigned interchange control number 000000001, the second is assigned 000000002, the third is assigned 000000003.

File 2 is run through Response Generator – Response Generator continues the numbering sequence that began with File 1. The first ISA within the file is assigned interchange control number 000000004, the second is assigned 000000005, the third is assigned 000000006, and so on.

To use this setting:

1. Deactivate/comment out the following settings by adding a colon (:) to the beginning of each line:

: InterchangeControlNumberStart=1
: InterchangeControlNumberMin=1
: InterchangeControlNumberMax=100
: InterchangeControlNumberStart

2. Activate InterchangeControlControlPath by either

(a) typing the entry (if the setting does not exist in the file), or 
(b) deleting the colon (:) in front of the entry.

3. Specify the path to a filename that contains a 9-digit starting interchange control number, such as:

000000001
000000500
000002000

Equivalent to the command line option: -dic <filename>

Example:
InterchangeControlControlPath=my_control
_filename.txt

Where the file my_control_filename.txt contains a nine-digit number such as 000000100.

Specify the maximum interchange control number. When the maximum number is reached, the interchange control number count will reset to the minimum interchange control number.

Requires use of InterchangeControlNumberMin parameter (see InterchangeControlNumberMin).

Default = 999999999.

Equivalent to the command line option: -dic

Example: InterchangeControlNumberMax=100

Specify the minimum interchange control number.

Requires use of InterchangeControlNumberMax parameter.

The interchange control number count will start with the number specified with this parameter and increment by one until the maximum number is reached (see InterchangeControlNumberMax).

Default = 000000001.

Equivalent to the command line option: -dic

Example: InterchangeControlNumberMin=10

InterchangeControlNumberStart allows you to specify a 9-digit starting interchange control number to be used each time Response Generator runs a file. This value should be between InterchangeControlNumberMin and InterchangeControlNumberMax, if they are specified.

Examples:
000000001
000000500
000002000

Numbering increments within that file only and numbering restarts with each file if multiple files are processed.

Example:

File 1 is run through Response Generator – The first ISA within the file is assigned interchange control number 000000001, the second is assigned 000000002, and the third is assigned 000000003.

File 2 is run through Response Generator – the count is restarted using the specified starting interchange control number. The first ISA within the file is assigned interchange control number 000000001, the second is assigned 000000002, the third is assigned 000000003, and so on.

: InterchangeControlControlPath

Equivalent to the command line option:  -dic <starting ICN>

Example: InterchangeControlNumberStart=000000010

Specify an interchange receiver ID to use in the outbound ISA08.

Value is 2 to 15 alphanumeric characters; If less than 15 characters, it will be automatically padded on the right with spaces to make it 15 characters

Default is the Interchange Receiver ID (ISA08) in the validation detail report

Equivalent to the command line option: -dir

Example: InterchangeReceiverID=PARTNERCORP

Sets a flag in the ISA14 element to notify the receiver that the sender is expecting a TA1 to be returned for the document.

Value is on or off; default is off.

If value is on, the ISA14 is set to '1', indicating the sender is requesting a TA1 be returned for the document.

If value is off, the ISA14 is set to '0', indicating the sender is not requesting a TA1 for the document. 

Equivalent to the command line option:  -diq

Example: InterchangeResponseRequested=ON

Specify an interchange sender ID to use in the outbound ISA06.

Value is 2 to 15 alphanumeric characters; if less than 15, it is automatically padded on the right with spaces to make it 15 characters

Default is the Interchange Sender ID (ISA06) in the validation detail report

Equivalent to the command line option: -dis

Example: InterchangeSenderID=KAVERCORP

Specify the interchange usage indicator (ISA15) for the outbound ISA.

Value is I (Information), P (production), T (testing) or X (use the value from the input file’s ISA15); default is P.

Equivalent to the command line option:  -diu

Example: InterchangeUsageIndicator=P

If LenientAK501= true, yes, on, or 1, then a 997 or 999 AK501 and AK509 can contain only A or E:

• If there are no errors, then the AK501 = A.

• If there are errors, regardless of type or number of claims, then the AK501 = E.

All other settings cause LenientAK501 to be false.

Equivalent to the command line option:  -k

Return 100 (success) even when a response document cannot be created from the source (e.g., as a 277 from a non-837).

Equivalent to the command line option:  -floose_src_check

Should a new-line sequence follow each segment delimiter in the EDI output?

Value is True or False; default is True.

Equivalent to the command line option:  -n

Example: NewLines=true

Suppress output of the 997 AK103 segment.

By default, AK103s are created if the source document is version 4060 or greater or if a 999 is requested.

If this switch is present (NoAK103 = true), AK103 output is suppressed.

Value is True or False; default is False.

Equivalent to the command line option:  -fno_AK103

Turns off functional group (UNG) data in EDIFACT CONTRL responses.

Equivalent to the command line option:  -no_ung

Specifies the original filename, which is needed for L2 report headers.

Equivalent to the command line option:  -dco<original filename>

Allows overwriting of the EDI output file without prompting (if it already exists). This option cannot be used if the Append option is set.

If true, existing output files are overwritten.

Example: OverwriteOK=true

Equivalent to the command line option:  -y

Should partial functional group acceptance be allowed when generating a 997 or 824 response?

If not, when any transaction is rejected, the entire functional group is rejected.

Value is True or False; default is True.

Default (True) is to partially accept a functional group if any transaction set is accepted, and reject a functional group only if all transaction sets are rejected.

Equivalent to the command line option:  -np

Example:

PartialFunctionalGroupAcceptance=true

Should partial transaction set acceptance be allowed when generating a 997 or 999 response?

• If omitted from TPA Setup file: No. The transaction set is rejected if errors are found; this is equivalent to not including the -pt switch on the command line.

• If set to FALSE or false: No. The transaction set is rejected if errors are found; this is equivalent to not including the -pt switch on the command line.

• If set to p: Yes. The transaction set is accepted with errors and a “P” is placed in the AK501; this is equivalent to the command line option: -pt p

  Example:

  PartialTransactionSetAcceptance="p"

• If set to anything else (true, 0, 1, etc.): Yes. The transaction set is accepted with errors; this is equivalent to the command line option: -pt

  Examples:

  PartialTransactionSetAcceptance ="1"

  PartialTransactionSetAcceptance ="on"

Should partial transaction set acceptance be allowed when generating an 824 response?

This parameter is useful when you are using Docsplitter.

If omitted, default behavior is used: transaction set is rejected if there are any errors.

If set to anything (true, false, 0, 1, etc.), it is equivalent to the command line option:  -pt824

Example:

PartialTransactionSetAcceptance824 ="true"

Set the error severity that will result in a rejected transaction set.

Value is 0, 1, 2, 3, 4, 5, or 6; default is 3.

Equivalent to the command line option:  -er

Example: RejectErrorSeverity=2

Specify the repetition separator for the output files.

This can be an actual character surrounded by double quotes, or an ASCII number representing the character.

An ASCII number may be hexadecimal, by starting the number with 0x, or octal by starting the number with a zero, or decimal.

The default separator is ^.

Equivalent to the command line option: -l

Example:

RepetitionSeparator=”^”
RepetitionSeparator=94     (Decimal value)

RepetitionSeparator=0x5E (Hexadecimal value)

RepetitionSeparator=0136  (Octal value)

Specify the segment delimiter for the output files.

This can be an actual character surrounded by double quotes, or an ASCII number representing the character.

An ASCII number may be hexadecimal, by starting the number with 0x, octal by starting the number with a zero or decimal. If a new-line sequence is to be used as a segment terminator, set the Segment Delimiter to zero (0).

The default delimiter is ~.

Equivalent to the command line option: -l

Example:

SegmentDelimiter=”!”

SegmentDelimiter=42 (Decimal value)

SegmentDelimiter=0x2A (Hexadecimal value)

SegmentDelimiter=052 (Octal value)

Specify the severity levels to go into the report. By default, all severity levels go in the report.

Equivalent to the command line option: -tev

Example (put claims with errors of severity 3, 4, and 5 in the report):  SeveritylevelFilter=345

Specify the error types to go into the report. By default, all error types go in the report.

Equivalent to the command line option: -te1

Example (put claims with errors of type 1, 2, 3, and 7 in the report):  SeveritylevelFilter=1237

Create 824s and 277s from clean documents.

Equivalent to the command line option:  -fsa

Specify a starting group control number (GS06) for the outbound GS.

Value is a number greater than 0 and no more than 999999999; default is 1

This value automatically increments with each group until it reaches 999999999 or is reset with another StartingGS06 or
-dac

Equivalent to the command line option: -dac

Example: StartingGS06=1000

Specify a starting transaction set control number (ST02) for the output EDI file.

Value is a number greater than 0; default is 1

Equivalent to the command line option: -c

Example: StartingST02=500

Name of a STC override file, if used. See  on page  .

Example STCTablePath=C:\setup\STCoverride.txt

Specifies table to STC override file for 277C. See  on page  .

Equivalent to the command line option:  -stc

Should strict 997 or 999 response processing be used? Strict means:

• 997s and 999s will only show error types 1 and 2

• 824s will only show application error types (usually 3 -7)

By default, if only one of these types of output transactions are generated:

997s, 999s, or 824s

… then ALL errors, regardless of type, are put in the one type generated.

Equivalent to the command line option: -s

Example: Strict997

Specify the subelement delimiter for the output files.

This can be an actual character surrounded by double quotes, or an ASCII number representing the character.

An ASCII number may be hexadecimal, by starting the number with 0x, octal by starting the number with a zero or decimal.

The default delimiter is : (a colon).

Equivalent to the command line option: -l

Example: SubelementDelimiter=”#”

Specifies where to find configuration files ErrMsgTrans.txt and ErrRespXref.txt. Do not use with ConfigFile.

Equivalent to the command line option:  -u

Generates a 999 if available according to the source version, overriding any previously specified output.

Equivalent to the command line option:  -fuse_highest_99x

If present, the GS05 is set to four characters (HHMM), instead of the default six (HHMMSS).

Equivalent to the command line option:  -fuseshortGS05

Use the source document’s delimiters for the response document delimiters. (Requires the GEN 10223 record to be present.)

Equivalent to the command line option:  -lsource

Set the output verbosity level:

0 = No Output,

1 = Errors Only

2 = Warnings and Errors (default)

3 = Info, Warnings

9 = Debug (lots of output)

Equivalent to the command line option: -v

Example: Verbosity=3

Displays Response Generator version. Do not use with other options.

Equivalent to the command line option:  -version

Causes the GS08 for the created 997 to mirror the GS08 of the source document.

Equivalent to the command line option: -fver_pass

Set the error severity that will result in an 'Accepted but Errors were Noted' acknowledgement for the transaction set.

Value is 0, 1, 2, 3, 4, 5, or 6; default is 2.

Equivalent to the command line option: -ew

Example: WarnErrorSeverity=2

When generating a 277CA, causes the DTL record's more descriptive error text (EMSG) to be written into the STC12 when A3:21 is encountered.

WriteSTC12=true (1) means the feature is enabled.

WriteSTC12=false (0) means the feature is disabled (default)

Example: WriteSC12="true"

Equivalent to the command line option:  -fWriteSTC12