Features · Task management
Every follow-up, followed up.
Tasks linked to the patient, assigned to a person or a team, due-dated and flagged routine or urgent. Raise them by hand from the record, or let a workflow raise them the moment work appears. Completing one writes its own audit trail.
ehr.usejump.co.uk · Task 0482 · Margot Whelan · pat_M2vXn7q9
Chase dermatology referralUrgent
task 0482 · due Fri 31 Jul · category: referrals
Subtasks · 2 of 3
✓Referral letter sent
✓Clinic called for acknowledgement
Confirm appointment date with patient
Activity
22 Jul 14:31 · created by Dr S. Mitchell
22 Jul 14:31 · assigned to Reception team
23 Jul 09:12 · comment · "No response yet, chasing Thursday"
22 Jul 14:31 · assigned to Reception team
23 Jul 09:12 · comment · "No response yet, chasing Thursday"
My queue
Today4
Overdue2
This week11
Saved views
Referrals to chase
Results to file · Reception team
1 in 15
lab results lack follow-up, even at the low end of published studies
2-3
safety incidents per 100 primary care consultations; missed and delayed diagnoses among the most harmful
25%
of GP time goes on administrative work around clinical care
2,700+
tasks raised through Jump since January
Sources: Callen et al., J Gen Intern Med (2011) · Panesar et al., BMJ Qual Saf (2016, WHO-commissioned) · RCGP GP Voice Survey (2025) · Jump platform data, July 2026
How it works
What happens between "I'll sort that" and sorted.
Four steps. A task is born where the work appears, finds the right person or team, gets worked in a queue that suits how you work, and closes with a record of what was done.
Step 1
Raise it where the work appears
Create a task from the patient record and it arrives already linked to the patient. Give it a due date, flag it routine or urgent, pick a category, and assign it to a colleague or a whole team. Bigger jobs break into subtasks so progress is visible. Admin work with no patient attached? Tasks work for that too.
New taskfrom patient record
Chase dermatology referralUrgent
PatientMargot Whelan
AssignedReception team
Due31 Jul
Create task+Add subtasks
Step 2
Or let a workflow raise it for you
Build a workflow once and the task raises itself every time after: created, updated or closed by the workflow, assigned to a person or a team, with patient details merged in. Jump ships with sensible defaults - a task when an invoice is paid, a report task when a consultation is finalised, review tasks when documents arrive for filing.
Workflow · New registrationsactive
TriggerAppointment booked · new patient
Create taskReception team
"Check registration forms for {patient.first_name}" · due +2 days
Step 3
Work the queue, your way
Your list shows what's yours and your teams', with today, this week and overdue in plain sight. Filter by patient, assignee, category, urgency or status, save the views you use daily, and clear repetitive work with bulk actions. Questions live as comments on the task, not in a side channel.
Practice tasksview: Referrals to chase
Chase dermatology referral · M. WhelanUrgent
Confirm cardiology appointment · T. Oseidue 29 Jul
Send GP letter after discharge · J. Barnesdue 30 Jul
3 selectedReassign+Set due dateClose
Step 4
Close it with a trail
Every task has a number and a history: who raised it, who it moved to, what was said, when it closed - completion is logged at the database level, not as a courtesy. When you need the practice-wide picture, the tasks report filters by status, urgency, category, assignee or patient, and exports to CSV.
Task 0482 · closedfull history
22 Jul 14:31 · created by Dr S. Mitchell
22 Jul 14:31 · assigned to Reception team
23 Jul 09:12 · comment · "No response yet, chasing Thursday"
24 Jul 11:05 · subtask completed · appointment date confirmed
24 Jul 11:06 · completed by A. Reid
22 Jul 14:31 · assigned to Reception team
23 Jul 09:12 · comment · "No response yet, chasing Thursday"
24 Jul 11:05 · subtask completed · appointment date confirmed
24 Jul 11:06 · completed by A. Reid
What's included
From "someone should" to someone did.
What task management covers today. If something you need isn't here, ask us on a demo call.
- 01Patient-linked tasksRaised from the record, visible on the record, linked back from the task.
- 02Assign to a person or a teamOrg-managed teams; your queue includes what's assigned to your teams.
- 03Routine / urgent flagOne honest distinction, so urgent actually means something.
- 04Due dates & overdue viewDeadlines on every task; overdue surfaces in lists, filters and buckets.
- 05CategoriesReferrals, results, admin - organise by the kind of work it is.
- 06SubtasksBreak big jobs into steps; progress stays visible on the parent.
- 07Comments on tasksContext and questions live with the task, not in a side channel.
- 08Saved views & bucketsEach person's queue, organised the way they actually work.
- 09Bulk actionsReassign, re-date or close many tasks at once.
- 10Workflow-created tasksWorkflows create, update and close tasks, with patient details merged in.
- 11Sensible defaults includedInvoice paid, consultation finalised, documents to file - tasks appear ready-made.
- 12Task numbers & activity historyEvery task citable, every change and completion logged.
- 13Practice-wide reportFilter by status, urgency, category, assignee or patient; export to CSV.
- 14Tasks from Semble, importedSwitching? Open tasks come across in the structured import.
“I used to keep a paper list of things to chase, and the list lived or died with me. Now the list keeps itself, and it doesn't care who's on holiday.”
Common questions
Questions, answered.
The five questions practices most often ask about running their workload in Jump. If yours isn't here, ask us on a demo call.
Yes. Create a task from a patient record and it's linked automatically - it shows on the record, and the task links straight back to the patient. Tasks without a patient work too: reordering supplies, updating a protocol, anything the practice needs to track.
Yes. Teams are managed at practice level - reception, nursing, admin, whatever shape your practice takes - and any task can be assigned to a team instead of an individual. Everyone's queue includes work assigned to their teams, so cover during holidays and sick days is built in rather than improvised. Workflows can assign to teams too.
Yes, through workflows. Build one once - on a trigger like an appointment being booked, create a task with a title, assignee (person or team), due date and patient details merged in - and it runs every time after. Workflows can update and close tasks as well as create them. Jump also ships with sensible defaults, like a review task when documents arrive for filing.
It stays loudly visible. Overdue tasks surface in your queue's buckets, in filters, and in the practice-wide report, so they can't quietly age out of sight. Anyone with access can see what's overdue, who owns it, and how long it's been waiting - which tends to be all the escalation a small team needs.
Yes. Every task has a reference number and a full activity history: creation, assignment changes, comments, subtask progress and completion, each with who and when - completion is logged at the database level. The practice-wide report filters by status, urgency, category, assignee or patient and exports to CSV when you need the evidence in a document.
See a follow-up run itself.
We'll set up a workflow that raises a task, route it to a team, and close it with a full trail on a 30-minute call - then leave a sandbox for your team to try.