Assessments · Healthcare AI

Model makers should not grade their own homework.

Protege runs independent, double-blind evaluations of healthcare AI on uncontaminated real-world patient data. Measure efficacy, cost, latency, and safety in workflows, rather than toy tasks.

The Problem

Current benchmarks are static. But in healthcare, nothing is.
Verification is the bottleneck and moat.
Christian Catalini Meta
When models start continually updating, much of AI evaluations and alignment goes out the window.
Stephanie Chan Google DeepMind
Trust and alignment are quickly becoming the most important capabilities that will differentiate agents and models.
Mark Zuckerberg Meta

Read how we partner with AI builders who care about trustworthy evaluation

Read our launch announcement

Xlue AI Evaluation

Using de-identified longitudinal patient history to predict disease

Standard Model Bio Evaluation

Double-blind eval of biomedical model for breast & lung cancer

Disease Odyssey by Protege

How well can AI identify conditions from real, de-identified patient records before diagnosis?

Current benchmarks are falling short

Existing benchmarks test on a fraction of one patient's record

Context tokens each public benchmark sends the model per case (log scale). Across 504,185 real patients, the median patient has 13 notes; the median single note is 153 tokens.

  • MedHELM 10k
  • Protege Disease Odyssey benchmark 6.9k
  • MedAgentBench 3.5k
  • HealthBench Hard 177
  • HealthBench 167
  • HealthBench Consensus 162
  • NOHARM 127

RED = Less context than median single clinical note

ORANGE = less context than median single patient

What matters once AI is deployed — and isn't measured

Public leaderboards measure preference, not outcome. Deployment replays miss the 1-in-10,000,000 failure, and treat dynamic clinical workflows as linear steps

  • Deskilling ×
  • Task aggregation ×
  • Task automation ×
  • Task deletion ×
  • KPIs that are correct ×
  • KPIs that change over time ×
  • Adherence to laws and regulations over time ×

What Trustworthy Benchmarking Looks Like

Workflows, not tasks

Tasks are not the atomic unit of study. Workflows are. Benchmarks should measure entire workflows.

Interaction is the unit

How humans and AI work together matters more than AI on its own. We should measure this interaction.

Account for spillover effects

Once deployed, indirect effects may outweigh the direct ones. Both should be measured.

Real-time measurement

Measurement must happen alongside the work, continuously.

Accurate failure reporting

Failure modes are presented so that model makers can improve their models.

Prioritized safety

Always measure the safety of the model alongside the efficacy.

Bring your model. Protege brings the real-world, de-identified data.

Bring your model

Call it by API, host it with us, or use frontier models through our zero-data-retention keys.

We bring the data

De-identified records on ~40M patients. The data never leaves your private sandbox.

Build a focused test set

Shape the test to your workflow — optionally to a specific health system or payer.

Run the evaluation

At most two runs on the held-out test set. No tuning to the answers.

Receive score, report, attestation

Publish it as a double-blind evaluation by Protege — or keep it private.

What you get

A real data corpus

Access to data you can later use for fine-tuning — never from the test set.

A credible go-to-market signal

Expand CPT codes, win health systems and payers, prove your position.

See where you fail

A clear view against frontier models, on data no model has seen.

Faqs

Evaluate with Protege

Related Articles