“Our patients don’t leave. They’d tell us.” Every owner has said a version of it, and meant it. Some do. A patient who cancels creates a record. A patient who does not show creates a record. A patient who simply stops coming creates nothing at all.
There is no event. Nobody called, nothing was canceled, and the appointment that should have been booked in six weeks was never booked. So there is no row anywhere describing what did not happen. That is why patients quietly stopping is the largest lost-revenue category in most practices, and the one nobody has a number for.
This sits at the very front of the path from a visit to money in the bank. It comes before there is a charge, the visit written up as a billable line, or a claim, the bill sent to the insurance company. A visit has to be booked before anything can be billed.
Every step after that leaves a record, which is why the later steps get watched and this one does not. Lapse detection is one of the five checks that watch the money path, and it is the only one aimed at a visit that never happened.
What is lapse detection in a medical practice?
Comparing the date each patient was expected to return against whether an appointment exists, and listing the ones who passed the date with nothing booked. It turns a silent absence into a name to call this week.
At practices we have worked with, a large share of follow-up patients never came back, and not one had canceled. Nothing recorded it, because nothing happened. The check is a date against a booking.
Why nothing catches it
Every alert in a billing or scheduling system is triggered by something happening. A cancellation fires because somebody canceled. A denial, the insurance company’s refusal to pay a claim with a reason code, fires because the insurer’s answer arrived. Even a no-show fires, because the appointment existed and its status changed.
A lapse has no trigger. The absence of a future booking is a condition, not an event, and conditions are only visible to something that checks for them on purpose. So the practice finds out months later, when somebody notices volume is soft, or when a provider mentions they have not seen someone in a while. By then the patient has found care somewhere else or stopped seeking it.
The date already exists
This is what makes the check cheap instead of hard. Most care runs on a rhythm: weekly, every two weeks, monthly, quarterly. That rhythm is written down in the treatment plan, the appointment type, or a clinical note. Which means the expected return date can be worked out from data the practice already holds.
Nothing new has to be collected from anyone. Where the plan says every two weeks, the date is fourteen days after the last completed visit, and the question is whether a booking exists on or near it.
How the check works
Three parts, and none of them needs judgment. First, an expected return date on every active patient, worked out from the treatment rhythm instead of typed in by hand. Second, a comparison against booked appointments: does a future appointment exist for this patient now, not did they have one once.
Third, a tolerance. A patient a few days past the expected date is normal life. Two weeks past for a weekly rhythm is a signal. The window has to differ by rhythm, because a month late matters enormously for weekly therapy and not at all for a quarterly review.
What comes out is a list of names, each with a last visit date, an expected return date, and how far past it they are.
Why the list has to be short and current
This is the same principle behind every other check on the money path, and the reason most attempts at this fail. A list of everybody who has ever lapsed is a database, and nobody works a database. It reads as a project, it needs a block of time nobody has, and it gets deferred.
A list of who crossed the line this week is a task: ten or fifteen names, workable in an hour, and the same hour next week.
There is also a recovery argument. A patient two weeks past their expected return is reachable and probably just busy. A patient six months past has made other arrangements, and that call is a different and far less successful conversation. Early is most of the value here.
What the list tells you beyond the names
Run it for a few months and it starts telling you why. Lapses concentrate by provider, rarely evenly and rarely for the reasons anyone would guess. Usually it traces to whether follow-ups get booked before the patient leaves, not to anything clinical, and the per-provider view is what makes that visible.
They concentrate by visit number: the gap after a first appointment behaves differently from the gap after a twelfth, and knowing where you lose people tells you where to put the effort.
And they concentrate in time. A spike in lapses traces to something with a date: a scheduling change, a staffing gap, a provider leaving, a week when nobody was rebooking at checkout. None of that is visible in a total. All of it is visible in a weekly list with names and dates.
Real situations, and what the schedule said at the time
At practices we have worked with, the lapses are not spread across the clinicians. Lapses cluster under the providers whose sessions end without a next date on the calendar, and the fix is a habit at checkout. The fix was a habit at checkout, not a conversation about outcomes.
At another, lapses spiked for three weeks and then settled. Lapse spikes tend to line up with a stretch when nobody covered the rebooking step at checkout. No report showed the gap. A weekly list with names did.
The prevention that follows
Detection finds the ones who lapsed. It does not stop the next ones, and the thing that does sits before everything above. Book the next appointment before the patient leaves the building or ends the call. A patient with a date in hand never enters the lapse list at all.
That makes lapse detection the safety net instead of the answer. It is necessary, because rebooking will never be perfect, and it is no substitute for the rebooking itself.
What this means for you
Pick one rhythm, the most common in your practice, and run the check for a single month. Count how many patients passed their expected return date with nothing booked. Multiply that by your average revenue per visit and by the visits a typical course of care contains.
The figure is usually larger than anybody expects, because nothing has ever shown it as a figure. Then look at which providers the names cluster under, because that is where the checkout habit needs to change.
Grab 30 minutes with us. Prep nothing. You will see who stopped coming and roughly what it cost.
Questions people ask
What is lapse detection?
Comparing the date a patient was expected to return against whether an appointment exists, and listing the ones who passed the date with nothing booked. It turns a silent absence into a name somebody can act on this week, while the patient is still reachable.
Why does patient attrition not show up in reports?
Because it produces no event. A cancellation and a no-show both create records. A patient who simply stops coming creates nothing, and reports total up records. There is nothing to total, so the largest lost-revenue category in most practices has no line on any report.
Where does the expected return date come from?
From how often the patient is meant to be seen, which is usually already written in the treatment plan or implied by the appointment type. Weekly means seven days after the last completed visit. Nothing new has to be collected from anyone.
How far past the date should trigger a follow-up?
It depends on the rhythm. Two weeks past matters enormously for weekly therapy and not at all for a quarterly review. Set the tolerance per rhythm instead of using one number for everybody, or the list fills with noise and stops being read.
Does lapse detection replace rebooking at checkout?
No. Booking the next appointment before the patient leaves prevents the lapse entirely. Detection is the safety net for the ones that slip through, and rebooking will never be perfect, so a practice needs both.