What states getting Medicaid H.R.1 right are doing differently

Across states, success under H.R.1 is tied to engineering discipline — not documentation or procurement volume.

Clear separation of core and edge is non negotiable

The most consistent pattern is a firm separation between systems of record and systems of execution. Core eligibility and Medicaid Management Information System (MMIS) platforms are protected and stabilized. Policy logic, verification workflows and citizen interaction are handled elsewhere, in layers designed to change.

This separation allows states to respond to evolving guidance without destabilizing foundational systems or triggering months of rework.

Speed comes from configurability, not customization

States getting H.R.1 right treat rules as configurable assets. Eligibility and verification logic can be adjusted quickly, tested automatically and deployed incrementally.

By contrast, states reliant on custom code move slower with every change. Each update requires revalidation, procurement or manual intervention — compounding risk over time.

Accountability replaces handoffs

Successful states reduce fragmentation. They rely on fewer, more integrated partners and establish clear ownership across policy, technology and operations. This end to end accountability shortens decision cycles and limits the delays that often derail compliance timelines.

Handoffs are where speed goes to die.

Compliance works only if it works for people

Another defining trait is journey first design. States that map real citizen and caseworker experiences catch problems early — before compliance logic collides with operational reality.

These states also treat operational support as part of the solution. Call centers, outreach, training and ongoing support are designed alongside system changes, not bolted on after go live.

Continuous delivery beats heroic delivery

Finally, the strongest performers release continuously. They align incremental changes to federal deadlines and adjust as guidance evolves. Large, monolithic implementations consistently underperform in environments where policy keeps moving.

Iteration is not a sign of immaturity. It is a sign of readiness.

The line H.R.1 is drawing

H.R.1 is not just another mandate. It is exposing whether states have built Medicaid operating models designed to change — or whether they are still relying on accumulated workarounds to survive volatility.

The states getting H.R.1 right are not documenting faster or working harder. They are engineering differently. And that distinction will matter long after this mandate is met.