By the Time the Notice Arrives, You're Already Behind
A CMS deficiency notice should not be a surprise. The problem behind it, a missed minimum count or a time and distance failure in a specific county and specialty, was usually sitting in your network well before CMS scored it. The notice is CMS telling you what you could have caught yourself: any organization with a contract ID can upload HSD tables to the Network Management Module at any time to test.
A good response treats the notice as a data and execution problem, not a crisis. Emergencies make people cut corners. Here are five mistakes to avoid, and what a competent response looks like.
Mistake 1: Treating Effort as the Defense
The natural reaction to a deficiency notice is to call every provider in the gap county and try to sign contracts right away. Urgency is correct. The mistake is believing that a record of hard work will carry the response.
CMS's December 2024 guidance says inability to contract is not a valid exception rationale, because the non-interference clause keeps CMS out of plan and provider negotiations. A log of unanswered calls won't excuse a gap. A gap closes with a contracted provider in range or, where supply really isn't there, an approved exception under 42 CFR 422.116(f).
Log every recruitment contact anyway, from the first outreach through execution. It tells you who is still worth calling, and it gives you a dated disposition for each provider in range if the gap turns out to be a real supply problem. Reconstructing outreach that really happened is legitimate; invented records are not.
Mistake 2: Counting Providers Who Aren't Ready
CMS's guidance says plans list providers with a fully executed contract on their HSD tables. Letters of intent work only for applicants during the application, and they end when the contract year starts. So check every provider you add in response to a notice: is the contract actually executed, and is the address the office where they see patients?
Then check credentialing. In most plans a provider isn't loaded as participating until the credentialing committee approves the file, so a provider signed in response to the notice may be on the table long before members can see them. There is no reliable national average for how long that takes; see how long provider credentialing takes.
Run two tracks: what you can fix in this upload, and what is in your pipeline and when it will be ready. Don't blur them when you report to leadership.
Mistake 3: Filing an Exception That Is Really a Rate Dispute
When you cannot close a rural or specialty gap in time, an exception is the obvious thing to reach for. But under 422.116(f), it needs proof of two things: the providers you would need are not available, and the ones you contracted with are available and accessible to most enrollees, consistent with the local pattern of care.
MedPAC reports that CMS denied 259 of 448 exception requests in 2021, and that the most common reason was providers within the criteria that the plan "failed to include." So a strong request includes:
- Every provider inside the standard, from the Provider Supply file and your own checks, with a disposition for each
- Dated proof for each provider marked not available: a license lookup, an OIG exclusion search, a Medicare opt-out check
- Claims or a detailed explanation showing the local pattern of care
- A comparison of the closer non-contracted providers against the farther contracted ones
If the honest reason a provider isn't in network is the rate, you don't have an exception. We walk through the rest in how to request a CMS network adequacy exception.
Mistake 4: Missing the Deadline
Treat the response date as hard. For applicants, the response to a Notice of Intent to Deny is due within 10 days and is the final upload opportunity. Plans can miss dates for avoidable reasons: the notice went to the wrong internal inbox, or legal review took longer than expected.
Build a response process that accounts for this. The notice should go to your network director, compliance lead, and legal counsel on day one. Set an internal due date well ahead of the real one, with time for review and for problems with the upload itself.
If you see a problem coming, talk to your CMS Account Manager before the deadline, not after.
Mistake 5: Treating the Notice as a One-Time Event
The worst outcome of a deficiency notice is resolving it and then returning to the exact processes that created it. The gap that triggered the notice was a symptom of a monitoring process that failed to catch what CMS caught.
After every deficiency notice response, run a process review: Why did we miss this gap? What would have caught it earlier? Is our monitoring cadence aligned with CMS's review cycle? Are we testing against the current HSD Reference File, or running quarterly snapshots against an outdated roster?
A deficiency notice is not a failure of the compliance team. It is a signal that the plan's network monitoring is operating behind the regulatory clock. Closing that gap, between when the problem develops and when you see it, is the only durable fix. Everything else is crisis management.
The Blueprint team
Provider network build practice
Written by the people behind Blueprint, who between them have spent 30 years building provider networks for health plans: recruiting and contracting providers, chasing credentialing, and filing adequacy. Blueprint is new. The experience behind it isn't.