Title: QME AI audit trail: the file note that proves your work | AI for QME
URL: https://aiforqme.com/audit-trail/

> The 12 entries a QME should keep for every report where AI touched the file, each tied to the rule it proves, with 5-year retention and a synthetic file note.

# The QME audit trail for AI use
By [Ahmed Jemaa](/about/#author), Co-Founder and CEO of Medrecords AI. Updated 2026-11-19.
**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:
- **[Medical Director](/glossary/#medical-director) review.** 8 CCR 39.5(b) lets the Medical Director ask for any report you wrote as a QME, and refusing can lead to discipline under 8 CCR 60. A report with an AI disclosure invites the follow-up question.
- **Discipline for lost reports.** 8 CCR 60(b)(6) covers failing to keep reports under 39.5.
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

| # | Entry | What to write | Rule it supports |
|---|---|---|---|
| 1 | Records received | Date each batch arrived, who sent it, declared page count, declaration present or missing | 8 CCR 35(i), 41(c)(2); [DWC](/glossary/#dwc) checklist |
| 2 | Late records | Any batch received more than 10 days after the exam, and what you did | 8 CCR 35(i) |
| 3 | Tool and version | Application name, version or model shown in the product, plan with a [BAA](/glossary/#baa) | DWC checklist |
| 4 | Run date and input | Date run; which batches went in; total pages | Our practice |
| 5 | Output kept | What the tool produced (index, chronology, [excerpts](/glossary/#excerpting)) and where the export is saved | 8 CCR 10682(b)(4) |
| 6 | Your read | Which records you read in full; which you skimmed with reason | 8 CCR 41(c)(2) |
| 7 | Excerpt checks | Number of cited excerpts you opened against the page; how many matched | Our practice |
| 8 | Corrections | Each tool error you found, with the page, and the fix | Our practice |
| 9 | Staff help | Name, qualifications and task of each person who helped beyond typing | DWC checklist |
| 10 | Authorship | Statement that the record summary, discussion and conclusions were written by you; transcription tool if any | 8 CCR 41(c)(2), (c)(7) |
| 11 | Report and signing dates | Exam date, date ready to sign, date signed, county | 8 CCR 41(c)(6), 35.5(b) |
| 12 | Service and retention | Date served, form used, where the signed copy and this note are stored, destroy-after date | 8 CCR 36, 38(a), 39.5(a) |

Rules captured 2026-11-12 from [8 CCR 39.5](https://www.dir.ca.gov/t8/39_5.html), [8 CCR 60](https://www.dir.ca.gov/t8/60.html), [8 CCR 35](https://www.dir.ca.gov/t8/35.html) and [8 CCR 41](https://www.dir.ca.gov/t8/41.html). 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](/glossary/#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
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](/glossary/#page-citation) 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.
**Where Medrecords AI fits:** its chronology and answers cite the source page on every line and export as hyperlinked files, which covers entries 5 and 7. It signs a BAA at signup and does not train on customer records. Your file note stays your job.
[Medrecords AI security and BAA](https://medrecords.ai/security/?src=aiforqme.com)
## 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](/glossary/#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.
