Free Network Build Assessment
Score your buildA CMS deficiency notice isn't a denial, it's a request for corrective action. Here's how to respond effectively, what documentation CMS expects, and how to avoid repeat deficiencies.
A network adequacy deficiency notice (sometimes called a compliance deficiency or corrective action requirement) is a formal communication from CMS indicating that your Medicare Advantage plan's submitted network does not meet one or more time-and-distance thresholds in your approved service area, or that your submission contained errors that prevent CMS from completing its adequacy review.
A deficiency notice is not an automatic plan termination or loss of approval. It is a structured opportunity for the plan to address identified gaps within the timeframe set in the notice. For applicants, it is the second of three HSD upload rounds. The last is the response to the Notice of Intent to Deny, with 10 days to respond under 42 CFR 422.502(c)(2)(ii).
Network adequacy deficiencies generally fall into four categories:
An effective deficiency response follows a structured sequence:
Review the deficiency notice line by line and classify each cited gap as: (a) a data error that can be corrected with supporting documentation, (b) a real gap that requires provider recruitment, or (c) a true supply shortage that may support an exception request. The classification determines the response strategy for each item.
Data errors are the fastest to resolve. If a provider was listed at an incorrect address, or a provider who should have been included was omitted, document the correction with supporting contracts and directory data, and correct the HSD tables.
For real gaps, add any provider whose contract is signed. Applicants may use letters of intent signed by both parties under 42 CFR 422.116(d)(7), marked in the LOI column of the HSD table. Operating contracts need fully executed agreements. Don't count a negotiation as a contract.
Where the needed providers truly aren't available, file an exception request under 42 CFR 422.116(f) with a complete provider census, a checkable reason for each provider not in network, and evidence of the local pattern of care. Inability to contract is not a valid reason under CMS's guidance.
If CMS asks for corrective action, be specific about which deficiencies have been resolved, which are in process, the timeline for the rest, and how the plan will monitor its network going forward.
Don't miss it. For an applicant, the stakes are the county: MedPAC's June 2024 report says CMS has never imposed intermediate sanctions or civil money penalties for network adequacy noncompliance, but that new applications have been denied on this basis. Operating contracts that fail a review may face compliance or enforcement action.
Prevention requires year-round monitoring, not just pre-submission review, of county-specialty adequacy status. In Blueprint, a team can score its network by county and specialty against CMS's standards at any time, see which providers a county depends on, and get a ranked list of who would close a gap.
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.