Free Network Build Assessment
Score your buildCMS time-distance standards are scored against where beneficiaries live, not against a county's center. Networks built without understanding member geographic distribution fail adequacy tests that county-center analysis said they would pass.
Many network adequacy models use a county's geographic center, the geometric centroid of the county polygon, as the reference point for time-distance calculations. It is an intuitive simplification, but it is not how CMS measures adequacy. CMS scores each county against a representative sample of beneficiary locations and asks what share of those beneficiaries have a contracted provider within both the maximum time and the maximum distance: 90% in Large Metro and Metro counties, 85% in Micro, Rural, and CEAC counties. For counties with uniform population distribution, the difference between the two approaches is minor. For counties with concentrated or uneven population distribution, it can determine whether a county passes or fails.
The practical consequence is that network operations teams that build adequacy models from a single county point are solving the wrong problem. They may recruit and contract providers that satisfy time-distance thresholds from the county's center while failing to satisfy those same thresholds for the places where many members actually live. When CMS scores the network against where beneficiaries are, gaps that didn't appear in the plan's internal model become visible, and those gaps generate deficiency findings that require corrective action.
Shifting to population-based adequacy analysis is one of the highest-leverage methodology improvements a network operations team can make. It doesn't require recruiting more providers: it requires recruiting the right providers in the right locations, which is a different optimization problem with a potentially different solution.
CMS's sample of beneficiary locations is representative for each county and, in CMS's words, available only to CMS. Plans can't see exactly where it places members. What plans can do is approximate it: model each county as many population points spread across the places people actually live, rather than as one point at the middle.
A single population-weighted centroid is better than the geometric center, but it is still one point. It hides the members at the edges of the county, which is exactly where most failures live. In a county where 80% of members live in one town and 20% are spread across the surrounding countryside, a provider in town may cover the town and still leave the county short of a 90% threshold.
The CMS calculation then asks, for each beneficiary location, whether a contracted provider of the applicable type is within both the time and the distance limit for the county's designation. The county passes the time-distance test when the required share of beneficiaries is covered. Models that use a county's center rather than dispersed population points will systematically misjudge counties where people and the center are far apart.
The most important insight from population-based adequacy analysis is that counties are not uniform. The geographic center of a county can be misleading in both directions: it may suggest inadequacy where members are well served, or suggest adequacy where members face real access barriers. An approach anchored to where members actually are provides a more accurate picture of both.
In suburban areas, population-based analysis typically reveals that the effective demand for access is concentrated along specific corridors, major roads, transit lines, or developed commercial areas, rather than distributed evenly across the county's land area. Providers located in the heart of those corridors satisfy adequacy much more efficiently than providers located at the county's geographic periphery, even if both locations are technically within the county boundary.
In rural counties, population-based analysis often reveals that much of the county's population is clustered around a single town, sometimes the county seat, sometimes a larger commercial center, and that the geographic center of the county is far from any significant population concentration. Providers located in or near the population cluster cover most county members, while providers located closer to the county's geographic center serve very few. The members outside the town still count, though, and they often decide whether the county reaches the required share.
The American Community Survey (ACS) and the decennial census provide census tract-level population data that is a practical input for population-based adequacy modeling. Census tracts are small statistical areas, which makes them a useful unit of geographic analysis that is granular enough to capture population distribution patterns without being so fine-grained that the data becomes unstable from year to year.
For adequacy modeling, each tract's population is associated with the tract's center of population, and those tract-level points are kept as separate points within each county rather than averaged into a single county point. The result reflects the actual distribution of population across the county and provides a much more accurate representation of where members are than the county's geometric center.
Network operations teams that build their adequacy models on census tract data should also be aware that census data has a lag: the most recent decennial census data is from 2020, and ACS five-year estimates provide the most current tract-level population figures but still lag real population change by several years. In rapidly growing counties or counties experiencing significant demographic shifts, census-based points may diverge from where members actually live. Plans in dynamic markets should compare census-based models with actual enrollment data, where available, and treat any internal result as unconfirmed until CMS's own results agree.
One of the most common adequacy modeling challenges involves high-density suburban corridors that straddle county lines. In metropolitan areas, population density often follows development patterns, major roads, transit corridors, employment centers, that cross county boundaries without regard for the administrative divisions that structure CMS adequacy calculations. A densely populated suburban corridor may have the majority of its population on one side of a county line, with the most accessible providers on the other side.
CMS adequacy calculations are county-specific: each county is evaluated independently against its applicable time-distance threshold. But CMS's criteria are not restricted by county or state boundaries. A contracted provider located across the county line counts for a county if enough of that county's beneficiaries are within the applicable time and distance. Internal models that only credit providers inside the county will show gaps that CMS would not find.
The practical strategy for cross-county corridor situations is to map the population points for all counties in the metropolitan service area simultaneously, identify providers within or near each county that are accessible to each county's population, and prioritize contracting with providers that are geographically positioned to satisfy multiple counties' adequacy requirements simultaneously. Providers located near county boundaries in high-density corridors can often count toward adequacy for two or more counties, making them particularly high-value targets for network recruitment in metropolitan markets.
The rural county scenario is in many ways the mirror image of the suburban corridor challenge. Rural counties are geographically large, some covering thousands of square miles, but their populations are often concentrated in a single town or a small number of communities. The county's geographic center may be in an uninhabited area far from any significant population concentration, while the majority of the county's residents live in or near a single population center that may be offset from the geographic center by tens of miles.
For adequacy modeling, this means that a provider located in or near the dominant town covers most of the county's population, even if the provider is not centrally located from a geographic standpoint. Conversely, a provider located at the county's geographic center, which might seem like an optimal central location from a mapping perspective, may actually be less accessible to the majority of county residents than a provider in the dominant town.
This insight has direct implications for rural network recruitment strategy. In single-center rural counties, the highest-impact first recruitment target is usually a provider in or near the dominant population center. The next target is whoever practices nearest to the members still outside the limits. Plans that have been recruiting rural providers based on geographic centrality rather than population may have been prioritizing the wrong locations.
Building a population-based adequacy model requires three data inputs: census tract population data with tract-level population points, county boundary files that enable tract-to-county assignment, and contracted provider location data with geographic coordinates. Each of these data sets is publicly available, census tract data from the Census Bureau, county boundaries from the Census TIGER/Line shapefiles, and provider location data from NPPES, and can be combined in a GIS environment or dedicated adequacy analysis platform.
The process involves, for each county in the service area: identifying all census tracts that fall within the county boundary, keeping each tract's population point and population, and loading the county's designation and standards from the current HSD Reference File.
The adequacy calculation then follows the CMS structure: for each county and each provider and facility type, determine for each population point whether a contracted provider of that type, in or out of the county, is within both the maximum time and the maximum distance; add up the population covered; and compare the covered share to the required 90% or 85%. Separately, compare the number of contracted providers to CMS's minimum count for that county. The output is a county-by-specialty adequacy matrix that approximates CMS's measurement approach far better than a single-point model.
The most immediate operational impact of population-based adequacy analysis is on provider recruitment targeting. When adequacy gaps are identified using where people live rather than county centers, the gap locations are often different, sometimes dramatically so, from where county-center analysis would have directed recruitment resources. This changes the list of high-priority outreach targets and, in some cases, changes which counties are flagged as priority gaps at all.
Population-based targeting allows network operations teams to evaluate potential recruitment targets not just by whether they are in the gap county, but by how many uncovered members their location would bring within the limits. Recruitment resources directed toward those providers produce more adequacy improvement per contracted provider than resources directed toward providers who are merely central on a map.
Blueprint models each county from 2020 Census tract centers of population and scores it by specialty against CMS's standards on straight-line distance, then ranks who would close a gap. It doesn't measure drive time, so a straight-line pass shows as unconfirmed, and every result is a planning estimate until CMS's own tools confirm it.
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.