About Jump
Private practice shouldn’t mean second-class clinical safety.
Jump is an electronic health record for UK private GP practices. Properly coded records, prescribing checks that fire before the script goes out, and an audit trail that still holds up months later - in software a two-clinician practice can run without an IT department.
The trade-off nobody should have to make.
One kind is a booking and billing tool with a clinical text box bolted on. The other does coded problems, interaction checking and structured medication histories - and is procured by NHS organisations, priced for them, and configured over months.
So a private GP assembles the job out of parts. A diary here, a Word template there, a spreadsheet for recalls, and a growing folder of PDFs that only one person knows the shape of. It works, right up until it has to be evidence.
The part that gets dropped is almost never the invoice. It is the coding, the audit trail, and the safety net that only matters on the day it matters. Not because anyone decided patient safety was optional, but because the software made one easy and the other manual.
We built Jump on the opposite premise. The record comes first, and the booking, the prescription, the letter, the invoice and the follow-up all hang off it. Not to give clinicians more admin, but because a record that is correct at the moment of care is the only version that is still correct a year later, when somebody asks.
Four things we have argued about more than once.
Each of these started as a disagreement inside the team, and each one still costs us something to hold to. They are here because they explain decisions you will run into if you use the product.
- You have to code the problem before the note can be finalised
- This is the thing people push back on hardest in demos, and we have never found a version of it we were willing to relax. Coding at the point of care is slower than typing free text and moving on. But the alternative is a record that gets reconstructed later by someone who was not in the room, and in practice that reconstruction either does not happen or happens badly. So the constraint stayed, and the effort went into making the coding quick instead: existing problems surface before new ones, a suggested match is one click, and the full SNOMED CT dictionary is there for when the suggestion is wrong.
- The clinical safety features are not part of what you are choosing between
- Pricing is per user with volume discounts, and there is one plan. Commercially it would be easy to move prescribing checks or the audit trail into a higher tier, because those are exactly the things a buyer will pay more to get. Our view is that a practice choosing the cheaper option is the practice least able to absorb a missed interaction, so there is no cheaper option and nothing to upgrade to.
- We would rather show you a screen than describe a capability
- Software in this category tends to get marketed in the abstract, which makes it impossible to evaluate and very easy to overstate. Every clinical string in a product image on this site is a real one, down to the dm+d product names, the SNOMED concept IDs and the units. The feature pages are written against what was in the product on the day they were published, and where something is not built yet it does not appear.
- The interface stays quiet, even where a warning would get more attention
- Clinical systems have a habit of escalating everything at once: colour-coded banners, competing alerts, counters that never reach zero. What people learn from that is how to dismiss them, including the one that mattered. Jump reserves colour for state that genuinely needs a decision, which does mean parts of it look less urgent than they would in a system designed to demo well.
One record, and sixteen features that write to it.
Coded notes, checked prescriptions, online booking, billing, filing, recalls and the automation between them. Every feature page describes what ships, which is why they are worth reading before a demo rather than after.
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.
“CQC inspection passed with full clinical governance evidence. Prescribing audit trails and SNOMED-coded consultations. Appointment and billing workflows unchanged.”
The positions we publish in full.
Jump EHR is provided by Use Jump Limited. Where we are mid-way through a standard we say so on the page rather than in a footnote.
How Jump supports clinical decisions, where its limits are, and how incidents get reported and handled. It says plainly that Jump is a support tool and does not replace professional clinical judgement. The DCB0129 risk-management work is in progress, which is why it says pending rather than certified.
Encryption, access control, infrastructure and application security, sub-processors, backup and recovery, personnel, and how to report a vulnerability to us.
Where AI is used in Jump and where it is not. It does not write clinical content. What it does produce is non-clinical, and it is put in front of you to confirm before it goes anywhere near the record.
The DPA itself, the sub-processors we rely on, and our position on the national data opt-out, alongside the privacy notice.
Also published: our privacy policy, terms of service and cookie policy.
See whether the record-first argument holds up.
Thirty minutes end to end: book, consult, prescribe, invoice, follow up. Then a sandbox with sample patients, so your team can decide for themselves.