D-SNP Alignment 2027: What Changes for Agents

Beginning in 2027, a federal regulation most agents have never had a reason to open, 42 CFR 422.514(h), starts restricting how many D-SNPs a Medicare Advantage organization can offer in a service area it shares with its own affiliated Medicaid plan, and who can newly enroll in the ones that remain. If any part of your book is dual-eligible clients, this is the rule that decides whether the D-SNP you enrolled someone in last AEP is still one your carrier can keep selling to new members two AEPs from now. It doesn’t touch Medicare Supplement or ACA business at all, and it doesn’t disenroll anyone automatically in 2027 — but it changes what “the right D-SNP” means for a client, and it does it on a clock that’s already running.

The pain: a plan you sold in good faith might not survive its own carrier’s restructuring

Here’s the actual situation. You have dual-eligible clients on your book. Some are in a D-SNP tied to the same parent company as their state Medicaid managed care plan. Some are in a D-SNP that has nothing to do with their Medicaid MCO — maybe it had better supplemental benefits, maybe it was what was available when you enrolled them, maybe their Medicaid MCO changed since. You’ve never had a reason to sort your book by that distinction, because until now, nothing forced the question.

That changes with 42 CFR 422.514(h). It doesn’t ask whether the D-SNP is a good plan. It asks whether the D-SNP’s enrollment is aligned with the client’s Medicaid coverage, and starting in 2027, an MA organization that also runs the client’s Medicaid MCO in that service area generally can’t keep selling a second, non-aligned D-SNP option there, and can’t add new non-aligned members to the ones it keeps. You didn’t do anything wrong by enrolling a client in a non-aligned plan before this rule mattered. But if you don’t know which of your clients that describes, you’re going to find out from a plan termination notice instead of from your own book review, and that’s a worse way to have the conversation with a client who trusted you to see it coming.

Why it’s happening: CMS is trying to stop duals from being spread across plans that don’t talk to Medicaid

CMS didn’t write this rule to make your job harder. Its own fact sheet for the Contract Year 2025 Medicare Advantage and Part D final rule (CMS-4205-F), which is where these provisions originate, frames the goal directly: “increasing the percentage of dually eligible Medicare Advantage enrollees who are in affiliated Medicaid managed care plans, as opposed to Medicare Advantage plans that differ from the enrollee’s Medicaid plan,” in order to expand access to integrated materials, unified appeal processes across Medicare and Medicaid, and continued Medicare services during an appeal (CMS, CY2025 Final Rule Fact Sheet, Apr. 4, 2024).

The mechanism is enrollment restriction, not benefit design. CMS isn’t telling carriers what a D-SNP has to cover differently. It’s telling MA organizations that share a parent company with a Medicaid MCO that they can’t keep running parallel D-SNPs in the same territory that don’t feed into that same Medicaid relationship — because every non-aligned D-SNP is a place a dual-eligible member’s Medicare and Medicaid benefits can end up managed by two organizations that don’t coordinate, which is the exact fragmentation CMS has been trying to reduce since D-SNPs were permanently authorized under the Bipartisan Budget Act of 2018.

Source: KFF, 10 Things to Know About Medicare Advantage D-SNPs, Feb. 9, 2024 (2023 enrollment data). Note: this integration-type breakdown is a different classification from the aligned/non-aligned enrollment status this article is about — a coordination-only plan can be either aligned or non-aligned, and KFF doesn't publish a single national figure for how many current enrollees sit in a non-aligned plan specifically, which is exactly why this has to be checked plan by plan.

The compliance timeline, in the order it actually bites

Four separate dates matter here, and they come from two different rulemakings, which is part of why this gets confusing if you only skim a headline.

The look-alike threshold and the 422.514(h) alignment rule are two different enforcement levers aimed at the same underlying problem: Medicare Advantage plans that carry a lot of dual-eligible members without actually functioning as a properly integrated D-SNP. The threshold drop is already in force, tightening every year since 2025. The alignment rule is the one with the harder deadline still ahead of you.

What it costs if you miss this

The direct cost isn’t a fine against you personally — this is a carrier-level contracting rule, not an agent conduct rule. The cost is downstream and it’s about your book’s stability and your credibility with clients.

Picture a straightforward version of the exposure. Say your upline’s MA organization also runs the Medicaid MCO in your state, and today it offers three D-SNP benefit packages in your county: one built around a large hospital network, one with a richer OTC card, and one that’s the historically aligned option. Under 422.514(h)(1), beginning in 2027, that organization can generally keep only one of those three open to new full-benefit dual enrollment in that county (absent one of the (h)(3) exceptions). If you’ve been steering clients toward the richer-OTC-card option because it converts better in a sales conversation, and that’s not the one that survives as the surviving aligned plan, every client you put there is now sitting in a plan that can’t take new same-type enrollment going forward — and by 2030, under (h)(2), a non-aligned enrollee in that specific plan type isn’t guaranteed continuing coverage in it either.

That’s not a hypothetical fine. It’s a service problem that lands on your desk as a stack of plan-change conversations you didn’t schedule, at a time CMS didn’t choose around your calendar. The agents who avoid that are the ones who know today which of their dual-eligible clients sit in a non-aligned plan, so the move happens as a proactive re-shop conversation on their own timeline, inside a normal SEP window, instead of a reactive scramble after a termination notice.

How to check your book by hand — the free method, no tool required

This is the part we’re not gating behind anything. Here’s the actual process.

Where Ambrose’s medicare-watchdog spoke actually helps, and where it doesn’t yet

Ambrose OS, the platform included with a Tech Savvy membership, ships a spoke documented as medicare-watchdog: “Scheduled MAPD/PDP/Med Supp intelligence,” using federal data only, with no client identifiers crossing the wire, and cross-referencing your vault book against CMS data internally (Ambrose docs, medicare-watchdog). Its documented tools are medicare_scan_book (scans your book for risk signals — cost increases, plan discontinuations, network changes, Star Rating changes, and rate filings), medicare_check_plan, medicare_star_diff, and medicare_rate_filing.

Here’s the honest boundary. If a client’s non-aligned D-SNP gets discontinued or restructured as a downstream effect of 422.514(h), medicare_scan_book would very likely surface that the same way it surfaces any plan discontinuation or rate filing change — that’s squarely inside what it’s documented to do. What it is not documented to do, as of this article, is flag a client’s D-SNP as “aligned” or “non-aligned” today, before a discontinuation happens. That specific cross-check, plan parent organization against Medicaid MCO enrollment, is the six-step manual process above, and it stays manual until (if) that capability shows up in the docs. We’re not going to describe a feature that isn’t there just because it would make a better pitch.

Everything above works whether you ever join anything or not. If you’d rather run this book review with Ambrose’s medicare-watchdog already scanning for the discontinuations and rate changes while you handle the alignment cross-check by hand, that’s exactly the kind of thing we work through on a Tuesday call, with the screen open, no downline pitch attached.

What you get

A Tech Savvy Insurance membership is $97 a month, billed monthly, cancel anytime, with the founding rate locked in while the membership stays active. It includes one Ambrose AI seat (the platform above — Ambrose usage itself runs on its own credit system, separate from the membership fee), weekly Zoom calls with open Q&A and build-with-you sessions, 30+ hours of recorded training on AI, Meta Ads, and marketing/sales, pre-built AI templates and bot deployments, and a free annual in-person member workshop. It’s also an explicit no-recruiting zone — you can ask a real question about your book without getting DM’d about a downline. Join here: https://buy.stripe.com/8x2cN63OE6dO2yCdv2g3600.

The compliance layer this sits inside

Everything above is regulatory information about plan structure, not marketing copy aimed at a beneficiary — but two frameworks still apply to how you use it. If a conversation with a client touches specific plan benefits, premiums, or a recommendation to switch, CMS’s Medicare Communications and Marketing Guidelines still require the standard TPMO disclosure that you don’t represent every plan available in the service area, delivered before the marketing portion of the conversation, alongside the usual Scope of Appointment and call-recording obligations. Nothing in 422.514(h) changes those requirements.

Separately, if you use any AI tool, including Ambrose, to help research a regulation like this one or draft a client explanation, the NAIC’s Model Bulletin on the Use of Artificial Intelligence Systems by Insurers, adopted December 4, 2023, sets the expectation that insurers and the producers acting for them maintain a written approach to AI use, keep a human reviewing what it produces before it reaches a consumer, document the process, and hold any vendor accountable for what its tool outputs (NAIC, Model Bulletin, Dec. 4, 2023). Treat everything in this article, including the regulatory citations, as a starting point you verify against the current eCFR and CMS documents before repeating a specific figure to a client — regulations get amended, and the eCFR text quoted here reflects what was live on the date this article was researched.

What about the rest of your book

This rule is specific to D-SNPs. If a client is on a standard Medicare Advantage plan with no D-SNP designation, 422.514(h) doesn’t apply to them regardless of dual-eligible status, because the restriction is about D-SNP enrollment specifically, not about dual eligibility generally. Medicare Supplement clients are entirely outside this rule — Medigap isn’t Medicare Advantage, and CMS’s MA enrollment regulations don’t reach it. If you also write ACA marketplace business, that market runs under its own separate CMS rulemaking and isn’t touched by this regulation either. The only clients this affects are full-benefit dual eligible individuals currently enrolled, or being considered for enrollment, in a D-SNP whose parent organization also runs an affiliated Medicaid MCO in the same service area.

The close

Nothing above requires a membership to act on. Pull your dual-eligible list, make the calls, check CMS’s own published lists, and you’ll know exactly where you stand before AEP conversations start. If you’d rather have Ambrose’s medicare-watchdog already watching your book for the discontinuations and rate changes this rule will eventually cause, with people on a call helping you build the workflow instead of guessing at it alone, one Ambrose seat comes with a Tech Savvy Insurance membership: $97 a month, cancel anytime, no downline pitch: https://techsavvyinsurance.com/.