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

推荐订阅源

T
Threat Research - Cisco Blogs
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
The Register - Security
The Register - Security
A
About on SuperTechFans
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
L
LangChain Blog
N
Netflix TechBlog - Medium
量子位
博客园 - 三生石上(FineUI控件)
宝玉的分享
宝玉的分享
H
Help Net Security
D
Docker
D
DataBreaches.Net
T
Tailwind CSS Blog
阮一峰的网络日志
阮一峰的网络日志
B
Blog
博客园 - 聂微东
Apple Machine Learning Research
Apple Machine Learning Research
Google DeepMind News
Google DeepMind News
The Cloudflare Blog
F
Full Disclosure
GbyAI
GbyAI
F
Fortinet All Blogs
Last Week in AI
Last Week in AI
Y
Y Combinator Blog
人人都是产品经理
人人都是产品经理
Recent Announcements
Recent Announcements
博客园 - Franky
MongoDB | Blog
MongoDB | Blog
有赞技术团队
有赞技术团队
博客园 - 叶小钗
小众软件
小众软件
V
Visual Studio Blog
月光博客
月光博客
Stack Overflow Blog
Stack Overflow Blog
The GitHub Blog
The GitHub Blog
Recorded Future
Recorded Future
J
Java Code Geeks
雷峰网
雷峰网
P
Privacy & Cybersecurity Law Blog
C
Cisco Blogs
C
Cyber Attacks, Cyber Crime and Cyber Security
AWS News Blog
AWS News Blog
Webroot Blog
Webroot Blog
美团技术团队
N
News | PayPal Newsroom
G
Google Developers Blog
Security Archives - TechRepublic
Security Archives - TechRepublic
博客园_首页
V
Vulnerabilities – Threatpost

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
on the comparator in clinical AI
galsapir · 2026-05-07 · via Hacker News - Newest: "AI"

03 May 2026 health, evaluation

Listen to this post

0:00

0:00

a paper from Brodeur et al. (2026) has been making the rounds the past few days.1 the framing it’s traveling with is “OpenAI’s o1 correctly diagnosed 78.3% of cases in NEJM clinicopathologic conferences, outperforming human physicians.” it didn’t click for me when i first saw it, and after sitting with it for a day i think i can articulate why, from the perspective of a (ex)physician and researcher. let me get this out of the way first: it’s a thorough piece of work, and my issue isn’t with the methods.

what they did

the paper reports six experiments. five use curated clinical case vignettes: NEJM clinicopathological conferences (CPCs) for differential diagnosis and test selection, NEJM Healer cases for documenting clinical reasoning, Grey Matters cases for management reasoning, a set of landmark diagnostic cases from a 1994 study, and probabilistic reasoning cases on primary care topics. the sixth uses 76 real emergency department cases from BIDMC, with model and physician differential diagnoses scored at three touchpoints (initial triage, ER physician evaluation, admission to floor or ICU). across the experiments, OpenAI’s o1-preview is compared against GPT-4 and against physician baselines drawn from prior published studies, hundreds of physicians in total. blinding in the ED arm was robust: the two scoring physicians correctly identified AI versus human only 15.2% and 3.1% of the time. the headline result is that o1-preview meets or beats both GPT-4 and physician baselines on most tasks, with the largest gaps where information is sparsest (initial ER triage).

the central finding stopped being interesting around 2024

an arxiv preprint of essentially this work was up in december 2024.2 in 2026, with chatgpt for health, openevidence, claude in the clinic, and ambient scribes becoming standard, telling me an LLM beats a physician on a CPC is something close to telling me it beat a human at chess: it’s the water we all live in. according to the AMA’s 2026 survey, 81% of US physicians now report using AI in some form in their practice, up from 38% in 2023 and 66% in 2024.3 saying “the model outperforms physicians on curated cases” with rigor doesn’t make it interesting at this stage. the comparator that matters in 2026 is not the unaided physician, because the unaided physician is increasingly a hypothetical.

this is a long way of saying that the result framed as the paper’s headline is a 2024 finding that landed in 2026. what would have been interesting is the result the paper itself underplays.

the buried finding

on the Grey Matters management cases, physicians using GPT-4 scored a median of 41% (IQR 31 to 54). GPT-4 alone scored 42% (IQR 33 to 52). physicians without any model scored 34% (IQR 23 to 48). on the landmark diagnostic cases, physicians with GPT-4 scored a median of 76%, physicians with conventional resources 74%, GPT-4 alone 92%. the model alone outperformed the model plus physician. physicians given the tool barely outperformed physicians without it.

the paper reports these numbers and doesn’t engage with why. that “why” is the most interesting question the paper raises, and it gets a sentence. either the 2024 finding still generalizes, in which case the question worth asking is what’s happening between physicians and these tools that erases the model’s advantage. or it no longer generalizes, in which case the headline result is also dated: the comparator isn’t the unaided physician anymore, it’s the physician with the tool. either way the buried finding deserves the foreground. the accompanying Perspective by Hopkins and Cornelisse, in the same issue of Science, foregrounds it where the paper doesn’t, citing the same effect from earlier work and writing that the collaborative configuration “itself must be tested.”4

clinical vignettes are pretty bad maps for the territory

the harder thing to say, and i’ll try to say it without dunking on the methods, because you have to compare against something: a CPC, an NEJM Healer case, a USMLE question, all of these are artifacts where the messy work of clinical medicine has already been done. someone took a real patient and a real chart and a real history that didn’t quite hang together, and they did the curation: pulled out the relevant labs, summarized the timeline, decided which of the patient’s seven complaints mattered for this question. by the time you have a vignette, the answer is almost downstream of the curation, and most of the value a good physician adds is upstream of where the vignette starts.

the ED arm is the most honest part of the paper for this reason: they at least try to use unstructured data from real patients. but even there, the AI and the comparator physicians get the same pre-extracted information at three predefined touchpoints. the curation step, where a clinician at triage figures out which of the eight things a patient is reporting is the actual presenting concern and which lab value is going to matter in three hours, is invisible. i don’t think this is a fixable problem with vignette-based benchmarking. the authors themselves note in the discussion that benchmarks rely on the careful work of clinicians to “clean up” cases and may overstate AI performance on messier data. that’s the right footnote in the wrong paper.

what would have been worth asking

two questions, since the paper invites them.

what do physicians actually delegate to AI systems in 2026, and what do they keep? when i talk to colleagues, the answer is overwhelmingly “documentation, summarization, the boring parts.” very few are using these tools as differential generators in the way the paper measures. so what does 78.3% top-k accuracy on a CPC tell us about a workflow that essentially nobody is running?

what are the new failure modes of the physician plus AI duo? this is where i think the next stretch of clinical AI research lives. the buried finding above hints at one, something about the joint system performs worse than either component, and we don’t know what. is it overreliance, is it anchoring on the model’s first suggestion, is it deskilling on the tasks the model handles, is it something else entirely? a properly powered study of that question, ideally on real workflows with ambient AI in the loop, would be worth a Science paper.5

why it matters where this was published

if this had appeared in JAMA or NEJM AI, i’d shrug and move on. medical journals publish a lot of work that’s mostly a sanity check on what clinicians already suspect, and that’s fine. Science is read by people outside medicine. when a CS researcher, a physicist, or a policy person sees “performance of a large language model on the reasoning tasks of a physician” in Science in 2026, they read it as: this is the state of the art, this is where the field is. and the field has moved. ambient scribes are becoming standard. physicians are figuring out, sometimes well and sometimes badly, how to integrate these tools into real workflows. the interesting questions have shifted from “can the model do it” to “what happens when the model and the human do it together, in a real workflow, with messy data and time pressure and liability.” a Science-level platform at this moment, ideally from these same authors who have done a lot of foundational work in the area, could have been a reflection on where the field is now. instead it’s a thorough answer to a 2024 question, and the accompanying Perspective is doing more of the 2026 work than the paper itself.

i don’t think this is a bad paper. it’s a careful one, and the methodological choices are defensible inside the frame the authors chose. it’s just that the frame itself was set in 2024, and it shows.


  1. Brodeur et al., “Performance of a large language model on the reasoning tasks of a physician,” Science 392 (2026), DOI: 10.1126/science.adz4433. strictly, 78.3% is the rate at which o1-preview included the correct diagnosis somewhere in its differential. top-1 accuracy was 52%; including potentially helpful or very close diagnoses brings the figure to 97.9%. 

  2. arxiv:2412.10849, december 2024. same work; the preprint was titled “Superhuman performance of a large language model on the reasoning tasks of a physician”, with “Superhuman” dropped for the Science version. 

  3. AMA 2026 Augmented Intelligence Research survey: 81% of physicians report using AI professionally, with documentation and research summarization the most common use cases. (source) notably, 88% expressed some level of concern about AI-driven skill loss, which is the question the buried finding in this paper actually speaks to. 

  4. Hopkins and Cornelisse, “AI can reason like a physician — what comes next?”, Science 392 (2026), DOI: 10.1126/science.aeg8766. they cite Goh et al. (Nat Med 2025) on the physicians-with-GPT-4 effect and write that “determining the optimal implementation will likely require an evaluation that compares AI alone, clinician alone, and clinician with AI.” 

  5. there’s a related thread i’m leaving for another post: how the work of medicine reorganizes around these tools, which tasks get unbundled, where liability lives, who supervises what. abbott’s system of professions is the right starting point. a benchmark score is orthogonal to all of it.