OpenMTB-Audit: Exposing Over-Refusal and Clinical Expert Perspectives in LLM-Based Molecular Tumor Board Safety Evaluation

cs.AI cs.LG Negin Ashrafi, Jia Luo, Stacey M. Frumm, Roxana Daneshjou · Oct 1, 2026
Local to this browser
What it does
Molecular tumor boards must distinguish truly unsupported therapies from evidence-supported recommendations that still require oncologist review because of incomplete clinical information or poor performance status. This paper introduces...
Why it matters
2% accuracy. The work matters because label collapse in high-stakes oncology auditing can conceal unsafe endorsements or inappropriately block appropriate treatments.
Main concern
The paper makes a timely contribution by framing clinical over-refusal as a label-calibration failure in molecular tumor board auditing and by releasing an open benchmark. However, its conclusions are constrained by a small,...
Community signal
0
0 up · 0 down
Sign in to vote with arrows
AI Review AI reviewed
Plain-language introduction

Molecular tumor boards must distinguish truly unsupported therapies from evidence-supported recommendations that still require oncologist review because of incomplete clinical information or poor performance status. This paper introduces OpenMTB-Audit, a 500-case synthetic NSCLC benchmark with four safety labels, and exposes pervasive over-refusal: every tested LLM configuration collapses the Partially Supported label, misclassifying valid-but-caveated therapies as either Unsupported or Supported. To address this, the authors propose MTB-AuditAgent, a deterministic seven-module pipeline that reduces over-refusal to 6.7% and achieves 91.2% accuracy. The work matters because label collapse in high-stakes oncology auditing can conceal unsafe endorsements or inappropriately block appropriate treatments.

Critical review
Verdict
Bottom line

The paper makes a timely contribution by framing clinical over-refusal as a label-calibration failure in molecular tumor board auditing and by releasing an open benchmark. However, its conclusions are constrained by a small, non-independent expert study—one oncologist agreed perfectly with the benchmark labels, suggesting possible involvement in their design—and by evaluating only two GPT-4o family models. The deterministic MTB-AuditAgent is tested on the same synthetic benchmark it was co-designed with, and the authors correctly caution that this shared provenance means the results should not be treated as independent clinical validation. While the four-label taxonomy and module ablations are instructive, the gains may reflect tuning to the benchmark rather than generalizable clinical reasoning.

“All LLM configurations failed to retain the Partially Supported label in 83.3–100% of true Partially Supported cases, achieving high aggregate safety scores through label collapse rather than clinically calibrated reasoning.”
paper · Abstract
“Oncologist A demonstrated complete agreement with the benchmark reference labels (50/50, κ=1.000), showing that the study-defined labeling framework can be applied consistently by an independent expert.”
paper · Section 8.2
“Benchmark labels, evidence knowledge base, and decision rules share common design provenance, so performance on OpenMTB-Audit should not be interpreted as independent clinical validation.”
paper · Section 10
What holds up

The strongest element is the precise definition of clinical over-refusal as the systematic failure to preserve the Partially Supported category, which captures a genuine safety gap that aggregate metrics miss. The deterministic seven-module design separates evidence verification, missing-information detection, safety classification, and abstention, and the ablation study shows that these modules serve complementary functions rather than providing interchangeable gains. The fully open-source benchmark, evaluation code, and prompts support reproducible follow-up work.

“We define this as clinical over-refusal—the systematic failure to correctly classify Partially Supported cases, whether misclassified as Unsupported (conservative escalation) or as Supported (without required caveats).”
paper · Section 2.3
“Removing the Evidence Verifier (M3) caused the largest drop (−55.0 points), confirming that evidence concordance is the principal determinant of safety.”
paper · Section 9.2
Main concerns

The principal limitation is circularity between the benchmark and the proposed agent. MTB-AuditAgent’s rules and evidence base were built using the same public sources and label definitions that shape the benchmark, and the 50-case expert subset was used to refine the agent, so the reported concordance is post-hoc rather than prospective validation. The authors acknowledge this but still present benchmark accuracy as the primary evidence of superiority.

Additional gaps restrict generalizability. Only GPT-4o and GPT-4o-mini are tested, so the claim that 'all LLM configurations' over-refuse applies to a narrow model family. The expert study is tiny (n=50, enriched for hard cases), and one annotator’s perfect agreement with the benchmark undermines its intended independence. The custom Safety Score formula $\text{SS}=100\times(0.30(1-R_{\text{miss}})+0.20\text{F1}_{\text{abs}}+0.20R_{\text{MI}}+0.15C_{\text{WD}}+0.10C_{\text{Hall}}+0.05C_{\text{OC}})$ embeds subjective harm weights, and the deterministic approach may not scale to other cancer types or evolving guidelines without extensive manual curation.

“Benchmark labels, evidence knowledge base, and decision rules share common design provenance, so performance on OpenMTB-Audit should not be interpreted as independent clinical validation.”
paper · Section 10
“Because the 50-case expert subset informed MTB-AuditAgent refinement, reported agreement reflects post-refinement concordance rather than prospective external validation, and independent multi-institutional validation is needed.”
paper · Section 8.1
“Only GPT-4o and GPT-4o-mini were evaluated; open-source and medical-specialized LLMs should be included to determine whether over-refusal generalizes across model families.”
paper · Section 10
Evidence and comparison

The evidence supports the existence of over-refusal on the evaluated benchmark, but the paper does not compare against other rule-based or medical-specialized LLM baselines, so the gap between MTB-AuditAgent and alternative clinical systems remains unclear. Related work is cited accurately: CARES and Health-ORSC-Bench do identify over-refusal in medical contexts, and the broader LLM safety literature is represented fairly. We verified that OR-Bench is a large-scale over-refusal benchmark and that CARES evaluates both harmful compliance and false-positive refusals in healthcare, matching the authors’ descriptions. However, the paper’s scope is limited to synthetic NSCLC cases, and no real-world MTB retrospective or prospective validation is provided, so the clinical translation of the findings is still speculative.

“Prior work has largely emphasized recommendation correctness, evidence retrieval, or detection of clearly unsafe outputs, with less attention to intermediate cases in which a therapy is evidence-supported but requires clinical review.”
paper · Section 1
“This study proposes a novel method for automatically generating large-scale over-refusal datasets. Leveraging this technique, we introduce OR-Bench, the first large-scale over-refusal benchmark.”
“Our analysis reveals that many state-of-the-art LLMs remain vulnerable to jailbreaks that subtly rephrase harmful prompts, while also over-refusing safe but atypically phrased queries.”
Chen et al., CARES · Abstract
Reproducibility

The authors release benchmark cases, prompts, evaluation code, and predictions on GitHub, which is a strong reproducibility practice. LLM baseline hyperparameters are reported (temperature=0, max_tokens=512). Yet independent reproduction of MTB-AuditAgent is hampered by incomplete specification of the deterministic rule set: while the seven modules are described conceptually, the exact decision logic, thresholds, and rule tables are not provided in the paper. Moreover, the benchmark lacks a held-out test set that was never exposed during system development, and the expert annotation subset was used for refinement, meaning external teams would need to assemble a new clinical panel to reproduce the concordance claims. The reliance on fully synthetic cases simplifies data sharing but also reduces external validity.

“Full prompts, evaluation code, and benchmark data are available at https://github.com/Negiiinx/OpenMTB-Audit.”
paper · Section 5
“Because the 50-case expert subset informed MTB-AuditAgent refinement, reported agreement reflects post-refinement concordance rather than prospective external validation...”
paper · Section 8.1
Abstract

Molecular tumor boards integrate genomic findings, clinical context, and therapeutic evidence to support precision oncology. As AI enters this workflow, a key safety challenge is distinguishing truly unsupported recommendations from evidence-supported options that still require oncologist review because of incomplete information, poor ECOG performance status, or other clinical caveats. We introduce OpenMTB-Audit, an open-source benchmark of 500 synthetic non-small cell lung cancer cases spanning five adversarial error categories and four safety labels: Supported, Partially Supported, Unsupported, and Insufficient Information. Across eight large language model configurations, we identify pervasive over-refusal: all LLM configurations failed to retain the Partially Supported label in 83.3-100% of true Partially Supported cases, achieving high aggregate safety scores through label collapse rather than clinically calibrated reasoning. To address this limitation, we developed MTB-AuditAgent, a deterministic seven-module framework separating evidence verification, missing-information detection, safety classification, and abstention. It reduces over-refusal to 6.7% and achieves 91.2% accuracy (95% CI: 88.6-93.6%). A two-oncologist annotation study found disagreement concentrated at the boundary between information sufficiency and treatment optimization, underscoring the need to preserve clinically meaningful distinctions.

Challenge the Review

Pick a starting point or write your own. Challenges run in the background, so you can keep reading while the AI investigates.

No challenges yet. Disagree with the review? Ask the AI to revisit a specific claim.