Validate and Split the Tutorial File

1. Go to the DemoData directory of Instream and look at the EDI data in 837I_4010_H_ErrorEvenClms.txt.

   This contains one 837I transaction set with one provider, one subscriber, and 10 claims. The claims are numbered from 1 to 10 and the even-numbered claims have errors.

2. Validate and split the data.

3. Go to the Scripts directory of Instream and look at the contents of V_DS_837I_4010_EasyEdit.sh. Execute this script by typing its name.

   This script first runs Instream validation with GuidelinePlus PDSA837I, and then runs Docsplitter to separate the invalid data from the valid data.

   When the script finishes, you should see return codes and the message Docsplitter was successful.

   See pages C++, C# and Java Application Program Interface and Annotated Example Script Files for details about the script file format.

4. Look at the following files created in the Output directory of Instream.

   Files created by the validation process (see the TIB_fsp-instream_<n.n>_usersguide.pdf for file details):

   • Summary_837I_4010_H_ErrorEvenClms_Results.txt
     Validation summary report.

   • 837I_4010_H_ErrorEvenClms_Results.txt
     Validation detail results file. Serves as input to Docsplitter.

   Files created by Docsplitter:

   • 837I_4010_H_ErrorEvenClms_Invalid.txt
     EDI file containing the 5 invalid claims.

   • 837I_4010_H_ErrorEvenClms_Report.xml
     EDI report providing information about each claim, including whether it passed or failed. For XML report format, see page XML Report File Formats. For suggestions on how to view the Docsplitter XML report in Unix, see page Viewing the XML Report in Unix.

   • 837I_4010_H_ErrorEvenClms_Valid.txt
     EDI file containing the 5 valid claims.

Top