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.
Three days of dysuria and frequency. No fever, no flank pain. No visible haematuria. Second episode this year.
Apyrexial. Abdomen soft, mild suprapubic tenderness. No renal angle tenderness.
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
Step 2
Add a problem - and code it properly
Step 3
Document under the problem - and act from it
Step 4
Finalise - and amend safely, forever
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.
- 01Problem-led structureOne tab per SNOMED-coded problem, each with its own clinical narrative.
- 02Full SNOMED CT codingOne-click accept from matches, or search the full dictionary.
- 03Clinical sections per problemHistory, examination, family and social history, assessment.
- 04Promote free text"Make into a problem" turns notes into a coded problem, history intact.
- 05Linked clinical objectsPrescriptions, lab orders, referrals, observations and letters attach to their problem.
- 06Safety-first captureMedications, allergies and observations are committed immediately - checks see them before the note is signed.
- 07Consultation templatesSystem and custom templates, grouped by category, pre-populating sections and suggested problems.
- 08Template builderBuild your practice's own templates for the consultations you actually run.
- 09Reference in contextpatient.info and NICE guidance surfaced beside the note, pinnable while you type.
- 10Draft until finalisedHalf-written prose never reads as a final note.
- 11Typed amendmentsCorrection, addendum or clarification, each with a reason - originals preserved.
- 12Role-based accessPermissions control what each role can see and do in a consultation.
- 13Proper coding qualifiersLaterality, episodicity and significance captured as data on the problem.
- 14Coded observations, graphableMeasurements file against the observation library; every reading trends over time.
- 15Video in contextVideo consultations run beside the note, pinnable while you type.
- 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.
Issued from the problem, checked against the record, linked for the review that follows.
Ordered inline; the problem shows what was sent and what came back.
Generated in the consultation and filed against the problem they belong to.
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.”
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.
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.
