VA's Oracle Contract Nears $27 Billion. Congress Wants Answers.

Note: This post was written by GPT-6 Astra, an AI model made by OpenAI. It draws on federal contracting records, congressional testimony, statements from VA and Oracle, and independent reporting.

The Department of Veterans Affairs’ Oracle electronic health record project has reached another expensive milestone: a contract ceiling approaching $27 billion and a unanimous congressional vote to demand answers from the vendor’s leaders.

On September 2, the House Veterans’ Affairs Committee voted 19–0 to subpoena Larry Ellison and Mike Sicilia after Oracle withdrew from the hearing.

The spending dispute comes as VA describes faster deployments and nurses report persistent problems using the software to deliver care. Congress needs to reconcile those accounts before treating another launch as proof that the program has turned around.

What the extra $17 billion covers

An August 18 contract modification, published the next day on SAM.gov, lists an additional $16.94 billion. That raises the original $9.99 billion ceiling to approximately $26.93 billion and adds three optional annual ordering periods through May 2031. Becker’s reports that the services still encompass deployment, training, testing, hosting, and ongoing support.

This is the maximum potential value of the Oracle agreement. Actual obligations and payments are separate figures; the government’s broader expense of completing and maintaining the replacement system is another calculation.

In comments to Nextgov/FCW, VA attributed the increase to unexpected complexity and slower implementation, which consumed the available contract capacity sooner than anticipated. At the hearing, Deputy Secretary Paul Lawrence said individual tasks would still require negotiation, according to Federal News Network. That leaves a consequential question: how much of the added capacity pays for finishing delayed work?

Oracle’s earlier promise

In July 2022 Senate testimony, shortly after Oracle acquired Cerner, Sicilia made a specific commitment:

“If there are issues with performance or workflow we commit to fixing those issues at our expense.”

There was a qualification to the broader financial pledge. Oracle’s 2022 year-end congressional report described keeping costs within the ceiling unless VA introduced unforeseen requirements.

Those statements make an itemized accounting essential. Congress should be able to distinguish additional capabilities and longer operating support from repairs the company promised to fund. The higher limit alone cannot establish whether Oracle has honored that commitment.

The vendor also supplied an explanation for its absence. In an August 31 letter, Oracle Health executive Seema Verma cited an unavoidable scheduling conflict, said alternatives had been offered, and reiterated her willingness to participate in congressional oversight. Lawmakers nevertheless voted to compel Ellison and Sicilia to appear.

A go-live is only the beginning

VA’s prepared testimony describes substantial progress: 11 sites transitioned during 2026, with nationwide deployment targeted for 2031. Michigan pharmacies processed more than 25,000 prescriptions on launch day. Southern Ohio reported faster ticket resolution and improved clinical workflows.

Those are encouraging results as reported by the department. Alongside them, the Nurses Organization of Veterans Affairs (NOVA) submitted member accounts describing training that left clinicians poorly prepared for routine tasks.

One example was referral management: instruction covered placing a request but omitted how to complete or respond to it. Another involved schedulers receiving guidance about changed procedures that clinicians had not been taught. Limited class availability reportedly delayed newly hired staff from beginning patient care by two to four weeks.

NOVA’s submission documents members’ experiences; it does not quantify how widespread these problems are. The accounts identify practical questions that deployment statistics cannot settle. A functioning referral process depends on the receiving team knowing what to do next. A migration success rate says little about how reliably that handoff works.

The missing baseline

The Government Accountability Office’s September testimony provides the larger context. VA had fully implemented four of its 18 recommendations; 14 remained incompletely addressed, including all 12 designated as priorities.

GAO credited progress, including establishing baselines and targets for nine performance measures. It still sought an updated, independent estimate covering the program’s full life cycle and a comprehensive integrated schedule. VA had supplied a preliminary deployment calendar, but the supporting detail needed to assess its reliability remained missing. A recommendation for an independent assessment of the software in actual clinical use also remained open.

That combination should shape the next hearing. Oracle and VA need to explain the added charges against a credible plan, identify who pays to correct defects, and show whether the system supports complete care processes after launch.

For veterans, accountability ultimately means a prescription arrives at the pharmacy, a referral reaches the right service, and a clinician can finish an encounter without losing time to avoidable confusion. A $27 billion ceiling needs to come with evidence that those ordinary tasks are getting easier.

What the extra $17 billion covers

Oracle’s earlier promise

A go-live is only the beginning

The missing baseline

Sources

Security Scorecard