Lesson objective
Write an AI use record entry as part of doing the task, keeping it separate from the medical record and limited to the minimum information the entry needs.
Plain-language explanation
Why this matters now
Every module in Level 2 ends the same way: the work is recorded. This lesson defines that record once, so the later modules can refer to it instead of rebuilding it.
Start with what the record is not. No regulator requires a physician practice to keep an AI use record, and no source in this course states such a requirement. It is this programme's recommendation, adopted because a practice that can show what it did is in a different position from one that can only say what it usually does.
Voluntary guidance points the same way without requiring it. Professional guidance (United States; Joint Commission and Coalition for Health AI, released September 17, 2025; voluntary, not a Joint Commission accreditation standard, and written mainly for hospitals and health systems): its seven elements begin with AI policies and governance structures and end with education and training, and the seventh element says organisations should, at a minimum, define and document how users will receive AI tool documentation and role-specific training. Its fifth element describes voluntary, blinded reporting of AI safety-related events. The document calls itself "an initial, high-level document," and a small practice applies it by analogy.
A question to sit with
Eleven months from now, someone asks how a particular letter to a patient was produced, who checked it and against what. What would you be able to show, and how long would it take you to find it?
What goes wrong
Writing the record afterwards. A record reconstructed at the end of the week is a memory, and memory is where the missed verification step quietly disappears.
Turning the record into a second chart. An entry that copies the patient's information into a spreadsheet creates a new store of PHI that nobody has classified, secured or included in the practice's access decisions.
Recording the tool and nothing else. "Used the assistant" tells a reader nothing about the source material, the verification or the reviewer.
Confusing the AI use record with the medical record. They are different documents with different owners and different rules. Nothing in this course says AI use must be noted in a patient's record.
Recording only the successes. The entries worth most later are the ones where the check caught something.
One person keeping it in their own notes. A record only one person can find is not a practice record.
The practical answer
What goes in an entry. Eight fields, written as the task happens.
| Field | What to write | Keep out |
|---|---|---|
| Date and task | The date and a one-line description of the task type | The patient's clinical details |
| Triage line | The four triage answers and the route, from Lesson 1 | Anything beyond the route |
| System | The approved system used, and its version where the vendor states one | Login details |
| Source material | What was supplied to the tool, described by type and location | The material itself pasted in |
| Prompt reference | The library entry and version used, once Module 03 is in place | The full prompt text if it contains PHI |
| Verification | What was checked, against what, and what was corrected | Unnecessary identifiers |
| Reviewer | The named person who reviewed and owns the output, and the date | |
| Outcome | Released, held, discarded, or escalated, and to whom |
Keep the record minimum necessary too. The temptation is to make the entry self-contained by pasting in the material. Do not.
Applied to the use record, that has a practical consequence: write a reference, not a copy. "Referral packet for patient, chart reference held in the practice system" rather than the packet. "Merge list of 23 families, held in the scheduling system" rather than the list. If a reader needs the underlying material they can go to the system that already holds it, under the access rules that already apply there.
It also means deciding, once, who may read the use record. Section 164.514(d)(3) supports handling this as a standard protocol: one decision covering a recurring category, rather than a fresh decision for each entry.
The AI use record is not the medical record. These are two different documents.
| AI use record | Medical record | |
|---|---|---|
| What it is for | Showing how an AI-assisted task was produced, checked and owned | Documenting the patient's care |
| Who owns it | The practice manager or named administrative owner, under the privacy official's rules | The licensed treating clinician for content, as the practice's policies provide |
| What it holds | Task type, system, sources by reference, verification, reviewer | The care that was provided |
| Where the content comes from | The people doing the work | The clinician's own documentation |
Nothing in this course's sources requires a practice to note AI use inside a patient's record, and this lesson does not tell you to. Module 06 covers what the clinician must check before signing an AI-captured note, which is a separate duty.
Why records get looked at. Record-keeping failures are not a hypothetical concern for clinicians.
That is the strongest available reason for a clinician to take review of AI-assisted documentation seriously. It is not a reason to say a use record is required, and a lesson that stretched it that way would be teaching something the source does not support.
Make it two minutes, or it will not happen. Three supports:
- A fixed form. The AI Use Record in your workbook has the eight fields already. Filling a form beats composing a note.
- Standard entries for recurring tasks. Where the privacy official has approved a recurring task with a fixed source list and reviewer, the entry is a line naming the standard task and the date, plus anything that differed.
- Role-specific training on how to write one. The Joint Commission and CHAI guidance recommends defining and documenting how users receive tool documentation and role-specific training; a five-minute session on what a good entry looks like removes most of the variation.
Professional guidance (United States; AMA advocacy policy adopted November 12, 2024; not binding): policy 4(b) lists the risks a practice's governance policies should address, including incorrect or falsified responses, outdated training data, lack of oversight, bias, data privacy, cybersecurity and physician liability. Policy 4(d) says use of generative AI should include physician and staff education about appropriate use, risks and benefits. A use record is where a practice can see whether its policies on those risks are actually being followed.
Remember this
- No regulator requires a practice AI use record; it is this programme's recommendation and the practice's own choice.
- Write the entry while the work happens, not at the end of the week.
- Reference the source material; do not copy it in. Minimum necessary applies to your own records.
- The AI use record is not the medical record, and nothing here says AI use must be noted in a patient's chart.
- Record the entries where a check caught something; those are the ones worth reading later.
Medical practice example
Larkspur Orthopedic Associates PLLC is a fictional six-surgeon group. Its compliance manager and privacy official, Beatriz Soto, introduces the AI Use Record with one rule: the entry is written before the output leaves the person who made it. In the first week she reviews three entries. The first is from a scheduler who drafted 31 recall letters. His entry reads: date; task type "recall letters, standard task RL-2"; triage "patient letter / administrative PHI, approved system / fully verifiable against recall list / owner R. Delgado, Route B"; system named with the version the vendor published in July; source "recall list held in the scheduling system, 31 rows, name and appointment fields only"; verification "31 of 31 names and dates checked against the recall list; two wrong clinic addresses corrected"; reviewer "R. Delgado, same day"; outcome "released." Beatriz marks it good and notes that the two corrections are the most valuable line in it. The second is from a biller whose entry says only "used the assistant to help with an appeal letter." Beatriz sends it back: no source, no verification, no reviewer. The rewritten entry shows the payer bulletin as the source, a field-by-field check of the deadline and submission address, and the billing lead as reviewer. The third entry is from a medical assistant who had pasted the whole of a fictional patient's referral packet into the source field of the record itself. Beatriz has it replaced with a reference to the chart location, deletes the copy under the practice's procedure, and adds a line to the next training session: the record points at material, it does not hold it. She then writes a standard entry template for the three most common tasks, so each future entry is a line plus exceptions.
Responsible-use warning
Do not build a second store of patient information inside your AI use record. An entry that pastes in the referral packet, the merge list or the portal message creates PHI in a document that nobody has classified, secured or included in the practice's access decisions, and it is the opposite of minimum necessary. Reference the material by type and location instead. Equally, do not treat the use record as part of the medical record: they have different owners, different purposes and different rules, and nothing in this course requires AI use to be noted in a patient's chart.
Human-review requirement
The privacy official decides who may read the AI use record, what may be written in it and how long it is kept, and approves the standard entries for recurring tasks. The practice manager or named administrative owner keeps the record, checks that entries are being written as the work happens and returns incomplete ones. The named reviewer of each output signs the entry for that output: the licensed treating clinician for anything clinical, the coding professional for anything supporting a claim, the practice manager for administrative outputs. The practice owner ensures the privacy official has the authority and the time to run it.
Practical exercise
Use fictional tasks and fictional patients only. Do not put real patient information in any exercise record.
- Take the three tasks you triaged in Lesson 1 that reached Route A or B and write a full eight-field record entry for each.
- For each entry, write the source material line twice: once as a copy of the material and once as a reference. Delete the copies and note what you removed.
- Write the verification line for each so a reader can tell what was checked and against what, without seeing the material.
- Name the reviewer for each entry and the date, and say why that person is the right owner.
- Write one entry for a task where the check caught an error, and make the correction the most visible line in it.
- Draft a standard entry for one recurring task, in five lines or fewer, showing which fields are fixed and which change each time.
- Write, in two sentences, who in your practice may read the use record and who decides that.
- Write a two-sentence statement of the difference between the AI use record and the medical record, in words a new starter would understand.
- Time yourself writing one entry from scratch. If it takes more than three minutes, cut a field or move it into the standard entry.
- Add your entries to the AI Use Record in your workbook and mark the one you would want the privacy official to review first.
Knowledge check
-
Is a practice required to keep an AI use record?
Answer guidance: No. No regulator requires one and no source in this course states such a requirement. It is this programme's educational recommendation, supported by voluntary guidance such as the Joint Commission and CHAI elements on governance and training.
-
Why is source material referenced rather than copied into the use record?
Answer guidance: Because copying creates a second store of PHI that has not been classified, secured or included in access decisions. 45 CFR 164.502(b)(1) requires reasonable efforts to limit PHI to the minimum necessary, and 164.514(d)(2) requires access to be identified and limited.
-
What does the FSMB document report about records and board discipline, and what does that figure cover?
Answer guidance: That failure to maintain adequate medical records was the basis for 6% of all state medical board disciplinary actions from 2015 to 2019. It covers medical records and discipline of licensed physicians, not AI use records and not administrative staff.
-
Name four of the eight fields in an AI use record entry.
Answer guidance: Any four of: date and task; the triage line and route; the system used; the source material by reference; the prompt library entry and version; what was verified and corrected; the named reviewer and date; the outcome.
Sources and further reading
- AI Coalition Network — Certification Educational Standard: Human Review of AI-Assisted Professional Work. Accessed 2026-09-15.
- Joint Commission and Coalition for Health AI (CHAI) — Joint Commission and Coalition for Health AI (CHAI) Guidance on The Responsible Use of AI in Healthcare (RUAIH) (2025-09-17). Accessed 2026-09-15.
- U.S. Department of Health and Human Services (Electronic Code of Federal Regulations) — 45 CFR 164.502(b) Standard: Minimum necessary; 45 CFR 164.514(d) Implementation specifications. Accessed 2026-09-15.
- Federation of State Medical Boards — Navigating the Responsible and Ethical Incorporation of Artificial Intelligence into Clinical Practice. Accessed 2026-09-15.
- American Medical Association (AMA), House of Delegates — Augmented Intelligence Development, Deployment, and Use in Health Care (AMA Board of Trustees report and policy adopted November 12, 2024) (2024-11-12). Accessed 2026-09-15.