Network Gap Exceptions
How to Request a Network Gap Exception
A network gap generally means your plan does not have a reasonably available in-network provider for a specific specialty, subspecialty, or service. Some plans call this a gap exception, a network deficiency exception, or a single-case agreement; others have no formal term for it at all.
Important
A gap does not automatically create a right to out-of-network coverage
Not every plan or state uses the term "network gap exception," and the absence of a preferred provider does not automatically create a right to out-of-network care at in-network cost sharing. Whether a gap exception applies depends on your plan's own network-adequacy standard, and fully insured plans are subject to state network-adequacy rules that self-funded ERISA plans generally are not.
Is This a Directory Error or an Emergency?
This page covers a genuine access gap, not a directory error or emergency
If the plan's own directory incorrectly listed a provider as in-network, or this involves emergency care, see the separate out-of-network denial guide instead. A true network gap means no in-network option reasonably exists, not that the directory was wrong.
How to Approach a Network Gap
Pre-service request versus post-service appeal
-
Pre-service: request approval before you get care
If you have not yet received the service, the standard procedure is to ask your plan in advance to approve an out-of-network provider at in-network cost sharing, because no in-network option is reasonably available. This usually requires clinical justification from the ordering or treating provider and proof of the search for an in-network option.
-
Post-service: appeal a denial after the gap already caused a problem
If you already received out-of-network care because of a genuine gap and the claim was denied or paid at out-of-network rates, that becomes a member appeal addressing the plan's network-adequacy standard, not a pre-service request.
-
Identify the specific specialty or subspecialty need
General availability of "a" provider in a broad specialty does not resolve a gap involving a subspecialty, a specific procedure, or a provider with relevant experience the plan's network genuinely lacks. Be specific about what was actually needed and why a generalist or different subspecialist could not reasonably substitute.
-
Document the provider search
Keep a log of every in-network provider contacted, the date, whether they were accepting new patients, the specialty or subspecialty confirmed, and the outcome. A search of one provider is weaker evidence than a documented search of several.
-
Document appointment availability and travel distance
Record how far out the next available in-network appointment was, and the distance or travel time to the nearest in-network provider who could actually treat the condition. Many state network-adequacy standards use specific time-and-distance or appointment-wait benchmarks, though the exact standard varies by state and plan type.
-
Continuity of care is a related but separate concept
If you were already in an active course of treatment with a provider who left the network, some plans and states allow a transition period at in-network cost sharing. That is different from a one-time gap request and follows its own rules.
Build the File
Documents worth gathering
-
Denial notice and EOB, if a claim has already been denied
-
Insurance card
-
Plan document or Summary Plan Description network-adequacy language
-
A log of in-network providers contacted, with dates and outcomes
-
Appointment-availability records for in-network providers
-
Distance or travel-time documentation to the nearest in-network provider
-
A clinical letter explaining the specific specialty or subspecialty need
-
Any prior authorization request already submitted
Which Situation Applies
Have you already received the care?
Remedy Support's current service is limited to post-service network gap disputes. Pre-service requests follow a different process with your health plan directly.
Not yet — I need approval before an upcoming service
This is a pre-service request you make directly with your health plan, using your provider's clinical justification and your documented search for an in-network option. Remedy Support does not currently support pre-service network gap advocacy.
Yes — I already received care and the claim was denied or paid out of network
This is the fact pattern Remedy Support currently screens for a member appeal.
Check Whether Your Case Is EligibleCommon Questions
Frequently Asked Questions
Does every plan use the term "network gap exception"?
No. Plans and states use different terms, and some have no formal named process at all. The underlying question is always whether an in-network option was reasonably available.
Does a long wait for an in-network appointment guarantee a gap exception?
Not automatically. It is evidence that can support a gap request, but plans apply their own network-adequacy standards, and fully insured plans are subject to state standards that self-funded plans generally are not.
Can I ask for approval before I get the service?
Yes, and that is the standard procedure for a genuine gap. Remedy Support does not currently support pre-service gap advocacy; this page explains what to document either way.
Is a network gap the same as a directory error?
No. A directory error means the plan's own directory was wrong about a provider's network status. A network gap means no suitable in-network provider reasonably exists.