Former U.S. CTO calls out Epic Systems

Video thumbnail: Former U.S. CTO calls out Epic Systems
Nov 19, 20262m 30s video lengthSTAT

The Signal

A recent health conference highlighted a sharp dispute between a former HHS chief technology officer and a representative from Epic Systems—the dominant electronic health record provider—over the nature of a VA scheduling arrangement. The conflict centers on whether this deployment represents harmful vendor lock-in via proprietary standards or a high-value, VA-selected innovation that has demonstrably accelerated patient access.

The Case

The Scheduling Dispute

  • A former HHS CTO—the agency’s former top tech advisor—criticized a VA scheduling implementation as a “vendor-brokered” system using proprietary standards, warning that this structure prevents the agency from switching vendors.1:02
  • Epic’s representative countered that the VA selected the vendor itself and asserted that the feature allows veterans to secure appointments weeks faster than they otherwise could, though provided no data to back this claim.1:28
  • Both parties clashed over the definition of the arrangement, with the critic characterizing it as a lock-in risk and the Epic representative defending it as a beneficial deployment, while admitting the VA pays “a lot of money” for it.

Broader Integration Allegations

  • The exchange followed separate, wider allegations from third-party app developers who claim Epic makes it harder than necessary for external software to integrate with its records system.0:10
  • Although the reporter attempted to raise these broader concerns during the conference, the discussion remained limited to the specific VA scheduling case study.
  • The reporter stated that Epic had not commented on these specific allegations prior to the conference, and the company did not engage with the substance of those broader complaints during the public exchange.

The 1 Minute Signal Take

This standoff illustrates the persistent tension between proprietary EHR systems and the demand for open, interoperable standards that would facilitate vendor switching. While both sides claim to support open standards in theory, the current lack of transparency regarding specific procurement processes and performance metrics leaves the reality of these integration hurdles and their supposed benefits unproven.

Pro Analysis

Why It Matters

The dispute over VA scheduling represents the broader conflict between the health tech ecosystem's need for interoperability and the market incentives that drive proprietary lock-in. When a government agency relies on a vendor-controlled standard, it forfeits the ability to adapt as technology evolves or as service needs change.

Strategic Implications

For health organizations, relying on vendor-specific scheduling or integration standards creates a significant strategic risk. The ability to "swap out" a vendor is a foundational requirement for any large-scale infrastructure, yet the industry currently lacks a clear enforcement mechanism for open standards.

Evidence & Hype Audit

This content is low on independent evidence. Both the critic (the former HHS CTO) and the defender (the Epic representative) provide assertions without supplying technical documentation, procurement contracts, or appointment-time data. It functions more as a public airing of a grievance than an analytical review of the software architecture.

Counterarguments

One could argue that focusing on open standards risks sacrificing immediate patient benefits. If a proprietary "smart scheduling" feature is the only technology capable of providing rapid appointment access today, forcing an open standard might actually degrade performance until the market matures.

Who Should Care

  • Health System IT Leadership: To evaluate whether current scheduling implementations create hidden lock-in risks.
  • Healthcare Policy Advocates: To track the efficacy of open-standard mandates in public procurement.
  • App Developers: To understand the ongoing challenges of scaling integrations within dominant EHR ecosystems.

What To Do Next

  • Conduct a gap analysis between existing proprietary scheduling standards and emerging open-source interoperability protocols.
  • Review procurement contracts to explicitly define vendor-switching rights and data portability requirements.
  • Require that any future vendor-brokered implementation includes clear benchmarks for comparing service delivery performance.
  • Support independent benchmarking of appointment-time improvements to validate vendor claims.

Share this

Written by: 1 Minute Signal Editorial Team