Decision support. ChironAI OM drafts and structures every WC artifact for the treating physician. The physician edits, attests, and signs every report, analysis, and form before it leaves the practice. ChironAI does not make a regulatory clearance claim; see Disclosures.

ChironAI OMFull capabilities inventory

Everything ChironAI OM does, in production.

Causation, treatment and UR, impairment, DWC reporting, QME/AME, IMR, billing, and closure — reasoned and drafted by a Round Table of specialist Digital Employees running on Eve-Healthcare™ F5/reasoner, decided where the law requires certainty by deterministic engines, and signed by the physician on every claim. Nine groups, one system, no link dump — the full arsenal is below.

01Agentic AI & reasoning

The reasoning is visible, verified, and never trusted blind.

Chiron leads every case. Issac assesses utilization-review denial risk on every case, no exception. Justine convenes when apportionment or mixed causation is in play; Eli convenes on billing disputes; Theo opens automatically the moment Chiron’s confidence drops below 70%. Runs in parallel, degrades gracefully, and is visible on screen — live, not a spinner.

Eve-Healthcare™ F5/reasoner

Read the architecture →

A compound, five-component reasoning architecture — a classifier, a domain-tuned clinical reasoner, and frontier reasoning slots working in concert. Not a single model behind a prompt.

Chain-of-Verification

Every specialist self-critiques before a physician ever sees the output: initial finding, then a verification pass — did I invent anything not in the record? what would opposing counsel argue? would this survive cross-examination? — then a final answer. Three passes, one determination.

Honest reasoning stream

A live, step-by-step trace of what the system is actually doing: which specialist is running, which guideline it just retrieved, which source it just found. Engineered to never fake a progress bar; the chain-of-thought itself never leaks to the transcript.

Ask the Case

Ask the record anything; the answer is grounded only in the case file and the guideline corpus, with inline citations. A hard code guardrail deletes any citation the reasoning didn’t actually retrieve, backed by an ICD-10 hallucination guard and apportionment-citation validation.

Defend This

The system argues against its own determination first — standing in as the defense QME, the UR reviewer, and the carrier. It tallies what it can answer, what it can’t yet, and where the exposure sits, then assembles a submit-ready defense packet.

Human-in-the-loop, architecturally

Physician review/override endpoints sit on every determination. Deterministic engines override the reasoning layer on the actual numbers. The IMR-eligibility classifier fails open, so a worker’s appeal window is never lost to a model error.

02Causation & forensic

The causation math is code, not a guess.

AOE/COE causation analysis

Causation →

Arising-out-of and course-of-employment narratives under Labor Code §3600, drafted from the full record and versioned from first draft to final.

§4664 prior-award offset

The apportionment offset for a prior award of permanent disability runs as a deterministic engine built on the Brodie/Strait three-prong test: exact, reproducible, versioned, and self-documenting.

Impairment engine

Whole Person Impairment under the AMA Guides, 5th Edition, with DRE/ROM method selection and deterministic AMA Combined Values math, feeding a 2005 PDRS calculation — FEC rank, age adjustment, occupation adjustment, final PD. The age/occupation adjustment currently runs a simplified table pending the full DWC schedule load.

Case-law grounding

Every apportionment and impairment narrative is anchored to the controlling authority: Escobedo, Brodie, Strait, Hikida, Almaraz/Guzman.

What-If scenario modeling

Instant, deterministic dollar-impact modeling on the case’s own AI-derived findings plus the Labor Code constants that actually govern the number — $870 per permanent-disability point, the SB 863 §4660.1 1.4 adjustment factor. Math over facts already in the record, not a live-AI simulation.

Defensible narratives

Every statement in a causation analysis traces back to the specific field in the record that produced it. The reasoning path is reconstructable years later for deposition.

03Treatment & UR

It scores the denial before the payer does.

MTUS / ACOEM alignment

Every treatment plan is checked against MTUS (California) and ACOEM (national) guidelines at the point of care — retrieved from two dozen authentic California DWC guideline documents, not a summary. Deviation surfaces with the citation and the rationale.

UR Survival Score

See the score →

Before a request for authorization goes out, the system scores its own denial probability and the downstream IMR-appeal risk, and names the evidence that needs to be attached for the request to survive utilization review the first time.

RFA lifecycle tracking

Every request for authorization tracked from submission through UR determination, with the timeline visible end to end.

§4610(g)(2) auto-authorization detection

Flags requests that qualify for automatic authorization under the statute rather than routing into a full utilization-review cycle.

Denial-risk drivers

The specific gaps behind a UR Survival Score — a missing exam finding, a guideline citation not yet on file, treatment outside the MTUS window — surfaced inline, not buried in a report.

04IMR & appeals

When UR says no, the appeal is already built.

Dubon / Bodam denial classification

Every UR denial is classified against Dubon II and Bodam before it’s routed, because that classification is what gates IMR eligibility versus a straight appeal.

IMR packet assembly

The §4610.5 independent medical review packet assembled from the case record, timed against the 30-plus-5-day mail clock.

Deadline math

Every IMR and appeal deadline computed against the California business-day and holiday calendar. Day-count specifics on QME-adjacent deadlines and record-retention windows remain under counsel review, so the system flags rather than finalizes those.

05QME / AME

The panel process runs like a state machine, not a spreadsheet.

§4628 QME report

The statute’s twelve required sections drafted and checked against a compliance checklist before the report leaves the practice.

§4062.1 / §4062.2 panel process

The qualified-medical-evaluator and agreed-medical-evaluator panel process runs as a state machine, including the Vázquez good-cause generator, which produces a byte-stable filing exhibit when a party has good cause to request a new panel.

PTP/QME reconciliation

The treating physician’s determination is reconciled line by line against the QME or AME findings, with disagreement surfaced rather than silently overwritten.

06Regulatory reporting & deadlines

Every DWC clock, tracked to the business day.

Doctor’s First Report of Occupational Injury or Illness, drafted against the 5-business-day statutory deadline.

PR-2 progress reports

Auto-drafted on the 45-day cadence or the moment a material change triggers one; the physician edits every section before signature.

P&S/MMI under §4061

Permanent-and-stationary determinations triggered by the clinical milestone, not by elapsed time, deadline-tracked and physician-attested.

Deadline engine

Every statutory clock in the claim encoded and holiday-aware against the California calendar. A daily 07:00 cron surfaces every approaching and overdue report across the practice.

AB 3030 attestation

Every AI-drafted report carries the generative-AI disclosure required by AB 3030 — non-dismissible by design, and it persists through the signed PDF.

07Billing & revenue

Coded to the fee schedule. Chased to the penalty.

OMFS coding

Official Medical Fee Schedule coding applied to every billable encounter.

ML204 page-tiering

Page-count tiering for medical-legal reports computed under ML204 rather than left to a biller’s judgment call.

§4603.2 penalty & interest

The 45-business-day payment rule tracked against every bill; penalty and interest computed automatically the moment the payer misses it.

Appeals & IBR support

Second-review and Independent Bill Review appeal packets assembled from the same billing record that generated the original claim.

E/M coding on CMS 2021 MDM

Evaluation-and-management coding leveled against the CMS 2021 Medical Decision-Making rules, not the retired time-based table.

08Case lifecycle & operations

One system runs the whole file, start to close.

Eligibility & §3600 classification

Every case classified — industrial, denied, delayed, first-aid, non-industrial — at intake, versioned as the record develops.

MPN routing & weekly sync

§4616 medical-provider-network verification, refreshed weekly from the California DWC’s public open-data feed, so a referral never routes to a network that lapsed.

Case Drift

Flags cases whose recovery is lagging the trajectory the treatment plan predicted, before the file goes stale.

Morning Rounds

An overnight-worked worklist waiting at the start of the day: what the system read, flagged, and drafted while the practice was closed.

Records that react

The moment a new document lands in the file — a QME report, a UR determination, a lab result — the case is re-read and the relevant determinations refresh.

Closure & §5410 reopening

Case closure drafted with the five-year reopening window computed and tracked, so a case never closes blind to its own reopen date.

09Trust, security & verification

Every signature is provable. Every tenant is isolated.

Public cryptographic verification

Four public, no-login, zero-PHI, rate-limited endpoints — IMR, QME, PTP-QME, closure. A SHA-256 hash binds the physician’s attestation to the exact rendered PDF, so anyone holding a document can confirm it hasn’t changed since signature.

Per-clinic database isolation

Each clinic runs on its own separately provisioned database and its own tenant Blob storage containers, with Postgres row-level security enforced across 40 tables as a second layer, not the only one.

Immutable PHI access log

Every PHI access recorded automatically, by decorator, not by developer discipline — tamper-evident by construction.

Breach detection

Failed-authentication bursts, cross-tenant access attempts, and mass-export patterns are monitored and mapped to HIPAA’s breach-notification triggers.

Physician-agreement tracking

The rate at which the signing physician agrees with Chiron’s determination is tracked over time as an operational trust metric for the practice — visible, not hidden from the people signing the reports.

Agentic, not autonomous

Forty-plus capabilities. One rule that never bends.

Every capability above takes initiative — convening specialists, scoring risk, drafting reports, computing deadlines — but none of it crosses into deciding. Deterministic engines hold the numbers the law requires to be exact. A must-review- before-final gate sits under every output. And once a physician signs, the document is cryptographically verifiable against a public endpoint — provably unaltered since attestation. That is the bounded agency a defensible workers’ compensation record demands.

Run your next claim with Chiron

See the full arsenal run on your own caseload.

Powered by Eve-Healthcare™ F5/reasoner — a compound reasoning architecture, physician-attested at every step. Read the architecture.