Index of TIBCO Foresight Validation Demo Files

Index of TIBCO Foresight Validation Demo Files
TIBCO Foresight® HIPAA Validator® Desktop
and TIBCO Foresight® Instream®
Index of TIBCO Foresight Validation Demo Files
Software Release 8.5.0
July 2015
Two-second advantage®
Important Information
SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR
PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY
OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.
USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE
LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR
INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER
LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR
USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.
This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written
authorization of TIBCO Software Inc.
TIBCO, Two-Second Advantage, TIBCO Foresight EDISIM, TIBCO Foresight HIPAA Validator Desktop, TIBCO Foresight Instream, and TIBCO Foresight Transaction Insight are either registered
trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.
Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform Enterprise Edition (J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks of
Oracle Corporation in the U.S. and other countries.
All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only.
THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE
RELEASED AT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.
THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS.
CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC.
MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.
THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE,
INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.
Copyright © 2010-2015 TIBCO Software Inc. ALL RIGHTS RESERVED.
TIBCO Software Inc. Confidential Information
General Contact Information
TIBCO Software Inc., Foresight Group
655 Metro Place South
Suite 900
Dublin OH 43017
Phone: (614) 791-1600
Fax: (614) 791-1609
Technical Support
E-mail: [email protected]
Web: https://support.tibco.com
(Note: Entry to this site requires a username and password. If you do not have one, you can request one. You must have a valid maintenance or support contract to use this site.)
Contents
This document lists the contents of TIBCO Foresight® Instream®’s Database and Scripts
directories, and the TIBCO Foresight® HIPAA Validator® Desktop Database directory.
Table Key ......................................................................................................................................... 3
Instream Scripts Directory ................................................................................................................ 3
Instream Discontinued Scripts ................................................................................................. 17
Instream and Desktop DemoData Directories ............................................................................... 19
Discontinued DemoData Files ................................................................................................. 28
Instream and Desktop Database Directories ................................................................................. 30
Demo File Index
Page 1
7/6/2015
Demo File Index
Page 2
7/6/2015
Table Key
Key to columns in table below:
V
=
Demo show validation
DS
=
Demo shows DocSplitter
RG
=
Demo shows Response Generator
Other =
Other features demonstrated by demo file
Instream Scripts Directory
Execute these files to try out features of Instream. They use sample data files in the DemoData directory.
V
DS
RG
Other
Filename
(.bat for Windows, .sh for UNIX)
Contents
Ref #
H
DocSplitterReport.xsd
DocSplitterReportPlus.xsd
Schemas for DocSplitter XML reports. This is for your
reference only and can be deleted with no ill effects. A copy
is automatically put in the Output directory when certain
scripts are run.
4
Gen275 java
program
H
Generate275
Creates a 275 with attachment in the BIN02 from a DDE
®
®
created by TIBCO Foresight Transaction Insight 's 275
Attachments page and an attachment file uploaded by that
same page. The attachments are in Instream’s
DemoData\Gen275 directory.
6
GuideMerge
H
GuidelineMergeSample
Sample command line that runs GuideMerge.exe to merge a
company and a HIPAA guideline. Edit it to use your paths
and guideline names. See GuideMerge.pdf.
7

ISErrors
H
ISErrors
ISErrors-noconfig
Use ISErrors to see if ISerror_835_BadResults.dtl contains
one or more errors. See ISErrors.pdf.
8

Shuffler
H
Run_Shuffler_only_demo
Installed with Shuffler.
Translator
H
T_837I_4010_to_XML_and_back
Uses Translator to translate between EDI and XML, both
directions. This is installed with Translator.
32
Translator
H
T_837I_5010_to_flat_and_back
Uses Translator to translate between EDI and flat file, both
directions. This is installed with Translator.
33

Demo File Index
Format
(see *)
Page 3
7/6/2015
Instream Scripts Directory
Execute these files to try out features of Instream. They use sample data files in the DemoData directory.
V
DS
RG
Other
Filename
(.bat for Windows, .sh for UNIX)
Contents
Ref #
X12
TPARouter_810_5040
Uses TPARouter to move files with sender TOPCAT to a
directory called TOPCAT under DemoData. The config file is
TPARouter_Sample_X12.cfg in DemoData.
The two files being considered for routing are:
- 810_5040_X_1.txt (which should be moved)
- 850_4010_X_1.txt (which should NOT be moved)
34

X12
XML
V_275_4050_BinSeg
Replaces XML_275
Validates a 275 with a BIN segment containing XML. It
validates all segments with an EDI guideline, and uses an
XML guideline to validate the BIN segment.
Notice the –xg parameter that specifies the XML guideline as
well as the usual -g parameter that specifies the EDI
guideline.
90

H
V_278RQ_5010_1
Validates 278Q_5010_1.txt, a small 278 request.
95

H
V_278RP_5010_1
Validates 278R_5010_Clean.txt, a small 278 response.
96

X12
V_810_5040_1
Validates an X12 Invoice, 810_5040_X_1.txt, in Instream’s
DemoData directory.
36

H
V_835_4010_EasyEdit
Validates 835_4010_H_6CAS.txt.
13

TPA
V_835_4010_TPA
Demonstrates partner automation, where the correct
guideline is automatically selected based on values in a CSV
file. It validates 835_4010_H_6CAS.txt.
37

H
V_835_4010_xml_EasyEdit
Validates 835_4010_H_6CAS.txt and delivers validation
results in an XML report.
14

H
V_837I_4010_1
Validates 837I_4010_H_ErrorEvenClms.txt in Instream’s
DemoData directory, using a simple command line.
38
H
V_837I_4010_EasyEdit
Validates 837I_4010_H_ErrorEvenClms.txt
It is used in a tutorial in
InStreamValidationTechnicalManual.pdf.
18
TPARouter


Demo File Index
Format
(see *)
Page 4
7/6/2015
Instream Scripts Directory
Execute these files to try out features of Instream. They use sample data files in the DemoData directory.
V
DS
RG
Other

Format
(see *)
H


Rule processing
H
Filename
(.bat for Windows, .sh for UNIX)
Contents
Ref #
V_837I_4010_noData
Replaces RunNoData
Demonstrates the RunNoData business rule, which is
attached to the 2000A CUR segment in the guideline
NO_DATA. It displays a message if the EDI does not contain
a CUR segment.
16
V_837I_5010_1
Validates 837I_5010_H_errorTable1.txt in Instream’s
DemoData directory, using a simple command line.
39
V_837P_5010_ProcessingOrderOfRules
Validates 837P_5010_H_2Sub_BadCLM02.txt to show the
order in which business rules process. It has rules in the
segment dictionary, exit rules on the ST segment that run in
various places, and regular business rules.
Copy 837P_5010_ProcessingOrder.std to Instream's
Database directory before running this demo for the first time.
58
V_850_4010_1
Validates 850_4010_X_1.txt, in Instream’s DemoData
directory, using a simple command line.
40

X12

H
V_997_4010_TA1
Validates 997_4010_TA1.txt, which demonstrates TA1 and
997 handling.
12

UN
V_CUSCAR_D93A
Validates CUSCAR_D93A.txt, which contains EDIFACT 93A
data, using a simple command line.
41
V_DS_275_5010_Binary
Validates and splits 275_5010_H_binary.txt, which contains
two 275s with attachments. The first 275 is bad and second
one is good.
42
X12
V_DS_810_5040_1
Validates and splits 810_5040_X_2intchg.txt, which contains
two interchanges. The first is good and the second has an
error.
43
UN
V_DS_835_4010_Basic_EasyEdit
Validates and splits 835_4010_H_2CLP.txt, a 4010 835 with
two CLP groups. The second one has an error in the NM1.
44




Binary attach.
H


H
V_DS_837I_4010_Basic_XMLreport
Validates and splits 837I_4010_H_5provider.txt. Claim 7 has
an error.
46


H
V_DS_837I_4010_CommandLineOnly
Validates and splits 837I_4010_H_ErrorEvenClms.txt with a
basic command line.
20
Demo File Index
Page 5
7/6/2015
Instream Scripts Directory
Execute these files to try out features of Instream. They use sample data files in the DemoData directory.
V
DS



Filename
(.bat for Windows, .sh for UNIX)
Contents
Ref #
content based
splitting
V_DS_837I_4010_ContentSplit
Replaces CBS_auto_short
Demonstrates automatic content-based splitting as described
in DocumentSplitterTechnicalManual.pdf. It splits
837I_4010_H_5provider.txt into valid and invalid files for each
provider and uses Content_Based_Split_Auto_Setup.ini for
its Docsplitter setup file. The four claims for PROVIDER TWO
will be split between a valid file and an invalid file. The
guideline PCBS creates z-records for each provider, so they
can each get their own output file(s).
1

content based
splitting
V_DS_837I_4010_ContentSplit1
Replaces CBS_short
Demonstrates content-based splitting for two providers. It
splits 837I_4010_H_5provider.txt into valid and invalid
providers for the providers listed in
Content_Based_SplitMap_Setup.ini, its Docsplitter setup file.
The guideline PCBS creates z-records for each provider, so
the ones listed in the INI file can get their own output file(s).
2


return code
H
V_DS_837I_4010_EasyEdit
Replaces RunTutorial837IA
Validates and splits 837I_4010_H_ErrorEvenClms. It also
demonstrates how to display a Docsplitter return code.
It generates a valid EDI file that contains the odd-numbered
claims (which are all valid) and an invalid EDI file that
contains the even-numbered claims (which are all invalid).
It is used in the tutorial in
InStreamValidationTechnicalManual.pdf.
19


content based
splitting
H
V_DS_837I_4010_NoContentSplit
Replaces No_CBS_short
Validates 837I_4010_H_5provider.txt without content-based
splitting. You can compare the results to those from
V_DS_837I_4010_ContentSplit and
V_DS_837I_4010_ContentSplit1.
9
Demo File Index
RG
Other
Format
(see *)
Page 6
7/6/2015
Instream Scripts Directory
Execute these files to try out features of Instream. They use sample data files in the DemoData directory.
V
DS


split point
grouping


Split and Swap


Partner Auto.










Demo File Index
RG


Other
Format
(see *)
Filename
(.bat for Windows, .sh for UNIX)
Contents
Ref #
V_DS_837I_4010_SetupFile_DelimReport
Validates 837I_4010_H_6claims.txt in Instream's DemoData
directory and then uses Document Splitter to split the valid
and invalid EDI, and to create a delimited report.
Docsplitter uses setup file SplitPointGrouping_Setup.ini in
Instream's DemoData directory to only allow two split units
per output file, and to delete any empty output files.
31
H
V_DS_837I_4010_Swap
Demonstrates Docsplitter’s split-and-swap capabilities. It runs
Docsplitter to split 837I_4010_H_2Interchanges.txt into valid
and invalid files and then automatically changes data in the
output files according to Dataswapper rules in the guideline.
Docsplitter uses the Dataswapper setup file
DataSwap_SplitAndSwap.ini.
53
H
V_DS_837I_4010_TPA
Validates 837I_4010_H_6claims and then runs Docsplitter
with partner automation to pick a Docsplitter INI file. Claims
2-4 are invalid. Be sure your $Dir.ini’s
PARTNERAUTOMATION line points to
SampleTPA_DS_RG.csv in DemoData and that the paths in
TPA_DocSplitter.ini are correct.
48
H
V_DS_837I_5010_999split
Demonstrates Docsplitter using 999 splitting.
77
H
V_DS_837I_5010_Basic
Validates 837I_4010_H_ErrorEvenClms.txt and splits it into
valid and invalid files.
49
H
V_DS_837P_4010_997split
Demonstrates Docsplitter using 997 splitting.
76
UN
V_DS_CUSCAR_D93A_UNB
Validates EDIFACT D93A data in CUSCAR_D93A.txt, using
guideline MYCUSCAR_D93A that creates SVALU records at
the UNH, UNG, and UNB. It then uses Document Builder to
create a valid and an invalid file by splitting at the UNB. The
split is set up in SplitPointUNB.ini, which is in Instream’s
DemoData directory.
50
UN
V_DS_CUSCAR_D93A_UNH
Validates EDIFACT D93A data in CUSCAR_D93A.txt, using
guideline MYCUSCAR_D93A that creates SVALU records at
the UNH, UNG, and UNB. It then uses Document Builder to
create a valid and an invalid file by splitting at the UNH.
51
Page 7
7/6/2015
Instream Scripts Directory
Execute these files to try out features of Instream. They use sample data files in the DemoData directory.
V
DS




RG
Other
Format
(see *)
FF
Split XML
XML
Filename
(.bat for Windows, .sh for UNIX)
Contents
Ref #
V_DS_FFdelim_vet
Validates and splits FF_Delim_2VetCustomer.txt, a delimited
flat file with two customers. One of the customers contains an
error. It uses delimited flat file guideline VETDELIM.
52
V_DS_XML_split_PO
Windows only.
Demonstrates validation and splitting of XML data. It
validates XML_PO_f_1error.xml (in DemoData) with guideline
XML_PO_F and then splits it into valid and invalid XML files
at the ORDERS element. There are 10 ORDERS, and the
last one is invalid. Setup file DocSplitter_XML.ini in
DemoData controls the splitting.
54

DataSwapper
H
V_Dswap_837I_4010_BHT06
Replaces DataSwapper837i
DataSwapper changes BHT-06 in
837I_4010_H_2Interchanges.txt to always be “CH” by using
guideline SUB1. The first BHT06 was CH and remains
unchanged. The second BHT06 was RP and is changed to
CH.
3

DataSwapper
Generate
FSUID business
rule
H
V_Dswap_837I_4010_FSUID_eachCLM
Replaces Unique_Claim_ID_837I
Demonstrates the Unique ID created by the GenerateFSUID
business rule. It uses guideline pfsuid.std, which contains a
GenerateFSUID business rule on the CLM segment. It uses
profile pfsuid.apf, which has UID=1 to activate the
GenerateFSUID business rule.
The script validates 837I_4010_H_6claims.txt and sends its
detail results file through DataSwapper. Dataswapper creates
a new EDI file and places an ACT segment (which normally
doesn’t occur in an 837) containing a unique ID right after
each CLM segment, like this:
35
CLM*1*100.00***11:A:1*N*A*N*A*********N**1~
ACT*fcf5cd0f-de20-11db-88de-915cc9ef8349~
Demo File Index
Page 8
7/6/2015
Instream Scripts Directory
Execute these files to try out features of Instream. They use sample data files in the DemoData directory.
V
DS
RG
Other
Format
(see *)
Filename
(.bat for Windows, .sh for UNIX)
Contents
Ref #

Partner Auto.
FF
V_FFdelim_CBTPA
Validates flat file FF_Delim_Customers.txt and uses contentbased trading partner automation to switch guidelines and
profiles whenever the data contains OH or MI in the address.
The guideline that controls this switching is
CustDELIM_BASE. It uses SampleTPA_FF_XML.csv in
Instream’s DemoData directory to select the profile for each
customer based on their state.
55

Flat file
validation
FF
V_FFdelim_vet
Replaces FlatFileDelim
Validates FF_Delim_1VetCustomer.txt, a delimited flat file,
using guideline VETDELIM.
5

Flat file
validation
FF
V_FF_fixed_oneRec
Validates FF_FL_OneRecordType_NoTag.txt, a flxed-length
flat file that has only one record type and no record tag, using
guideline FF_FL_NoTag_OneRec.
101
Split Interchg.
H
V_IntchgSplit_837I_5010_6intg_EasyEdit
Replaces RunInterchangeSplitterDemo1.bat
Uses InterchangeSplitter.exe to splits
837I_5010_H_6intg_clean.txt into separate interchanges.
The data contains 6 interchanges, each with one group and
one transaction set containing 2 subscribers. The first
subscriber in each has 2 subscriber claims and 2 patient
claims. The script creates a separate file for each
interchange.
15

Partner Auto.
T
V_INVOICES_TRADACOMS_TPA
Validates TRADACOMS file INVOICES_TRAD93_clean.txt
with partner automation using guideline Trad93.std.
56

NCPDP
N
V_NCPDP_51_BillRequest
Replaces RunNCPDP_trans_short
Simple command line that validates
NCPDP_BillRequest_51.txt.
92

TRADACOMS
V_Order_TRADACOMS_TPA
Validates TRADACOMS data with partner automation.
87
UN
V_ORDERS_D93A_UN_1
Validates an EDIFACT Purchase Order,
ORDERS_D93A_UN_1, in Instream’s DemoData directory.
57


HL7
HL7
V_ORUR01_HL7_Clean
Validates HL7_ORU_R01_Clean.txt, an HL7 file.
94

Pain
XML
V_pain.001.001.002_xml
Validates pain.001.001.02_BadBIC.xml, an XML file.
100
Demo File Index
Page 9
7/6/2015
Instream Scripts Directory
Execute these files to try out features of Instream. They use sample data files in the DemoData directory.
V
DS
RG
Other
Format
(see *)
Filename
(.bat for Windows, .sh for UNIX)
Contents
Ref #


H
V_RG_270_textrpt
Validates 270_4010_H_3InfoSrc_Clean.txt and uses
Response Generator to create a report describing errors in
rejected claims. This report format is controlled by
RGtemplate270.txt in Instream’s DemoData directory.
47


H
V_RG_277_4010_textrpt_all
Replaces Run277RG_short_textrpt_all
Validates 277_4010_H_2error.txt and then uses Response
Generator to create text report
277_4010_H_2error.txt_Textout_all.rpt in Instream’s Output
directory. This report includes all data and all report sections
possible in a 277 text report. This report format is controlled
by RGtemplate277all.txt in the DemoData directory.
60


H
V_RG_277_4010_textrpt_html
Replaces Run277RG_short_textrpt_h
Validates 277_4010_H_2error.txt in Instream’s DemoData
directory and uses Response Generator to create an html
report. This report format is controlled by
RGtemplate277_h.txt in Instream’s DemoData directory.
61


H
V_RG_277_4010_textrpt_vertical
Validates 277_4010_H_2error.txt and uses Response
Generator to create a vertically-formatted report. It uses
template RGtemplate277_t.txt in Instream’s DemoData
directory.
62


H
V_RG_834_4010_BigTextOut
Replaces V_RG_834_4010_BigTextOut
Validates 834_4010_H_2members.txt and uses Response
Generator to create a text report that shows almost all fields
possible in an 834 text report. It uses template
RGtemplate834A.txt in Instream’s DemoData directory.
10


H
V_RG_834_4010_TableOut
Replaces Run834RG_short_textrpt_tB
Validates 834_4010_H_2members.txt and uses Response
Generator to create a text report in table format. It uses
template RGtemplate834B.txt in Instream’s DemoData
directory.
11


H
V_RG_835_5010_textrpt_1
Validates 835_5010_H_3interchanges.txt and uses
Response Generator to create a text report describing errors.
It uses custom report template RGtemplate835_c.txt in
Instream’s DemoData directory.
63
Demo File Index
Custom reports
Page 10
7/6/2015
Instream Scripts Directory
Execute these files to try out features of Instream. They use sample data files in the DemoData directory.
V
DS
RG










Demo File Index
Other
custom text
report
custom text
report in
columns
custom text
report
Format
(see *)
Filename
(.bat for Windows, .sh for UNIX)
Contents
Ref #
H
V_RG_837I_4010_277_824_997_text
Replaces RunRespGen837IDemo
Validates 837I_4010_H_6claims.txt and uses Response
Generator to create a 277, 997, 824, and a text report.
17
H
V_RG_837I_4010_997_COBA
Replaces RunTutorial837IRG_short_COBA
Validates 837I_4010_H_ErrorEvenClms.txt and uses
Response Generator to create a COBA claims dispute file.
Response Generator uses template
RGtemplate_COBA837.txt in Instream’s DemoData directory.
23
H
V_RG_837I_4010_ColumnsTextRpt
Replaces RunTutorial837IRG_short_textrpt_c
Validates 837I_4010_H_ErrorEvenClms.txt and uses
Response Generator to create a custom text report in
columns. It uses template RGtemplate837I_c.txt in Instream’s
DemoData directory.
It is used in a tutorial in
ResponseGeneratorTechnicalManual.pdf.
27
H
V_RG_837I_4010_CommandLineOnly
Windows only.
Validates 837I_4010_H_ErrorEvenClms.txt and uses
Response Generator to create 997 and 824 responses. It
contains only the command lines and the return codes.
It is used in a tutorial in
ResponseGeneratorTechnicalManual.pdf.
22
H
V_RG_837I_4010_HTML_lines
Replaces RunTutorial837IRG_short_textrpt_t
Validates 837I_4010_H_ErrorEvenClms.txt and uses
Response Generator to create a custom text report with table
lines. It uses template RGtemplate837I_hl.txt in Instream’s
DemoData directory.
93
Page 11
7/6/2015
Instream Scripts Directory
Execute these files to try out features of Instream. They use sample data files in the DemoData directory.
V
DS
RG
Other
Format
(see *)


custom text
report with logo
in HTML format






Demo File Index
Filename
(.bat for Windows, .sh for UNIX)
Contents
Ref #
H
V_RG_837I_4010_HTMLrpt
Replaces RunTutorial837IRG_short_textrpt_h
Validates 837I_4010_H_ErrorEvenClms.txt and uses
Response Generator to create a custom text report with a
logo in HTML format.
It uses the sample text report template
RGtemplate837P_h.txt and the logo file fslogo.gif in the
DemoData directory.
This script is used in a tutorial in
ResponseGeneratorTechnicalManual.pdf.
28
H
V_RG_837I_4010_Sep997_TA1.bat
Replaces RunTutorial837IRG_multi-997-TA1
Validates 837I_4010_H_6claims.txt and demonstrates how
Response Generator can put the TA1 into its own separate
file rather than in the same file as the 997. It also
demonstrates how to append an interchange count and group
count to an output filename by using #icount#- and #gcount#.
21
custom text
report
H
V_RG_837I_4010_SimpleTextRpt
Replaces RunTutorial837IRG_short_textrpt
Validates 837I_4010_H_ErrorEvenClms.txt and uses
Response Generator to create a custom text report.
It uses the sample text report template RGtemplate837P.txt
in Instream’s DemoData directory.
It is used in a tutorial in
ResponseGeneratorTechnicalManual.pdf.
24
custom text
report
H
V_RG_837I_4010_SimpleTextRpt_277_
824_997
Replaces RunTutorial837IRG_short_textrpt_997_277_824
Validates 837I_4010_H_ErrorEvenClms.txt and uses
Response Generator to create a custom text report, a 997, a
277, and an 824. It uses text report template
RGtemplate837I.txt in Instream’s DemoData directory.
26
Page 12
7/6/2015
Instream Scripts Directory
Execute these files to try out features of Instream. They use sample data files in the DemoData directory.
V
DS
RG
Other
Format
(see *)
Filename
(.bat for Windows, .sh for UNIX)
Contents
Ref #


custom text
report
H
V_RG_837I_4010_SimpleTextRpt_997
Replaces RunTutorial837IRG_short_textrpt_997
Validates 837I_4010_H_ErrorEvenClms.txt and uses
Response Generator to create a custom text report and a 997
response.
It uses text report template RGtemplate837I.txt in Instream’s
DemoData directory.
It is used in a tutorial in
ResponseGeneratorTechnicalManual.pdf.
25


custom text
report
H
V_RG_837I_4010_TextRptTotals
Replaces RunTutorial837IRG_short_textrpt_t1
Validates 837I_4010_H_ErrorEvenClms.txt in Instream’s
DemoData directory. Response Generator uses template
RGtemplate837I_t1.txt to create a text report that has
information by provider and by transaction set, including
totals.
30


Partner Auto.
H
V_RG_837I_4010_TPA
Validates 837I_4010_H_6claims.txt, and then uses Response
Generator with the INI file found identified within a trading
partner automation file. Both validation and Response
Generator use TPA lookup file SampleTPA_DS_RG.csv in
Instream’s DemoData directory.
64


H
V_RG_837I_5010_277CA
Validates 837I_5010_H_errorTable1.txt and uses Response
Generator to create a 277CA. It uses the Foresightdistributed guideline PDSA5010837I for validation. This
creates the SVALU records in the validation detail results file
that allows it to be used by Response Generator.
65


H
V_RG_837I_5010_999
Validates 837I_5010_H_errorTable1.txt and uses Response
Generator to create a 999. It uses the Foresight-distributed
guideline PDSA5010837I for validation. This creates the
SVALU records in the validation detail results file that allows
it to be used by Response Generator.
66


H
V_RG_837I_5010_999_CTX
This script is in the DemoData\CTX folder.
67
Demo File Index
Custom CTX
segments in a
5010 999
Validates a HIPAA 5010 837I (837I_5010_CTXtest.txt) and
uses Response Generator to create a 999 with custom CTX
(Context) segments as described in CTX.pdf. Also see
_readme_CTX.txt in Instream’s DemoData\CTX directory.
Page 13
7/6/2015
Instream Scripts Directory
Execute these files to try out features of Instream. They use sample data files in the DemoData directory.
V
DS
RG
Other
Format
(see *)
Filename
(.bat for Windows, .sh for UNIX)
Contents
Ref #
H
V_RG_837I_5010_z_param
Validates 837I_5010_H_errorTable1.txt and then uses
Response Generator with z-parameter setup file
ResponseGen_z.ini to control the use of RED segments in
the output 824s. Compare the two .824 files to see the effect
of the RespoonseGen_z.ini file.
69




Custom reports
H
V_RG_837P_4010_textrpt_1
Validates 837P_4010_2interchanges.txt, and uses Response
Generator with template RGtemplate_837any_t.txt to create a
text report describing errors in rejected claims.
71


Custom reports
H
V_RG_837P_4010_textrpt_ELOC
Validates 837P_4010_2interchanges.txt with ELOC.apf, and
uses Response Generator with template
RGtemplate837any_t_ELOC.txt to create a text report
describing errors in rejected claims. It shows how to use nontechnical wording in the error messages of type 1-2 errors.
72


Partner Auto.
H
V_RG_837P_4010_TPA
Validates 837P_4010_H_4subClean.txt and uses Response
Generator, both with partner automation file
SampleTPA_DS_RG.csv.
70


STC override
H
V_RG_837P_5010_277CA_ STCoverride
Validates 837P_5010_MedicareB.txt and uses Response
Generator and SampleSTCOverride_MedB.csv to specify the
values in the STC segment.
73


Response
Generator
Overrides in a
5010 999
V_RG_837P_5010_999_rgoverride
Validates 837P_5010_H_2Sub_BadCLM02.txt and uses
Response Generator to create a 999, using
Respgenoverride.apf to substitute a custom value when
creating certain segments in the detail file. See the Demo
Example section of Appendix H in
ResponseGeneratorTechnicalManual.pdf
68


Encoding
V_RG_837P_5010_ExtendedASCII
Validates 837P_5010_ExtendedASCII_GS03_N404.txt. Uses
Response Generator three times, to generate output in
ASCII, UTF8, and UTF16.
97


Encoding
V_RG_837P_5010_UTF8
Validates 837P_5010_UTF8_GS03_N404.txt. Uses
Response Generator three times, to generate output in UTF8,
UTF8 without BOM, and UTF16.
98
Demo File Index
Page 14
7/6/2015
Instream Scripts Directory
Execute these files to try out features of Instream. They use sample data files in the DemoData directory.
V
DS
RG
Other
Format
(see *)
Filename
(.bat for Windows, .sh for UNIX)
Contents
Ref #
V_RG_837P_5010_UTF16
Validates 837P_5010_UTF16_GS03_N404.txt. Uses
Response Generator three times, to generate output in UTF8,
UTF8 without BOM, and UTF16.
99




X12
V_RG_850_5050
Validates 850_5050_X.txt and uses Response Generator to
create a 997 and TA1. It uses guideline
RG_X12_Responses.std, which contains the necessary DSR
marks on the ISA, GS, and ST segments.
74


UN
V_RG_CUSCAR_D93A
Validates CUSCAR_D93A.txt, which contains three EDIFACT
D93A ORDERS messages. It uses guideline
MYCUSCAR_D93A that creates SVALU records at the UNH,
UNG, and UNB. It then uses Response Generator to create a
CONTRL response document.
75




Encoding
Partner Auto.
H
V_RG_DS_835_4010_TPA997split
Validates 835_4010_H_2CLP.txt, runs Response Generator
to generate a 997, and then uses the 997 as input for
Docsplitter, which runs with partner automation to pick a
Response Generator INI file. The partner automation lookup
file is SampleTPA_997split.csv in DemoData, which points to
TPA_DocSplitter1.ini. Check Instream paths in these two
files.
45
Dataswapper
H
V_Swap_850_5050
Validates 850_5050_X_onePO1.txt in Instream’s DemoData
directory, using guideline 850_5040_SwapST03. It then uses
the results file with Dataswapper to replace whatever is in the
ST03 with "KAVERCO" and create a new file with the
changed data.
78
V_XML_PO
Replaces XML_PO_f
Validates XML_PO_f.xml with XML guideline XML_PO_F.
91
ValidationHighlighter_5010_837I
Validates 837I_5010_H_errorTable1.txt and then uses
Validation Highlighter to create an HTML report of the
validation results.
Execute PDSA5010837I.exe in Instream’s LibraryLinks
directory before running the script for the first time. This
creates the Library Links (guideline help pages) for any
document validated with PDSA5010837I.
79


Demo File Index
XML
Validation
Highlighter
H
Page 15
7/6/2015
Instream Scripts Directory
Execute these files to try out features of Instream. They use sample data files in the DemoData directory.
V
DS
RG
Other
Format
(see *)
Filename
(.bat for Windows, .sh for UNIX)
Contents
Ref #

Validation
Highlighter
H
ValidationHighlighter_5050_850
Validates 850_5050_X.txt and then uses Validation
Highlighter to create an HTML report of the validation results.
80

Validation
Highlighter
H
ValidationHighlighter_837I
Validates 837I_4010_H_1clm_multiErrors.txt and then uses
Validation Highlighter to create an HTML report of the results.
81

Validation
Highlighter
X12
ValidationHighlighter_850
Validates 850_4010_X_1.txt and then uses Validation
Highlighter to create an HTML report of the validation results.
82

Validation
Highlighter
X12
ValidationHighlighter_856
Validates 856_4010_X_1.txt and then uses Validation
Highlighter to create an HTML report of the validation results.
83

Validation
Highlighter
UN
ValidationHighlighter_CUSCAR
Validates CUSCAR_D93A.txt and then uses Validation
Highlighter to create an HTML output report. If you have
previously run ValidationHighlighter_D93A_CreateLinks, the
output will have LibraryLinks (where errors become links to
the related segment in the guideline).
84

Validation
Highlighter
UN
ValidationHighlighter_D93A_CreateLinks
Runs TIBCO Foresight EDISIM ’s DocBuilder from the
command line to create LibraryLinks for D93A data validated
against the MYCUSCAR_D93A guideline. If you then run the
ValidationHighlighter_CUSCAR script, you should have
LibraryLinks in its output.
85

Validation
Highlighter
FF
ValidationHighlighter_FF_Delim
Validates delimited flat file FF_Delim_2Vetcustomer.txt and
then uses Validation Highlighter to create an HTML output
report.
86

Validation
Highlighter
XML
ValidationHighlighter_XML
Validates XML_PO_f.xml and then uses Validation
Highlighter to create an HTML report.
88
version
Displays information about the versions of the Instream
executables and the code tables.
89


Demo File Index

n/a
Page 16
®
®
7/6/2015
Instream Discontinued Scripts
Discontinued script
Use this instead …
CBS_auto_short
V_DS_837I_4010_ContentSplit
CBS_short
V_DS_837I_4010_ContentSplit1
DataSwapper837i
V_Dswap_837I_4010_BHT06
FlatFileDelim
V_FFdelim_vet.bat
No_CBS_short
V_DS_837I_4010_NoContentSplit
Run InStream Demo1_xmpout
V_835_4010_xml_EasyEdit
Run_997_TA1
V_997_4010_TA1
Run277RG_short_textrpt_all
V_RG_277_4010_textrpt_all
Run277RG_short_textrpt_h
V_RG_277_4010_textrpt_html
Run277RG_short_textrpt_t
V_RG_277_4010_textrpt_vertical
Run834RG_short_textrpt_tA
V_RG_834_4010_BigTextOut
Run834RG_short_textrpt_tB
V_RG_834_4010_TableOut
RunDocSplitter837IDemo
V_DS_837I_4010_Basic_XMLreport.
RunInStreamDemo1
V_835_4010_EasyEdit
RunInStreamDemo1PartnerAutomation
V_835_4010_TPA
RunInterchangeSplitterDemo1
V_IntchgSplit_837I_5010_6intg_EasyEdit
RunNCPDP_trans_short
V_NCPDP_51_BillRequest
RunNoData
V_837I_4010_noData
RunRespGen837IDemo
V_RG_837I_4010_277_824_997_text
RunTutorial837IA
V_DS_837I_4010_EasyEdit
RunTutorial837IRG_multi-997-TA1
V_RG_837I_4010_Sep997_TA1
RunTutorial837IRG_short
V_RG_837I_4010_CommandLineOnly
RunTutorial837IRG_short_COBA
V_RG_837I_4010_997_COBA
RunTutorial837IRG_short_textrpt
V_RG_837I_4010_SimpleTextRpt
RunTutorial837IRG_short_textrpt_997
V_RG_837I_4010_SimpleTextRpt_997
RunTutorial837IRG_short_textrpt_997_277_824
V_RG_837I_4010_SimpleTextRpt_277_824_997
Demo File Index
Page 17
7/6/2015
Instream Discontinued Scripts
Discontinued script
Use this instead …
RunTutorial837IRG_short_textrpt_c
V_RG_837I_4010_ColumnsTextRpt
RunTutorial837IRG_short_textrpt_h
V_RG_837I_4010_HTMLrpt
RunTutorial837IRG_short_textrpt_t
V_RG_837I_4010_HTML_lines
RunTutorial837IRG_short_textrpt_t1
V_RG_837I_4010_TextRptTotals
SplitPoint837IA
V_DS_837I_4010_SetupFile_DelimReport
Unique_Claim_ID_837I
V_Dswap_837I_4010_FSUID_eachCLM
V_DS_Swap_837I
V_DS_837I_4010_Swap
XML_275
V_275_4050_BinSeg
XML_PO_f
V_XML_PO
Demo File Index
Page 18
7/6/2015
Instream and Desktop DemoData Directories
Use these files to try out features of Instream and Desktop. Many of them are used by the demo scripts in Instream’s Scripts directory.
Filename
*
Instream
Desktop
Format
270_4010_H_3InfoSrc_Clean.txt


H
An error-free 270 with three Information Source levels, each with one dependent.
270_5010_H_BadReceiverID.txt


H
A 270 with one error in the Receiver NM1.
271_4010_H_2InfoSrc_Clean.txt


H
An error-free 271 with two Information Source levels. The first has a dependent and the
second does not.
271_5010_H_BadTaxCode.txt


H
A small 271 with one Information Source level. It has an erroneous taxonomy code.
275_4050_BinSeg.txt


XML
X12
275_5010_H_binary.txt


H
Two 275s with attachments. The first 275 is good and the second 275 contains an error.
Used by the V_DS_275_5010_Binary script.
276_4010_H_3InfoSrc_Clean.txt


H
An error-free 276 with three Information Source levels, each containing a different
assortment of levels.
276_5010_2Sub_Clean.txt


H
An error-free 276 with one Information Source containing a subscriber with a dependent
and a subscriber with no dependent.
277_4010_H_2error.txt


H
Small 277 text report with two subscribers. The first subscriber has an error and no
dependent, and the second subscriber has a dependent with an error.
277_5010_2Sub_Clean.txt


H
An error-free 277 with one Information Source containing a subscriber with a dependent
and a subscriber with no dependent.
278RP_4010_H_2UMO_Clean.txt


H
An error-free 278RP with two UMO levels, each with one service level.
278RP_5010_Clean.txt


H
A small error-free 278RP.
278RQ_4010_H_1UMO_Clean.txt


H
An error-free 278RQ with one dependent, which has three service provider levels, each
with three service levels.
278RQ_5010_1.txt


H
A small 278RQ with three errors.
5010-MEDICAREA_testdata.txt

H
A 5010 Medicare A claim. Installed with Shuffler and Translator and used with the
Run_Shuffler_only_demo script.
5010-MEDICAREA_testdata_flat.txt

H
A flat file. Installed with Shuffler and Translator.
810_5040_X_1.txt


X12
X12 Invoice with interchange control numbers that do not match.
810_5040_X_2intchg.txt


X12
Two interchanges, each with one X12 purchase order. The second purchase order has an
error in its first N1 segment.
Demo File Index
Contents
Replaces XML_275.txt
A 275 transaction with a BIN segment that contains XML.
Page 19
7/6/2015
Instream and Desktop DemoData Directories
Use these files to try out features of Instream and Desktop. Many of them are used by the demo scripts in Instream’s Scripts directory.
Filename
*
Instream
Desktop
Format
820_4010_H_4GS_1error.txt


H
Four GSs, each containing multiple 4010 820s. The third transaction set in the first group
has an error.
820_4010H_clean.txt


X
An 820 with four ENT loops.
834_4010_H_1.txt


H
HIPAA 834 with a code value error, a trailing delimiter, and a missing mandatory element.
834_4010_H_10members.txt


H
834 with 10 members, each with two HD. The first member’s name starts with A, the
second with B, etc.
The third member (Calkins) and the sixth member (Flannigan) are invalid.
834_4010_H_2members.txt


H
834 data with two members.
835_4010_H_2CLP.txt


H
835 with one LX and two CLP. The first CLP is valid and the second contains one error.
835_4010_H_6CAS.txt


H
An 835 with one LX, one CLP, and 6 CAS.
835_4010_H_6CAS_NoEnv.txt


H
The same as 835_4010_H_6CAS.txt but with no ISA, GS, GE, or IEA
835_5010_ACH_clean.txt


H
X12-5010 835 (BPR04=ACH) with one LX and one CLP and no errors.
835_5010_CHK_clean.txt


H
X12-5010 835 (BPR04=CHK) with one LX and one CLP and no errors.
835_5010_H_10claims.txt


H
One interchange with 10 CLP loops. The CLP01’s are numbered sequentially. All odd
CLPs are good and all even CLPs have warnings (CLP*2) or errors.
835_5010_H_2trans_10claimsEach.txt


H
Two interchanges, each with 10 CLP loops. The CLP01’s are numbered sequentially. All
odd CLPs are good and all even CLPs have warnings (CLP*2 and CLP*12) or errors.
835_5010_H_3interchanges.txt


H
X12-5010 835s. The first interchange is clean and the other two have errors. It is used by
the V_RG_835_5010_textrpt_1 script.
835_835_837I_4010_3interchanges.txt


H
Three interchanges in one file. The first two are 835s and the last is an 837I with an error.
837D_4010_H_2Prov_Clean.txt


H
An error-free 837D with two providers. Each has an assortment of subscribers and
dependents.
837I_4010_H_1clm_multiErrors.txt


H
837I with one subscriber as patient who has one claim and one service line. It contains a
wide variety of errors.
837I_4010_H_2Interchanges.txt


H
Two interchanges, each containing one 837i. Each 837I contains one subscriber with one
claim. Claim 2 has an error.
837I_4010_H_2transNoErr.txt


H
Two 837I transactions in the same functional group and interchange. The Subscriber NM109 value is different in each set to illustrate the UserExitWithWait business rule.
Please see readme-UserExits.txt in Instream’s DemoData\UserExits directory.
Demo File Index
Contents
Page 20
7/6/2015
Instream and Desktop DemoData Directories
Use these files to try out features of Instream and Desktop. Many of them are used by the demo scripts in Instream’s Scripts directory.
Filename
*
Instream
Desktop
Format
837I_4010_H_400claims.txt


H
An 837I with 400 sequentially-numbered claims. Useful for splitting practice
837I_4010_H_5provider.txt


H
837I with 5 providers. Each has 1 subscriber as patient and 1 dependent as patient. The
provider IDs are in numeric order (111111111, 222222222, etc.) and the names are in
alphabetical order. The only error is in claim 7, the dependent as patient for the second
provider).
This file is used in the content-based splitting example in
DocumentSplitterTechnicalManual.pdf and is used by scripts
V_DS_837I_4010_ContentSplit and V_DS_837I_4010_ContentSplit1.
837I_4010_H_5provider.txt


H
837I with 5 providers. Each has 1 subscriber as patient and 1 dependent as patient. The
provider IDs are in numeric order (111111111,222222222, etc.). The only error is in
provider 2222222228, the dependent as patient.
This file is used in the content-based splitting example in
DocumentSplitterTechnicalManual.pdf and is used by scripts CBS_short and
No_CBS_short.
837I_4010_H_6claims


H
Two interchanges, each containing one 837I. The first contains one subscriber with five
claims. The second contains one subscriber with one claim. Claims 2, 3, and 4 have
errors.
837I_4010_H_clean.txt


H
One provider with two subscribers. The first subscriber is a subscriber-as-patient scenario
with two claims. The second subscriber is a dependent-as-patient scenario with two
claims. The file has no errors.
837I_4010_H_Demo3DB.txt


H
837I data that goes with the ODBC exercises in BusinessRules.pdf. Also see
_readme_ODBC.txt in Instream’s DemoData\ODBC directory.
837I_4010_H_ErrorEvenClms.txt


H
837I containing one subscriber as patient with 10 claims. Claims are numbered from 1 to
10, and their amounts are from $100 to $1000. The odd-numbered claims are valid and the
even-numbered claims are invalid.
It is used in the tutorials in the validation, DocSplitter, and Response Generator
documentation.
837I_4010_H_future BHT04.txt


H
Simple 4010 837I with BHT-04 date in the future. Used with the BusinessRules.pdf tutorial.
837I_5010_H_2intg_2transEach.999

H
Used by V_DS_837I_5010_999split.
837I_5010_H_2intg_2transEach.txt

H
HIPAA 5010 837I with two interchanges, each with two transaction sets. Each transaction
set contains 10 subscriber claims. The first claim in the file has errors and the others are
clean. Claims are numbered sequentially.
Demo File Index

Contents
Page 21
7/6/2015
Instream and Desktop DemoData Directories
Use these files to try out features of Instream and Desktop. Many of them are used by the demo scripts in Instream’s Scripts directory.
Filename
*
Instream
Desktop
Format
Contents
837I_5010_H_clean.txt


H
HIPAA 837I with no errors. The first subscriber has two claims. The second subscriber has
a dependent with two claims. Claims are numbered sequentially.
837I_5010_H_ErrorEvenClms.txt


H
HIPAA 5010 837I with one subscriber containing 10 claims. The even-numbered claims
have errors. Claims are numbered sequentially and their amounts are from $100 to $1000.
837I_5010_H_errorTable1.txt


H
HIPAA 5010 837I with two subscribers. The first has two claims (the first is clean, the
second has an error). The second subscriber has a patient level with two claims (both
clean). The BHT in Table 1 has an error.
It is used by the V_RG_837I_5010_z_param and V_RG_837I_5010_999 scripts.
837Iclean_xml.xml

H
XML data used in Translator demos and installed by Translator.
837P_4010_2interchanges.997

H
Used by V_DS_837P_4010_997split.
837P_4010_2interchanges.txt


H
837P data with two interchanges. Each contains a subscriber with two claims and a
dependent with two claims. Claims with errors include claim 1 and 3 in the first
interchange, and claim 3 in the second interchange. It validates
837P_4010_2interchanges.txt.
837P_4010_H_4subClean.txt


H
Replaces 837Pclean.txt
Good 837P data with 4 subscribers. The last two subscribers have dependents.
837P_5010_ExtendedASCII_GS03_N404.txt


H
ASCII file that contains encoded data in the GS-03 and the first N4-04. Used by the
V_RG_837P_5010_ExtendedASCII script.
837P_5010_H_2Sub_BadCLM02.txt


H
An 837P which contains an error 10626 on the first CLM02. It is used by script
V_RG_837P_5010_999_rgoverride.
837P_5010_H_4Sub_clean.txt


H
An error-free 837P with four subscribers. Two have dependents and the other two do not.
837P_5010_MedicareB.txt


H
A 5010 837P Medicare B with multiple errors. Used by the
V_RG_837P_5010_277CA_STCoverride script.
837P_5010_ProcessingOrder.std


H
Demonstrates processing order of business rules. Copy it to Instream’s Database directory
and validate a 5010 837P to see the rules execute. Please see Appendix I: Processing
Order in BusinessRules.pdf.
This file works with V_837P_5010_ProcessingOrderOfRules.
837P_5010_ProcessingOrder_Rules.txt


H
This is the list of rules used in the 837P_5010_ProcessingOrder.std. It is used by script
V_837P_5010_ProcessingOrderOfRules.
837P_5010_UTF8_GS03_N404.txt


H
UTF8 file that contains encoded data in the GS-03 and the first N4-04. Used by the
V_RG_837P_5010_UTF8 script.
Demo File Index
Page 22
7/6/2015
Instream and Desktop DemoData Directories
Use these files to try out features of Instream and Desktop. Many of them are used by the demo scripts in Instream’s Scripts directory.
Filename
*
Instream
Desktop
Format
837P_5010_UTF16_GS03_N404.txt


H
850_4010_X_1.txt


X12
X12-4010 Purchase Order with conditional element relation violation in PO1.
850_5050_X.txt


X12
X12-5050 Purchase Order with many errors.
850_5050_X_onePO1.txt


X12
X12-5050 Purchase Order used by the V_Swap_850_5050 script.
850_6032_X_Small.txt


X12
15-line Purchase Order with one PO1.
X12
X12 Purchase Order Acknowledgement with a code value error in the BSN.
856_4010_X_1.txt
Contents
UTF16 file that contains encoded data in the GS-03 and the first N4-04. Used by the
V_RG_837P_5010_UTF16 script.
997_4010_TA1.txt


H
BC_837PClean.txt


X12
BC_837PClean.txt.xml

H
Example XML data to be used in a Translator demo. Installed by Translator.
CBTPAdemo directory containing:
_readme_CBTPA.txt
V_835_4010_CBTPA.bat or .sh
835_4010_H_4trans.txt
CBTPA_EX.std
MYapf_1.apf
MYapf_2.apf
MyCBpartnerAutomation.csv

H
This set of files accompanies the content-based trading partner automation exercises in
InStreamTPAutomation.pdf.
Content_Based_Split_Auto_Setup.ini

H
Docsplitter content-based splitting file that shows how to automatically split when a ZCBS
record is encountered in the validation detail results file. It is used with the
V_DS_837I_4010_ContentSplit script.
CSEG.apf
CTX directory containing
V_RG_837I_5010_999_CTX and associated
files.
Demo File Index
Three interchanges with various combinations of 997s and TA1s. Used by
V_997_4010_TA1.
A 4010 837P with an assortment of subscribers, some with subscriber claims and some
with dependent claims. Installed by Translator.
Validation profile that sets CSEG=1 so that the detail results file would contain CSEG
records, needed by Validation Highlighter when generating an HTML report from XML
data. Used by the ValidationHighlighter_XML script.

H
This set of files demonstrates custom CTX segments in a 5010 999 as described in
CTX.pdf.
Page 23
7/6/2015
Instream and Desktop DemoData Directories
Use these files to try out features of Instream and Desktop. Many of them are used by the demo scripts in Instream’s Scripts directory.
Filename
*
Instream
Desktop
Format
CUSCAR_D93A.txt


UN
Two EDIFACT interchanges. The first contains one valid message and the second
contains a valid and then an invalid message.
D93A_Orders.txt

UN
EDIFACT data used in a Translator demo and installed by Translator.
DataSwap_SplitAndSwap.ini

H
DocSplitter_XML.ini

Edifact_Orders_new.txt

UN
EDIFACT data used in a Translator demo and installed by Translator.
Edifact_Orders_new.xml

UN
XML data used a Translator demo and installed by Translator.
ELOC.apf


X
Validation profile that generates ELOC records. Used by the
V_RG_837P_4010_textrpt_ELOC script.
FF_Delim_1Vetcustomer.txt
FF_Delim_2Vetcustomer.txt


FF
Delimited flat files with one or two vet customers. The corresponding guideline is VETFF.
FF_Delim_1VetCustomer.txt


FF
Delimited non-EDI file with one error. Used with the V_FlatFile_Delim script and
VETDELIM guideline.
FF_Delim_Customers.txt


FF
Delimited flat file data used by the V_FFdelim_CBTPA script. The corresponding
guidelines are CustDELIM*.
FF_FL_1VetCustomer.txt


FF
Fixed length flat file data with one vet customer. The corresponding guideline is VETFF.
FF_FL_OneRecordType_NoTag.txt

FF
Flxed-length flat file that has only one record type and no record tag. Validate with
guideline FF_FL_NoTag_OneRec. Used by V_FF_fixed_oneRec script.
FFTPAdemo directory containing V_FF_TPA
and associated files

FF
This set of files demonstrates flat file first record partner automation as described in
InStreamTPAutomation.pdf.
Please see the file _readme_FFTPA.txt for an explanation of the demo.
fsuid.apf

H
Validation profile used with V_Dswap_837I_4010_FSUID_eachCLM, the unique ID demo.
It has UID=1, which activates the guideline’s GenerateFSUID business rule.
Gen275 directory containing DDE and Attach
files for input into Generate275 script.

H
This set of files demonstrates how to use Gen275 to create a 275 transaction from a DDE
and Attach file. See 275atForesight.pdf.
HeaderResponse.NCPDP

N
Header file to put in front of NCPDP responses that do not have 1.1 enveloping.
HeaderTrans.NCPDP

N
Header file to put in front of NCPDP transmissions that do not have 1.1 enveloping.
HL7_ORU_R01_Clean.txt

Demo File Index


XML
HL7
Contents
Dataswapper INI file used by the V_DS_837I_4010_Swap script.
Docsplitter setup file for splitting XML. It is used by V_DS_XML_split_PO in the Scripts
directory.
HL7 ORU R01 file. Used by Instream’s V_ORUR01_HL7_Clean script.
Page 24
7/6/2015
Instream and Desktop DemoData Directories
Use these files to try out features of Instream and Desktop. Many of them are used by the demo scripts in Instream’s Scripts directory.
Filename
*
Instream
Desktop
Format
INVOIC_D96_UN_1.txt


UN
INVOICES_TRAD93_clean.txt


T
SampleTRADACOMS order. Used by script V_Order_TRADACOMS_TPA.
ISerrorConfig.ini
ISerror_835_BadResults.dtl

H
These two files go with the ISError demos in the Scripts directory. The INI file is an
example ISErrors configuration file and the demos check the DTL file to see if they contain
at least one error. See ISErrors.pdf.
NCPDP_ Response _51.txt


N
A B2 Billing Reversal (Response) containing five G1 segments, each containing segment
21, a Response Status Segment.
NCPDP_BillRequest_51.txt


N
A Billing (Request) containing three G1 segments, each with one claim.
ODBC directory containing two ODBC demos.


H
This demo only works for 32-bit Instream.
This set of files demonstrates the ODBC business rules that are explained in Appendix E
of BusinessRules.pdf.
See the directions in _readme_ODBC.txt in Instream’s DemoData\ODBC directory.
ORDERS_D93_UN_1.txt


UN
Simple EDIFACT D93A purchase order with errors trailing sub-element separator in the
BGM and a wrong code value in a NAD01.
Respgenoverride.apf

pain.001.001.02_BadBIC.xml

XML
ResponseGen_z.ini

H
Setup file for Response Generator z parameter.
It is used by the V_RG_837I_5010_z_param script.
RGtemplate_COBA837.txt

H
Response Generator custom report template that generates a COBA claims dispute file.
Executed by RunTutorial837IRG_short_COBA in the Scripts directory.
RGtemplate270.txt

H
Response Generator custom report template that generates a 270 custom report in html
format.
RGtemplate277_h.txt

H
Response Generator custom report template that generates a 277 custom report in html
format.
RGtemplate277_t.txt

H
Response Generator custom report template that generates a 277 custom report in table
format.
RGtemplate277all.txt

H
Response Generator custom report template that uses all possible fields in a 277 custom
report.
Demo File Index
Contents
EDIFACT D96A invoice with errors in both LIN segments.
Sample Validation profile (.apf file) used to generate a 999 with Response Generator
overrides.
Sample Pain credit transfer message. It is used by the V_pain.001.001.002_xml script.
Page 25
7/6/2015
Instream and Desktop DemoData Directories
Use these files to try out features of Instream and Desktop. Many of them are used by the demo scripts in Instream’s Scripts directory.
Filename
Instream
Desktop
Format
*
Contents
RGtemplate834A.txt

H
Response Generator custom report template that uses most fields possible in an 834
custom report.
RGtemplate834B.txt

H
Response Generator custom report template that generates a report in columns.
RGtemplate835_c.txt

H
Response Generator custom report template that generates an 835 report in columns.
RGtemplate837any_t.txt

H
Response Generator custom report template that generates a text report that shows errors
in claims. It is used by script V_RG_837P_4010_textrpt_1.
RGtemplate837any_t_ELOC.txt

H
Response Generator custom report template that generates a text report that shows nonerrors in claims. It is used by script V_RG_837P_4010_textrpt_ELOC.
RGtemplate837I.txt

H
Response Generator custom report template that generates a plain report.
RGtemplate837I_c.txt

H
Response Generator custom report template that generates a report in columns.
RGtemplate837I_h.txt

H
Response Generator custom report template that generates an HTML report with a logo.
RGtemplate837I_hl.txt

H
Response Generator custom report template that generates an HTML report with a logo
and table lines.
RGtemplate837I_t1.txt

H
Response Generator custom report template that generates a text report that has
information by provider and by transaction set. It is run by script
RunTutorial837IRG_short_textrpt_t1.
SampleSTCOverride_MedB.csv

H
STC override file for script V_RG_837P_5010_277CA_STCoverride.
SampleTPA_997split.csv

H
Lookup file for trading partner automation. Used by Docsplitter to pick an INI file in script
V_DS_835_4010_TPA997split.
SampleTPA_DS_RG.csv

H
Lookup file for trading partner automation. Used by validation, Response Generator, and
Docsplitter. Used by these scripts: V_DS_837I_4010_TPA, V_RG_837I_4010_TPA, and
V_RG_837P_4010_TPA.
SampleTPA_FF_XML.csv

FF, XML
SplitPointUNB.ini

TIBCOlogo.gif

Tibco logo added to HTML report generated by V_RG_837I_4010_HTMLrpt.
TPA_DocSpliltter1.ini

Docsplitter INI file that can be by Docsplitter trading partner automation. It is not suitable
for calling with the -s command line parameter.
Demo File Index

UN
Lookup file when validating XML and flat file data using content-based trading partner
automation. Used by the V_FFdelim_CBTPA script.
Split point configuration file used with script V_DS_CUSCAR_D93_UNB. It sets the split
point at the UNB segment in EDIFACT EDI.
Page 26
7/6/2015
Instream and Desktop DemoData Directories
Use these files to try out features of Instream and Desktop. Many of them are used by the demo scripts in Instream’s Scripts directory.
Filename
Instream
Desktop
Format
*
Contents
TPA_DocSplitter.ini

Docsplitter INI file that can be called by the command line -s parameter or by Docspliltter
trading partner automation.
TPA_ResponseGen.ini

Response Generator INI file suitable for Response Generator trading partner automation.
TPARouter_Sample.cfg

TPARouter_Sample_X12.cfg

Trailer.NCPDP

User_Error_Messages.xls

UserExits directory containing two UserExit
demos.

H
This set of files demonstrates the UserExitWithWait and UserExitWithoutWait business
rules that are explained in BusinessRules.pdf.
See the directions in readme-UserExits.txt in Instream’s DemoData\UserExits directory.
WEBSRV1_837P.sef

H
Guideline to illustrate Array, Lookahead, and Web Services business rules. Import into
EDISIM’s Standards Editor to see the rules. See Appendix J in BusinessRules.pdf.
XML_PO_f.xml


XML
A purchase order in XML format. Validate it with the XML_PO_f guideline. It has 10
th
ORDERS elements, and the 6 one contains an error. It is used by V_DS_XML_split_PO
and XML_PO_f in the Scripts directory.
XML_PO_f_1error.xml


XML
There are 10 ORDERS, and the last one is invalid. It is used by the V_DS_XML_split_PO
script.
Demo File Index

H
Sample configuration file for TPARouter. See TPARouter.pdf.
X
Sample configuration file for TPARouter. Used by script TPARouter_810_5040.
N
Trailer file to put at the end of NCPDP responses that do not have 1.1 enveloping.

Spreadsheet to help you manage your custom error messages. For details, please see
ManagingCustomErrorMessages.pdf.
Page 27
7/6/2015
Discontinued DemoData Files
Discontinued file
Use this instead …
277.txt
277_4010_H_2error.txt
2Interchanges837i.txt
837I_4010_H_2Interchanges.txt.
400claims.txt
837I_4010_H_400claims.txt
6claims.txt
837I_4010_H_6claims
820clean.txt
820_4010H_clean.txt
820Errors5.txt
820_4010_H_4GS_1error.txt
834-2members.txt
834_4010_H_2members.txt
835-Demo1.txt
835_4010_H_6CAS.txt
835-Demo1STSEonly.txt
835_4010_H_6CAS_NoEnv.txt
835-Demo2.txt
837I_4010_H_1.txt
837I_4010_H_ErrorEvenClms.txt
837I_5010_H_10claims.txt
837I_5010_H_ErrorEvenClms.txt
837Iclean.txt
.
837I-Demo3.txt
837I_4010_H_1clm_multiErrors.txt.
837I-Demo3DB.txt
837I_4010_H_Demo3DB.txt
837P_4010_2interchanges_ 1type2error.txt
837P_4010_2interchanges.txt
837P_5010_H_2Sub.txt
837P_5010_H_4Sub_clean.txt
837Pclean.txt
837P_4010_H_4subClean.txt
DocSplitter_835_Demo.txt
835_4010_H_2CLP.txt
DocSplitter_837I_Demo.txt
FF_D_Oneill_2.txt
FF_Delim_2Vetcustomer
FF_FL_Oneill.txt
FF_FL_1VetCustomer.txt
fslogo.gif
TIBCOlogo.gif
InterchangeSplitter3ISADemo.txt
835_835_837I_4010_3interchanges.txt
MultProvider837I.txt
837I_4010_H_5provider.txt
Demo File Index
Page 28
7/6/2015
Discontinued DemoData Files
Discontinued file
Use this instead …
NCPDP_Response.txt
NCPDP_Response_51.txt
NCPDP_Trans.txt
NCPDP_BillRequest_51.txt
Oneill.txt
FF_Delim_1VetCustomer.txt
TA1_997.txt
997_4010_TA1.txt
Trad93_Order.txt
INVOICES_TRAD93_clean.txt
Tutorial834A.txt
834_4010_H_10members.txt
Tutorial837IA.txt
837I_4010_H_ErrorEvenClms.txt
Two837i.txt
837I_4010_H_2transNoErr.txt
XML_275.txt
275_4050_BinSeg.txt
Demo File Index
Page 29
7/6/2015
Instream and Desktop Database Directories
These files are used by Instream demos
Filename
Instream
Desktop
Contents
850_5050_SwapST03.std

Purchase order guideline for the V_Swap_850_5050 script. It has a Dataswapper business rule that replaces
the data in the ST-03 with “KAVERCO”.
CustDELIM_BASE.std

Flat file base guideline for the V_FFdelim_CBTPA script. It contains an IdentifierLookup business rule that
points to SampleTPA_FF_XML.csv on the State field. The corresponding data file is F_Delim_Customers.txt.
CustDELIM_MI.std

Flat file guideline for the V_FFdelim_CBTPA script. The validation switches to this guideline whenever the
State field contains MI in the flat file data (based on settings in SampleTPA_FF_XML.csv). The corresponding
data file is F_Delim_Customers.txt.
CustDELIM_OH.std

Flat file guideline for the V_FFdelim_CBTPA script. The validation switches to this guideline whenever the
State field contains OH in the flat file data (based on settings in SampleTPA_FF_XML.csv). The corresponding
data file is F_Delim_Customers.txt.
MYCUSCAR_D93A.std

EDIFACT D93A CUSCAR guideline that creates structure records in validation detail results file. Used in
V_DS_CUSCAR_D93A_UNB script.
NO_DATA.std

ODBCEX2.std

Guideline used by the V_837I_4010_noData script. It demonstrates the RunNoData business rule, which is
attached to the CUR segment in the guideline NO_DATA. It displays a message if the EDI does not contain a
CUR segment.

Level 1-2 guideline containing pre-defined ODBC business rules for example 2 in Appendix E of
BusinessRules.pdf.
RG_X12_Responses.std

Guideline used by the V_RG_850_5050 script, which creates responses from an X12 850. It contains the
necessary DSR marks on the ISA, GS, and ST segments.
Sub1.std

Guideline used by the V_Dswap_837I_4010_BHT06 script. It has a DataSwapper business rule on the BHT06.
VETDELIM.std


Delimited guideline that describes a veterinary customer. The corresponding data files are
FF_Delim_1VetCustomer.txt and FF_Delim_1VetCustomer.txt .
VetFF.std


Fixed field length flat file guideline. The corresponding data file is FF_FL_1VetCustomer.txt.
VETFIXED1.std
VETFIXED2.std


Fixed field length flat file guideline that describes a veterinary customer. The corresponding data file is
FF_FL_1VetCustomer.txt.
XML_PO_F.std


Guideline used by the V_DS_XML_split_PO and XML_PO_f scripts. It corresponds to XML data file
XML_PO_f.xml in DemoData.
Demo File Index
Page 30
7/6/2015
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement