Free Network Build Assessment
Score your buildDual Eligible Special Needs Plans meet the standard Medicare Advantage network rules, and their contract with the state Medicaid agency can add more. New plan teams need to understand where the requirements differ.
Dual Eligible Special Needs Plans (D-SNPs) serve Medicare beneficiaries who are also enrolled in Medicaid: a population with complex health needs, high rates of chronic conditions, and significant reliance on both medical and social services. A D-SNP is a Medicare Advantage plan, governed by 42 CFR Part 422 and filed through HPMS, so CMS's MA network adequacy standards apply. The key difference is that a D-SNP also needs a contract with the state Medicaid agency under 42 CFR 422.107, and that contract and the state's Medicaid program can add requirements of their own.
New D-SNP plan teams, particularly those launching D-SNPs within an existing MA organization, can underestimate that second layer. This guide covers the key areas to check.
D-SNPs differ in how closely they integrate with the state Medicaid program, and FIDE and HIDE designations carry more integration requirements. More integrated plans need networks that can coordinate both Medicare and Medicaid services for members.
The contract with the state Medicaid agency may specify network requirements beyond those CMS imposes directly. Review what the state asks for during market entry planning, because it varies by state and can include provisions on LTSS provider networks, behavioral health, and care coordination.
Beyond the 29 provider types and 14 facility types in CMS's 2026 HSD Reference File, your state contract or Medicaid program may call for other categories relevant to the dual eligible population, such as:
Credentialing LTSS providers, personal care agencies, adult day programs, home health agencies, requires different credentialing standards than physician credentialing. These providers are licensed at the entity level (the agency), not the individual level, and their credentialing involves verification of state licensure, Medicare and Medicaid certification, liability insurance, background check processes for direct care workers, and quality and compliance history. Plans new to credentialing LTSS provider types should not assume their physician credentialing workflow applies: it does not, and applying the wrong standards creates compliance gaps.
D-SNP provider directories should accurately reflect the full scope of the plan's network, including any LTSS and behavioral health providers, not just the medical network. Extend your verification workflow to non-physician providers too. Section 422.111(b)(3)(i) also requires MA plans to disclose providers' cultural and linguistic capabilities, including American Sign Language.
Members may transition to a new D-SNP from fee-for-service Medicare or from another plan, some in the middle of treatment. Check the transition rules that apply to you, and ask whether your network has the capacity to absorb them.
FIDE and HIDE plans carry more integration requirements, so members shouldn't experience fragmented access when their care involves both programs. This takes coordination between the plan's MA network team and its Medicaid managed care counterpart, which can be hard when those teams sit in separate parts of the organization.
If a D-SNP build doesn't account for the extra provider types, LTSS credentialing, and state contract provisions from the beginning, the gaps tend to surface close to the filing deadline. Begin with a D-SNP-specific provider requirements map, not just the standard MA list, and engage with the state Medicaid agency's managed care unit early, before you finalize the build plan.
Blueprint automates the network build workflows described in this article: from adequacy modeling to provider outreach tracking. See it with your state and line of business.