Your provider says the portal blocked them, or says they can't help with your claim
When a provider tries to submit through Availity and the portal rejects them — or when a provider says they can't participate because the system won't accept them — the problem is not the provider. The insurer's portal blocks the very actor whose action is required. Asking the provider to try again will produce the same result.
The portal requires provider submission. The portal blocks provider submission.
Availity is the insurer's electronic portal for prior authorizations, referrals, and claims. For out-of-network providers, the portal often rejects submissions outright — because the provider is not contracted with the network.
This creates a contradiction. The insurer says: the provider must submit. The insurer's system says: this provider cannot submit. Both cannot be true in practice. The submission pathway is closed.
When the provider says "I can't help" or "the portal won't accept me," they are usually describing this technical reality — not refusing to cooperate.
Asking the provider to try the portal again, calling the insurer for verbal guidance, or filing a generic appeal that does not address the submission pathway failure. These repeat the blocked step or accept the insurer's frame without forcing them to provide a working alternative.
A portal blockage is a system-level defect, not a provider problem
The insurer created a submission requirement. The insurer built a system that prevents fulfilling that requirement for certain providers. The member and provider are caught in a constraint that the insurer controls.
The resolution is not to keep pushing through the blocked route. The resolution is a written demand designed to force a response in which the insurer acknowledges the blocked route and provides an alternative pathway — one that does not depend on the provider successfully navigating a portal that rejects them.
"I am writing to confirm that [provider name]'s attempt to submit [claim/prior authorization] through your portal was rejected because the provider is out of network. Please confirm in writing whether you will accept this submission directly from me as the member, and if not, please identify an alternative submission pathway that does not require the provider to use a portal that your system will not accept them through."
Send via certified mail or through the insurer's secure member portal. Keep the transmission record. If they do not respond or deny an alternative pathway exists, that documented refusal becomes the basis for a regulator complaint.
Distinguish between "won't" and "can't"
Some providers genuinely cannot submit through an insurer's system — the portal blocks them, they lack a contract, or the electronic submission channel requires in-network credentials they don't have. This is a system problem.
Other providers won't participate in the appeal or authorization process for administrative reasons — office policy, staffing, or reluctance to document a clinical position. That is a different issue requiring a different response.
Claim Lane helps identify which situation you're in, because the right next move is different for each.
Member-side fallback routes exist
When the provider-side route is blocked, member-initiated routes become available. These include:
- Written request to the insurer to accept direct member submission
- Formal complaint to the state insurance department citing the blocked submission pathway
- Request for a specific alternative submission channel (mail or email) rather than Availity
- Documentation of the portal failure as part of an internal appeal supporting the claim that in-network access was not actually available
None of these require the provider to go back through the portal. Each is a written demand designed to force a response in which the insurer solves the problem they created.
Free denial pattern classification identifies a likely pattern, the missing fact to check, and the next question to ask. No account required.
Free denial classification — 30 secondsFrequently asked questions
Availity is primarily an electronic data interchange network for contracted providers. Out-of-network providers typically lack the credentials or contracts to submit through the portal — the system is not designed to accept them. This is a design choice, not a bug, but it creates a submission barrier for members who need out-of-network care.
In some cases, yes. Members can request prior authorizations and submit supporting documentation directly to the insurer through written channels. Whether this is accepted depends on the insurer and the type of authorization. The written demand described above forces the insurer to clarify whether member-initiated submission is available.
Yes. Documentation that the standard submission pathway was unavailable due to the insurer's own system is relevant to appeals and regulator complaints. It establishes that any delay or failure to authorize was not due to the member or provider failing to take required steps — the pathway was closed.
Ask the insurer to provide that alternative portal in writing, with instructions. Then ask your provider to attempt that channel. Document all attempts. If the alternative also fails, that documentation strengthens your written record for escalation.
Three pillars · classification, coordination, record-building · how coordination works → · administrative record-building, not legal action.