Free Network Build Assessment
Score your buildThe time-and-distance standard that applies to any given county depends on how CMS designates that county: Large Metro, Metro, Micro, Rural, or CEAC (counties with extreme access considerations). Using the right designation for every county is fundamental to accurate adequacy modeling.
CMS applies different network adequacy time-and-distance standards depending on how it designates each county in a plan's service area. Under 42 CFR 422.116(c) there are five designations: Large Metro, Metro, Micro, Rural, and CEAC (counties with extreme access considerations). Each carries materially different maximum time and distance limits, and applying the wrong designation to a county can produce an adequacy model that looks compliant when it is not (if you apply Rural limits to a Metro county) or flags gaps that don't exist (if you apply Large Metro limits to a Rural county).
Large Metro counties have the largest, densest populations, and CMS applies its tightest limits there. For Primary Care, the 2026 limit in a Large Metro county is 10 minutes and 5 miles. The logic is that in a dense market, providers are numerous enough that members should not need to travel far to access care.
Metro counties carry somewhat looser limits: 15 minutes and 10 miles for Primary Care. Micro counties loosen further, to 30 minutes and 20 miles.
Rural counties carry significantly looser limits, 40 minutes and 30 miles for Primary Care and longer for most specialty categories, reflecting provider scarcity and long travel distances.
CEAC counties, the sparsest designation, still carry numeric time and distance limits: 70 minutes and 60 miles for Primary Care in 2026. There is no designation in which the time-and-distance standard simply disappears. Where a plan cannot meet the standard in a county, the path is an exception request, not an assumption that the county is exempt.
CMS assigns each county its designation from the county's population and population density, under the criteria in 42 CFR 422.116(c). The designations are not drawn from commuting-area codes or other tract-level rural classifications, and they are not the urban, suburban, rural, and frontier categories some state programs use. The designation that applies to each county is published in CMS's HSD Reference File.
Because the designation comes from CMS's file, the right practice is simple: load the designation for every county in your service area directly from the current HSD Reference File rather than inferring it from a map, a state classification, or last year's model.
A designation applies to the whole county, but members don't all live in the same place. A single county can contain a dense city center, commuting corridors, and sparsely settled outer areas. The county-level designation collapses this within-county variation into a single set of limits.
This has practical implications. A county designated Metro may contain sparsely populated outer areas where members actually live. If your provider supply is concentrated in the county's population center, your model may show adequate coverage for most members while missing genuine access gaps in the outer areas. Understanding this is important for plans that serve large counties with significant geographic variation.
Conversely, a county designated Rural may contain a county seat with a hospital and a concentration of specialists. Plans that serve these counties may comfortably meet the Rural limits near that town while genuine access gaps exist in the most remote portions.
CMS publishes an HSD Reference File for each contract year, and county designations can change between files. When a county moves to a denser designation, for example from Rural to Micro, its time and distance limits tighten, and a network that was adequate last year may not be adequate this year.
Network operations teams should treat the designation check as a standing annual task, not a one-time setup. Compare the current HSD Reference File against the designations in your model for every service area county well before your adequacy filing deadline, and run your adequacy model against the current designations before finalizing your submission.
The practical implications of designation are most visible when you examine the specific standard differences. For Primary Care, the most scrutinized adequacy category, CMS's 2026 base standards are:
For specialist categories, the limits are generally wider, but the relative differences between designations follow the same pattern. Cardiology, for example, runs from 20 minutes and 10 miles in Large Metro counties to 95 minutes and 85 miles in CEAC counties. CMS also customizes standards for some counties, so the county's own row in the HSD Reference File is the number that governs. A plan building a network across a mix of designations must apply the correct limits and the correct required share to each county in its model.
CEAC counties are where plans most often run out of providers to contract. The standard does not change shape there: the plan still has to show the required share of beneficiaries within both the maximum time and the maximum distance. What changes is how often the honest answer is that the providers do not exist.
When that is the case, the plan files an exception request under 42 CFR 422.116(f). A strong request accounts for every provider in and around the county who is inside the standard, gives a checkable reason for each one not in network, and shows that the contracted providers are available and accessible to most enrollees, consistent with the local pattern of care. CMS's guidance says inability to contract is not a valid reason.
Plans that treat CEAC counties as adequacy-exempt misunderstand the obligation. Exceptions are not automatic: in 2021, CMS denied 259 of 448 exception requests, about 58%, according to MedPAC's June 2024 report. The documentation is examined closely, and a weak request leaves the deficiency standing.
CMS's HSD Reference File is the authoritative source for county designations and standards. When an internal model, a vendor tool, or a state classification disagrees with it, the HSD Reference File governs for Medicare Advantage adequacy purposes.
The most common source of disagreement is stale data: a model built on a prior year's file, or one that mapped counties to a state's own urban and rural categories. Rebuilding the county list from the current file each year eliminates most of these discrepancies before they reach a submission.
The most complex adequacy modeling challenges arise in large counties where population ranges from a dense center to a sparse fringe within the same county boundary. These counties are most common in the West and Midwest, where county geographies are large and population distribution is uneven.
Because one designation applies to the entire county, members in the sparse fringe are evaluated against the same limits as members in the population center. For plans with robust provider presence in the center and thin coverage elsewhere, this can produce a county-level adequacy calculation that passes threshold while leaving a meaningful portion of members with genuine access gaps.
Network operations teams in markets with large, uneven counties should consider supplementing their adequacy calculation with a sub-county analysis that maps provider time and distance against where members live. This analysis won't change the HPMS submission, but it can surface genuine access gaps before they become member grievances, and it can inform recruitment priorities.
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.