Free Network Build Assessment
Score your buildCMS changes Medicare Advantage network adequacy requirements through rulemaking and the annual HSD Reference File, not through bulletins or Call Letters. Here's a plain-language guide to where the rules live, what is settled, and what network teams should verify before relying on any summary.
Medicare Advantage network adequacy requirements live in regulation at 42 CFR 422.116. CMS changes that regulation through its annual MA and Part D rulemaking: a proposed rule, a comment period, and a final rule published in the Federal Register. The county-level numbers that put the regulation into practice, each county's designation, its time and distance maximums, and its minimum provider counts, are published in CMS's HSD Reference File for each contract year.
That structure matters for network teams. A summary of "what changed this year" is only as good as its source. Before acting on any claimed change to adequacy standards, including summaries on this site, confirm it against the regulation text and the current HSD Reference File.
The practical consequence is that network ops teams should not wait for a final rule to begin network build and contracting. Proposed rules signal where CMS is heading months in advance, and the current HSD Reference File gives the numbers to build against today.
Under 42 CFR 422.116, CMS assigns every county one of five designations, Large Metro, Metro, Micro, Rural, or CEAC (counties with extreme access considerations), based on population and density. It sets maximum time and distance standards for 29 provider types and 14 facility types, and requires that a set share of beneficiaries live within both the time and the distance limit: 90% in Large Metro and Metro counties and 85% in Micro, Rural, and CEAC counties. Those last three were held to 90% until the CY2021 final rule lowered them to 85%.
The base standards are published in the regulation and repeated in the HSD Reference File. For 2026, Primary Care runs from 10 minutes and 5 miles in Large Metro counties to 70 minutes and 60 miles in CEAC counties; Cardiology runs from 20 minutes and 10 miles to 95 minutes and 85 miles. CMS customizes standards for some counties, and a customized standard can only be higher than the base. Minimum provider counts are set county by county from the number of beneficiaries.
Geographic access is not the only access requirement. CMS's MA rules also set appointment wait-time standards, so that members can obtain appointments within set windows even when a provider is geographically close. Check the current regulation text for the exact windows that apply to each type of care.
The operational challenge is significant. Wait-time standards require plans to actively monitor appointment availability across their contracted network, not just verify that providers are contracted and geographically located within threshold. Plans that rely on static directory attestations from providers should consider actual appointment availability testing.
Plans operating in markets with high provider demand and thin panel capacity, particularly in behavioral health and primary care, face the most difficult compliance path on wait-time standards. A provider who is geographically adequate but routinely unavailable for new patient appointments is a compliance liability that geographic adequacy modeling alone would not have detected.
Telehealth's role in MA adequacy is narrower than many plans assume. Telehealth-only providers do not count toward the minimum provider count, and they are not physical locations for time-distance purposes. What telehealth earns is a credit: for the 15 specialty types listed in 42 CFR 422.116(d)(5), a plan with contracted telehealth providers in that specialty receives a 10 percentage point credit toward the required share of beneficiaries in a county.
This is a meaningful limit for plans that had built telehealth-dependent adequacy strategies. The credit lowers the bar; it does not by itself cure a deficiency. Plans counting virtual-only providers as if they were physical locations must replace them with physically located contracted providers, rely on a credit that actually closes the gap, or file an exception request.
The listed specialties include psychiatry, clinical psychology, clinical social work, and outpatient behavioral health, so the credit is especially relevant to behavioral health builds. It is still a credit, not coverage.
Behavioral health remains among the most persistent adequacy challenges across the Medicare Advantage market. CMS's list of provider and facility types includes Psychiatry, Clinical Psychology, Clinical Social Work, Inpatient Psychiatric Facility Services, and Outpatient Behavioral Health, each with its own time and distance standards and minimum counts.
That disaggregation increases compliance complexity, but it reflects the clinical reality that members needing psychiatric medication management have different access needs than members needing outpatient counseling. Plans that rely on one behavioral health group to satisfy several types should verify, type by type and county by county, that each required category is actually covered.
CMS's MA rules also require accurate provider directories. Directory accuracy and network adequacy are connected: a provider who is listed but not genuinely available inflates both the directory and the adequacy calculation. Check the current regulation text and CMS guidance for the exact update and verification requirements that apply to your plan.
The practical consequence is that plans need timely notification workflows from their contracting and credentialing systems to their directory management platform. A provider termination that sits in a contracting system for weeks before the directory team learns of it is a compliance risk, and plans should treat directory maintenance as a hard operational standard, not an aspirational goal.
CMS has authority to sanction plans for network adequacy failures. According to MedPAC's June 2024 report, it has never imposed intermediate sanctions or civil money penalties for network adequacy noncompliance, but new applications have been denied on that basis. Exceptions are not automatic either: in 2021, CMS denied 259 of 448 exception requests, about 58%.
For network teams, the takeaway is simple. Build against the current HSD Reference File, confirm any claimed rule change against the regulation text, and plan as if a weak network will cost you an application or an exception, because it can.
Blueprint automates the network build workflows described in this article: from adequacy modeling to provider outreach tracking. See it with your state and line of business.