Lapsed Patient Reactivation for Cardiology Practices

Lapsed patient reactivation is the workflow every cardiology practice knows it should run and almost none run consistently. The list exists. It is sitting in the order and tickler queue right now, full of patients whose device check was due in March and whose echo surveillance interval passed in February.

The reason it does not get worked is not that nobody has tried. It is that the first attempt teaches you the list is dirty, and cleaning it is a bigger job than calling it. Somewhere in those rows are patients who transferred to another cardiologist, patients who moved, and patients who have died. Calling those families is worse than not calling anyone, so the whole program stalls at the point where somebody would have to verify a few thousand rows by hand.

List hygiene comes before outreach, not after

The correct order of operations is counterintuitive and it is where most reactivation programs go wrong. You do not call the list and handle the bad rows as they surface. You screen the list first.

The screens are mostly mechanical. Has the patient had an encounter with the practice more recently than the tickler suggests, under a different provider. Is there a chart alert or a status that should suppress outreach. Has a records request gone out to another practice, which usually means they transferred. Does the demographic record show a returned address or a disconnected number. Each of those is a reason to route the row to a person rather than dial it.

The chart’s primary provider field deserves specific mention because it is the field most reactivation lists are built on and it is stale almost everywhere. A list assembled from it will include patients who have been seen four times this year by a colleague, and calling them to say they are overdue makes the practice look like it does not read its own records.

Screening first also makes the remaining list credible to the staff who have to work the exceptions. A queue that has already had the obvious problems removed gets worked. A queue where every third row is wrong gets abandoned in a week.

The recall reason decides the offer

Cardiology recall is not one category, and treating it as one produces outreach that sounds generic enough to ignore.

An overdue device check has a hard interval and a specific appointment type. Post-discharge follow-up after a hospital stay has a short window where it matters most. Echo or imaging surveillance has an interval attached to an order that is sitting open in the queue. A patient overdue for a lipid recheck is a different conversation than a patient overdue after a procedure.

Working from the order and tickler queue rather than from a generic last-seen date is what makes the outreach specific. The row already contains what was ordered and when it was due, so the call can reference the actual reason rather than a vague invitation to come back. Practices consistently find that specificity, not persistence, is what moves the booking rate.

The queue is also where the result has to land. An outreach program that books appointments but does not satisfy or close the tickler leaves the practice with a queue that keeps growing and no way to tell worked rows from unworked ones. Reading, updating, and closing the follow-up task is as much a part of the job as the call.

What the call says, and the line it does not cross

Reactivation outreach sits close to a boundary and the wording is where practices get it wrong.

The call says the practice’s records show a follow-up was due, names what was ordered, and offers appointment times. That is administrative. It is the same information a postcard would carry, delivered by phone at a time the patient can act on it.

What it does not do is give the patient a reason to worry or a reason not to. It does not explain why the follow-up matters clinically, does not characterize the risk of having missed it, and does not answer questions about the patient’s condition. Those calls come back frequently in cardiology, because a patient who is told they are overdue for a device check reasonably asks what happens if something was missed. The rule is a warm transfer to clinical staff with the chart and the overdue order attached, every time, with no attempt at reassurance first.

The practice also decides in advance which cohorts are not called by automation at all. Post-discharge follow-up within a short window after a cardiac admission is a common one to route to a nurse from the start. Which patients need a clinician on the line is decided by the practice’s clinicians, and encoded once.

Booking has to survive the payer rules

A reactivated patient is only recovered revenue if the appointment actually pays, and cardiology has more ways for that to fail than most specialties.

Coverage changes while a patient is lapsed. Someone who was overdue for eighteen months may have moved from a commercial plan to Medicare, changed employers, or lost coverage. Booking them with the same cardiologist under the assumption that nothing changed produces a visit that happens and a claim that does not. A real-time eligibility check as part of the outreach, rather than at check-in, is what catches it while there is still a conversation happening.

Credentialing is the second gate. It resolves per provider, per payer, per state, and per treatment type, and the provider the patient used to see may no longer take the plan the patient now has. The practical artifact for this is the inverse list, a per-provider record of plans that provider does not take, because the full enrollment grid is usually too messy for a practice to hand over.

For surveillance studies and procedures the authorization window matters too. A visit that needs prior authorization gets its earliest offer set out far enough for the auth team to submit, rather than booked into next week and then pushed. Reactivation outreach that ignores this produces a burst of bookings followed by a burst of reschedules, which costs more staff time than it recovered.

Why this is worth running as a campaign

Reactivation behaves differently from inbound work, and the difference is that nobody is waiting on the phone.

That means it can run in the gaps: outbound attempts spread across the week, retried on a defined schedule, at the times of day a given cohort actually answers. A patient who does not pick up on Tuesday morning is not a failed row, they are a row scheduled for Thursday evening. Human-worked recall lists almost never get a second and third attempt, because the person working them has a day job.

Care coordination in the sense that matters here is unglamorous. It is knowing which follow-ups are open, contacting the patient, getting the visit on the calendar, and closing the loop in the system so the practice can tell what happened. Handoff and follow-up tracking is the documented weak point in ambulatory care, not knowing who is overdue. An analysis of primary care referrals to specialists in a large health system found the documented rate of closing the referral loop was under 35%, and a recall queue fails the same way for the same reason: the contact happens, or it does not, and nothing records which.

The measurable version is straightforward: how many open ticklers existed at the start of the period, how many were contacted, how many booked, how many were suppressed by screening and why. A practice that can answer those four questions has a program. One that cannot has a list.

Key Takeaways

Screen the list before you dial it. Transfers, returned addresses, suppressing chart alerts, and recent encounters under another provider all get removed first, or the staff stop trusting the queue within a week.
Do not build the list from the chart’s primary provider field. It is stale almost everywhere and will put patients on the call list who have been seen four times this year.
Work from the order and tickler queue so the call can name what was actually ordered and when it was due. Specificity moves the booking rate; persistence mostly annoys people.
Close the tickler when the outcome is known. Outreach that books appointments but never satisfies the task leaves a queue nobody can tell worked rows from unworked ones.
Run eligibility during the outreach call, not at check-in. Coverage changes while a patient is lapsed, and the conversation is the last cheap moment to catch it.
Decide in advance which cohorts a person calls instead. Short-window post-discharge follow-up is the usual one, and your clinicians decide that once, in advance.

Every cardiology practice is sitting on a list of patients who were supposed to come back and did not. The barrier has never been knowing who they are. It has been that working the list properly means screening a few thousand rows, making several attempts each at hours the front desk does not work, and closing the loop in the system afterward, which is more hours than any practice has spare. That is the part worth automating, and the part where a patient asks a real question is the part worth keeping.

Sources