What 50 States Taught Me About Medicaid
There’s a moment that happens when you study something long enough.
At first, it’s all details.
Eligibility categories. Income limits. Waivers. Acronyms stacked on acronyms.
But eventually, the details start to blur—and patterns come into focus.
That’s where I found myself at the end of this series.
Because this was never just about learning Medicaid.
It was about understanding what kind of system we’ve built—and who it’s actually built for.
The Pattern I Couldn’t Unsee
Across state after state, one thing became impossible to ignore:
Disability Medicaid is still fundamentally punitive.
Not in one place.
Not in a few outlier states.
Almost everywhere.
To qualify through a disability pathway, people are still expected to:
Prove they cannot work (often repeatedly)
Stay under strict income and asset limits
Navigate complex, fragmented systems
Endure long waiting periods and frequent re-verification
And even then—approval isn’t stability.
It’s conditional.
It’s monitored.
It can be taken away.
There’s a quiet but consistent message embedded in these systems:
Support is available—but only if you remain limited enough to deserve it.
That’s not accidental.
That’s design.
When Support Requires Scarcity
One of the hardest truths in this work is this:
In many states, the path to care is still tied to proving deprivation.
Not just need—but lack.
Lack of income.
Lack of assets.
Sometimes even lack of progress.
And that creates a system where people are forced into impossible trade-offs:
Work more → risk losing coverage
Save money → risk losing eligibility
Improve stability → risk losing support
This is what people call “benefits cliffs.”
But it’s deeper than that.
It’s not just a cliff—it’s a structure that often requires people to stay at the edge of it.
What Happens When Systems Don’t Evolve
In states that continue to treat Medicaid as a minimal safety net—rather than a core system—the consequences are visible.
Not abstract. Not theoretical.
You see it in:
Provider shortages and care deserts, especially in rural areas
Hospital instability and closures, where reimbursement gaps stretch systems past their limits
Maternal and infant health outcomes, where inconsistent coverage and access directly shape survival
Long waitlists for home and community-based services, leaving families to fill impossible gaps
These aren’t isolated failures.
They’re downstream effects of policy choices that haven’t kept pace with reality.
When systems remain fragmented, outdated, or intentionally restrictive, the burden doesn’t disappear.
It shifts.
Onto patients.
Onto families.
Onto already strained providers.
And Yet—Some States Feel Different
At the same time, there was another pattern.
Because not every state felt the same.
In some places, something shifted.
Coverage extended more intentionally.
Programs were designed to work together instead of against each other.
Administrative processes were simpler—or at least more navigable.
And when that happened, Medicaid started to feel different.
Not perfect.
Not even always equitable.
But more…functional.
More stable.
More like infrastructure.
What Intentional Design Actually Changes
When a state builds Medicaid with intention, you can feel it.
It shows up in things like:
Broader eligibility pathways (especially for families and children)
Better integration with public health systems
More continuity of coverage
Fewer administrative drop-offs
Stronger provider participation
And the impact isn’t abstract.
It changes whether people can:
See a doctor without waiting months
Maintain consistent treatment
Stay employed (or return to work)
Care for their families without constant disruption
In those states, Medicaid isn’t just a safety net.
It’s part of the foundation.
But “Better” Isn’t the Same as “Finished”
Even in the strongest states, the system is not complete.
You can have:
Expanded coverage
Strong family programs
Integrated care models
And still have:
Disability pathways that require poverty to qualify
Asset limits that prevent long-term stability
Administrative systems that still assume constant compliance capacity
That contrast is striking.
It means that even where Medicaid is functioning well, it is still unevenly designed.
Still carrying older assumptions about disability, work, and worthiness.
Still asking some people to stabilize—while asking others to remain precarious.
Fragmentation vs. Infrastructure
By the end of this series, this became the clearest dividing line:
Some states treat Medicaid like a patchwork of programs.
Others are starting to treat it like public infrastructure.
And that distinction matters.
Because fragmented systems:
Shift the burden onto individuals
Require persistence, literacy, and time to navigate
Break down easily under stress
While infrastructure systems:
Absorb complexity instead of exporting it
Create continuity instead of disruption
Work with people’s lives, not against them
What This Series Changed for Me
Before this, I understood Medicaid as policy.
Now, I understand it as architecture.
A system that quietly shapes:
Who gets to stabilize
Who has to fight to stay covered
Who can build a life—and who has to constantly prove they deserve one
And once you see that, it’s hard to unsee.
Where This Leaves Us
If there’s one thing I’m taking forward from this series, it’s this:
Medicaid works best when it’s built like infrastructure—and breaks down when it’s built like a test.
A test of persistence.
A test of limitation.
A test of worthiness.
We already have examples of states moving in a different direction.
But even the strongest systems are still in progress.
And the weakest ones are showing us, in real time, what happens when systems fail to evolve.
The question isn’t whether we can build something better.
It’s whether we’re willing to build systems that assume people deserve stability—without requiring them to sacrifice it first.
And maybe the most honest question this series leaves me with is this:
If Medicaid is this uneven—this conditional—
what support do disabled people actually have?
That’s where I’m going next.
