Free Network Build Assessment
Score your buildA CMS network adequacy deficiency notice is not the end of your filing, but the rounds that follow it are short. Here's what the notice means, how the HSD upload rounds work, what an exception needs, and how to organize your response.
Not every negative communication from CMS about a network adequacy filing carries the same weight or requires the same response. Start by working out what you actually received and whether you are an applicant or an operating contract, because the response and the timeline differ.
A deficiency notice means the HSD tables you uploaded fell short in one or more counties and specialty types. In an application, it opens the second of three upload rounds: the initial submission, the response to the deficiency notice, and the response to the Notice of Intent to Deny. It does not mean the filing has been rejected outright. Read the ACC result and the ZIP Code Report for Failed Counties to see exactly where you missed.
Some failures are data problems rather than network problems. CMS's Automated Criteria Check (ACC) reads provider addresses exactly as typed, and names and addresses have to be submitted the same way each time. Check for a mistyped address or a provider under the wrong specialty before you assume you have a recruiting problem. These are the quickest failures to fix.
A Notice of Intent to Deny (NOID) is the most serious step in an application and your final upload opportunity. For an operating contract, CMS's December 2024 guidance says networks that fail may face compliance or enforcement actions. Know which situation you are in before you plan the response.
We can't cite a fixed CMS corrective action period for network deficiency notices, so take the response date from the notice itself rather than from a number you remember. The response window that is written into regulation is the NOID: the applicant must respond within 10 days under 42 CFR 422.502(c)(2)(ii).
Plans should make sure HPMS messages get seen promptly. Designate a specific staff member to watch them, with an escalation path to the head of network or the chief compliance officer, so a short window doesn't get shorter because nobody opened the message.
Be realistic about what a short window can do. It is enough time 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 time to recruit a specialist. The deficiency and NOID rounds are not a recruiting extension, which is why the work has to start well before them.
If CMS asks for a corrective action plan (CAP), follow its instructions first. Beyond that, here is the structure we would use. This is our suggestion, not a CMS-published format. Open with a deficiency-by-deficiency analysis that acknowledges each gap and gives the plan's root cause: why the gap exists and what led to it in that county and specialty.
The core of the CAP is the remediation plan for each deficiency. For each county and specialty below the standard, provide: the specific remediation strategy (adding a provider via contracting, reopening a closed panel, submitting a valid exception), the name and NPI of any specific provider being recruited or activated, the expected timeline for contract execution and credentialing completion, and the individual responsible for each step. "We will contract with additional providers" says nothing a reader can check.
The CAP should also cover process improvements: what the plan is changing in its network development and monitoring to prevent the deficiency from recurring. A CAP that addresses the immediate gaps and nothing else leaves the cause in place.
One of the most operationally challenging aspects of responding to a deficiency is the need to bring in new providers during the CMS review. Contracting timelines depend on provider responsiveness, contract negotiation complexity, and the plan's internal approval processes. Credentialing timelines are constrained by primary source verification and cannot be fully compressed. Commit only to what is achievable.
Provider contracting can sometimes be accelerated using streamlined contract templates for providers joining an existing network to fill a gap, rather than full contract negotiations. Whatever the template, CMS expects fully executed contracts on the HSD tables. In an initial or service area expansion application, a letter of intent signed by both parties can stand in, and it must come off once the contract is executed.
Credentialing for new providers can start in parallel with contracting: plans do not need to wait for contract execution to begin primary source verification. Whether a provider can participate before credentialing is complete depends on the program, the state, your contract, and your credentialing policy, so assume no until someone shows you the clause.
For gaps in counties where the providers simply are not there, the exception request is the mechanism. Under 42 CFR 422.116(f), the plan files CMS's current exception request template in HPMS for one county and one specialty and has to show two things. First, the providers needed to meet the time and distance standard are not available, as shown in CMS's Provider Supply file. Second, the providers the plan did contract with, possibly beyond the standard, are currently available and accessible to most enrollees, consistent with the local pattern of care.
Inability to contract is not a valid reason, and neither are the plan's own internal standards. In 2021, CMS denied 259 of the 448 exception requests it reviewed, according to MedPAC's June 2024 report, and the most common reason was that CMS found providers within the criteria that the plan "failed to include." A good exception request is mostly a good census. See how to request an exception for the details.
When you are recruiting for some gaps and requesting exceptions for others, keep clear which gap is on which track. And remember that plans must resubmit all previously approved exceptions whenever CMS requests an HSD upload.
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." So for an applicant, the realistic worst case is losing the county or the application. CMS may deny an application based on its network evaluation under 42 CFR 422.116(a)(2)(ii).
For an operating contract, the guidance leaves compliance or enforcement action open. The critical variable you control is your own response: take the deficiency seriously, have a realistic plan, and execute it. Keep your CMS Account Manager informed. A gap the plan discloses itself has to be reported to the Account Manager in any case.
The documentation package submitted with a resubmission, whether following a deficiency notice CAP, a data error correction, or an exception request, is the evidentiary record on which CMS will base its determination. Assembling this package requires retrieving, organizing, and presenting documentation that may be scattered across multiple systems: the contracting database, the credentialing platform, the outreach CRM, provider communication records, and HPMS submission logs.
Best-practice resubmission packages are organized by deficiency, with each identified gap having its own documentation section. That section should include the original deficiency description from the CMS notice, the plan's remediation or exception response, and the supporting documentation for that response. For a remediation response, the supporting documentation includes: the executed contract (or, in an application, a mutually signed letter of intent) for any new provider, the credentialing approval, and evidence that the provider is accepting new plan members. For an exception response, the supporting documentation includes: the provider census for the county, the reason each non-contracted provider isn't in the network, and evidence that the contracted providers are accessible to most enrollees.
Keep a short internal summary of the response: which deficiencies are being addressed through remediation, which through exception, and any residual gaps with an explanation and timeline. It keeps everyone working from the same picture, and it is ready if CMS asks.
Blueprint keeps a history of work on each provider and recorded decline reasons, scores adequacy by county and specialty against the CMS 2026 HSD standards on straight-line distance, and ranks who would close a gap. It produces HSD-format tables and a printable draft of an exception request for your team to review and file; it doesn't file anything with CMS.
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.