Description

IBM WebSphere Business Integration Collaborations for HIPAA Transactions 1.1.1 Fix Pack

Prerequisites

• IBM WebSphere InterChange Server 4.2.0 or higher
• IBM WebSphere Business Integration Collaborations for HIPAA Transactions 1.1.1

APARs Included

1.1.1

JR19600 Collaboration Enhancements

The IBM WebSphere Business Integration Collaborations for HIPAA Transactions 1.1.1 Fix Pack includes changes to HIPAA collaborations and underlying HIPAADB database tables needed to support limited batch message processing. Installations that use real time messages exclusively will not benefit from the enhancements contained in this Fix Pack.

Files included in this Fix Pack:

• Readme.htm - this file
• BIA_HIPAA_Patch1.jar - changed collaborations
• BIA_Create_HIPAA111WIN_TablesPatch1.txt - example DB2 table creation script

Collaboration changes

Changed templates are:

• HIPAA270
• HIPAA270Prov
• HIPAA271
• HIPAA271Prov
• HIPAA278Req
• HIPAA278ReqProv
• HIPAA278Resp
• HIPAA278RespProv
• HIPAA837Inst
• HIPAA837InstProv
• HIPAA837Dental
• HIPAA837Dentallrov
• HIPAA837Prof
• HIPAA837ProfProv

The 270, 271, and 278 collaborations now check for a Trace Number attribute in their BOs and store the Trace Number in their respective database tables as a key field. If a Trace Number segment (TRN) cannot be found, the collaborations default the Trace Number value to "TRN". The attribute from the TRN segment is Reference_Identification (30 characters). The search order for the TRN segment in 270, 271, 278Req, 278Resp payer and provider versions is from innermost loop outward. The first loop that contains a TRN will be used.

The modified collaborations along with the segments they search for the Trace Number are:

• HIPAA270, HIPAA270Prov, HIPAA271 ,HIPAA271Prov
• 2000A.2000B.2000C.2000D.TRN, 2000A.2000B.2000C.TRN

• HIPAA278Req, HIPAA278ReqProv, HIPAA278Resp, HIPAA278RespProv
• 2000A.2000B.2000C.2000D.2000E.2000F.TRN, 2000A.2000B.2000C.2000E.2000F.TRN, 2000A.2000B.2000C.2000D.TRN, 2000A.2000B.2000C.TRN

The 837Inst and 837InstProv collaboration templates have been enhanced to look for the Provider ID information in the 2000A.2010AA.NM1.Last_Name_or_Organization_Name attribute in addition to the 2000A.PRV and 2300.2310E.PRV locations.

All 837 collaborations include a new collaboration property called CLAIMID_REQUIRED.

• If true, require the 2300.CLM.Claim_Submitter_s_Identifier attribute to be present, if not present fail the flow.
• If the TracerID is missing and if the property is true, set the TracerID = ClaimID.
• If the TracerID is missing and the property is false, create the unique TracerID. This is the default setting and results in the collaboration operating exactly as it did before this change.

JR19600 Database changes

The script supplied with this Fix Pack updates all tables on HIPAADB. AIX users must transfer the script to the target machine using ftp or a similar transfer program. The script drops all the data on those tables in the process. If you have data that you do not wish to lose on the HIPAADB, see your DB administrator before proceeding. Manual table changes or an export/import are required in order to keep existing table data intact.

The script has been modified to add the TRACENUM column to the INQUIRYIN, INQUIRYINPROV, SVCINQ, SVCINQPROV tables and make it one of the key fields. The script has also been modified to increase the PROVID column width from 30 to 35 VARCHARS. This applies to the tables:

• CLAIMIN
• CLAIMINPROV
• CLAIMRSP
• CLAIMRSPPROV
• PROCIN
• PROCINPROV
• PROCRSP
• PRCORSPPROV

Installation Instructions

JR19600

Before installing this Fix Pack, backup all affected collaborations. Please see the installation instructions in WebSphere Business Integration Collaborations for HIPAA Transactions 1.1.1.

1. Install BIA_HIPAA_Patch1.jar using the same procedure used to install the original BIA_HIPAA.jar. Note that installing the BIA_HIPAA_Patch1.jar overwrites all same named templates in your CSM Library.
2. The new collaboration property added to the 837 collaboration templates requires that you re-create each of the 837 collaboration objects.
3. If you are installing into a running system, deploy all changed templates with compile.
4. Deploy the re-created collaboration objects.
5. Stop your ICS.
6. Update all affected tables on the HIPAADB database.
7. Restart your ICS.