avacollins
New
Please is anyone else experiencing this issue???
As of last week none of our claims have been able to go through to this payer ID for Independence Blue Cross. IBX is in the process of transitioning to a new platform, Smart Data Solutions, and has specifically advised providers NOT to change the "headers" in the EDI files when submitting claims. We have not changed anything in our submission process which is done via a billing vendor who uses the Availity clearinghouse. Somewhere in this process the claims are not being routed to the correct payer ID, 54704, and are instead going out with a header of ISA08. So every single claim is being rejected as being sent to the wrong payer. IBX has no answers to this problem, Smart Data Solutions has no answers, our billing vendor has no answers, and Availity is nearly impossible to deal with. There are no updates on any sites acknowledging this issue, although I was informed by our billing vendor that there are several other providers experiencing the same problem with this specific payer ID.
If you have any answers to what is going on here please let me know!
As of last week none of our claims have been able to go through to this payer ID for Independence Blue Cross. IBX is in the process of transitioning to a new platform, Smart Data Solutions, and has specifically advised providers NOT to change the "headers" in the EDI files when submitting claims. We have not changed anything in our submission process which is done via a billing vendor who uses the Availity clearinghouse. Somewhere in this process the claims are not being routed to the correct payer ID, 54704, and are instead going out with a header of ISA08. So every single claim is being rejected as being sent to the wrong payer. IBX has no answers to this problem, Smart Data Solutions has no answers, our billing vendor has no answers, and Availity is nearly impossible to deal with. There are no updates on any sites acknowledging this issue, although I was informed by our billing vendor that there are several other providers experiencing the same problem with this specific payer ID.
If you have any answers to what is going on here please let me know!