File Viewer

Aug 28, 2011 at 11:09 PM

Anyone know any good EDI/X12 file viewers components (as in an embeddable C# component/control)?

Ideally, it should be customizable so as to simply the file structure so it's human readable by an end user.

Thanks.

Coordinator
Sep 1, 2011 at 11:19 PM

You could write your own app using the Interchange object SerializeToX12 method with addWhitespace=true to write out the x12 with indents such as:

ISA*00*          *01*SECRET    *ZZ*SUBMITTERS.ID  *ZZ*RECEIVERS.ID   *030101*1253*^*00501*000000905*1*T*:~
  GS*HC*SENDER CODE*RECEIVER CODE*19991231*0802*1*X*005010X222~
    ST*837*0021*005010X222~
      BHT*0019*00*244579*20061015*1023*CH~
      NM1*41*2*PREMIER BILLING SERVICE*****46*TGJ23~
        PER*IC*JERRY*TE*3055552222*EX*231~
      NM1*40*2*KEY INSURANCE COMPANY*****46*66783JJT~
      HL*1**20*1~
        PRV*BI*PXC*203BF0100Y~
        NM1*85*2*BEN KILDARE SERVICE*****XX*9876543210~
          N3*234 SEAWAY ST~
          N4*MIAMI*FL*33111~
          REF*EI*587654321~
        NM1*87*2~
          N3*2345 OCEAN BLVD~
          N4*MAIMI*FL*33111~
        HL*2*1*22*1~
          SBR*P**2222-SJ******CI~
          NM1*IL*1*SMITH*JANE****MI*JS00111223333~
            DMG*D8*19430501*F~
          NM1*PR*2*KEY INSURANCE COMPANY*****PI*999996666~
            REF*G2*KA6663~
          HL*3*2*23*0~
            PAT*19~
            NM1*QC*1*SMITH*TED~
              N3*236 N MAIN ST~
              N4*MIAMI*FL*33413~
              DMG*D8*19730501*M~
            CLM*26463774*100***11:B:1*Y*A*Y*I~
              REF*D9*17312345600006351~
              HI*BK:0340*BF:V7389~
              LX*1~
                SV1*HC:99213*40*UN*1***1~
                DTP*472*D8*20061003~
              LX*2~
                SV1*HC:87070*15*UN*1***1~
                DTP*472*D8*20061003~
              LX*3~
                SV1*HC:99214*35*UN*1***2~
                DTP*472*D8*20061010~
              LX*4~
                SV1*HC:86663*10*UN*1***2~
                DTP*472*D8*20061010~
    SE*42*0021~
  GE*1*1~
IEA*1*000000905~
Otherwise if there are only a few transaction sets that you need, I could write some xslts for you that give you a catalog of what's contained in the file.  If that's what you would like, suggest it as a Feature and we will get that work prioritized.

Sep 20, 2011 at 6:36 PM

Hello,

i am trying to parse an x12 file to XML by this code

Dim interchange = parser.Parse(msgString).Serialize()

And it wors fine in most cases exept this one:

ISA*00* *00* *28*PPPPP *28*XXXXXX *100915*1002*^*00501*091536298*0*T*:~GS*HN*PPPPP*0*20100915*100208*26*X*005010X214~ST*277*000000001*005010X214~BHT*0085*08*091536332*20100915*09153600*TH~HL*1**20*1~NM1*PR*2*CARRIER NAME*****PI*PPPPP~TRN*1*PPPPP20100915000003~DTP*050*D8*20100915~DTP*009*D8*20100915~HL*2*1*21*1~NM1*41*2*TEST SUBMITTER*****46*XXXXXX~TRN*2*000008~STC*A1:19:PR*20100915*WQ*4500~QTY*90*1~AMT*YU*4500~HL*3*2*19*1~NM1*85*2*PROVIDER NAME*****XX*1234567890~TRN*1*IA92330H1..0001~STC*A1:19:PR**WQ*4500~QTY*QA*1~AMT*YU*4500~HL*4*3*PT~NM1*QC*1*TEST**PART**A*MI*111111111F~TRN*2*IA92330H1..0001~STC*A2:20:PR*20100915*WQ*4500~REF*1K*21025800000107TST~REF*BLT*131~DTP*472*RD8*20090701-20090701~SVC*HC:22305:22*350*****1~STC*A3:122**U*******A3:153:82~REF*FJ*11SE*27*000000001~GE*1*26~IEA*1*091536298~

error says:

X is not a valid subelement separator in position 105 of the file.

What seems to be wrong?

 

Sep 20, 2011 at 7:40 PM

and another example taken from http://www.ngscedi.com/5010/5010.htm

test file is:

ISA*00*          *00*          *ZZ*EMEDNYBAT      *ZZ*ETIN           *110311*0512*^*00501*000001120*0*T*|~GS*HN*EMEDNYBAT*ABCD*20110311*051225*1120*X*005010X214~ST*277*000001120*005010X214~BHT*0085*08*3920394930203*20110311*051225*TH~HL*1**20*1~NM1*PR*2*NYSDOH*****FI*141797357~TRN*1*000001120~DTP*050*D8*20110311~DTP*009*D8*20110311~HL*2*1*21*1~NM1*41*1*TEST*TEST****46*ETIN~TRN*2*11200001~STC*A1|20*20110311*WQ*199.14~QTY*90*1~AMT*YU*199.14~HL*3*2*19*1~NM1*85*2*PROVLNAME*****XX*123456789~TRN*1*1107000000000001FF~HL*4*3*PT~NM1*QC*1*CLILNAME*CLIFNAME*CLIMI***MI*XX99999X~TRN*2*3920394930203~STC*A7|562|85*20110311*WQ*199.14~REF*1K*1107000000001120~REF*BLT*731~DTP*472*D8*20090311~SE*24*000001120~GE*1*1120~IEA*1*000001120~ 

error says:

Segment 'TRN*1*000001120' in position 6 within transaction '000001120' cannot be identified within the supplied specification for transaction set 277.
Parameter name: 277

Sep 20, 2011 at 10:25 PM

Please disregard first exemple. Error was found.

thank you

Dec 28, 2011 at 10:21 PM

Hello!

I'm also receiving the same "Segment 'TRN....' in position 6 within transaction" error as alex above. Does anyone know how to resolve this error?

Thanks!

Nick

Dec 28, 2011 at 10:50 PM
I got a Segment error on a test 837 file I got from a client but it actually was a malformed claim with control loops out of order.
I had to find that by going to the 837 spec. I found the record in error by debugging until the 'throw' statement. Examined the data in error and then used that information to search into my x12 file. The physical line in error was one below the line stated in the throw statement. ie in the throw stated position 1136 and it was line/segment 1137. I say line because my file has a line feed after every ~ so each segment is it's own line.

I don't know anything about the 277 format but I hope the above information helps you find the spot in error.

Doug


On Wed, Dec 28, 2011 at 4:21 PM, nzacca <notifications@codeplex.com> wrote:

From: nzacca

Hello!

I'm also receiving the same "Segment 'TRN....' in position 6 within transaction" error as alex above. Does anyone know how to resolve this error?

Thanks!

Nick

Read the full discussion online.

To add a post to this discussion, reply to this email (x12parser@discussions.codeplex.com)

To start a new discussion for this project, email x12parser@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe or change your settings on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com


Jun 4, 2012 at 8:36 PM

I am getting the same 277 as alexbrodsky above, has the error been identified / resolved?

"Segment 'TRN*1*000001120' in position 6 within transaction '000001120' cannot be identified within the supplied specification for transaction set 277." 

I am getting this (with my identifiers) when trying to parse a 277 file that passes other validation checks.  Here are the first few lines in the file for reference:

ISA*00*          *00*          *30*590909099      *ZZ*590909000      *120127*0355*^*00501*000203263*0*T*:~
GS*HN*590909099*590909000*20120127*035502*203263*X*005010X214~
ST*277*0001*005010X214~
BHT*0085*08*203263.1*20120127*035502*TH~
HL*1**20*1~
NM1*AY*2*AMERISYS*****FI*2323232323~
TRN*1*20060831001~
DTP*050*D8*20120127~
DTP*009*D8*20120127~
HL*2*1*21*1~

.......

Thanks!

CS

Coordinator
Jun 5, 2012 at 3:26 AM

I have added the file from alexbrodsky and bogeyone to the unit tests and was not able to reproduce the error.

There are multiple versions of the 277 and some fixes were added on 1/13/2012 for the 5010X214.

If you have the first few segments of the transaction that matches the error message instead of the first transaction in the file, I can continue to troubleshoot.

Jun 5, 2012 at 4:24 PM
Thank you for your quick response. We were using an older release and after downloading the current release I can't duplicate the problem. I apologize for my lack of diligence. We appreciate the X12 project, it has made our development much more efficient.

Creston Swaim


From: [email removed]
To: [email removed]
Date: Mon, 4 Jun 2012 20:26:39 -0700
Subject: Re: File Viewer [x12parser:270711]

From: dstrubhar
I have added the file from alexbrodsky and bogeyone to the unit tests and was not able to reproduce the error.
There are multiple versions of the 277 and some fixes were added on 1/13/2012 for the 5010X214.
If you have the first few segments of the transaction that matches the error message instead of the first transaction in the file, I can continue to troubleshoot.
Read the full discussion online.
To add a post to this discussion, reply to this email (x12parser@discussions.codeplex.com)
To start a new discussion for this project, email x12parser@discussions.codeplex.com
You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on CodePlex.com.
Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at CodePlex.com