PH18893: INVALID EDI DATA IS NOT BEING DETECTED BY THE IBM TRANSFORMATIONEXTENDER ADVANCED DEENVELOPE SERVICE

APAR status

• Closed as program error.

Error description

• An invalid EDI data file (HIPPA/X12) is not being detected by
  the IBM Transformation Extender Advanced Deenvelope Service. The
  processing of the invalid data shows success instead of the
  expected failure.
  
  This occurs when the segment identifier/tag is not present.
  

Local fix

• ITXA: TS002913310 / github #20
  TR / TR
  Circumvention: None
  

Problem summary

• Problem Description: Invalid HIPAA data
  returns "SUCCESS" status from ITXA service when WTX compliance
  check produces a "Rejected" status but with no reported errors.
  

Problem conclusion

• Problem Conclusion: SPE parsed the WTX 999 for the compliance
  check operation but did not retain the transaction level codes
  reported by the AK5 and IK5 segments. This was not an oversight.
   SPE purposefully did not read these codes because the
  assumption was transaction level errors would be reported by
  running the transform map and the errors from the compliance
  check would be double-reported.
  
  However, in the customer case, there is no transform map.
  Therefore, no transaction level errors are reported.
  Subsequently, this leads to a false service report of SUCCESS
  and no error reporting for the bad transaction. The generated
  INT-1 999 acknowledgment is also not correct because it does not
  contain the IK5 segment.
  
  There are other errors exposed by this defect: The 999 specific
  transaction syntax error codes (e.g. I5) were not being parsed
  and reported properly in the SPE generated INT-1 999
  acknowledgment. The AK9 "E" (accepted with errors) status was
  not being reported properly in the
  InterchangeComplianceReport.xml document.
  
  The following fixes have been applied:
  1) Parse the WTX 999 for the transaction level error codes when
  creating the intermin compliance report.
  2) Fixed parsing of the 999-specific transaction syntax error
  codes and their respective mappings to the compliance report.
  3) When the WTX and SPE transaction compliance reports are
  merged check for duplicate error reporting and toss out the
  duplicates.
  
  Platforms Affected: All
  Customers Affected: Customers using WTX compliance checking for
  HIPAA where the inbound ST envelope does not use a
  transformation map and errors exist at the transaction level.
  Applies to: SPE.COMMON.9.0.2.0, SPE.COMMON.10.0.1.0
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  ITX ADV

• Fixed component ID

  5724Q2301

Applicable component levels