Free Network Build Assessment
Score your buildCMS applies five distinct sets of time-distance standards based on county designation. Understanding which standards apply where, and how county boundaries interact with member population, is the foundation of every accurate adequacy calculation.
Before a network ops team can evaluate whether a county meets CMS time-distance standards, they must first know which set of standards applies. CMS does not use a single national threshold. Instead, under 42 CFR 422.116(c), it assigns every county one of five designations, Large Metro, Metro, Micro, Rural, or CEAC (counties with extreme access considerations), and each designation carries its own maximum time and distance for each provider and facility type.
This designation-first logic means that a plan with a thin specialist panel in a sparsely populated Montana county and a plan with the same panel density in Cook County are evaluated against entirely different benchmarks. Getting the designation wrong, even by one county, can produce adequacy calculations that are either artificially compliant or needlessly deficient. Neither outcome serves the plan well when CMS reviews the submission.
Understanding how designation works and where it comes from is the prerequisite to every other adequacy analysis task.
CMS sets each county's designation from two numbers: the county's population and its population density. The criteria are written into 42 CFR 422.116(c). They are not derived from commuting-area codes or other tract-level rural classifications, and the five designations are not the urban, suburban, rural, and frontier categories that some state programs use.
CMS publishes the designation for every county in its HSD Reference File. Plans should always take county designations directly from that file rather than inferring them from census data, a state classification, or a vendor's map.
The practical difference between designations is substantial, both in the limits and in the share of beneficiaries who must be within them. Large Metro and Metro counties require 90% of beneficiaries to be within both the maximum time and the maximum distance; Micro, Rural, and CEAC counties require 85%.
For Primary Care in 2026, the base standards are 10 minutes and 5 miles in Large Metro counties and 15 minutes and 10 miles in Metro counties. The rationale is that dense areas have dense provider markets, and members there have reasonable access options across a short geographic range. Specialists carry wider limits: Cardiology is 20 minutes and 10 miles in Large Metro counties and 30 and 20 in Metro.
Micro counties loosen to 30 minutes and 20 miles for Primary Care, and Rural counties to 40 minutes and 30 miles. Most specialists are wider still; Psychiatry, for example, is 60 minutes and 45 miles in Micro and 75 minutes and 60 miles in Rural.
CEAC counties, the sparsest designation, carry the loosest limits, 70 minutes and 60 miles for Primary Care and 110 minutes and 100 miles for Psychiatry, but they are still numeric limits that a plan must meet or address through an exception request. In the 2026 file, CEAC counties are concentrated in the Great Plains (Texas, Kansas, Nebraska, Montana, and the Dakotas lead), the mountain West, and Alaska, where provider-to-population ratios make the standards hardest to reach. CMS also customizes standards for some counties, so the county's own row in the HSD Reference File always governs.
Designation errors fall into two categories: plans that apply tighter standards than CMS assigns to a county, and plans that apply looser standards than CMS assigns. Both errors produce inaccurate adequacy models, but they have opposite consequences.
Applying standards that are too strict inflates the apparent adequacy gap in a county and may cause a plan to recruit providers it does not actually need to meet threshold. This wastes contracting resources and can skew network build priorities away from genuine gaps. Applying standards that are too loose does the opposite: it masks real deficiencies that CMS will catch during review, potentially resulting in corrective action plans or a denied application.
The most common source of designation errors is lag between the HSD Reference File and plan adequacy models. A county's designation can change from one file to the next, and plans using legacy adequacy tools or internally maintained spreadsheets frequently miss these changes because there is no automated notification mechanism: teams must proactively check the current file each benefit year.
A second common error involves mapping counties to a state's own urban and rural categories, or to a metropolitan statistical area, instead of CMS's designation. A county at the edge of a metro area may carry a CMS designation that differs from how the plan's internal geography team would describe it. When in doubt, the HSD Reference File controls.
CMS evaluates adequacy at the county level: plans must meet the applicable time-distance standard and minimum provider count for each required provider type in each county in their service area. That standard is scored against where beneficiaries live, using a representative sample that only CMS can see.
A large Rural county where providers cluster near the county seat may pass for members in town and still fall short of 85% if many members live on the opposite side of the county. Census tract analysis, evaluating which populated tracts within the county are within both the time and the distance limit, gives network ops teams the closest practical picture of where access gaps exist.
For large CEAC counties where travel times are long and population is sparse, tract-level analysis is the clearest way to see which members are driving the result. Blueprint scores each county by specialty using census tract population points, on straight-line distance, and ranks who would close a gap.
CEAC counties require a distinct operational approach because the standard adequacy playbook, recruit more providers until the county meets threshold, is often not viable. Provider supply is constrained by population density, and there may not be enough physicians of a given specialty in the county or adjacent counties to bring it into compliance with even the loosest published standard.
Plans can file exception requests for counties where meeting time-distance standards is not possible given provider supply. Exception requests should document provider supply constraints, demonstrate good-faith recruitment efforts, and describe the alternative access arrangements, such as telehealth, transportation benefits, and contracts with the nearest available out-of-county providers, the plan has implemented. Exceptions are not automatic: in 2021, CMS denied 259 of 448 exception requests, about 58%, according to MedPAC's June 2024 report.
That is why CEAC county exception strategy must be part of the initial network build plan, not a late-stage corrective action. Plans that discover exceptions are needed during final adequacy review before submission face compressed timelines that make a strong exception package difficult to assemble.
Blueprint shows each county's CMS designation and standards, so a team can spot CEAC counties early. For a county that fails, it prints a draft exception request for the team to review.
One subtlety that adequacy models frequently miss is the difference between geographic adequacy and population-based adequacy. An internal model may show a county as compliant because the nearest contracted provider is within threshold of the county centroid or the county seat. But CMS's test asks what share of beneficiaries are within reach, and if many members live in a part of the county that is farther from that provider, the internal model overstates access.
The boundary also cuts the other way. CMS's criteria are not restricted by county or state boundaries, so a contracted provider just across a county line can count toward a county if enough of that county's beneficiaries are within the applicable time and distance.
The practical implication is that network ops teams should evaluate provider coverage against the actual distribution of population or projected enrollment within the county, and should credit providers in neighboring counties and states. For counties with irregular shapes or significant population concentration in one sub-area, this distinction can be the difference between a county that looks compliant on paper and one that passes CMS's review.
Blueprint carries CMS's 2026 HSD standards for 3,221 counties, 29 provider types and 14 facility types, along with each county's designation and minimum provider counts. It scores by county and specialty on straight-line distance; drive time isn't measured, so a straight-line pass shows as unconfirmed.
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.