The Margin for Error on Networks Is Small
Medicare Advantage plans leave markets for many reasons, and the network is rarely the only one. But a network gap can stop a new county outright, and the rules around networks and directories keep getting more specific.
The baseline is public. Under CMS's December 2024 network adequacy guidance, operating contracts are reviewed on a triennial basis, and an application, a significant termination, a network access complaint or a gap the plan discloses can pull that review forward. Applicants may be denied, and operating contracts that fail may face compliance or enforcement actions. The organizations that do well will be the ones that treat network as a strategic asset, not a compliance artifact.
What the Enforcement Record Actually Shows
For network adequacy, the sharpest consequence is a denied application: MedPAC's June 2024 report says CMS has never imposed intermediate sanctions or civil money penalties for network adequacy noncompliance, but new applications have been denied on that basis. And since contract year 2024, applicants have had to show compliance inside the application itself. A "we'll fix it before the review" plan has little room: the final upload is the response to the Notice of Intent to Deny, and the regulation gives 10 days.
Three areas deserve the most attention in 2026:
- Appointment wait times: Since the CY2024 rule, 42 CFR 422.112(a)(6)(i) sets standards for primary care and behavioral health: 7 business days for care that needs attention but isn't urgent, and 30 business days for routine and preventive care. The automated criteria check doesn't test them, so an HSD table can pass while members wait.
- Provider directory accuracy: Under 42 CFR 422.111(m), for plan years beginning on or after January 1, 2026, plans make directory data available to CMS for publication, update it within 30 days of learning of a change, and attest at least annually that it is accurate. From plan year 2028, the REAL Health Providers Act adds 90-day verification and an accuracy score. See ghost networks and directory compliance.
- D-SNP access: Ask whether a D-SNP network actually includes the behavioral health and long-term services and supports (LTSS) providers the population needs, not just the ones that look good on paper.
D-SNP Expansion Is Easy to Underestimate
D-SNPs draw a lot of attention as a growth path, and the work is easy to underestimate. A D-SNP must have a contract with the state Medicaid agency under 42 CFR 422.107, and that contract has to address how Medicaid benefits are coordinated and how information on Medicaid provider participation is shared. Find that work before you commit to the expansion, not after.
The population is different, too. A network built for a general MA population and then given a D-SNP product can pass the county tests and still not serve dual-eligible members well.
Build the network first, then launch the product. The reverse order means finding out afterward that you needed a different network.
The Directory Is Now Part of the Competition
Hospital affiliation has long been what brokers and members ask about first, and it still matters. But a telehealth contract with no real capacity, or a behavioral health listing with a closed panel, doesn't help a member trying to get care.
The directory also sits in plainer view now. Under the 422.111(m) rule, directory data goes to CMS for Medicare Plan Finder, so a member choosing a plan can see your listings next to a competitor's. A "good enough" network looks different once people can compare.
What Network Leaders Should Be Doing Right Now
A few deliberate moves today will put you in a stronger position a year from now:
- Audit your documentation, not just your network. Can you show when each listing was last verified and how you monitor appointment access, or are you still relying on annual surveys?
- Map your D-SNP exposure early. If you have D-SNP products or are planning them, read the state Medicaid agency contract and the state's own network standards, and check your network against those as well as the CMS standards.
- Treat Rural and CEAC counties as a strategy problem, not a credentialing problem. Use telehealth deliberately, within the limits of CMS's 10 point telehealth credit, not as a substitute for physical coverage.
- Build the business case for network investment at the executive level. CFOs need to see what a denied county or a compliance action would cost, next to what proactive investment costs. Make that math visible before a review forces the conversation.
Network leaders who wait for the compliance team to flag problems before acting are operating on the wrong timeline. Plans that see network as infrastructure for growth have more options when the review comes.
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.