A repeatable dental recall and follow-up workflow

A dental recall process connects a clinician-approved interval, current patient context, eligible outreach and a recorded outcome. Message volume is not evidence that the clinical policy is appropriate, that every candidate was eligible or that continued care was completed. Each open candidate also needs a named owner and next review date.

Define which completed treatment, diagnosis, visit or review date can create a candidate and who has clinical authority to approve the interval. Avoid applying one identical interval to every patient without reviewing risk and current care. Record the basis in language the team can inspect. Software may calculate dates from recorded rules, but it should not silently replace practitioner judgement about an individual patient.

Decide the operating states: candidate, reviewed, excluded, ready to contact, contacted, booked, declined, unreachable and next review, adapted to the clinic’s process. Name who can change each state and which clinical questions require escalation. If a patient already has an appointment, transferred care or received later treatment, the candidate should be reviewed rather than contacted from an old date alone.

Open the patient record and verify identity, relevant clinical context, the due basis, later visits, treatment history, future appointments, contact preference, consent and suppression. This check prevents duplicate or inappropriate outreach. It also makes exclusions auditable: the clinic can distinguish an ineligible patient from an eligible patient who was not reached, rather than dropping both from the denominator.

For an eligible candidate, choose a configured channel and approved message that avoids unnecessary clinical detail. Assign an owner for replies, booking and failed attempts. A delivery-state update is not the recall outcome. The workflow closes only when the clinic records what happened—booked, declined, unreachable, excluded or reviewed again on a defined date.

Review the complete candidate set for a period. Count generated candidates, clinically reviewed candidates, exclusions by reason, eligible contacts, contact attempts, bookings, declines, unreachable patients and open cases. Investigate candidates with no owner or next date. Compare the same candidate population and account for exclusions and missing outcomes.

Sample edge cases: a patient seen at another location, a patient with a later appointment, a changed consent preference, an unreachable number and a clinician-adjusted interval. Confirm that the current record changes the action. Keep clinical policy review separate from software configuration review so a technically correct automation does not continue an outdated clinic rule.

Use one entry per candidate with a record reference, owner and review date. A clinician determines the recall basis when clinical judgment is needed. Staff check bookings and contact preferences before outreach. Keep exclusion reasons visible.

In Thirty2OS, an Action Engine candidate should retain the patient and treatment context that created it. Open the source before outreach, check for a later appointment and confirm the clinic’s rule. The user may complete, snooze or dismiss work according to the recorded outcome. The queue organises eligible signals; it does not guarantee clinical appropriateness, patient response or completed continued care.

During a trial, create a valid candidate, a patient with later care, a suppressed patient and a candidate requiring a clinician-adjusted interval. Review what each role can see and who owns communication. If WhatsApp is used, test template and provider eligibility separately. Keep the Action Engine state, communication attempt and actual appointment outcome distinct. Repeat the review from another clinic location where relevant, then export or record the candidate set so an owner can verify exclusions, open cases and next-review dates without relying on the queue alone. Review a small sample with the clinician who owns the policy and the team member who handles replies. Their agreement should cover the due basis, exceptions, escalation route and the date on which each unresolved candidate returns for review.

Review these with the people who book visits, record care and handle payments. Give any unresolved issue an owner and a next review date.