Release notes

Consent given on your booking pages is now honoured by your own tags

If your practice has its own marketing or analytics tags on your public booking and patient-link pages, a patient accepting cookies wasn't passed on to them — so the tags stayed switched off even though consent had been given, and your reporting under-counted.

Accepting or declining now applies to both Jump's own analytics and your practice's tags. A choice a patient made previously is honoured too — they aren't asked again, and their saved answer is applied rather than being treated as no answer.

Declining still switches everything off.

Three smaller corrections

A greyed-out Reschedule button says what's missing. Rescheduling from the diary could offer a disabled button with no explanation; it now tells you what it needs.

An appointment type is labelled Paid only when the patient is actually charged. The label appeared on types the patient is never charged for.

A notification no longer suggests your SMS is switched off. A message whose delivery hadn't resolved yet read as though sending was disabled, rather than simply not confirmed.

Clear about what happened, and never silent

When a clinical entry couldn't be saved, what you saw varied: sometimes an internal message about drafts or context, sometimes an error code, and in one case nothing at all.

• A failed clinical save now reads as one plain sentence — "We couldn't save this observation — nothing was recorded. Please try again in a moment." You're told the entry was not recorded, so there's no doubt about whether to try again.
• No failed clinical write is silent. A path that failed without saying so now reports it.
• Error messages no longer leak internal detail into what you read.

Readings captured by the scribe are no longer lost to a momentary timing problem — they're retried rather than dropped.

Two fixes to managing your plan and invoices

Finishing in the billing portal brings you back to Jump, rather than leaving you on the portal's own home page wondering whether what you did had worked.

An invoice payment Stripe won't accept now tells you which line is the problem, instead of failing with a general message and leaving you to work out which of them it meant.

You decide when day passes are bought

Day passes are topped up automatically when your practice runs low. If you would rather buy them deliberately — to keep control of what gets charged, or because you would prefer to be asked — you can now turn automatic top-ups off.

Leave it on and nothing changes.

You will find the setting with your day passes at Settings → Plan.

The price in the picker is the price on the line

A pathology test cost more than the picker said it would. The catalogue popover showed the lab's list price without your practice's markup applied, then added the line with the markup on — so a test shown at £113.00 landed on the invoice at £141.25. You could quote a patient the lab's cost price without realising. The picker and the line now price through the same rule, so what you're shown is what you add.

A test no longer appears twice. Adding a pathology test to an invoice creates a matching product behind the scenes so it can be billed, and that product then showed up in the search too — leaving you choosing between two identical-looking entries for one test. Only the pathology entry is shown now, and it prices live from the lab's current list price with your markup. Your own products, and anything migrated from a previous system, are untouched.

Three fixes to the tables you insert into a letter

An empty table now says it's empty, instead of writing a sentence you didn't type. Inserting "Consultation table (last 3)" for a patient with no consultations put the words "No consultations recorded." into the document as a paragraph — indistinguishable from something you had written. Inserting now reports that there was nothing to insert and leaves the letter untouched. Medication, allergy and problem tables all behave the same way. A template applied to an empty patient keeps its placeholder rather than leaving a gap, so the letter still says what was expected there.

The consultations you pick keep the order you picked them in. Selecting specific consultations for a table no longer silently reorders them.

Long lists are complete. A patient with more than 1,000 medications, allergies, problems or consultations had the list quietly cut off at 1,000 — no warning, just missing rows. Every clinical table now pages through the whole record.

A template scaffolds your consultation; it never forces it

A required observation with no value used to disable the Submit button outright. So a template that asked for a blood pressure could stop a clinician filing the record at all — when the patient declined, the equipment wasn't available, or the reading simply wasn't indicated that day.

Now:

• Outstanding items prompt, they no longer gate. You can always file the consultation.
• You can record why an observation was not taken — the patient declined, equipment unavailable, not clinically indicated today — and the item is satisfied by that reason just as it would be by a value.
• The reason goes into the note and into the record, reading as e.g. "Systolic blood pressure: not recorded — Patient declined", so the record carries a stated clinical decision rather than a silent gap.
• Template authors choose what's required. Required is now an explicit setting on an observation rather than being inferred from what an item is for.

Existing templates are unchanged — one that doesn't set the new flag asks for exactly the same items it always did.

This is a beta feature, part of the redesigned consultation module, and off by default.

History imported from another system now reads in the right order

Consultations are ordered by when the note was written, so a note you write today about last month's appointment appears at the top where you expect it.

For a consultation imported from a previous system there is no written date — the only timestamp is when the import ran. Ordering by it put a patient's history into the order the records happened to be loaded in, which is arbitrary: a history could read 2026, 2024, 2025, 2026, and a card for a 1958 encounter could be labelled as though it had been written this year.

Now:

• A consultation you wrote in Jump is ordered by when you wrote it, and shows that date — exactly as before.
• An imported consultation is ordered by when the care actually happened, and shows that date. No written date is displayed, because there isn't one.

Ordering, the month headings and the date each card leads with all come from one shared rule, so they cannot disagree with each other.

If your practice's history was migrated into Jump, this changes the order of most of your consultation lists — to the clinically correct one.

Across Jump

Several interface faults are fixed: the sidebar and top bar stay in view when you change section, a drawer opened from inside another drawer is visible and full height, the top bar keeps its title while a screen loads, and lists that name colleagues now actually name them instead of showing blanks.

On the Control Centre, one handled fault no longer hides the next one, and the patient-safety report link goes somewhere that exists.

Clinical

Three things that read wrongly now read as intended:

• A lab result the laboratory sent no report for still produces a PDF, instead of failing to open.
• A professional message that could not be sent says why.
• A consultation's version history describes what happened in words, rather than showing a raw code.
• A Medichecks order is only marked venous once it carries more than one blood test.

Scheduling

Booking into a clash now offers the override in place, rather than closing the dialog and making you start again.

Billing

The plan page reads the real price from Stripe rather than assuming a standard rate, so a practice on negotiated pricing sees its own figure.

A single unrecognised price no longer takes the whole billing portal down with it, and a scheduled change that has gone stale now heals on the next update rather than continuing to promise something that was already reversed.

Billing

An invoice recorded in GBP now shows a pound sign whichever way the currency was stored. Some invoices were rendering the currency code instead.

The Credit / refund screen also opens with the amount filled in, rather than showing a broken figure, and the customer field says it is loading instead of looking empty.

A patient booking for themselves must always reach someone, so Jump does not let a pathway rule make those bookings silent. The check was only recognising some of the ways a patient can book, so a rule naming the most common ones - an online booking, or a public booking link - could be set to silent after all.

Every patient-led booking source is now covered. Booking source has also been simplified in the editor to two groups, patient-led and practice-led, which is the distinction the rules actually turn on.

Recalls

Recall triggers now run across every patient in a practice. A cap in the underlying query meant that beyond a thousand patients, the rest were silently skipped — no error, just recalls that never fired.

If your practice is larger than that, recalls you expected and did not see should now appear.

Changing two things on a trigger in quick succession - the assignee, then the priority - could see the second change quietly undo the first. Both saves reported success and nothing said otherwise.

Both changes now hold. If you have edited a pathway recently, it is worth opening it once to check the settings read as you intended.

Across Jump

When a request fails behind the scenes, Jump now passes through what actually went wrong instead of collapsing it into a generic error.

A message that names the real cause is one you can act on, or send to us and get a straight answer about. Moving between sections is also quicker: Jump starts loading a screen while your pointer is still travelling to it.

A practice using Roseway could find it missing from the prescribing-provider picker, leaving only the other provider available, with no obvious way to get it back.

The connection was working the whole time. Issuing a prescription triggered a follow-up request that the provider had not granted that practice permission for, and the refusal was recorded as though the whole connection had failed - which took the provider out of the picker for everyone at the practice.

A refusal of one particular request is no longer treated as the connection being down, so the provider stays available. Practices affected by this do not need to reconnect anything.

Four changes so the pathway editor describes what your inbox is really doing.

Only pathways that can route are offered. The editor listed pathways that had never produced anything and could not, alongside working ones, with nothing to tell them apart. Pathways is the router for patient engagement - bookings, questionnaires and communications - and it now offers only those.

A trigger that has not been configured says so. An unconfigured trigger used to render an identical sentence and exception list to a configured one, which read as live routing when in fact nothing was in effect. It now tells you.

Say whose court the ball is in. A trigger can now record who is expected to act next, so an episode carries that with it.

A setting that leaves the episode unchanged says that too. Where an event already belongs to an episode it stays on that episode whatever the trigger says, and the editor now states this rather than implying the setting applies.