Lesson 4 of 4 · AI for Doctors
Setting Up Your AI-Augmented Clinical Workflow
Dr. Reyes's Two-Hour Miracle
Dr. Elena Reyes had been an internist at a mid-sized multispecialty practice in Minneapolis for eleven years. She was good at her job -- her patient satisfaction scores were consistently in the 90th percentile, her clinical outcomes were solid, and she had earned a reputation among colleagues as someone who could handle complex, multimorbid patients with a calm competence that put everyone at ease. But by the autumn of 2025, she was drowning.
Her typical day started at 6:45 AM, when she would arrive at the clinic to review charts for her morning patients. She saw 18 to 22 patients a day -- a mix of chronic disease management, acute visits, pre-operative clearances, and the occasional diagnostic puzzle. Between patients, she would squeeze in documentation, pecking at her keyboard during the four-minute gaps between appointments. She never finished. By 5:30 PM, when the last patient left, she still had six to eight notes to complete, a dozen inbox messages from patients, three referral letters, two prior authorization forms, and a stack of lab results to review and act on.
Most nights, she sat down at her dining room table at 8 PM, opened her laptop, and spent another two to two and a half hours finishing documentation. Her husband called it "pajama time" -- the medical profession's dark euphemism for the unpaid hours physicians spend every evening doing paperwork. Elena called it something less polite.
She had heard about physicians using AI tools but had dismissed the idea. She pictured tech bros in Silicon Valley making chatbots, not serious clinical tools. Then, in November 2025, a hospitalist colleague named Dr. Jay Patnaik stopped her in the physician lounge.
"Elena, how much pajama time are you pulling these days?"
"Two, two and a half hours. Every night."
Jay shook his head. "I'm down to thirty minutes. Sometimes less."
She stared at him. Jay saw even more patients than she did -- he covered a 20-bed hospitalist service. "How?"
"I rebuilt my entire workflow around AI over the past three months. I use it for chart prep in the morning, documentation during the day, referral letters, patient messages -- basically everything except the actual clinical decision-making. That part is still me."
What Jay described wasn't a single magic tool. It was a system -- a carefully designed daily workflow that placed AI at specific points where it could absorb the most administrative friction. He had experimented, failed, adjusted, and iterated until he found a rhythm that worked.
Over the next twelve weeks, Elena followed a similar path. She didn't adopt every tool at once. She started small, tested one change at a time, and measured the impact. By the end of three months, her pajama time had dropped from two-plus hours to an average of twenty-two minutes. On good days, she finished all her documentation before leaving the clinic.
The transformation wasn't just about time. Elena noticed she was more present with patients because she wasn't mentally composing notes during conversations. She was sleeping better. She started exercising again. She picked up a hobby she had abandoned during residency. Her marriage improved.
22 min
Average Pajama Time
After implementing a structured AI workflow, Dr. Reyes reduced her nightly documentation time from over two hours to an average of 22 minutes.
"The AI didn't make me a better diagnostician," she told a colleague. "But it made me a better doctor -- because I wasn't burned out anymore."
This lesson walks you through exactly how to build the kind of workflow Elena and Jay created. Not a theoretical framework -- a practical, step-by-step system you can start implementing today.
Part 1: The Architecture of a Clinical AI Workflow
Why "Workflow" Matters More Than "Tool"
The most common mistake physicians make with AI is thinking in terms of individual tools rather than integrated workflows. They download ChatGPT, try it once for a progress note, get a mediocre result, and conclude that AI isn't ready for clinical use.
The problem isn't the tool. It's the approach.
A clinical AI workflow is a deliberate system that defines:
- When in your day you use AI (and when you don't)
- What tasks you delegate to AI versus handle yourself
- How you structure your prompts for consistent, high-quality output
- Where patient data boundaries exist (the HIPAA line you never cross)
- What review process ensures AI output meets your clinical standard
Think of it like building an operating room. A scalpel by itself is just a sharp piece of metal. But placed within a sterile field, held by trained hands, supported by anesthesia, nursing, and surgical tech -- it becomes part of a system that saves lives. AI tools work the same way. Their value comes from the system you build around them.
The Four Phases of a Clinical Day
Every physician's day, regardless of specialty, follows a broadly similar arc. Your AI workflow maps onto these four phases:
| Phase | Timing | AI Role |
|---|---|---|
| Prep | Before clinic or rounds | Chart review, case preparation, literature lookup |
| Encounter | During patient interactions | Ambient documentation, real-time reference |
| Process | Between encounters and after clinic | Note completion, referrals, messages, prior auths |
| Research | After-hours or protected time | Literature review, guideline summaries, CME |
The key insight is that AI serves a different function in each phase. In the Prep phase, it's a summarizer. During Encounters, it's a scribe. In the Process phase, it's a drafting assistant. During Research, it's an analyst. Understanding these distinct roles helps you choose the right tool and the right prompting strategy for each moment.
Part 2: Choosing Your Tools
The Tool Landscape for Physicians
The AI tools available to physicians fall into three categories, and understanding the differences is critical for building a safe, effective workflow.
Category 1: EHR-Integrated AI (Highest Safety, Least Flexibility)
These are AI features built directly into your electronic health record system. They operate within your institution's existing HIPAA framework.
- DAX Copilot (Nuance/Microsoft) -- Ambient documentation integrated with Epic and other EHRs. Listens to the patient encounter and generates structured notes.
- Epic AI features -- In-basket message drafting, chart summarization, patient instruction generation.
- Oracle Health (Cerner) AI -- Clinical documentation assistance and order set suggestions.
Advantages: PHI stays within your institution's BAA-covered environment. No data leaves the system. IT and compliance have already vetted it. Limitations: You can't customize prompts. The output format is fixed. You're limited to what your institution has purchased.
Category 2: HIPAA-Compliant General AI (Moderate Safety, High Flexibility)
These are general-purpose AI tools offered under Business Associate Agreements (BAAs) that allow use with de-identified or appropriately safeguarded patient information.
Do not let Setting Up Your AI-Augmented Clinical Workflow become a hidden assumption. If teammates cannot see the rule, config, or verification path, Claude will behave inconsistently across sessions.
- ChatGPT Team/Enterprise (OpenAI) -- BAA available. Data not used for training.
- Claude for Work (Anthropic) -- BAA available for business/enterprise tiers.
- Google Vertex AI / Gemini Enterprise -- BAA available through Google Cloud.
- Microsoft Azure OpenAI Service -- BAA covered under Microsoft's healthcare agreements.
Advantages: Highly flexible prompting. Can be customized for your specific documentation style. Powerful for research, education, and administrative tasks. Limitations: Requires your institution to sign a BAA. You must still follow de-identification protocols. Not integrated with your EHR directly.
Category 3: Consumer AI Tools (Lowest Safety, Highest Accessibility)
Free or personal-subscription AI tools without healthcare-specific data protections.
- ChatGPT Free/Plus (personal)
- Claude Free/Pro (personal)
- Google Gemini (personal)
- Perplexity, Copilot, etc.
Advantages: Immediately available. No institutional approval needed. Free or low cost. Limitations: No BAA. Never use with any patient-identifiable information. Appropriate only for general medical knowledge queries, literature review with no PHI, drafting templates, and personal education.
This is the rule that has no exceptions: Never enter Protected Health Information into a consumer AI tool. No names, no dates of birth, no medical record numbers, no specific clinical details that could identify a patient. This applies even if you think the information is "anonymized" -- the combination of a rare diagnosis, a specific date, and a geographic location can be enough to re-identify someone. If you want to use AI for tasks involving real patient data, you need either an EHR-integrated tool or an enterprise tool covered by a BAA signed by your institution.
Mobile vs. Desktop: Matching Device to Moment
Your workflow should leverage both your phone and your workstation, because the moments when you need AI don't all happen at a desk.
Desktop (Clinic Workstation)
- Primary documentation and note-writing
- Complex prompts that require long context
- Chart review and case preparation
- Referral letter drafting
- Research and literature review
Mobile (Phone/Tablet)
- Quick clinical reference questions between patients ("What is the dose adjustment for apixaban in CrCl 20 mL/min?")
- Voice-to-AI workflows while walking between exam rooms
- Dictating rough notes that AI will structure later
- After-hours inbox triage -- reviewing AI-drafted replies to patient messages
If Setting Up Your AI-Augmented Clinical Workflow becomes part of a recurring workflow, document the exact trigger, boundary, and verification step now. Future speed comes from clarity, not from memory.
The Voice Advantage
Many physicians find voice input transformational. Modern AI apps support voice input on mobile, and the combination of medical dictation skills (which most physicians already have) with AI processing creates a powerful workflow:
- You dictate a rough, unstructured summary of the encounter into the AI app
- The AI structures it into a proper SOAP note, H&P, or discharge summary
- You review, edit, and finalize
This is faster than typing, and for physicians who already think out loud when processing clinical information, it feels natural. Dr. Reyes found that dictating a 90-second stream-of-consciousness summary into Claude on her phone, then having it generate a structured progress note, cut her per-note documentation time from 8 minutes to 3.
Open your AI app on your phone. Tap the microphone icon. Say: "I just saw a 67-year-old male with poorly controlled type 2 diabetes, A1c 9.2, on metformin 1000 twice daily. He's having GI side effects. I'm adding semaglutide 0.25 weekly, continuing metformin but dropping to 500 twice daily. Follow-up in 3 months with repeat A1c. He needs a diabetic eye exam and a foot exam today, which was normal. Generate a structured SOAP note for this encounter." Then review what it produces. You will be surprised by how good the output is -- and where it needs correction.
Part 3: Building Your Daily Workflow -- Phase by Phase
Phase 1: Morning Prep (15-20 minutes before clinic)
What Dr. Reyes does:
Elena arrives at the clinic at 7:00 AM. She opens her schedule for the day -- eighteen patients. She spends the first 15 minutes doing AI-assisted chart preparation for her complex patients.
For each complex patient (typically 4-6 per day), she pulls up the chart in her EHR and identifies the key information: recent labs, medication list, last visit assessment, and the reason for today's visit. Then she opens Claude on her desktop and enters a prompt like this:
"I'm seeing a patient today for follow-up. Here is the clinical context [de-identified summary]. What are the key items I should address, and are there any guideline-based recommendations I should consider?"
She never includes patient names or identifiers. She describes the clinical scenario in generic terms -- "68-year-old female with HFrEF, EF 35%, on guideline-directed medical therapy, presenting for 3-month follow-up. Recent BNP trending up from 450 to 680. Creatinine stable at 1.3."
Map Your Setting Up Your AI-Augmented Clinical Workflow Layers
- Open your global, project, and local Claude configuration files.
- Write down which rule for this lesson belongs in each layer and why.
- Start a fresh Claude Code session and confirm the effective behavior matches your intent.
The AI responds with a structured checklist: medication optimization per ACC/AHA guidelines, volume status assessment, consideration of device therapy, labs to order, and questions to ask. Elena doesn't follow this blindly -- she uses it as a pre-rounding cognitive checklist that catches items she might otherwise miss during a busy clinic day.
Why this works:
Research on clinical decision-making shows that physicians are most likely to miss guideline-concordant care steps when they are cognitively overloaded -- managing multiple complex patients under time pressure. The AI-generated prep sheet serves as a cognitive offload, not a clinical authority. You still make every decision. But you're making decisions with a checklist in hand rather than relying purely on memory.
Your Morning Prep Template:
Phase 2: During the Encounter
The Ambient Documentation Model
If your institution uses an ambient AI documentation tool like DAX Copilot, this phase is largely automated. The AI listens to the patient encounter, identifies clinical elements, and generates a structured note.
If you don't have ambient AI, you have two options:
Option A: Brief Dictation After Each Patient
Immediately after the patient leaves the room, before you call the next patient, spend 60-90 seconds dictating a summary into your phone. Don't try to structure it. Just talk:
"Sixty-seven-year-old male, follow-up diabetes, A1c still elevated at 9.2 despite metformin, GI side effects, adding semaglutide, reducing metformin dose, follow-up three months, needs eye exam referral, foot exam today was normal, discussed diet and exercise, he's agreeable to the new medication."
Test a Safe Setting Up Your AI-Augmented Clinical Workflow Override
- Add one narrow allow rule and one narrow deny rule related to this lesson.
- Ask Claude to trigger both cases in a scratch project or branch.
- Note which rule wins and whether the result matches the hierarchy described here.
Later -- during your Process phase -- you'll feed this dictation to AI to generate the structured note.
Option B: AI-Assisted Templates
For common visit types (diabetes follow-up, hypertension check, annual wellness visit), create pre-built prompt templates that you fill in with the specific clinical details. This is faster than free-form dictation for routine visits.
Phase 3: Processing (The Biggest Time Saver)
This is where Elena reclaimed most of her two hours. The Process phase covers everything that happens after the patient encounter: completing notes, drafting referral letters, responding to patient messages, handling prior authorizations, and reviewing results.
Note Completion
If you dictated raw summaries during encounters (Phase 2, Option A), this is when you process them. Open your AI tool and use this workflow:
- Paste or send your dictated summary
- Ask the AI to generate a structured note in your preferred format (SOAP, H&P, etc.)
- Review the output -- check for accuracy, add clinical reasoning, correct any errors
- Copy the finalized note into your EHR
For Elena, this takes 2-3 minutes per note instead of the 7-8 minutes it used to take when she composed each note from scratch. Across 18 patients, that's a savings of roughly 90 minutes per day.
Referral Letters
Referral letters are one of AI's greatest strengths. They follow a predictable format, require synthesis of clinical information, and consume far more time than their clinical complexity warrants.
What used to take Elena 10-15 minutes per letter now takes 2-3 minutes including review and editing.
Test a Safe Setting Up Your AI-Augmented Clinical Workflow Override
- Add one narrow allow rule and one narrow deny rule related to this lesson.
- Ask Claude to trigger both cases in a scratch project or branch.
- Note which rule wins and whether the result matches the hierarchy described here.
Patient Messages
The patient portal inbox is one of the top contributors to physician burnout. AI can draft replies to common patient messages -- medication questions, appointment requests, lab result interpretations -- that you then review and send.
Some EHR systems (Epic, for example) now offer this natively. If yours doesn't, you can use a similar workflow to note completion: copy the patient's message (de-identified if using a non-integrated tool), ask AI to draft a professional, empathetic reply, review it, and send it.
You will find that about 80% of your documentation tasks fall into predictable patterns -- routine follow-ups, standard referral letters, common patient message replies. AI handles these extremely well. The remaining 20% -- complex diagnostic reasoning, sensitive communications, unusual clinical scenarios -- still require your full attention and original writing. Build your workflow around automating the 80% so you have more mental energy for the 20% that truly needs a physician's judgment.
Prior Authorizations
Prior authorization letters require specific language that insurance companies expect. AI is remarkably good at generating these because the format is formulaic:
Several physicians report that AI-drafted prior auth letters have a higher approval rate than their manually written ones -- likely because the AI consistently includes all the required elements that busy physicians sometimes omit.
Phase 4: Research and Learning
Clinical Questions
Every physician generates clinical questions throughout the day -- "What's the latest evidence on SGLT2 inhibitors in CKD without diabetes?" or "What are the diagnostic criteria for hemophagocytic lymphohistiocytosis?" Most of these questions go unanswered because looking up the answer takes too long in a busy clinic.
AI changes this equation. You can ask clinical knowledge questions and get structured, referenced answers in seconds. But there are critical caveats:
- Always verify against primary sources. AI can hallucinate references and get details wrong. Use it as a starting point for literature review, not as a definitive source.
- Specify the level of evidence you want. Ask for "guidelines from major societies" or "systematic reviews and meta-analyses" rather than generic answers.
- Be specific in your questions. "Tell me about diabetes management" will get a generic response. "What is the evidence for adding finerenone to SGLT2 inhibitor therapy in a patient with type 2 diabetes and stage 3b CKD with albuminuria?" will get a targeted, useful answer.
Quick Check
What is the main benefit of using Setting Up Your AI-Augmented Clinical Workflow well in Claude Code?
CME and Learning
AI can serve as a personalized tutor for continuing medical education:
- Summarize landmark clinical trials in your specialty
- Generate practice questions on topics you're studying for board recertification
- Explain complex pathophysiology in clear language
- Compare treatment guidelines from different societies
Part 4: HIPAA-Safe Configuration -- The Non-Negotiable Setup
Before you use any AI tool in your clinical workflow, you need to establish your HIPAA safety configuration. This is not optional, and it is not something you can figure out as you go. Get this right from day one.
Tier 1: Institutional Tools (Safest)
If your institution offers EHR-integrated AI (DAX, Epic AI features, etc.), use these for any task involving patient data. The BAA is in place, the data stays within your institution's infrastructure, and compliance has already approved it.
Tier 2: Enterprise AI with BAA
If your institution has a BAA with an enterprise AI provider (ChatGPT Enterprise, Claude for Work, etc.), you can use these tools with appropriately handled patient information per your institution's policies. Check with your compliance officer to understand exactly what is and isn't permitted.
Tier 3: Consumer AI (Personal Use Only)
For consumer AI tools (personal ChatGPT, Claude, Gemini subscriptions), follow these absolute rules:
The PHI Bright Line
Use EHR-integrated AI or BAA-covered enterprise tools for any task involving patient data
Enter Protected Health Information into consumer AI tools -- no names, no MRNs, no dates of birth, no facility names
- Never enter PHI. No names, dates of birth, MRNs, specific dates of service, or clinical details that could identify a patient.
- Use clinical scenarios, not clinical cases. Instead of "My patient John Smith with MRN 12345," write "A 72-year-old male with a history of..."
- Avoid rare diseases with geographic context. If you're the only rheumatologist in a small town and you ask about a rare vasculitis, the combination of specialty, location, and rare diagnosis could theoretically identify a patient.
- Never paste EHR text directly. EHR notes contain embedded identifiers you might not notice -- headers with patient names, auto-populated fields, timestamps.
- Turn off chat history and training when available. Both ChatGPT and Claude offer settings to prevent your conversations from being used for model training.
Quick Check
After reading this lesson, what should you validate when applying Setting Up Your AI-Augmented Clinical Workflow?
The De-Identification Checklist
Before pasting any clinical information into a consumer AI tool, mentally run through this checklist:
- No patient name or initials
- No date of birth or age over 89
- No specific dates (use "recently" or "3 months ago" instead)
- No geographic information smaller than a state
- No medical record numbers, account numbers, or device identifiers
- No Social Security numbers or insurance IDs
- No phone numbers, email addresses, or URLs
- No photographs or biometric identifiers
- No unique clinical details that could identify the patient in context
If you are uncertain whether a piece of information could identify a patient, do not include it. The HIPAA Safe Harbor method requires removal of 18 specific identifier categories. When using consumer AI tools, be more conservative than the minimum -- strip everything that isn't strictly necessary for the clinical question you're asking.
Part 5: Building Your Prompt Template Library
One of the most powerful things you can do is create a personal library of prompt templates for your most common clinical tasks. This eliminates the "blank page problem" -- you never have to figure out how to phrase a request from scratch.
Template Structure
Every good clinical prompt template has four elements:
Quick Check
After reading this lesson, what should you validate when applying Setting Up Your AI-Augmented Clinical Workflow?
- Role: Tell the AI what role to assume ("You are a clinical documentation assistant for an internal medicine physician")
- Task: Specify exactly what you want ("Generate a SOAP note from the following encounter summary")
- Context: Provide the clinical information
- Format: Specify the output format ("Use bullet points," "One page maximum," "Include ICD-10 codes")
Starter Template Library
Here are ten templates to get you started. Save these in a note app or text file on your computer and phone for quick access.
1. SOAP Note from Dictation
2. H&P from Admission Summary
3. Discharge Summary
4. Referral Letter
5. Prior Authorization
6. Patient Education Handout
7. Literature Summary
8. Differential Diagnosis Expansion
9. Patient Message Reply
10. Clinical Decision Support
Part 6: When NOT to Use AI
Building an effective AI workflow isn't just about knowing when to use AI -- it's about knowing when to stop.
Do Not Use AI For:
Final clinical decisions. AI is a drafting tool, a brainstorming partner, a literature assistant. It is never the decision-maker. You are. Every AI-generated differential, treatment suggestion, or guideline summary must pass through your clinical judgment before it affects patient care.
Breaking bad news or sensitive conversations. AI can help you structure your thoughts before a difficult conversation, but the actual communication with a patient about a cancer diagnosis, a poor prognosis, or a medical error must be entirely human. Patients need to see your face, hear your voice, and feel your presence.
Situations where you don't understand the output. If AI generates a recommendation and you don't understand the reasoning behind it, do not use it. AI should augment expertise you already have, not substitute for expertise you lack.
Documentation you haven't verified. Never sign an AI-generated note without reviewing every line. AI will sometimes fabricate physical exam findings, invent lab values, or include information from the wrong patient context. Review is not optional -- it is the core of your responsibility as the physician of record.
Rare or novel clinical situations. AI models are trained on published literature and common patterns. For truly novel presentations, rare diseases with limited literature, or situations where the clinical context is unusual, AI's output is less reliable. These are the moments when your training, your colleagues, and primary literature matter most.
I will use AI to handle administrative burden so I can focus on clinical care. I will never let AI make clinical decisions for me. I will review every piece of AI-generated content before it enters a medical record or reaches a patient. I will protect patient privacy absolutely. I will stay current on AI capabilities and limitations as the technology evolves.
Part 7: Measuring Your Workflow's Impact
Once you've implemented your AI workflow, track its impact. This serves two purposes: it helps you optimize the workflow, and it gives you data to share with skeptical colleagues or administrators.
What to Track (Week 1 vs. Week 4)
| Metric | How to Measure |
|---|---|
| Pajama time | Minutes spent on documentation after leaving the clinic |
| Per-note time | Average minutes to complete a progress note |
| Inbox clearance | Minutes to process patient messages and results |
| Referral letter time | Minutes per referral letter |
| Error catches | Times you caught an AI error during review |
| Satisfaction | Your subjective sense of workload and burnout (1-10 scale) |
Most physicians who implement a structured AI workflow report 30-50% reduction in documentation time within the first two weeks, and 50-70% reduction by week four as they refine their templates and workflow.
Apply What You've Learned
Set Up Your First Clinical AI Workflow
This exercise takes about 30 minutes and will give you a working foundation for your AI-augmented clinical day.
Step 1: Choose Your Tool (5 minutes)
Based on the three categories above, identify which AI tool you will use:
- Check if your institution offers EHR-integrated AI (ask your CMIO or IT department)
- Check if your institution has a BAA with any enterprise AI provider
- If neither, start with a personal subscription to ChatGPT Plus or Claude Pro -- but remember the strict PHI rules for consumer tools
Step 2: Set Up Your Mobile and Desktop Access (5 minutes)
Install the AI app on both your phone and your computer. Log in on both devices. Familiarize yourself with the voice input feature on your phone.
Step 3: Create Your First Three Templates (10 minutes)
From the Starter Template Library above, choose the three templates most relevant to your daily work. Copy them into a note app (Apple Notes, Google Keep, Notion -- whatever you already use) so they are accessible on all devices.
For most internists, start with:
- SOAP Note from Dictation
- Referral Letter
- Patient Message Reply
Step 4: Test With One Patient Tomorrow (10 minutes)
Tomorrow, pick one patient -- ideally a routine follow-up visit. After the encounter, dictate a 60-90 second summary into your AI app using the voice input. Then use your SOAP Note template to generate a structured note. Review it carefully, noting what the AI got right, what it got wrong, and what it missed.
Step 5: Track Your Baseline
Before you start using AI regularly, write down your current metrics: How many minutes do you spend on pajama time tonight? How long does a typical progress note take? How long does a referral letter take? You will compare these numbers in four weeks.
Key Takeaways
- A clinical AI workflow is a system, not a single tool -- it maps AI capabilities onto the four phases of your clinical day: Prep, Encounter, Process, and Research
- Start with Tier 1 tasks (documentation, referral letters, patient messages) where AI provides immediate time savings with lowest risk
- The PHI bright line is absolute: never enter identifiable patient information into consumer AI tools -- use EHR-integrated or BAA-covered enterprise tools for patient data
- Voice-to-AI workflows leverage dictation skills you already have and can cut per-note documentation time by 50% or more
- Prompt templates eliminate the blank-page problem -- build a personal library of 5-10 templates for your most common tasks
- Review is not optional: every AI-generated clinical document must be checked line by line before it enters the medical record
- Know when NOT to use AI: final clinical decisions, sensitive conversations, unfamiliar outputs, and rare or novel clinical situations remain firmly in human hands
- Measure your impact: track pajama time, per-note time, and inbox clearance to quantify your workflow's value and identify areas for improvement
Use ← → to navigate, Space to mark complete