How to Review AI-Drafted Notes Without Signing Your Name to Hallucinated Errors

15 min read

I've watched colleagues get burned by AI-drafted clinical notes. Not in some abstract, "someday this could happen" way, I mean a real attending physician who signed a note that said a patient was "counseled on smoking cessation" when the patient had never smoked a day in their life. The AI pulled it from a template, stitched it into the encounter, and nobody caught it until the patient requested their records. That's a complaint filed. That's your name on a document you didn't write but legally endorsed.

This article is for educational purposes only. It is not legal advice, not financial advice, and not tax advice. Malpractice exposure, licensing consequences, and institutional policies vary significantly, figures vary by jurisdiction and circumstance. Consult a qualified professional for guidance specific to your practice.

Here's the reality: AI scribes and ambient documentation tools are now embedded in Epic, Cerner, Athena, and every other major EHR. They're not going away. But neither is your signature. And when a hallucinated error lands in a medical record with your name on it, "the AI wrote that" is not a defense. Let's make sure you never have to find that out the hard way.

Before you begin, it is essential to understand the malpractice trap of AI-drafted notes and how your reliance on automation can impact your legal standing.


A weary physician reviewing a digital tablet with red warning overlays

The AI Trap: Why Your Credential Is on the Line

Let me be blunt about what AI clinical documentation actually is: a prediction engine. It's a very sophisticated autocomplete. It doesn't know that your patient has CHF, it predicts that the string "CHF" belongs near the string "cardiomegaly" based on patterns it learned from millions of documents. Sometimes those patterns are right. Sometimes they're catastrophically wrong.

The real danger isn't the AI. It's you. Specifically, it's a cognitive failure called automation bias, the tendency to trust automated output more than your own judgment, especially when you're tired, behind, and staring at 23 unfinished notes at 7 PM on a Friday.

I've seen it happen to excellent clinicians. They read the AI-drafted note, it sounds right, the formatting looks clean, the assessment flows logically, and they sign. They don't verify the medication dosages. They don't cross-check the physical exam against what they actually observed. They don't question the family history that the AI pulled forward from a 2019 encounter without checking if it's still accurate.

Here's what happens when you sign a note containing an AI hallucination:

Legally, that note is your work product. Your signature is an attestation that you personally reviewed and verified the contents. "The AI generated this" is not a defensible position in a malpractice suit or a board complaint. You are the author of record. Full stop.

To keep your documentation safe, familiarize yourself with common AI documentation tool misuses to avoid risking your professional license.

Before you finalize your charting, review these AI documentation tools: common misuses that risk your license to ensure your workflow remains compliant.

Ethically, you've potentially introduced false information into a patient's medical history that will propagate forward. Every future clinician who opens that chart sees the AI's fabrication as your clinical finding. The patient who "tolerated the procedure well" according to the AI, but who actually had a vasovagal episode, now has a clean procedural record that contradicts reality.

Professionally, you've handed any plaintiff's attorney a gift-wrapped argument: "Doctor, you signed a note stating the patient's abdomen was soft and non-tender. The nursing notes from the same encounter document guarding and rebound. Did you actually examine this patient?"

The mindset shift you need right now: you are not the prompter. You are the final editor. The AI is your assistant, not your co-signer. Every word it generates is a draft. Nothing is final until you say it is.


Anatomy of an AI Hallucination: Spotting the Red Flags

Not all hallucinations are obvious. That's what makes them dangerous. An AI that fabricated a wild medication dose, say, "metformin 5000 mg twice daily", would be easy to catch. But that's not how most hallucinations work. They're subtle. They're plausible. They're just wrong enough to cause harm but just believable enough to slip past a tired attending.

Here's what to watch for:

If you are struggling with these tools, remember that being afraid to say you don't understand an AI tool? how to ask safely is a common concern among busy clinicians.

1. "Plausible but impossible" medication dosages and frequencies

The AI might generate "lisinopril 20 mg PO daily", which is a perfectly valid dose, when the patient is actually on lisinopril 10 mg. It pulled the number from a different encounter or inferred it from a population-level pattern. Or it might list a medication as "BID" when the patient takes it once daily, leading to a doubling of dose if the next clinician follows your note as written.

Red flag: Any medication in the AI-drafted note that you didn't explicitly mention during the encounter. Verify against the medication list. Every time.

2. Incorrect patient history integration between encounters

This is the one that keeps me up at night. AI tools often pull from prior encounters to "enrich" the current note. That sounds helpful until you realize it's pulling from the wrong patient's template, or from an encounter where the history was documented incorrectly, or from a template that was never actually reviewed.

I've seen an AI-drafted note state "Patient denies alcohol use" in a patient actively being treated for alcohol use disorder. The AI pulled the "denies" language from a different encounter's ROS template and applied it to a patient whose entire clinical picture contradicts it.

Red flag: The social history, family history, or surgical history reads like a template. If it's too clean, too complete, or doesn't match what you actually discussed, it's probably fabricated or stale.

3. Fabricated physical exam findings

This is the most dangerous category. Some AI tools will generate a full physical exam section even when you only documented portions of it. If you note "lungs clear to auscultation," the AI may auto-populate "regular rate and rhythm, no murmurs, no gallops, no rubs" for the cardiac exam you didn't perform.

In a malpractice case, a note documenting a normal cardiac exam on a patient who later has a cardiac event is a liability nightmare, especially if you didn't actually listen to their heart.

Red flag: Any exam finding more detailed than what you actually performed. If you documented a focused exam, the note should reflect a focused exam.

4. Subtle inconsistencies in the Assessment and Plan

The AI is generally good at structure but terrible at internal logic. I've reviewed notes where the assessment says "acute decompensated heart failure" and the plan says "continue outpatient diuretics and follow up in 2 weeks." The two statements are clinically contradictory, ADHF doesn't get managed with a clinic follow-up in two weeks, but the AI generated them from different parts of the transcript without recognizing the conflict.

Red flag: Read the A&P as a coherent argument. If the assessment doesn't justify the plan, or the plan doesn't address the assessment, something is wrong.


The Systematic Review Protocol: How to Protect Your License

Don't rely on reading the note start-to-finish and hoping errors jump out. They won't. Your brain is wired to skip over text that "looks right," and AI-drafted notes are specifically designed to look right. You need a system. Here's mine.

The 3-Pass Review Strategy

Pass 1: Accuracy scan. Read the note fast, top to bottom. You're not reading for detail. You're reading for anything that feels wrong. Does the chief complaint match what you remember? Does the HPI sound like the patient you saw? Does the assessment list the problems you actually addressed? This pass should take 60-90 seconds. If something catches your attention, flag it mentally and move on.

Pass 2: Context verification. Now go back and verify the data points. Check every medication against the medication list. Check every lab value against the actual lab results. Check the physical exam against what you documented (or what you actually did). Cross-reference the problem list against the assessment. This pass takes 3-5 minutes. It's tedious. Do it anyway.

Pass 3: Completeness check. Did the AI capture what you actually said? Did it include your clinical reasoning, or just your conclusions? Did it document the shared decision-making conversation you had? Did it capture the patient's concerns? This is where AI notes most commonly fail, they capture the what but miss the why.

Never, ever bulk sign

I cannot state this forcefully enough: bulk signing AI-drafted notes without individual review is malpractice waiting to happen. I don't care if your colleagues do it. I don't care if the EHR makes it easy. I don't care if you're three hours behind. Bulk signing is how you end up with your name on a note documenting a normal physical exam on a patient you never touched.

If your institution's workflow pressures you toward bulk signing, that's an institutional problem that needs to be raised with medical staff leadership. But the liability is personal. The board doesn't accept "the system made me do it" as a defense.

Cross-reference against raw transcript data

If your AI tool provides a raw transcript of the encounter, use it. This is your ground truth. The transcript tells you what was actually said; the AI-drafted note tells you what the AI thinks was said. When they diverge, the transcript wins. Always.

I recommend pulling up the transcript side-by-side with the drafted note during your review, at least for the HPI and assessment/plan sections. It adds 2-3 minutes per note. It has caught errors that would have been clinically significant in roughly 8% of notes I've reviewed.

Document your AI usage appropriately

This is nuanced and evolving, but here's my position: if you used an AI tool to draft the note, that fact should be transparent. Some institutions require a specific attestation. Some don't, yet. But consider this: if a note is ever called into question, the discovery that it was AI-drafted (and you didn't disclose that) looks like concealment, regardless of your intent.

A simple approach: include language like "This note was drafted using an AI documentation assistant and reviewed and edited by the signing clinician" in your note template. It's honest, it's protective, and it establishes that you took editorial responsibility.


When Technology Betrays You: Incident Response

Let's say you followed every protocol, and you still missed something. You signed a note three days ago, and now you're reviewing the chart and realize the AI documented "no acute distress" when the patient was actively in atrial fibrillation with RVR. What now?

Don't panic. But don't wait, either.

Step 1: File an addendum immediately

An addendum is not an admission of guilt. It's a correction. It's the mechanism the medical record provides for exactly this situation. Write a clear, factual addendum:

"Addendum: Upon review of the encounter dated [date], the physical exam finding of 'no acute distress' was inaccurate. The patient was in atrial fibrillation with rapid ventricular response as documented in the nursing vital signs from the same encounter. The note has been reviewed and the following corrections are made: [specific corrections]."

Do not delete the original note. Do not alter the original text. The addendum is appended; the original remains. That's how medical record integrity works.

Documenting an addendum in an EHR interface

Step 2: Report the AI failure

If the AI hallucinated a finding, it will do it again, possibly for other patients, possibly for other clinicians. Report it to your IT or informatics department. Document the specific failure (what was generated vs. what was accurate), the tool version if known, and the encounter context. This creates an institutional record of the problem and triggers a review process.

If your institution doesn't have a clear reporting pathway for AI documentation failures, raise that gap with medical staff leadership. This is a patient safety issue, not just a technology issue.

Step 3: Communicate with the patient if clinically relevant

If the error affected clinical decision-making, the wrong medication dose was continued, a follow-up was missed, a referral wasn't placed, you need to communicate with the patient. Be honest. "The note from your last visit contained an error that we've now corrected. Here's what was wrong, here's what we've done to fix it, and here's what this means for your care."

This is uncomfortable. It's also the right thing to do. And it's significantly less uncomfortable than a board complaint.

Step 4: Review your own process

Why did you miss it? Were you rushed? Did the error fall into a "blind spot" in your review process? Were you bulk-signing (I hope not)? Use the incident as a forcing function to improve your review protocol. The next note should get a more rigorous review, not the same one.


Final Guardrails: Action Steps for Every Encounter

Let me leave you with something practical. A checklist. Not a suggestion, a checklist you should use for every AI-drafted note before you sign.

Before signing any AI-drafted note:

  1. Chief complaint match: Does the CC in the note match the reason the patient presented?
  2. HPI accuracy: Does the HPI reflect what you discussed, or does it contain template language you didn't say?
  3. Medication reconciliation: Every medication in the note is verified against the active med list.
  4. Physical exam fidelity: Every exam finding in the note corresponds to an exam you actually performed. Delete anything that's fabricated.
  5. Lab and imaging values: Any values cited in the note are checked against the actual results, not the AI's summary of them.
  6. Assessment coherence: The assessment addresses every problem in the problem list relevant to this encounter.
  7. Plan logic: Every element of the plan follows logically from the assessment. No orphaned orders.
  8. Shared decision-making: If you had a counseling or SDM conversation, it's documented. The AI frequently omits these.
  9. Follow-up appropriateness: The disposition and follow-up instructions match the clinical acuity.
  10. No copy-paste carryover: The note doesn't contain language from a prior encounter that's no longer accurate.
Physician checklist on a clipboard

Treat AI like a junior scribe

Here's the framing that works: treat the AI like a first-year medical scribe who is enthusiastic, fast, and occasionally fabricates findings. You would never sign a scribe's note without review. You'd check their work. You'd verify the exam they documented matches what you did. The AI deserves the same scrutiny, actually, it deserves more, because the scribe at least has the possibility of clinical judgment. The AI doesn't.

Avoid the copy-paste spiral

AI tools love to pull forward prior documentation. That's how you get notes that grow longer with each encounter, carrying forward irrelevant ROS elements, stale social histories, and exam findings from three admissions ago. Cut the bloat. Every encounter note should reflect this encounter, not a cumulative archive of the patient's entire medical history restated each time.

Your clinical intuition is the final authority

If something in the note doesn't feel right, it probably isn't. Trust that instinct. You spent years developing clinical judgment. The AI spent milliseconds generating text. When your gut says "this doesn't match what I saw," listen to it. Delete the AI's language and write your own.


The Bottom Line

AI documentation tools are powerful. They can save you 30 minutes per day and reduce burnout. But they are tools, not authors. The moment you sign your name, you own every word, hallucinated or not. No EHR vendor, no AI company, and no institutional policy will stand between you and a board complaint when the note bears your signature.

Your action steps starting tomorrow:

  • Implement the 3-pass review on every AI-drafted note. No exceptions.
  • Never bulk sign. Period.
  • Pull up the raw transcript alongside the drafted note for verification.
  • If you catch an error after signing, file an addendum the same day.
  • Report AI failures to informatics so others don't make the same mistake.
  • Add an AI usage attestation to your note template if your institution allows it.
  • Keep a personal log of AI errors you've caught, it'll reveal patterns over time.

Your license, your patients, and your professional integrity are worth the extra five minutes per note. The AI will get better over time. Until then, you're the guardrail. Act like it.


Keep reading

View more