AI Engineer World's Fair 2026

From Ambient Documentation to Clinical Intelligence

Loading slides…

Read the talk

From Ambient Documentation to Clinical Intelligence

Abridge’s path from writing visit notes to contextual clinical assistance exposes the engineering demands of physician-calibrated evaluation, specialized models, and live order matching.

From a talk by Chaitanya Asawa

Before you start: Basic familiarity with language models and software workflows is helpful; no clinical training is assumed.

Finishing the visit without carrying the notes home

A clinician in Abridge’s opening testimonial reports finishing a 22-patient day by 4:30 p.m., with notes complete. Another describes the tool as indispensable to their practice. Others describe a change during the encounter itself: they can listen and look at the patient without continually deciding what to remember or enter into the computer. The benefit extends beyond the clinic to getting home afterward. These are individual accounts of the experience, rather than a controlled productivity measurement.

0:531:01
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

0:53 · section reference included

From promising technology to clinical adoption

Healthcare can still run on fax machines while presenting some of the hardest problems in applied AI. That combination frames Chaitanya Asawa’s move into the field: the opportunity is both to improve an established workflow and to build clinical intelligence around it.

Asawa began in research engineering at Vicarious, where the pursuit of artificial general intelligence involved neuroscience-inspired methods, probabilistic graphical models, and robotics. He then joined Glean to work on a problem he had experienced firsthand: workplace information scattered across systems, even though that context was essential to decisions. Asawa reports spending about six and a half years at Glean as it grew from ten people to more than 1,100.

His interest in healthcare came from a different contrast. He remembers seeing AI for skin-cancer detection on a Nature cover, then receiving a bill after a minor hospital visit and struggling to understand what he had paid for. Advanced technical capabilities existed alongside basic problems of cost and access. A seminar he organized with physicians, researchers, and entrepreneurs revealed how little of that promising technology was reaching clinics at the time.

When he returned to the field years later, the deployment picture had changed. Asawa reports that Abridge reached 300 US health systems in two to three years, naming Kaiser, Mayo, Johns Hopkins, and Sutter among its customers. Getting inside those systems created opportunities beyond documentation. He now leads engineering for clinical decision support and agentic experiences, where existing clinical context can inform assistance throughout a visit.

Journey slide with three columns labeled Vicarious, Glean, and Abridge, describing AI and robotics, enterprise assistance, and healthcare AI.Open full source frame
A career journey through Vicarious, Glean, and Abridge.
2:082:21
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

2:08 · section reference included

Why the clinical note was the entry point

The economic pressure is broader than documentation. In many industries, productivity improvements reduce the cost of producing goods. Asawa contrasts that pattern with rising healthcare administrative costs and a reliance on additional labor that cannot keep pace. He connects this partly to Baumol’s cost disease and partly to technology’s limited effect on healthcare productivity. Thin hospital margins, closures, patient debt, and clinician burnout make the consequences tangible; some doctors even discourage their children from entering the profession.

Clinical documentation offers a specific place to intervene. After each patient visit, a clinician must produce a note. A common structure is the SOAP note—subjective, objective, assessment, and plan—with details and formatting that vary by specialty. It records the patient’s complaint, the clinician’s assessment, and what should happen next. Asawa estimates that clinicians often spend about two hours a day writing notes, including after-work “pajama time.”

A clinical note is both an administrative record and an input to future care. It supports billing, but it also gives the next clinician context about the patient’s history. That context may need to travel across health systems. An error therefore has consequences beyond a poorly written document: it can affect financial records and the longitudinal medical record used in subsequent decisions.

Abridge started with this longstanding pain point because the technology had become capable of generating high-quality notes personalized to the clinician. Asawa describes documentation as an effective entry into a technology-reticent industry: clinicians already cared deeply about getting these records right. He credits the product with improving provider satisfaction, freeing capacity to see patients, and producing better records for billing and audits.

5:255:43
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

5:25 · section reference included

Building around the doctor–patient conversation

Asawa credits the documentation product alone with the adoption described earlier. The next step follows from where its information originates: the doctor–patient conversation. The note is one output, but billing, clinical-trial matching, and clinical decision support also depend on what happens in that encounter. Much of the administrative machinery surrounding care exists to carry information from the conversation into another workflow. Capturing the conversation creates a foundation for assisting those downstream workflows.

Nested coral rectangles connect conversations to clinical notes, coding and claims, care management, clinical trials, decision support, and clinical outcomes.Open full source frame
From clinical notes to broader work built around the conversation.
8:288:42
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

8:28 · section reference included

From trial eligibility to preparing tomorrow’s charts

The recorded demonstration begins with a clinician invoking “Hey, Abridge” and asking whether Nathan is eligible for any clinical trials. The assistant says he may qualify for the Abridge HF study: he remains symptomatic despite maximal therapy, and most screening criteria are already met. But eligibility is incomplete. An updated echocardiogram is needed to confirm his ejection fraction. The clinician requests that echo, and the demo responds, “Confirmatory echo ordered.” The next request moves beyond the current patient: prepare tomorrow’s charts.

The broader workflow covers both sides of the encounter. Before the visit, Abridge suggests discussion topics, including clinical and billing concerns. Afterward, it generates the patient visit summary and clinical note and prepares pended orders. The demo’s order confirmation should be understood in that review workflow: orders are prepared for clinician review and signature, rather than autonomously executed.

Three sources of context make this assistance possible:

  • The electronic health record (EHR): prior laboratory results, notes, and other patient history.
  • The live conversation: what the patient is experiencing now, which Asawa likens to the place where healthcare debugging happens.
  • Medical literature and clinical guidelines: sources against which patient-specific reasoning can be grounded.

The EHR supplies history, the conversation supplies the present encounter, and medical evidence supplies a basis for interpreting them together.

9:289:41
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

9:28 · section reference included

Making evaluation part of the operating system

The engineering objectives are familiar—quality, latency, and cost—but clinical assistance makes all three demanding. An incorrect workplace answer might be recoverable with limited consequences; an incorrect clinical answer can cause harm and destroy trust. During a live visit, an answer must also arrive while the information is useful, at an appropriate point in the conversation. Finally, inference must remain affordable at deployment scale. Asawa maps these objectives to the company’s aim to save lives, save time, and save money.

Abridge treats evaluation as an operating system for development, not a test performed just before launch. The sequence spans the product lifecycle:

  1. Build internal benchmarks before developing the product. Trial matching, note generation, decision support, and coding each need a robust reference set.
  2. Evaluate offline against cases encountered in practice. This establishes a starting point without assuming the benchmark captures every real-world condition.
  3. Release to a trusted clinician alpha group, then beta. Expand exposure gradually, with A/B testing at scale where appropriate.
  4. Continue monitoring after full rollout. A few successful prototype cases do not establish reliable behavior in clinical practice.

The staged release matters because offline evaluation cannot perfectly represent what happens when a product meets real encounters.

Clinicians embedded throughout the company calibrate LLM judges to encode the behavior they want from the product. This gives engineers who are not clinicians a feedback loop for improving it. The judges act as a reusable expression of domain expertise, while online signals add evidence from actual use: edits to generated notes, thumbs up or down, star ratings, and free-form feedback. Together, these signals support iteration throughout development and deployment.

11:0511:27
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

11:05 · section reference included

Answering a question whose context is unstated

Consider the provider’s question: “Does this patient meet the criteria for febrile neutropenia?” The request leaves much of its context unstated. A contextual decision-support system must retrieve previous laboratory values from the EHR, incorporate the live conversation, and use clinical guidelines and medical journals as reasoning sources. Answering the question requires assembling patient-specific evidence, not simply recalling a definition.

White question-and-answer panel asking whether a patient meets febrile neutropenia criteria and needs hospital admission, with paragraphs of clinical reasoning below.Open full source frame
A clinical question about febrile neutropenia and hospital admission, followed by a detailed response.

Evaluating that answer introduces a second hard problem. Sudoku has a useful asymmetry: finding a solution can be difficult, but checking a completed grid is straightforward. Clinical reasoning has a much smaller generator–verifier gap. A verifier capable of reliably determining the correct answer may need much of the same ability as the generator. Simply asking another language model whether the answer is right does not provide a sufficiently independent reference.

Abridge therefore uses multiple judges, each examining a different aspect of the response:

JudgeEvaluation focus
Clinical qualityWhether the response contains the right clinical content
Boundary and adversarialBehavior under boundary-testing and adversarial inputs
Clinical safetySafety of the response
Tone and styleHow the answer is expressed to the clinician

These are complementary signals. Each captures part of a quality problem that is difficult to measure with a single verdict.

14:5015:04
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

14:50 · section reference included

Human references without one golden answer

For the clinical-quality judge, the independent reference comes from physicians. A single golden response would be too restrictive: many differently worded answers can be clinically valid. Instead, Abridge starts with real clinical cases and asks physicians to specify the elements a good answer should contain. The reference is a rubric, rather than a paragraph the model must reproduce.

Asawa describes a four-clinician process:

  1. Two physicians independently create rubrics for the case.
  2. A separate physician adjudicates their work and combines it into a final rubric.
  3. A fourth clinician performs quality assurance on that rubric.

An LLM judge then compares the agent’s response with the required elements using semantic matching. This preserves room for valid variation in wording while giving developers concrete feedback about what the response includes or misses.

16:4916:59
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

16:49 · section reference included

Training for smaller clinical workflows

Rubric-based evaluation provides a target for improving agent architecture, models, and search ranking. Cost and latency then determine how that quality can be delivered during a live conversation. Asawa reports an annualized run rate of 100 million medical conversations. That is a measure of reported operating scale, not a count of completed encounters or a disclosed training-corpus size.

Clinical-note generation illustrates the opportunity for specialization. A note contains distinct sections, including history of present illness, past medical history, and assessment and plan. Instead of asking one foundation model to generate everything, Abridge decomposes the task into smaller workflows and post-trains smaller models, sometimes at the level of an individual section. A narrower task can require less general capability, allowing smaller models to serve it at lower cost and latency.

Asawa connects this strategy to a data flywheel from clinical conversations. He describes Abridge’s data advantage as unusually large, qualifying the comparison with what the company knows about other datasets. The strategic question is whether the team has distinctive data and sufficient focus to make model training worthwhile.

There are two different reasons to train:

  • Quality is already sufficient: preserve that quality while reducing cost and latency.
  • Quality still needs improvement: use distinctive data and a tightly defined clinical task to pursue quality gains faster than general frontier-model progress.

The second is a potential advantage, not a demonstrated guarantee of outperforming frontier models. The key is the combination of relevant data and concentrated effort on a problem that a general model developer may not prioritize.

17:5518:13
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

17:55 · section reference included

Spend inference when the conversation calls for it

In-visit orders expose another way to control inference cost. Clinicians mention medication and non-medication orders during the encounter. Abridge listens, queues those orders in the background, and leaves them for the clinician to sign off in the EHR. The goal is to remove the work of manually preparing orders while retaining the clinician’s approval step.

Invoking expensive order processing every few seconds would waste computation. Instead, the system looks for conversational events that justify heavier processing. Detecting that an order was mentioned is only the first task: the system must also match that mention to an approved, relevant order in the health system’s catalog. Cheap, fast gates determine when to hand the work to larger models.

An illustrative TypeScript interface makes the separation explicit. The gates decide whether a conversation event deserves more work; the matcher resolves it against the approved catalog; the output remains pending signature. The gate and matching implementations are separate dependencies because they perform different jobs.

typescript

type ConversationEvent = {
  text: string;
  encounterId: string;
};

type CatalogOrder = {
  id: string;
  name: string;
};

type PendingOrder = {
  encounterId: string;
  catalogOrderId: string;
  status: "pending-clinician-signature";
};

type OrderPipeline = {
  gates: Array<(event: ConversationEvent) => Promise<boolean>>;
  match: (
    event: ConversationEvent,
    approvedCatalog: readonly CatalogOrder[],
  ) => Promise<CatalogOrder | null>;
};

async function proposeOrder(
  event: ConversationEvent,
  approvedCatalog: readonly CatalogOrder[],
  pipeline: OrderPipeline,
): Promise<PendingOrder | null> {
  for (const gate of pipeline.gates) {
    if (!(await gate(event))) return null;
  }

  const match = await pipeline.match(event, approvedCatalog);
  if (!match || !approvedCatalog.some(order => order.id === match.id)) {
    return null;
  }

  return {
    encounterId: event.encounterId,
    catalogOrderId: match.id,
    status: "pending-clinician-signature",
  };
}

This structure separates the decision to spend inference from the harder task of resolving an order, and separates both from clinical authorization.

The closing invitation is to take healthcare seriously as an AI engineering domain. Asawa returns to his own earlier skepticism about whether promising technology could actually work inside clinical practice. He presents Abridge’s adoption as evidence that it can. The remaining work demands frontier capabilities under unusually high stakes: reliable clinical reasoning, evaluation grounded in physician judgment, and assistance that arrives affordably at the moment a clinician can use it.

19:4920:01
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

19:49 · section reference included

Resources

Transcript download
Full transcript

Loading transcript…