惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

K
Kaspersky official blog
T
Threat Research - Cisco Blogs
N
News and Events Feed by Topic
Hacker News: Ask HN
Hacker News: Ask HN
Project Zero
Project Zero
Application and Cybersecurity Blog
Application and Cybersecurity Blog
博客园 - 叶小钗
Security Latest
Security Latest
Spread Privacy
Spread Privacy
aimingoo的专栏
aimingoo的专栏
N
News and Events Feed by Topic
Webroot Blog
Webroot Blog
U
Unit 42
Cyberwarzone
Cyberwarzone
小众软件
小众软件
Scott Helme
Scott Helme
Engineering at Meta
Engineering at Meta
Microsoft Security Blog
Microsoft Security Blog
T
The Blog of Author Tim Ferriss
A
About on SuperTechFans
爱范儿
爱范儿
S
Schneier on Security
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
Schneier on Security
Schneier on Security
Latest news
Latest news
GbyAI
GbyAI
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
Simon Willison's Weblog
Simon Willison's Weblog
The Register - Security
The Register - Security
WordPress大学
WordPress大学
博客园_首页
Blog — PlanetScale
Blog — PlanetScale
PCI Perspectives
PCI Perspectives
Jina AI
Jina AI
AI
AI
NISL@THU
NISL@THU
I
Intezer
G
GRAHAM CLULEY
B
Blog
S
Secure Thoughts
IT之家
IT之家
宝玉的分享
宝玉的分享
Recent Announcements
Recent Announcements
Y
Y Combinator Blog
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
酷 壳 – CoolShell
酷 壳 – CoolShell
有赞技术团队
有赞技术团队
V2EX - 技术
V2EX - 技术
Recorded Future
Recorded Future
Hacker News - Newest:
Hacker News - Newest: "LLM"

Hacker News - Newest: "AI"

AI can't read an investor deck AI as an attorney? Student uses ChatGPT, Gemini to sue UW over alleged racial discrimination Hacking MCP Servers in AI Systems – The Rug Pull: Tool Changes After Approval GitHub - MeepCastana/KubeezCut: Free Web based video editor GitHub - GenAI-Gurus/awesome-eu-ai-act: Curated tools, official sources, OSS, templates, and guides for EU AI Act compliance. Can AI judge journalism? A Thiel-backed startup says yes, even if it risks chilling whistleblowers Coming soon: 10 Things That Matter in AI Right Now DARPA built an AI to fact-check enemy weapons claims What explains heterogeneity in AI adoption? When AI Meets Muscle: Context-Aware Electrical Stimulation Promises a New Way to Guide Human Movements - Department of Computer Science AI Changed How We Build. It Did Not Change What Matters. Linux rules on using AI-generated code - Copilot is OK, but humans must take 'full responsibility for the… Meta spins up AI version of Mark Zuckerberg to engage with employees Code Mode: Let Your AI Write Programs, Not Just Call Tools | TanStack Blog GitHub - Delavalom/graft: Go framework for building AI agents. Type-safe tools, multi-provider (OpenAI, Anthropic, Gemini, Bedrock), zero vendor SDKs. India's TCS tops estimates, says new AI models did not dent services demand Gen Z's fading AI hype Strong feeling: we are in a folded AI reality GitHub - machinarii/total-recall-catalog: A reference catalog of latest knowledge retrieval, memory & RAG systems GitHub - mensfeld/code-on-incus: Give each AI agent its own isolated machine with root, Docker, and systemd. Active defense detects and stops threats automatically.. Quantization, LoRA, and the 8% Problem: Benchmarking Local LLMs for Production AI Iran war: We spoke to the man making Lego-style AI videos that experts say are powerful propaganda Powell, Bessent discussed Anthropic's Mythos AI cyber threat with major U.S. banks GitHub - immartian/bellamem: Persistent belief-graph memory for AI agents. Retrieves decisive context by importance — not recency, not RAG, not /compact. recursive-mode: The Repo-Native Operating System for AI Engineering After the attack on Sam Altman's home, will AI CEO's go on the offensive? The biggest advance in AI since the LLM Opus 4.6 vs GPT 5.4 One Prompt Unity World Generation Test “AI polls” are fake polls Client Challenge Can AI be a 'child of God'? Inside Anthropic's meeting with Christian leaders How to Switch AI Chatbots and Why You Might Want To GitHub - MattMessinger1/agentic_refund_guardrail: Safe refund policy layer for AI agents — Python + TypeScript. Same behavior, shared tests. Adam/papers/emergent_values_whitepaper.md at master · strangeadvancedmarketing/Adam Ask HN: How do you stop playing 20 questions with your AI coding tools How far can automation and AI support psychotherapy? - @theU GitHub - stagas/rtdiff: realtime git diff gui and AI-assisted commits A Mac Studio for Local AI — 6 Months Later A History of the Early Years of AI at the University of Edinburgh Why AI Coding Tools Still Feel Stuck on Localhost MSN AI Datacenters Are Becoming Strategic Targets twitter.com Penn Researchers Use AI to Surface Unreported GLP-1 Side Effects in Reddit Posts Show HN: MoodSense AI (ML and FastAPI and Gradio, Deployed on Hugging Face) Moodsense Ai - a Hugging Face Space by aman179102 AI models are terrible at betting on soccer—especially xAI Grok GitHub - xialeistudio/echoic GitHub - HimashaHerath/github-dev-wrapped: AI-powered weekly GitHub activity reports deployed to GitHub Pages GitHub - alejandrobalderas/claude-code-from-source: Architecture, patterns & internals of Anthropic's AI coding agent — reverse-engineered from source maps AI and Tech brief: Ireland ascendant GitHub - Titovilal/context0: Context0 - Never Surrender Training for a Marathon with an AI Coach: What Worked and What Didn't Cyber Pulse: Agentic Intel - Apps on Google Play I Built an AI PR Reviewer That Catches Bugs by Not Looking for Bugs Gen Z workers are so fearful AI will take their job they’re intentionally sabotaging their company’s AI rollout | Fortune How AI Is Reimagining the Game of Golf–For Both Players and Courses GitHub - nattergabriel/reseed: A CLI tool for managing and distributing agent skills across projects Is SVG the final frontier? My AI workflow evolved from prompts to a near-autonomous workflow MLSharp Help - 3DGS Viewer & Generator I put my cognitive field based AI's runtime on GitHub Is Numble the first AI-proof game? A3: Kubernetes for autonomous AI agent fleets | Emergent Principles Deepali Vyas ("The Elite Recruiter") GitHub - msmarkgu/RelayFreeLLM: A restful API designed to route user prompts to various AI model providers. Unionized ProPublica staff are on strike over AI, layoffs, and wages Unleashing the Advantage of Quantum AI We're heading for an AI-fueled 'dementia crisis,' brain scientist warns The AI-Assisted Breach of Mexico's Government Infrastructure [pdf] GitHub - stef41/lmscan: 🔍 Detect AI-generated text and fingerprint which LLM wrote it. Open-source GPTZero alternative. Zero dependencies, works offline. MSN GitHub - visionscaper/collabmem: Enabling long-term collaboration with Agentic AI - building up episodic and world model memory over time with in-context awareness We gave an AI a 3 year retail lease in SF and asked it to make a profit | Andon Labs AI Code is Hollowing Out Open Source, and Maintainers are Looking the Other Way What leaked "SteamGPT" files could mean for the PC gaming platform's use of AI AI is the boss at this retail store. What could go wrong? GitHub - Wuzu11517/agentic-proxy: Local proxy meant to help reduce With Drones, Geophysics and ArtificiaI Intelligence, Researchers Prepare to Do Battle Against Land Mines A Single Operator, Two AI Platforms, Nine Government Agencies: The Full Technical Report 在 Steam 上购买 FriedrichAI: Offline AI 立省 10% GitHub - inevolin/resume-cli: Hit Claude usage limits? Resume any AI coding session elsewhere. Switch tools at zero friction. GitHub - atripati/ark: AI Runtime Kernel — a context operating system for AI agents. Eliminates tool bloat, loads only what’s needed, and gives LLMs their reasoning space back. How to Build a Secure AI PR Reviewer with Claude, GitHub Actions, and JavaScript This Startup Wants You to Pay Up to Talk With AI Versions of Human Experts Intel Arc Pro B70 Brings 32GB VRAM to Local AI for $949 WordPress 7.0: The Good, the AI, and the Still Missing AI on the couch: Anthropic gives Claude 20 hours of psychiatry IatroBench: Pre-Registered Evidence of Iatrogenic Harm from AI Safety Measures AI Agents Know About Supabase. They Don't Always Use It Right. The history and future of AI at Google, with Sundar Pichai Inside an AI‑enabled device code phishing campaign How Meta Used AI to Map Tribal Knowledge in Large-Scale Data Pipelines AI for Systems: Using LLMs to Optimize Database Query Execution Forecasting the Economic Effects of AI Introducing Tinker: Play with AI, bring your ideas to life AI sheds light on an ancient gaming mystery People really hate AI but not as much as Iran—or Democrats | Fortune What is an AI Product Engineer? Phoebe Gates wants her $185 million AI startup to succeed with 'no ties to my privilege or my last name': 'I have a chip on my shoulder' | Fortune
I Was an Enthusiastic Early Adopter of AI Scribes. Here’s Why I Stopped
Dr Benn Gooch · 2026-04-16 · via Hacker News - Newest: "AI"

I want to be clear about something before I begin: I am not a technophobe. I am a GP with a background in clinical digital leadership, a member of the RCGP Informatics Group, and someone who spent eighteen months as an enthusiastic, committed early adopter of ambient AI scribing technology. I believed in it. I advocated for it. I used it every day.

And then I stopped. Not because the technology failed — but because it worked exactly as intended, and that turned out to be the problem.

What I experienced over those eighteen months, and what I have since spent considerable time trying to articulate, is not a first-order failure of the technology. It is a second, third, and fourth-order failure of our understanding of what the GP consultation actually is, and what we put at risk when we hand its documentary function to a machine.

The Promise Was Seductive — and Real

Let me not be ungenerous to the tools themselves. The clinical governance around the particular tool used, is genuinely solid. It is MHRA-registered, GDPR-compliant, and designed with patient safety at its core. The early outcome data is, on the face of it, compelling. A large US study published in JAMA found that ambient scribing reduced clinician burnout from 51.9% to 38.8% after just thirty days of use. The efficiency metrics — around 26% time saved on documentation — are similarly striking.

And experientially, the appeal is visceral. You walk into a consultation. You speak to your patient. You look at them — really look at them, rather than at a screen. The machine captures everything, assembles a structured note, and within seconds of the patient leaving, your record is essentially complete. It feels like a superpower. It feels like being given back the consultation you trained for, minus the administrative drag that hollowed it out.

I understand why colleagues are excited. I was excited. The question I want to pose is not whether these tools offer something real — they do — but whether we are paying a price we haven’t yet noticed.

The Consultation Began to Change

The first thing I observed — and it took several months before I could name it — was that my consultations were getting longer, and not because I was doing more.

With an impartial, photographic memory capturing everything, I found I was giving patients more latitude. The implicit contract of the ten-minute GP appointment has always involved a degree of managed agenda-setting. Experienced GPs develop a sophisticated, largely unconscious set of tools for this: a particular way of listening that signals receipt without necessarily invitation, a calibrated use of silence, the gentle steering of “and what else?” Patients learn, over many encounters, to make their most important point early.

The scribe dissolved this contract. Because everything would be recorded and reviewed, I began to allow consultations to expand to fill whatever space the patient needed. It felt, in the moment, like better medicine. It felt like finally doing it properly.

What I was actually doing was offloading the work of clinical curation — one of the most cognitively demanding and clinically important things a GP does — to the post-consultation review process. And that review process was mine alone, unsupported, often done at the end of a surgery already running thirty minutes over.

I was left with too many problems documented to manage, too many loose threads to follow up, and a creeping sense of clinical overextension that I initially attributed to patient complexity rather than to a change in my own behaviour.

The Notes Weren’t Mine

The deeper unsettling came later, at follow-up appointments.

I sat down to review a patient I had seen six weeks previously. I read the note. It was accurate. It was comprehensive. It contained no factual errors that I could identify. And I did not recognise it.

The voice in the note was not my voice. The emphasis was not my emphasis. The clinical narrative — the selective, interpretive story that a GP constructs to capture not just what was said but what mattered, what worried them, what they decided to watch and why — was absent. In its place was a faithful transcription of everything spoken, organised by structure rather than by clinical significance.

I had not written that note. An algorithm had written it, in response to sounds it had heard, and I had approved it, hurriedly, at the end of a session. Now, six weeks later, I was reading someone else’s account of a consultation I had conducted — and I couldn’t recall the patient clearly enough to reconstruct what had been left out.

This is not a small thing. The clinical note in general practice is not merely a medicolegal record. It is, as research in the Journal of General Internal Medicine has articulated, a form of narrative medicine — a clinician-authored story that reflects how the physician understood the patient’s situation at that moment in time. The act of writing it is itself a cognitive process: it forces synthesis, prioritisation, and reflection. It is, in a real sense, how we think.

When we outsource that act to an AI, we are not merely saving time. We are externalising a cognitive function that was doing clinical work we didn’t realise it was doing.

The Cognitive Science of What We’re Losing

There is a body of research on what cognitive scientists call “extended mind theory” — the idea that human cognition is not confined to the brain but extends into the tools and artefacts we use. Writing is perhaps the oldest and most profound of these cognitive tools. When we write clinical notes in our own voice, we are not transcribing our thoughts after the fact: we are completing them.

A PMC paper on cognitive perspectives in physician expertise makes this concrete. Clinical reasoning in general practice relies on what researchers call “illness scripts” — compressed, experiential summaries of what a particular clinical picture looks and feels like, built up over thousands of encounters. These scripts are stored not just neurologically but in the patterns of how we document: the phrases we reach for, the features we choose to record, the anxieties we articulate in the margin of the plan.

When an AI records everything rather than what we chose to record, this feedback loop breaks. The note stops being a reflection of clinical reasoning and becomes a verbatim archive. And as a PMC piece on note bloat explicitly warns, this risks obscuring the most medically important information under a volume of equally-weighted detail.

The research on “note bloat” — a concern raised explicitly in the ambient scribing literature — captures something important but doesn’t go far enough. The problem is not just that notes become longer. It is that they become less curated, less authored, less *ours*. And the clinical memory they are supposed to scaffold — the ability to pick up a case six weeks later and immediately reorient — degrades with them.

A qualitative study in JAMIA published in 2025 formalised what I had experienced intuitively: clinician identity and voice emerged as central constructs in how physicians perceive AI-authored notes. The notes don’t feel like theirs because, in a meaningful sense, they aren’t.

The Consultation’s Hidden Architecture

There is something else the ambient scribe disrupts that receives almost no attention in the literature: the hidden architecture of the GP consultation as a therapeutic and diagnostic instrument in itself.

The general practice consultation is not simply an information-gathering exercise followed by a decision. The process of how information is gathered — what is asked, in what order, how ambiguity is held or resolved, what the clinician chooses to make explicit — is itself diagnostic. The GP who listens to a patient describe fatigue and quietly decides not to ask about mood yet, who files something away for a later question, who notes a hesitation as clinically significant: this is not inefficiency. This is the craft.

The ambient scribe passively records all of this without understanding any of it. It captures the conversation but not the clinical intelligence embedded in its architecture. And — more critically — it changes the conversation itself. Knowing that everything will be recorded, patients speak differently. They raise more. They venture into territory they might previously have held back, trusting that the thoroughness of the record will carry the weight of what they’ve shared.

This is, in many ways, a good thing. In others, it is a transfer of clinical responsibility that we have not acknowledged: the patient has disclosed more, the scribe has recorded more, and the GP is now accountable for all of it, whether or not they had the clinical bandwidth to assess it in the moment.

I exceeded my time. I over-ran my surgeries. I accumulated more documented problems per consultation than I could safely manage. And the research, when you look for it, acknowledges exactly this risk: a 2024 review in PMC notes that comprehensive documentation might capture previously missed information, but could also clutter the medical record with less clinically relevant details — and that either approach creates challenges. What is less clearly stated is that the clinician, not the AI, carries the consequences.

What the Burnout Studies Are Missing

The headline finding — that ambient scribes reduce burnout — deserves scrutiny. A rapid review of the evidence, screening over 1,400 studies, found that burnout measured using standardised scales was essentially unaffected, even where engagement and perceived workload improved. The review concluded that digital scribes are unlikely to fully address the multifaceted issue of clinician burnout, which is driven by systemic factors the scribe does not touch.

My own experience is consistent with this. The administrative relief was real and immediate. The downstream cognitive and relational consequences took months to accumulate, and by then I had already attributed my increasing sense of disconnection to patient complexity, to the NHS, to everything except the tool.

The studies measuring burnout at thirty days, or even ninety, are too short to capture what I experienced. They are measuring the relief phase. They are not yet measuring what happens when the consultation you conducted three months ago is documented in a voice you don’t recognise, by a process you increasingly don’t trust, in notes you are nominally responsible for but did not substantively write.

A Caution for Trainee GPs

I want to say something specific about training, because I believe the risk is most acute here and least discussed.

Clinical reasoning is a skill that is built through practice, and a significant part of that practice is documentation. The act of writing up a consultation — deciding what to include, how to frame the assessment, what language to use — is not an administrative afterthought. It is a learning process. It is how junior doctors and GP registrars build the illness scripts and pattern libraries that will underpin their expert practice for the rest of their careers.

If registrars are trained from the outset with ambient scribing as the norm, we may be producing a generation of highly competent conversationalists who have never fully developed the cognitive discipline of clinical synthesis. The scribe will have done that work for them. And the consequences — subtler than an exam failure, much harder to measure — may only become visible years later.

The RCGP, as I understand it, has not yet produced a position statement on scribe use during training. It should.

What I Am Not Saying

I want to be precise about the limits of this argument. I am not saying ambient scribes are bad technology. I am not saying they should be withdrawn. I am not saying the burnout gains are illusory — for many colleagues, particularly those with the most crushing documentation burdens, they may be transformative and genuinely sustainable.

What I am saying is this: the consultation is not simply a conversation from which a document is generated. It is a complex cognitive and relational act, and the document we produce is not a by-product of that act but part of it. Any tool that changes how that document is produced will change the act itself, and we should expect those changes to be significant, not trivial.

We are in the relief phase of ambient scribing. The efficiency gains are real and the risks are not yet visible in our outcome data — partly because we haven’t looked, and partly because the timescales are too short. The absence of evidence is not evidence of absence.

I stopped using my ambient scribe not because it was broken, but because I began to understand, with increasing unease, what it was doing to the consultation I had spent twenty years learning to conduct. I felt myself becoming a passive observer in encounters where I had previously been an active architect. I felt my clinical memory, my narrative identity, and my sense of connection to my patients beginning to erode at the edges.

I cannot prove that to you in a randomised trial. What I can tell you is that when I sat in front of a patient I hadn’t seen in six weeks and did not recognise myself in the notes I had written — or rather, that had been written in my name — something important had already been lost.

We should be asking what that was, before we lose the ability to remember.

The author is an NHS GP in England and member of the RCGP Informatics Group. The views expressed are personal.

A note on process: the ideas, clinical experience, and arguments in this piece are entirely my own, developed over eighteen months of practice and reflection. I used Claude, an AI assistant, to help shape and structure the writing. I think that’s worth being transparent about — not least given the subject matter.

References and further reading

- Olson KD, Meeker D, Troup M, et al. Use of Ambient AI Scribes to Reduce Administrative Burden and Professional Burnout. JAMA Netw Open. 2025;8(10):e2534976. doi:10.1001/jamanetworkopen.2025.34976

- Lukac PJ, Turner W, Vangala S, Chin AT, Khalili J, Shih YT, Sarkisian C, Cheng EM, Mafi JN. Ambient AI Scribes in Clinical Practice: A Randomized Trial. NEJM AI. 2025 Dec;2(12):10.1056/aioa2501000. doi: 10.1056/aioa2501000. Epub 2025 Nov 26. PMID: 41497288; PMCID: PMC12768499.

- Kanaparthy NS, Villuendas-Rey Y, Bakare T, Diao Z, Iscoe M, Loza A, Wright D, Safranek C, Faustino IV, Brackett A, Melnick ER, Taylor RA. Real-World Evidence Synthesis of Digital Scribes Using Ambient Listening and Generative Artificial Intelligence for Clinician Documentation Workflows: Rapid Review. JMIR AI. 2025 Oct 10;4:e76743. doi: 10.2196/76743. Erratum in: doi: 10.2196/93250. PMID: 41071988; PMCID: PMC12513689.

- Brender, T.D., Celi, L.A. & Cobert, J.M. Clinical Notes as Narratives: Implications for Large Language Models in Healthcare. J GEN INTERN MED 40, 687–689 (2025). https://doi.org/10.1007/s11606-024-09093-y

- Van Tiem J, Cramer E, Iverson C, Kennelty K, Andrys N, Lee J, Knake L, Misurac J, Blum J, Reisinger HS. Listening to the note: clinician perspectives on ambient artificial intelligence scribes in medical documentation. J Am Med Inform Assoc. 2026 Feb 1;33(2):255-262. doi: 10.1093/jamia/ocaf214. PMID: 41340524; PMCID: PMC12844589.

- Fraundorf SH, Caddick ZA, Nokes-Malach TJ, Rottman BM. Cognitive perspectives on maintaining physicians' medical expertise: IV. Best practices and open questions in using testing to enhance learning and retention. Cogn Res Princ Implic. 2023 Aug 8;8(1):53. doi: 10.1186/s41235-023-00508-8. PMID: 37552437; PMCID: PMC10409703.

- Risko EF, Gilbert SJ. Cognitive Offloading. Trends Cogn Sci. 2016 Sep;20(9):676-688. doi: 10.1016/j.tics.2016.07.002. Epub 2016 Aug 16. PMID: 27542527.

Discussion about this post

Ready for more?