Epic Systems’ executives took the stage at the HLTH conference and directly addressed recent scrutiny of the company’s market practices. The executives defended Epic against allegations of anticompetitive conduct reported in a prior STAT investigation, saying the company is working to build a more open ecosystem for third-party developers. The panel exchange was moderated by a STAT reporter; the source reported the company’s remarks but did not include a full transcript of the discussion.
Seth Howard, Epic’s executive vice president of research and development, said the company received roughly 75,000 inquiries last year from organizations seeking to tap into its systems. Howard also cited that Epic’s platforms hold records on more than 280 million Americans, using those figures to explain why the vendor could not create bespoke integrations for every request. The company framed those operational constraints as practical limits — not as an exclusionary policy — and presented them as the rationale for offering standardized access routes instead of one-off connections.
Company leaders told the audience they would make it easier for vendors to allow artificial intelligence to read data stored on Epic systems. They pointed to open.epic, Epic’s publicly listed application programming interfaces (APIs), and said that the list is available to anyone. The executives characterized their responsibility as enabling the market — patients and health systems — to choose which applications connect to their data. The source did not report detailed technical steps, timelines, or specific new API endpoints that Epic plans to release, nor did it report contractual or commercial changes tied to the pledge to ease AI access.
The STAT investigation referenced by the panel alleged that Epic had been selectively withholding data access needed by rival application developers, a practice the investigation suggested undercut competition. At the HLTH panel, Epic’s executives responded directly to those allegations and rejected the characterization presented in the earlier STAT reporting. They told attendees they are seeking to open the ecosystem amid a surge of integration requests. The source article recounted that exchange and quoted company leadership, but it did not reproduce the investigation’s full findings or provide independent verification of Epic’s rebuttal beyond the executives’ statements.
The article noted several concrete claims from Epic — the 75,000 inquiry figure, the >280 million records assertion, and the availability of open.epic — but stopped short of documenting implementation specifics. The source did not report technical timelines for expanded AI access, nor did it report how Epic will address claims that it had previously favored certain partners. The story also did not include responses from regulators, competing vendors, or customers verifying that access changes will follow. STAT’s coverage of the panel is partially gated behind a STAT+ paywall; the publicly available article summarized the remarks but did not provide exhaustive detail.
Those gaps leave practical questions for clinicians, developers, and health systems. How will Epic operationalize broader read access for AI models? Will there be changes to authentication, data-use agreements, or pricing? What safeguards will Epic require to govern downstream model behavior with patient data? The source did not provide answers to these operational and policy questions.
The reporting anchored the exchange in specific, attributable statements from Epic leadership at a public conference and cited metrics provided by the company. Beyond those attributions, the article did not invent technical or contractual specifics; it explicitly lacked further granular details about execution and did not report any new regulatory actions or third-party confirmations tied to Epic’s pledge.
Limitations recorded in the source are straightforward: the STAT article summarized Epic’s public remarks at HLTH and referenced a separate STAT investigation but did not publish a verbatim transcript, technical road map, or vendor and regulator responses. Readers interested in deeper, proprietary, or technical follow-up will need to consult the STAT+ version or seek additional reporting that captures vendor road maps, developer experiences, and regulatory scrutiny in more detail.