Vaccine Recall and Screening Reminders Without a Mail Merge

Vaccine recall in most pediatric practices is a project rather than a process. Somebody pulls a report, cleans it in a spreadsheet, runs a mail merge, and the practice gets a bump in visits for about three weeks. Then that person gets busy, and the next pull happens whenever the next person has a free afternoon.

The work is not hard, it is just relentless, and relentless work done by hand always loses to the phones. Meanwhile the list is decaying continuously. Children age into new recommendations every month, records arrive from other practices, and the gap between what the chart says and what the practice believes gets wider the longer it has been since the last pull.

The gap is real and it is not only about hesitancy

It is worth being precise about what the national picture actually shows, because the operational implication is different from the political one.

CDC reported that among kindergartners in the 2023-24 school year, coverage with required vaccines fell below 93%, ranging from 92.3% for DTaP to 92.7% for MMR, down from roughly 95% earlier in the decade. Exemptions rose to 3.3%.

Read those two numbers together and something useful appears. Exemptions moved by well under a point while coverage moved by more than two, which means a meaningful share of the children who are not up to date have no exemption on file at all. They are not refusals. They are appointments that never got made.

That is the population a recall program exists to reach, and it is the population a mail merge reaches worst, because these are the families who are hardest to get on the phone in the first place.

The practice sets the rules, the automation runs them

The scope line here is the same one that governs every care-gap program, and it needs stating before any of the mechanics.

The practice decides what counts as due. Those rules come from clinicians and from whatever schedule the practice follows, and they are configured once. The automation applies them to the record, produces the list, calls the family, offers times, books, and confirms.

What the automation does not do is decide what a particular child needs, weigh whether a gap matters, or talk a parent through a concern about a vaccine. A parent who raises a question gets that question captured and routed to clinical staff, with a call back from a person. Trying to satisfy that conversation in the automation is both out of scope and the fastest way to lose a family’s trust.

Inside athenaOne the two inputs are the immunization record on the chart and the patient’s appointment history. The first says what has been given and when. The second says whether anything is already on the books, which is what keeps the program from calling families who are already scheduled.

The complication: you are calling households, not patients

This is the detail that separates pediatric recall from every other recall program, and the one that mail merges get badly wrong.

A recall list is a list of children. A phone number belongs to a parent, and that parent frequently has two or three children on the same list. Run the list naively and one parent gets three calls in a day about three different children, each asking them to book separately. The predictable result is that they book one, feel harassed, and stop answering.

The fix is to group by household before dialing, and to make the call about the family. One conversation, all the children named, and where possible one visit slot per child booked back to back so the parent makes one trip. Practices that do this see the booking rate per contact rise sharply, for reasons that have nothing to do with the technology and everything to do with respecting a working parent’s afternoon.

The second complication is that being due for a vaccine and being due for a well visit are different clocks. A child can need a catch-up dose without being due for their next well-child appointment, and booking them into a full well-visit slot burns capacity the practice needs for the children who are due for one. Where the practice has a shorter nurse visit type for exactly this, the automation should be selecting it, and where the record is unclear about what is outstanding, the family goes to a staff queue rather than getting a call built on a guess.

The third is that records arrive from elsewhere. A child who transferred in may be fully up to date with the history sitting in an unreconciled document rather than in the immunization record. Calling that family produces an annoyed parent and a correction. Practices that run this well work the reconciliation backlog first and treat an outreach that produces a records correction as a success, because it is.

Timing the outreach against the calendar families actually use

Pediatric demand is seasonal in a way that most recall programs ignore, and working with the season rather than against it costs nothing.

The weeks before school starts are when parents are already thinking about forms, requirements, and appointments. Recall outreach that lands then converts better than the same call in February. The same window is when the practice is busiest, which is exactly why the outreach should not depend on staff having spare time.

The inverse is also useful. The quiet stretches are when the schedule has room for the catch-up visits, so the program can pull families forward into slots that would otherwise go unused. A recall list and an underfilled template are two halves of the same solution and they are rarely looked at together.

One practical guardrail: keep the outreach volume matched to the capacity the practice actually has that week. A recall campaign that books more visits than the schedule can hold produces reschedules, and a rescheduled catch-up visit has a high chance of never happening.

Measuring it as a program rather than a campaign

The difference between a recall campaign and a recall program is whether anyone can tell you the current number without doing work.

The number that matters is how many children on the panel are currently outstanding against the practice’s own rules. If producing it takes a person and an afternoon, the practice has a campaign. If it rebuilds nightly, the practice has a program, and every other measure becomes meaningful because the denominator is live.

From there, watch bookings per household contacted rather than per child called, because that is the metric the household-grouping change actually moves. Watch the share of outreach that resulted in a records correction instead of a visit, which tells you how much of the apparent gap is a data problem. And watch completion rather than booking, because in pediatrics the gap between those two is wider than administrators expect.

None of this needs new staff. It needs the list to stop being something a person builds and start being something the practice always has.

Key Takeaways

Group the recall list by household before dialing. One parent receiving three separate calls about three children is the fastest way to lose all three bookings.
Configure the due rules once with clinical input, then let the automation apply them. Questions from parents about a vaccine route to staff, never to the automation.
Check appointment history before calling so families who are already booked never get contacted, which is what destroys trust in a recall program.
Separate vaccine-due from well-visit-due and book the shorter visit type when that is what is actually needed. Otherwise catch-up doses consume well-visit capacity.
Work the unreconciled outside records first, and count an outreach that produces a records correction as a success rather than a failed booking.
Match outreach volume to the capacity available that week. Booking more catch-up visits than the schedule holds produces reschedules that often never happen.
Judge the program by whether the outstanding count rebuilds itself nightly. If producing it takes a person and an afternoon, it is a campaign and it will lapse.

Pediatric recall fails for organizational reasons rather than clinical ones. The rules are known, the families are reachable, and the visits are billable, and it still comes down to whether somebody has time to rebuild a spreadsheet this month. An AI team reading immunization records and appointment history inside athenaOne can hold that list continuously, call households instead of children, book the right visit type, and route every question a parent raises to the people who should be answering it.

Sources