Stop reminders when an appointment changes or is cancelled

What this means for your practice

Define which events stop or change reminders and verify that those events are handled reliably. Keep a visible exception route for information that has not synchronised.

A practical conversation with your supplier

Ask to cancel a fictional booking after message preparation but before dispatch. Then demonstrate a failed update between systems. Who sees that exception and can prevent an inappropriate reminder through the approved process? A cancellation tick in one system is not enough evidence that the messaging tool acted on it.

Plan the first improvement

Write a short list of the changes that should stop or alter a reminder. Cancellation is the obvious one, but your actual process may include rescheduling, a changed communication preference or a record awaiting review. The responsible team should approve that list and explain any differences between message types. Ask the supplier where each change originates and how a missed update becomes visible. Staff need a practical way to investigate an exception without assuming they should edit several systems independently.

Include a message already prepared but not yet sent in the test, because changing the diary early is the easier case. If a mistaken reminder does go out, preserve enough information to understand its cause and support an appropriate response through your normal process. Review whether the issue was a missing update, unclear stop rule or delay. Each points to a different improvement, and counting mistakes alone will not tell you which one is needed.

How to check the result

Count reminders sent after a change that should have stopped them, and record why the stop did not reach the message.