TIBCO Foresight® Instream® - TIBCO Software · Instream Release Notes 1 Release Notes for TIBCO Foresight® Instream® Release 8.7.0 Instream® automates transaction flow and validates

TIBCO Foresight® Instream®

Release Notes

Software Release 8.7.0

August 2017

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 BusinessConnect, TIBCO BusinessEvents EDI Plug-in, TIBCO Foresight EDISIM, TIBCO Foresight HIPAA Validator Desktop, TIBCO Foresight Instream, TIBCO Foresight Studio, 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.

The United States Postal Service holds the copyright in the USPS City State Zip Codes. (c) United States Postal Service 2017.

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-2017 TIBCO Software Inc. ALL RIGHTS RESERVED.

TIBCO Software Inc. Confidential Information

General Contact Information

TIBCO Software Inc.

3303 Hillview Avenue|

Palo Alto, CA 94304 USA

Tel: +1 650 846 1000

Fax: +1 650 846 1005

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.)

mailto:[email protected]

https://support.tibco.com/

Contents

Important Information about Instream Release 8.7.0 ................................................................................... 1

API users ................................................................................................................................................... 1

Download Documentation ......................................................................................................................... 1

License File Information ............................................................................................................................ 1

Code Tables .............................................................................................................................................. 1

New and Changed Features ......................................................................................................................... 2

Demo Changes ............................................................................................................................................. 3

Code Table Changes .................................................................................................................................... 4

CCI Table Updates .................................................................................................................................... 4

Core3 Code Combination Table Updates ................................................................................................. 4

Code Table Updates .................................................................................................................................. 4

Guideline Changes ........................................................................................................................................ 6

New and Changed HIPAA Guidelines ....................................................................................................... 6

New and Changed Healthcare Guidelines (Non-HIPAA Mandated) ......................................................... 6

No Future Guideline Changes ................................................................................................................... 6

Guideline Updates ..................................................................................................................................... 6

Error Message File Changes ........................................................................................................................ 7

Other Installations and Miscellaneous .......................................................................................................... 7

Separate Code Table Updates .................................................................................................................. 7

TIBCO Foresight® Transaction Insight® Customers ................................................................................ 8

Closed Issues ................................................................................................................................................ 9

Instream Release 8.7.0 ............................................................................................................................. 9

Appendix A –Closed Issues for Previous Releases .................................................................................... 13

Appendix B – No Future Guideline Changes Listing .................................................................................. 20

Instream Release Notes 1

Release Notes for TIBCO Foresight® Instream®

Release 8.7.0

Instream® automates transaction flow and validates transactions according to industry standards, organizational guidelines, and specific business rules.

We are pleased to offer you our newest version of Instream. Instream is available in two versions: Instream Standard Edition and Instream Healthcare Edition. Some information in this document pertains only to Instream Healthcare Edition and is noted appropriately.

We welcome all feedback. Please contact our Support Representatives by:

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.)

Important Information about Instream Release 8.7.0

This section lists important information about the newest release of this product.

API users

API users do not need to recompile their API code for Instream 8.7.0.

Download Documentation

The installation program no longer installs documentation.

Instream documentation is available on https://docs.tibco.com/. When Instream is installed, a /Doc

directory is provided. You may wish to download your documentation to this directory for ease of access.

License File Information

A license file is no longer required to use Instream.

Code Tables

HIPAA code tables, which apply to Instream Healthcare Edition only, are updated with each release and as needed (see Separate Code Table Updates on page 7).

mailto:[email protected]


https://docs.tibco.com/


New and Changed Features

Change Details

Additional Guideline Supported Support for the following guideline was added:

Health Care Claim Request for Additional Information (277)

277-X213.std (types 1-2)

PDSX5010-277X213.std (types 1-2)

Additional Platforms Supported Instream now supports the following platforms:

IBM AIX 7.2, 64-bit on pSeries

Novell SUSE Linux Enterprise Server 12.2, 64-bit on x86-64

Oracle Solaris 11, 64-bit on SPARC

Oracle Solaris 11, 64-bit on x86-64

APF File Options The following validation profile options were updated:

AllowDelimiterAsPartOfData

Option is now available for flat files. Previously it had only

been available for HL7.

ContinueAfterSQLErrors

Option was enhanced to include ODBC business rules.

Refer to APF.pdf for more information.

Document Splitter The following command line option was added to Document Splitter:

UseDocSplitterPlus =n

When set to 1 (yes), this option specifies the use of High-Performance

Parsing, which improves processing time on large files.

High-Performance Parsing should be used for HIPAA EDI documents

ONLY.

Refer to TIB_fsp-instream_<n.n>_docsplitter.pdf for more

information.

Instream - SVALU Record Structure

IDs

SVALU Record Structure IDs were added for the following Post-

adjudication Claims guidelines:

837 Dental (PDSA5010-837X300)

Institutional (PDSA5010-837X299)

Professional (PDSA5010-837X298)


Change Details

Response Generator The following parameter was added to Response Generator:

-fdostrictTA1

Use this parameter along with the -oTA1 parameter to generate a TA1

only when the inbound data is valid according to the base X12 5010

TA1 syntactical requirements

Example: -oTA1 TA1.txt -fdostrictTA1

When using this parameter, the generation of a TA1 response is

entirely dependent on your inbound data. If any inbound data required

for use in the TA1 does not meet requirements, an error is generated

and no TA1 is created.

Demo Changes

This section describes changes and additions to the demos provided with Instream. Refer to Demo_Index.pdf for more information.

None at this time.


Code Table Changes

CCI Table Updates

Note: CCI Tables apply to Instream Healthcare Edition only.

Instream Release 8.7.0 includes the following updates to CCI Tables. Some of these changes were

originally released in the following interim CCI Table Updates: 8.6.0.1 through 8.6.0.4.

Table Updated to this Version/Date

CMS CCI Version 22.3, effective from October 1, 2016 through December 31, 2016.

Version 23.0, effective from January 1, 2017 through March 31, 2017.

Version 23.1, effective from April 1, 2017 through June 30, 2017.

Version 23.2, effective from July 1, 2017 through September 30, 2017.

Core3 Code Combination Table Updates

Note: Core3 Code Combination Tables apply to Instream Healthcare Edition only.

Instream Release 8.7.0 includes the following updates to Core3 Code Combination Tables. Some of

these changes were originally released in the following interim Core3 Code Combination Table updates:

8.6.0.1 through 8.6.0.3.

Table Updated to this Version/Date

Core3Code

Combination

Version 3.3.1, released October 2016.

Version 3.3.2, released February 2017.

Version 3.4.0, released June 2017.

Code Table Updates

Note: Code Tables apply to Instream Healthcare Edition only.

Instream Release 8.7.0 includes the following updates to Code Tables. Some of these changes were

originally released in the following interim Code Table updates: 8.5.0.27 through 8.5.0.29 and 8.6.0.1

through 8.6.0.28.

Important: TIBCO Foresight’s license agreements with some code set vendors prevent us from listing

specific updates.

Table Name Updated to this Version/Date

AdjustmentReasonCodes WPC Updates Mar 1, 2017

WPC Code Updates (Received 11/1/2016)

CDT Annual 2017


Table Name Updated to this Version/Date

ConditionCode UB-04 July 2017

UB-04 Update 2017

CPT Category I codes

Category III codes

CPT4 Annual 2017 update

Category I Updated Jan 2017

Category III Updated Jan 2017

PLA codes (Proprietary Laboratory Analyses)

DecisionReasonCodes Corrected dates from 10/01/2001

DRG Annual 2017

HCPCS October 2016

Annual 2017 update

Apr 1, 2017 (Corrections to the 2017 Alpha-Numeric HCPCS file)

Correction for G0498

July 1, 2017

ICD10Diagnostics 2017 corrections (Removed termination date from 6 codes)

LOINC V2.56, V2.58

NAIC Semi-Annual June 2016

Dec 2016

PaymentType WPC Code Updates (Received 11/1/2016)

WPC Alert (Received May 12, 2017)

POScodes Annual 2017 update

RemarkCodes WPC Updates Mar 1, 2017


ReportType WPC Alert (Received May 12, 2017)

RevenueCodes UB-04 July 2017

UB-04 Update 2017

ServiceType WPC Updates Mar 1, 2017


StatusCodes Corrected some dates from 10/31/2006 to 10/31/2004


TaxonomyCodes Received 01/01/2017

Value Codes UB-04 July 2017

Zip Sept 2016 through July 2017


Guideline Changes

This section describes changes and additions to the HIPAA and Non-HIPAA guidelines provided with Instream. Refer to the documents ForesightHIPAAguidelinelist.pdf and ForesightGeneralGuidelinelist.pdf.

New and Changed HIPAA Guidelines

Guideline Change

HIPAA Guidelines 5010, Types 1-2, Errata None at this time

HIPAA Guidelines 5010, Types 1-7, Errata None at this time

HIPAA Guidelines PLUS 5010 Errata

The changes to the HIPAA guidelines listed in HIPAA

Guidelines 5010, Types 1-7 Errata, are also included in the

corresponding HIPAA "Guideline Plus" listed in this section.

X12-5010 before June 2010 Errata Although still supported, these guidelines are no longer

shipped with TIBCO Foresight products.

New and Changed Healthcare Guidelines (Non-HIPAA Mandated)

Guideline Change

Health Care Claim Request for Additional Information

(277)

This guideline has been added as:

277-X213.std (types 1-2)

PDSX5010-277X213.std (types 1-2)

No Future Guideline Changes

See Appendix B for a listing of guidelines for which changes are no longer being incorporated.

Guideline Updates

A comprehensive listing of all guideline updates contained in this release of Instream can be found in the

document TIBCO Foresight® Instream® Release Notes Addendum - Guideline Updates

(tib_instream_8.7.0_gl_addendum.pdf).


Error Message File Changes

Note: If you are using your own profiles, please make sure you run HVUpdate.exe. This will ensure that

your profiles are updated with all the latest error numbers and latest parameters. See APF.pdf for

details. Some of these errors may apply to Instream Healthcare Edition only.

Error message additions and/or changes resulting from guideline updates are now noted in the document

TIBCO Foresight® Instream® Release Notes Addendum - Guideline Updates

(tib_instream_8.7.0_gl_addendum.pdf).

Other Installations and Miscellaneous

Separate Code Table Updates

After installation, it is recommended that you check for Code Table Updates. This ensures you have access to the most up-to-date Code Tables

The code table database is available for download separately from the product installation. This allows TIBCO Foresight to provide code table updates between major releases of the product.

Updates are distributed through the TIBCO Support system. In order to receive automated emails when an update is available, you must subscribe to the products you are interested in.

To receive emails

1. Sign into TIBCO Support (https://support.tibco.com) using your credentials.

2. From the dropdown menu beside your user name, select Product Interests and Knowledge Base

Subscriptions.

3. Click as desired to subscribe to products of interest.

4. Configure your subscriptions for those products.

5. Click Save Interests.

To download code table updates

1. Sign into TIBCO Support (https://support.tibco.com) using your credentials.

2. Select Downloads > Hotfixes > Available Downloads.

3. Click on Foresight.

4. Select HIPAA_Code_Tables.

Note: Code tables with version 7.3 and later require the actual Instream 7.3 or later program. You can check the Instream version and the code table version by executing the Version.bat file in Instream’s Scripts directory.




TIBCO Foresight® Studio

Foresight® Studio is a separate installation program with a separate Release Notes document. Please contact TIBCO Foresight Support for details.

TIBCO Foresight® Transaction Insight® Customers

Transaction Insight® customers who update Instream need to run one of the scripts below to get their new error definitions into TI:

TI_ErrorUpdate_For_Instream_8.7.0.0_MSSQL.sql

TI_ErrorUpdate_For_Instream_8.7.0.0_ORACLE.sql

These scripts are available in Instream’s Scripts directory (\Scripts\TI).


Closed Issues

Instream Release 8.7.0

Note: Instream Release 8.7.0 includes changes originally contained in Release 8.6.0 Hotfix 1 through

Hotfix 5.

Change

Request ID Summary

Originally

contained in

a Release

8.6.0

Hotfix?

FINS-721 (IBM AIX platforms only) An issue which caused the fsdir.ini file to be over-

written during installation has been resolved.

Hotfix 3

FINS-893 Behavior of the Response Generator -fdostrict999 parameter has been revised.

The CTX01-02 is limited to 35 characters.

No

FINS-973 This Change Request corrects two issues:

999 requests in the Response Generator Java API were being handled as

997s

999 files were being written to 997s in the Instream Java API.

No

FINS-1019

Existing DocSplitter functionality was slow when splitting large 834 files. This

issue was addressed with the new High-Performance Parsing option, which

improves execution time on large files.

No

FINS-1148 The Response Generator -csovr option, which directs Response Generator to

use a specified value for the specified field in the interchange and/or group

header segment(s), is now available for EDIFACT responses.

Hotfix 1

FINS-1170 The Response Generator -csovr option was updated to better handle the

following X12 Keys:

ISA03: SECQ

ISA04: SEC

ISA12: IVER

ISA13: ICTL

ISA14: ACK

ISA15: USAGE

GS06: GCTL

GS07: RAC

GS08: GVER

Hotfix 1

FINS-1177 Two new .dll files are provided for use when developing APIs with Microsoft

Visual Studio(r) 2010. To utilize the files:

1. Access \<TIBCO_HOME>\instream\8.6\API\InStreamAPISample\dlls

2. Copy the following files to \<TIBCO_HOME>\instream\instream\8.6\bin

HVInStream_VS2010.dll (release version)

HVInStreamD_VS2010.dll (debug version)

Hotfix 3


Change

Request ID Summary

Originally

contained in

a Release

8.6.0

Hotfix?

FINS-1179 (Sun Solaris platforms only) The process used for checking trailing zeros was

updated and now uses the correct pointer.

Hotfix 3

FINS-118

The Response Generator -csovr option was updated to better handle double

quotes when they are passed via the Java or C++ API.

Hotfix 1

FINS-1184 Values specified for ISA elements using the Response Generator -csovr option

are now automatically padded with spaces and/or zeros to satisfy fixed length

field requirements.

Hotfix 1

FINS-1193 The DefineCustomRec business rule now produces a more specific error

message when ID length exceeds four characters.

No

FINS-1194

An issue causing DocSplitter to fail for 271-type transactions when 2100C/2110C

and 2000D are present was resolved.

Hotfix 3

FINS-1202 APF file option 'AllowDelimiterAsPartOfData' option is now available for flat files.

Previously it had only been available for HL7.

Hotfix 3

FINS-1203 An issue causing intermittent invalid data results in output buffers when

Response Generator results are saved to memory was corrected.

Hotfix 3

FINS-1211 ExitLoop business rules used in a ForEach loop were not decreasing the loop

level correctly. This has been resolved.

Hotfix 3

FINS-1214 An issue causing Document Splitter to create incorrect XML output when data is

using UTF8-BOM has been corrected.

No

FINS-1217 Issues causing memory buffer overrun errors have been resolved. Hotfix 2

FINS-1219 The APF file option 'ContinueAfterSQLErrors' was enhanced and the expanded

range of effect now includes ODBC business rules.

Hotfix 3

FINS-1283 The ISIServer Log files timestamp format was corrected to include seconds

(HH:MM:SS).

No

FINS-1285 The following Response Generator parameters are no longer case-sensitive:

-fDoGS05_HHMM

-fDoGS05_HHMMSS

-fDoGS05_HHMMSSD

-fDoGS05_HHMMSSDD

No


A blank TRN02 now returns a 999 with a CTX.

No


A/N fields allowed to have trailing spaces now result in creation of a 999.

No


Change

Request ID Summary

Originally

contained in

a Release

8.6.0

Hotfix?

FINS-1318 An issue causing Response Generator custom reports for HL7 to produce

duplicate responses has been resolved.

No

FINS-1319 The DateCalc ‘BYMONTH’ business rule produced unexpected results under

some conditions. The rule was updated and now runs as expected.

No


A missing or invalid ST01 now results in creation of a 999 with no AK2 loop.

No


A missing or invalid ST03 now results in creation of a 999 with no AK203

element.

No


An invalid ST02/SE02 now results in creation of a 999 with no AK2 loop.

No

FINS-1327

An issue with the API (C++) caused Response Generator to write TA1s to a 277.

This has been corrected.

Hotfix 5

FINS-1341 An issue causing TA1 interchange control numbers to increment by two instead

of one has been resolved.

No

FINS-1358

When run in memory, Java Unified API functions

Doc_getNextInValidDocumentName and Doc_getNextValidDocumentName

returned null values. This has been corrected and the functions now return the

proper values.

Hotfix 4

FINS-1360 The XML engine for validation was modified to treat maxOccurs greater than

1,000,000 as ‘unbounded'.

No

FINS-1363 Response Generator now generates REF*BLT for 837I (837X299). No

FINS-1370 AK1 responses were generated with Response Generator's -fdo_strict999

parameter when the parameter had not been specified. This issue has been

resolved.

Hotfix 5

FINS-1373

In order to conform to the Centers for Medicare and Medicaid Services

requirement for the creation of both valid and invalid TA1 response documents,

existing Response Generator functionality was updated with the -fdostrictTA1

flag.

Hotfix 5

FINS-1376 UN character set ‘A’ was incompletely defined, causing EDIFACT files with the

UNB02.01 set to UNOA to generate an error during validation. This issue has

been resolved.

No

FINS-1377 PDSA5010-999X231 was missing IK502 code I5. It was added and the code

now merges properly into PDSA5010-999X231.std.

No


Change

Request ID Summary

Originally

contained in

a Release

8.6.0

Hotfix?

FINS-1387 Response Generator behavior has been modified to account for GEN records

when checking for the SVRTY entry for a severity of 3+.

No

FINS-1428 The 277-X150.std, 275-X151.std, and 277CA-X214.std were found to be

encrypted after installation of Interim Guideline Update 8.6.0.3. This issue has

been resolved.

No

FINS-1442 Support for the 2014 version of the EANCOM 2002 Standard has been added as

an EDIFACT derivative to TIBCO Foresight® EDISIM® version 6.17.0

No

FINS-1445 The GetARowFromArray business rule produced an ‘invalid rowIndex’ error. This

issue has been resolved.

No


Appendix A –Closed Issues for Previous Releases

Closed Issues for Previous Releases are retained in this document for one year. These tables are for

reference only and contain no new or updated information.

Note: Instream Release 8.6.0 included changes originally contained in Release 8.5.0 Hotfixes 1 through

5.

Change

Request ID Summary

Originally

contained

in a Release

8.5.0

Hotfix?

FINS-587 New custom report parameters have been added to Response Generator,

allowing for the inclusion of ISA totals at the end of the report.

No

FINS-652 To better handle linefeeds or carriage return-linefeeds within data elements, new

option "CheckEmbeddedNewlines" was added to the [Analyzer Options] section

of the .apf file.

Hotfix 3

FINS-719 (Sun Solaris platforms only) An issue causing a segmentation fault when

validating delimited flat files has been corrected.

Hotfix 2

FINS-733 (EDIFACT only) Instream now generates a 10234 error (Severity 2 - Warning)

when trigger segments have the same ID in different loops.

Hotfix 2

FINS-746

and

FINS-930

(Novell SUSE Linux Enterprise Server platforms only) Text imperfections

appearing in 824 transactions were corrected.

Hotfix 3

FINS-752 (X12 and EDIFACT responses only) A new Response Generator option, -csovr,

directs Response Generator to use a specified value for the specified field in the

interchange and/or group header segment(s).

No

FINS-753 An issue causing DocumentSplitter to create invalid 835 files when the LX

segment is missing in the data has been corrected.

No

FINS-779 An issue causing DocumentSplitter to create invalid 5010 837P files when the

CLM segment is missing in the data has been corrected.

No

FINS-791 Setup File option AddST02ToFilename was added to DocumentSplitter. If set to

true (1), the first ST02 value encountered in the file is added to the output

filename.

No

FINS-794 The handling of CORE Code combination CARC/RARC code validation was

enhanced to better match the implementation guide.

Hotfix 2

FINS-796 The PartialFunctionalGroupAcceptance entry in the dir.ini file was updated and

now works as expected.

Hotfix 2


Change

Request ID Summary

Originally

contained

in a Release

8.5.0

Hotfix?

FINS-797 The Response Generator 835 Custom Report has been updated to display PLB

segments, both with and without Payments.

Hotfix 2

FINS-812 An issue causing DocumentSplitter to produce fatal errors 11302 and 11323 has

been resolved.

Hotfix 2

FINS-814 Several missing invalid date formatting error messages have been restored. This

may result in the generation of errors not seen previously.

No

FINS-815

FINS-830

and

FINS-1002

Platform support information listed in the readme.txt files for Instream Standard

and Healthcare products was updated as follows:

-32-bit versions of IBM AIX are no longer supported

-IBM AIX 5.3 is no longer supported

-Support for Red Hat Enterprise Linux Server 7.x was added

-Support for Windows Server 2012 R2 was added.

No

FINS-817 The PartialTransactionSetAcceptance parameter in the dir.ini file was updated

and now works as expected.

Hotfix 2

FINS-818 Bad data in the 276 document HL segment was not producing an error as

expected. This has been corrected.

Hotfix 2

FINS-819 Response Generator return codes in the 300+ range were reassigned to the

100+ range.

Hotfix 2

FINS-820 Return Codes were updated to include new codes 101-199. Change was made

in the following user document:

ResponseGeneratorTechnicalManual.pdf > Appendix A: Return Codes

No

FINS-822 Response Generator functionality to increment ISA control number using a file

was added to the following user document:

ResponseGeneratorTechnicalManual.pdf > Appendix C: TPA Setup File

>TPA-Parameter Setup File Contents > InterchangeControlControlPath

No

FINS-823

and

FINS-1067

New option -omsa was added to Response Generator to specify generation of an

HL7 MSA (Message Acknowledgement Segment).

Refer to ResponseGeneratorTechnicalManual.pdf > Executing Response

Generator > Command Line Format > -omsa

No

FINS-825 The IsAlpha business rule was updated to better handle cases in which the

'falseRule' clause is omitted.

Hotfix 2

FINS-829

The IsNum business rule was updated to better handle cases in which the

'falseRule' clause is omitted.

No


Change

Request ID Summary

Originally

contained

in a Release

8.5.0

Hotfix?

FINS-832

The value specified in the STCoverride.csv file was populating the STC11

instead of the STC10. Response Generator has been updated to correct this

issue.

Hotfix 1

FINS-833 Instream was updated to more gracefully handle and alert users when validating

an 5010X222 and 201 0AA HL03=22 is encountered. Previously, Instream would

sometimes exit unexpectedly in this scenario.

No

FINS-834 Response Generator custom reports for 834 and 837 now use empty fields to

represent empty loops.

Hotfix 2

FINS-836

Changes were made to string creation in the OutputAK3() function to prevent

intermittent Response Generator crashes.

Hotfix 1

FINS-838

Setup File options CalcValidTS3a and CalcInValidTS3a were added to

DocumentSplitter. These options specify if the TS3 element values in the

Valid/Invalid output file should be recalculated.

No

FINS-839 (TIBCO BusinessEvents® EDI Plug-in customers only) Instream was updated to

alert users to bad EDI during validation. Previously, Instream would exit

unexpectedly in this scenario.

No

FINS-842 An issue causing validation to stop when the GetValueFromSegment business

rule is used has been resolved.

No

FINS-844

(TIBCO BusinessConnect™ only) An internal DocumentSplitter issue regarding

the splitting of valid claims and invalid documents was addressed.

Hotfix 3

FINS-868 DSR marks defined at the Loop level were causing a memory leak. This has

been resolved.

Hotfix 2

FINS-869 New options were added to Response Generator’s –f command to control GS05

formatting:

-fdo_gs05_hhmm

-fdo_gs05_hhmmss

-fdo_gs05_hhmmssd

-fdo_gs05_hhmmssdd

Refer to ResponseGeneratorTechnicalManual.pdf > Executing Response

Generator > Command Line Format > -f<option>

No

FINS-886

A DocumentSplitter issue causing leading and trailing zeros in 5010 835

monetary fields to produce an error was resolved.

Hotfix 3

FINS-889 Instream was updated to better handle alignment of HL7 segments with the

guideline.

Hotfix 2


Change

Request ID Summary

Originally

contained

in a Release

8.5.0

Hotfix?

FINS-891 Response Generator now provides an option to write the more descriptive error

message found in the Instream Detail file into the STC12 segment when

STC01.01=A3 and STC01.02=21 are both present.

Hotfix 2

FINS-893 Due to a mismatch in the maximum field lengths for the 270 2000C TRN02

(50 characters) and the 999 CTX01-02 (35 characters), Response Generator

sometimes created invalid 999 response documents for 270 transactions. To

correct this issue, Response Generator now truncates the CTX01-02 after 35

characters.

Hotfix 3

FINS-898 DocumentSplitter was not creating an SE when splitting at the ISA level for good

files unless the CalcValidSE01=1. This has been corrected.

Hotfix 2

FINS-906 An issue causing validation to stop when the AMT02 length is greater than 55

characters has been resolved.

Hotfix 2

FINS-908 A new APF File Option, ContinueAfterSQLErrors, allows validation to continue

when a communication issue is encountered during validation.

No

FINS-909 Response Generator no longer creates an invalid 999 when the source

document has a missing or invalid ST01.

No

FINS-910 Under certain conditions, an invalid TA1 was created from a file with errors.

Response Generator now generates return code 198 when a TA1 fails validation.

No

FINS-914 Changes were made to string creation in the OutputIK3() function to prevent

intermittent Response Generator crashes.

Hotfix 2

FINS-931 Instream and TIBCO Foresight® HIPAA Validator® Desktop no longer use

external code list NDC. Therefore, mention of it was removed from the following

user document:

ExtendingCodeTables.pdf > External Code Table List

No

FINS-953 An issue causing Response Generator to create a 999A response document for

an incomplete results file was corrected.

Hotfix 3

FINS-959 Added Library to the list of EDISIM® modules that do not support HL7. Change

was made in the following user document:

HL7.pdf > HL7 in TIBCO Foresight Products

No


Change

Request ID Summary

Originally

contained

in a Release

8.5.0

Hotfix?

FINS-965 Instream was updated to generate an error when the maximum number of bytes

in an element is exceeded, even if CheckTrailingBlanks is disabled

(CheckTrailingBlanks=0).

No

FINS-967 Response Generator was enhanced to handle BP** SVALU records for 277CA

and 277P.

No

FINS-971 DocumentSplitter erroneously required a report file path/ filename when the -cd

(disable/do not create a report) parameter was specified. This has been

corrected.

No

FINS-972

An issue causing Response Generator to crash if detail file records are not

generated during validation has been corrected.

No

FINS-980

(Sun Solaris 64-bit on SPARC only) An issue causing a memory leak was

resolved.

Hotfix 3

FINS-995 User documentation for the SaveCurrentSegment business rule was updated to

note that the rule works with the GetValueFromSegment rule only; it cannot be

used with any other rule. Change was made in the following user document:

BusinessRules.pdf > Business Rules Reference > Variable Business Rules >

SaveCurrentSegment

No

FINS-1003 Error message ranges for 5010 278 were updated as follows:

X215I-X215R - 48000-48299

X216A-X216N- 48300-48599

X217Q-X217R- 43000-43299

Change was made in the following user document: ErrorMessageNumbers.pdf.

No

FINS-1004

and

FINS-1009

(Validations using X12-40xx guidelines only) Validation incorrectly reported

missing trigger segment errors rather than use segments occurring later in the

guideline. Validation was updated and no longer aligns a segment within a loop if

that loop's trigger segment has not yet been seen.

Hotfix 3

FINS-1006 Instream now supports Red Hat Enterprise Linux Server versions 7.x. Hotfix 3

FINS-1011 Documentation for the Response Generator -o999 parameter has been

expanded to explain the differences between 999 5010X231/231A responses

and 999 5010 responses.

No

FINS-1014

and

FINS-1037

Under certain conditions, Response Generator created an extra NTE segment in

an 824 response. This has been corrected.

No


Change

Request ID Summary

Originally

contained

in a Release

8.5.0

Hotfix?

FINS-1024

(Validations using X12-3060 guidelines only) Validation incorrectly reported

missing trigger segment errors rather than use segments occurring later in the

guideline. Validation was updated and no longer aligns a segment within a loop if

that loop's trigger segment has not yet been seen.

Hotfix 4

FINS-1025 (Validations using the following guidelines: X12-2002, X12-3010, X12-3040,

X12-3050, X12-3060, X12-4030, X12-4050, and X12-5010) Validation incorrectly

reported missing trigger segment errors rather than use segments occurring later

in the guideline. Validation was updated and no longer aligns a segment within a

loop if that loop's trigger segment has not yet been seen.

No

FINS-1026 An issue causing erroneous STRUS/E positions on XML validations has been

resolved.

Hotfix 4

FINS-1028 An issue causing Instream to stop when validating XML files has been corrected. Hotfix 4

FINS-1034 Segment Value Records can now be used in XML data. No

FINS-1041 Instream was updated to better handle control and escaped-control characters in

XML files.

No

FINS-1043

A zero position on the final STRUE record (End of Transaction) in a UTF-8 flat

file validation caused a Java exception fault in TIBCO BusinessConnect™. This

has been corrected.

Hotfix 5

FINS-1049 HIPAA-specific X12 response fields in the DTL record are now left blank for non-

X12 validations.

No

FINS-1050 When processing a 5010-275 with attachment, if the byte count of the BIN02

does not equal the count in the BIN01, Instream outputs a 'Binary Segment Error'

message. This allows for generation of a valid detail file. Previously, Instream

failed without generating an error.

No

FINS-1051 A new structure record, 1000DDTPClaimServiceDate, was created and added to

the 5010-275X210.std and 6020-275X314.std.

No

FINS-1052 Instream now generates an error when one of the LS/LE pair is missing in a

5010X279 transaction.

No

FINS-1057

Additional checking was added to the Java API to better handle invalid

parameters.

Hotfix 5

FINS-1058 A missing Instream\DemoData file was restored for use with the DataSwapper

tutorial.

No


Change

Request ID Summary

Originally

contained

in a Release

8.5.0

Hotfix?

FINS-1092 999 AK101 and AK102 information was updated to indicate that the:

-AK101 is from the initiating transaction’s GS01

-AK102 is from the initiating transaction’s GS06

Change was made in the following user document:

ResponseGeneratorTechnicalManual.pdf > Appendix E: Response Document

Contents > 999 Structure and Data Sources > Table

No

FINS-1157 Documentation of the validation profile settings needed for Response Generator

were updated to include DTL=1. Change was made in the following user

document:

ResponseGeneratorTechnicalManual.pdf > Introduction > What you need

before using Response Generator

No


Appendix B – No Future Guideline Changes Listing

Changes are no longer being incorporated into these guidelines:

Guideline type Guideline

HIPAA Guideline 4010

Non-Addenda

Types 1-7

4010270.std

4010271.std

4010276.std

4010277.std

41-278RP.std

41-278RQ.std

4010-820.std

4010834.std

4010-835.std

4010837D.std

4010837I.std

4010837P.std

PDSA820.std (removed from Document Splitter)

PDSX820.std (removed from Document Splitter)

PDSA835.std (removed from Document Splitter)

PDSX835.std (removed from Document Splitter)

PDSA837D.std (removed from Document Splitter)

PDSX837D.std (removed from Document Splitter)

PDSA837I.std (removed from Document Splitter)

PDSX837I.std (removed from Document Splitter)

PDSX837P.std (removed from Document Splitter)

PDSX837P.std (removed from Document Splitter)

HIPAA Guideline 4010

Addenda

Types 1-7

B41A270

B41A271

B41A276

B41A277

41A278RQ

41A278RP

B41A820

B41A834

B41A835

B41A837P (*CCI)

B41A837D

B41A837I


Guideline type Guideline

HIPAA GuidelinePlus 4010

Types 1-7 (PDSA)/

Types 1-2 (PDSX)

PDSA270/PDSX270

PDSA271/PDSX271

PDSA276/PDSX276

PDSA277/PDSX277

PDSX277U

PDA278RQ/PDX278RQ

PDA278RP/PDX278RP

PDSA820/PDSX820

PDSA834/PDSX834

PDSA835/PDSX835

PDSA837P (*CCI)/PDSX837P

PDSA837D/PDSX837D

PDSA837I/PDSX837I

PDSA997

4010-997

HIPAA 4050

Addenda

Types 1-7

4050-275

4050-277

HIPAA Guidelines 5010

Pre- Errata (pre-June 2010)

Types 1-7

NOTE:

Until April 1, 2011, fixes required in the base

guideline, and NOT due to a June 2010 Errata

change, were updated. After April 1, 2011, no further

maintenance of these guidelines will be done.

5010-835-A0.std

5010837DA1.std

5010837IA1.STD

5010837PA0.STD

5010-MEDICAREA-A1.STD

5010-MEDICAREB-A0.STD

PDSA5010835-A0.STD

PDSA5010837D-A1.STD

PDSA5010837I-A1.STD

PDSA5010837P-A0.STD

PDSA5010MEDICAREA-A1.STD

PDSA5010MEDICAREB-A0.STD

Documents

TIBCO Foresight® Instream® - TIBCO Software · Instream Release Notes 1 Release Notes for TIBCO Foresight® Instream® Release 8.7.0 Instream® automates transaction flow and validates