We are sending 298 files out through a send port using XML receive on the receive port, and EDISend on the send port.

The error we are getting doesn't quite make sense - its complaining about a referring provider loop, which isn't there

If we delete the rendering provider loop, the transaction processes.

BizTalk is acting like if you have a 2310B loop, you need a 2310A loop.

But that's not called out in the implementation guide for a 298

Has anyone else seen anything like this?

The schema was purchased from wpc

Here's the segment in the source XML(Altered to remove some PHI)

<ns0:Loop_2310B>
          <ns0:NM1_RenderingProviderName_2310B>
            <ns0:NM101__EntityIdentifierCode>82</ns0:NM101__EntityIdentifierCode>
            <ns0:NM102__EntityTypeQualifier>2</ns0:NM102__EntityTypeQualifier>
            <ns0:NM103__RenderingProviderLastOrOrganizationName>FAKE COMPANY NAME</ns0:NM103__RenderingProviderLastOrOrganizationName>
            <ns0:NM108__IdentificationCodeQualifier>XX</ns0:NM108__IdentificationCodeQualifier>
            <ns0:NM109__RenderingProviderIdentifier>9999999999</ns0:NM109__RenderingProviderIdentifier>
          </ns0:NM1_RenderingProviderName_2310B>
        </ns0:Loop_2310B>

it gets this set of errors out of biztalk

We are sending 298 files out through a send port using XML receive on the receive port, and EDISend on the send port.

Can u please elaborate  the above statement.

298? I've not encountered this one.  You mean 278 or 837?

No its a 298

Its the All Payers version of the 837 family, so they are related, but they are not the same

Its post adjudication