H.R.1 exposes Medicaid’s execution and compliance gaps

Systems built for stability are being forced into motion

Most Medicaid core platforms were engineered to be stable systems of record. Eligibility systems, Medicaid Management Information System (MMIS) platforms and customer relationship management (CRM) tools excel at maintaining data integrity, enforcing established rules and processing volume reliably. They were not designed to absorb frequent rule changes, shifting guidance or policy logic that must be toggled on and off across programs and populations — especially under hard deadlines that do not flex to system constraints.

Under H.R.1, those limitations are becoming visible. States are stretching core systems far beyond their intended purpose, layering customizations, point integrations, scripts and manual processes to keep up — often in compressed timeframes that limit testing, iteration and coordination across teams. Over time, this creates brittle environments that are difficult to test, slow to modify and costly to maintain.

In many programs, the system technically “works” — but only because staff compensate for its limitations. Eligibility workers reconcile data across programs manually. Policy teams rely on offline analysis to answer basic questions. Operational knowledge lives with individuals rather than being embedded in systems. What looks like modernization on the surface often masks an operating model held together by human effort — an approach that becomes significantly harder to sustain when requirements must be met on a recurring, time-bound basis.
 

One off compliance is becoming the norm — and the risk

H.R.1’s specificity is pushing states toward bespoke fixes. Each new requirement spawns a narrowly scoped solution layered on top of standardized systems. Individually, these fixes seem pragmatic. Collectively, they increase long term cost, operational risk and vendor sprawl, particularly when timelines force rapid, one-off implementations rather than deliberate, scalable design.
 

Compounding the problem, compliance work is competing directly with modernization, operations and citizen experience improvements — often using the same limited staff and funding. When federal guidance evolves, as it inevitably does, rigid solutions magnify the cost of change. Updates require reconfiguration, new procurement or extended testing cycles that simply do not align with federal timelines or the expectation of ongoing, time-based compliance.
 

The result is an execution model optimized for continuity, not adaptability.
 

The real issue is not policy — it’s operating design

At its core, H.R.1 is exposing the limits of an industry model optimized for efficiency of record instead of speed of execution at the edge. States are not struggling because they lack commitment or capability. They are struggling because the systems and operating models they inherited were never designed for this level of sustained policy volatility combined with recurring, deadline-driven execution.
 

This distinction matters. If H.R.1 is treated primarily as a policy or documentation exercise, states will continue to accumulate cost and risk through incremental workarounds. If it is recognized as an execution challenge — one defined as much by timing as by policy complexity — it creates an opportunity to rethink how Medicaid operations absorb change — now and in the future.

H.R.1 is not an anomaly. It is a signal. A signal that compliance is no longer episodic, but continuous and time-bound. And the states that respond by strengthening execution — not just compliance — will be better positioned for what comes next.