Even though ChatGPT for Healthcare can now integrate with Epic, health system leaders told Becker’s that generative AI does not get closer to the medical record unless its output can be traced, checked, and audited against the chart and a clinician’s own judgment, setting a high bar for CIOs trust ChatGPT Epic integration decisions across the industry.
What OpenAI’s Epic Integration Actually Offers Behind This CIOs Trust ChatGPT Epic Integration Question
OpenAI announced Sept. 1 that it had added an Epic EHR integration and a public health data plugin to its enterprise healthcare platform, with San Francisco-based UCSF Health serving as the company’s pilot partner. The integration, which OpenAI said is read-only and does not write information back to the patient record, lets authorized clinicians pull together appointment notes, lab results, medications, and specialist documentation inside ChatGPT or directly within Epic workflows.
AdventHealth’s Evaluation Standard
“At AdventHealth, we evaluate emerging AI technologies against a simple standard: Can they measurably improve care while preserving patient trust and clinical judgment?” said Rob Purinton, chief AI officer at the Altamonte Springs, Fla.-based health system, a ChatGPT for Healthcare user. “Technical capability alone is not clinical readiness. We consider clinical use only when the evidence shows that an AI tool will support, not distract from, the human relationships at the heart of whole-person care.”
Cedars-Sinai’s Homegrown Comparison Within This CIOs Trust ChatGPT Epic Integration Debate
At Los Angeles-based Cedars-Sinai, the safeguard checklist doubles as one the health system has already been building against for nearly a year, not for OpenAI’s new integration, but for its own tool. “Our teams have been developing and deploying ChartChat, what we call our own in-chart solution, built and operated within our HIPAA-compliant Azure environment and using OpenAI models, for nearly a year,” said CIO Craig Kwiatkowski.
Why Build-Versus-Buy Remains an Open Question
“For any tool handling patient data, our focus is on protecting access, preserving accountability and keeping clinicians in control,” Kwiatkowski said, pointing to secure authentication, access limited to existing EHR permissions, comprehensive audit logs, and clear expectations that AI-generated information must be verified against the chart. He said building an in-house solution gives Cedars-Sinai direct control over user experience, roadmap, and underlying model economics, advantages the system will weigh against a packaged solution’s integration and governance benefits.
Nationwide Children’s Hospital’s Binary Threshold
At Columbus, Ohio-based Nationwide Children’s Hospital, the bar is more binary: a tool isn’t considered unless there’s no other way to do the job. “The requestor would need to present a solid use case that can’t be solved any other way,” said CIO Denise Zabawski, describing a thorough risk analysis involving security, privacy, legal, and compliance teams.
Why Some Systems Are Staying With Native Epic Features
Zabawski said her organization hasn’t evaluated generative AI tools that connect directly to its EHR, focusing instead on using Epic-provided features, and that OpenAI’s Epic integration doesn’t change that plan, illustrating how some health systems are choosing to stay within their EHR vendor’s native AI ecosystem rather than layering on third-party tools.
Corewell Health’s Higher Bar for Direct EHR Connections Within This CIOs Trust ChatGPT Epic Integration Question
At Corewell Health, a direct EHR connection doesn’t ease the burden of proof for an AI tool, it heightens it, said Chief Medical Information Officer Daniel Smith. “Privacy and security must be foundational, but they are only the beginning. We also need confidence that the information returned is accurate, understandable, grounded in the source record and easy for a clinician to verify,” he said, adding that evaluation cannot stop at implementation and requires ongoing monitoring.
Distinguishing Securing Data From Correctly Interpreting It
“Read-only access, existing EHR permissions and strong enterprise controls are important design choices,” Smith said. “But protecting the data and correctly interpreting the data are two different questions. The harder challenge is ensuring that an AI-generated synthesis is consistently accurate, clinically appropriate and transparent enough that clinicians can recognize when it gets something wrong.”
Penn Medicine’s Chart Hero as a Working Model
At Philadelphia-based Penn Medicine, the answer is a tool that’s already built and in daily use. Mitchell Schnall, MD, PhD, senior vice president for data and technology solutions, pointed to Chart Hero, the in-house generative AI tool Penn Medicine built to help clinicians sift through patient records, now used by about 30 clinicians.
Traceability and Drift Monitoring as Chart Hero’s Core Trust Features
Schnall, a practicing radiologist who uses Chart Hero for nearly every case he reviews, pointed to two features central to trusting the tool: “Every insight about the patient that Chart Hero surfaces includes a reference and link to where it learned the information from, so you have transparency and can check if you have questions,” he said. “We built a model to monitor performance… This allows us to track performance to monitor for drift,” including objectively assessing the impact of changes ranging from foundation model updates to documentation practice changes.
What This CIOs Trust ChatGPT Epic Integration Debate Means Going Forward
Across all five health systems, the shared condition for trusting any AI tool with EHR access, whether OpenAI’s new integration or a homegrown alternative, centers on traceability, audit logs, and a clinician’s ability to verify AI-generated information against the source record. Given the range of approaches, from Cedars-Sinai’s year-long ChartChat build to Nationwide Children’s binary “no other way to do it” threshold, health systems evaluating OpenAI’s Epic integration may find these five institutional standards a useful benchmark for developing their own evaluation criteria before granting any generative AI tool direct EHR access.
What to Watch Going Forward
As more health systems weigh OpenAI’s Epic integration against homegrown alternatives like ChartChat and Chart Hero, industry observers will likely watch whether build-versus-buy decisions increasingly favor packaged vendor solutions as governance and integration capabilities mature, or whether systems with existing in-house tools continue prioritizing the control that comes with building their own. Given the consistent emphasis on ongoing monitoring rather than one-time implementation review, this CIOs trust ChatGPT Epic integration debate suggests health systems are converging on a shared framework, read-only access, audit trails, and continuous performance monitoring, even as they arrive at different conclusions about whether to build or buy the underlying AI capability itself.
For more healthcare industry updates, insights and news, visit DistilINFO. Click here to subscribe to stay informed.
