Free Network Build Assessment
Score your buildTechnical reference
What Blueprint measures today, the rules it follows, and what isn’t built yet. Every limit comes from a reference file you load, every result shows its source and date, and where data is missing the result says so instead of guessing.
Section 1
For Medicare Advantage, CMS assigns every county one of five types under 42 CFR 422.116(c), based on its population and density, and publishes the assignments in its HSD Reference File. The type sets the share of beneficiaries that must be within the standard. Blueprint uses CMS's assignments as published; for your own standards, the type comes from your counties file. A county without one isn't scored.
| County type | Share of beneficiaries that must be within the standard |
|---|---|
| Large Metro | 90% |
| Metro | 90% |
| Micro | 85% |
| Rural | 85% |
| CEACCounties with Extreme Access Considerations | 85% |
Shares from 42 CFR 422.116(d)(4). Minutes and miles come from CMS’s file county by county, because CMS customizes the standard wherever the base standard for the county type can’t be met. In 2026 that is about 7,500 county and specialty pairs.
Section 2
Each county is scored for each of CMS's 29 provider and 14 facility types. A type has to meet every test its standard imposes; a high score on one doesn't make up for a miss on another. Primary care is scored as CMS scores it: general practice, family practice, internal medicine, geriatrics, and primary care PAs and NPs counted together.
Distance
The share of the county's population within the maximum miles of at least one counted provider of that specialty, compared with the share required for the county type.
Time
The same test in minutes. It needs road routing, which isn't connected yet, so time is shown as not measured rather than estimated.
Minimum count
Distinct providers serving the county, counted once however many offices they have, against CMS's published minimum for that county. CMS sets it from the beneficiaries required to cover (beneficiaries times the 95th percentile base population ratio for the county type), not total beneficiaries. For acute inpatient hospitals the minimum is beds, not hospitals.
Who counts
Only providers who are both contracted and credentialed. A signed but uncredentialed provider doesn’t count; counting them is the most common way a build overstates its coverage. While an application for a new or expanding service area is pending, providers with a signed Letter of Intent count too.
Each credit lowers the required share by 10 percentage points for the time and distance tests, and they add together: MedPAC’s June 2024 report to Congress shows a rural county with the telehealth and Certificate of Need credits needing 65%. Credits don’t change minimum counts, and none apply unless you turn them on.
Telehealth
422.116(d)(5)
For the 15 specialties the regulation lists, when at least one counted provider in that specialty offers telehealth.
Certificate of Need
422.116(d)(6)
For the county and specialty pairs on CMS's Certificate of Need list, except where CMS has customized the county's standard.
New or expanding service area
422.116(d)(7)
While an application is pending. In this mode, providers with a signed Letter of Intent also count.
Every test that applies was measured and met on a road network. Straight-line measurement can't produce this status.
Nothing failed, but a test relied on straight-line distance or couldn't be measured. Compliance is not proven.
At least one test definitively failed, with the shortfall and the uncovered population shown.
No standard for this specialty and county type, or no population data for the county. We say which, instead of filling in a number.
A county takes the worst status of its specialties.
Section 3
Every county is measured in a straight line first, and can then be re-measured on the road network with drive times. A straight line is never longer than the road, and that sets how far each result can be trusted.
A straight-line fail is definitive
If beneficiaries are too far from a provider in a straight line, the road is at least as far. The same holds for counts: a shortfall measured this way is real.
A straight-line pass is unconfirmed
A provider inside the limit in a straight line can be outside it by road. So a straight-line pass is an upper bound, and Blueprint reports it as unconfirmed, never as a pass.
Drive time is never estimated from distance. That would need an assumed speed, which is an invented number. Drive times and road distances come from a routing server (OSRM, on OpenStreetMap roads, free-flow, no traffic); only a road-measured result can be a confirmed pass. Routing runs when a routing server is connected to your Blueprint deployment, and isn’t connected on blueprintnetworkhub.com yet. Population is measured from Census 2020 tract population centers, labeled as such, unless you load CMS’s sample beneficiary file from HPMS or your own enrollment, which then replaces them.
Section 4
Pass or fail is the start. These answer what to do about it, and produce the files CMS asks for, from the same data and the same rules.
Who to recruit first
Ranks providers who aren't counted yet by the coverage each would add, given the picks above it, so two practices on the same street aren't both recommended for the same gap. Candidates come from your pipeline, any list you load (such as CMS's supply file), and CMS's Medicare directory: every Medicare-enrolled clinician in the specialties CMS counts, plus certified hospitals and skilled nursing facilities with their beds.
Who you depend on
For each counted provider, the coverage the county would lose if they left, and whether losing them would turn the county to failing.
The map
Coverage by county with what-if recruits and the providers you depend on marked. Exports as an image stamped with the standards source, the date and the straight-line caveat.
Draft HSD tables
The Provider and Facility HSD tables CMS asks for, with each in-network provider listed in every county it serves, under SSA codes and individual primary care codes. Fields Blueprint can't know are left blank and listed.
Pre-check report
Pass or fail by county and specialty, with the share within distance and time, the credited threshold, and counts, laid out like the HPMS automated check.
Exception requests
For a failing county: every uncontracted provider inside the standard, each with a reason CMS accepts, plus the contracted providers members use just beyond it. Exports as CSV or a printable document.
Section 5
For Medicare Advantage, only your roster. CMS's reference file, Census population, CMS's Medicare directory and the taxonomy crosswalk ship with Blueprint. Column names are matched loosely, so Max Miles, max_miles and MAXMILES are the same column.
| File | Columns | Notes |
|---|---|---|
| Providers | NPI, name, specialty, address or latitude and longitude, contracted, credentialed, telehealth, Letter of Intent, beds | The one file you always supply; a CMS HSD table loads as is. Specialty can be the CMS name, the HSD code or the NPI taxonomy code. Providers marked In network in your Blueprint workspace are included automatically. |
| Standards (optional) | specialty, county type, max minutes, max miles, minimum count, minimum per 1,000 | For Medicaid, Marketplace or your own rules. Not needed for Medicare Advantage. Rows can apply to one county by FIPS. |
| Counties (optional) | FIPS, name, state, county type, a representative point, beneficiaries, beneficiaries required to cover | Not needed for Medicare Advantage. The county type comes from this file; Blueprint never infers one. |
| Certificate of Need list (optional) | FIPS, specialty | Only for your own standards. CMS's list comes with the CMS data. |
| Beneficiaries (optional) | county (FIPS or SSA code), ZIP or latitude and longitude, beneficiaries | CMS's sample beneficiary file from HPMS, or your enrollment. Replaces Census tract population for the counties it covers. |
| Recruit list (optional) | NPI, specialty or HSD code, address or coordinates | CMS's supply file, or any list of providers to recruit. Nobody on it counts toward adequacy. |
Section 6
The engine scores whatever standards table you load against it, so each program is scored on its own rules and never mixed with another's.
Medicare Advantage
42 CFR 422.116Built in: CMS's 2026 HSD Reference File for every state, the required shares by county type, and the three credits. Pick your states and load your roster.
Medicaid managed care
42 CFR 438.68Each state sets its own time and distance standards. Load the state's table with its required share, as one number or one per county type. Appointment wait-time standards and secret shopper surveys aren't tracked yet.
Marketplace plans
45 CFR 156.230Time and distance standards load as a table like any other. The Essential Community Provider threshold isn't tracked yet.
D-SNP
42 CFR 422.116Scored against Medicare Advantage standards like any MA plan. Requirements a state adds on top aren't modeled.
Section 7
What a submission-grade adequacy tool needs that Blueprint doesn't do today. We list it here so you never have to find out from a result.
Routing on blueprintnetworkhub.com
Road distance and drive time work once a routing server is connected; ours isn't yet, so results here stay straight-line and unconfirmed.
Proof against CMS's own results
Blueprint follows CMS's published rules and data, but CMS's exact distance method isn't public. We haven't yet compared our results with a plan's actual HPMS check.
Exact provider locations
Directory and address-only providers sit at their ZIP's center. Rosters with coordinates are measured exactly.
Multiple locations in the workspace
Your workspace stores one location per provider. Uploaded rosters can list each office.
SAM and uploaded rosters in screening
Rosters typed into the portal are checked each week against OIG's exclusion list and CMS's opt-out list. SAM isn't part of the weekly screening, and roster files that are uploaded aren't screened. The Directory Audit add-on checks an uploaded file against OIG, SAM and the opt-outs when you run it.
Medicaid wait times and Marketplace ECPs
Appointment wait-time standards, secret shopper results and Essential Community Provider counts aren't tracked.
Section 8
Adequacy runs on provider data (names, NPIs, specialties and locations) and county-level population. It doesn't use member records, and Blueprint doesn't ask for claims.
CMS and Census reference data ships with Blueprint. Files you load stay in your browser. Your pipeline lives in your Blueprint workspace, which only its members can see. Questions about data handling? Contact us.
We’ll load your counties and roster and walk through the results with you, including what’s unconfirmed and why.