D-SNP Medicaid State Alignment: Building Networks That Satisfy Both CMS and Your State

The Dual Regulatory Framework for D-SNP Networks

Dual Eligible Special Needs Plans occupy a uniquely complex regulatory position in the managed care landscape. A D-SNP is a Medicare Advantage plan — subject to CMS oversight under Title XVIII, governed by 42 CFR Part 422, and required to meet CMS network adequacy standards as specified in 42 CFR 422.107 and the annual CMS Final Rule. At the same time, a D-SNP must hold a Medicaid contract with the state Medicaid agency or, at minimum, a Memorandum of Understanding (MOU) with the state that governs how the D-SNP coordinates Medicaid benefits for dually eligible beneficiaries. That MOU creates a second layer of network obligations — Medicaid network requirements — that overlay the federal Medicare Advantage standards.

The challenge for D-SNP network teams is that these two regulatory frameworks were designed independently and do not always align. CMS's MA network adequacy standards use time-and-distance thresholds applied at the county level across defined specialty categories. State Medicaid agency network requirements may use different geographic units (zip codes, planning regions, or service areas), different specialty categories (including LTSS provider types not addressed in CMS adequacy standards), different quantitative thresholds (provider-to-member ratios rather than time-and-distance standards), and different measurement methodologies. A network that satisfies CMS's adequacy requirements may fall short of state Medicaid standards in certain provider categories — and a network built to state Medicaid standards may not pass CMS's HPMS adequacy submission without additional analysis and documentation.

The regulatory stakes of D-SNP network non-compliance are higher than for standard MA plans because D-SNP beneficiaries are among the most medically complex and socially vulnerable members in the healthcare system. CMS and state Medicaid agencies both prioritize D-SNP oversight and both conduct monitoring activities that can surface network deficiencies and result in enforcement actions. D-SNP network teams that understand the dual compliance framework and build their networks to satisfy both sets of requirements simultaneously are in a structurally stronger position than teams that optimize for one framework and retrofit the other.

How State Medicaid Agency Network Requirements Differ from CMS MA Standards

The specific differences between state Medicaid network requirements and CMS MA standards vary across states, but several categories of difference appear consistently across Medicaid managed care markets.

Geographic measurement is a common area of divergence. CMS measures MA network adequacy using county-level time-and-distance standards — maximum drive time or drive distance from a member's residence to a contracted provider. Many state Medicaid agencies use provider-to-member ratios as their primary adequacy metric, requiring a minimum number of contracted providers per 1,000 members in each geographic service area. These two measurement approaches can produce different assessments of the same network: a county that passes CMS's time-and-distance standard because a single large group practice is within the threshold distance may fail a state's provider-to-member ratio standard if that group's panel capacity is insufficient to serve the plan's Medicaid enrollment in the county.

Specialty category coverage is a second area of divergence. CMS evaluates MA network adequacy across 22 specialty categories. State Medicaid managed care contracts typically include a broader set of provider types, particularly in the LTSS and behavioral health categories. States operating MLTSS programs require plans to maintain networks of personal care attendants, home health agencies, adult day health programs, assisted living facilities, and HCBS waiver service providers — provider types entirely outside the scope of CMS's 22-category adequacy framework. D-SNP plans participating in MLTSS programs must build networks that cover the full MLTSS provider universe in addition to the standard MA specialty categories, and must document adequacy separately in each framework.

Appointment access standards are a third area of divergence. CMS's MA adequacy standards are primarily geographic — they measure whether providers are physically accessible within a defined time or distance threshold. State Medicaid managed care contracts frequently include appointment access standards — maximum waiting times for routine appointments, urgent care appointments, and behavioral health appointments — that impose an additional access dimension beyond geographic proximity. A plan can have adequate geographic distribution of providers and still fall short of state Medicaid appointment access standards if those providers have long wait times for appointments.

MOU Network Commitments and How They Interact with the Adequacy Filing

Under 42 CFR 422.107, D-SNPs are required to have a Memorandum of Understanding with the state Medicaid agency in each state where they operate. The MOU is not simply an administrative formality — it is a legally binding agreement that specifies, among other things, the Medicaid benefits the plan will coordinate for dually eligible beneficiaries and the network requirements the plan will meet in serving those beneficiaries.

MOU network commitments vary substantially across states and plan types. In states where D-SNPs are Highly Integrated Dual Eligible Special Needs Plans (HIDE SNPs) — plans that provide both Medicare and Medicaid benefits directly — the MOU network commitments are typically the most comprehensive, effectively incorporating the full scope of the state's Medicaid managed care network requirements into the D-SNP's operational framework. In states where D-SNPs operate as Fully Integrated Dual Eligible Special Needs Plans (FIDE SNPs), the Medicaid contract is typically a separate document from the MOU, and the network requirements are specified in the Medicaid managed care contract rather than the MOU itself.

The interaction between MOU network commitments and the annual CMS adequacy filing creates a documentation alignment requirement that D-SNP network teams frequently underestimate. The CMS HPMS adequacy submission reflects the plan's Medicare Advantage network — the network that satisfies CMS's 22-category, county-level, time-and-distance framework. The MOU network commitments reflect the plan's Medicaid coordination obligations, which may include LTSS providers, behavioral health providers, and other provider types not captured in the HPMS submission. These two documentation artifacts are reviewed by different regulatory bodies on different timelines and in different formats, but they must be consistent in their representation of the plan's contracted network. Inconsistencies — providers listed in Medicaid network documentation but not in the CMS filing, or adequacy representations in the HPMS submission that contradict Medicaid access reports — create dual compliance exposure that is difficult to remediate after the fact.

LTSS Provider Requirements Specific to D-SNPs

Long-term services and supports provider network requirements are among the most distinctive and operationally demanding aspects of D-SNP network compliance. Dually eligible beneficiaries are disproportionately likely to require LTSS, and CMS has consistently emphasized that D-SNPs must maintain networks capable of meeting the LTSS needs of their enrolled populations. State Medicaid agencies have further operationalized this expectation through Medicaid managed care contract requirements that specify minimum network standards for individual LTSS provider types.

The LTSS provider universe that D-SNP networks must address includes, at minimum: home health agencies providing skilled nursing and therapy services; personal care attendant programs providing non-skilled in-home support services; adult day health programs providing structured daytime care and health monitoring; assisted living facilities and residential care homes for members who need a supported living environment but do not require nursing facility level of care; skilled nursing facilities for members requiring post-acute or long-term institutional care; and, in states with robust HCBS waiver programs, the full range of HCBS waiver service providers — including supported employment, adult companion services, environmental modification contractors, and others.

Building and maintaining a D-SNP LTSS network requires a fundamentally different approach from the provider recruitment processes that work for physician and specialist networks. LTSS providers are often not enrolled in PECOS or state provider enrollment databases in the same way that licensed clinicians are, making standard provider data sources less useful for initial network development. LTSS provider contracting often involves negotiating not with a centralized medical group or hospital contracting department but with individual agency administrators who have limited familiarity with managed care contracting conventions. And LTSS provider credentialing is governed by state-specific certification and licensure requirements that vary considerably across states and provider types.

Behavioral Health Parity Requirements in the Dual-Eligible Context

D-SNP beneficiaries have substantially elevated rates of behavioral health conditions compared to the general Medicare Advantage population. Studies consistently find that a majority of dually eligible beneficiaries have at least one behavioral health diagnosis, and a significant proportion have serious mental illness (SMI) or substance use disorder (SUD). This population-level behavioral health need creates both a network adequacy imperative and a regulatory compliance obligation that D-SNP network teams must address explicitly.

At the federal level, the Mental Health Parity and Addiction Equity Act (MHPAEA) requires that MA plans — including D-SNPs — not impose treatment limitations or financial requirements on mental health and substance use disorder benefits that are more restrictive than those applied to medical and surgical benefits. From a network adequacy perspective, this means that geographic access standards for behavioral health providers must be comparable to those applied to analogous medical specialty providers. A D-SNP that maintains robust physician and specialist networks but has sparse behavioral health provider networks in certain counties may face a parity argument in addition to a standard adequacy finding.

At the state Medicaid level, behavioral health network requirements for D-SNPs serving populations with SMI or SUD often include specific provider type mandates — psychiatric prescribers, licensed therapists, community mental health centers, certified peer support specialists, and, in SUD waiver markets, providers across the full ASAM Criteria treatment continuum. D-SNP network teams should review their state Medicaid managed care contract provisions for behavioral health-specific network requirements before finalizing their adequacy modeling methodology, as generic MA behavioral health adequacy standards may not capture all of the state Medicaid obligations that apply to the dual-eligible behavioral health network.

Coordination Between MA Network Team and Medicaid Contract Management

One of the most common structural failures in D-SNP network compliance is insufficient coordination between the plan's Medicare Advantage network team — responsible for the CMS HPMS adequacy filing — and the Medicaid contract management team — responsible for maintaining the state Medicaid managed care contract and MOU compliance. In large plan organizations, these functions may sit in different divisions, report to different leadership structures, and use different systems of record for network documentation. The result is a siloed compliance posture that produces accurate documentation within each framework but fails to maintain consistency across the two frameworks.

The consequences of siloed D-SNP network management range from the operational — providers counted in one framework but not the other, requiring manual reconciliation before regulatory submissions — to the compliance — representations in the CMS HPMS filing that are inconsistent with representations in state Medicaid network reports, creating discrepancies that can surface in cross-agency oversight activities. CMS has engaged in increased information sharing with state Medicaid agencies regarding D-SNP compliance, and the probability that inconsistencies between the two frameworks will be detected has increased accordingly.

Best-practice D-SNP organizations designate a D-SNP network compliance lead who has responsibility for both the CMS adequacy submission and the Medicaid network compliance documentation and who ensures that provider roster data, adequacy calculations, and network representations are consistent across both frameworks. This person serves as the integration point between the MA network team and the Medicaid contract management team, and is responsible for maintaining the cross-framework documentation alignment that regulators expect. Depending on the organization's structure, this role may be a new position or an expanded scope for an existing network compliance manager — but the explicit designation of someone with cross-framework accountability is essential for D-SNP organizations that want to maintain a defensible compliance posture.

How Blueprint Handles D-SNP Dual Compliance Tracking

Blueprint Network Hub's multi-program architecture is designed to support D-SNP dual compliance tracking without requiring separate, siloed systems for MA and Medicaid network documentation. The platform maintains a unified provider roster that can be tagged with both MA specialty classifications (aligned with CMS's 22-category framework) and Medicaid provider type designations (aligned with state-specific LTSS and behavioral health network requirements), allowing the same provider record to support both compliance frameworks without duplication or manual reconciliation.

Blueprint's adequacy scoring engine can run compliance calculations against both CMS time-and-distance standards and state Medicaid provider-to-member ratio standards simultaneously, giving D-SNP network teams a unified view of their adequacy posture across both frameworks. Gap identification highlights counties and provider types where the network meets one framework's standards but not the other's — the most common source of D-SNP compliance exposure — allowing network teams to target recruitment efforts at the highest-priority dual compliance gaps rather than managing the two frameworks sequentially and discovering misalignments only at submission time.

For plans managing MOU network commitments, Blueprint's reporting module supports the documentation formats that state Medicaid agencies and CMS require for D-SNP network compliance reporting, including both HPMS-formatted adequacy calculations and state-specific network reports that reflect the plan's Medicaid contract obligations. The platform's cross-framework documentation architecture ensures that network representations are consistent between the CMS filing and the state Medicaid network reports — the fundamental prerequisite for a defensible D-SNP compliance posture in an era of increasing federal-state regulatory coordination.