Free Network Build Assessment
Score your buildWritten for health plan network development teams, compliance officers, and executives managing CMS adequacy requirements. Covers standards, strategy, submission, and what happens when things go wrong.
In This Guide
CMS scores a Medicare Advantage network with two tests, run separately for every county in the service area and for each of 29 provider types and 14 facility types. The first is a minimum count of contracted providers (for acute inpatient hospitals, beds). The second is time and distance: a required share of beneficiaries must have a provider of that type within the published maximum minutes and miles. A network needs both.
The legal basis is 42 CFR 422.116. CMS publishes the county-by-county standards in its HSD Reference File for each contract year, and the current guidance is its December 2024 network adequacy guidance.
Network Adequacy
Provider availability.Are there enough contracted providers of each required type within the required time and distance for members to reach them? This is what CMS's Automated Criteria Check scores in HPMS.
Network Access
Member experience. Can members actually get appointments with those providers in a timely way? A county passing the HSD test says nothing about how long a member waits. Member surveys ask about it, and those measures are one input to Star Ratings.
Medicaid and Exchange (ACA marketplace) plans have network adequacy requirements too, under separate rules. For Medicaid managed care, each state sets its own standards under 42 CFR 438.68. Exchange plans fall under 45 CFR 156.230. This guide covers Medicare Advantage under 42 CFR 422.116.
Key Takeaway
Network adequacy is a regulatory requirement, but it is also an operational discipline. Providers retire, move and terminate, and CMS publishes a new Reference File every year, so a network that passed once has no guarantee of passing again.
CMS assigns every county one of five designations under 42 CFR 422.116(c): Large Metro, Metro, Micro, Rural and CEAC (counties with extreme access considerations), and sets a maximum time and distance for each provider and facility type in each. For primary care that runs from 10 minutes and 5 miles in a Large Metro county to 70 minutes and 60 miles in a CEAC county.
Both the time threshold and the distance threshold must be met simultaneously. A provider 4 miles away that takes 20 minutes to reach fails a Large Metro primary care standard of 10 minutes and 5 miles, even though it meets the distance. And the share of members who must be within both is 90% in Large Metro and Metro counties, 85% in Micro, Rural and CEAC counties.
Loading CMS’s standards…
How CMS measures: it uses both travel time and travel distance from representative beneficiary locations, and its published methodology derives time from distance using area-specific speed assumptions. No current public CMS document says whether its software routes on roads or measures a straight line. The criteria aren't restricted by state or county boundaries, so a provider just over a line can serve your county.
Key Takeaway
CMS's beneficiary locations come from its MA Medicare Sample Census, which plans can't see, so treat your own distances as estimates. A straight line is never longer than the road, so a straight-line fail is real, but a straight-line pass is unconfirmed. Centroids flatter you: use dispersed points, and let CMS's check be the referee.
CMS organizes provider types into Health Service Delivery (HSD) categories. A plan must meet the time-distance standard for each applicable HSD category in every county within its service area. A gap in any single category in any single county is a deficiency, even if every other category in that county is fully covered.
This means a plan with a 200-county service area is managing 8,600 county and type pairs. Manual tracking at this scale is where errors accumulate.
For 2026 that is 29 provider types, from primary care and cardiology to clinical social work, and 14 facility types, from acute inpatient hospitals to outpatient behavioral health. The HSD reference lists every one with its standards.
CMS can add, split or change types from one contract year to the next. Check the HSD Reference File for your submission year before you build. See full HSD reference with specialty codes →
Key Takeaway
Every HSD category is a separate compliance obligation. A plan that achieves adequate PCP coverage across its entire service area but has a single behavioral health gap in one rural county has a deficiency. CMS does not aggregate across categories: each is evaluated independently.
For a new or expanding service area, February is the finish line of the build, not the start. Here is the path, laid against the CY2027 cycle because its dates are published. CMS says those dates are subject to change, and when we last checked, on September 30, 2026, it had not posted CY2028 dates.
Pull the current HSD Reference File and Provider Supply file, score your contracted network against each county's minimum and time and distance standards, and turn the result into a gap list with a named owner on every gap.
Outreach and contracting, hardest specialties first. Applicants can sign letters of intent where contracts won't close in time. Start credentialing as soon as a provider says yes.
Do a full internal re-score, decide which counties you are really filing, and clean every name and address. Anyone with a contract ID can upload to the Network Management Module at any time to test against CMS's check.
Since contract year 2024, applicants must demonstrate compliance as part of the application, under 42 CFR 422.116(a)(2)(ii). HSD tables for the requested service area go in with it. The Notice of Intent to Apply was due January 23, 2026.
CMS's check scores every provider and facility type in every county: the minimum count, and the share of beneficiaries within both the maximum time and the maximum distance.
CMS's deficiency notice opens the second of three upload rounds. It is a chance to upload corrected tables and to file exceptions where they apply.
The third round is the applicant's final upload opportunity, under 42 CFR 422.502(c)(2)(ii). CMS may deny an application based on its network evaluation.
Under CMS's December 2024 guidance, contract networks are reviewed on a triennial basis. Four events can pull a review forward: an application, a termination CMS considers significant, a network access complaint, and a gap the plan discloses.
For HSD table columns and the upload itself, see the HPMS Submission Guide.
Key Takeaway
The only things that close in a 10-day response window are things you started in the spring. Count back from CMS's date, put a name on every gap by June, and use the later rounds for cleanup rather than recruiting.
A county and type can fail on the count, on time and distance, or on both. Your internal report and CMS's check use different member locations, address handling and counting rules, so a network can pass internally and fail at CMS. These are the usual reasons.
Too few beneficiaries within the standard
Providers cluster in the county seat, and fewer than 90% of beneficiaries (85% in Micro, Rural and CEAC counties) have one within both the maximum time and the maximum distance. A network can pass the count and fail this.
Below the minimum count
CMS multiplies beneficiaries required to cover by the specialty's minimum ratio per 1,000, divides by 1,000 and rounds up to the next whole number. For acute inpatient hospitals the minimum is beds.
A provider who doesn't count, counted
Telehealth-only providers don't count toward the minimum. PAs and NPs under primary care codes 005 and 006 count only in the narrow case the Reference File's notes describe.
An address CMS's software can't place
CMS reads addresses as typed. Its 2017 guidance said an unlocated address with a valid ZIP gets a generated point inside the ZIP, and an invalid address and ZIP is left out of automated processing.
The wrong code
A primary care provider has to be under one of codes 001 to 006, and a provider submitted as Psychiatry, Clinical Social Work or Clinical Psychology can't also be submitted under Outpatient Behavioral Health (068).
A response to a deficiency notice is a chance to upload corrected tables and to file exceptions where they apply. The response is discussed in Section 8. For more, see CMS Deficiency Response.
Key Takeaway
Three of the five reasons above are data problems, not network problems. They can be fixed without adding a single provider, so check them first. An internal pass stays unconfirmed until CMS's check, run on the same tables, agrees.
42 CFR 422.116(f) doesn't ask whether you tried hard. CMS is asking whether its own picture of supply is wrong, and whether members will get care the way people in that county already do under Original Medicare. Dated outreach records matter because they are proof of why a provider inside the standard isn't available.
What a request has to show
What won't carry a request
What to keep as you go
Keep these as the work happens, not at filing time. A dated record made on the day is easier to stand behind than one rebuilt later. See the outreach records guide →
Key Takeaway
A good exception request is mostly a good census with an argument on top. If the honest answer to "why isn't this provider in network?" is about rates, that is a contracting decision, not an exception. Log every contact as it happens.
Under 42 CFR 422.116(f), inability to contract is not a valid reason for an exception. CMS's December 2024 guidance says so, because the non-interference clause in Social Security Act section 1854(a)(6) keeps CMS out of plan and provider negotiations. The plan's own internal standards aren't valid either. A request has to walk through one of these two doors.
When used: Certain providers aren't available in that county and specialty, as shown in the Provider Supply file, and the plan has contracted with others, possibly beyond the standard, who are available and accessible to most enrollees
Documentation requirements:
When used: A facility-based institutional SNP can't contract with certain specialty types because of how its enrollees receive care, or provides adequate access through additional telehealth benefits
Documentation requirements:
Rationales CMS lists for a provider not being in network
From the December 2024 guidance, which says the list is "not limited to" these. Two more, possible beneficiary harm and inappropriate credentialing under 42 CFR 422.204, need substantial and credible evidence.
A request to serve only part of a county is different: it falls under the county integrity rule in 42 CFR 422.2, not 422.116(f). And although the CY2027 proposed rule floated a standalone pattern-of-care exception, the final rule did not amend 422.116. For more, see Exception Requests.
Key Takeaway
If the evidence isn't there, the exception isn't either. The honest options are recruiting, a better offer or a smaller service area. For real supply gaps, start the census when the gap appears, because a Notice of Intent to Deny leaves 10 days.
The response is a chance to upload corrected tables and to file exceptions where they apply. It offers no flexibility on the standard itself. A county that fails the time and distance test needs a contracted provider in range or an approved exception. Follow the deadline in CMS's notice. For an applicant, the final round is the response to the Notice of Intent to Deny, with 10 days under 42 CFR 422.502(c)(2)(ii).
Correct the data
Fix mistyped addresses, wrong codes and providers left off. Read the Address Information Report and the ZIP Code Report for Failed Counties to see where the misses cluster.
File exceptions for genuine supply gaps
Only where the providers you would need really aren't available and your contracted network fits the local pattern of care. Start the evidence early: the response window isn't enough time to build a census.
Add providers you already have
A contract already signed, or for an applicant a mutually signed letter of intent marked Y, can go on the next upload. Recruiting from a standing start in this window rarely works.
Telehealth provider addition
For the specialties listed in 42 CFR 422.116(d)(5), contracting telehealth providers earns a 10 percentage point credit toward the share of members who must be within reach. It reduces a gap; it doesn't close one on its own, and it never touches the minimum count.
Common mistake: Treating the response as a negotiation
A well-written letter explaining why the standard is unreasonable for a county is not a path to approval. Spend the window on provider access or evidence.
Common mistake: Not reading the notice precisely
Note whether each county and type failed the minimum count, time and distance, or both, and which threshold applies. The fix is different for each.
For more on responding to a notice, see CMS Deficiency Response.
Key Takeaway
Ten days is enough to fix a mistyped address, add a provider whose contract was already signed, or finish an exception you had mostly built. It is not enough to recruit a cardiothoracic surgeon. Do the work that makes the later rounds short.
Suspension of enrollment is one of the intermediate sanctions listed in 42 CFR 422.750. But MedPAC's June 2024 report says CMS has never imposed intermediate sanctions or civil money penalties for network adequacy noncompliance, and adds: "However, new applications have been denied on this basis." Plan around the consequences that are on the record.
A denied application
Under 42 CFR 422.116, CMS may deny an application based on its network evaluation. For an expansion, that can mean a year without enrollment in that county.
Compliance or enforcement action
CMS's December 2024 guidance says operating contracts that fail a network review may face compliance or enforcement actions.
Suspension of enrollment
It exists in the regulation, and MedPAC says it hasn't been used for network adequacy. Treat it as a low-probability risk, not an expected cost.
Keep checking adequacy through the year, not just at upload time. Providers terminate, retire, and move, and a significant termination can trigger a network review.
Identify gap counties early. Our rule of thumb is a county list and target providers by June of the year before a February application.
Log outreach and outcomes as they happen. Don't wait for a deficiency notice to start recording your recruiting.
Start exception evidence as soon as you know a gap is a real supply problem. A gap you disclose yourself goes to your CMS Account Manager, and can pull a review forward.
For more on enrollment sanctions and how they apply, see Enrollment Freeze Risk.
Key Takeaway
Be precise about the risk when you brief leadership. The sharpest consequence on the record is a denied application, not a freeze or a fine. An operating contract with a gap faces possible compliance or enforcement action. An applicant with a gap can lose the county.
Network adequacy and Star Ratings aren't the same thing. They connect through the member: someone who can't get care may answer the CAHPS survey less favorably, and those measures are part of the Star Ratings, alongside many others. That chain is plausible rather than proven, and we don't know of a published estimate of how much network gaps move ratings.
How a Gap Could Reach a Rating
Adequacy gap
Provider unreachable
Access failure
Member can't get appointment
CAHPS survey
Access answers may slip
Star Rating
One input among many
Quality bonus
Set by the rating
What the bonus is
According to KFF, plans rated at least 4 out of 5 stars get a higher benchmark, usually by 5 percentage points, and star ratings also set the share of savings a plan keeps as a rebate. The dollar impact depends on your benchmarks, membership and county mix, so run it with your own actuaries.
The lag
Survey results lag the network, ratings lag the surveys, and bonus status is based on the prior year's rating. By the time an access problem shows up in a rating, it's too late to fix it for that year. Check CMS's current technical notes for the measures and their weights, which change.
For more on how to think about this link, see Network Adequacy and Star Ratings.
Key Takeaway
Model the link rather than asserting it. State your assumption about how much a network change moves the rating, and test it, because that assumption is the weakest link in any business case built on it.
Blueprint keeps contracting, outreach, credentialing status and adequacy scoring on the same provider records. It drafts for your team to review; it doesn't connect to HPMS, file anything, or measure drive time.
Adequacy scoring by county
Scored by county and specialty against CMS's 2026 standards, on straight-line distance. A straight-line pass shows as unconfirmed, and drive time isn't measured.
Contracting pipeline
Six stages for every provider: Prospect, Outreach, LOI signed, Contracting, Credentialing and In network, plus Declined.
Outreach and a draft request
Sequences with automatic emails, calls and tasks, recorded decline reasons, and a printable draft of an exception request.
HSD-format tables
Build HSD-format provider tables from your network, for your team to review and file.
Recruit list and dependencies
A ranked list of who to recruit next, and which providers a county depends on.
Roster check and screening
Roster check and screening against the OIG exclusion and Medicare opt-out lists. Credentialing status is tracked; Blueprint doesn't perform credentialing.
Related Tools and Guides
Blueprint gives your team adequacy scoring by county and specialty, a contracting pipeline, and HSD-format tables to review and file, so you can spend more time closing network gaps.