A House committee questioned Oracle executives about a costly veterans’ health-records contract and whether veterans’ data could be used to train AI. Oracle executive Seema Verma said the company has no access to that data and does not use it; lawmakers raised concerns about privacy terms and the VA’s discussions with Oracle.
Oracle Watch analysis
What happened
FedScoop reports that Oracle co-CEO Mike Sicilia and executive vice-president Seema Verma appeared before the House Veterans’ Affairs Committee on 19 November. The hearing covered the Department of Veterans Affairs’ electronic health-record modernisation contract, whose ceiling has risen from $10 billion to $17 billion. Committee chair Mike Bost said the cost was more than $2,000 per veteran.
Lawmakers also challenged Oracle over possible use of veterans’ health data in AI systems. Verma said Oracle has “zero access” to the data and uses none of it for any purpose. Representative Nikki Budzinski pointed to Oracle sales terms that she said could allow the company to own the data. Mark Takano said the VA had described a “long and feisty” discussion with Oracle about data use. Those concerns are not proof that Oracle has accessed or used the records.
The executives said the contract increase reflected expanded scope and scale, pandemic delays, early customisation and inadequate infrastructure. Sicilia said Oracle would work with the VA to reduce costs. The company also said the next software version is included at no additional cost and referred to a clinical AI agent.
Why it matters
This is a live question about both public spending and the boundaries around sensitive health data. The hearing puts competing claims on the record: Oracle’s denial of access, lawmakers’ concerns about contract language, and the VA’s reported discussions with the company. For veterans, the distinction between data needed to deliver care and data available for commercial AI development is not a technicality.
The contract’s increase also makes oversight practical, not abstract. Lawmakers questioned the price, rollout and patient-safety figures, while Oracle defended the reasons for the expansion. A larger contract does not establish wrongdoing, but it raises the stakes for clear costs, delivery milestones and enforceable data protections.
Our read
The most important point is that the committee heard a direct denial from Oracle alongside specific concerns from lawmakers about the terms and the VA’s negotiations. Neither side’s account settles what the contract permits. The useful next step is documentation: what the contract says about data, what the VA agreed to, and what oversight can verify. “Trust us” is a thin substitute for clear rules when public money and medical records share a room.
What to watch
- Whether the VA or Oracle publishes clearer details of the contract’s data-use terms.
- Whether lawmakers seek a cost estimate, deployment schedule or further records, as Representative Abe Hamadeh called for.
- Whether the VA provides measurable progress on the rollout and patient-safety issues raised at the hearing.
Discussion spark: Should Oracle have any route to use veterans’ health data for AI development if the VA approves it, or should that data remain off-limits to contractors altogether?
Sources and evidence
- Source update (19 November 2026, 22:49 UTC)
Independent WittyWires tracker for public updates about Oracle. Not affiliated with or endorsed by Oracle; this is not an official account.