ajay6601/clinicalbench — explained in plain English
Analysis updated 2026-08-11 · repo last pushed 2026-04-02
Set up automated quality gates that block unsafe medical AI outputs or flag borderline ones for human review.
Run a second AI judge model as an independent reference to check agreement with your primary judge.
Inject fake medical claims into correct answers to test whether your AI judge catches hallucinations.
Configure stricter safety thresholds for high-risk contexts like emergency medicine versus general health Q&A.
| ajay6601/clinicalbench | 0verflowme/learnings | 0verflowme/r2ai | |
|---|---|---|---|
| Language | Python | Python | Python |
| Last pushed | 2026-04-02 | 2022-06-18 | 2025-11-19 |
| Maintenance | Maintained | Dormant | Quiet |
| Setup difficulty | moderate | easy | moderate |
| Complexity | 3/5 | 1/5 | 3/5 |
| Audience | pm founder | researcher | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires API keys for AI model providers and approximately $10-14 in API costs to run the full evaluation pipeline.
ClinicalBench helps you figure out whether you can trust AI to automatically catch dangerous mistakes in medical AI outputs, without a human reviewer checking every response. If you're building a clinical AI product and want to use an AI "judge" to approve or block answers before they reach patients, this project tests how reliable that judge actually is. The framework runs medical questions through several AI models, then has automated judges score each answer on four dimensions: factuality, safety, hallucination, and completeness. It validates those judge scores against known-correct answers to see whether the judges give high marks to good answers and low marks to bad ones. You can also run a second judge model as an independent reference to check agreement, and inject fake medical claims into correct answers to see if the judge catches them. A healthcare startup founder or product manager building a clinical AI feature would use this to set up automated quality gates, rules that block unsafe outputs or flag borderline ones for human review. For example, you might configure stricter thresholds for emergency medicine responses than for general health Q&A. The project includes calibrated thresholds based on real testing, so you know what tradeoff you're making between catching errors and false alarms. The results are surprisingly encouraging: the factuality judge catches nearly all wrong answers while rarely flagging correct ones, and a cheap model works almost as well as an expensive one. The hallucination judge is the weakest link, the author recommends running two models and taking the stricter score to improve it. The whole evaluation pipeline costs about $10-14 in API calls. The author openly notes the limitations: the test data is clean multiple-choice questions rather than messy real-world clinical text, and there are no physician-reviewed annotations. The framework and thresholds transfer, but you'd want to retest with data that matches your actual deployment context before trusting it in production.
ClinicalBench tests whether AI judges can reliably catch mistakes in medical AI outputs before they reach patients. It evaluates automated judges on factuality, safety, hallucination, and completeness against known-correct answers.
Mainly Python. The stack also includes Python, OpenAI API, LLM Judges.
Maintained — commit in last 6 months (last push 2026-04-02).
No license information provided, so assume all rights are reserved by the author.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly pm founder.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.