Features · Consultation notes

Notes built around problems, not paragraphs.

Every consultation is organised around SNOMED-coded problems - coded properly, laterality and all - with history, examination and assessment under each one, and everything you do linked to the problem it belongs to. Guidance and video sit beside the note, not in another tab.

SNOMED CT · laterality · episodicitypatient.info · NICE · video in contextcorrection · addendum · clarification
ehr.usejump.co.uk · New consultation · Margot Whelan · pat_M2vXn7q9
Consultation detailsDysuria+ Add problem
DysuriaSNOMED CT 49650001New episodeSignificant
History

Three days of dysuria and frequency. No fever, no flank pain. No visible haematuria. Second episode this year.

Examination

Apyrexial. Abdomen soft, mild suprapubic tenderness. No renal angle tenderness.

+ Family history+ Social+ Assessment / comment+ Add section
This visit · linked actions
Medication+Lab order+Referral+Observation+Procedure+Document+
RxMedicationAllergy check passedNitrofurantoin 100mg MR capsules100mg twice daily · 3 days · dm+d checked
LabLab orderUrine MC&Ssent · awaiting result
RecordReferenceVideo
Reference · pinned
UTI in womenpatient.info
UTI (lower): antimicrobialsNICE
Patient context
Allergies
Penicillin · anaphylaxis, 2019
Active medication
Metformin 500mgJump
Methotrexate 15mgExternally managed
Observationscoded · graphable
BP 132/84 · Temp 36.8°C

How it works

From opening the record to a signed, coded note.

Four steps, in the order they happen during a consultation. The structure does the organising; you do the medicine.

Step 1

Start on the details tab - verify, don't re-enter

Every consultation opens on a details tab with the patient's context beside you: allergies, active medication including externally managed medicines, and recent observations. A channel strip holds reference material - patient.info and NICE guidance - and video, pinnable so they stay in view while you type. You confirm what's there rather than typing it again.

allergies · medication · patient.info · NICE · video

Consultation detailstab 1 · always first
PatientMargot Whelan
DOB · NHS no.14-Mar-1962 · 943 476 5919
AllergiesPenicillin · anaphylaxis
Active medication8 · 2 externally managed

Step 2

Add a problem - and code it properly

A new problem is a blank, codeable tab: write into it straight away, then code it with one click or a search of the full SNOMED CT dictionary. And coding means proper coding: laterality, episodicity and significance are captured as data on the problem - "otitis media, left, new episode" - not buried in prose. Existing problems surface first so reviews attach to the right history, and a note can’t finalise until its problems are coded.

laterality · episodicity · significance · coded before finalise

What problem?existing problems + SNOMED CT
Otitis media65363002
Otitis externaSNOMED CT
Otalgia · existing problem16001004
QualifiersLeftNew episodeMinor

Step 3

Document under the problem - and act from it

Each problem carries its own clinical sections: history, examination, family and social history, assessment. Anything you do - issue a medication, order a lab, refer, record an observation - is created inline and linked to the problem, so the record shows what happened in the visit and why. Wrote free text first? Promote it into a coded problem with "Make into a problem". Observations file as coded measurements against the observation library, so every reading - blood pressure, weight, temperature - is graphable over time on the record.

linked objects · coded observations · graphable trends

Dysuria · linked objectscreated inline
Nitrofurantoin 100mg MR · 3 daysprescription
Urine MC&Slab order
Temp 36.8°C · suprapubic tendernessobservation
Safety-net advice letterdocument

Step 4

Finalise - and amend safely, forever

The narrative stays a draft until you finalise, so half-written prose never reads as a final note - but medications, allergies and observations are committed the moment they're captured, so safety checks protect the next prescriber even before you sign. After finalising, changes are typed amendments - correction, addendum or clarification - each with a reason, with the original preserved. And the finalise preview is rendered from the same source as the record itself, so what you sign is exactly what gets filed.

draft until finalised · safety data committed on capture

Finalise consultationdraft → record
Finalised Dr S. Mitchell14:52:08
1 problem coded · 4 linked objectswritten to record
A+AddendumUrine MC&S result reviewed: E. coli, sensitive. No change to plan.16 Apr 2026 · reason recorded · original preserved

What's included

From blank tab to audit-ready record.

What the consultation module covers today. If something you need isn't here, ask us on a demo call.

  1. 01Problem-led structureOne tab per SNOMED-coded problem, each with its own clinical narrative.
  2. 02Full SNOMED CT codingOne-click accept from matches, or search the full dictionary.
  3. 03Clinical sections per problemHistory, examination, family and social history, assessment.
  4. 04Promote free text"Make into a problem" turns notes into a coded problem, history intact.
  5. 05Linked clinical objectsPrescriptions, lab orders, referrals, observations and letters attach to their problem.
  6. 06Safety-first captureMedications, allergies and observations are committed immediately - checks see them before the note is signed.
  7. 07Consultation templatesSystem and custom templates, grouped by category, pre-populating sections and suggested problems.
  8. 08Template builderBuild your practice's own templates for the consultations you actually run.
  9. 09Reference in contextpatient.info and NICE guidance surfaced beside the note, pinnable while you type.
  10. 10Draft until finalisedHalf-written prose never reads as a final note.
  11. 11Typed amendmentsCorrection, addendum or clarification, each with a reason - originals preserved.
  12. 12Role-based accessPermissions control what each role can see and do in a consultation.
  13. 13Proper coding qualifiersLaterality, episodicity and significance captured as data on the problem.
  14. 14Coded observations, graphableMeasurements file against the observation library; every reading trends over time.
  15. 15Video in contextVideo consultations run beside the note, pinnable while you type.
  16. 16Sign what gets filedThe finalise preview shows exactly what will land on the record - nothing more, nothing less.

Connected

Everything you do lands on the problem.

Real-world acts - a prescription issued, an order sent, an invoice raised - are committed the moment they happen and linked to the problem that explains them.

dm+d · SignatureRx
Prescriptions

Issued from the problem, checked against the record, linked for the review that follows.

orders · results
Lab orders

Ordered inline; the problem shows what was sent and what came back.

referrals · letters
Referrals & letters

Generated in the consultation and filed against the problem they belong to.

Stripe · Xero
Invoices

Raised from the consultation, so billing matches what was actually done.

The first EHR I've used where writing the note is faster than the consultation itself. It feels like it was built by someone who has actually sat in clinic.
GP partner · private GP practice, London

Common questions

Questions, answered.

The questions clinicians most often ask about how Jump structures the note. If yours isn't here, ask us on a demo call.

Each problem is coded when you create it: accept a suggested match with one click, or search the full SNOMED CT dictionary. Existing problems surface first, so a review attaches to the right history instead of duplicating it. A consultation can't finalise while a problem is uncoded - which is how the record stays audit-ready without a tidy-up later.

See a problem-led note written end to end.

We'll run a full consultation on a 30-minute call - problem, coding, linked prescription, finalise - and leave a sandbox with sample patients for your team to try.