D-SNP Compliance Now Runs on Two Regulatory Calendars
Medicare and Medicaid integration requirements are converging on a three-wave compliance timeline. The C-SNP enrollment surge tells you how many plans already decided not to deal with it.
In This Edition
One Regulatory Calendar Is No Longer Enough
For most Medicare Advantage plans, compliance means one regulatory calendar — CMS, the program audit schedule, the annual rule cycle. For plans operating dual eligible special needs plans, it means two.
Dual eligible special needs plans (D-SNPs) are Medicare Advantage products limited to individuals enrolled in both Medicare and Medicaid. These are among the most clinically complex beneficiaries in the Medicare population: higher rates of chronic conditions, lower incomes, and higher reliance on both programs simultaneously.
That complexity is why the integration requirements exist. It is also why compliance with those requirements is operationally difficult in ways that a single-program compliance framework cannot fully address.
By the Numbers
82%of all SNP enrollees are in D-SNPs — plans for individuals enrolled in both Medicare and Medicaid.
Coverage Area
D-SNPs have never previously appeared as a standalone topic in PCOOB Weekly. This is a persistent gap now addressed.
Three Waves. Three Regulatory Sources.
The near-term compliance calendar for D-SNP operators does not run on one clock. It runs on three — and two of those deadlines arrive before the end of 2026.
SMAC Submissions Due
State Medicaid Agency Contract submissions for contract year 2027 must be filed. Each state has its own agency, its own integration requirements layered above federal minimums, and its own review timeline. Multi-state D-SNP operators are managing multiple submissions, not one.
Integrated ID Card + HRA
Two requirements activate simultaneously: integrated member ID cards (serving both Medicare and Medicaid enrollment) and integrated health risk assessments combining Medicare and Medicaid dimensions into a single unified assessment. HRA requirement applies for January 2027 effective dates — the operational infrastructure must be ready before the enrollment period.
Enrollment Restrictions
Section 422.514(h) creates escalating enrollment restrictions for D-SNPs affiliated with Medicaid MCOs. Beginning 2027, enrollment restricted to individuals in the affiliated Medicaid plan. By 2030, FIDE SNPs must maintain exclusively aligned enrollment — one shared enrollee base across both programs.
These are not marginal adjustments to an existing compliance framework. They require health plans to coordinate across organizational structures — often separate Medicare and Medicaid lines of business — that were built to operate independently.
The plans best positioned to meet this timeline are not those with the most robust Medicare compliance programs. They are the ones that have built governance structures designed to operate across both programs simultaneously.
$ trace --plan D-SNP --horizon 2030 [CMS Medicare] Annual rule cycle [State Medicaid] SMAC contract requirements [Federal] §422.514(h) enrollment restriction [Federal] FIDE/HIDE integration mandate WAVE 1 → July 6, 2026 source: State Medicaid Agencies action: CY2027 SMAC submissions scope: per-state, per-agency owner: Medicaid compliance + contracts risk: late submission = CY2027 exposure WAVE 2 → October 1, 2026 source: CY2027 MA Final Rule action: Integrated ID card / HRA requires: cross-system data alignment owner: IT + Medicare + Medicaid ops risk: missed October 1 = January enrollment gap WAVE 3 → 2027-2030 source: §422.514(h) action: Enrollment restriction scope: affiliated Medicaid MCO required 2027: enrollment limited to affiliated plan 2030: exclusively aligned enrollment risk: product viability without MCO affiliate
// GOVERNANCE GAP DETECTED Most health plan compliance orgs: Medicare team: monitors CMS / ODAG / CPE Medicaid team: manages SMAC / state rules Coordination layer: rarely formalized D-SNP compliance requires both: - SMAC = Medicaid contract - Integrated HRA = cross-system IT project - Enrollment restriction = shared MCO roster // KEY QUESTION Does your compliance committee own this across both teams — or is it split between two separate governance structures with no shared accountability? // MARKET SIGNAL C-SNP +71% (2024-2025) D-SNP +3% (2024-2025) Dual-eligible in C-SNPs: ~20% of surge Interpretation: plans are solving for regulatory burden, not integration goal
Source: KFF SNP analysis (Sept 2025); CMS CY2027 Final Rule; Federal Register 2026-06600
The Governance Problem Underneath the Calendar
Most health plan compliance programs are organized around a single regulatory framework. Medicare compliance teams monitor CMS program audit activity, manage the ODAG and CPE review cycles, and track annual final rule changes. Medicaid compliance teams work with state agencies, manage SMAC contracts, and navigate state-specific quality and reporting requirements.
In most large health plans, these teams are structurally separate. D-SNPs sit across that organizational boundary. A SMAC submission due July 6 is a Medicaid contract document reviewed by a state Medicaid agency. An integrated HRA operational by October 1 requires coordination between the Medicare enrollment system and the Medicaid eligibility database. An exclusively aligned enrollment requirement beginning in 2027 requires the Medicare and Medicaid plan business units to share a member roster and enrollment decision workflow.
The plans best positioned to meet this compliance timeline are not necessarily the ones with the most robust Medicare compliance programs. They are the ones that have built governance structures designed to operate across both programs simultaneously. That is a different organizational design question — and one that most compliance frameworks have not yet answered.
For plans still deciding whether to remain in the D-SNP market, operate through C-SNPs, or pursue both simultaneously, the June and October deadlines are decision accelerators. The governance question cannot be deferred to the 2027 enrollment period. It is already open.
Key Insight
The problem is not regulatory complexity. The problem is that two separate compliance programs must now produce a single coordinated output — and most governance structures were not designed for that.
The Arbitrage Risk
C-SNPs avoid integration requirements. But CMS has observed the enrollment pattern. The look-alike threshold has dropped twice. Regulators rarely allow visible arbitrage to persist indefinitely.
Until next week, stay briefed.
— PCOOB Weekly, June 25, 2026
“The plans best positioned to meet this compliance timeline are the ones that have built governance structures designed to operate across both programs simultaneously.”
The D-SNP integration mandate is not a stable set of requirements. It is a policy trajectory. CMS has tightened the look-alike threshold three times since 2022. FIDE and HIDE integration requirements expanded in 2025. The CY2027 final rule added ID card and HRA mandates. The §422.514(h) enrollment restriction escalates through 2030.
Plans that treat each annual rule cycle as a discrete compliance project are misreading the pattern. This is a progressive compliance build — each year adds requirements, narrows alternatives, and moves the integration endpoint closer.
D-SNP look-alike threshold set at 80%. CMS eliminates plans serving 80%+ dual-eligible enrollees without full D-SNP status.
Look-alike drops to 70%. FIDE SNPs: exclusively aligned enrollment required. HIDE SNPs: aligned service areas required.
Look-alike drops to 60%. SMAC due July 6. Integrated ID card + HRA active October 1.
§422.514(h): enrollment restricted to individuals in affiliated Medicaid plan.
FIDE SNPs: exclusively aligned enrollment. One shared enrollee base across both programs.
What Needs to Move Now
Four governance questions that cannot wait for the 2027 enrollment planning cycle.
Who owns July 6?
CY2027 SMAC submissions are due July 6, 2026. Is that process owned by your Medicaid team, your Medicare team, or a joint governance structure? Multi-state operators need a per-state submission tracker with confirmed agency contacts today.
Is your HRA one document or two?
The integrated HRA requirement means a single assessment covering both Medicare and Medicaid dimensions. If your clinical and enrollment teams currently run separate HRA workflows, the October 1 deadline is an IT and operations project — not just a policy update.
Is your C-SNP dual-eligible enrollment a managed decision?
If dual-eligible individuals are enrolling in C-SNPs rather than D-SNPs, is that an intentional plan design strategy or an unexamined enrollment pattern? CMS has watched the C-SNP surge. Plans should have a documented rationale before regulators ask for one.
Does your affiliated Medicaid MCO relationship support exclusively aligned enrollment?
The §422.514(h) enrollment restriction means the D-SNP and its affiliated Medicaid plan must share the same enrollee base by 2030. Does your current Medicaid MCO affiliate operate in all counties where your D-SNP serves members? If not, the product viability question is open now — not in 2029.
Why It Matters — By Function
Compliance
SMAC submissions due July 6. If you operate D-SNPs in multiple states, that deadline is not a single task — it is a multi-agency coordination effort that should already be in progress.
Operations
The October 1 HRA integration requirement demands data pipeline coordination between Medicare and Medicaid enrollment systems. Plans waiting until Q4 will not have enough implementation runway.
Government Affairs
The §422.514(h) enrollment restriction timeline is a product strategy constraint, not just a compliance question. Whether a plan can sustain exclusively aligned enrollment depends on its affiliated Medicaid contract footprint.
Finance / Actuarial
D-SNP and C-SNP margins are approximately double the MA average. Growing dual-eligible share of C-SNP enrollment creates risk adjustment and audit exposure as CMS monitors the arbitrage pattern.
IT / Data Governance
Integrated ID cards and integrated HRAs require shared eligibility records across Medicare and Medicaid systems. This is an IT project with a fixed deadline — October 1, 2026 — not an aspirational goal.
Product / Strategy
The choice between D-SNP, C-SNP, and both-simultaneously is no longer neutral. It carries compliance architecture, payment implications, and regulatory scrutiny. The decision needs to be documented and defensible.
Questions Leaders Should Be Asking
Are our SMAC contracts current, accurate, and ready for CY2027 submission by July 6? Who owns that process — our Medicaid team, our Medicare team, or both?
What does our integrated HRA process look like today? Do we have a single assessment that satisfies both Medicare and Medicaid requirements, or two separate assessments that will need to be redesigned by October 1?
If we have dual-eligible enrollees in C-SNPs, are we prepared for CMS to scrutinize that enrollment pattern as the look-alike threshold tightens further?
Has our compliance committee reviewed the §422.514(h) enrollment restriction timeline? Does our current affiliated Medicaid MCO relationship support exclusively aligned enrollment by 2030?
Are our Medicare and Medicaid compliance teams operating with shared governance for D-SNP requirements — or managing to separate regulatory calendars with no coordination mechanism?