Free Network Build Assessment
Score your buildPassing a CMS network review starts a compliance obligation; it doesn't end one. Here's how to build a monitoring cadence, what to track, and what to do when a network change opens a gap.
Many network operations teams treat a passed CMS network review as the finish line: a milestone to clear and then move on from. CMS takes the opposite view. Under its December 2024 network adequacy guidance, CMS reviews contract networks on a triennial basis, and the MA application's attestation asks for a network that meets 42 CFR 422.116 for each county during the entire contract year. A network that was adequate in January may not be adequate in September if providers terminate, panels close, or practice locations change.
Several events can pull a CMS review forward between triennial cycles: a termination CMS considers significant, a network access complaint, and a gap the plan discloses itself, which plans must report to their CMS Account Manager. The same guidance says operating contracts that fail may face compliance or enforcement actions. A plan that isn't watching its own network finds out about these gaps last.
Post-submission monitoring also serves a practical operational function independent of regulatory compliance. Networks are dynamic systems. Providers retire, relocate, sell practices to health systems, or simply stop accepting new patients. Without a systematic monitoring program, plans often discover adequacy problems only when members file grievances or CMS flags an issue in an audit: at which point the remediation timeline is compressed and the options are limited. A well-designed monitoring program gives network operations teams advance warning of emerging gaps while there is still time to recruit and credential replacement providers before a deficiency materializes.
We don't know of a single CMS list of required post-submission monitoring metrics, so treat what follows as a working list rather than a regulatory one. Start with what CMS itself scores: for each county and each provider or facility type, the minimum provider count and the share of beneficiaries within the time and distance standard. Then track what those two tests don't show, starting with how many contracted providers are actually accepting new patients.
Appointment wait times are the second major category. Since the CY2024 rule, 42 CFR 422.112(a)(6)(i) sets wait-time standards for primary care and behavioral health: urgently needed or emergency services immediately, services that need medical attention but are not urgent within 7 business days, and routine and preventive care within 30 business days. Plans can collect availability data through member surveys, provider responses, and direct calls to contracted practices. A county whose PCP practices can't offer new patients an appointment inside those windows has an access problem even if the time and distance math passes.
Panel status monitoring is the third critical dimension. A provider who is contracted but has closed their panel to new patients is not an option for a member who needs a new doctor. Plans should track open versus closed panel status at the provider level, updated on a regular schedule, and keep it in view alongside the adequacy numbers. This is particularly important in tight markets where a few providers serve a large enrolled population: panel closure by even one or two high-volume PCPs can change what access really looks like.
We can't point to a CMS rule that sets up a formal "network adequacy amendment" filing, so don't plan around one. What the sources do say is more specific. A gap the plan discloses itself must be reported to its CMS Account Manager. For terminations a plan considers significant, Chapter 4 of the Medicare Managed Care Manual asks for notice to the Account Manager at least 90 days before the effective date, and a significant termination can trigger a network review. Separately, 42 CFR 422.111(e) requires enrollee notice 45 calendar days ahead for primary care and behavioral health providers, and 30 days for other specialties.
Provider terminations, practice closures, and acquisitions that move providers to a health system outside the network are the obvious events to watch. Plans should define what counts as a network-threatening event ahead of time: the loss of a provider that drops any county and specialty below the CMS standard, or the loss of a provider that a county depends on. The second definition is often more useful because it catches fragility before it becomes a deficiency.
CMS may also learn about a problem from outside your monitoring program, since a network access complaint is one of the events that can pull a review forward. Dated monitoring records won't fix the gap, but they let you show when you found it and what you did about it.
A structured monthly monitoring cadence is the operational backbone of a compliant post-submission program. The cadence should be anchored to three primary activities: data refresh, adequacy scoring, and exception review. Data refresh involves pulling updated provider status from the credentialing system of record, reconciling against the directory, and flagging any providers whose status has changed since the prior month. Adequacy scoring involves re-running the county-specialty adequacy calculation against the refreshed provider data to identify any county-specialty combinations that have dropped below threshold or that are approaching the threshold within a defined margin. Exception review involves a structured discussion of flagged counties with network development and credentialing leadership to determine whether remediation is needed and what form it should take.
Monthly cadence should be supplemented with event-triggered monitoring for high-impact changes. When a large multi-site practice group terminates, when a hospital system exits the network, or when CMS publishes a new or updated HSD Reference File, those events warrant an immediate out-of-cycle assessment rather than waiting for the next monthly review. Plans should have a documented escalation protocol that defines what categories of events require immediate assessment, who is responsible for initiating it, and how the team decides whether CMS has to be told.
The output of the monthly monitoring process should be a short written adequacy status report that is retained as a compliance record. It should capture the date of the review, the data source and pull date, the county-specialty combinations reviewed, the results of the adequacy scoring, any exceptions identified, and the disposition of those exceptions. That gives you a dated record to show if CMS asks how you monitor your network.
Software offers real advantages in speed, consistency, and scale. Running the county and specialty calculation by software rather than by hand means it can run more often, which lowers the risk that a developing problem goes unnoticed until it has become a deficiency. For plans with large service areas, particularly those operating across multiple states, manual review struggles to be both comprehensive and timely.
Manual monitoring processes remain viable for smaller plans or for the exception investigation and remediation phases of the workflow, where human judgment is genuinely required. A credentialing analyst reviewing a flagged county needs to assess not just whether the mathematics show a deficiency, but whether the situation is likely to self-correct (a provider on temporary leave returning shortly), whether there are compensating factors (a new provider in the credentialing pipeline expected to clear soon), or whether CMS needs to hear about it. These assessments require contextual knowledge that software cannot fully replicate.
A practical model for most plans is a hybrid: software for the scoring, people for exception investigation and disposition. The software handles volume and consistency; people handle judgment and context. Plans evaluating monitoring tools should ask how data gets in, how closely the scoring follows CMS's method (CMS places members using a sample census plans can't see, so no internal tool reproduces its result exactly), and what the output looks like for the people deciding what to do next.
CMS's network review itself scores the HSD tables you upload to the Network Management Module, using its Automated Criteria Check. We can't cite a public CMS protocol listing what it asks for about monitoring, so prepare for the obvious questions: when did you learn of this gap, what did you do, and can you show it? The answers live in your monitoring reports, the underlying data, and your records of exceptions and dispositions. A written policy with no outputs behind it answers none of them.
Watch the lag between a provider status change and the records that depend on it. If a provider terminates on March 1 and your monitoring doesn't show it until mid-April, your adequacy view was wrong for six weeks. The directory rules set a useful outer limit: 42 CFR 422.111(m) requires updates within 30 days of learning of a change, and the Provider Directory API under 42 CFR 422.120 must be updated no later than 30 calendar days after the plan receives new information.
Plans can also see CMS's answer early. Any organization with a contract ID can upload HSD tables to the Network Management Module at any time to test compliance, and CMS offers an informal Consultation upload before the formal triennial review. Pair that with a self-assessment: pull your recent monitoring reports, check that they are complete and consistent, review exception dispositions, and confirm the reports match your contract and credentialing records for the same dates. Gaps you find yourself can be fixed on your own schedule.
Blueprint scores adequacy by county and specialty against the CMS 2026 HSD standards on straight-line distance, shows which providers a county depends on, and ranks who would close a gap; a straight-line pass shows as unconfirmed because drive time is not measured. Reports, dashboards and scheduled digests keep the team current, but your team loads the data, and CMS's own check in HPMS remains the test.
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.