Optum Seeks Dismissal of Maryland's $380 Million Medicaid Fraud Suit Over Failed Claims System

Optum wants a Maryland fraud lawsuit thrown out before it ever reaches a jury, and the company's argument is straightforward: the state already had remedies for exactly this kind of failure, used them repeatedly, and is now trying to relitigate a deal gone sour as a fraud case.

The underlying dispute centers on a computer system Optum built to manage Maryland's Medicaid behavioral health program. According to the state's original complaint, filed by Attorney General Anthony Brown in August, the system crashed on its first day of operation and "never functioned properly" afterward. The failure was severe enough that Maryland took the system offline for eight months in 2020, putting service access at risk for 1.5 million Medicaid enrollees.

That is not a minor technical hiccup. It is a sustained operational failure in a program that serves some of the state's most vulnerable residents, people seeking mental health and substance abuse treatment through Medicaid. Brown's office says the broken system denied legitimate claims, made incorrect payments to providers, and failed to catch what the lawsuit describes as "rampant, multi-million-dollar fraud."

The contract ran from 2019 to 2024. Maryland paid Optum $126.9 million to manage its Administrative Services Organization program over that period. The state now claims the technology issues cost it "tens of millions of dollars" beyond the contract price, and it's seeking roughly $380 million in damages, triple the contract value, under Maryland's False Claims Act. The complaint also alleges breach of contract and intentional misrepresentation.

The Core Legal Dispute

Optum's motion to dismiss, filed in October, reframes the entire narrative. The company says the problems the state is complaining about were "resolved years ago on the terms the State itself drafted." Both sides knew going in that the implementation would be complicated, Optum argues, and the contract reflected that reality with built-in mechanisms: tools to manage the transition, adjust payment based on Maryland's own performance assessments, and impose remedies if Optum fell short.

Crucially, Optum says Maryland actually used those tools, multiple times, over the life of the contract. That is a meaningful detail. If the state had contractual remedies available and exercised them repeatedly, it becomes harder to argue later that the company's conduct rose to the level of fraud rather than an underperforming vendor relationship managed through normal contractual friction.

Optum's framing is blunt: having already extracted concessions through contract-based remedies, the state is now trying to "extort additional penalties" by dressing up a commercial dispute as fraud. A company spokesperson told Fierce Healthcare the lawsuit "is inaccurate and misleading in its attempt to transform what is fundamentally a contract dispute into allegations of fraud." The spokesperson added that the AG's office "overlooks Optum's sizeable commitment and investment to provide a high standard of compliant services for the State."

That distinction between contract dispute and fraud is not just semantic. It determines which legal standard applies, what damages are available, and whether treble damages under the False Claims Act are even on the table. Fraud claims require evidence of intentional deception or reckless disregard for the truth, a higher bar than simple underperformance against contractual benchmarks. Optum's strategy is to keep this fight on contract-law turf, where its drafted-and-exercised remedy provisions give it a defensible position. Maryland's strategy is the opposite: to establish that the system's failures were not just bad execution but a deliberate or reckless misrepresentation of what the company could deliver.

One detail worth flagging from the original complaint: the state alleges that in the final months before rollout, Optum swapped its own proprietary claims management system for one built by a subcontractor, and that this replacement system was "inadequately tested" and "inadequately vetted." If that allegation holds up, it strengthens Maryland's fraud theory because it suggests a known, last-minute substitution rather than an unforeseeable implementation snag. Optum's motion does not appear to directly rebut that specific claim in the public filing summary, which leaves it as a potential vulnerability in the company's otherwise contract-centric defense.

Optum has also pushed back on scope. A spokesperson emphasized that the contract was directly between Optum and the state, separate from UnitedHealthcare's Medicaid managed-care business in Maryland. That distinction matters for reputational containment. UnitedHealth Group, Optum's parent, already faces scrutiny on multiple fronts, and keeping this dispute siloed to a single administrative-services contract limits the narrative spillover into the broader managed-care business.

The Bottom Line

This case is a useful marker for how healthcare technology failures get litigated when the stakes involve public health programs and taxpayer dollars. Maryland is not just alleging a vendor underperformed, it's alleging the underperformance was fraudulent and that the state's affected population, 1.5 million Medicaid enrollees who rely on behavioral health services, bore real consequences during an eight-month outage.

For Optum and UnitedHealth, the motion to dismiss is a calculated bet that contract language drafted years ago will insulate the company from fraud exposure, even if the underlying system failure was severe. If the court agrees that Maryland's own contractual remedies were the exclusive recourse, the $380 million fraud claim could collapse into a much smaller contract dispute. If the court instead finds enough evidence of intentional misrepresentation, particularly around the undisclosed subcontractor swap, Optum faces a far costlier outcome and a reputational problem that extends well beyond Maryland.

Either way, this case sets a precedent worth watching for any company selling critical infrastructure software into state Medicaid programs. Contracts with built-in remedy provisions are standard risk management. Whether they double as liability shields against fraud claims is now a question for a Maryland court to decide.