OpenAI Connected ChatGPT to Epic Charts on 1 September 2026, With Read-Only Access
Quentir Medicine Monitor
Evidence-based insights for quantum medicine.
A clinician preparing for an afternoon appointment spends the first minutes of it reading: the last visit note, the newest labs, the medication list, whatever the specialist sent over. On 1 September 2026 OpenAI said that reading can be handed to ChatGPT, working from the patient's own Epic record.
Two capabilities ship together. Health organizations can connect their Epic electronic health record environments to ChatGPT for Healthcare, and a separate Healthcare Public Data plugin wires the same workspace to nine official public datasets, among them ClinicalTrials.gov, CMS Coverage, RxNorm, DailyMed and PubMed. Access to the chart is read-only. The model writes nothing back into the record.
Two things carry this deployment to the bedside, and a regulatory clearance is neither of them. The first is a business associate agreement, the contract HIPAA requires before an outside vendor may handle protected health information. The second is OpenAI's own physician evaluation, which reports 4,363 ratings across 27 clinical use cases, with 99.1 percent of responses graded safe.
Those figures come from evaluation results OpenAI published itself, and the company says so. The denominator is ratings, and the announcement does not say whether one response could receive several of them, so 99.1 percent of 4,363 leaves approximately 39 non-safe ratings rather than a countable set of unsafe answers. No definition of the safety rating is published: the announcement does not say what the scale was, what those 39 ratings concerned, how severity was graded, or whether reviewers were blinded to the source of the answer.
Where the product lands against FDA's four criteria for clinical decision support software, the fourth of which asks that a clinician can independently review the basis for a recommendation, is an open question that read-only access does not settle on its own, and the announcement reports no determination. The decision support interventions criterion at 45 CFR 170.315(b)(11) reaches interventions a developer supplies with its own health IT module, which leaves the scope question for a hospital to settle with its vendors.