IBM Support

WebSphere Transformation Extender Pack for HIPAA EDI V4.3.2.2 Fix List

Release Notes


Abstract

This document provides information about the release of WebSphere® Transformation Extender Pack for HIPAA EDI V4.3.2.2.

Content

Note: Some APAR URLs may not work due to the APAR not having reached the publish phase.


APARDescription
PM38829 HIPAA COMPLIANCE CHECK MAP DOES NOT PRODUCE A TA1 FOR AN INVALIDHIPAA VERSION VALUE IN THE GS08 ELEMENT
PM37283 HIPAA VALIDATION FAILURE OCCURS DUE TO 5010X222 2010CA LOOP NM104 FIELD DEFINED AS REQUIRED BUT SHOULD BE OPTIONAL
PM45978 276 LEVEL 4 ISSUE AT COMPLIANCE CHECK
PM46677 277CA REPEATS BILLING PROVIDER LOOP IF SAME PROVIDER IN MULTIPLE 2010AA LOOP
PM40767 276 FILE (GS08 005010X212) WITH 3 DECIMAL PLACES IN THE AMT02 SEGMENT IN LOOP 2200D IS NOT REJECTED BY COMPLIANCE CHECK MAP
PM47516 HIPAA PACK NOT ENFORCING THAT BHT06 MUST BE PRESENT WHEN BHT02 = 01 FOR A 5010X279A1 270 TRANSACTION
PM38718 HIPAA ISSUE REGARDING WHETHER SV105 (1331) SHOULD NOT BE SUBMITTED WHEN IT IS THE SAME VALUE AS CLM05-1
PM37278 HIPAA COMPLIANCE CHECK MAP FAILS TO GENERATE A 999 WHEN THE REPETITION SEPARATOR IS THE ASTERISK ( * ) CHARACTER
PM37649 TA1 IS NOT CREATED BY COMPLIANCE CHECK MAP WHEN ISA11 AND ISA16 CONTAIN THE SAME VALUE IN 271 TRANSACTION FOR HIPAA 5010
PM36900 A HIPAA 5010X212 276 TRANSACTION IS REJECTED WHEN TWO NM1 SEGMENTS ARE PRESENT IN THE 2100C LOOP
PM38065 TA1 IS NOT CREATED BY COMPLIANCE CHECK MAP WHEN ISA11 AND ISA16 CONTAIN THE SAME VALUE IN HIPAA 5010 271 TRANSACTION
PM38293 HIPAA 5010X231A 999 CTX06-1 FIELD DEFINED AS NUMERIC IN IMPLEMENTATION GUIDE BUT DEFINED AS TEXT IN HIPAA TYPE TREES
PM38152 COMPLIANCE MAP GENERATES INVALID 999 FOR CTX06-1 WITH AN ALPHANUMERIC CXXX VALUE.
PM38495 COMPLIANCE CHECK IS FAILING A 5010 FILE BUT PASSING A 4010 FILE THAT DOES NOT CONTAIN A 2000 DTP SEGMENT
PM38537 999 FOR 5010X279A1 TRANSACTION 271 NOT REPORTING ERROR WHEN NM103 IS MISSING FOR LOOP 2100A
PM38753 837 DN2 SEGMENT FAILING TYPE 1 VALIDATION INCORRECTLY
PM38952 HIPAA COMPLIANCE CHECK MAP ALLOWS 5010X222A1 837P TRANSACTION TOCONTAIN MULTIPLE DTP_453 IS ALLOWED IN 2300 CLM LOOP
PM39209 5010 835 TRANSACTION, LOOP 2100 NM1 (CROSSOVER CARRIER NAME), SEGMENT SHOULD BE REQUIRED WHEN CLP02 =  19. 20, 21, OR 23
PM40112 HIPAA 4.3.2 COMPLIANCE CHECK MAP FAILS FOR VALID 5010X279A1 271 TRANSACTIONS
PM40185 DATA REJECTED WHEN LN02 = "EN" FOR PRODUCT/SERVICE ID QUALIFIER IN HIPAA 5010X222A1 837 TRANSACTION LOOP 2410
PM41590 HIPAA COMPLIANCE CHECK MAP ERROR: X12CLR277CATXN.MMC DID NOT COMPLETE SUCCESSFULLY ONE OR MORE INPUTS WAS INVALID
PM41484 HIPAA COMPLIANCE CHECK MAP GENERATES AN INCORRECT 999 FOR AN 5010X223A2 837 NM1 SEGMENT WITH AN EXCEEDS MAX USE ERROR
PM42119 HIAPP COMPLIANCE CHECK MAP DOES NOT REJECT 5010X221A1 835 TRANSACTION WHEN MANDATORY 1000A PER_BL IS NOT PRESENT
PM43145 HIPAA COMPLIANCE CHECK NOT REJECTING SECONDARY ID IN 2010BB/REF WHEN 2010AA/NM109 CONTAINS NPI IN 837 TRANSACTION FOR 5010X222A1
PM42798 WHEN $ IS USED AS A TERMINATOR IN THE HIPAA DATA, UNEXPECTED RESULTS OCCUR WITH COMPLIANCE CHECKING
PM42826 HIPAA DATA FAILS THROUGH A VALIDATION MAP, BUT PASSES HIPAA COMPLAINCE CHECK FOR 5010X279A1 271 2100D NM1 DATA
PM43602 HIPAA_X12_SEGMENT.MTT TYPE TREE ALLOWS INCORRECT VALUE 32 FOR V5010X220A1 834 TRANSACTION IN 2000 LOOP FOR INS02 ELEMENT
PM44069 837 DATA PASSES COMPLIANCE CHECK BUT FAILS VALIDATION AGAINST HIPAA_X12.MTT TYPE TREE
PM44079 HIPAA COMPLIANCE REJECTING WHEN NM102 IS 1 AND FIRST NAME/LAST NAME IS MISSING WITH 5010X279A1 271 TRANSACTION
PM44040 HIPAA NOT REJECTING DATA WITH TYPE 4 CHECKING WHEN HI SEGMENT IS NOT PRESENT AT 2000E LOOP AND SV1-07 IS PRESENT
PM44375 HIPAA 5010X220A1 834 TRANSACTION DATA FAILING VALIDATION MAP WITH TYPE 4 TYPE TREE BUT PASSES COMPLIANCE CHECK PROCESS
PM44521 COMPLIANCE CHECK NOT REJECTING DATA WHEN CLP02 HAS A VALUE OF 22 AND CLP05 IS NOT EMPTY
PM46096 HIPAA 5010X217 278 (REQUEST) HL NUMBERING IS NOT BEING CHECKED
PM45235 HIPAA 5010X223 837 TRANSACTION DOES NOT FAIL COMPLIANCE CHECK WHEN DTP01 = 573 IN BOTH 2330B AND 2430 LOOPS
PM46042 NO ERROR MESSAGE PRODUCED FOR WHEN CLP11 ELEMENT IS PRESENT AND CLP12 IS MISSING
PM52178 COMPLIANCE CHECK ACCEPTING 837P 5010X222A1 DATA WHEN SBR SEGMENT IS DEFINED AS SECONDARY AND THERE IS NO LOOP 2320
PM45987 HIPAA TRN03 VALUES DO NOT HAVE TO START WITH A 1, 3 OR 9 FOR 271TRANSACTION
PM46412 NOT GETTING 999 REJECTS WHEN HL04 HAS INCORRECT VALUE FOR 278 5010X217 TRANSACTION
PM46454 HIPAA COMPLIANCE CHECK 277CA INCLUDES ONLY THE FIRST BILLING PROVIDER IF ALL CLAIMS ARE ACCEPTED
PM46320 IF THE CL1 SEGMENT IS MISSING IN A 5010X223A2 TRANSACTION, COMPLIANCE CHECK IS NOT REJECTING THE DATA
PM46389 HIPAA PACK 4.3.2 1 COMPLIANCE CHECK MAP ACCEPTS NON COMPLIANT 5010X223A2 DATA FOR THE 2420A NM1 SEGMENT
PM47222 DMG03 VALUE OF U IS REJECTED IN 997 FROM TMGR BUT NOT REJECTED IN 997 FROM COMPLIANCE CHECK MAP WITH TIP FIX (WTX38475)
PM48349 835 5010 TRANSACTION HAD A NON ZERO BPR02 SEGMENT WHEN BPR01 WAS'H', BUT NO COMPLIANCE ERROR WAS REPORTED
PM48871 5010X222A1 DATA IS BEING REJECTED BECAUSE CR1 IS PRESENT AND THEIR IS NO CRC SEGMENT WITH A CRC01=07 VALUE PRESENT
PM52175 COMPLIANCE CHECK IS NOT REJECTING 5010X220A1 834 DATA WHEN THE N102 VALUE IS MISSING WHEN N101 IS SET TO TV.

[{"Product":{"code":"SSVSD8-1","label":"WebSphere Transformation Extender"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF025","label":"Platform Independent"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"4.3.2.2","Edition":"International","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Product Synonym

Ascential DataStage TX Mercator

Document Information

Modified date:
05 October 2022

UID

swg27024912