Nobody falls through the cracks.
Shown in the product as “Follow-up Recalls”Patients who should come back and have not been booked — a follow-up no slot fitted, a review the doctor named — land on one worklist: due first, then invited. Inviting is an explicit act through the consent-checked messaging engine; the booking is made in the diary, and a booking closes the recall. Cohort rules (annual reviews, screening due, vaccination gaps) arrive next. Advice to patients: the practice keeps its own lists of who a message is for — the codes or words it matches against each patient’s active problem list (J45, asthma) — and writes its own message with where the advice comes from; a prescriber approves the words before anything goes, and an edit sends them back to draft. A seasonal or festival message carries the days it may go and reaches a patient once; a bad-air-day message carries the AQI it goes at, with the threshold’s source, and goes only on a day whose AQI the desk recorded from the source it names at or above it — once a day per patient. Each send passes the consent check, and who was not reached is counted.
/recallsrecall.readWhat it does not do, by design. A listing with only benefits is an advertisement.
The design preview: every screen drawn with the product’s own blocks, on an example clinic’s demo data. Nothing here is a real patient.
Read out of the code, not the brochure: each app below is here because one service queries the other’s tables. Install either side and the hand-over is already wired.
Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.