The Complete Guide to Medicare Advantage Network Adequacy
Written for health plan network development teams, compliance officers, and executives managing CMS adequacy requirements. Covers standards, strategy, submission, and what happens when things go wrong.
In This Guide
Network adequacy is the foundation of Medicare Advantage coverage.
CMS requires Medicare Advantage plans to maintain a sufficient number of contracted providers within specified time and distance thresholds so that members can access covered services without unreasonable travel. This requirement applies across dozens of provider specialties and must be met in every county in the plan's service area.
The legal basis for network adequacy requirements is 42 CFR Part 422.116, which directs CMS to establish time and distance standards for MA organizations. CMS updates these standards annually through the Call Letter process. Plans are evaluated against the standards in effect at the time of submission.
Network Adequacy
Provider availability. Are there enough contracted providers of each required specialty within the required time and distance for members to reach them? This is what CMS measures at submission time through HPMS.
Network Access
Member experience. Can members actually get appointments with those providers in a timely way? Access is measured through CAHPS surveys and member complaints — and directly affects Star Ratings even when adequacy is met on paper.
Medicaid and Exchange (ACA marketplace) plans are also subject to network adequacy requirements, but under parallel — and distinct — regulatory frameworks. Medicaid adequacy is regulated at the state level. Exchange adequacy is governed by 45 CFR 156.230. This guide focuses on Medicare Advantage under 42 CFR Part 422.116.
Key Takeaway
Network adequacy is a regulatory requirement — but it is also an operational discipline. Plans that treat adequacy as an annual filing exercise consistently under-perform plans that manage it as a continuous monitoring function. The difference shows up in deficiency rates, enrollment freezes, and Star Ratings.
Standards vary by county classification and specialty — and both thresholds must be met.
CMS classifies every county in the United States into one of four categories — urban, suburban, rural, and frontier — and sets different time and distance thresholds for each classification. The thresholds reflect the practical realities of provider supply and member geography: an urban member can reasonably be expected to access a specialist within 10 miles, while a frontier member may travel 50 miles or more.
Both the time threshold and the distance threshold must be met simultaneously. A provider that is 4 miles away but takes 20 minutes to reach (due to road network conditions) fails the urban PCP time standard even though it meets the distance standard. CMS uses a drive-time model — not straight-line distance — in its final adequacy calculations.
| County Type | Primary Care | Specialist | Hospital |
|---|---|---|---|
| Urban | 10 min / 5 mi | 15 min / 10 mi | 15 min / 10 mi |
| Suburban | 20 min / 10 mi | 25 min / 15 mi | 20 min / 10 mi |
| Rural | 30 min / 20 mi | 40 min / 25 mi | 30 min / 20 mi |
| Frontier | 60 min / 40 mi | 75 min / 50 mi | 60 min / 40 mi |
Plans often build their provider networks assuming straight-line distance compliance and discover drive-time failures only after CMS runs its model. The safest approach is to apply drive-time modeling during network development — not just at submission time — so gaps are identified and remediated before the filing window opens.
Key Takeaway
Your network analysis is only as accurate as your distance model. If you're calculating straight-line distance from provider coordinates to county centroids, you are probably over-estimating adequacy in rural and frontier counties. CMS uses drive-time — your internal compliance modeling should too.
CMS evaluates adequacy across 22 Health Service Delivery categories — in every county.
CMS organizes provider types into Health Service Delivery (HSD) categories. A plan must meet the time-distance standard for each applicable HSD category in every county within its service area. A gap in any single category in any single county is a deficiency — even if every other category in that county is fully covered.
This means a plan with a 200-county service area is managing adequacy across potentially thousands of county-by-specialty combinations. Manual tracking at this scale is where errors accumulate.
The 22 categories listed above cover the core HSD framework. CMS may add, split, or reclassify categories in a given benefit year. Plans should review the HSD table published with each year's Call Letter to confirm no category changes affect their submission. See full HSD reference with specialty codes →
Key Takeaway
Every HSD category is a separate compliance obligation. A plan that achieves adequate PCP coverage across its entire service area but has a single behavioral health gap in one rural county has a deficiency. CMS does not aggregate across categories — each is evaluated independently.
Eight phases, one shot per year — the HPMS submission cycle.
The annual HPMS network adequacy submission is not an event — it is a cycle that begins months before the submission window opens and continues through final determination. Plans that treat it as a last-minute data export consistently produce lower-quality submissions than plans that run it as a managed process.
Audit provider contracts for active participation, validate NPIs against NPPES, confirm specialty coding matches CMS HSD categories, and reconcile your provider roster against the counties in your service area.
Map your provider data to the HPMS file format. Common errors at this stage include incorrect specialty codes, missing geographic coordinates, and duplicate NPI entries. CMS automated validation will flag these and require correction.
Plans submit provider data through HPMS during the annual submission window. CMS publishes the exact window in the annual Call Letter. Late submission is treated as non-submission — build buffer time.
CMS runs automated checks: NPPES cross-reference to confirm provider participation, specialty code validation, and preliminary time-distance modeling against the county-by-county standard.
CMS analysts manually review flagged records, assess exception requests, and apply the full drive-time model (not straight-line) to final adequacy determinations.
CMS issues preliminary findings identifying counties and specialties where the plan has failed to meet standards. This is not a final determination — plans have a response window.
Plans respond to preliminary findings by correcting data errors, filing exception requests, or submitting good faith effort documentation. This window is the most time-sensitive phase of the entire cycle.
CMS issues the final adequacy determination. Persistent deficiencies may result in a compliance action plan, enrollment freeze, or other regulatory consequence.
For a step-by-step HPMS file preparation walkthrough, see the HPMS Submission Guide.
Key Takeaway
The submission window is the deadline for data — not the deadline for preparation. Plans that begin their adequacy review 16 weeks before the submission window have time to identify gaps, recruit providers, and build good faith effort documentation before they need it. Plans that begin 4 weeks before do not.
A deficiency notice is the beginning of remediation — not the end of the road.
CMS issues a deficiency notice when its review of a plan's HPMS submission reveals that one or more county-specialty combinations fail to meet the applicable time-distance standard. The specific triggers below explain how most deficiency notices originate — and which ones are preventable through better data hygiene.
Fails time-distance standard
A county/specialty combination does not have the required number of providers within the applicable time and distance thresholds.
Non-participating provider counted
A provider in your submission is found through NPPES cross-referencing to be non-participating in your plan, retired, or deceased.
Telehealth credentialing defect
A telehealth provider was counted to fill a gap but does not meet CMS telehealth credentialing requirements for the applicable specialty.
Drive-time gap revealed by CMS model
CMS uses a drive-time model — not straight-line distance. Providers that appear adequate in straight-line analysis may fail the CMS drive-time calculation due to road network gaps.
Specialty coding error
A provider was submitted under an incorrect specialty code, causing them to be misassigned to an HSD category they do not fill.
Receiving a deficiency notice does not automatically result in a compliance action. Plans that respond promptly and with well-documented exception filings or provider additions frequently resolve deficiencies before final determination. The response process is discussed in Section 8. For the full response playbook, see CMS Deficiency Response.
Key Takeaway
Two of the five deficiency triggers above — non-participating providers and specialty coding errors — are data quality problems, not network problems. Plans that validate their provider roster before submission eliminate a significant share of their deficiency risk without adding a single provider to their network.
When you can't fill a gap, good faith effort documentation is your protection.
When a plan cannot contract a sufficient number of providers to meet the time-distance standard in a county-specialty combination, it must demonstrate that it made genuine, documented efforts to do so. CMS uses good faith effort documentation to distinguish between plans that are genuinely operating in markets with limited provider supply and plans that simply failed to recruit.
What CMS expects
- Multiple outreach attempts (min. 4)
- Multi-channel: written + phone
- Documented dates and contacts
- Specific declination reasons
- Alternative access plan
- Plan officer attestation
Common documentation failures
- Single-attempt outreach
- Undated or reconstructed logs
- Missing declination reasons
- No alternative access plan
- Outreach clustered in final 2 weeks
- Templated-looking declination entries
What draws CMS scrutiny
- Same county + specialty gapped 2+ years
- High exception rate vs. service area
- Filings without clear audit trails
- Outreach volume inconsistent with lead time
- Declination reasons that look cut-and-paste
Good faith effort documentation must be built contemporaneously — as outreach occurs — not reconstructed at the time of filing. CMS evaluators can identify reconstructed logs by date clustering and contact inconsistencies. See the full good faith effort guide →
Key Takeaway
Good faith effort is not a checklist — it is a documented story. CMS reviewers are evaluating whether your documentation tells a credible, complete account of genuine attempts to recruit providers. Thin, formulaic documentation is challenged routinely. Start outreach 12 weeks before your submission deadline and log every contact in real time.
Four exception pathways — each with different documentation requirements.
When a plan cannot meet a time-distance standard, CMS allows exception requests as an alternative to a compliance finding — provided the plan demonstrates that the exception is warranted and that members retain meaningful access to covered services. Choosing the wrong exception type or filing with insufficient documentation typically results in denial.
Access Exception
When used: Provider supply exists in the area but contracting efforts failed
Documentation requirements:
- Minimum 4 documented outreach attempts
- Specific declination reasons for each provider
- Multi-channel outreach (written + phone)
- Alternative access plan for members
- Plan officer attestation
Good Faith Effort Exception
When used: Genuine recruitment attempts exhausted with no willing providers
Documentation requirements:
- Full outreach log with dates, contacts, outcomes
- Written declinations where obtainable
- Evidence of alternative arrangements explored
- Member impact assessment
Single Provider Market
When used: No providers of the required specialty exist in the county
Documentation requirements:
- HRSA HPSA or MUA designation documentation
- Evidence of provider search exhaustion
- Alternative access arrangement
State-Approved Alternative
When used: State has approved an alternative delivery arrangement that meets member access needs
Documentation requirements:
- State approval documentation
- Description of the alternative arrangement
- Member notification plan
For detailed documentation requirements and filing instructions for each exception type, see the Exception Filing Guide.
Key Takeaway
Exception filing is not a fallback position — it is a planned component of a mature adequacy strategy. Plans operating in rural or frontier markets should identify counties likely to require exception filings at the start of the submission cycle, not after deficiency notices arrive.
The 30-day response window is the most time-sensitive phase in the entire cycle.
When CMS issues preliminary findings, plans typically have 30 days to respond. In that window, the plan must take one or more of the following actions for each deficient county-specialty combination: add a provider, file an exception, or correct the data error that caused the deficiency. Missing the window — or responding with thin documentation — converts a preliminary finding into a final deficiency.
Emergency provider contracting
Identify and contract providers on an expedited basis. Credentialing timelines may need to be compressed. Confirm with CMS whether a signed contract (rather than credentialing completion) satisfies the adequacy standard for the response window.
Exception filing for genuine gaps
For counties where providers genuinely do not exist or will not contract, file the appropriate exception type with complete documentation. Match the exception type to the facts — a Good Faith Effort exception requires different documentation than a Single Provider Market exception.
Supplemental outreach documentation
If your Good Faith Effort documentation was thin at submission time, use the response window to supplement it — additional outreach attempts made since submission, written declinations obtained, or alternative access arrangements documented.
Telehealth provider addition
For eligible specialties (behavioral health, certain primary care categories), adding a qualified telehealth provider may resolve a time-distance deficiency. Confirm the provider meets CMS telehealth credentialing requirements before counting them.
Common mistake: Not responding within the window
The single most common — and most avoidable — deficiency response failure. A non-response is treated as acceptance of the preliminary finding.
Common mistake: Misidentifying the affected counties
Plans sometimes respond to the wrong county or specialty combination, or miss affected counties entirely because the deficiency notice was not reviewed carefully. Map every deficiency before building your response.
For the complete deficiency response playbook including response letter templates, county-by-county triage framework, and CMS communication protocols, see CMS Deficiency Response.
Key Takeaway
A 30-day window sounds like plenty of time. It is not. Emergency provider contracting, exception package assembly, and data correction all require coordination across legal, credentialing, and network teams. Plans that pre-build response protocols — before deficiency notices arrive — move faster when the window opens.
An enrollment freeze is the most disruptive regulatory consequence of persistent adequacy failures.
CMS has authority to impose an enrollment freeze on Medicare Advantage plans with unresolved adequacy deficiencies. An enrollment freeze blocks the plan from enrolling new members until CMS determines that the deficiencies have been remediated. Existing members are not disenrolled, but the plan's growth stops entirely during the freeze period.
12 months of lost growth
A freeze imposed at the start of the annual enrollment period can block new member acquisition for an entire benefit year, including AEP and OEP enrollments.
Broker relationship damage
Brokers who can't enroll clients in your plan shift volume to competitors during the freeze. Rebuilding those relationships after the freeze lifts takes time and cost.
Reputational and competitive harm
CMS enrollment freezes are documented in public regulatory databases. Employer and government clients monitor CMS compliance status — a freeze affects RFP eligibility.
How to avoid an enrollment freeze
Run continuous adequacy monitoring — not just at submission time. Providers terminate, retire, and close panels throughout the year.
Identify gap counties early — ideally 16–20 weeks before your submission window — so you have time to recruit, contract, and credential providers.
Build good faith effort documentation as outreach occurs. Don't wait for a deficiency notice to start logging your recruitment activity.
Pre-file exception documentation for counties where you know provider supply is insufficient. Getting ahead of the deficiency notice is always better than responding to it.
For a detailed analysis of CMS enrollment freeze triggers, timelines, and the remediation process, see Enrollment Freeze Risk.
Key Takeaway
Enrollment freezes are preventable. They result from persistent, unresolved deficiencies — not from a single submission gap. Plans that monitor adequacy continuously, respond promptly to deficiency notices, and maintain documented good faith efforts for hard-to-fill counties virtually eliminate their enrollment freeze risk.
Adequacy gaps become Star Rating losses — with a two-year lag.
The link between network adequacy and Star Ratings is indirect but powerful. Adequacy gaps do not appear on the CMS Star Ratings scorecard as a labeled measure. Instead, they show up through member experience: members who cannot access a provider in their network report worse access scores on the CAHPS survey, which directly drives multiple Star Rating measures.
The Adequacy-to-Stars Causation Chain
Adequacy gap
Provider unreachable
Access failure
Member can't get appointment
CAHPS survey
Lower access scores reported
Star Rating drop
Access/timeliness measures fall
QBP loss
$400–700 per member/year
The QBP stakes
CMS Quality Bonus Payment (QBP) bonuses are available to plans rated 4 stars or higher. The bonus is worth approximately $400 to $700 per member per year, depending on the contract and benchmark. For a plan with 50,000 members, the difference between a 3.5-star and a 4-star rating can represent $20–35M in annual revenue.
The two-year lag problem
An adequacy gap in 2024 leads to member access failures in 2024–2025, which appear in the 2025 CAHPS survey results, which are reflected in the 2026–2027 Star Ratings. By the time the Star Rating impact is visible, the root cause is two years in the past. This lag makes proactive adequacy management a forward-looking revenue protection strategy.
For a detailed analysis of how adequacy gaps flow through to Star Rating measures, see Network Adequacy and Star Ratings.
Key Takeaway
Network adequacy is a Star Rating issue — it just doesn't look like one in the CMS scorecard. Plans that manage adequacy proactively protect their CAHPS access scores, which protect their Star Rating, which protects their Quality Bonus Payment eligibility. Framing adequacy as a revenue protection strategy — not just a compliance obligation — is how high-performing plans secure executive investment in network development.
Purpose-built for health plan network adequacy teams.
Blueprint gives network teams a single platform for adequacy monitoring, provider pipeline management, exception documentation, and CMS submission preparation — replacing the spreadsheets and manual processes that create compliance risk.
Real-time adequacy scoring
Live adequacy scores per county and specialty — updated as providers are added, terminated, or credentialed.
Provider pipeline tracking
Track every provider through contracting stages: outreach, negotiation, credentialing, active, and terminated.
Good faith effort workflow
Structured outreach logging, declination capture, and one-click exception package generation.
HPMS-ready reporting
Export provider data pre-formatted to HPMS file specifications, reducing manual data prep time.
Deficiency response templates
Pre-built response templates for common deficiency scenarios, customized to your filing.
Exception filing support
Guided exception filing workflows for all four exception types, with documentation checklists.
Related Tools and Guides
Stop managing CMS adequacy in spreadsheets.
Blueprint gives your team real-time adequacy scores, provider pipeline tracking, and submission-ready reporting — so you spend less time on manual data work and more time closing network gaps before they become compliance findings.