Building Networks for MA Supplemental Benefits

What is a supplemental benefit network, and why is it now the hard part?

Original Medicare does not cover routine dental, vision, or hearing care, so these have become the table-stakes supplemental benefits of Medicare Advantage. More than 97 percent of available MA plans offer dental, vision, and hearing, which means these benefits no longer differentiate a plan on paper. What differentiates it is delivery: whether a member in a rural county can find a participating dentist within a reasonable drive, whether the vision vendor's directory is accurate, whether the hearing benefit covers a device the member can actually obtain.

That delivery runs on a network you often do not build the way you build your medical network. Dental, vision, and hearing are typically administered through third-party benefit managers who bring their own contracted panels. Meals, transportation, and in-home support run through specialized vendors. SSBCI benefits can involve community-based organizations that have never contracted with a health plan before. The result is a patchwork of vendor networks, each with its own directory, credentialing posture, and data feed, sitting outside the CMS time-and-distance framework that governs your medical network.

CMS does not apply the 42 CFR 422.116 adequacy standards to most supplemental benefits the way it does to primary care or cardiology. But the absence of a mechanical test does not mean the absence of accountability. The agency has signaled, through the bid review process and new disclosure rules, that it expects the advertised benefit and the accessible benefit to match. When they do not, the exposure is a marketing complaint, a bid challenge, or a Stars hit on the member-experience measures that increasingly drive the overall rating. Treating supplemental networks as an afterthought is how plans end up with a ghost network in their most member-visible benefits.

How did the rules change? From generous rebates to bid-to-benefit scrutiny

The strategic backdrop is a squeeze. Rebate dollars grew for years, and plans loaded up on supplemental benefits to compete. MedPAC's June 2025 analysis broke down where the roughly 86 billion dollars in rebates go: about 39 billion toward additional non-Medicare benefits, 27 billion toward reducing cost-sharing on Medicare services, 15 billion toward enhanced Part D drug benefits, and 5 billion toward reducing Part B premiums. The Commission's core critique was transparency -- CMS and the public have limited visibility into whether the benefits are being used at all.

That critique is turning into oversight. CMS reviews plan bids against Total Beneficiary Cost thresholds and scrutinizes larger year-over-year changes case by case, asking organizations to justify or revise bids that move too far, too fast. Informally, the industry calls this bid-to-benefit discipline: the expectation that the value a plan books in its bid corresponds to value members actually receive. When a plan advertises a rich benefit that data shows almost no one uses, that is not a bargain for the Trust Fund -- it is a signal that the benefit was designed to win the shopping comparison, not to be delivered.

For 2026, the practical consequence is that plans are paring back. The landscape has shifted from more-is-better to a smaller number of benefits a plan can actually stand behind. That shift raises the stakes on the ones you keep. If you are going to carry fewer supplemental benefits, each one has to work, which means the network behind it has to be real, accessible, and measurable. This is the same discipline we describe in build vs outsource: the decision is not only who administers the benefit, but who is accountable for its delivery.

What does the 2026 mid-year notification rule require?

The Contract Year 2025 final rule (CMS-4205-F) created a new obligation that changes how you must manage supplemental benefit networks. Beginning January 1, 2026, MA organizations must send each enrollee a personalized mid-year notification of the supplemental benefits they have not used. The notice must go out no sooner than June 30 and no later than July 31 each year, and it must list the unused benefits, the scope and cost-sharing of each, any eligibility limits, clear instructions on how to access them, relevant provider and network details, and a toll-free customer service number.

Read that requirement as a network stress test with a statutory deadline. You cannot tell a member how to access an unused dental benefit if your dental directory is wrong. You cannot instruct someone to schedule transportation if the vendor's booking process is broken. The mid-year notice forces the plan to confront, in writing and at scale, whether every advertised benefit has a working path to use. Plans that treated supplemental directories as low-priority now have a compliance reason to fix them, and a July deadline to do it by.

There is also a Stars and retention dimension. Utilization gaps are not neutral. Survey evidence shows roughly nine in ten enrollees consider supplemental benefits important, but only about seven in ten report using them, a gap driven by cost-sharing, awareness, and access friction. The mid-year notice is CMS forcing plans to close that awareness gap -- but a notice only helps if the underlying network delivers. Accurate provider data is not optional here; it is the mechanism, a theme we cover in directory accuracy isn't optional and provider data operations.

SSBCI: what is the evidence bar, and how does it shape network design?

Special Supplemental Benefits for the Chronically Ill let plans offer non-primarily-health-related benefits -- food, pest control, home modifications, and similar -- to enrollees with qualifying chronic conditions. SSBCI is the most flexible and the most scrutinized category. The CY2025 final rule requires that for each SSBCI item or service, the plan maintain an evidence-based bibliography of high-quality clinical literature demonstrating a reasonable expectation that the benefit will improve or maintain the health of chronically ill enrollees, with supporting evidence published within ten years of the coverage year. Plans must also apply written, objective, non-discriminatory eligibility criteria and document enrollees found ineligible.

This evidence bar reshapes network strategy in two ways. First, it forces plans to narrow SSBCI to benefits they can defend, which is why SSBCI participation has been declining and plans have adopted a more-targeted, fewer-benefits posture. Second, it pushes the delivery network toward organizations that can document what they did for whom -- because an evidence bibliography is only credible if the benefit is actually delivered and captured. A food-as-medicine benefit backed by clinical literature still fails if the community vendor cannot report deliveries against eligible members.

The practical build implication is that SSBCI vendor selection is now a due-diligence exercise, not a procurement exercise. You are choosing partners who can meet eligibility documentation requirements, feed utilization data, and survive an annual compliance review. Many strong community-based organizations have never been credentialed or contracted by a payer. Bringing them into a payable, reportable relationship is real work -- closer to a network build than a vendor contract -- and it overlaps with the value-based network requirements plans already navigate for medical care.

Building the vendor network: dental, vision, and hearing

For the table-stakes benefits, the strategic question is depth and accuracy, not existence. Because nearly every plan offers dental, vision, and hearing, the differentiator is whether your administrator's panel is genuinely accessible in every county you serve, including the rural and access-challenged ones where a national panel thins out. Before you sign a benefit manager, test their network the way CMS tests yours: pull their contracted panel against your enrollment geography and look for the counties where the nearest participating provider is an unreasonable drive. Those are your future member complaints.

The second question is directory integrity. A dental or vision directory that lists providers who no longer participate, no longer practice, or never accepted the plan is the supplemental-benefit version of a phantom network. Because these directories are usually maintained by the vendor, the plan's accountability can get blurry -- but the member complaint and the compliance exposure land on the plan. Contractually, you want directory accuracy standards, refresh cadence, and audit rights written into the administrator agreement, not assumed. The discipline mirrors what we describe for medical directories, and the No Surprises Act and adequacy has already made directory accuracy a legal expectation rather than a nicety.

Third, align the benefit design with the network's real economics. A rich hearing benefit that only covers devices the network cannot supply at the covered price will show low utilization and high frustration. The fee schedule and device coverage have to match what the panel will actually deliver -- the same alignment problem we cover in fee schedule benchmarking. Design the benefit around the network you have, or build the network the benefit needs; do not advertise a benefit the network cannot honor.

Managing vendor relationships and utilization data

Once the network exists, the work becomes ongoing management, and the central artifact is data. MedPAC's transparency critique is, at bottom, a data critique: CMS cannot see supplemental benefit utilization clearly because the encounter data is thin. That gap is closing. Plans that cannot measure which members used which benefit, through which vendor, at what cost, are exposed on two fronts -- they cannot answer CMS, and they cannot send an accurate mid-year notification of unused benefits. Utilization data is now infrastructure, not reporting.

Build vendor relationships around data feeds from day one. Every administrator and vendor agreement should specify what utilization data flows back to the plan, in what format, on what cadence, and with what member-level detail. This is not a nicety you add later; it is the mechanism that lets you produce the June-30-to-July-31 notice, feed your Stars analytics, and defend your SSBCI benefits at annual review. When a vendor cannot or will not report at the member level, treat that as a disqualifying finding, the same way you would treat a medical provider who refuses to submit encounters.

Relationship management also means governance cadence. Supplemental vendors need the same operating rhythm you apply to delegated medical partners: regular performance reviews, directory audits, complaint tracking, and remediation timelines. If you delegate credentialing or network functions to an administrator, hold them to standards you can audit, as we describe in delegated credentialing. A supplemental network is not a set-and-forget purchase; it is a living network subject to attrition, the same living target your medical network is.

The VBID sunset: what moves into SSBCI?

One more structural change reshapes 2026 strategy. CMS announced in December 2024 that it will terminate the Medicare Advantage Value-Based Insurance Design (VBID) model after calendar year 2025, citing substantial and unmitigable costs to the Medicare Trust Funds -- an estimated 2.3 billion dollars in excess costs in 2021 and 2.2 billion in 2022. VBID had been a common vehicle for cost-sharing reductions and social-determinant benefits, especially in dual-eligible plans, and its sunset removes that vehicle beginning in 2026.

CMS's own guidance is that many of VBID's most-used interventions remain available across the MA program, including through the SSBCI pathway. In practice, that means benefits that lived under VBID's flexible authority now have to fit inside the standard supplemental-benefit and SSBCI rules -- with the evidence bibliography, eligibility documentation, and utilization reporting those rules require. Benefits that were easy to offer under a demonstration model now carry a heavier compliance load.

For plan strategy, the VBID sunset means re-homing benefits, not simply cutting them. Any plan that leaned on VBID for its dual-eligible value proposition needs to map each affected benefit to a compliant 2026 pathway and confirm the delivery network survives the move. This is especially pointed for D-SNPs, where supplemental benefits are central to the model and where the integration work we describe in D-SNP integration and D-SNP network requirements already demands a coordinated network.

A KSM playbook for supplemental benefit networks

The plans that will win the supplemental-benefit era are the ones that treat these networks with the same rigor they apply to medical adequacy: build deliberately, contract for data and accuracy, and manage the network as a living asset. You are the one accountable for closing the gap between the benefit on the bid and the benefit in the member's hand, and the work is concrete. The steps below are how we sequence a supplemental network build or repair.

None of this is beyond a capable plan team, but it rewards a guide who has run it before -- especially when a mid-year notification deadline or a bid challenge is bearing down. If you are re-homing VBID benefits, tightening SSBCI, or fixing a supplemental directory that is generating complaints, talk to our team and see how we would sequence it. And if the harder problem is your core medical network, start with our services and the build-versus-repair diagnostic behind them.

• Map every advertised supplemental benefit to its delivery network, county by county, and flag the geographies where access thins out
• Test each administrator's panel against your enrollment before you sign, the way CMS tests time and distance
• Write directory accuracy standards, refresh cadence, and audit rights into every vendor and administrator agreement
• Require member-level utilization data feeds from every vendor as a condition of contract, not an afterthought
• Build the June-30-to-July-31 mid-year notification process on top of clean directories and working access paths
• Maintain an SSBCI evidence bibliography and eligibility documentation that can survive annual CMS review
• Re-home VBID-era benefits into compliant SSBCI or supplemental pathways and confirm the network survives the move
• Govern supplemental vendors on a fixed cadence: performance reviews, directory audits, and complaint remediation