Independent AI evaluation platform Artificial Analysis officially released HealthBench Professional alongside the length-normalized MLCR-AA index (@ArtificialAnlys). The benchmark revealed a pervasive industry blindspot: LLM-as-a-Judge evaluations suffer from acute 'verbosity bias', disproportionately rewarding longer generations regardless of medical conciseness. In raw HealthBench scoring where Anthropic outputs were 4–6x longer, Claude Opus 5.5 led at 71.4%. However, once length bias was scientifically normalized via MLCR-AA, GPT-6 Astra (max) tied Claude Sonnet 5.5 for #1, while Claude Opus 5.5 plummeted from #1 down to #6, setting a new rigorous standard for medical model evaluation.
Key Takeaways
- ✓Artificial Analysis unveils HealthBench Professional and the length-calibrated MLCR-AA benchmark
- ✓Exposes pervasive verbosity bias where evaluation judges disproportionately favor verbose outputs (Anthropic outputs averaged 4–6x longer)
- ✓Raw HealthBench placed Claude Opus 5.5 at #1 (71.4%) ahead of Sonnet 5.5 (70.8%) and GPT-6 Astra (69.7%)
- ✓Length-adjusted MLCR-AA shows GPT-6 Astra (max) tying Sonnet 5.5 for #1, while Opus 5.5 plummets from #1 to #6

Key Decision Metrics at a Glance
Turn your technical choice into a development budget
Compare 40 dev plans & simulate token costs vs $20/mo subscriptions
Project Links & Resources
Direct AccessIn-Depth Technical Analysis
Background and the Problem
As frontier AI models are integrated into clinical triage, medical record synthesis, and differential diagnosis, rigorous evaluation of healthcare reasoning is critical. However, modern automated evaluation pipelines rely extensively on LLM-as-a-Judge frameworks. This paradigm carries a systemic, unaddressed flaw: Verbosity Bias. Automated judges consistently award higher scores to longer, structurally elaborate answers regardless of medical conciseness or clinical necessity. In high-stakes emergency room triage, bloated answers that bury vital warnings beneath repetitive prose constitute active patient safety risks. To expose and eliminate this distortion, independent evaluation platform Artificial Analysis released HealthBench Professional alongside the length-adjusted MLCR-AA benchmark (@ArtificialAnlys).
Architecture and How It Works
- HealthBench Professional Clinical Protocol:
- Spans complex differential pathology, pharmacovigilance, contraindication detection, and guideline compliance across 2,000+ real-world clinical patient cases;
- Length-Adjusted MLCR-AA Normalization:
- Decouples raw word count from diagnostic efficacy by implementing a marginal information density metric per token;
- Penalizes repetitive boilerplate explanations that fail to introduce distinct, verified clinical assertions;
- Information Density Auditing:
- Directly measures how effectively models distill actionable insights under ambiguity without burdening physicians with redundant text.
Benchmarks and Measured Results
The comparative findings revealed dramatic ranking inversions (verified via official benchmark telemetry):
- Raw HealthBench Scoring (Distorted by Verbosity):
- Anthropic model generations were found to be 4–6x longer on average than competing models;
- Buoyed by expansive length, Claude Opus 5.5 scored 71.4%, holding #1 ahead of Sonnet 5.5 (70.8%) and GPT-6 Astra (69.7%);
- Length-Adjusted MLCR-AA Scoring (Normalized Ground Truth):
- When length bias was systematically neutralized, GPT-6 Astra (max) and Claude Sonnet 5.5 tied for the #1 position globally;
- Claude Opus 5.5 plummeted from #1 down to #6, proving that its raw lead was largely an artifact of verbose, dilutive formatting rather than superior medical reasoning.
Getting Started for Developers
- Benchmark Access: Available on Artificial Analysis (
https://artificialanalysis.ai); - Clinical AI Blueprint: Healthcare engineering teams building medical copilots must reject uncalibrated raw LLM benchmarks. SFT and RLHF pipelines must incorporate strict brevity and density penalties to ensure clinical recommendations remain concise, actionable, and free of deceptive filler.
Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.
Discussion & Comments
0Sign in to join the discussion
Connect with AI developers to exchange benchmark insights.