The global community for advancing AI in healthcare Tag @AskMedSphere to test AI models on medical cases

🌎
🥇 We evaluated Grok 4.6 on MedAgentBench, a benchmark for agentic clinical EHR tasks, and it took the top spot. Grok 4.6 posts the highest pass@1 we've measured to date, moving ahead of the previous leader, GPT-5.6 Sol, to claim first place on the leaderboard. 🏥 Grok 4.6 averages ~95.9% pass@1 (avg of 3 runs), edging out the prior best (GPT-5.6-sol at ~94.7%) and improving on Grok 4.5 by roughly 2.5 points. On a benchmark where the model acts as an autonomous agent in a simulated EHR, calling FHIR APIs to complete clinical tasks across 10 task types, the result is also remarkably consistent run to run (95.3% to 96.3%). 📊 Leaderboards: medicalsphere.ai/benchmarks
68
54
376
2,967,847
Medical Sphere retweeted
Cool to see Elon sharing our work at @MedicalSphereAI, Grok 4.6 made a pretty compelling case! 🙂 Medical Sphere is built to address the widening gap between rapidly advancing AI model capabilities and their independent and objective validation in real-world settings. And that gap is even more critical in a domain like healthcare.
Grok 4.6 takes top spot on this benchmark
3
8
514
Medical Sphere retweeted
Replying to @arkanalabs
1
2
123
We benchmarked Gemini 3.7 Flash on two medical evals: HealthBench Professional (clinician-authored cases) and MedAgentBench (agentic EHR tasks) 🏥 A clear, consistent step up from Gemini 3.6 Flash on both, strong agentic results with a 🥉 third-place finish on MedAgentBench and landing mid-pack on HealthBench Professional. HealthBench Pro: the gain is real, not noise, Gemini 3.7 Flash's worst run beat 3.6's best run across three independent runs, on both raw and length-adjusted scores. Answer style unchanged, so it's pure quality improvement. MedAgentBench: ~93% pass@1 (avg of 3× 300-task runs), up ~2.7 pts from 3.6 Flash, with gains concentrated in harder multi-step tasks like recent-lab retrieval and potassium-replacement ordering. 📊 Leaderboards: medicalsphere.ai/benchmarks
4
8
86
10,640
Medical Sphere retweeted
We benchmarked Qwen3.8-Max on HealthBench Professional, clinician-authored cases evaluating how AI models handle real medical questions. 🏥 Qwen3.8-Max lands mid-pack: well behind the frontier (Muse Spark 1.1, Claude Opus 5), and trailing Kimi-K3 among open-weight peers, though comfortably ahead of GLM-5.2. One thing stood out, it writes the longest answers of any model we've tested, by a wide margin. HealthBench penalizes verbosity the way a busy clinician would, and that costs Qwen more ranking spots than any other model once length-adjusted scores are applied. 📊 Leaderboards: medicalsphere.ai/benchmarks 🧪 HealthBench: github.com/medicalsphere/Hea…
1
1
8
746
NEJM Medical Image Challenge of the Week vs. the Medical AI Council, too easy for AI models?! 🤔👀 All models predicted Fusarium keratoplasticum, consistent with the majority vote!
1
2
8
1,394
🩺🩻 Test AI models on this medical case here: medicalsphere.ai/cases/4ecf9…
175
Medical Sphere retweeted
We put Gemini 3.6 Flash to the test on two healthcare AI benchmarks: HealthBench Professional and MedAgentBench. 🏥🩺 On HealthBench Professional, the 0.523 score makes Gemini 3.6 Flash the strongest Gemini model we’ve tested so far, ahead of Gemini 3.5 Flash (0.510) and Gemini 3.1 Pro (0.483). On MedAgentBench, its 90.0% pass@1 puts Gemini 3.6 Flash in the top five, a 2.7-point gain over Gemini 3.5 Flash (87.3%) and just behind the larger Gemini 3.1 Pro (91.3%).
4
12
796
Medical Sphere retweeted
Put together a list of NeurIPS 2026 workshops across health, biology, and scientific discovery, plus a separate tab for evals, given my obsession with benchmarking! 🏥🧬🧪 🗂️ List here: app.notion.com/p/e39e1472786… Feel free to send over anything I missed, I’ll keep the list updated! P.S. Credit to @DanielKhashabi for compiling the full workshop list: danyaljj.github.io/neurips20…
1
5
12
1,343
Want to quickly share your Medical AI Council summary with the community? We made it easy! 🩺🤖👇
4
513
Claude Opus 5's performance on MedAgentBench drops substantially compared to its predecessors, Opus 4.7 and 4.8: roughly half their success rate. 🏥 We benchmarked Opus 5 as an autonomous clinical agent across 10 EHR task types, and it landed at ~40% pass@1 (avg of 3× 300-task runs), well below both earlier Opus models on the same benchmark. We dug into why 🧵
1
1
16
2,885
The cause isn't clinical knowledge, it's agentic behavior. In ~60% of turns, Opus 5 hallucinates the API's response inside its own message (emitting a tool call and a fabricated server reply together), instead of issuing one call and waiting. Opus 4.8 did this ~7% of the time. To isolate the effect, we ran a diagnostic that ignores the fabricated text and executes only the real call. Score rises to ~68% but still short of 4.8. Retrieval tasks recover; multi-step order-writing tasks stay low (potassium replacement 7%, HbA1c ordering 23%), and it sometimes reports real patients as "not found." A capable model held back by not respecting the tool-use loop. Note: the ~40% is the leaderboard figure, same harness as every other model. The ~68% is a diagnostic only, with a temporary parser tweak, and isn't directly comparable. 📊 Leaderboards: medicalsphere.ai/benchmarks 🧪 Full pipeline: github.com/medicalsphere/Med…
5
269
Claude Opus 5 is now on HealthBench Professional. 🏥 It debuts 2nd 🥈 on overall score (0.68, mean of 3 runs) behind Muse Spark 1.1 (0.69) and ahead of GPT-5.6 Sol (0.63). On the length-adjusted score it slots into 3rd 🥉 (0.57): its responses are long enough that the length penalty costs it ~0.11, more than either Muse Spark or GPT-5.6 Sol, which moves it just behind GPT-5.6 Sol on that measure. 📊 Leaderboards: medicalsphere.ai/benchmarks 🧪 HealthBench: github.com/medicalsphere/Hea…
4
4
51
3,301
Medical Sphere retweeted
How does Moonshot AI's Kimi K3 perform on medical AI benchmarks? 🏥 To find out, we tested Kimi K3 on HealthBench Professional for open-ended clinical reasoning and MedAgentBench for agentic EHR tool use. On HealthBench Professional it ranks 3rd 🥉 (0.577), behind Muse Spark 1.1 and GPT-5.6 Sol and ahead of Claude Fable 5. On MedAgentBench it sits further back, trailing the leading models with some ground still to make up on agentic tasks.
1
2
7
4,957
A closer look at both benchmarks: 🔹HealthBench Professional: Kimi K3 keeps pace with the top models on routine clinical cases (0.77, just past GPT-5.6 Sol), but falls off on the hardest cases and on adversarial / red-teaming prompts, that's where its distance from the leaders comes from. Its scores held steady across all 3 runs. 🔹MedAgentBench: Kimi K3 handles the lookup and lab-retrieval tasks cleanly, but stumbles on the multi-step protocols that chain several tool calls under a strict output format, potassium replacement (0.57) was its weakest task. 🔹vs Kimi K2.6: a clear step up on both benchmarks, most visibly on patient lookup (0.68 → 0.97). One task moved the other way, vital-sign recording, where K2.6 was perfect and K3 slips.
1
1
239
Everything here is public, data, code, and both live leaderboards: 📊 Leaderboards: medicalsphere.ai/benchmarks 🧪 HealthBench: github.com/medicalsphere/Hea… 🤖 MedAgentBench: github.com/medicalsphere/Med… Methodology: mean of 3 runs per benchmark; HealthBench Professional graded by GPT-5.4 at low reasoning effort.
1
166
OpenAI's GPT-5.6 Sol just landed on MedAgentBench and claimed the top spot 🥇🏥 MedAgentBench is a medical benchmark of 300 test instances evaluating LLMs as autonomous clinical agents across 10 EHR task types (30 instances each).
2
3
281
A few observations from the runs: 🔹Aggregate rank hides task-level variation. No model leads on every task. The new #1 records its lowest score on HbA1c ordering, below the other three on that specific task. Winning overall means the fewest weak spots, not zero. 🔹The ranking is decided on the hard tasks. Age math, vital-sign recording and patient lookups are at or near 100% for all four. Separation comes almost entirely from multi-step write actions, ordering potassium replacement and HbA1c follow-ups, where scores swing by ~30 points. 🔹A narrow field. The top four sit within a few points of each other, with under 1 pt of run-to-run variance for most. Differences are real but small, and could shift with a handful of tasks. 🔹Failures are clinical, not formatting. All four reliably follow the tool-call protocol, near-zero invalid-action errors. Remaining misses come from wrong values or not terminating; muse-spark-1.1 most often ran to the step limit.
1
1
121