Clinical Documentation AI#

Conceptual Explanation#

Ambient Documentation

Ambient documentation captures the patient-physician encounter in real time — typically through a microphone in the clinical examination room or worn by the physician — and converts the encounter to a structured clinical note. The pipeline has four stages:

1. Audio capture: Record the encounter conversation (with patient consent)
2. Transcription: Convert audio to text using a speech-to-text model
3. Note generation: Convert the transcript to a structured clinical note (SOAP, progress note, or specialty template) using an LLM
4. Physician review and EHR write-back: The physician reviews, edits, and approves the note; the approved note is written to the EHR

The patient consent requirement for audio capture is non-negotiable and must be obtained before recording begins. In some states, two-party consent for recording is legally required — the patient and the physician both must consent.

Post-Hoc Documentation Assistance

Post-hoc documentation assistance generates clinical documents from EHR data rather than from encounter audio. The input is structured FHIR data (diagnoses, medications, labs, procedures, vital signs); the output is a structured document (discharge summary, after-visit summary, referral letter). The pipeline:

1. FHIR data retrieval: Pull clinical context for the encounter or admission
2. Minimum necessary prompt construction: Assemble only the relevant clinical facts
3. Document generation: LLM generates the draft document
4. Physician review and EHR write-back: Physician reviews, edits, approves, and saves to EHR

Post-hoc documentation assistance is simpler to deploy than ambient documentation (no audio capture infrastructure, no transcription model, no patient consent for recording), but it is limited to information already in the EHR — nuanced clinical reasoning from the patient encounter that was not captured in structured data is not available to the AI.

Core Architecture#

Common Mistakes#

Allowing AI Notes into the EHR Without Physician Review. The legal medical record is the physician's authored document. AI-generated content must be explicitly reviewed and approved before it enters the medical record — the physician's signature on the note attests that the content is accurate and complete. Systems that auto-populate the EHR note field from AI output without physician review create medicolegal exposure.

Missing the Ambient Documentation Consent Workflow. Audio recording in a clinical encounter requires patient consent. Organizations that deploy ambient documentation without a clear, consistent patient consent workflow create privacy violation risk. The consent step must be part of the clinical workflow, not an afterthought.

Generic Templates for All Specialties. A hospitalist discharge summary template does not produce clinically useful output for a cardiology note or a surgical operative note. Every specialty deployed on clinical documentation AI requires a specialty-specific template developed with clinical champion input and evaluated against real clinical examples.

Best Practices#

• Obtain explicit patient consent for audio recording before any ambient documentation session begins
• Write AI-generated content to a staging area, not directly to the medical record — the physician must explicitly approve the content before it becomes the record
• Track edit rate by specialty and use case as the primary quality proxy
• Develop specialty-specific templates with clinical champion input before deploying to a specialty
• Include an explicit "AI-assisted draft — reviewed and approved by [physician name]" notation in the final record for audit trail purposes

Trade-offs#

Interview Questions#

Q: A physician asks: "The AI-generated discharge summary is mostly right but sometimes includes clinical information I never ordered — things that appear in an old note. How do I know I can trust it?" How do you design around this concern?#

Category: System Design / Clinical AI Difficulty: Senior Role: AI Architect / Healthcare AI Engineer

Answer Framework:

This is a hallucination-adjacent concern, but the specific failure mode is different: the AI is pulling information from EHR data (correctly) but from the wrong encounter or the wrong timeframe. The root cause is likely that the FHIR query for clinical context is retrieving Conditions or MedicationRequests that are marked as "active" from prior encounters rather than scoped to the current admission.

Three architectural fixes:

First: scope FHIR queries to the current encounter where possible. FHIR R4 Condition and MedicationRequest resources can be filtered by encounter parameter. Retrieve conditions and medications explicitly associated with the current encounter ID, not all active conditions for the patient.

Second: include provenance metadata in the AI context. Instead of passing a flat list of conditions to the LLM, pass each condition with its recorded-date and encounter association. The prompt can then instruct the LLM to distinguish "conditions documented during this admission" from "pre-existing conditions relevant to this discharge."

Third: implement a section-level source citation in the AI draft. Each major clinical claim in the draft (diagnosis, medication, procedure) carries a reference to the FHIR resource ID that generated it. The physician can hover over a claim to see which EHR record the AI drew from. This makes the provenance visible, which restores physician trust even when the AI is occasionally pulling from the wrong context.

Key Points to Hit:

• Scope FHIR queries to current encounter — not all-time "active" resources
• Pass temporal provenance (recorded-date) with each clinical fact to the LLM
• In-draft source citations restore physician trust by making provenance transparent
• The concern is real and valid — the design fix is in the data retrieval layer, not in the LLM

Key Takeaways#

• Clinical documentation AI addresses physician burnout from documentation burden — the goal is to shift physicians from primary author to authoritative reviewer
• Ambient documentation captures encounter nuance that post-hoc documentation cannot; it also requires audio recording consent, medical ASR infrastructure, and higher operational complexity
• AI-generated content must never enter the medical record without explicit physician review and approval — the physician's signature attests to accuracy and completeness
• Physician edit rate (the fraction of AI content a physician modifies) is the primary practical quality proxy for clinical documentation AI
• Specialty-specific templates are required for each deployment — a hospitalist template does not produce clinically useful output for cardiology or surgery