Skip to main content
Scribe runs inside a Patient Chat. You record audio — a visit, or your own dictation — or upload an existing recording; a Scribe Agent transcribes it and extracts the fields its template defines, and you send the structured draft into the chat as Markdown.
Isaree is a research version. Record synthetic visits only — no real patient audio.

Prerequisites

  • At least one Scribe Agent downloaded from the Isa Hub.
  • A patient to attach the Scribe session to — Scribe doesn’t run in Workspace.

Start a Scribe session

Open a Patient Chat and start a Scribe session from the round purple Scribe button on the right of the composer. The button is only visible when the composer is empty — start typing and it tucks itself away.

Choose a template

The Select Template sheet groups templates by the Scribe Agent that ships them. Pick the template that matches the note shape you want.

Route transcription and extraction

The Select Provider sheet comes next. Two switches control where the work runs, independently of each other:
  • Transcription & DiarizationOn-Device or Cloud. On-Device uses the ASR Model the Scribe Agent ships, plus its Diarization Model if it has one — a model that isn’t on the device yet downloads on first use. Cloud replaces both with ElevenLabs’ speech-to-text and diarization.
  • Extraction — On-Device or Cloud. On-Device runs the extraction LLM the Scribe Agent ships. Cloud sends the transcript to the provider and model picked in Settings → Scribe — OpenAI or Aki.io.
Each cloud step needs your own API key. You add or edit it right on this sheet — keys are stored in the iOS Keychain — and Continue stays disabled until every cloud step you’ve picked has one. A Scribe session is fully on-device only when both switches are On-Device.
If Extraction is marked Unavailable with “This package needs an update”, the Scribe Agent was published before Scribe Agents bundled an extraction LLM. Update it from the Isa Hub, or switch Extraction to Cloud for this session — see Troubleshooting.

Pick an audio source

The Audio Source sheet offers two ways in:
  • Record — capture the visit live with the microphone.
  • Upload Audio File — transcribe a recording you already have.

Record the visit

Recording shows a live waveform, a running timer, and three controls — discard, pause, stop. Long visits are fine: the recording is processed in chunks, so a session can run as long as the consultation does. Stop ends the recording and starts processing: transcription, then diarization if the Scribe Agent ships a Diarization Model, then extraction against the template’s fields.

Review the structured draft

When processing finishes, Isa shows the structured draft. The header carries the template name and a timestamp (SOAP - 25 May 2026, 14:16). The Original Transcript at the top expands to show the raw transcription — labeled by speaker if the Scribe Agent uses diarization, otherwise as one continuous block. Useful when you want to double-check what the Scribe Agent heard against what it extracted. Below the transcript, each field defined by the template renders as an editable section with a name, a short description, and a character counter. Edit any section directly before you send.
The quality of the extracted fields is bound by whichever model runs the Extraction step — on-device, that’s the extraction LLM the Scribe Agent ships. If extractions look thin or repetitive, try a Scribe Agent with a stronger extraction LLM, or route Extraction to a cloud provider. See Choose a model.

Send the draft into the Patient Chat

Save & Confirm drops the draft into the Patient Chat composer as Markdown, with each template field rendered as a section. Review the Markdown, edit as needed, and send. Cancel discards everything — the recording, the transcript, and the extraction — and returns you to the chat.

Understand what leaves your device

  • The recording is processed by whichever provider you’ve routed Transcription to. On-Device keeps the audio on the device; ElevenLabs sends it off-device.
  • The transcript is processed by whichever provider you’ve routed Extraction to. On-Device keeps the transcript on the device; a cloud provider sends it off-device.
  • The structured draft lands in the Patient Chat once you send it. Where the chat goes from there depends on the Primary Agent’s own routing — see Data and privacy.

Next

Patient Chat

Where Scribe runs and where the draft lands.

Settings

Pick the Primary Agent model and the cloud Scribe extraction model.

Build a Scribe Agent

Build your own template and ASR model on the Community Hub.