Jump vs Semble: Clinical Documentation Compared

Clinical documentation is the foundation of everything a GP practice does. The quality of your clinical record determines your ability to audit care, report on outcomes, share information with other providers, and defend your clinical decisions if challenged.

This article focuses specifically on how Jump EHR and Semble handle the core clinical documentation workflow: how consultations are structured, how clinical data is coded, how allergies and observations are recorded, and how AI assists the documentation process.

For the full deep dive into consultations - including templates, voice transcription, and the AI pipeline in detail - see our comprehensive consultations comparison. This article covers the essentials that most practices need to evaluate first.

The Fundamental Difference: Structured Data vs Free Text

The most consequential difference between Jump and Semble is architectural. It shapes how data is captured, stored, queried, and used.

Jump uses problem-oriented medical records (POMR) with SNOMED CT coding throughout. Every consultation is structured by the clinical problems being addressed. Each problem gets its own documentation sections, its own SNOMED code, and its own episode type (New Episode, Review, Flare Up, End Episode). A consultation covering three problems produces three distinct, coded, queryable clinical records.

Semble uses section-based free text. Clinicians create a consultation note, optionally choose a template, and write into sections. Problem headings can be marked active or inactive. The record is a clinical document - readable and useful - but not a structured clinical dataset.

Why This Matters

The practical consequences cascade through every aspect of clinical record-keeping:

• Querying and reporting. With POMR, a practice can ask "show me all patients with a diabetes review in Q4 where HbA1c was above 64." With free text, this requires manually reading every note.
• Clinical audit. CQC increasingly expects evidence-based care demonstrated through auditable data. SNOMED-coded records are auditable by definition. Free text requires manual review.
• Longitudinal records. SNOMED-coded problems with episode types build into a structured clinical timeline - not just a list of notes, but a queryable history of diagnoses and outcomes.
• Interoperability. SNOMED CT is the NHS standard. Coded records can be shared with other systems preserving clinical meaning. Free text loses its structure in transit.

Allergy Recording: A Clinical Safety Difference

How allergies are recorded is a patient safety issue, not just a documentation preference.

Jump records allergies as fully structured clinical data: SNOMED-coded allergen, five-level verification status (unconfirmed, provisional, confirmed, refuted, entered-in-error), type, category, criticality (high/low/unable to assess), onset date, and individually SNOMED-coded reaction manifestations covering anaphylaxis, angioedema, respiratory reactions, dermal reactions, and gastrointestinal reactions.

The five-level verification status is a clinical safety feature. A confirmed penicillin anaphylaxis is fundamentally different from an unconfirmed patient-reported intolerance - and that distinction should change prescribing decisions.

Semble captures allergies in a dedicated consultation section that appears in the patient summary by default for safety. However, structured coding of allergens, reaction types, and criticality classification is not documented in Semble's public help centre.

The difference: structured allergy data enables automated safety checks. Narrative allergy notes rely on the prescribing clinician reading and interpreting text.

Observations and Vitals

Jump captures observations as SNOMED-coded clinical measurements with UCUM (Unified Code for Units of Measure) units and reference ranges. Blood pressure, heart rate, respiratory rate, temperature, weight, BMI, HbA1c, eGFR - each carries abnormality flags and links back to both the consultation and the specific problem. Derived observations support auto-computation: a PHQ-9 total auto-computes from the nine individual values.

Observations become part of the patient's longitudinal record - queryable and trendable over time. A practice can track a patient's blood pressure readings across months and years as data, not as numbers buried in consultation notes.

Semble's consultation notes do not document a structured vitals or observations capture system within the consultation workflow. Vital signs would be recorded as free text within note sections.

AI-Powered Clinical Documentation

Jump: Record-Aware AI (Included)

Jump's AI consultation tool transforms freeform clinical text - typed or voice-transcribed - into SNOMED-coded structured data. The clinician works naturally, and the AI extracts:

• Multiple distinct clinical problems (up to five) each with SNOMED code candidates
• Observations and vitals with codes and units
• Structured allergy records with coded reactions and criticality
• Actionable tasks (referrals, investigations, follow-ups) with urgency and due dates
• Document suggestions when a referral letter or discharge summary is implied

The AI reads the patient's existing clinical record - active problems and allergies are fetched so it can deduplicate intelligently. If the patient already has asthma on their problem list and the clinician dictates an asthma review, the AI recognises this as a review, not a new diagnosis.

All AI suggestions are presented for clinician review before committing. Nothing is saved without approval. AI is included in the platform - no extra cost.

Semble: Heidi AI (Separate Product, Extra Cost)

Semble's AI comes through Heidi AI - a separate ambient scribing product at additional cost per licence per year. Heidi transcribes consultations and generates structured notes from 25+ template types.

The fundamental differences:

• What the AI reads. Jump reads the full structured clinical record. Heidi reads the consultation transcript only.
• What the AI produces. Jump produces SNOMED-coded structured data. Heidi produces narrative text.
• Cost. Jump's AI is included. Heidi is a separate subscription.
• Deduplication. Jump deduplicates against existing problems and allergies. Heidi cannot, because it doesn't access the patient record.

Consultation Templates

Jump's templates are SNOMED-coded clinical guides that follow clinical guidelines (NICE, GOLD, KDIGO) with six structured item types, conditional visibility, clinical intent tagging, priority levels, reusable blocks, and template immutability for medico-legal protection. Pre-built system templates cover common clinical scenarios.

Semble's templates are question-based forms with required/optional questions. They do not capture structured clinical data, support conditional logic, or provide reusable blocks.

Where Semble Has the Edge

• Video consultations. Semble's built-in video platform includes virtual waiting rooms, background blur, noise cancellation, and group calls up to 200 participants.
• Consultation diagrams. Anatomical diagram annotation for surgical and dermatological specialties.
• Simplicity. Section-based free text has lower cognitive overhead for clinicians who prefer narrative note-taking without structured data entry.

The Bottom Line

The choice between Jump and Semble for clinical documentation is a choice between two fundamentally different models of what a clinical record should be.

If your practice needs structured, coded, queryable clinical records for audit, governance, and reporting - Jump's problem-oriented, SNOMED-coded approach is in a different category. If your practice prefers fast, narrative note-taking with minimal structure and values built-in video consultations - Semble's approach has genuine advantages.

For practices building a scalable, data-driven clinical operation where CQC readiness, multi-site consistency, and long-term data value matter, Jump's clinical documentation model is the stronger foundation.