What Scribe does during a consultation
Scribe runs inside Patient Chat. When you start a recording, Scribe captures the full audio in the background without interrupting the consultation. Recordings are processed in smaller chunks, which keeps memory use stable — a session can run as long as the visit does, even for very long consultations. When you stop, the recording moves through up to three sequential stages:- Transcription — An ASR model converts the audio to text.
- Diarization (optional) — A diarization model separates the speakers so the output distinguishes the clinician’s contributions from the patient’s.
- Extraction — An LLM reorganizes the transcript into a predefined Extraction Template — for example, a SOAP note, a referral summary, or a medication review form. Templates aren’t limited to flat fields; they can nest objects and arrays, like a medication list with a name, dose, and frequency per entry.
Why it matters for clinicians
- Uninterrupted consultations: You can give the patient your full attention throughout the encounter, rather than dividing your focus between the patient and the keyboard.
- Consistent documentation: Because the output follows a predefined template, notes are structured consistently across all clinicians and all encounters, improving the quality of the clinical record.
- Reduced after-hours burden: Documentation that would otherwise be completed after clinic hours is handled automatically during the encounter, returning time to clinicians at the end of the working day.
Next
Build a Scribe Agent
Create a Scribe Agent on the Community Hub and configure its Extraction Template.
Train medical voice AI
Train a custom ASR model tuned to your specialty’s vocabulary.

