This site is published by Medrecords AI, which makes 1 of the products it covers. We say which one wherever it appears. How we handle that.

AI for QME

The QME audit trail for AI use

By Ahmed Jemaa, Co-Founder and CEO of Medrecords AI. Updated .

Short version: keep a 1-page file note for every QME report where AI touched the file. It records which tool ran, what it produced, which pages you checked, what you wrote yourself and when you signed. File it with the report and keep both for 5 years, the period 8 CCR 39.5(a) sets for the report itself.

Limits: Not legal or billing advice. California rules are quoted as read on 2026-11-19 from dir.ca.gov; verify the current text there before you bill, sign or serve, and ask counsel about your case.

Why a QME needs a file note, not just the tool's log

2 rules make the file behind a report matter:

An AI vendor's activity log helps, but it shows what the software did, not what you did. It will not show that you read pages the tool never flagged, or that you rewrote a paragraph. The file note covers the physician's side.

The 12 entries

#EntryWhat to writeRule it supports
1Records receivedDate each batch arrived, who sent it, declared page count, declaration present or missing8 CCR 35(i), 41(c)(2); DWC checklist
2Late recordsAny batch received more than 10 days after the exam, and what you did8 CCR 35(i)
3Tool and versionApplication name, version or model shown in the product, plan with a BAADWC checklist
4Run date and inputDate run; which batches went in; total pagesOur practice
5Output keptWhat the tool produced (index, chronology, excerpts) and where the export is saved8 CCR 10682(b)(4)
6Your readWhich records you read in full; which you skimmed with reason8 CCR 41(c)(2)
7Excerpt checksNumber of cited excerpts you opened against the page; how many matchedOur practice
8CorrectionsEach tool error you found, with the page, and the fixOur practice
9Staff helpName, qualifications and task of each person who helped beyond typingDWC checklist
10AuthorshipStatement that the record summary, discussion and conclusions were written by you; transcription tool if any8 CCR 41(c)(2), (c)(7)
11Report and signing datesExam date, date ready to sign, date signed, county8 CCR 41(c)(6), 35.5(b)
12Service and retentionDate served, form used, where the signed copy and this note are stored, destroy-after date8 CCR 36, 38(a), 39.5(a)

Rules captured 2026-11-12 from 8 CCR 39.5, 8 CCR 60, 8 CCR 35 and 8 CCR 41. The 12 entries are our design; no rule prescribes a log format.

A synthetic file note

Synthetic example, no real patient, no real case. A panel QME in orthopedics evaluates a warehouse worker with a claimed lumbar injury. 2 record batches arrive, 1 late.

FILE NOTE: AI USE AND AUTHORSHIP Internal file Q-2026-0412 (synthetic) 1 Records Batch A from defense, rec'd 2026-09-02, declared 1,184 pp, declaration present. Batch B from applicant atty, rec'd 2026-09-08, declared 236 pp, declaration present. 2 Late Batch C (PT notes) rec'd 2026-09-29, 19 days after exam. Noted per 35(i); supplemental offered. 3 Tool [Application, version shown in app], plan covered by BAA signed 2026-03-14. 4 Run 2026-09-09; input A+B, 1,420 pp; 61 exact duplicate pages flagged. 5 Output Index + dated chronology, 412 entries with page cites. Export: /cases/Q-0412/ai-export-0909.pdf 6 Read Read in full: MRI reports, ortho consults, 2 prior PR-2s, job description, depo excerpt. Skimmed: pharmacy logs (no entries relevant to lumbar treatment). 7 Checks Opened 88 cited entries against the page: 85 matched. 8 Fixes p. 644 visit dated 2021-05-03 in tool, page shows 2022-05-03. Fixed. p. 901 "denies prior back pain" in tool, page says "reports prior back pain 2017". Fixed. p. 1,212 MRI level L4-5 in tool, page says L5-S1. Fixed. 9 Staff None beyond scheduling and typing. 10 Author Summary of records, discussion, causation, apportionment and WPI written by me. Dictation transcribed by [transcription tool]; transcript checked line by line. 11 Dates Exam 2026-09-10. Ready to sign 2026-10-06. Signed 2026-10-06, [county]. 12 Service Served 2026-10-07, Form 122. Report + this note stored /cases/Q-0412/. Keep to 2031-10-07.

In this synthetic file the tool got 3 of 88 checked entries wrong, and 1 was a flipped negative on prior back pain, which goes straight to apportionment. That is why the note counts checks and lists fixes rather than saying "verified".

When the note gets written

When each file note entry is written, from records received to service A timeline from records received to report served within 30 days of the exam. Entries 1 and 2 at records receipt, 3 to 5 at the AI run, 6 to 8 during the read and checks, 9 and 10 while writing, 11 at signing, 12 at service. The note is filed with the report and kept 5 years under 8 CCR 39.5. Records inAI runRead, checkWriteSignServe entries 1, 2entries 3 to 5entries 6 to 8entries 9, 10entry 11entry 12 Exam to service: 30 days unless extended (8 CCR 38(a)). Keep report and note 5 years (8 CCR 39.5(a)).
Figure 1. Write each entry when it happens. A note reconstructed after a challenge is worth much less than one dated as you went.

What to ask an AI vendor for

Your note is only as good as what the tool lets you keep. Before you rely on a tool for QME files, confirm:

  1. You can export the output with page citations as a file you keep, not only view it in the app.
  2. The product shows a version or model identifier you can write down.
  3. Every extracted fact links to its source page, so entry 7 takes minutes, not hours.
  4. A BAA is signed before the first upload, and records are not used to train models.
  5. You can delete the case from the vendor after you save your export, and the vendor says how long backups persist.

Retention: how long and where

8 CCR 39.5(a) requires a QME to keep every QME report for 5 years from the date of the evaluation report. An electronic copy is enough if it is a true copy of the signed, served report. No rule sets a retention period for an AI file note. Keeping it with the report for the same 5 years is our recommendation: a challenge to the report arrives with the report, and the note is the answer to it. Store it where the report lives, under the same access controls, because it names the worker's records and is itself PHI.

Is a QME required to keep an AI audit trail?

No rule says so in words. 8 CCR 39.5 requires keeping reports for 5 years, and a dated record of who did what is how you answer if a report is challenged.

Is the AI vendor's activity log enough?

It shows what the software did. It does not show which records you read, which excerpts you checked or what you wrote yourself. Keep your own note and save the vendor export with it.

Should the file note be served with the report?

No. The disclosure in the report says what helped. The note stays in your file for the Medical Director, a deposition or a hearing.