Skip to main content

Practice Operations

Podiatry Recall Outreach That Books the Next Visit

Podiatry recall outreach dies when the phones get busy. How AI works the recall list, refreshes coverage, and books the visit inside athena.

6 min read

Podiatry recall outreach is the highest-yield work in the practice and the first thing that gets dropped. A large share of the panel is on a recurring interval set by the clinical team, the visits are short, the schedule has room for them, and the calls that would fill that room never get made because the phones are busy and the front desk is two people.

Small podiatry practices have a structural staffing problem that no amount of discipline solves. The same one or two people cover the phones, check patients in, and handle the desk during procedure blocks. When the doctor is in a procedure, the phones are effectively unstaffed, and the outreach list does not move at all.

The recall list itself is not the hard part. It already exists in athena as recurring intervals and open orders, and the clinical team already decided who belongs on it. The hard part is that somebody has to call a few dozen people a week, reach maybe half of them, and try again with the rest.

When that does not happen, patients drift past their interval. They come back eventually, often as a new patient with fresh paperwork, and the visit that should have happened on schedule happened late or somewhere else.

The list is already there, and the interval is already set

This is the part worth being precise about, because it defines the scope. The practice’s clinicians set the recall interval and decide who belongs on the list. That is a clinical determination and it stays entirely with them.

What the automation does is work the list they produced. It calls the patient, offers slots that are eligible for that visit type with that provider, books the appointment, and writes the outcome back onto the recall record so staff can see who has been reached and who has not.

The volume argument is straightforward. CDC data on diabetes prevalence explains why a podiatry panel carries so much recurring visit volume in the first place, and Medicare’s own coverage rules define which routine foot care visits are payable and under what circumstances. Both facts make the recall list predictable, which is exactly what makes it automatable.

Coverage changes between visits and nobody tells the practice

Practices put this to us almost word for word: patients do not know their insurance changed, so the chart just goes ineligible and the practice finds out at the worst moment. On a recurring-visit panel that happens constantly, because months pass between appointments and plan years turn over.

The recall call is the natural place to catch it, because you already have the patient on the phone about their next visit. The workflow we built for this texts the patient a link, has them photograph both sides of the card, reads the card, matches it against the plans configured in the EHR, uploads the image to the right place in the chart, and runs the eligibility check.

That matters because a couple of characters on a card decide whether the plan is one you are contracted with. Doing it during the recall call rather than at check-in turns a denial into a two-minute conversation. It is the same mechanic described in insurance card verification, applied earlier in the cycle.

A long gap can turn an established patient into a new one

Here is a rule that varies by practice and quietly breaks recall booking. How long a patient has to be away before they count as new again is a different number nearly everywhere. A podiatry group flagged the specific edge they live with: the Medicare new-patient rule is exactly three years, but their own paperwork requirements mean they need fresh forms after two.

That is not a technicality. New-patient visits are a different appointment type with a different duration, different documentation, and often a different lead time. Booking a lapsed patient into an established-patient slot produces a visit that runs over and paperwork that is not done.

So the recall workflow checks the gap against the practice’s own threshold, not a generic assumption, and books the correct appointment type. When the patient falls in the window where the billing rule and the paperwork rule disagree, it books the longer visit and flags it, because the recoverable error is a slot that ran short.

Paperwork finished before the patient arrives

New-patient onboarding is a data-completion problem rather than a form. Where a referral already loaded the demographics, the call should ask only for what is missing instead of walking the whole intake. Where nothing exists, the useful timing is a call the day before the appointment, so that most of the paperwork is already filled in when the patient walks in.

That framing changes what the outreach call is for. It is not just booking. It is arriving at the appointment with eligibility verified, forms complete, and the correct appointment type on the calendar.

For a practice where the front desk disappears during procedure blocks, that is the whole return. The patients who arrive during those blocks are the ones who get checked in slowly, and pre-completing the work removes the bottleneck rather than staffing around it. The same effect shows up in no-show reduction, because a confirmed patient with finished paperwork is a patient who turns up.

Where staff still own the call

Anything about the patient’s condition, whether the interval should change, or what should happen at the visit goes to the practice. The automation does not answer those questions and does not attempt to.

It calls, it books, it refreshes coverage, it finishes the paperwork, and it tells staff what happened. When a patient raises something clinical, the call transfers with the context already captured so the patient is not starting over. That split is what makes recall outreach safe to run continuously, and running it continuously is the only version that works. It depends on reading the recall record directly, which is the practical case for working inside athena.

Key Takeaways

  • Let clinicians own the recall interval and who is on the list. Automation works the list, it does not build it.
  • Refresh coverage during the recall call. On a recurring-visit panel the plan often changed since the last appointment and nobody told the practice.
  • Your own new-patient threshold is the number that matters, not a generic assumption. Medicare’s three-year rule and your paperwork rule are frequently different.
  • Book the longer appointment type when the two rules disagree. A short slot that runs over costs more than an over-booked one.
  • Call the day before to finish intake, so patients arrive with paperwork done rather than filling it in at the desk.
  • Run outreach through procedure blocks. That is exactly when the front desk cannot answer the phone and when the list stops moving.

A podiatry practice with a recurring-visit panel has next quarter’s schedule sitting in its recall list right now. The constraint is not knowing who to call, it is having somebody free to call them. Automating that outreach, with coverage refreshed and paperwork finished on the same call, turns a list nobody has time for into booked visits, using the recall records and appointment types already in athena.

Sources

Ready to See It in Action?

See how PGA works your athena recall list and books the visit before the gap opens

Schedule a Demo →

Written by Kevin Henrikson