Same Verdict, Different Reasons: LLM-as-a-Judge and Clinician Disagreement on Medical Chatbot Completeness
Organizations: Data Science and AI Institute, Johns Hopkins University
Abstract
LLM-as-a-Judge frameworks are increasingly trusted to automate evaluation in place of human experts, yet their reliability in high-stakes medical contexts remains unproven. We stress-test this assumption for detecting incomplete patient-facing medical responses, evaluating three rubric granularities (General-Likert, Analytical-Rubric, Dynamic-Checklist) and three backbone models across two clinician-annotated datasets, including HealthBench, the largest publicly available benchmark for medical response evaluation. LLM Judges discriminate complete from incomplete responses at and slightly above near chance (AUC --); at the threshold required to recall of incomplete responses, clinicians must still review the vast majority of the dataset, offering no triage utility. Even when model and clinician verdicts agree, they rarely cite the same explanation; and when they diverge, false positives stem from over-flagging non-essential gaps while false negatives reflect outright detection failures. These results reveal that LLM Judges and clinicians apply fundamentally different completeness standards; a finding that undermines their use as autonomous evaluators or triage filters in clinical settings.
Figures & tables
| LLaMA 3.3-70B | OpenBioLLM | GPT-5 Mini | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Dataset | Metric | F1 | Prec | Rec | AUC | F1 | Prec | Rec | AUC | F1 | Prec | Rec | AUC |
| HealthBench | Dynamic-Checklist ∗ | 0.89 | 0.97 | 0.82 | 0.91 | 0.91 | 0.90 | 0.93 | 0.85 | 0.93 | 0.96 | 0.91 | 0.93 |
| Analytical-Rubric | 0.42 | 0.91 | 0.27 | 0.65 | 0.20 | 0.84 | 0.11 | 0.53 | 0.76 | 0.86 | 0.68 | 0.66 | |
| Analytical-Rubric (FSS) | 0.75 | 0.83 | 0.68 | 0.64 | 0.65 | 0.82 | 0.54 | 0.59 | 0.83 | 0.81 | 0.84 | 0.62 | |
| General-Likert | 0.07 | 0.95 | 0.04 | 0.53 | 0.01 | 0.83 | 0.01 | 0.50 | 0.54 | 0.89 | 0.39 | 0.64 | |
| General-Likert (FSS) | 0.61 | 0.85 | 0.47 | 0.63 | 0.39 | 0.82 | 0.26 | 0.54 | 0.67 | 0.82 | 0.57 | 0.58 | |
Appendix figures & tables17 assets
Supplementary material from the paper’s appendix.
Appendix
| Metric Name | Definition | Annotation Setup |
|---|---|---|
| Completeness ( Xie et al., 2024 ) | Amount of salient details in the [generated answer] as recalled from a reference | Fine-grained checklist of the claims in the generated answer from the original response |
| Completeness ( Wang et al., 2024b ) | How well the generated text captures the key ideas of the reference | Rating Scale of 1-5 5 5 5 Wang et al. (2024b) use human evaluation to verify their automated approach, though the annotation details are not specified. |
| Thoroughness ( Allen et al., 2024 ) | Answers all questions posed by a patient | - |
| Completeness ∗ ( Arora et al., 2025 ) | All important information needed to be safe and helpful to the user. Even if accurate, a response that is incomplete (e.g., omitting key steps or red flags) can still result in low-quality advice or harm. | Fine-grained checklist of required information for a question |
| Informativeness ∗ ( Xu et al., 2024 ) | Comprehensive: answers include additional information beyond the expectations | Rating Scale of (0) incomplete (1) adequate (2) comprehensive |
| Completeness ∗ ( Yarmohammadi et al., 2025 ) | A complete answer contains all relevant medical information for the patient based on the provided question. Incomplete responses contain omissions, which are defined as important information whose omission could cause clinical harm to the patient. | List of omissions and their severity levels |
| Code | Name | Description |
| False Positive categories (Model = Incomplete, Clinician = Complete) | ||
| FP01 | Over-flags minor gaps | The model identifies omissions the clinician considers non-essential or supplementary. The core clinical question is safely answered; the model applies a completeness standard stricter than clinical safety requires. |
| FP02 | Demands depth beyond patient-facing scope | The model expects provider-level or specialist-level detail (e.g., exact risk percentages, pharmacokinetics, procedure-specific protocols) that the clinician considers beyond what a patient-facing answer needs, especially for underspecified questions. |
| FP03 | Misapplies safety-netting to non-urgent context | The model inserts emergency or red-flag framing into questions that are informational, low-acuity, or underspecified. The clinician judges the answer adequate for the question as asked; the model penalizes for missing escalation criteria when no emergency context exists. |
| FP04 | Misinterprets question intent / misapplies rubric | The model fundamentally misunderstands what the question is asking or incorrectly applies evaluation criteria (e.g., penalizing an appropriate doctor referral for not directly answering, or evaluating against criteria unrelated to the question). |
| False Negative categories (Model = Complete, Clinician = Incomplete) | ||
LLM-as-a-Judge
Large language model (LLM)-as-a-judge research uses language models to score, compare, and verify AI outputs as scalable alternatives to human evaluation.
See all 555 papers