Development report · November 2026

A physician-first decision-support tool for behavioral health utilization review

UM Review takes a submitted clinical review and gives the physician advisor an organized, criteria-referenced picture of the case, a proposed decision, and the documentation written both ways. Its purpose is to enrich the information in front of a physician, not to automate utilization management.

Principles

The six design commitments the tool is built around

These determine how the tool behaves, and they are the standard a plan, a regulator or a reviewer should measure it against.

01

The physician decides

When the physician sets a decision, the tool writes to it. When the submitted review proposes one, the tool uses that and says so. Only when neither exists does it propose a decision of its own, labelled as a proposal. Who decided is recorded on every output. This is the shape California's SB 1120 requires: AI may inform a medical-necessity determination; a physician makes it.

02

Good enough, on purpose

The target is a supportable, transparent decision with documentation a physician can edit in a minute, not a tool that is right on its own. A physician who changes the proposal for reasons that do not generalize has not found an error; they have done their job with better information in front of them.

03

One format, every time

Every review has the same four parts, in the same order, with the same fixed sentences: a verdict for the physician, the criteria attestation, structured notes whose Advisor Review always states the findings against the decision before the findings that decide it, and a member letter in plain language. The model writes the prose; it never writes the fixed sentences.

04

Criteria you can read

The reasoning runs on service profiles the author wrote and owns, with shared rules on fairness and proportionality. They can be read, edited and published without a license. Licensed criteria a review names (ASAM, LOCUS, InterQual) appear as labels, which matters because ASAM's terms prohibit entering its criteria into AI systems at all.

05

Rules live in code and leave a trace

The mechanical parts of review, such as how appealed days are counted, how long a single case agreement runs, and what happens when a person's needs exceed the level requested, are applied by code, identically every time. Whenever a rule changes what the model proposed, or cannot be applied, a flag beside the decision says so.

06

Built to be audited

Every case leaves a record of who decided, what the referral proposed, what the model proposed before any rule applied, which rules acted, and which version of the tool and model produced it. A plan can measure its own override rates and anchoring from those fields; an auditor can check a decision against the criteria without the model in the room.

What it looks like

The tool on a synthetic case

Synthetic case · Partial hospitalization · AdmissionDenied, as proposed in the submitted review

The whole pass on one synthetic case: the empty interface, the submitted review pasted in, the facts for and against lifted out of the record, one call to the model, and the review as it comes back, with the Advisor Review stating the findings against the decision before the findings that decide it, and the member letter in plain language. The wait for the model is shortened here; in practice it is about seventeen seconds. Nothing in it is a real member.

What it does well

Results of two automated evaluations on 120 synthetic cases

The two evaluations used different scorers and different standards, and they agree on the shape of the result: the tool reproduces the record faithfully, reaches decisions a second reader finds supportable, and makes its reasoning visible enough that its errors can be found and corrected.

01 · Fidelity

98.8%

factual fidelity, author-calibrated scoring, 108 cases; decision-making 94.4%

Fidelity to the record

The clinical review it writes is a condensation of the record with the contradictions left in, which is what a physician needs to read and what an auditor needs to check.

02 · Supportability

96%

of decisions matched a second model's independent reading, 55 of 57 held-out cases

Agreement with an independent reading

A model from a different vendor read each case cold, reached its own decision, then graded the output. It rated the decision line as fully supported by the record in 51 of 57. Single case agreements were the weakest category, and the one where it found a defect rather than a judgment call.

03 · Correctability

6 → 3

major defects on the same 60 cases, one version to the next; decision agreement 86% → 96%

Correction between versions

The grader found a reasoning pattern the author had missed: denials that left a member with less care when their needs exceeded the level requested. It was corrected in a day as a rule, not by prompt-tuning, and the grader confirmed the fix on the same cases. A tool whose mistakes are legible to a second reader is one that can be governed.

Methods, the grading rubric, per-criterion scores, the version log and case-level results are in the full development report, shared on request.

Limitations

What these results do not establish

Collaborate

What is needed for a human validation study

01

Physician reviewers and raters

Behavioral health physician advisors to review cases in both arms, and raters to score documentation blind. Paid.

02

A plan or a regulator willing to look

A health plan, delegated review vendor or regulator that wants to see a physician-first, auditable tool on its own synthetic or de-identified cases.

03

A nonprofit criteria owner

A partner so the same format and audit record can run on criteria a plan already uses.

04

Funding for the human study

The study is small. Reviewer time is the cost.

Gerrit van Schalkwyk, MD

Child and adolescent psychiatrist; payer-side physician advisor in behavioral health utilization management

Gerrit@resilientmindsmd.com