Practice operations

The patient who should have come back and did not

Most practices know roughly who is due back. Very few can produce the list on demand, and almost none know what proportion of it was contacted. That gap is not an administrative detail: a patient who needed a six-month follow-up and never heard from anyone is a clinical outcome as well as a commercial one.

A recall and a reminder are different things

A reminder tells somebody about an appointment that already exists. A recall tells somebody they need an appointment that does not exist yet, and it has to carry a reason - what was found, what interval the clinician set, what happens if it slips. Practices that treat recalls as reminders send messages that read as marketing, and patients file them accordingly.

The list is only as good as what was written down

A recall list is built from what the clinician recorded at the end of the last appointment: the interval and the reason. If that was noted in free text, or not at all, no system can assemble the list later. Before buying anything that promises recall automation, check whether the interval exists as a field rather than as a sentence - because that is the difference between a list and an archaeology project.

What software may say, and what it must not

It can tell a patient their practice recommends a review and that the interval has passed, and it can take the request to book. It must not say why in clinical terms, restate a finding, or imply urgency that no clinician assigned - a recall message that frightens somebody is worse than one that was never sent. The clinical content of a recall belongs to the person who set it.

Measure contacted and returned, not messages sent

Messages sent is a number any system can make look good. The pair that matters is what proportion of the due list was contacted at all, and what proportion of those returned - split by interval length, because a six-week recall and a two-year recall behave nothing alike. Practices usually discover the shortfall is in contact rather than in response.

Frequently asked questions

What is a patient recall?
A request to a patient to book an appointment that does not exist yet, because a clinician set an interval for review. It differs from a reminder, which concerns an appointment already in the diary, and the difference matters: a recall needs a reason attached or it reads as advertising.
Can recalls be automated?
The contacting can be, if the interval and reason exist as structured data from the previous appointment. The clinical judgement that set the interval cannot, and neither can deciding that a particular patient needs chasing rather than a standard message. Check your records for the field before scoping the automation.
Should a recall message say what was found?
No. It can say the practice recommends a review and the interval has passed, and leave the clinical content to the appointment. A message that restates a finding is both a privacy question - who else sees that screen - and a clinical one, because a patient reading it alone has nobody to ask.
What do we measure to know whether this is working?
Two proportions: how much of the due list was contacted, and how much of the contacted list returned, both split by interval length. Messages sent tells you about the software. If the due list cannot be produced at all, that is the finding and the first thing to fix.
Which languages can a patient reply in?
Hebrew with full right-to-left layout, English and Russian, detected from what the patient writes. For recalls this matters more than for most messages: a patient who cannot easily reply in their own language does not reply, and silence here looks identical to refusal.

Get in touch

Leave your details and we will reply. You do not need a sales call to get an answer.