Summary: Cigna Healthcare modified its Network Adequacy Provision policy (UM-20), effective April 7, 2026. Here's what billing teams and network participation managers need to know before that date.
Cigna Healthcare updated UM-20, its internal policy governing network adequacy determinations. This coverage policy doesn't list specific CPT, HCPCS, or ICD-10 codes — it operates at the network and utilization management level, not the procedure level. That scope makes it easy to overlook and dangerous to ignore. Network adequacy provisions directly affect whether claims route as in-network or out-of-network, which means your reimbursement rates and patient cost-sharing calculations are both on the line.
Quick-Reference Table
| Field | Detail |
|---|---|
| Payer | Cigna Healthcare |
| Policy | Network Adequacy Provision (NAP) — UM-20 |
| Policy Code | UM-20 |
| Change Type | Modified |
| Effective Date | April 7, 2026 |
| Impact Level | High |
| Specialties Affected | All specialties billing Cigna — particularly high-risk for primary care, mental/behavioral health, and specialist groups in rural or underserved markets |
| Key Action | Confirm your participating provider agreements and network status with Cigna before April 7, 2026 |
Cigna Network Adequacy Coverage Policy and Medical Necessity Requirements 2026
Network adequacy is the framework Cigna uses to determine whether its plan networks meet state and federal access standards. When a network falls short — too few providers, too long a wait time, too little geographic coverage — UM-20 is the policy that governs what happens next.
The modification to UM-20 on April 7, 2026 signals that Cigna updated the criteria or procedures it uses to assess and respond to adequacy gaps. Without the full policy text, the specific criteria changes aren't public, but the structure of UM-20 policies generally covers these areas: provider-to-member ratios, travel time and distance standards, appointment availability benchmarks, and the process for granting out-of-network exceptions when in-network access isn't available.
That last piece — the out-of-network exception process — is where this coverage policy has the most direct effect on billing teams. When Cigna determines a network is inadequate for a specific service or geography, it's required to allow members access to out-of-network providers at in-network cost-sharing. Your billing team needs to understand whether and how this policy change affects those exception workflows.
Prior authorization requirements can also shift under a network adequacy modification. If Cigna tightens the standard for what qualifies as an adequacy gap, prior auth exceptions that previously cleared automatically may now require additional documentation. If it loosens standards, the opposite is true — but you need to know which direction this change moves before April 7, 2026.
Cigna Network Adequacy Exclusions and Non-Covered Indications
The policy data provided does not list specific exclusions or non-covered indications. UM-20 is a utilization management and network governance policy, not a procedure-level coverage policy.
That said, the practical exclusion risk is real. If a provider or facility isn't recognized as qualifying for an adequacy exception under the updated UM-20 criteria, claims that previously processed at in-network rates may now face out-of-network adjudication. That's not a clinical exclusion — it's a network status determination — but the financial outcome for your practice is the same: lower reimbursement and higher claim denial exposure.
Coverage Indications at a Glance
Because UM-20 is a network governance policy and not a procedure-specific coverage policy, the standard indication-by-indication table doesn't apply here. Instead, here are the network status scenarios this policy governs:
| Scenario | Coverage Status | Notes |
|---|---|---|
| Provider is in-network, network meets adequacy standards | In-network benefits apply | Standard adjudication; no exception needed |
| Provider is out-of-network, network gap demonstrated | Out-of-network provider treated at in-network cost-sharing | Exception must be documented and approved under UM-20 criteria |
| Provider is out-of-network, no adequacy gap demonstrated | Out-of-network benefits apply (or denial if plan has no OON benefit) | Prior auth for OON services required where applicable |
| Adequacy gap claimed but not substantiated | Claim adjudicated at OON rate or denied | Appeals process applies; document access barriers thoroughly |
| Plan operates in state with independent adequacy oversight | State standards may supersede Cigna's UM-20 criteria | Check your state's insurance department standards |
Cigna Network Adequacy Billing Guidelines and Action Items 2026
These are the concrete steps your billing team should take before April 7, 2026.
| # | Action Item |
|---|---|
| 1 | Verify your current network participation status with Cigna. Pull your provider agreement and confirm your in-network status is active and accurately reflected in Cigna's directory. Discrepancies between your agreement status and the directory are a common source of claim denial under network adequacy disputes. Do this now — directory corrections can take 30–60 days. |
| 2 | Identify any services where you've relied on network gap exceptions. If your practice has been billing out-of-network Cigna claims at in-network rates based on prior adequacy exceptions, review those approvals. Confirm whether they carry over under the modified UM-20 criteria or require reauthorization after April 7, 2026. |
| 3 | Update your prior authorization workflows for out-of-network referrals. If the UM-20 modification changes the documentation threshold for adequacy exceptions, your front-end authorization team needs to know. Build the updated criteria into your PA checklist before the effective date. If you're not sure what changed, contact your Cigna provider relations rep directly and request the updated UM-20 criteria in writing. |
| 4 | Review your denial patterns for network-related claim denials. Pull the last 90 days of Cigna denials flagged with network or out-of-network remark codes. If you're seeing a pattern, that's a signal that network adequacy disputes are already affecting your revenue cycle — and the April 7 change may sharpen that exposure. |
| 5 | Check state-specific adequacy rules. Network adequacy standards aren't just Cigna's to set. Most states have independent requirements, and several states — including California, New York, and Texas — have specific adequacy standards for mental/behavioral health under parity laws. If your state's standard is stricter than UM-20, the state standard controls. Talk to your compliance officer if your patient population includes a high proportion of Cigna members seeking specialty or behavioral health services. |
| 6 | Flag this policy for your credentialing team. Network adequacy policy changes can affect new provider onboarding timelines, especially in markets where Cigna has closed or restricted panel participation. If you're onboarding providers who plan to bill Cigna, confirm whether the updated UM-20 criteria affect credentialing timelines or panel access in your market. |
The real issue here is that UM-20 changes are invisible at the claim level until a denial hits. By then, you've already done the work and the patient has already been seen. Getting ahead of this before April 7, 2026 is the only way to avoid absorbing avoidable write-offs.
| 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 policy does not list specific CPT, HCPCS, or ICD-10 codes. This is expected for a network governance policy — it applies across all procedure codes rather than to a defined list.
This is worth flagging to your billing team explicitly: UM-20 affects network adequacy billing across your entire charge master, not a subset of codes. Any Cigna claim can be subject to network adequacy adjudication depending on the provider's participation status and the plan's network configuration for the service area.
If you're trying to identify which claims carry the highest financial exposure, focus on:
- High-dollar specialty services billed by providers who operate in markets with thin Cigna networks
- Mental and behavioral health claims, where parity requirements create specific adequacy obligations
- Out-of-network claims in any specialty where you've historically relied on gap exception approvals
- Any service line where you've added providers in the past 12 months and haven't confirmed Cigna directory accuracy
These aren't code-level exposures — they're portfolio-level exposures. Your revenue cycle director and compliance officer both need visibility into this policy change, not just your billing staff.
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.