Free Network Build Assessment
Score your buildDual Eligible Special Needs Plans must satisfy both CMS network adequacy standards and state Medicaid agency requirements, and those two sets of standards don't always align. Here's how network teams navigate the overlap.
Dual Eligible Special Needs Plans occupy a uniquely complex regulatory position in the managed care landscape. A D-SNP is a Medicare Advantage plan: governed by 42 CFR Part 422 and required to meet CMS's network adequacy standards under 42 CFR 422.116. At the same time, a D-SNP must have a contract with the state Medicaid agency under 42 CFR 422.107, which governs how it coordinates Medicaid benefits for dually eligible beneficiaries. That contract, and any Medicaid managed care contract the organization holds, can add a second layer of network obligations.
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 review.
D-SNP members are often medically complex, so gaps matter. It is easier to build for both sets of requirements from the start than to optimize for one and retrofit the other.
The specific differences between state Medicaid network requirements and CMS MA standards vary across states, but there are several kinds of difference to look for.
Geographic measurement is one. CMS measures MA network adequacy county by county, with a minimum count and a required share of beneficiaries within both a maximum time and a maximum distance of a contracted provider. A state may use other measures, such as provider-to-member ratios, across its own service areas. These two 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 29 provider types and 14 facility types. State Medicaid contracts may include a broader set of provider types, particularly in LTSS and behavioral health. States operating MLTSS programs may require networks of personal care attendants, home health agencies, adult day health programs, assisted living facilities, and HCBS waiver service providers, which aren't part of CMS's MA framework. A D-SNP organization in an MLTSS program has to cover those providers as well as the standard MA types.
Appointment access standards are a third difference. CMS's MA time-and-distance test is geographic, though MA has its own wait standards under 42 CFR 422.112(a)(6)(i) for primary care and behavioral health. On the Medicaid side, 42 CFR 438.68(e) requires states to hold plans to maximum waits for routine appointments, starting with the first rating period beginning on or after July 9, 2027. A plan can have adequate geographic distribution and still fall short if its providers have long waits.
Under 42 CFR 422.107, a D-SNP needs a contract with the state Medicaid agency in each state where it operates. It is a legally binding agreement, not an administrative formality, and it may include commitments that affect your network.
These commitments vary across states and plan types. FIDE and HIDE designations carry more integration requirements than a coordination-only D-SNP, so read the terms that apply to your designation.
The state contract and the CMS filing need to agree. The HSD tables show the plan's Medicare Advantage network, scored against CMS's 29 provider types and 14 facility types. State commitments may also cover LTSS, behavioral health, and other provider types not on those tables. The two are reviewed by different agencies on different timelines, so check that they describe your contracted network consistently.
Long-term services and supports can be among the most demanding parts of D-SNP network compliance, depending on what your state contract covers.
The LTSS provider universe can include: 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 needs make this part of the network hard to skip for a D-SNP, and the rules come from two directions.
At the federal level, CMS's MA standards cover psychiatry, clinical psychology, clinical social work and outpatient behavioral health, and 42 CFR 422.112(a)(6)(i) sets appointment wait standards for behavioral health.
At the state Medicaid level, behavioral health network requirements may include specific provider types: 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.
A common structural failure in D-SNP network compliance is poor coordination between the Medicare Advantage network team, responsible for the CMS HPMS filing, and the Medicaid contract management team, responsible for the state contracts. In large organizations, these functions may sit in different divisions and use different systems of record.
The consequences range from providers counted in one framework but not the other, which means manual reconciliation before each submission, to statements in a CMS filing that don't match what the state was told.
Consider designating 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 keeps the two consistent. This may be a new position or an expanded role for an existing network compliance manager. What matters is that one named person is accountable across both.
Blueprint scores adequacy against CMS's Medicare Advantage standards. It doesn't include state Medicaid rules out of the box and doesn't score both at once, but a customer can load another standards file, for example a state's Medicaid standards, and the engine scores against that file and cites it.
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.