Transaction Set Code 837P-5010 isnt working

May 5, 2016 at 3:58 AM
I receive the following parsing error:
Segment 'LIN**N4*01234567891' in segment position 95 within transaction '000011' cannot be identified within the supplied specification for transaction set 837 in any of the expected loops: 2000A[1],2000B[2],2000C[3],2300. 
when processing:
ISA*00*          *00*          *30*111111111111111*ZZ*133052274      *120422*1828*^*00501*113182822*0*T*:~
  GS*HC*222222222222*600540000*20120422*1828*211300001*X*005010X222A1~
    ST*837*000011*005010X222A1~
      BHT*0019*00*211300001-1*20120422*1828*CH~
      NM1*41*2*ABC SUBMITTER*****46*999999999~
        PER*IC*JOHN SMITH*TE*5555551234*EX*123~
      NM1*40*2*XYZ RECEIVER*****46*133052274~
      HL*1**20*1~
        PRV*BI*PXC*207Q00000X~
        NM1*85*2*ABC Group Practice*****XX*1234567890~
          N3*123 MAIN STREET~
          N4*KANSAS CITY*MO*64108~
          REF*EI*123456789~
          REF*0B*654321~
          PER*IC*JOHN SMITH*TE*5555551234*EX*123~
        NM1*87*2~
          N3*123 MAIN STREET~
          N4*KANSAS CITY*MO*64108~
        NM1*PE*2*ANY STATE MEDICAID*****PI*12345~
          N3*123 MAIN STREET~
          N4*KANSAS CITY*MO*64108~
          REF*EI*123456789~
        HL*2*1*22*1~
          SBR*P**GRP01020102******CI~
          NM1*IL*1*DOE*JOHN*T**JR*MI*123456~
            N3*123 MAIN STREET~
            N4*KANSAS CITY*MO*64108~
            DMG*D8*19690815*M~
          NM1*PR*2*ABC INSURANCE CO*****PI*11122333~
            N3*25 MAIN STREET~
            N4*KANSAS CITY*MO*64108~
          HL*3*2*23*0~
            PAT*01~
            NM1*QC*1*DOE*SALLY*J~
              N3*123 MAIN STREET~
              N4*KANSAS CITY*MO*64108~
              DMG*D8*19690815*M~
            CLM*A37YH556*500***11:B:1*Y*A*Y*I*P*AA~
              DTP*431*D8*20050108~
              DTP*439*D8*20060108~
              DTP*484*D8*20050108~
              DTP*360*D8*20050108~
              DTP*297*D8*20050108~
              DTP*435*D8*20030108~
              DTP*096*D8*20050108~
              DTP*050*D8*20051030~
              PWK*OZ*BM***AC*DMN0012~
              AMT*F5*152.45~
              REF*G1*13579~
              REF*F8*R555588~
              REF*D9*TJ98UU321~
              REF*EA*44444TH56~
              REF*9A*RJ55555~
              REF*4N*1~
              REF*9F*12345~
              REF*F8*R555588~
              REF*9A*RJ55555~
              REF*9C*RP44444444~
              K3*STATE DATA REQUIREMENT~
              NTE*ADD*SURGERY WAS UNUSUALLY LONG BECAUSE [FILL IN REASON]~
              CRC*07*Y*01~
              HI*BK:8901*BF:87200*BF:5559~
              HCP*03*100.0000**RPO12345~
              NM1*DN*1*WELBY*MARCUS*W**JR*XX*1234567891~
                REF*G2*12345~
              NM1*82*1*DOE*JANE*C***XX*1234567804~
                PRV*PE*PXC*1223G0001X~
                REF*G2*12345~
              NM1*DQ*1*DOE*JOHN*B***XX*1234567891~
                REF*G2*12345~
              NM1*PW*2~
                N3*123 MAIN STREET~
                N4*KANSAS CITY*MO*64108~
              SBR*S*01*GR00786******13~
                CAS*OA*93*15.06~
                CAS*PR*1*7.93~
                AMT*D*100~
                OI***Y***Y~
                NM1*IL*1*DOE*DAVID****MI*123457~
                  N3*123 MAIN STREET~
                  N4*KANSAS CITY*MO*64108~
                NM1*PR*2*XYZ INSURANCE CO*****PI*11122444~
                  DTP*573*D8*20040203~
                  REF*G1*AB333-Y5~
                  REF*F8*R555589~
              LX*1~
                SV1*HC:99211:25*500*UN*1*11**1:2:3**Y~
                PWK*OZ*BM***AC*DMN0012~
                CR1*LB*140**A*DH*12****UNCONSCIOUS~
                CRC*07*Y*01~
                DTP*472*RD8*20050314-20050325~
              QTY*PT*2~
              REF*6R*54321~
              AMT*T*45~
              NTE*TPO*STATE REGULATION 123 WAS APPLIED DURING T~
              HCP*03*100.0000*10.0000*RPO12345~
              LIN**N4*01234567891~
              CTP****2*UN~
              REF*XZ*123456~
              NM1*82*1*DOE*JANE*C***XX*1234567804~
                REF*G2*12345~
              NM1*77*2*ABC CLINIC*****XX*1234567891~
                N3*123 MAIN STREET~
                N4*KANSAS CITY*MO*64108~
                REF*G2*12345~
              NM1*DQ*1*DOE*JOHN*B***XX*1234567891~
                REF*G2*12345~
            NM1*DK*1*RICHARDSON*TRENT****XX*1234567891~
              REF*G2*12345~
            NM1*DN*1*WELBY*MARCUS*W**JR*XX*1234567891~
              REF*G2*12345~
              SVD*43*0.55*HC:84550**3~
              CAS*OA*93*15.06~
              CAS*PR*1*7.93~
              DTP*573*D8*20040203~
    SE*114*000011~
  GE*1*211300001~
IEA*1*113182822~
Any ideas? Many thanks in advance for any assistance you can provide.
Jun 25, 2016 at 5:07 AM
I'm having trouble processing a whole range of 837 varieties:

837D_5010

Segment 'NM1772A-OK MOBILE CLINICXX1112233301' in segment position 52 within transaction '987654' cannot be identified within the supplied specification for transaction set 837 in any of the expected loops: . To change this to a warning, pass throwExceptionOnSyntaxErrors = false to the X12Parser constructor. Parameter name: 837

837DA_5010

Segment 'NM1
ZD
2
ABC INSURANCE CO' in segment position 20 within transaction '987654' cannot be identified within the supplied specification for transaction set 837 in any of the expected loops: 2000A[1],2000B[2],2010BA. To change this to a warning, pass throwExceptionOnSyntaxErrors = false to the X12Parser constructor. Parameter name: 837

837I_4010

Segment 'LX
1' in segment position 39 within transaction '54322' cannot be identified within the supplied specification for transaction set 837 in any of the expected loops: . To change this to a warning, pass throwExceptionOnSyntaxErrors = false to the X12Parser constructor. Parameter name: 837

837IA_5010

Segment 'NM1
ZD2Medicaid Agency' in segment position 19 within transaction '000000001' cannot be identified within the supplied specification for transaction set 837 in any of the expected loops: 2000A[1],2000B[2],2010BA. To change this to a warning, pass throwExceptionOnSyntaxErrors = false to the X12Parser constructor. Parameter name: 837

837P_5010

Segment 'LINN401234567891' in segment position 95 within transaction '000011' cannot be identified within the supplied specification for transaction set 837 in any of the expected loops: 2000A[1],2000B[2],2000C[3],2300. To change this to a warning, pass throwExceptionOnSyntaxErrors = false to the X12Parser constructor. Parameter name: 837

837PA_5010

Segment 'NM1
ZD2Medical Agency' in segment position 23 within transaction '000011' cannot be identified within the supplied specification for transaction set 837 in any of the expected loops: 2000A[1],2000B[2],2010BA. To change this to a warning, pass throwExceptionOnSyntaxErrors = false to the X12Parser constructor. Parameter name: 837

837R_5010

Segment 'NM1
SJ
2ABC HOSPITAL
*XX1234567890' in segment position 7 within transaction '987654' cannot be identified within the supplied specification for transaction set 837 in any of the expected loops: 2000A[1]. To change this to a warning, pass throwExceptionOnSyntaxErrors = false to the X12Parser constructor. Parameter name: 837

I've uploaded a zip file containing the raw 837 data here:

[https://equalityhealth.blob.core.windows.net/temp/Failed837.zip?sr=b&sv=2015-02-21&st=2016-06-25T04%3A06%3A39Z&se=2020-06-25T05%3A06%3A00Z&sp=rwd&sig=zrcTcHjZOPKgdgP7mI8tkSfbVfxGKZVp7kM6MB4Fz1s%3D]

I've read the article on how to add customized specfications, but still do not know where to start adjusting the XML to address these errors. If someone could show me the process to change one of them, I'd gladly do the rest and share.

Many thanks, Kurt
Coordinator
Jun 25, 2016 at 1:03 PM
I was not able to access your raw 837, but hopefully you have de-identified it.

Your NM1 segments aren't getting recognized because it is using a ZD entity code qualifier that is probably not in the specification.
You would need to add a section in the spec where you expect that loop to appear:
A sample is below. It would depend on where it is showing up in your X12, is it part of the claim or is it at a higher level than that?
      <Loop LoopId="2310ZD" Usage="Situational" LoopRepeat="2">
        <Name>REFERRING PROVIDER NAME</Name>
        <StartingSegment SegmentId="NM1" Usage="Situational" Repeat="1">
          <EntityIdentifier Code="ZD"/>
        </StartingSegment>
        <Segment SegmentId="REF" Usage="Situational" Repeat="3"/>
      </Loop>
It looks like you have EntityIds: ZD, SJ, 77 that are showing up where they aren't expected.

The LX1 should be recognized, but there is something preceeding it that is throwing it off so that it no longer thinks it's in the claim loop. If you could just show your sequence of segments Ids from the CLM to the LX1 I might be able to identify without the full raw data.

LIN should show up within a service line so it might be the same issue if you show your sequence from LX1 to the LIN that should be enough to troubleshoot the issue.