TL;DR: Cigna Healthcare modified its Network Adequacy Provision policy (UM-20) on November 7, 2025. When your patient can't access an in-network provider within reasonable distance or timeframe, this is the policy that governs whether Cigna approves an out-of-network authorization. Here's what changes for billing teams.
Cigna Healthcare updated the UM-20 network adequacy coverage policy, effective date November 7, 2025. This policy — formally known as the Network Adequacy Provision — establishes the process Cigna uses to evaluate and respond to authorization requests when no qualified in-network provider is available within a reasonable distance from the member's home or within acceptable appointment timeframes. The policy does not list specific CPT, HCPCS, or ICD-10 codes. It applies across specialties and service types whenever network gaps trigger an out-of-network access request.
Quick-Reference Table
| Field | Detail |
|---|---|
| Payer | Cigna Healthcare |
| Policy | Network Adequacy Provision (NAP) |
| Policy Code | UM-20 (um20-network-adequacy-provision) |
| Change Type | Modified |
| Effective Date | November 7, 2025 |
| Impact Level | High |
| Specialties Affected | All specialties — any provider billing out-of-network under a network adequacy authorization |
| Key Action | Audit your current out-of-network authorization workflow for Cigna members and confirm your documentation meets the updated proximity and availability criteria before submitting new NAP requests |
Cigna Network Adequacy Provision Coverage Criteria and Medical Necessity Requirements 2025
The UM-20 Cigna network adequacy coverage policy exists to answer one question: when a Cigna member genuinely cannot access a qualified in-network provider, what process does Cigna use to authorize out-of-network care at in-network benefit levels?
The answer is more structured than most billing teams realize. This is not a blanket out-of-network exception process. Cigna evaluates each request against specific criteria — reasonable distance from the member's home and reasonable appointment availability timeframes — both of which are defined in attachments to the policy itself. Those definitions matter. "Reasonable" is not a judgment call you get to make unilaterally.
Medical necessity is baked into this framework at two levels. First, the underlying service must be medically necessary — Cigna still requires that the care being requested meets its standard medical necessity criteria. Second, the network gap itself must be genuine. You can't use UM-20 as a workaround for a member who simply prefers an out-of-network provider. The policy requires that no qualified, participating provider is available within the defined distance or timeframe thresholds.
Prior authorization under UM-20 is the mechanism that unlocks out-of-network reimbursement at in-network rates. Without an approved prior authorization through this process, claims for out-of-network services will process at out-of-network benefit levels — or trigger a claim denial entirely if the plan doesn't cover out-of-network care. Your billing team should treat every NAP request as a formal prior auth submission, not an informal exception request.
The November 7, 2025, modification to this policy signals that Cigna tightened or clarified the evaluation process. The updated policy language reinforces a "consistent process" — Cigna's words. That phrase is doing real work here. It means Cigna is standardizing how these requests get evaluated across markets and plan types. What worked regionally before may not hold up under the updated framework.
Coverage Indications at a Glance
This policy does not list specific covered or non-covered diagnoses or procedures by code. Coverage applies to any medically necessary service where a network adequacy gap is documented. The table below reflects the indication-level logic the policy establishes.
| Indication | Status | Relevant Codes | Notes |
|---|---|---|---|
| Medically necessary service with no qualified in-network provider within defined distance threshold | Eligible for NAP authorization | No codes specified — applies across all procedure types | Distance criteria defined in policy attachments; must document proximity gap |
| Medically necessary service with no in-network provider available within reasonable appointment timeframe | Eligible for NAP authorization | No codes specified | Timely access criteria defined in policy attachments; must document scheduling gap |
| Service where in-network provider is available but member prefers out-of-network | Not eligible | N/A | Preference is not a network adequacy issue; standard out-of-network benefit applies |
| Service that does not meet Cigna's medical necessity criteria | Not eligible | N/A | NAP authorization does not override medical necessity requirements |
Cigna Network Adequacy Provision Billing Guidelines and Action Items 2025
This policy change has real operational teeth. If your practice or billing team handles out-of-network authorizations for Cigna members, you need to move before you submit your next NAP request under the updated framework.
| # | Action Item |
|---|---|
| 1 | Pull the updated UM-20 policy attachments from Cigna's provider portal. The distance thresholds and appointment availability timeframes live in the attachments, not in the main policy body. Those numbers define whether your authorization request is even eligible. Get them now — before November 7, 2025, if you haven't already reviewed the update. |
| 2 | Audit your current NAP authorization workflow against the updated criteria. Map each step in your current process to the updated requirements. If your team has been submitting requests based on informal distance assumptions, that approach won't survive the "consistent process" language Cigna added. Update your internal checklist to match the actual threshold language in the policy attachments. |
| 3 | Build a documentation template that captures network gap evidence. Every NAP request needs to show two things: the service is medically necessary, and no qualified in-network provider is available within the defined distance or timeframe. Generic statements won't hold up. Document specific provider searches, dates of searches, and why each in-network option was unavailable or inaccessible. |
| 4 | Train your authorization staff on the distinction between network gap and member preference. This is where denials happen. A member who lives 15 minutes from an in-network specialist but wants to see someone out-of-network does not qualify for a network adequacy authorization. Your team needs to screen requests at intake and not submit NAP requests that don't meet the threshold criteria — those will generate claim denial exposure and delay care. |
| 5 | Confirm how the updated policy applies across your Cigna plan mix. UM-20 applies across plan types, but Cigna's attachments may define thresholds differently by market or plan type. If you bill across multiple Cigna products — commercial, Cigna-HealthSpring, or employer-sponsored plans — verify which attachment governs each. Your Cigna provider relations contact or your billing consultant can help you map this. If the plan mix is complex, loop in your compliance officer before the effective date to make sure your workflow covers all scenarios. |
| 6 | Check your billing guidelines for how to submit claims after a NAP authorization is approved. Out-of-network claims processed under a network adequacy authorization need the authorization number on the claim. Confirm your billing team knows where to place it and which modifier or billing guidelines apply to your specific plan contracts. A missing authorization number on an otherwise-approved claim will still generate a claim denial. |
| Previous Version | Current Version |
|---|---|
| Coverage is considered experimental and investigational for all indications | Coverage is considered medically necessary when specific criteria are met |
| Prior authorization is not required | Prior authorization is required for initial treatment |
| Documentation must include clinical history | Documentation must include clinical history |
| Re-review every 24 months | Re-review every 12 months with updated clinical documentation |
CPT, HCPCS, and ICD-10 Codes for Network Adequacy Provision Under UM-20
The UM-20 network adequacy coverage policy does not list specific CPT, HCPCS, or ICD-10 codes. This is intentional — the policy applies to any medically necessary service across all specialties and procedure types where a network gap exists.
There are no code-specific coverage restrictions within UM-20 itself. The codes that apply to any given authorization request are determined by the underlying service being requested, not by this policy. UM-20 is the authorization framework, not the coverage determination.
What this means for network adequacy billing: the relevant codes for your claim are the same codes you would use for that service under any other authorization. The NAP authorization number is what ties the out-of-network claim back to the approved exception. Make sure your billing team applies the authorization number correctly on every claim that flows through this process. A claim submitted without that reference number will not process at in-network benefit levels, regardless of whether the authorization was legitimately approved.
If your practice bills a high volume of services that frequently trigger NAP requests — think rare specialties, behavioral health, certain surgical subspecialties, or rural service areas — document your most common procedure codes internally and build them into your NAP request templates. Even though UM-20 doesn't list codes, your internal tracking should.
The Real Issue With This Policy Change
Here's the honest take: modifying a network adequacy policy to emphasize a "consistent process" is Cigna signaling that prior submissions were inconsistent — meaning some markets or staff were approving requests that didn't fully meet the criteria, and others were denying requests that should have been approved.
The update is a double-edged change. On one hand, it creates a more predictable framework — if you document the network gap correctly, you have a clearer path to approval. On the other hand, Cigna is tightening scrutiny. Requests that previously sailed through on informal documentation are more likely to face additional review.
The practices most at risk are those in mid-sized markets where in-network coverage is uneven. You might have one in-network provider listed in Cigna's directory who is technically accepting patients but has a six-month wait. Whether that qualifies as a "reasonable appointment availability timeframe" under the updated policy depends entirely on what the attachments say. Pull those numbers now.
Get the Full Picture
Track this policy across versions, search 1,500+ policies by CPT code, and get real-time alerts when any payer changes coverage.