Senate Pressure Mounts Over Medicaid Eligibility Systems Built on Years of Workarounds
Three Democratic senators are pressing the federal government to impose tougher standards on the companies that build and run Medicaid eligibility systems, warning that the next wave of enrollment changes will collide with software already known for costly failures. Their demand lands at a moment when states are being forced to overhaul computer platforms on a compressed timeline, while millions of beneficiaries face more frequent verification and new work-related reporting requirements.
The political fight centers on a deceptively technical question: who is responsible when a public benefits system fails? In Medicaid, the answer can decide whether a person keeps access to doctor visits, prescriptions, dialysis, cancer treatment, or disability-related care. When eligibility systems break down, the harm is not abstract. It can translate into wrongful disenrollment, delayed renewals, and days or weeks without coverage.
Contractors Run the Backbone of Enrollment, While States Carry the Formal Responsibility
Most states rely on private contractors to build or operate the computer systems that determine who qualifies for Medicaid. A smaller number of states run those systems directly. Deloitte, General Dynamics Information Technology, Gainwell Technologies, and Conduent are among the companies paid billions in taxpayer dollars to manage this work, and one company, Deloitte, has emerged as a dominant player in this slice of government business.
Baseline architecture in many states is already brittle. Eligibility platforms have been built, patched, and revised over decades, creating systems with layers of old code, partial fixes, and policy rules that do not always fit together cleanly. When those systems are asked to process more complex rules, the risk of error rises quickly. A small coding mistake can cascade into a broader eligibility failure, especially when millions of enrollees are being funneled through the same portal, renewal pipeline, or automated notice process.
The senators’ new report argues that administrative errors in this setting carry consequences unlike those in ordinary commercial software. A missed field, an incorrect calculation, or a flawed renewal notice can end with a person losing Medicaid even when they remain eligible. For patients with chronic illness, pregnancy-related care needs, or disability-related exemptions, the stakes are immediate and personal.
One line in the report lands with unusual force.
“Administrative errors in this line of work are not like errors in other fields.”
New Work Rules Raise the Risk of Improper Coverage Loss
The immediate pressure comes from Medicaid changes under President Donald Trump’s signature tax and domestic policy law, which added new restrictions and paperwork requirements. For the first time, the program will impose federally mandated work requirements. Next year, millions of adult enrollees in more than 40 states will have to prove they are working, or doing an equivalent qualifying activity, for at least 80 hours a month unless they qualify for an exemption.
That kind of rule is operationally demanding even in a system with clean data and modern infrastructure. In the Medicaid environment described in the report, it becomes far more precarious. States must verify employment or activity status, process exemptions, recheck eligibility every six months, and do it through systems that have already produced errors in the past. Each extra step creates another opportunity for a legitimate enrollee to be dropped from coverage because a form was not uploaded correctly, a portal malfunctioned, or a contractor-built interface misread the data.
The senators warned that new red tape layered onto old technical weaknesses will lead to large numbers of people improperly losing health coverage. Their concern is not merely that systems will frustrate applicants; it is that the systems will misclassify people who should remain covered. In a program serving low-income people and people with disabilities, that distinction determines whether care is reachable at all.
Democrats Want Public Contract Rules, Performance Data, and Change Orders
Sen. Ron Wyden of Oregon, Sen. Elizabeth Warren of Massachusetts, and Sen. Raphael Warnock of Georgia want the Centers for Medicare & Medicaid Services to do more than monitor systems after the fact. They are urging the agency to establish mandatory standards for state contracts with Medicaid eligibility vendors, publish the contracts and amendments, and disclose performance data and change orders.
Those changes would matter because states and contractors do not operate in a fully transparent environment. Contract amendments can expand the scope of work, shift costs, or reflect repeated fixes to systems that were supposed to be stable in the first place. Change orders are often used when the original design no longer matches policy needs or when software defects require added work. The senators say the public should be able to see where the money is going and how often systems need rescue.
Federal financing gives Washington leverage. The government covers 90% of the cost of developing and implementing state Medicaid eligibility systems and 75% of ongoing maintenance and operations. Even so, the lawmakers say the approval process has not produced enough accountability from the firms that build the technology.
Contractors Say States Make the Final Call, but the Design Still Shapes the Outcome
The companies responded by emphasizing that states, not private vendors or automated systems acting alone, make the final eligibility decision. Deloitte said state workers approve or deny eligibility. The firms also rejected the idea that they have a financial incentive to remove people from Medicaid. Conduent said it gets paid less if enrollment drops.
Those answers do not resolve the core problem. A system can still be deeply influential even if a human signs the final notice. In practice, software determines what a caseworker sees, which cases get flagged, which applicants are told to submit more paperwork, and which households are routed into appeal or termination workflows. If the front-end logic is flawed, the state employee may be approving or denying eligibility based on contaminated data.
The companies also did not provide the senators with detailed information about the documents or internal processes they use when helping states make eligibility determinations. That gap is important because transparency is the only way to judge whether a contractor is catching mistakes early or merely passing them along until they become coverage terminations.
CMS Has Some Oversight Tools, but Enforcement Has Been Rare
CMS already checks certain metrics when certifying state systems. Those include whether states are correctly calculating income, whether eligibility decisions are timely, and whether categories are assigned accurately. Yet the federal government rarely withdraws funding when states fall short.
CMS has now said it intends to develop standards for Medicaid systems. The agency said the goal is to improve enrollees’ access to care and their experiences with these systems, while also pushing companies to deliver platforms that can adapt to policy changes more reliably. The language suggests federal officials understand the scale of the problem, but the path from intention to enforcement remains narrow.
The scale of the program makes the issue hard to dismiss. As of June, 66 million people were enrolled in Medicaid. For them, a technical failure is not a back-office inconvenience. It is a missed refill, an unpaid hospital bill, a cancelled appointment, or a letter saying coverage ended when it should have continued.
The senators’ report puts CMS on notice at a moment when Medicaid systems are being asked to do more, faster, and with less room for error. The unanswered question is whether the federal government will set binding rules before the new enrollment burden starts pushing fragile systems past their limits.