Prescribing & Medication Management

Both Jump EHR and Semble offer electronic prescribing for private UK clinics. But prescribing is not a single feature - it is a stack of interdependent capabilities: a drug database, clinical decision support, allergy checking, repeat prescription handling, pharmacy fulfilment, and audit controls. This article examines each layer to understand where the two platforms genuinely differ.

Summary comparison

• Drug database - Jump: NHS dm+d via Terminology Server FHIR API, real-time. Semble: Self-configured product catalogue; CloudRX-specific products for that integration.
• Drug-drug interaction checking - Jump: 70+ medication safety rules covering bleeding, respiratory depression, QT prolongation, serotonin syndrome, myopathy, and more. Semble: No documented interaction checking.
• Drug-allergy checking - Jump: Active, real-time ingredient-level alerts with drug-family cross-reactivity. Semble: Passive allergy display; no active alerts at prescribing.
• Drug-disease contraindication - Jump: Organ-system rules covering renal, hepatic, cardiac, respiratory, neurological, and pregnancy. Semble: No documented contraindication checking.
• Electronic prescribing - Jump: SignatureRx integration with PIN auth, IP logging, webhook lifecycle tracking. Semble: SignatureRx plus six additional pharmacy partners.
• Pharmacy integrations - Jump: SignatureRx with webhook lifecycle tracking. Semble: 7 pharmacies including SignatureRx, Pharmacierge, CloudRX, Somer, Clynxx, Smartway, Healistic.
• Repeat prescriptions - Jump: Full tracking with patient-facing safety questionnaire. Semble: Clinician-side repeats; no patient self-request.
• Document generation - Jump: Google Docs, SharePoint, built-in editor with merge fields. Semble: PDF generation with allergy text, clinician signatures.
• Controlled drugs - Jump: Records in medication list; AI highlights high-risk meds. Semble: Records with warning; blocks electronic CD prescribing.
• Dispensing labels - Jump: Not supported. Semble: DYMO/Zebra label printing.
• AI and prescribing - Jump: High-risk medication highlighting plus CDS clinical rationale at point of prescribing. Semble: Heidi ambient scribe (documentation, not prescribing safety).
• FP10 / EPS - Neither platform supports this (private platform).

The drug database question

Every downstream prescribing safety feature depends on the quality and structure of the underlying drug database. This is where the architectural difference between the two platforms is most pronounced.

Jump integrates directly with the NHS dm+d (Dictionary of Medicines and Devices) via the NHS Terminology Server FHIR API. When a clinician searches for a medication, the query hits the national Terminology Server in real time. The dm+d uses a strict product hierarchy - VTM (generic concept), VMP (prescribable product), AMP (branded product), and pack-level variants - and Jump's medication resolver maps any input code to the correct prescribable level through a seven-step resolution pipeline, including SNOMED-to-dm+d fallback mapping.

This is not a cosmetic distinction. dm+d product codes are the foundation that enables ingredient resolution, which in turn enables allergy cross-reactivity checking and drug-drug interaction logic. Without structured product codes, clinical decision support has nothing to reason against.

No public documentation specifies which drug database Semble uses. There is no mention of dm+d, BNF, or FDB Multilex. Medications appear to be configured as "Products" of type "Medication," and when using the CloudRX integration, items must specifically be CloudRX products. For a UK healthcare EHR, the absence of a standard clinical drug database is a notable gap - it means the safety features that depend on structured drug data (interaction checking, ingredient-level allergy alerts, contraindication rules) cannot function in the way clinicians would expect from primary care or secondary care systems.

Drug-drug interaction checking

Jump's clinical decision support engine evaluates over 70 database-driven medication safety rules in real time whenever a clinician selects a medication. The interaction rules are organised by clinical risk category:

Interaction groups covered

• Bleeding risk - NSAID + anticoagulant (hard stop), NSAID + antiplatelet (soft warning)
• Respiratory depression - opioid + benzodiazepine (hard stop, reflecting FDA black box warning)
• QT prolongation - two QT-prolonging agents combined (soft warning)
• Serotonin syndrome - SSRI + tramadol (soft warning)
• Myopathy risk - macrolide + statin via CYP3A4 inhibition (soft warning)

Each rule fires at one of three alert levels: hard (contraindication - prescribing requires documented clinical override), soft (caution - review and consider alternatives), or info (informational guidance). Within each group, alerts are deduplicated to the highest-severity match, preventing alert fatigue. Every alert includes a clinical rationale, suggested action, and recommended checks, displayed in an expandable explainer panel.

The CDS engine is database-driven: rules, parameters, and ValueSet definitions are stored in Supabase and can be updated without code redeployment.

No evidence of drug-drug interaction checking exists in Semble's documentation or help centre. Semble references "clinical decision support" and "built-in prescribing guidance" in its marketing, but these appear to refer to narrower features like the controlled drug warning banner and allergy display - not systematic interaction screening.

Drug-allergy checking

Jump performs active, real-time drug-allergy checking using SNOMED CT-based ingredient resolution. When a clinician selects a medication, the CDS engine resolves its active ingredients via dm+d, then checks each ingredient against the patient's documented allergies. This is not a passive display - the system fires alerts when a prescribed medication contains an ingredient that matches a recorded allergy.

Drug-family cross-reactivity is built in. The allergy service maps documented allergies to drug class codes using SNOMED CT structural hierarchies - penicillin, cephalosporin (with the 1-2% cross-reactivity flag), NSAIDs, sulfonamides, tetracyclines, quinolones, and macrolides. Specific allergen rules also cover neomycin, egg allergy (relevant for certain vaccines), gelatine (MMR, varicella, capsule formulations), and latex (vial stoppers, syringe components).

NKDA (No Known Drug Allergy) is enforced as mutually exclusive with active drug allergies - recording NKDA inactivates existing allergies, and recording a new allergy inactivates any existing NKDA record, preventing contradictory allergy states.

Semble displays allergies in the patient summary and can automatically print them on prescription documents. However, there is no active alert when prescribing a medication that conflicts with a documented allergy, no ingredient-level checking via SNOMED or dm+d, and no drug-family cross-reactivity logic. The allergy feature is informational - it surfaces data for the clinician to interpret manually.

Organ-system contraindication rules

Jump's CDS engine checks the proposed medication against the patient's active conditions. The rule set covers renal impairment (NSAIDs, metformin, aminoglycosides, digoxin, and nitrofurantoin with eGFR-dependent severity), hepatic disease (paracetamol dose limits, statins, methotrexate), cardiac conditions (NSAIDs in heart failure, QT-prolonging drugs in long QT syndrome), respiratory conditions (opioids and benzodiazepines in COPD), neurological conditions (tramadol and tricyclics in epilepsy, macrolides and aminoglycosides in myasthenia gravis), and pregnancy (valproate, ACE inhibitors, ARBs, retinoids, tetracyclines, and third-trimester NSAIDs).

Semble does not document any drug-disease contraindication checking.

Pharmacy integrations

This is where Semble's longer market presence delivers a clear advantage. Semble integrates with seven pharmacy partners - SignatureRx, Pharmacierge, CloudRX, Somer Pharmacy, Clynxx, Smartway, and Healistic - with no additional cost beyond what clinics pay the pharmacy providers directly. The breadth of choice is genuinely useful: different pharmacies suit different clinical scenarios (delivery vs. collection, specialist compounding, geographic coverage).

Jump currently integrates with SignatureRx as its primary electronic prescribing partner. The integration includes prescriber management, pharmacy and delivery contact selection, multiple fulfilment pathways (collection, delivery, named pharmacy), and - notably - webhook-based lifecycle tracking that provides visibility across the full prescription journey: created, dispensed, collected, and delivered. This level of status tracking gives practices real-time operational visibility that goes beyond simple submission.

Jump's prescribing architecture is built for multi-provider expansion - prescriptions are stored with a provider field and provider-specific metadata - but today, Semble offers more pharmacy choice.

Repeat prescriptions

Both platforms support repeat prescription tracking. Semble allows clinicians to set refill counts, duration, and review dates. The mechanics work: the prescribing clinician configures the repeat, and the system tracks the refill count against the authorised total.

Jump provides the same clinician-side tracking - authorised issue count, issued count, expiry date, review date, and authorising clinician - but adds a patient-facing repeat prescription request questionnaire. This is a structured, SNOMED CT-coded safety workflow that replaces free-text or phone-based repeat requests.

What the questionnaire covers

• Medication identification - which medication is being requested, with dosage confirmation
• Adherence - whether the patient has been taking the medication as prescribed (auto-coded to SNOMED)
• Side effects - a structured checklist (nausea, headache, dizziness, fatigue, GI symptoms, skin rash, muscle pain, mood changes) each mapped to a SNOMED code
• Safety - new medical conditions since last prescription, plus pregnancy status (flagged as requiring mandatory clinician review)
• Monitoring - optional blood pressure readings for patients on antihypertensives or other monitored medications

All questionnaire responses are surfaced as proposed clinical writes for clinician review - the system does not auto-authorise. The clinician sees structured, coded safety data and decides whether to reissue, adjust, or schedule a review.

Semble's user reviews consistently flag the inability for patients to request repeat prescriptions through the system as a gap. Jump's patient-facing questionnaire directly addresses this while adding a layer of structured safety checking that goes beyond a simple request form.

Electronic prescribing workflow

Both platforms generate electronic private prescriptions - neither supports NHS FP10 forms or connects to the Electronic Prescription Service, which is expected for private healthcare platforms. Both use electronic signatures compliant with The Human Medicines Regulations 2012.

Jump's workflow routes through SignatureRx with a secure 6-digit PIN for clinician authentication and captures the prescriber's IP address for the audit trail. Issuance options include draft (save for later), issue for collection, issue to a named pharmacy, and issue for home delivery. Prescription status is tracked via webhooks through the full lifecycle.

Semble's workflow is similar in principle: the clinician creates a prescription within a consultation note, selects the destination pharmacy, and submits electronically. The experience varies slightly depending on the pharmacy integration - CloudRX, for instance, requires selecting CloudRX-specific products, while SignatureRx follows a more standard flow.

Controlled drugs

Controlled drug prescribing is not fully supported by either platform - an honest assessment for both.

Jump records controlled drugs in medication records, and its AI document drafting system automatically highlights controlled drugs alongside anticoagulants and insulin as high-risk medications requiring additional clinical attention. However, Jump does not include a dedicated controlled drug register or Schedule 2-5 workflow differentiation.

Semble explicitly blocks electronic controlled drug prescriptions within the platform. The system records CDs in consultation notes and displays a "Controlled drug" warning, but clinicians must use separate methods (such as handwritten prescriptions) for Schedule 2-5 drugs.

Jump's approach is marginally more flexible - controlled drugs can be included in prescriptions - but neither platform offers a purpose-built CD workflow.

AI and prescribing

The two platforms apply AI to different parts of the prescribing workflow.

Jump's AI extends into prescribing safety: the clinical documentation system recognises high-risk medications during document drafting, and the CDS engine provides structured clinical intelligence at the point of prescribing. Each alert includes a clinical rationale, suggested action, and recommended checks - this is actionable guidance, not just a warning icon.

Semble's AI capability comes via the Heidi integration, which provides ambient clinical documentation and scribing - transcribing consultations and generating structured notes. Heidi does not suggest medications, generate prescriptions, or provide prescribing safety decision support. The two AI approaches serve different purposes: Heidi focuses on documentation efficiency; Jump's AI focuses on prescribing safety.

Where each platform leads

Jump's advantage is clinical safety infrastructure - dm+d integration, drug-drug interaction checking, ingredient-level allergy alerts with cross-reactivity, organ-system contraindication rules, and a patient-facing repeat prescription safety questionnaire. For clinicians whose primary concern is prescribing safely, Jump provides decision support that Semble does not currently offer.

Semble's advantage is pharmacy partnership breadth and operational features - seven pharmacy integrations, dispensing label printing for DYMO/Zebra printers, and a more established market presence. For clinics that prioritise fulfilment flexibility and have existing pharmacy relationships across multiple providers, Semble offers more choice today.

The distinction is architectural. Jump has invested in the clinical safety stack - the drug database, ingredient resolution, interaction rules, and structured allergy checking that underpin safe prescribing at the point of care. Semble has invested in the fulfilment network - the pharmacy partnerships, label printing, and operational breadth that support prescription delivery. These are different priorities serving different clinical concerns, and the right choice depends on which layer matters most to the practice making the decision.