In July 2025, the Washington State Senate Health and Long-Term Care Committee convened to discuss the implications of H.R. 1 for Medicaid. Medicaid Director Fotinos delivered the stark assessment: work requirements would affect 620,000 adults enrolled in Apple Health, and while most recipients already work, the administrative burden would drive significant coverage losses. The Health Care Authority was working to automate eligibility through CMS systems, but those systems wouldn’t be ready until June 2027. Fortunately, Washington already qualified to delay implementation of federal work requirements until December 2028 by demonstrating good faith effort toward compliance infrastructure.
This positioning reflects Washington’s broader resistance stance. Governor Bob Ferguson, who took office in January 2025 after serving as attorney general, has been among the most vocal critics of federal Medicaid changes. He characterized work requirement provisions as devastating and predicted at least 250,000 Washingtonians would lose coverage. The Governor’s office committed to maintaining Medicaid eligibility for all who currently qualify under state law, though the state cannot override federal eligibility conditions for federally funded programs.
H.R. 1, signed July 4, 2025, transformed Medicaid work requirements from a state-option policy experiment into a federal mandate affecting approximately 18.5 million expansion adults nationwide. The law requires 80 hours monthly of work, education, training, or qualifying community engagement activities, with semi-annual redetermination cycles replacing annual reviews. States face a January 1, 2027 implementation deadline, though good-faith extensions are available through December 31, 2028 for states demonstrating genuine progress toward compliance infrastructure.
CMS issued its first substantive implementation guidance on December 8, 2025, establishing several parameters that shape state planning. States must use reliable data sources to verify compliance before requesting documentation from enrollees, a data-first approach that privileges automated verification over member-initiated reporting. A 30-day cure period is required between initial non-compliance determination and coverage termination, during which members can demonstrate they were meeting requirements or qualify for exemptions. Congress allocated $200 million in implementation funding, half distributed equally across states and half proportional to affected population.
Two provisions create particular downstream pressure. Individuals who lose Medicaid coverage for work requirement non-compliance are barred from receiving premium tax credits on the ACA marketplace, meaning non-compliance creates a coverage void rather than a coverage transition. And the Trump administration rescinded Biden-era guidance on health-related social needs services in March 2025, while CMS has signaled it will not approve new or extend existing continuous eligibility waivers, narrowing the flexibility states had been using to stabilize enrollment.
Washington’s Health Care Authority updated its impact timeline in January 2026, confirming the state’s intention to seek the extension waiver. This positions implementation for late 2028 at the earliest, providing time to build automated verification systems and member navigation infrastructure. The state’s resistance posture creates political tension with federal mandates, but Washington’s Democratic legislative majority and governor’s office present a unified front on coverage preservation.
The Apple Health Brand Confusion Challenge#
Legislative hearings flagged a persistent problem that could undermine implementation. Many Washington residents are unaware that Apple Health is the state’s Medicaid program. This branding disconnect means eligible individuals may not understand that new federal requirements apply to them. The confusion stems from a deliberate strategy to reduce Medicaid stigma by using a distinctive brand name, but it creates communication challenges when federal changes specifically target “Medicaid expansion adults.”
Washington expanded Medicaid under the Affordable Care Act on January 1, 2014. Expansion enrollment exceeded 800,000 at its peak during the pandemic. The unwinding period reduced enrollment to approximately 620,000 expansion adults as of mid-2025. These individuals, aged 19 to 64 without qualifying disabilities, will be subject to work requirements unless they meet federal exemptions.
The state’s outreach infrastructure built during expansion provides foundation for work requirement communications. Community-based organizations, healthcare systems, and county health departments established enrollment assistance networks. Whether these networks can be mobilized for compliance navigation at scale remains uncertain. The transition from helping people gain coverage to helping them maintain coverage through verification processes represents new territory.
Administrative Structure and Verification Capacity#
Washington operates a state-administered Medicaid program through the Health Care Authority. Unlike county-administered states such as New York or California, eligibility determinations are centralized through state systems. This structure provides administrative consistency but concentrates implementation burden on state agencies.
The Department of Social and Health Services administers programs for aged and disabled populations. Washington Healthplanfinder, operated by the Washington Health Benefit Exchange, manages enrollment for working-age adults and families. This division of responsibility across state agencies creates coordination requirements for work requirement implementation.
Washington has never implemented Medicaid work requirements. The state lacks institutional memory from prior attempts. This absence of experience means building verification systems, exemption determination processes, and member navigation infrastructure from scratch. The compressed federal timeline compounds the challenge, though Washington’s extension waiver provides breathing room.
The state’s existing data infrastructure provides some foundation. The Healthplanfinder system connects to federal data hubs for income verification and immigration status. Expanding this infrastructure to verify work activity requires new data sharing agreements with the State Workforce Agency for wage records, educational institutions for enrollment verification, and potentially employers for direct work confirmation.
Automated verification through wage records will capture most full-time workers but misses gig economy participants, cash workers, and informal caregivers. These gaps are particularly significant in Washington’s diverse economy. Seattle’s tech sector employs many Apple Health members in contract or temporary positions that may not generate consistent wage records. Eastern Washington’s agricultural workforce includes seasonal workers whose employment patterns don’t align with monthly reporting cycles.
Cross-Program Coordination Potential#
Washington maintains SNAP and TANF programs with existing work requirements. H.R. 1 allows states to deem Medicaid requirements satisfied if individuals meet SNAP or TANF work requirements. This cross-program coordination could reduce verification burden, though the extent of overlap between programs varies.
The state’s WorkFirst program provides TANF employment services and has operated under federal work requirements for years. Infrastructure and staff expertise from WorkFirst could inform Medicaid implementation, though populations only partially overlap. TANF serves parents with dependent children, while Medicaid expansion includes many childless adults not eligible for TANF.
SNAP serves broader populations than TANF but narrower than Medicaid expansion. Cross-program data sharing through the state’s integrated eligibility system provides technical capability to identify members who satisfy both SNAP and Medicaid requirements. However, SNAP work requirements differ from Medicaid requirements in qualifying activities, hours, and exemption criteria. Perfect alignment is impossible without federal regulatory changes.
Tribal Sovereignty and Federal Exemptions#
Washington maintains government-to-government relationships with 29 federally recognized tribes. Federal law exempts tribal members from Medicaid work requirements, a recognition of tribal sovereignty and trust responsibilities. Implementing these exemptions requires coordination between state systems and tribal programs.
The Urban Indian Health Program serves Native Americans in Seattle and other urban areas who may not be enrolled in federally recognized tribes or whose tribes are not from Washington. Ensuring these populations receive appropriate exemption processing requires coordination between state systems and urban Indian health organizations.
Washington’s tribal populations access healthcare through a mix of Indian Health Service facilities, tribal clinics, and mainstream providers. The state has worked to improve Medicaid reimbursement for tribal healthcare and reduce administrative barriers. Work requirement implementation must preserve these gains while ensuring tribal exemptions function properly.
Managed Care Landscape and Financial Exposure#
Washington’s Medicaid managed care program contracts with multiple health plans across regions. Apple Health Managed Care serves approximately 2 million enrollees, including expansion adults subject to work requirements. These managed care organizations have financial stakes in membership retention.
Plans receive capitated payments per member per month. Work requirements create dual financial exposure. Plans lose premium revenue from members who lose coverage. Additionally, risk adjustment degradation occurs if healthier members navigate verification more successfully than members with complex conditions, leaving plans with sicker, more expensive risk pools.
The magnitude of this exposure depends on coverage loss rates and which members lose coverage. If Washington achieves low coverage loss through effective exemption processing and automated verification, MCO financial impact remains modest. If coverage losses approach higher projections, MCO financial stress could trigger contract renegotiation or market exit.
Plans have limited capacity to build member navigation infrastructure under current payment rates. Washington’s MCO contracts include care coordination requirements but don’t explicitly fund work requirement navigation. Whether MCOs receive additional payment for this function or are expected to absorb costs within existing rates remains undetermined.
Provider Tax and Payment Constraints#
Washington relies substantially on hospital and nursing facility assessments to finance its Medicaid program. The federal limit reduction from 6 percent to 3.5 percent of net revenue, phasing in from 2028, will significantly constrain state financing capacity. State-directed payment reductions will remove over $1.5 billion annually from hospital payments when fully implemented.
These fiscal pressures compound work requirement implementation challenges. The state budget must absorb federal funding losses while investing in new verification infrastructure. Governor Ferguson’s administration faces a $15 billion budget shortfall entering the 2025 legislative session, limiting capacity to backfill federal funding reductions.
Provider systems serving Apple Health members will experience dual pressure from reduced reimbursement and increased uncompensated care. Fourteen rural hospitals were identified at risk of closure from Medicaid cuts even before work requirements. Coverage losses will translate directly to uncompensated care increases for facilities already operating at the margin.
Geographic Variation in Compliance Capacity#
Washington’s geography creates vastly different compliance environments. Seattle and Puget Sound regions offer abundant formal employment, robust public transportation, and digital infrastructure. Eastern Washington faces sparser employment opportunities, limited transit, and broadband gaps. These variations mean identical federal requirements become fundamentally different challenges based on residence.
Yakima County’s agricultural workforce includes substantial seasonal employment that may not generate consistent wage records. Spokane’s service economy offers part-time positions that may fall short of 80 monthly hours. Rural counties across the state have limited formal employment opportunities outside healthcare, education, and government.
Federal exemptions for areas lacking sufficient employment may provide some relief, but qualification criteria remain undefined. Whether Washington will proactively identify high-unemployment areas and automatically exempt residents or require individual hardship demonstrations will significantly affect implementation burden.
Immigration Population Complexity#
Federal changes to lawfully present non-citizen eligibility will affect over 30,000 current Apple Health enrollees. Washington’s state-funded Apple Health Expansion program for undocumented immigrants provides alternative coverage but operates under enrollment caps due to budget constraints.
The state’s diverse immigrant and refugee populations present unique outreach challenges. King County alone is home to substantial Somali, Vietnamese, Chinese, and Latino communities. Each requires culturally competent, multilingual communications and trusted community intermediaries. The state’s community-based organization infrastructure provides potential capacity, but mobilizing these networks for work requirement compliance represents new territory.
Refugee populations arriving through federal resettlement programs face particular challenges. Many are learning English, navigating unfamiliar systems, and seeking employment in tight labor markets. Work requirements add another layer of complexity to already difficult transitions. Whether the state will build specialized navigation for refugee populations or expect mainstream systems to accommodate diverse needs remains unclear.
Expected Implementation Approach#
Washington will seek the federal extension waiver, positioning implementation for late 2028 at the earliest. This delay provides time to build automated verification systems, establish member navigation infrastructure, and potentially adapt to federal regulatory clarifications or policy reversals.
The state’s resistance posture shapes implementation approach. Washington will design systems to maintain coverage rather than maximize compliance enforcement. This means pursuing automated verification wherever possible, broadly interpreting exemption criteria, and investing in member support rather than punitive termination processes.
Verification systems will likely emphasize wage record matching through the State Workforce Agency, cross-program coordination with SNAP and TANF, and educational enrollment verification. Members who don’t appear in automated systems will receive outreach and navigation support before facing termination. The 30-day cure period provides buffer time for members to respond to notices and demonstrate compliance or exemptions.
Exemption determination processes will accommodate Washington’s diverse populations. Tribal exemptions will be automated through enrollment verification. Disability exemptions will accept self-attestation initially while medical documentation is gathered. Hardship exemptions will be broadly available for members facing barriers to compliance.
MCOs will receive implementation guidance from the Health Care Authority and will be expected to support member navigation through care coordination infrastructure. Whether MCOs receive additional payment for this function or are expected to absorb costs remains a point of negotiation. The financial calculations for MCOs will determine how aggressively they invest in member outreach.
The state’s rural hospital crisis creates urgency for Rural Health Transformation Program funding. Washington applied before the December 2025 deadline, positioning transformation grants as mitigation for coverage losses and payment constraints. If awarded, these funds could support telehealth infrastructure, workforce development, and care coordination systems that might indirectly support work requirement compliance.
Washington’s implementation will test whether resistance-posture states can minimize coverage losses through coverage-protective system design. The state has resources, technical capacity, and political will to build navigation infrastructure that other states may lack. Whether these advantages translate to substantially different outcomes than compliance-focused states remains an empirical question that Washington’s implementation will help answer.
The healthcare systems serving Washington’s diverse populations are preparing for implementation with uncertainty. Coverage losses will affect provider revenue and patient care regardless of how carefully the state designs systems. The gap between political commitment to coverage preservation and federal mandate compliance may prove unbridgeable, forcing Washington to choose between federal funding and state values. How that tension resolves will shape not just Washington’s implementation but potentially influence other resistance-posture states facing similar dilemmas.