Free Network Build Assessment
Score your buildCMS time-distance standards are scored against where beneficiaries live, county by county, and both the time and the distance limit must be met. Here's how the calculation actually works, and where internal models drift from CMS's results.
Time-distance standards in CMS network adequacy are a proxy measure for member access. The underlying question is simple: can a plan member who needs a given type of care reach a contracted provider within a reasonable time and distance? CMS has translated that goal into quantitative thresholds, a maximum travel time and a maximum travel distance, for each of 29 provider types and 14 facility types in each county, set in 42 CFR 422.116 and the HSD Reference File.
Understanding how these thresholds are applied matters for network teams because the method has specific choices that are not always intuitive. Which county designation applies, how beneficiaries are represented, and what share of them must be within reach are all defined by CMS in ways that can produce different results than a network team might expect from a naive reading of the standard.
This guide works through the method systematically: from the county designation that determines which threshold applies, through how CMS places beneficiaries and what share must be in reach, to how provider availability affects the result. Understanding these details allows network teams to run internal adequacy calculations that align with CMS's results, rather than discovering discrepancies at the point of submission.
Each provider and facility type in each county has two limits: a maximum time in minutes and a maximum distance in miles. A beneficiary counts as having access only if a contracted provider of that type is within both limits. If the provider is within the distance limit but outside the time limit, or the reverse, that beneficiary does not count.
Plans that run internal calculations using different road network data, different routing methods, or straight-line distance where CMS's results reflect travel may produce results that differ from CMS's. Treat any internal estimate that CMS did not produce as unconfirmed until it matches CMS's results.
The practical implication of the two-limit test is that a provider who is close in distance may still fail the time test if the route requires a circuitous path, as is common in areas separated by rivers, mountain ranges, or limited-access highway corridors. Network teams building in rural or geographically complex markets should verify both measures for marginal counties rather than assuming that a provider who passes the mileage test will also pass the time test.
The standard is not met by a single nearest provider. It is met when the required share of beneficiaries in the county has a contracted provider of that type within both limits: 90% in Large Metro and Metro counties, and 85% in Micro, Rural, and CEAC counties. A county with one cardiologist 15 miles from the county seat can still fail if too many beneficiaries live farther out.
CMS also sets a minimum number of providers for each type in each county, county by county, based on the number of beneficiaries. A county must pass both the minimum count and the time-distance share. Credits for telehealth, Certificate of Need states, and new or expanding service areas can each reduce the required share by 10 percentage points where they apply, but none of them changes the minimum count.
The word "available" carries real operational weight. A provider counted toward adequacy should have an active, executed participating provider agreement with the plan, should have completed credentialing with a current and active status, and should be genuinely seeing the plan's members. A provider who fails any of these conditions should not be in your adequacy calculation, even if they are otherwise the nearest contracted provider in the specialty.
Panel status is the most operationally dynamic of these conditions. Providers open and close their panels based on patient volume, staffing, and practice economics. A provider who is accepting new patients in January may have a closed panel by June. This is why panel-status attestation cadence matters: if your adequacy calculation is based on panel-status data that is six months old, you may be counting providers who are no longer genuinely available.
Panel status is more nuanced than the simple open/closed binary that most provider databases record. Panel status can be product-specific and member-population-specific: a provider may be accepting new patients for commercial insurance but not for Medicare Advantage, or may be accepting new adult patients but not new pediatric patients.
For Medicare Advantage adequacy, the relevant panel status is the provider's willingness to accept new Medicare Advantage plan members specifically. A provider who accepts Medicare fee-for-service patients but has opted out of all MA plan contracting is not available for MA adequacy purposes even if they are physically close to your members. Conversely, a provider who is contracted with your MA plan and accepting new MA plan members is available, even if their panel for other insurance products is closed.
This product-specificity creates a data management challenge. Most provider attestation forms ask about panel status in general terms, "Are you currently accepting new patients?", without capturing product-level availability. Collecting product-specific status gives you a more precise picture of who is really available.
A practical recommendation: when redesigning your provider attestation workflow, add a product-specific question, "Are you currently accepting new Medicare Advantage plan members?", in addition to or instead of the general accepting-new-patients question.
Under 42 CFR 422.116(c), CMS assigns every county one of five designations: Large Metro, Metro, Micro, Rural, or CEAC (counties with extreme access considerations). CMS sets the designation from the county's population and population density. It is not based on commuting-area codes, and it is not the urban, suburban, rural, and frontier scheme some state programs use.
The designation sets the limits. For Primary Care in 2026, the base standard is 10 minutes and 5 miles in Large Metro counties, 15 and 10 in Metro, 30 and 20 in Micro, 40 and 30 in Rural, and 70 and 60 in CEAC. CMS also customizes standards for some counties, and a customized standard can only be higher than the base, never lower. Network teams should take each county's designation and standards directly from the current HSD Reference File rather than inferring them from census or state data.
One designation applies to the whole county, even where the population ranges from a dense center to a sparse fringe. CEAC counties, the sparsest designation, still carry numeric time and distance limits. Where providers genuinely do not exist, the plan files an exception request, documenting the county's provider supply and the geographic constraints on access along with its outreach logs. Exceptions are not automatic: in 2021, CMS denied 259 of 448, about 58%, according to MedPAC's June 2024 report.
CMS does not measure from a single county centroid. It scores each county against a representative sample of beneficiary locations, which CMS describes as available only to CMS. Plans can't see exactly where CMS's sample places members, so the best internal approximation is a dispersed set of population points, such as census tracts, rather than one point per county.
CMS's criteria are also not restricted by county or state boundaries. A provider just across a county or state line counts for your county if enough of your county's beneficiaries are within the applicable time and distance of that provider. An internal tool that only credits in-county providers will fail counties CMS would pass.
The most reliable check is CMS's own: run your HSD tables through CMS's network adequacy tools before you file, and compare the results to your internal model county by county. Every disagreement points to a difference in how the two models place members, locate providers, or apply the standard.
Ghost providers, a colloquial term for providers who appear in adequacy calculations as available but are not genuinely accessible to new patients, are one of the most significant accuracy problems in network adequacy submissions. Ghost providers take several forms: providers with formally open panels but appointment wait times so long that access is functionally unavailable; providers whose NPPES record is active but whose practice has wound down or relocated; providers who are contracted with the plan but have stopped accepting Medicare Advantage patients specifically; and providers who have retired or left the market but whose records haven't been formally deactivated.
Secret shopper programs, where callers contact provider offices posing as new patients seeking appointments, are one way ghost providers surface. A plan can pass the mathematical adequacy threshold while still failing a provider availability or directory review if the providers counted in the calculation are not genuinely accessible to members.
The practical response to the ghost provider problem is regular call-out testing, contacting a sample of providers counted in your adequacy calculation to verify appointment availability. Call-out testing should be weighted toward providers in specialty categories and counties that are at or near adequacy threshold, and the results should be documented with date, time, caller identity, and provider response. Document what you find, and remove ghost providers from your adequacy model before submission.
Telehealth's role in network adequacy is often misunderstood. CMS's position is more specific than either "telehealth counts fully" or "telehealth doesn't count at all," and the details have significant operational implications for network teams.
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), including psychiatry, clinical psychology, clinical social work, and primary care, a plan with contracted telehealth providers in that specialty receives a 10 percentage point credit toward the required share of beneficiaries in a county. The credit lowers the bar. It does not by itself cure a deficiency.
Plans that have counted virtual-only providers as if they were physical locations should audit their adequacy models to ensure they are no longer doing so, because the gap will still be there when CMS scores the network.
Blueprint applies the telehealth credit only in the specialties CMS lists. It scores providers at the addresses it is given, so don't enter a telehealth-only provider as if it were a physical location.
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.