ISErrorRefiner

Note: The ISErrorRefiner activity is for use by Centers for Medicare and Medicaid Services (CMS) customers utilizing data that has been validated by Instream to convert EDI to and from flat file format for compliance with the CEM requirements for electronic processing of claims. Purchase of the TIBCO Foresight® Instream® MAC Adapter is required to use ISErrorRefiner

Errors in Instream are assigned a severity, a HIPAA Type, various response codes, and more that apply to the error wherever it occurs. However, a customer may prefer that an error have different values for those parameters, depending on the location of the error within the EDI. ISErrorRefiner allows you to make changes to these parameters based on a configuration table of modification instructions.

For more details on ISErrorRefiner, refer to the Foresight® Instream® MAC Adapter ISErrorRefiner PDF document.

Example

An example use of ISErrorRefiner is as follows.

The following data is encountered during validation:

DTL 30 2330AN4 1343 27 4 1 1 7 41652 2 14482 8 7024 X7 21

The ISErrorRefiner configuration file specified in the input field "config_file" contains the following modification instructions:

If an Instream 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:

the element position set to ‘2’
the severity set to ‘3’

The modified Instream detail file (saved as specified in the input field "output_file") contains the changed severity and element position rather than the default settings.

The modified data appears as follows:

DTL 30 2330AN4 1343 27 2 1 1 7 41652 3 14482 8 7024 X7 21

General

The General tab contains the following fields.

Field	Literal Value/Module Property/Process Property?	Description
Name	No	User-defined name for the activity.
Input Mode	No	Specifies where the input data is stored. There are two options: File and Memory. Memory is normally the most efficient way of connecting, but large documents should be stored as files.
Output Mode	No	Specifies where the output data is stored. There are two options: File and Memory. Memory is normally the most efficient way of connecting, but large documents should be stored as files.

Description

The Description tab is used to provide a short description for the activity.

Input

The Input tab contains the following fields.

Field	Datatype	Description
instream_result	string	Specifies the file path and name of the Instream detail file to be modified. (Required) Note: This file is not changed by ISErrorRefiner.
config_file	string	Specifies the file path and name of the ISErrorRefiner configuration file containing the modification instructions that ISErrorRefiner is to use. (Required) (See ISErrorRefiner Configuration File for more information about the ISErrorRefiner Configuration Files.)
output_file	string	Specifies the file path and name for the output modified Instream detail file. (Required) It should not be the same as the Input file.

Output

The Output tab contains the following fields.

Field	Datatype	Description
instream_result_out	string	File path and name for the output modified Instream detail file.
return_code	string	Specifies the ISErrorRefiner return code. For example, 0 means ISErrorRefiner ran successfully, 2 means a specified file could not be found, and so on. Return codes are listed in Chapter 4 of the Foresight® Instream® MAC Adapter ISErrorRefiner PDF document

Fault

The Fault tab lists exceptions that are thrown by this activity.

Error Schema Element	Datatype	Description
msg	string	Error message description.
msgCode	string	The error code. It represents TIBCO ActiveMatrix BusinessWorks Plug-in for EDI and TIBCO Foresight errors. See Error Codes for details.