Originally posted by: SRW

Hi,

How can I find the exact error in EDI data. I have a pass through map which fails in input validation. I tried changing the map setting and made the validation custom and made other setting ignore so that it continues through the data.
Still I get input type contains errors and since the input validation stops I dont get any ouput. Neither from the audit log nor from the trace I can figure out where exactly the data is failing validation.

Kindly suggest how should I go about and correct the input data. I am attaching the data file.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: SystemAdmin

Can you post the trace file for the input card too?
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: SRW

PFA the trace file. If I use just the first ST-SE segment and remove the other ones it runs fine. For the 2nd ST-SE onwards it has some issues in the subscriber loop. but I cant make out where exacly it is failing.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

Errors in the trace file are usually indicated by the text "INVALID" - if you do a search for this you'll see it appears on line 12955:

Data at offset 4537 (
'*686868686<CR><LF>N3*1') is INVALID data of TYPE

this relates to the following line in the message:

NM1*QC*1*CLIFTON*WILLIAM**** *686868686

it looks to me like the element with a space in it is mandatory and that the space is also a pad character - so the mandatory element is effectively empty.

An audit log with the data audit settings switched on should highlight this fairly easily.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: SystemAdmin

Looking through the trace, there are other errors in the trace file - just keep looking for "INVALID" and then fixing the data or comparing it to the type tree to check.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: SRW

I corrected many of the invalid part even though it was very tedious to find which part of the data is causing it. but still left with one invalid data in GS segment which gives

status="E09">GE Segment V5010X223A1</object> in the audit log.

The trace log gives
Level 2: Offset 6871, len 4, comp 4 of 4, #1, DI 0000002D0019:)
Data at offset 6871 ('*6*1') failed COMPONENT RULE test
for component number 4, TYPE X'19E7' (#837 F5010X223A1 Inbound Partner Funct'lGroup ANSI EDI).

(Level 1: Offset 107, len 6770, comp 5 of 6, #1, DI 0000002D0019:)
Data at offset 107 ('GS*HC*PROFSERV*D...') is INVALID data of TYPE
X'19E7' (#837 F5010X223A1 Inbound Partner Funct'lGroup ANSI EDI).

(Level 1: Offset 107, len 6770, comp 5 of 6, #1, DI 0000002D001A:)
Data at offset 107 ('GS*HC*PROFSERV*D...') is INVALID data of TYPE
X'19D5' (F5010X223A1 Inbound Partner Funct'lGroup ANSI EDI).

(Level 1: Offset 107, len 6770, comp 5 of 6, #1, DI 0000002D001B:)
Data at offset 107 ('GS*HC*PROFSERV*D...') is INVALID data of TYPE
X'002F' (Inbound Partner Funct'lGroup ANSI EDI).
If I can have some clue it will be helpful.
Please find attached the new data file.
Sobha
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SRW

Also attaching the trace file
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: SystemAdmin

Have you tried checking the component rule in the element reporting the error - this probably shows how the segment count validation is done.

Also have you tried validating the data with , this gave me the following for your file:

At envelope ZZ/HEALTHCARE_PS->ZZ/HEALTHCARE_DEV, Ctrl=000000007: At group PROFSERV->DEVELOPMENT, Ctrl=1: At message 837:0123 Ctrl=0001: In segment B.HL.CLM.CLM: • Invalid code 
' ' At message 837:0124 Ctrl=0002: • The trailer reports 48 segments but there are really 46. In segment B.HL.CLM.CLM: • Invalid code 
' ' At message 837:0123 Ctrl=0003: • The trailer reports 61 segments but there are really 63. In segment B.HL.CLM.CLM: • Invalid code 
' ' In segment B.HL.CLM.CLM: • Invalid code 
' ' At message 837:0123 Ctrl=0004: • The trailer reports 42 segments but there are really 40. In segment B.HL.CLM.CLM: • Invalid code 
' ' At message 837:0124 Ctrl=0005: • The trailer reports 44 segments but there are really 42. In segment B.HL.CLM.CLM: • Invalid code 
' ' At message 837:0324 Ctrl=0006: • The trailer reports 44 segments but there are really 43. In segment B.HL.CLM.CLM: • Invalid code 
'

it looks like the segment counts are wrong and you've got some invalid codes.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: SRW

I am using the Hipaa X12 type tree. It does have a count rule for counting segment in 837 txn. I checked the data thorughly with the technical report for 837 i. I could not make out any invalid data.
where did you get the below trace for

"In segment B.HL.CLM.CLM: "

I checked the CLM part in Claim segment. It seems to be fine as I deleted some other portion of data it becomes valid and this CLM part is holding good.

Is there any way to know what part of the data is exactly causing this error?
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: SystemAdmin

there's a space at the end of each CLM segment - possibly this is a mandatory element, check it against the type tree and EDI Notepad.

>It does have a count rule for counting segment in 837 txn.
have you corrected the values in the SE segments?
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SRW

If I just retain the first ST-SE segment and delete all other ST-SE the validation is running fine and the input file does produce an output file. in that CLM segment also there is a space. I didnt do any correction in SE segments. what type of correction should i do. I just validated with the 837 i manual and it looks fine.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

What is the component rule that the map trace reports as a problem?
i.e.

Data at offset 6871 (
'*6*1') failed COMPONENT RULE test 

for component number 4, TYPE X
'19E7' (#837 F5010X223A1 Inbound Partner Funct
'lGroup ANSI EDI).

#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: SRW

It is the same rule for the GS_GE segment where the count is happening and it is failing
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

ok, but what is the rule?
I don't have a copy of the type tree!
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: Rich_McFate

What is it you're trying to do here?

The HIPAA Pack has several type trees -- each of which enforces a different level of HIPAA compliance.

If you have the HIPAA X12 pack, you can use the compliance_check map to generate a HIPAA acknowledgment. You would use the settings in the compliance_check_paramater.dat file to the compliance level you're interested in (i.e. Type I, Types I&II, Types I-IV). There is another setting at the bottom of the file that will let you generate an .html file that will contain English descriptions of the errors. If all you're trying to do is create compliant data, that's where I would start.

If all you're trying to do s create a transformation for data that was validated outside your map, you should be using the hippa_x12_ruleless.mtt Type Tree, which has minimal checking (i.e. it assumes the data is valid).

In this latter case, I suggest you use the most recent fix pack (4.3.1.1), in which the ruleless tree has had some changes made to eliminate some Type II and Type IV rules that had previously been included.
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SRW

The 5010 837 i data is generated by transforming the 4010 complaint data.
I need to check if the 5010 data is a compliant data and if it is failing what is the reason.

I noticed the moment I include the second ST-SE segment it fails compliance. So I am trying to find what is the reason. but it just gives in the audit log and trace that the
status="E09">GE Segment V5010X223A1</object>, Data at offset 107 ('GS*HC*PROFSERV*D...') is INVALID data of TYPE X'19E7' (#837 F5010X223A1 Inbound Partner Funct'lGroup ANSI EDI).
I tried running the compliance checker with the existing files just to see the html file. but it is not generating the html file inspite of putting HIPAA_TAck_Enabled="Y".

Do I need to change any other setting ?
Kindly suggest.

I am finding out due to what reason the 5010 data is failing compliance and what correction needs to be done.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: Rich_McFate

Out of the box, the compliance_check map should perform Types I,II,III,and IV validation and it should deliver a 997.

The only change you need to make in the out-of-the-box .dat file is to set HIPAA_TAck_Enabled="Y" (don't forget to remove the ; at the beginning of the line).

You might also want to set HIPAA_TAck_Accepted="A" temporarily. That will give you the ../data/compliance_check_TAck.html file even if there are no errors.

If you're running this from the Design Studio, look in the ../data directory for compliance_check_997h.out. If you don't see that, then it's possible the map is not completing correctly.

Look at ../data/compliance_check_summary.out. Check to make sure there are no errors in there that might be causing the compliance_check map to deliver no results.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: Rich_McFate

I'm attaching the .html file I got using your test data.

In this case, you won't get a 997. You're goin to get a TA1 because your ISA sement is invalid. You need to include the repetition character (e.g. ^ ) after the InterchangCtrlStandardsID

Three of the transactions are also invalid due to incorrect segment counts in the SE Segment.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: SRW

i hadnt removed the ;. I could generate the html files.
i even rechecked the 4010 and the 5010 files to see if any segment is missed out. but unfortunately i am struggling in that part.
since only 3 ST_SE segments are invalid i removed them and also put the ^ to see if the pass through map is working fine. but still the validation is failing. 4010 files are geting validated.
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SRW

i will put a count of the segments and correct the number and see. But still nt sure for the valid ST_SE ones why is it failing.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: SRW

After putting the count it is working fine. Thx a lot.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: jvanboga

Is this what you are looking for?
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender