Skip to main content
  1. Medicaid Work Requirements/
  2. Implementation Infrastructure/

Summary: Series 2 Synthesis: The Three Infrastructures

·751 words·4 mins
Author
Syam Adusumilli
MPH, Brown University. 33 years in healthcare systems, policy, and technology. Writes across rural health transformation, Medicare policy, and Medicaid work requirements.

Arkansas spent millions on verification technology and lost 18,000 people to coverage in ten months. Georgia spent nearly $100 million on systems and enrolled 6,500 against a 50,000 target. Both states built technical infrastructure. Neither built the complete system that technical infrastructure requires to function. The Series 2 trilogy reveals that work requirements implementation demands three distinct but interdependent infrastructures: technical architecture for verification (MRWR-2A), policy architecture for exemptions (MRWR-2B), and human architecture for navigation (MRWR-2C). States that build all three create systems where people can comply. States that build only one or two create systems where compliance becomes structurally difficult regardless of individual effort.

The central tension threading through all three articles is whether systems are designed to recognize existing compliance or to police potential non-compliance. This is not a technical distinction. It is a philosophical choice that determines every operational decision.

Recognition logic builds infrastructure to find work that is already happening. Ohio data-matched two-thirds of their population through existing wage databases and exempted them from active reporting. Recognition-based exemption systems use administrative data to automatically identify qualifying conditions, triggering review without requiring individual initiation. Recognition systems need less human intervention because technology identifies most compliance and exemptions automatically. Navigation focuses on edge cases and genuine complexity.

Compliance logic assumes non-compliance until proven otherwise. Arkansas required monthly reporting with coverage termination for missed deadlines. Compliance-based exemption systems require individuals to initiate requests, gather documentation, and navigate bureaucratic processes. Compliance systems need extensive human infrastructure because technology creates barriers that humans must help overcome. Navigation becomes remediation for system-generated obstacles.

The synthesis identifies a critical paradox: exemptions designed to protect people often create barriers that the qualifying conditions prevent people from overcoming. Medical frailty exemptions require documentation from healthcare providers, but the conditions qualifying for medical frailty (serious mental illness, substance use disorders, cognitive disabilities, chronic homelessness) impair the capacity to maintain stable provider relationships and navigate multi-step bureaucratic processes. Caregiver exemptions require proving care responsibilities, but informal caregiving through kinship networks produces minimal documentation. The populations most likely to provide informal care face the highest documentation barriers.

This paradox produces a design principle with immediate fiscal implications: exemption design and human infrastructure requirements are inversely related. Accessible exemptions (automated identification, presumptive eligibility, low documentation burden) reduce navigation needs. Rigorous exemptions (high documentation standards, individual initiation, frequent renewal) dramatically increase them. States claiming they will protect vulnerable populations through robust exemptions while building minimal human infrastructure are making incompatible commitments.

The synthesis maps four distinct failure modes that emerge when the three infrastructures misalign. Sophisticated verification technology with inaccessible exemptions and minimal navigation loses working people with complex employment patterns and vulnerable people who qualify for exemptions but cannot document them. Accessible exemptions with weak verification technology and minimal navigation loses workers with episodic employment who do not neatly fit exemption categories. Strong technology and accessible exemptions but inadequate human infrastructure produces good overall retention but systematically excludes the 10-15% with genuinely complex situations. Extensive human infrastructure supporting weak technology and inaccessible exemptions creates geographic inequality, navigator exhaustion, and coverage losses concentrated among populations without navigation access.

The fiscal interdependence across infrastructures is the synthesis’s most actionable finding. Recognition-based verification (MRWR-2A) reduces exemption processing volume (MRWR-2B) and navigation caseloads (MRWR-2C). Accessible exemptions reduce navigation burden. Adequate human infrastructure reduces the need for perfect technical systems. But the reverse is also true: compliance-based verification increases exemption volume and navigation demand. Rigorous exemptions overwhelm navigation capacity. Minimal human infrastructure necessitates automated recognition systems that most states have not built.

For state Medicaid directors, the trilogy demonstrates that technical infrastructure choices made in isolation from human infrastructure realities produce predictable failures. Directors must budget human infrastructure proportional to verification complexity and exemption rigor. For MCO executives, the verification technology states build determines care coordination requirements, and plans should advocate for state choices that reduce documentation burden on members. For community organization leaders, the trilogy confirms both their essential role and their impossible position: essential because technical systems cannot handle complexity, impossible because funding is inadequate and responsibility for failures they did not create falls on them. For federal policymakers, verification rigor, exemption accessibility, and human infrastructure investment are not independent variables to be set separately but interdependent system components that must be designed together.

The system functions at the level of its weakest infrastructure component. That outcome is neither philosophically necessary nor operationally inevitable. It is the predictable result of building incomplete systems and expecting people to navigate gaps that infrastructure design created.