After studying this material, you should be able to:
Before understanding solutions, you must understand what is broken.
Think of a patient calling their doctor's office. They confirm their identity. They explain why they're calling. They get transferred. They confirm their identity again. They explain why they're calling again.
The fundamental problem has two layers:
| Layer | What It Means |
|---|---|
| Fragmentation | Touchpoints exist (website, portal, phone, billing) but don't communicate with each other |
| Repetition | Patients repeat the same information at every handoff |
Key Insight: The problem is not clinical care quality — it is the administrative and navigational experience surrounding care.
Most organizations deploy AI in scattered, specialized pilots at the edges of their operations.
Why this fails:
A hero journey is defined by three criteria:
✅ High volume — affects many patients regularly
✅ Measurable — you can track success clearly
✅ Low risk — mistakes are recoverable, not dangerous
Why this works:
Appointment scheduling is the ideal hero journey because:
A patient needs a contact lens prescription. She calls an optometrist. An AI agent handles the entire intake.
Follow the flow:
Patient calls
↓
Agent collects: name, date of birth, phone number
↓
Agent verifies identity via SMS code
↓
Patient forgets insurance ID → Agent adapts ("bring your card")
↓
Agent offers 3 appointment slots
↓
Patient selects one → Confirmation email + text reminder sent
↓
Same workflow runs over SMS with no separate build
Lesson 1: Graceful Recovery
The patient misheard the SMS code. The agent recovered without failing the interaction. Good AI deployment anticipates errors and handles them smoothly.
Lesson 2: Omnichannel by Default
One agent handled both phone and SMS. You do not build separate systems for each channel — you build one agent that works across channels.
Lesson 3: Speed of Prototyping vs. Speed of Production
The demo took 2 hours to build. Enterprise production takes significantly longer because of integration, testing, and compliance work. Understand the difference between a prototype and a production system.
Follow this order deliberately — each step builds trust for the next:
Stage 1: Ambient Listening
Stage 2: Contact Center Automation
Stage 3: Patient Education and Medication Adherence
The technical work is not the slow part.
The actual obstacle is physician buy-in. Doctors are:
What actually works to overcome this:
| Strategy | Why It Works |
|---|---|
| Physician champions | Peers trust peers more than administrators |
| Aligned leadership | Provides authority and removes organizational friction |
| Individual coaching support | Meets clinicians where they are |
Every AI model in healthcare is probabilistic — meaning it can be wrong. This is not a flaw to eliminate; it is a reality to manage.
Your job is to build deterministic guardrails around probabilistic models.
Layer 1: System Prompt Steering
→ Instructions that shape how the agent behaves before any conversation begins
Layer 2: Input Validation
→ Catches adversarial or harmful inputs before the agent responds
Layer 3: Real-Time Output Evaluation
→ Every reply is checked against your policy before it reaches the patient
These are non-negotiable in healthcare AI:
What happens when a patient is distressed, angry, or in crisis?
The answer: Define your escalation threshold before go-live, not after.
Stop thinking of AI agents as software you configure. Start thinking of them as new hires you train.
The parallel:
| New Human Hire | AI Agent |
|---|---|
| Receives SOPs | Given standard operating procedures in system prompt |
| Learns from a knowledge base | Connected to a knowledge center |
| Trained on edge cases | Evaluated against antagonistic examples |
| Reviewed during probation | Tested before go-live |
| Ongoing performance reviews | Continuous PDSA cycles |
PDSA = Plan, Do, Study, Act — a continuous improvement loop used in healthcare quality management.
Operational Metrics (Is it being used?)
• Appointments booked per channel
→ Did patients actually use the agent, or did they call a human anyway?
• Agent deflection rate
→ How many calls did the agent resolve without human intervention?
• Minutes served / agents deployed
→ Adoption signal at the platform level
Experience Metrics (Is it helping?)
• Net Promoter Score (NPS) across patients, caregivers, and physicians
→ Rising NPS means the burden around care is falling
• CSAT (Customer Satisfaction Score)
→ Direct feedback on interaction quality
Key Insight: Most patients already like their doctors. If NPS is rising, it means the surrounding experience — scheduling, navigation, communication — is improving.
| # | Practice | Core Principle |
|---|---|---|
| 1 | Pick a hero journey | Depth before breadth |
| 2 | Fix data before automating | Garbage in, garbage out |
| 3 | Recruit physician champions | People change is harder than tech change |
| 4 | Onboard agents like new hires | Training, not just configuration |
| 5 | Make factual information deterministic | Look it up, don't infer it |
| 6 | Define escalation thresholds in advance | Plan for failure before it happens |
| 7 | Measure by channel and satisfaction | Adoption + experience, not just one |
Test your understanding before moving on:
Answers are embedded in the material above — if you cannot answer these confidently, revisit the relevant step before proceeding.