What if Scribe mishears something, or gets a problem wrong?

You review and correct the transcript before anything is structured from it, and you review the draft again before accepting - fix a wrong match to an existing problem, add one Scribe missed, or remove one you don't want. Change the draft and one Redraft reorganises the whole thing against your edits and the same transcript, rather than patching around a single change.

Can a problem or observation file if it's not fully coded?

No. Every problem needs a code and every observation needs its required fields before you can accept - a one-sided blood pressure reading, for instance, is flagged as needing detail rather than filed as if it were complete. Dismiss anything that isn't relevant; complete or correct the rest.

Does the draft land in the normal consultation record?

Yes. Accepted problems and observations write into the same consultation you'd get from typing directly - coded, matched against the patient's existing problem list, gradable over time - and you finalise it the same way. See how the record itself is structured on the consultation notes page.

Can I stop and type instead, or use Scribe for part of the consultation?

Yes, at any point. Scribe is one way to start a note, not the only way. Stop the recording and type directly, or record part of the consultation and finish the rest by hand - the note is the same note either way.

Features · AI Scribe

Record the consultation. Review a structured draft, not a blank page.

Scribe listens to the consultation and turns the conversation into a draft: a problem for each condition discussed, with a suggested SNOMED code for anything you named, and readings like blood pressure or temperature lifted straight into coded fields. Nothing files until you've reviewed it.

Book a demo See how it works

structures what's saidSNOMED CT on named problemsyou review before anything files

ehr.usejump.co.uk · New consultation · Scribe

TranscriptDraft

Otitis mediaSNOMED CT 65363002LeftNew episode

Observations

Temperature 37.9°CCoded · complete

Blood pressure 138/-Needs detail

RedraftAccept & insert+

Transcript · live

Dr Adeyemi And how long has the ear been sore?

Patient Since yesterday evening, and I've had a temperature since this morning.

Dr Adeyemi Left side. Let's take your blood pressure while we're at it - that's a hundred and thirty-eight over...

Duration04:12

StatusRecording

Reconnects automatically if the call drops.

Step 1

Start recording, then review the transcript

Start Scribe and it transcribes as you talk. Nothing goes further until you stop and confirm the transcript, so a mishearing gets corrected before anything downstream reads it. If a connection drops mid-consultation, the session picks back up rather than starting over - a refresh doesn't lose it either.

live transcription · reviewed before structuring · survives a drop

Transcriptlive

Dr Adeyemi

And how long has the ear been sore?

Patient

Since yesterday evening, and I've had a temperature since this morning.

Step 2

Confirm, and Scribe structures what was said

Once you confirm the transcript, Scribe drafts a problem for each condition discussed and suggests a SNOMED code for what was actually named - existing problems on the record surface first, so a review attaches to the right history instead of creating a duplicate. Readings mentioned in conversation - a temperature, a blood pressure, a weight - are pulled into the same coded observation fields the rest of the record uses, so they graph over time instead of sitting in prose.

existing-problem matching · SNOMED CT · coded, graphable observations

Draftfrom transcript

Otitis media · left · new episode65363002

Temperature 37.9°Cobservation

Step 3

Edit the draft, and Scribe redrafts around it

The draft is a starting point, not a decision. Add a problem Scribe missed, remove one, or correct a wrong match to an existing problem - then Redraft once and Scribe reorganises the whole draft against your changes and the same transcript, so a symptom you pulled out into its own problem doesn't stay buried under the one it was drafted under. A batch of edits becomes one redraft, not one per change.

add · remove · re-code · one redraft against the same transcript

Edited problem listpending redraft

Otitis media · leftkept

Feveradded

Redraft

Step 4

Nothing files until every problem and observation is complete

Before you can accept, every problem needs a code and every observation needs its required fields filled - Scribe won't let a one-sided blood pressure or an uncoded problem through as if it were finished. Dismiss anything that isn't relevant, complete what's flagged, then accept: everything writes into the consultation exactly as if you'd typed it, ready to finalise.

hard gate on incomplete coding · writes to the normal record

Draft · reviewbefore accept

Otitis media · left · new episodecoded

Blood pressure 138/-needs detail

Accept & insert+

01Live transcriptionStarts and stops with the consultation; review and correct before anything is structured.
02Session survives a dropA lost connection or an accidental refresh picks the session back up, not back to zero.
03Problem drafting from the transcriptOne problem per condition discussed, in the words used during the consultation.
04Existing-problem matchingSurfaces the patient's own history first, so a review attaches instead of duplicating.
05SNOMED coding on what was saidA suggested code for each problem named in the conversation - not invented from it.
06Coded, graphable observationsVitals and readings mentioned in the consultation land as coded fields, not free text.
07Steerable redraftAdd, remove or re-code a problem, then redraft once against the same transcript.
08Completeness gate before filingEvery problem coded and every observation's required fields filled, before Accept.
09Dismiss what's not relevantAnything drafted that you don't want can be dismissed, not just left unticked.
10Writes to the normal recordAccepted problems and observations land in the same consultation as anything typed by hand.
11You review every lineNothing reaches the record without a clinician confirming it first.
12Role-based accessThe same permissions model as the rest of the consultation.

from what’s said

Transcribes and structures

Turns the conversation into a problem list, coded observations and a note draft - organising what was said, not adding to it.

named in the transcript

Suggests coding

Matches a SNOMED code to a problem or observation because you said it - never a code you didn’t mention.

you decide

Diagnosis and treatment stay yours

Scribe does not suggest a diagnosis, propose a treatment, or recommend what to do next - that judgement is never something it offers.

before anything files

You review every line

Complete, correct or dismiss each problem and observation; nothing reaches the record without your review.

“I stopped writing the note during the consultation and started writing it after, from a draft that already has the problem, the code and the readings sitting there. Correcting a draft is a different job to starting one from nothing.”

GP partner · private GP practice, Bristol

Common questions

Questions, answered.

The questions clinicians most often ask about Scribe. If yours isn't here, ask us on a demo call.

No. Scribe documents the consultation - it structures what was said into problems, observations and a note draft, and suggests a SNOMED code for a condition you've explicitly named. It doesn't generate a diagnosis, propose a treatment, or suggest what to do next. That judgement is never something it offers; it stays a decision you make.