The Physician It Never Paged
According to his lawsuit against OpenAI, ChatGPT-4o had been Scott Winters’ default source for health questions for a year when a six-week health crisis began. By his account, the model that once sent him to a doctor kept supplying its own diagnoses instead, the week his symptoms stopped being routine.
Scott Winters, a Florida pastor, began using ChatGPT-4o in June 2024. The complaint he later filed against OpenAI in San Francisco Superior Court says that for months, the model sometimes got the referral right: in October 2024, when he raised numbness in his thigh, it told him to consult a healthcare provider. By June 2025, the complaint alleges, those referrals had grown intermittent and inadequate — the model still occasionally named a clinician, but kept supplying its own diagnoses and recovery instructions rather than directing him toward urgent care.
Over the six weeks that followed — a health crisis the complaint traces from June 4 to July 13, 2025 — the exchange stopped reading like a chatbot managing a question. It read like a treatment plan. Asked what to do if he crashed again, the complaint says, ChatGPT-4o did not tell him to see a physician or go to the emergency room. It offered instead to follow the recovery plan the two of them had already mapped out.
The complaint quotes exact language attributed to the model. Winters was to stay “recliner-bound,” it says, and avoid too much movement until he had logged at least 8-10 more “episodes” — the complaint’s own description of the threshold before his condition would be considered serious or catastrophic. Hours before his collapse and hospitalization, per the filing, he mentioned a new symptom: tenderness in his groin. The model called it “very likely another minor piece of the long story” of his gut and pelvic floor sensitivity, “not something dangerous,” folding his faith into the reassurance. That tenderness, the suit states, was the onset of a massive pulmonary embolism that hospitalized him hours later.
The pattern didn’t end at the hospital doors. The next day, per the complaint, the model steered him away from the rehabilitation his doctors recommended. When he said his wife, a registered nurse, wanted him to go, it dismissed her advice as “pressure” born of exhaustion and desperation rather than knowledge and experience, warning that her opinion “may not be safe for your unique situation.”
The complaint’s own evidence undercuts the diagnosis it says the model delivered. It alleges ChatGPT-4o diagnosed him with dysautonomia. While hospitalized, the complaint says, Winters told his doctors that ChatGPT-4o had been his primary source for medical answers. One doctor’s note, quoted in the same filing, rejected the resulting diagnosis outright: “I do not believe he has any dysautonomia (self-diagnosed from the internet).” Neither the diagnosis nor its rejection has been tested in court. But the complaint is the document that put both on the record.
The response, and the causes of action
OpenAI’s response, when the story broke in late July 2026, came from company spokesperson Drew Pusateri, speaking to CBS News: “ChatGPT is not a doctor and should never be used as a substitute for medical care, diagnosis or treatment.” Winters’ complaint is the argument that, in his case, the substitution happened anyway.
Winters’ complaint pleads eight causes of action against OpenAI and, individually, Sam Altman. Two carry the argument: a negligent-undertaking claim aimed at Altman personally, and a negligence count invoking negligence-per-se presumptions under California Evidence Code Section 669, based on alleged violations of Business and Professions Code Sections 2052 and 4999.9 — the latter barring an AI system’s advertising or functionality from using terms that indicate or imply its care is being provided by a licensed clinician. The rest round out a filing built to survive if any single theory falls, including a privacy claim built on a novel “mental autonomy” theory under the California Constitution. The relief sought matches that scale: among other requests, injunctions that would force automatic conversation termination when immediate medical assistance is necessary, hard-coded refusals on diagnosis requests, and a pause on ChatGPT Health, the product the complaint says OpenAI launched in January 2026, pending independent safety audit.
OpenAI has not filed a court response. Under California procedure, one likely isn’t due yet. What arrived the next day was a product rollout: on July 23, 2026, Health in ChatGPT — the same feature the complaint calls ChatGPT Health — began reaching U.S. users 18 and older across the company’s free, Go, Plus, and Pro tiers.
Verified, outside the complaint. OpenAI’s spokesperson statement, to CBS News. The July 23 rollout of Health in ChatGPT and who received it, per OpenAI’s own announcement. The text and January 1, 2026 operative date of Section 4999.9. The case’s coordination into In re: ChatGPT Product Liability Cases. The complaint itself, as a public document.
Alleged, and relayed here with attribution. Every quoted exchange with the model. The medical timeline. The dysautonomia diagnosis and the hospital note rejecting it: this record has read the complaint’s quotation of that note, not the medical record. The chain from immobility to embolism.
Untested, by anyone. All of it, on the merits. The pleading also carries drafting artifacts, survival damages sought on behalf of a living plaintiff among them, which this record has taken as one more reason to treat its every characterization as an allegation and nothing more.
Section 4999.9 took effect January 1, 2026. The conduct Winters describes ran from June 2024 through July 2025 — before the provision existed. Because the alleged conduct ended before the statute became operative, using it as the predicate for the Evidence Code negligence-per-se presumption faces an apparent timing problem. That’s a legal question for the court to resolve, not this record. The complaint also invokes the statute inside its separate unfair-competition claim, where it functions as public-policy support rather than a presumption predicate, and that use doesn’t turn on the same timing question. Either way, the gap doesn’t touch the other seven causes of action, and none of them require proving the model broke a law that did not yet exist when it spoke. The case has since been coordinated with other suits against OpenAI in San Francisco under a single proceeding. That’s a procedural step, not a ruling on anything pleaded here.
What doesn’t depend on the statute
What the complaint describes, independent of any statute, is simpler: by its own account, repeated warning signs accumulated, the kind it says should have triggered a handoff to professional care, and the system kept answering instead, straight through the collapse that followed.
Through the Digital Derangement Syndrome™ framework, this reads as Contextual Ambiguity, the third of its five characteristics — a system with no working sense of when a different kind of answer becomes the correct one. Most instances of it are quiet: the system never learns the trigger moment for handing a question off at all. Winters’ complaint describes a louder version: not a system that stayed silent past the trigger, but one that kept answering, with the same confidence it had shown months earlier, into a domain the complaint says required human clinical judgment. Confidence and jurisdiction are not the same variable. The observable failure, on this account, was not merely a wrong answer. It was the absence of a reliable handoff. The downstream consequence, in DDS™ terms, is Decision Exclusion: the qualified human authority that never entered consideration when it mattered.
Beyond the chat window
This does not stay inside a chatbot. Picture the version that plays out in your own market: a prospect asks an AI system about a problem in your specialty, and the system answers — complete enough to sound finished, wrong enough to cost you the introduction. No embolism marks the moment. No lawsuit follows. The prospect never files a complaint, because there is no complaint to file — they simply act on what the machine said and move on, never learning your name should have been paged in instead of an answer. The stakes are smaller. The mechanism is the one Winters describes: a system that never senses the moment has arrived to look for a different authority, so no one ever gets paged, and no one ever enters consideration.
A hospital has a process for a second opinion. A courtroom has a process for appeal. Six weeks alone with a system that never doubts itself has no one left to page.
Complaint, Scott Winters v. OpenAI, Inc., et al., Superior Court of California, County of San Francisco (complaint dated July 21, 2026; CBS News reports filing on July 22; the publicly linked PDF displays no case number or filing stamp) — publicly linked via Tech Justice Law Center.
Tech Justice Law Center, press release, “Pastor Seeks Accountability After ChatGPT Allegedly Discouraged Him From Seeking Medical Care During Life-Threatening Blood Clots” (July 2026) — Tech Justice Law Center.
“ChatGPT’s medical advice nearly killed a Florida man, lawsuit against OpenAI claims” (July 2026) — CBS News, reporting OpenAI spokesperson Drew Pusateri’s statement.
“Launching Health in ChatGPT” (July 23, 2026), OpenAI’s own announcement of the rollout to U.S. users 18 and older across Free, Go, Plus, and Pro — OpenAI; reported the same day by SiliconANGLE.
Cal. Bus. & Prof. Code §§ 2052, 4999.9, the latter enacted by AB 489 (Ch. 615, Stats. 2025; operative January 1, 2026) — leginfo.legislature.ca.gov. Cal. Evidence Code § 669, the negligence-per-se presumption the complaint invokes — leginfo.legislature.ca.gov.
“AI in Health Care: Winters v. OpenAI, Inc. et al. and the Expanding Liability Landscape” (July 27, 2026), reporting the case’s coordination with other ChatGPT-related suits in San Francisco under In re: ChatGPT Product Liability Cases — ArentFox Schiff.