Uploaded May 2026 | Updated September 2026, 2 weeks ago
Janie Lee and Chaitanya “Chai” Asawa of Abridge join us for a crossover episode with Redpoint’s Jacob Effron to dive into how Abridge is building the clinical intelligence layer for healthcare starting with ambient documentation, then expanding into clinical decision support, prior authorization, payer/provider/pharma workflows, and eventually real-time agents that act before, during, and after the patient conversation. We go inside the product, data, infra, evals, workflow, privacy, and org design choices behind bringing AI into one of the highest-stakes enterprise environments from 100M+ medical conversations and specialty-specific evals to real-time alerts, EHR integration, de-identification, clinician-scientist teams, and why healthcare may solve some of the hardest AI problems first.
We discuss:
• Why Abridge started with clinical documentation, “pajama time,” and saving clinicians 10–20 hours a week
• The transition from ambient scribe to clinical intelligence layer: save time, save money, and ultimately save lives
• Why conversations between patients and clinicians may be the most important workflow in healthcare
• Chai’s “healthcare-coded Glean” framing: context is king, but healthcare raises the stakes on safety, evals, and rollout
• Why Abridge wants AI to feel like “air conditioning”: always in the background, but only interrupting when it truly matters
• The prior authorization example: turning a denied MRI weeks later into real-time guidance while the patient is still in the room
• Why payer policies, EHR data, medical literature, and hospital-specific guidelines make the problem hard—and also create the moat
• How Abridge thinks about ambient form factors: mobile, desktop, in-room devices, nursing workflows, multimodality, and future AR
• The multi-sided healthcare customer: CMIOs, CFOs, CIOs, clinicians, patients, payers, and pharma
• The hardest AI problem at Abridge: high-quality, low-latency, low-cost real-time support in a high-stakes clinical setting
• When Abridge uses frontier models vs proprietary models, and why its unique data from medical conversations matters
• Why “every agent is a coding agent underneath,” and how the EHR can be thought of as a filesystem for healthcare agents
• How Abridge approaches personalization across individual doctors, specialties, and health systems
• Why “AI slop” is AI without context, and how edits, memories, and clinician preferences create a data flywheel
• Abridge’s eval stack: LFDs, LLM judges, in-house clinicians, third-party evaluators, specialty-specific evals, and progressive rollout
• HIPAA, PHI, de-identification, one-way anonymization, customer contracts, and learning from healthcare data safely
• What changes when you operate at 100M+ conversations: reliability, cost, post-training, model routing, and infrastructure optimization
• Why the same clinical conversation can serve doctors, patients, payers, pharma, and future clinical-trial workflows
• How Abridge works with EHRs, and why deep interoperability is table stakes for clinician adoption
• Why healthcare AI has regulatory tailwinds, why 80/20 does not work here, and why high-stakes domains may drive AI forward
• Why Abridge embeds “clinician scientists” into product and eval teams
• What Chai learned from Glean about search, quality, and durable AI infrastructure
• Why the future of AI infra may look like context layers, event-driven systems, Kafka, Temporal, sockets, CRDTs, and tools built for humans
• Why Janie changed her mind on “PRDs are dead,” and why crisp written clarity matters more in complex AI products
• How Abridge uses Claude Code, Cursor, and coding agents internally
—
Abridge
Website: abridge.com
X: https://x.com/AbridgeHQ
Janie Lee
LinkedIn: linkedin.com/in/janiejlee
Chaitanya “Chai” Asawa
LinkedIn: linkedin.com/in/casawa
Timestamps
00:00:00 Introduction
00:01:17 What Abridge does
00:03:22 From ambient documentation to clinical intelligence
00:05:21 Clinical decision support and context as king
00:08:14 Alert fatigue, proactive intelligence, and prior authorization
00:13:53 Ambient AI form factors and healthcare customers
00:18:16 The hardest AI problems in healthcare
00:19:43 Frontier models, proprietary data, and model strategy
00:22:24 The EHR as a filesystem for agents
00:25:20 Personalization, memory, and clinician preferences
00:31:57 Evals, LLM judges, and progressive rollout
00:38:04 HIPAA, de-identification, and privacy
00:40:38 100M conversations and operating at scale
00:45:27 EHR integration and the clinical intelligence layer
00:47:56 Healthcare regulation, latency, and high-stakes AI
00:51:28 Clinician scientists and long-tail quality
00:54:21 Lessons from Glean and durable AI infrastructure
00:58:20 The future of agentic healthcare workflows
00:58:51 PRDs, product clarity, and building serious AI products
01:04:28 AI coding tools at Abridge
01:05:23 Outro
Janie Lee and Chaitanya “Chai” Asawa of Abridge join us for a crossover episode with Redpoint’s Jacob Effron to dive into how Abridge is building the clinical intelligence layer for healthcare starting with ambient documentation, then expanding into clinical decision support, prior authorization, payer/provider/pharma workflows, and eventually real-time agents that act before, during, and after the patient conversation. We go inside the product, data, infra, evals, workflow, privacy, and org design choices behind bringing AI into one of the highest-stakes enterprise environments from 100M+ medical conversations and specialty-specific evals to real-time alerts, EHR integration, de-identification, clinician-scientist teams, and why healthcare may solve some of the hardest AI problems first.
We discuss:
• Why Abridge started with clinical documentation, “pajama time,” and saving clinicians 10–20 hours a week
• The transition from ambient scribe to clinical intelligence layer: save time, save money, and ultimately save lives
• Why conversations between patients and clinicians may be the most important workflow in healthcare
• Chai’s “healthcare-coded Glean” framing: context is king, but healthcare raises the stakes on safety, evals, and rollout
• Why Abridge wants AI to feel like “air conditioning”: always in the background, but only interrupting when it truly matters
• The prior authorization example: turning a denied MRI weeks later into real-time guidance while the patient is still in the room
• Why payer policies, EHR data, medical literature, and hospital-specific guidelines make the problem hard—and also create the moat
• How Abridge thinks about ambient form factors: mobile, desktop, in-room devices, nursing workflows, multimodality, and future AR
• The multi-sided healthcare customer: CMIOs, CFOs, CIOs, clinicians, patients, payers, and pharma
• The hardest AI problem at Abridge: high-quality, low-latency, low-cost real-time support in a high-stakes clinical setting
• When Abridge uses frontier models vs proprietary models, and why its unique data from medical conversations matters
• Why “every agent is a coding agent underneath,” and how the EHR can be thought of as a filesystem for healthcare agents
• How Abridge approaches personalization across individual doctors, specialties, and health systems
• Why “AI slop” is AI without context, and how edits, memories, and clinician preferences create a data flywheel
• Abridge’s eval stack: LFDs, LLM judges, in-house clinicians, third-party evaluators, specialty-specific evals, and progressive rollout
• HIPAA, PHI, de-identification, one-way anonymization, customer contracts, and learning from healthcare data safely
• What changes when you operate at 100M+ conversations: reliability, cost, post-training, model routing, and infrastructure optimization
• Why the same clinical conversation can serve doctors, patients, payers, pharma, and future clinical-trial workflows
• How Abridge works with EHRs, and why deep interoperability is table stakes for clinician adoption
• Why healthcare AI has regulatory tailwinds, why 80/20 does not work here, and why high-stakes domains may drive AI forward
• Why Abridge embeds “clinician scientists” into product and eval teams
• What Chai learned from Glean about search, quality, and durable AI infrastructure
• Why the future of AI infra may look like context layers, event-driven systems, Kafka, Temporal, sockets, CRDTs, and tools built for humans
• Why Janie changed her mind on “PRDs are dead,” and why crisp written clarity matters more in complex AI products
• How Abridge uses Claude Code, Cursor, and coding agents internally
—
Abridge
Website: abridge.com
X: https://x.com/AbridgeHQ
Janie Lee
LinkedIn: linkedin.com/in/janiejlee
Chaitanya “Chai” Asawa
LinkedIn: linkedin.com/in/casawa
Timestamps
00:00:00 Introduction
00:01:17 What Abridge does
00:03:22 From ambient documentation to clinical intelligence
00:05:21 Clinical decision support and context as king
00:08:14 Alert fatigue, proactive intelligence, and prior authorization
00:13:53 Ambient AI form factors and healthcare customers
00:18:16 The hardest AI problems in healthcare
00:19:43 Frontier models, proprietary data, and model strategy
00:22:24 The EHR as a filesystem for agents
00:25:20 Personalization, memory, and clinician preferences
00:31:57 Evals, LLM judges, and progressive rollout
00:38:04 HIPAA, de-identification, and privacy
00:40:38 100M conversations and operating at scale
00:45:27 EHR integration and the clinical intelligence layer
00:47:56 Healthcare regulation, latency, and high-stakes AI
00:51:28 Clinician scientists and long-tail quality
00:54:21 Lessons from Glean and durable AI infrastructure
00:58:20 The future of agentic healthcare workflows
00:58:51 PRDs, product clarity, and building serious AI products
01:04:28 AI coding tools at Abridge
01:05:23 Outro
