ChironAI™ OM — Occupational Medicine
Edition 02 · Generally availableOM · California workers’ comp

Be the doctor. Let Chiron run the claim.

A California workers’-comp visit asks one physician to be five people at once. ChironAI™ OM is the agentic operating system that runs the rest of the claim — causation, treatment authorisation, impairment, DWC reporting, billing and every statutory deadline — reasoned and drafted by a Round Table of Digital Employees that shows its work. You review, edit and attest.

Physician-attested · Reasoning shown on every determination · Built for California WC · Generally available since August 12, 2026

Five jobs, one visitThe problem

You trained for one of these. The claim demands all five.

The clinical work is the part you trained for, and it is the smallest part of the visit. The other four are where the hours go, where revenue leaks, and where a claim is won or lost long before anyone sees a courtroom.

  • Clinician

    diagnose and treat the injury

  • Forensic investigator

    establish work-relatedness and apportion cause

  • Regulatory clerk

    author DWC reports and beat every statutory deadline

  • Billing manager

    code to the fee schedule and chase the pay clock

  • Expert witness

    build a record that survives deposition

What is actually builtThe scale

Not a feature bolted onto a chart. An operating system for the claim.

Most tools in this market solve one step and hand you back the other seven. OM was built for the whole lifecycle, and the California statutory detail is implemented in the software rather than left to the physician to remember.

81
capability modulesNestJS domain modules, excluding infrastructure
619
API operationsHTTP route handlers across all controllers
137
data domains modelledmapped tables in the schema
67
statutes & regulations implementeddistinct section citations plus AB/SB statutes in shipped code
13
official DWC & QME formsstate PDFs bundled with field mappers
5
Digital Employees at the Round TableChiron, Justine, Eli, Issac, Theo
Agentic AI · Advanced reasoningHow it works

A specialist team, not an autocomplete.

OM runs on Eve-Healthcare f5/reasoner — a composed reasoning system rather than a single model. What matters clinically is not the engine underneath, but that the work is divided among specialists, shown as it happens, and grounded in sources you can check.

The Round Table

Five specialists. The right ones, on the right case.

Chiron leads every case. Issac assesses utilization-review and IMR exposure. Justine convenes when apportionment or mixed causation is in play, Eli when there is a billing dispute to reason through, and Theo on questions of ethics and fairness. Specialists convene on the cases that need them and stay out of the ones that do not.

Glass-box reasoning

It shows the work while it works.

A live, step-by-step trace of what is actually happening — which specialist is running, which guideline was retrieved, which source was found, and honestly when a step returns nothing. Reasoning visibility is on by default. It is the difference between a clinical instrument and a black box.

Work that outlives the tab

Start it, walk away, come back to it finished.

Long-running work runs on the server, not in your browser. Drop a stack of records, move to another patient, sign out and come back — it keeps going, and the reasoning trace is waiting where you left it rather than lost with the connection.

Grounded, never invented

Cited, or it does not say it.

Determinations are drafted against retrieved sources and the citations are validated. Where the system is not confident enough to route a document or support a finding, it abstains and says so — a confident wrong answer in a medical-legal record costs far more than a question.

Intake to closureThe whole claim

Eight phases. One system. No handoff to a spreadsheet.

  1. 01

    Front door

    Eligibility, MPN network rules under §4616, §4600 predesignation routing, claim-type determination, and intake that reads the documents you were sent instead of asking you to retype them.

  2. 02

    Exam room

    Encounters, work status and restrictions, a plan of care grounded in MTUS, dictation, and a treatment plan drafted from the record for the physician to edit and sign.

  3. 03

    Causation & apportionment

    AOE/COE reasoning with the evidence cited, and statutory apportionment under §§4663 and 4664 — with the citations validated rather than asserted.

  4. 04

    Treatment authorisation

    DWC Form RFA end to end, utilization review tracked on the §4610 clock, denial exposure assessed before you file, and IMR appeal packets when a denial has to be fought.

  5. 05

    Impairment rating

    AMA Guides Fifth Edition — range-of-motion tables, hearing loss, pain add-on, combined values — plus PDRS rating and Almaraz/Guzman analysis where a strict rating does not fit the patient.

  6. 06

    Reporting & med-legal

    Doctor’s First Report, PR-2 on cadence or material change, P&S/MMI, QME panels and evaluations, information exchange under §4062.3, and per-recipient proof of service.

  7. 07

    Billing & revenue

    OMFS coding, the §4603.2 45-working-day pay clock with its penalty and interest engine, explanation-of-review handling, bill review and appeals.

  8. 08

    Closure & defensibility

    Case closure with an attested packet, a sourced chronology that preserves contradictions rather than averaging them away, and defensibility analysis before a deposition rather than after.

DefensibilityWhy it holds up

Every determination has your name on it. That is the design, not a limitation.

The physician decides. Always.

Chiron reads, reasons and drafts. It does not diagnose, determine or treat. Every substantive output is reviewed, edited and attested by the treating physician before it becomes part of the record — enforced in the software, not promised in a policy.

Built for the disclosure rules, not retrofitted

AI authorship is disclosed where it is material, decision authority stays with the clinician, and the persona never implies licensure. These are architectural properties of the system rather than copy on a page.

Tenant-isolated by construction

Row-level isolation in the database, role-based authorisation on clinical and financial operations, per-case access control, and an immutable audit trail on every mutation.

Your data is not training data

Customer clinical data does not enter a training pipeline. There is no path by which it could — the property is enforced at the dataset layer rather than asserted as a policy that could later be revised.

The full posture, including what we do not claim, is in the Trust Center.

Next stepOM

See it run a real claim.

The fastest way to judge this is to watch the Round Table convene on a case that looks like yours — the reasoning, the citations, the drafted report, and the point where it hands the decision back to you.