Network Requirements for Section 1115 Medicaid Waiver Programs: A Health Plan Guide

What Section 1115 Waivers Are and How They Affect Network Obligations

Section 1115 of the Social Security Act grants the Secretary of Health and Human Services broad authority to approve experimental, pilot, or demonstration projects that promote Medicaid's objectives. When a state receives an 1115 waiver approval, it can deviate from standard Medicaid requirements — including eligibility rules, benefit structures, cost-sharing provisions, and, critically, managed care contracting requirements — in ways that have direct consequences for the networks that managed care organizations must build to serve waiver populations.

For health plan network teams, an 1115 waiver is not simply an administrative background fact. It is a legally binding framework that modifies the network standards the plan must meet in order to maintain its contract to serve the waiver population. Waiver demonstrations frequently introduce population-specific provider requirements, access standards tailored to high-need beneficiaries, and monitoring obligations that exceed those applicable to the plan's standard Medicaid managed care lines of business. Plans that apply their standard network adequacy framework to a waiver population without reading the waiver Special Terms and Conditions (STCs) in detail routinely find themselves out of compliance with obligations they did not know they had accepted.

The starting point for any network team managing a plan participating in a Section 1115 demonstration is a thorough reading of the waiver's Special Terms and Conditions, which are the legally binding terms negotiated between the state and CMS. The STCs specify the populations covered under the demonstration, the benefits included, the managed care contracting requirements that apply, and any network-specific obligations the waiver imposes. STCs vary substantially across states and demonstrations, so generic knowledge of 1115 waivers is not a substitute for reading the specific STC package governing your plan's participation.

How CMS Waiver Approval Processes Intersect with Network Standards

Section 1115 waivers are negotiated between the state Medicaid agency and CMS, and the terms of that negotiation establish the network standards that managed care plans participating in the demonstration must meet. CMS approval of a waiver does not mean CMS has pre-approved the specific network the plan will build — it means CMS has agreed to the general framework of standards within which the plan's network will be evaluated.

The practical implication is that plans participating in 1115 demonstrations face a two-layer regulatory oversight structure. At the federal level, CMS retains oversight authority over the demonstration and can impose conditions on the state's waiver renewal — conditions that may include enhanced network monitoring requirements or access standard modifications that flow down to managed care organizations through the state's contract amendment process. At the state level, the Medicaid agency serves as the plan's direct regulator and contract counterparty, and the state agency interprets and enforces the STC network requirements as part of its demonstration oversight responsibilities.

CMS conducts formal waiver evaluation activities, including independent evaluation requirements specified in the STCs, and those evaluations include assessments of beneficiary access to care. Network deficiencies identified in waiver evaluations are reported to CMS and can affect state waiver renewal prospects — which creates a state-level incentive to monitor plan network compliance more intensively than might occur in a standard managed care contracting relationship.

Plans should maintain regular communication with the state Medicaid agency's managed care contracting team throughout the demonstration period, not only during contract renewal cycles. Waiver STCs can be amended through Allotment Action Requests (AARs) or STC amendments at any point during the waiver term, and network requirement modifications can take effect relatively quickly once a STC amendment is approved. Plans that learn about STC amendments through the state contracting process rather than through active monitoring of the federal-state correspondence are frequently behind on implementation timelines.

State Flexibility Under Waiver Authority and What It Means for Plans

One of the defining features of 1115 waivers is that they allow states to exercise flexibility that is not available under standard Medicaid managed care authorities. For network teams, this flexibility manifests in several ways that create plan-specific obligations not found in the standard regulatory framework.

States frequently use 1115 authority to extend Medicaid coverage to populations not otherwise eligible — expansion adults under the ACA, individuals in institutions for mental disease (IMDs) under waiver IMD exceptions, justice-involved individuals, or other populations with distinctive service profiles. Each newly eligible population group may have associated network requirements: substance use disorder treatment providers for justice-involved beneficiaries, IMD-based providers for seriously mentally ill individuals, or primary care providers with documented experience serving low-income uninsured populations for expansion adults. The plan's network cannot be a simple extension of its existing Medicaid network; it must be evaluated against the actual service needs of the waiver population.

States also use 1115 authority to implement managed long-term services and supports (MLTSS) programs, which bring LTSS benefits into managed care and impose network requirements for home- and community-based services (HCBS) providers — personal care agencies, adult day health programs, home health agencies, supported employment providers, and others — that standard managed care networks typically do not include. MLTSS network builds are among the most complex managed care network builds in the Medicaid space, precisely because the provider universe is diffuse, often operates through individual provider arrangements, and is not systematically represented in standard provider directories or enrollment databases.

Population-Specific Network Requirements Common to 1115 Waivers

Certain population-specific network requirements appear with enough frequency across 1115 demonstrations that network teams should treat them as baseline expectations when entering a waiver market, subject to verification against the specific STC provisions of the applicable demonstration.

Behavioral health provider requirements are the most commonly encountered population-specific network obligation in 1115 waivers. Demonstrations serving individuals with serious mental illness (SMI) or serious emotional disturbance (SED), or those implementing behavioral health integration initiatives, routinely specify minimum network requirements for psychiatrists, licensed clinical social workers, psychologists, community mental health centers (CMHCs), and certified community behavioral health clinics (CCBHCs). Some states have established quantitative access standards for behavioral health — minimum appointment availability timelines, for example — that exceed the general managed care access standards and require specific tracking and reporting by the plan.

Substance use disorder (SUD) treatment network requirements have expanded substantially in states that received 1115 waiver authority specifically to address the opioid epidemic. CMS approved a series of SUD-specific 1115 demonstrations beginning in 2015, and the network requirements associated with those demonstrations include minimum capacity for each level of the ASAM Criteria continuum of care: outpatient, intensive outpatient, partial hospitalization, residential, and medically managed intensive inpatient treatment. Plans participating in SUD demonstrations must not only contract with providers across the continuum but also verify that those providers are licensed at the appropriate level by the state behavioral health authority and meet any state-specific SUD treatment provider certification requirements.

Long-term services and supports (LTSS) provider network requirements apply under MLTSS demonstrations and are among the most operationally demanding network build challenges. LTSS provider types include personal care attendants, home health agencies, adult day health programs, assisted living facilities, skilled nursing facilities, and the full range of HCBS waiver service providers. Each provider type may have its own credentialing or enrollment requirements under the state's HCBS waiver program, and the plan must build contracting relationships that accommodate the state's existing HCBS program structures rather than importing standard managed care contracting models wholesale.

Monitoring and Reporting Obligations Under Waiver Authority

Section 1115 demonstrations universally include enhanced monitoring and reporting obligations that go beyond what managed care plans typically face in standard Medicaid contracting. These obligations are imposed on the state by the STC monitoring and evaluation requirements, and states flow them down to managed care plans through the managed care contract.

The most common network-related reporting obligations include: monthly or quarterly provider network reports to the state, including provider counts by type, geographic distribution, and panel availability status; beneficiary access reports that track appointment availability and wait times for key provider types; member complaint and grievance data specifically related to access-to-care issues, reported with sufficient detail for the state to identify network adequacy correlates; and provider directory accuracy reports that confirm the currency of the plan's public provider directory against the active network.

Many 1115 demonstrations also include independent evaluation requirements — typically conducted by a CMS-designated evaluator or an independent contractor selected by the state — that include network adequacy assessment components. Plans may be required to provide data to independent evaluators on a separate timeline from their regular state reporting obligations. Understanding the full scope of monitoring and reporting obligations before the contract is executed allows network teams to build the data collection and reporting infrastructure they will need before they are in breach of a reporting deadline.

Plans should also be aware that CMS has the authority to require corrective actions at the state level if monitoring data reveals access deficiencies in the demonstration population. CMS-state corrective action correspondence related to network adequacy in 1115 demonstrations frequently triggers expedited state-plan contract compliance requirements that plans must respond to on compressed timelines.

Documenting Network Compliance in a Waiver Program Context

Documenting network compliance in an 1115 waiver program context requires a more structured and population-specific approach than standard managed care network documentation. The documentation framework must account for the population-specific provider requirements, the enhanced reporting obligations, and the dual federal-state oversight structure that characterizes 1115 demonstrations.

At the provider roster level, waiver program network documentation should maintain provider type classifications that map to the STC's network requirement categories — not just the plan's internal specialty taxonomy. If the STC specifies minimum network requirements for CCBHCs, the plan's roster must be able to identify CCBHC-certified providers specifically, not just behavioral health providers generally. If the STC specifies ASAM Criteria continuum levels for SUD treatment, the plan's provider database must maintain the ASAM credentialing level for each SUD treatment provider in the network.

At the access standard documentation level, plans should maintain appointment availability tracking that reflects the specific access standards in the STC rather than generic managed care access standards. If the STC requires that a member seeking routine behavioral health care can obtain an appointment within 10 business days, the plan's access monitoring system should be tracking against that 10-day standard — not a generic 30-day standard that may apply to other lines of business.

At the reporting documentation level, plans should maintain an indexed archive of all state-required network reports, including the methodology used to generate each report and the data sources used. When state or federal auditors review waiver program network compliance, the ability to trace each reported data point back to the underlying provider records and data systems is a critical element of a defensible compliance posture.

How Blueprint Supports 1115 Waiver Network Compliance

Blueprint Network Hub's provider tagging and specialty classification system supports the population-specific network documentation that 1115 waiver compliance requires. Plans can configure provider classifications that map to STC-defined provider categories — including CCBHC certification status, ASAM Criteria credentialing levels, HCBS waiver service provider type, and other waiver-specific designations — and track network adequacy against those population-specific categories rather than relying on generic specialty codes.

The platform's reporting infrastructure supports the enhanced state reporting obligations that 1115 demonstrations impose, with exportable provider network reports that can be configured to match state-specified report formats. Blueprint's access standard tracking also accommodates STC-specific appointment availability requirements, allowing plans to monitor compliance against population-specific access standards and identify deficiencies before they surface in state audit or independent evaluation activities. For network teams managing multiple lines of business — including both standard Medicaid managed care and 1115 demonstration contracts — Blueprint's multi-program structure maintains the separation of network compliance tracking that regulators expect without requiring duplicative data entry across programs.