Guide
Does California require a human to review AI claim denials? (SB 1120)
What SB 1120 actually says
SB 1120 amended California's Knox-Keene Act (Health and Safety Code § 1367.01) and the parallel Insurance Code provision, which govern health care service plans and disability insurers. When such a payer uses "artificial intelligence, algorithm, or other software tool" for utilization review or utilization management, the law requires, among other things, that:
- A determination of medical necessity — the decision to approve, modify, deny, or delay a service based on medical necessity — is made only by a licensed physician or a qualified health care professional competent to evaluate the specific clinical issues. The AI tool cannot supplant that human judgment.
- The tool bases any determination on the enrollee's own medical history and individual clinical circumstances, not solely on a group dataset.
- The tool is fairly and equitably applied, does not discriminate, and is periodically reviewed and audited for accuracy, reliability, and compliance.
- The tool's use is disclosed and open to inspection by the regulator (the Department of Managed Health Care, or the Department of Insurance for disability insurers).
The through-line is accountability: AI may assist, but a licensed human owns the medical-necessity decision and the payer must be able to show it.
What the law does not do
It is easy to overstate SB 1120. To stay accurate:
- It is not a blanket "a human must touch every AI decision" rule. It targets medical-necessity determinations in utilization review. Administrative or eligibility steps that don't turn on medical necessity are a different matter.
- It applies to California health plans and disability insurers regulated under Knox-Keene and the Insurance Code — not to every insurer, every line of business, or every state. Other lines (for example, life insurance) and other states' rules are governed separately.
- It does not outlaw AI in utilization review. Payers may use these tools; they simply cannot let the tool make the medical-necessity call unsupervised.
Treat this page as a plain-language explainer, not legal advice. For how the statute applies to a specific program, consult qualified counsel.
Why this is hard to prove after the fact
A payer can have a compliant policy and still struggle to demonstrate compliance. When a denial is challenged — by a regulator, an appeal, or in litigation — the question becomes: who reviewed this specific decision, were they qualified, and what did they see? If the answer lives in scattered logs, screenshots, and email, it is slow and contestable to reconstruct. The mandate is really a recordkeeping problem: every AI-assisted denial needs a durable, tamper-evident record that a named, credentialed human stood behind it.
How a human-in-the-loop record demonstrates compliance
HandInLoop is a verification layer, not an adjudicator: it does not decide medical necessity. What it provides is the human-in-the-loop workflow and the audit record the mandate implies:
- A denial can never auto-issue. When an AI-assisted decision proposes to deny or pend care, the job is always routed to human review — it cannot be finalized by the model alone.
- A credentialed human attests. To complete a denial, the reviewer records who they are and their qualification — name, credential type, license number, and jurisdiction — captured as a required attestation on the decision.
- The attestation is cryptographically bound. That "reviewed by licensed [X]" record is embedded in an Ed25519-signed Proof Object, so the signature binds the decision to the human who made it. Anyone can verify it offline against a public key — no trust in HandInLoop required.
- Everything is on the audit trail. The result shows what the AI proposed, that a licensed human reviewed it, and who that was — the exact chain SB 1120 asks a payer to be able to produce.
Note that this attestation is currently self-declared by the reviewer rather than checked against a licensing board — it records and signs the credential the reviewer supplies. That is enough to establish an auditable, tamper-evident chain of accountability; board-level verification is a separate control.
Doing this with HandInLoop
HandInLoop runs the loop as a service: AI extracts and scores the claim, any proposed denial or pend is forced to a human, the reviewer attests with their credential, and a signed, verifiable decision record comes back — showing that a licensed human, not a model, owned the call. It's a clean fit for the accountability SB 1120 requires, demoed today on synthetic and de-identified claims.