Free Network Build Assessment
Score your buildA gap notice, formally a deficiency notice, means CMS found shortfalls in one or more HSD categories during its review of your network. It's serious, and it's correctable. Here's a plain plan for your response.
Teams often say "gap notice." The term in CMS's review process is deficiency notice: CMS telling you that one or more county and specialty pairs failed its review, on the minimum count, on time and distance, or both.
A response by the date in the notice. It's a chance to upload corrected HSD tables and to file exceptions where they apply. It isn't a chance to negotiate the standard: a failing county needs a contracted provider in range or an approved exception.
CMS may deny an application, and MedPAC says new applications have been denied on this basis. Operating contracts that fail may face compliance or enforcement actions, though MedPAC says CMS has never imposed intermediate sanctions or civil money penalties for network adequacy noncompliance.
Six places to look first. Finding the real cause keeps you from making the same fix twice.
A provider left the network
Terminations lag. A provider who left in March can still look covered on an internal map in June, when your count and your coverage have already dropped.
A provider was counted too early
CMS's guidance says plans list providers with a fully executed contract. Letters of intent work only for applicants during the application, and they end when the contract year starts.
A specialty was filed wrong
A provider was submitted under the wrong HSD specialty. Check each provider against NPPES for the correct specialty and practice location.
A county leaned on one or two providers
When a county relies on one or two providers to meet the standard, it can fail as soon as one of them exits.
An address didn't work
CMS's Automated Criteria Check reads your provider addresses exactly as typed on the HSD tables. Each one has to be the office where the provider sees patients.
The county's standard changed
CMS's 2026 HSD Reference File lists 6,862 county and specialty criteria changes from 2025, including 807 county designation changes. A network that passed last year can fall short on the current file.
This order of work is our advice, not a CMS process. The only date that matters is the one in your notice.
Pull the Automated Criteria Check results and the ZIP Code Report for Failed Counties. Note whether each county and specialty failed the minimum count, time and distance, or both. Then re-score your whole network against the current HSD Reference File, so you know the full scope and not only what the notice names.
Correct what this upload can fix: addresses, specialties, and contracted providers missing from the tables. For each gap that remains, list the providers who could close it, and put first the ones who help the most.
Work your priority providers, and keep what this upload can fix separate from what is in the pipeline and when it will be ready. Only providers with a fully executed contract go on the tables, unless you are an applicant using letters of intent signed by both parties.
Upload corrected HSD tables to the Network Management Module by the date in the notice. An exception under 42 CFR 422.116(f) needs proof that the providers are not available and that your contracted network fits the local pattern of care. Inability to contract is not a valid reason.
It doesn't read the notice, track your deadline, or file anything. It shows you the gaps and helps you work them.
Blueprint keeps adequacy scoring and your recruiting pipeline on the same provider records, so your team can see what fails and work the providers who could close it:

A real screen from the walkthrough, on a fictional network.
3,221
counties in the CMS 2026 file, each with its own standards
5
CMS county types: Large Metro, Metro, Micro, Rural and CEAC
Drafts
of exception requests to print and review, from your outreach records
Talk to us about your counties, or request a free gap analysis. We'll show you what Blueprint scores, and what it can't confirm.
Or email us directly: mike@fusion-advisory.com