ISA11 field does not allow for a ^ but does allow U

Question

We have a process for the HIPAA elegibility and the claim status transactions. Both are using the same trade partner and the files have similar data on the ISA segment. The problem is that when I use the ^ in the elegibility transaction, biztalk will process the file with no problems. However, if I put that same charachter in the ISA11 for the claim status transaction, I get the error below. It does not make any sense why one transaction will allow for the ^ and the other does not. I know the claim status file are compliant. I have tried other HIPAA idenfiers, but get the same error. The only thing that will work is the U, but a trade partner we have can not use that value. They have to use another HIPAA value, but Biztalk is not allowing me to use any other value for the claim status transaction. Has anyone seen this?

Error encountered during parsing. The X12 interchange with id '000000007', with sender id '5999997      ', receiver id '5999998      ' had the following errors:

Error: 1 (Miscellaneous error)
 16: Invalid Control Standard Identifier

Error: 2 (Field level error)
 SegmentID: ISA
 Position in TS: 1
 Data Element ID: ISA11
 Position in Segment: 11
 Data Value: ^
 7: Invalid code value

---

Answer 1

Carlos,

 

ISA11 should be always U.  In the http://schemas.microsoft.com/Edi/X12ServiceSchema#ISA schema, ISA11 is restricted to have enumeration value as U .

If you have any other value in ISA11, we will get Compliance Error.

I have come across X12 files from Trading partner with ISA16 as ^ . I hope we are not discussing about ISA16.

Can you post the ISA Segment for both 270 and 276 files.

---

Sathish - http://blog.tsathish.com

Answer 2

Hi,

    In the party settings there is a field "Use ISA11 as repetition separator" , In Party as interchange sender -> X12 interchange processing. You need to mark it true if you are using ISA11 as other than 'U'.

 

Thanks

Gyan

---

If this answers your question, please mark it as "Answered".

Answer 3

Gyan,

It worked, it's good to know.

 

 

---

Sathish - http://blog.tsathish.com

Answer 4

Thank uyuo Gyan. That did it. I was able to use the ^ as well.

---

Please Indicate "Mark as Answer" if this Post has Answered the Question