Features · Patient recalls
Follow-up that closes its own loop.
Set the rule once: who's due, how often, and what counts as done. Jump sends the reminders on schedule, fulfils the recall automatically when the patient attends, and puts anything that lapses in front of your team for a decision. Nothing dies silently in a spreadsheet.
ehr.usejump.co.uk · Recalls · worklist
Margot WhelanAnnual diabetes review · due 4 AugPending
Tomas AdeyemiBlood pressure check · due 11 AugScheduled
Priya NairMedication review · due 28 JulCompleted
Iris ChettyCervical screening · due 2 JulLapsed
Occurrence · M. Whelan
Annual diabetes review
due 4 Aug · window 7 Jul - 18 Aug
fulfils on: Diabetes review appt
repeats: every 12 months
fulfils on: Diabetes review appt
repeats: every 12 months
Trigger history
28 Jul · email · automatic
4 Aug · SMS · automatic
next: 11 Aug · max 3
4 Aug · SMS · automatic
next: 11 Aug · max 3
Enrolment
source: Diabetes register · bulk
status: active · audit-logged
status: active · audit-logged
80%
the NHS coverage target for cervical screening
68.7%
actual coverage in England in 2023, a decade low
1 in 3
eligible people not up to date with screening they are due
48%
of NHS Health Check invitations that result in a completed check
Source: NHS England cervical screening statistics (2023) · Public Health England NHS Health Check data
How it works
Set the rule. The loop runs itself.
Four steps, and only the first one needs a human every time. The rest is the system working through your patient list on schedule.
Step 1
Define the recall rule once
A rule is a recall type with a schedule: the interval, whether it repeats and for how many cycles, and the notification window either side of the due date. Then the reminder schedule - how many reminders, at what offsets, over email, SMS or both - and the fulfilment criteria: which appointment or consultation types count as done.
Recall rule · Annual diabetes reviewactive
Intervalevery 12 months · repeats
Notification window28 days before · 14 days after
Reminderswindow start · +7d · +21d · max 3
ChannelsEmailSMS
Fulfilled byDiabetes review appt · or consultation
Step 2
Enrol one patient, or a whole register
Add a recall from any patient's record, or work at population level: rule-based clinical registers keep themselves up to date, care gaps flag everyone overdue for expected care, and one action enrols the whole cohort. Workflows can update enrolments automatically from practice events. Every enrolment is audit-logged with where it came from.
Care gaps · Diabetes registerrefreshed daily
HbA1c overdue · last more than 12 months ago45 patients
Annual review overdue12 patients
Setup recall for 45 patients+
register membership · preview, then apply
Step 3
Reminders send themselves, on your schedule
When an occurrence enters its notification window, the trigger runner sends templated reminders over email and SMS at the offsets you set, up to your maximum. Every send is recorded: when, which channel, automatic or manual. Your team can also send one on demand from the worklist. The clinician sees a banner on the record whenever a recall is due or overdue.
Trigger history · M. Whelan2 of 3 sent
Email · "Your annual review is due"28 Jul · auto
SMS · "Reminder: review due 4 Aug"4 Aug · auto
Next reminder11 Aug · if unfulfilled
merge fields: patient name · practice · rule · due date
Step 4
Attendance closes the loop. Lapses demand a decision.
When the patient completes a matching appointment or consultation, the recall fulfils itself and the next cycle is scheduled - nobody ticks anything. Care done elsewhere can be marked complete manually. And if the window closes without fulfilment, the recall lapses into the worklist where your team must choose: reactivate, defer until a date with a reason, or cancel. Recalls cannot quietly disappear.
Fulfilmentautomatic
Diabetes review attendedoccurrence fulfilled
Next cycle generateddue Aug 2027
Lapsed · Cervical screening · I. Chetty
Window closed after 3 reminders. Decide: reactivate, defer with a reason, or cancel.
Reactivate+DeferCancel
What's included
From rule to closed loop.
What the recall system covers today. If something you need isn't here, ask us on a demo call.
- 01Recall rulesInterval, repeat cycles and notification window per recall type - annual reviews, monitoring, screening, anything you define.
- 02Reminder schedulesOffsets from the window start or due date, a maximum reminder count, and allowed channels set per rule.
- 03Automated email and SMSTemplated messages with merge fields, sent by the trigger runner on schedule - or manually from the worklist.
- 04Auto-fulfilmentA completed matching appointment or consultation fulfils the recall - no manual ticking.
- 05Repeat cyclesFulfilment generates the next occurrence automatically - a set number of cycles, or ongoing.
- 06Four enrolment routesFrom the patient record, bulk from a register, from a care gap, or via a workflow action.
- 07Recalls worklistPending, scheduled, completed and lapsed tabs - your daily action list for patient contact.
- 08The lapse safety netRecalls that run out of reminders land in the worklist for an explicit decision: reactivate, defer or cancel.
- 09Defer with a reasonPause a recall until a date - for a travelling patient, say - and it resumes automatically.
- 10Trigger historyEvery reminder recorded: when it went, on which channel, and whether a human or the system sent it.
- 11On the patient recordA Recalls tab with full history, and a banner when anything is due or overdue.
- 12Clinical registersRule-based cohorts with preview-then-apply membership, kept current automatically.
- 13Care gapsPatients overdue for expected care, flagged per register and refreshed daily, with one-action recall setup.
- 14Audit trail throughoutEvery enrolment change logged with who, when, why, and manual-vs-automatic provenance.
Connections
Recalls work because the rest of Jump feeds them.
Auto-fulfilment only works when the diary, the notes and the recall system are the same product. No integration to configure - it's one record.
Built in
Calendar & diary
A completed matching appointment fulfils the recall automatically.
Built in
Consultation notes
Recording a matching consultation type counts as fulfilment too.
Built in
Workflows
Workflow actions update recall enrolments from real practice events.
Live · templated
SMS & email
Templated recall reminders delivered on both channels, per your rules.
“We used to keep the recall list in a spreadsheet and hope. Now the annual reviews chase themselves, and the only names I see are the ones who genuinely need a phone call.”
Common questions
Questions, answered.
The five questions practices most often ask about running recalls on Jump. If yours isn't here, ask us on a demo call.
Any recall type your practice needs - annual health checks, chronic disease reviews, medication monitoring, screening, or anything you define. Each rule sets its own interval, whether it repeats, its notification window, its reminder schedule and channels, and which appointment or consultation types count as fulfilment.
Mostly by themselves. Each rule defines which appointment or consultation types satisfy it; when the patient completes a matching one, the occurrence is fulfilled automatically and, if the rule repeats, the next cycle is scheduled. Care that happened elsewhere can be marked complete manually, and that action is audit-logged like everything else.
Yes. Clinical registers hold rule-based patient cohorts, and care gaps flag everyone on a register who is overdue for expected care - last HbA1c more than 12 months ago, say. One action enrols the whole cohort in a recall. Workflows can also update enrolments automatically from practice events like a completed appointment or a received lab result.
Reminders stop at the maximum you set, and when the notification window closes the occurrence lapses. Lapsed recalls land in the worklist where your team makes an explicit decision: reactivate for another attempt, defer until a date with a recorded reason, or cancel. Nothing is allowed to disappear quietly - that's the point.
CQC expects systematic follow-up, and Jump gives you the documented system: who is enrolled and why, every reminder with its timestamp and channel, every status change with who made it and whether it was manual or automatic, and a worklist showing that lapsed recalls were seen and decided on. When an inspector asks how you make sure reviews happen, you show them the system, not a spreadsheet.
See a recall close its own loop.
We'll set up a recall rule and a register on a 30-minute call, then leave a sandbox populated with sample patients for your team to try.