How CMS County Classifications Determine Your Network Adequacy Standards

The Four County Classifications and Their Thresholds

CMS applies different network adequacy time-and-distance standards depending on how it classifies each county in a plan's service area. The four classifications — urban, suburban, rural, and frontier — carry materially different threshold requirements, and applying the wrong standard to a county can produce an adequacy model that is simultaneously over-compliant (if you apply rural standards to an urban county) or non-compliant (if you apply urban standards to a county that is actually rural).

Urban counties are those with the highest population density and the most robust provider supply. CMS applies its tightest time-and-distance standards to urban counties — for example, requiring primary care access within 10 miles or 20 minutes for a specified percentage of the covered population. The logic is that in a dense urban market, providers are numerous enough that members should not need to travel far to access care.

Suburban counties carry somewhat looser standards than urban counties, reflecting lower density and longer typical travel distances. Primary care thresholds for suburban counties are typically in the range of 15 miles or 30 minutes.

Rural counties carry significantly looser standards, typically 30 to 60 miles or 60 minutes for most specialty categories, reflecting the reality of provider scarcity and long travel distances in rural America.

Frontier counties — the sparsest category — often have no quantitative time-and-distance standard at all. Instead, CMS requires plans to document their good-faith recruitment efforts and to demonstrate that available providers in the county are contracted, even if those providers don't meet a specific mileage threshold. Frontier counties operate on an access documentation standard rather than a numeric adequacy standard.

RUCA Codes: The Underlying Methodology

CMS's county classifications are derived from the Rural-Urban Commuting Area (RUCA) coding system, developed by the USDA Economic Research Service and the University of Washington. RUCA codes classify census tracts based on population density and commuting patterns, using a 10-code primary classification system and a more granular secondary coding layer.

RUCA codes 1 through 3 correspond to urban core and high-density suburban tracts. Codes 4 through 6 correspond to large rural towns with some urban commuting integration. Codes 7 through 9 correspond to small rural towns and rural areas with minimal urban integration. Code 10 identifies isolated rural tracts with very low population density — the frontier category.

CMS maps RUCA codes to its four county classification categories using a crosswalk that the agency updates periodically as new census data becomes available. The crosswalk determines which RUCA code ranges correspond to urban, suburban, rural, and frontier designations for adequacy purposes.

Why County-Level Classification Is an Approximation

RUCA codes are assigned at the census tract level, not the county level. A single county can contain census tracts spanning multiple RUCA code categories — urban tracts near a city center, suburban tracts along commuting corridors, and rural tracts in the county's outer areas. The county-level classification CMS uses in HPMS is therefore an approximation that collapses this within-county variation into a single classification.

This approximation has practical implications. A county that is classified as suburban at the county level may contain rural census tracts in its outer areas where members actually live. If your adequacy model applies suburban thresholds uniformly across the county, it may show adequate coverage in the county centroid while missing genuine access gaps in the rural portions. Understanding this limitation is important for plans that serve large counties with significant geographic variation.

Conversely, a county classified as rural may contain a small urban cluster — a county seat with a hospital and a concentration of specialists — where suburban standards would actually capture the access reality more accurately. Plans that serve these counties may be meeting or exceeding the rural standard in the urban cluster while genuine access gaps exist in the truly rural portions.

CMS Classification Updates: The 2025 Reclassifications

CMS updates its county classification data when new census information becomes available or when RUCA methodology is revised. The 2025 benefit year brought a significant reclassification affecting 43 counties nationally, driven by updated census tract data from the 2020 Census and subsequent American Community Survey estimates.

For the affected counties, the reclassification changed which adequacy standard applies — and therefore whether previously adequate networks remain adequate under the new standard. Counties that shifted from rural to suburban classification, for example, faced a tightened time-and-distance standard for the 2025 submission. Plans that hadn't updated their adequacy models to reflect the reclassification filed submissions that were evaluated against the old standard and then discovered deficiencies in audit review.

Network operations teams should treat the CMS county classification update as a standing annual task, not a one-time setup. Check the HPMS county classification data for your service area counties at least 90 days before your adequacy filing deadline, and run your adequacy model against the updated classifications before finalizing your submission.

Adequacy Standard Differences by County Type

The practical implications of county classification are most visible when you examine the specific standard differences across classification categories. For primary care physicians — the most scrutinized adequacy category — CMS has published the following thresholds for the 2025 benefit year:

• Urban: 85% of members within 10 miles or 20 minutes of a contracted PCP
• Suburban: 85% of members within 15 miles or 30 minutes
• Rural: 85% of members within 30 miles or 45 minutes
• Frontier: Good-faith documentation of all available contracted providers; no quantitative threshold

For specialist categories, the thresholds are generally wider — reflecting the lower density of specialist supply even in urban markets — but the relative differences between county classifications follow the same pattern. A plan building a network in a mix of urban, suburban, and rural counties must maintain separate adequacy calculations for each classification and apply the correct threshold to each county in its model.

Frontier County Standards and Access Exceptions

Frontier counties represent the special case where the standard documentation paradigm inverts. Rather than calculating a percentage of members within a defined time-and-distance threshold, plans serving frontier counties are expected to demonstrate that they have contracted with all available willing providers in the county, and to document their outreach to any providers who declined to participate.

CMS's frontier exception process requires the plan to identify all providers in the frontier county who are eligible to participate in the network, document outreach to each, and explain why any non-participating providers are absent from the network. If the county simply has no providers in a given specialty, the exception documentation should reflect that reality with supporting evidence — county-level provider density data, state licensing board provider counts, or HRSA shortage area designations.

Plans that treat frontier counties as adequacy-exempt — assuming that because there is no numeric threshold, there is no compliance requirement — misunderstand the obligation. The documentation requirement is real and is examined in audits. The difference is that adequate documentation, rather than a numeric calculation, satisfies the standard.

When County Classifications Are Wrong: Challenging HPMS Data

CMS's county classification data in HPMS is the authoritative source for adequacy modeling purposes — but it is not infallible. Cases exist where the HPMS classification does not accurately reflect the underlying RUCA code distribution in a county, either because of data lag, methodology updates that haven't been fully incorporated, or geographic edge cases.

Plans that believe a county is misclassified can challenge the classification through the HPMS comment process during the adequacy submission window. The challenge must be supported by RUCA code data for the county's census tracts, documentation of the crosswalk methodology, and an argument for why the current HPMS classification does not reflect the county's actual density profile.

Successful classification challenges are uncommon but consequential. A county reclassified from suburban to rural carries a loosened adequacy standard that may allow the plan to meet threshold without additional provider recruitment. Even if the challenge is not accepted for the current benefit year, it creates a documented record that may support exception filing rationale.

Multi-RUCA Counties and Mixed Classification Handling

The most complex adequacy modeling challenges arise in counties with significant RUCA code heterogeneity — counties where census tracts range from urban core to rural 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.

CMS's HPMS adequacy tool applies a single county-level classification to the entire county, which means that members in rural census tracts are evaluated against the same standard as members in the urban cluster. For plans with robust provider presence in the urban cluster and thin coverage in rural areas, this can produce a misleading county-level adequacy calculation that passes threshold while leaving a meaningful portion of members with genuine access gaps.

Network operations teams in markets with multi-RUCA counties should consider supplementing their HPMS adequacy calculation with a sub-county adequacy analysis that maps provider time-distance against member distribution at the census tract level. This analysis won't change the HPMS submission, but it will surface genuine access gaps before they become member grievances or audit findings — and it will inform targeted recruitment priorities.