First-person account: patient says a doctor read Google's AI search summary for a diagnosis and later called to say the patient was right
In an article published on Medium on 26 October 2026 and a Bluesky post on 30 October, a writer says that at one appointment a doctor said "Let's ask Dr. Google", searched for a diagnosis and read the AI summary at the top of the results without opening any sources. The writer says the doctor was wrong; after they emailed him their sources and asked what they were missing, he called to say they were right. They say they were nervous to send the emails, and that their own research used Claude and Gemini, cross-checked against the cited sources. The article does not say what the summary said, what the diagnosis was, or when the appointment took place.
- AI system
- Google Search AI summary (reported)
- Occurred
- Event date unknown
- Reported
- 26 October 2026
- Event location
- Unknown
- What the AI did
- Informed a human decision about the person
- Reported harm
- Psychological Distress
- Whose AI use
- An institution’s AI use · Their own AI use
- Setting
- Health
- Evidence
- AI involvement reported · Causal attribution alleged · 2 sources, 1 underlying account
- 5 claims: 5 reported. 5 open questions
- People reported harmed
- 1 person
AI system as recorded: AI-generated summary at the top of Google search results, as described by the patient; feature name not given
What Happened
The appointment. The author writes that at one appointment a doctor pulled up Google on his computer, said "Let's ask Dr. Google," and read the summary at the top of the page without clicking through to any of the sources. In a Bluesky post linking the article, the author describes this as the doctor Googling a diagnosis and reading them the AI summary at the top of the results.
The correction. The doctor was wrong, the author says. They emailed him their sources and asked what they were missing, and he called to say they were right. The author writes that they were nervous to send emails questioning doctors' diagnoses; the article describes a second diagnosis error by a different doctor in the same month that did not involve the AI summary.
The author's own AI use. The author says they used Claude and Gemini when researching the diagnosis, had Gemini look for holes in what Claude said, and read the cited sources themselves.
Limits. The account is the author's own. It does not say what the summary said, what the diagnosis was, whether any treatment was affected, or when and where the appointment took place.
Reported harm
The author says a doctor gave them a wrong answer on a diagnosis after reading Google's AI search summary aloud, and that they had to research and nervously challenge it by email before the doctor agreed (first-person account; no effect on treatment is reported).
How Harm Occurred
By the author's account, a doctor answered a diagnosis question by reading Google's AI search summary aloud without checking its sources; the answer was wrong, and the patient had to research and challenge it before the doctor agreed.
Outcome
ResolvedBy the author's account the doctor called to say the author was right after the author emailed sources. No complaint or other action is reported.
What remains unknown
- What the AI summary said, what diagnosis was at issue, and whether the error lay in the summary or in the doctor's reading of it.
- When the appointment took place; the article (26 October 2026) gives no date, and the Bluesky post of 30 October 2026 does not either.
- Which Google feature produced the summary; the author calls it the AI summary at the top of the results.
- Whether the wrong answer affected any treatment before it was corrected.
- Where the appointment took place.
What the evidence supports
AI involvement: reported. The author writes that during their appointment a doctor searched Google for a diagnosis and read them the AI-generated summary at the top of the results without opening any sources, and that the doctor's answer was wrong; after the author emailed sources, the doctor called to say the author was right. The output was used in the doctor's answer to the patient. What the summary said is not described.
5 claims: 5 reported. What the statuses mean
Reported The author wrote that at one of their appointments a doctor pulled up Google on his computer, said "Let's ask Dr. Google," and read the summary at the top of the page without clicking through to any of the sources.
Causal attribution. Author's first-person account of the appointment.
- medium.com(opens in new tab) supports · English
'one of my appointments, where a doctor pulled up Google on his computer, said, “Let’s ask Dr. Google,” and read the summary at the top of the page without clicking through to any of the sources'
Reported In a Bluesky post linking the article, the author described the doctor as Googling a diagnosis and reading them the AI summary at the top of the results, and wrote that he was actually wrong.
Causal attribution. The author identifies the summary as AI-generated and the doctor's answer as wrong; what the summary said is not described, so whether the error lay in the summary itself or in the doctor's reading of it is not established.
- bsky.app(opens in new tab) supports · English
'Google a diagnosis, and read me the AI summary at the top of the results'; 'Spoiler alert: He was actually wrong.'
Reported The author wrote that the doctor called to say they were right after they emailed to push back, saying in effect that he was wrong and giving their sources.
Causal attribution. Author's account of the correction.
- medium.com(opens in new tab) supports · English
'To his credit, he did call me to say I was right after I emailed to push back and essentially say, “I think you’re wrong, here are my sources. What am I missing?”'
Reported The author wrote that they were nervous to send the emails questioning the doctors' diagnoses.
Causal attribution. The author describes this for both diagnosis disputes in the article, only one of which involved the AI summary.
- medium.com(opens in new tab) supports · English
'I’d be 100% lying if I said that I wasn’t nervous to hit send on the emails to the doctors to question their diagnoses'
Reported The author wrote that they used Claude and Gemini to research the diagnosis, cross-checked them against other sources and read the cited sources themselves.
Causal attribution. Context: the author's own AI-assisted research is how they challenged the doctor.
- medium.com(opens in new tab) supports · English
'I definitely used AI when I was researching this diagnosis. But I didn’t just go with the first response Claude gave me'; 'I used Gemini to do deeper research and had it try to find holes in what Claude told me'
Sources
2 sources inspected, from 1 underlying account. Sources that repeat one account do not corroborate each other.
- Medium (Bootcamp), 26 Oct 2026: "Let’s ask Dr. Google: The risk of blind trust in AI"(opens in new tab)
s1 · medium.com · Personal blog · English · Inspected · 26 October 2026 · Shares an underlying account with another listed source · Primary
- Bluesky, 30 Oct 2026: author's post on the doctor reading the AI summary(opens in new tab)
s2 · bsky.app · Social post · English · Inspected · Shares an underlying account with another listed source
How the sources were read, and where the events happened
Read in English on 2026-10-31. medium.com returned HTTP 403 to the fetcher and the Wayback Machine had no capture, so the full article text was read from the author's own Medium RSS feed (HTTP 200), which carries the complete article dated 26 October 2026. Applies to s1.
Read in English on 2026-10-31 through the public Bluesky API (post, thread with no replies, and the author's feed, HTTP 200). Same author as the article, so not independent of it. Applies to s2.
Event countries: Unknown. Affected-person countries: Unknown. Court countries: Unknown.
The article and the post do not say where the appointment took place or where the author lives.
Reviewed for publication 2026-10-31: Published as a contextual case: the author says a doctor answered a diagnosis question by reading Google's AI search summary aloud during the appointment, that the answer was wrong, and that the doctor agreed after the author pushed back with sources. First-person account, low severity.
People described
The author, a patient (age and country not stated)
People reported harmed in this case
1 person
0 AI participants · 1 other person harmed
One person counted: the author, the patient about whom the doctor used the AI summary; the author was not the AI user.
Counted once within this case. The same person may appear in other cases. This count does not establish AI causation.
Cite this case
Compiled per our published methodology: verification statuses, sourcing standards, and corrections process.
APA
NOPE. (2026). First-person account: patient says a doctor read Google's AI search summary for a diagnosis and later called to say the patient was right. AI incidents. https://nope.net/incidents/2026-patient-says-doctor-read-google-ai-search-summary-for-a-diagnosis-then-called-to-say-the-patient-was-right-first-person
BibTeX
@misc{2026_patient_says_doctor_read_google_ai_search_summary_for_a_diagnosis_then_called_to_say_the_patient_was_right_first_person,
title = {First-person account: patient says a doctor read Google's AI search summary for a diagnosis and later called to say the patient was right},
author = {NOPE},
year = {2026},
howpublished = {AI incidents},
url = {https://nope.net/incidents/2026-patient-says-doctor-read-google-ai-search-summary-for-a-diagnosis-then-called-to-say-the-patient-was-right-first-person}
} Related cases
Reported by ABC News (Australia): an AI scribe used at a urology appointment inserted a false claim that the patient took psychedelic mushrooms into her record; the error reached her GP in a post-operative letter and was corrected only after she complained
A patient who consented to having her first urology appointment transcribed by an artificial-intelligence scribe discovered, after her kidney-stone surgery in March 2026, that the post-operative letter her specialist sent to her GP stated she micro-dosed psychedelic mushrooms and that this could explain earlier bleeding around the kidneys. She says she has never taken mushrooms. She was receiving workers' compensation and feared that any mention of illegal drugs on her medical record could affect her case. After she complained, the urologist sent a letter of apology saying the practice takes documentation accuracy seriously, that she could not determine how the claim came to be included but that it appeared to be an error during the 'dictation or transcription process', that the correspondence had been corrected and that she would review how AI was used in her practice. The doctor did not answer ABC's questions about what changes had been made. Australia's practitioner regulator AHPRA told ABC that clinicians must check all AI-scribe output; the patient says it was clear her doctor had not. The account is a single ABC News report (14 August 2026) based on the patient's interview and the letters she received; the scribe product and the clinic's location are not named.
United States: seven people who say they had no Otter account allege its AI Notetaker recorded calls without consent; a judge let core privacy claims proceed
Seven people in California, Illinois and Washington state are suing Otter.ai in a consolidated class action in the Northern District of California. Each says another meeting participant used Otter's AI Notetaker on a Zoom or Microsoft Teams call they joined, and that Otter recorded, transcribed and stored their conversation without their consent; six of them date their calls between March 2024 and May 2025. They say they were not Otter account holders. The calls they describe include a medical consultation, meetings with a financial professional and work discussions. They allege that Otter keeps the recordings and uses them to train its speech-recognition models, that it captured voiceprints of the Illinois plaintiffs, and one of them says learning of the recording left him frustrated, embarrassed and stressed. On 13 August 2026 the court found that the alleged interception of private conversations was a concrete injury and let the federal wiretap, California eavesdropping and Illinois biometric claims proceed, while dismissing some claims. Otter's answer to the consolidated complaint, filed on 17 September 2026, says it lacks knowledge of the plaintiffs' experiences and denies the allegations.
London: AI-generated GP record summary falsely listed diabetes, and a healthy patient was invited to diabetic eye screening, Fortune reports
Fortune reported on 20 July 2025 that a London patient, a healthy man in his mid-20s, had recently received a letter inviting him to diabetic eye screening although he had never been diagnosed with diabetes. He told Fortune he briefly worried he had been diagnosed without knowing, then assumed an admin error. The next day a nurse at a routine blood test questioned the diagnosis and showed him the notes on the system, which were AI-generated summaries. In his full records, which Fortune reviewed, the entry that introduced the diagnosis was listed as a summary 'generated by Annie AI', the tool of Anima Health. It said he had presented with chest pain and shortness of breath from likely angina due to coronary artery disease, that he had been diagnosed with type 2 diabetes and was on medications with dosages, and it gave the source document's address as a fictitious 'Health Hospital' on '456 Care Road' in 'Health City'. According to the patient and other records Fortune reviewed, none of these details was accurate; the entry appeared around the time he had attended hospital with tonsillitis, which it did not mention. Fortune writes that the invitation was presumably based on the erroneous summary. An NHS representative told Fortune the practice makes limited use of supervised AI, that Anima only suggests codes and a summary to a human reviewer, and that the error was a one-off human error: a summariser had spotted the mistake but, distracted, saved the original version instead of the corrected one. Anima Health did not respond to Fortune.
US: HCA nurses tell WIRED its AI scheduling tool overrode their shift requests and scheduled them on requested days off; one delayed a medical appointment
Nurses at HCA Healthcare, the largest US hospital chain, told WIRED, in an article published on 2 October 2026, that Timpani, an AI scheduling tool HCA co-developed with Palantir and has rolled out at about 130 of its 190 locations, assigns shifts that ignore their requests. A Florida critical care nurse said that over four months the tool gave her different shifts for more than half of the 50 she requested, often back-to-back days that left her mentally drained. A Missouri nurse said essentially every nurse at their facility had been assigned to work on a requested day off, and that they delayed a long-planned doctor's appointment for a chronic condition after struggling to trade such a day. HCA says nursing leaders, not Timpani, make final scheduling decisions and that the tool schedules nurses on about 1 percent of requested days off.
If you or someone you know is struggling, free and confidential support is available. Find a helpline near you at Signpost.