Recurring OMT Visits and the Standing Appointment

Recurring OMT visits are the reason an osteopathic manipulation practice runs on a different kind of schedule than most specialties. The work is delivered in repeat visits at a cadence, patients attach to one physician and stay attached, and the calendar fills with standing appointments that nobody owns once they are set.

A standing appointment is convenient right up until something moves, and something always moves.

The patient books every Tuesday at four. That arrangement lives in the schedule as a row of individual appointments, and nothing in the schedule knows they belong together. Cancel one and the rest sit there. Change the cadence and someone edits eight entries by hand.

Meanwhile the grid hardens. Standing appointments occupy the same slots week after week, which is exactly what makes them valuable and exactly what makes the schedule inflexible. The practice ends up with a calendar that looks full and a capacity picture nobody can explain.

The third problem is the quiet one. Patients on a recurring cadence stop by drifting rather than by declining. They miss one, they mean to rebook, and six weeks later they are gone with nothing in the system flagging it, because they never cancelled anything.

Write down the cadence, because it is a booking rule

Osteopathic manipulative treatment is a manual approach that osteopathic physicians use for somatic dysfunction of the musculoskeletal system, and it is delivered in repeat sessions rather than in a single encounter. That delivery pattern is the operational fact the schedule has to encode.

What the schedule needs is not the clinical reasoning behind the cadence, which belongs entirely to the physician. It needs the output: how often, for how long, with whom, and until when. Weekly for six weeks with the same physician, then reassess. Or every other week with no fixed end date. Those are booking rules, and they can be captured at the point the physician sets them.

Without that capture, the cadence lives in the visit note and the schedule finds out about it when the patient calls. Which means the front desk is reconstructing an arrangement rather than executing one, every single time.

The capture step is small. A defined appointment type for the recurring visit, and a field or task carrying the cadence and the review point. Once it exists, everything downstream in this article becomes possible, and until it exists none of it does.

The review point matters as much as the cadence. A standing appointment with no end date and no scheduled reassessment will run until the patient stops coming, which is the wrong way for it to end.

Book the run, and decide in advance what a cancellation does to it

Booking the whole series is the easy half. Keeping it intact through the first disruption is where practices lose the arrangement.

The patient cancels week three. Does week four move out, keeping the interval, or does it stay where it is and the patient simply misses one? Both answers are defensible and they produce completely different schedules. What is not defensible is deciding it differently depending on who takes the call.

There is a mechanical trap underneath the policy one. Changing the duration of a slot in a template requires freeing up the neighbouring slots to make room, so a schedule packed with standing appointments resists adjustment. What looks like moving one visit turns into three edits, and the person doing it under time pressure often just books the patient somewhere convenient instead, which breaks the interval nobody wrote down.

Automation handles the mechanical part cleanly once the rule exists. It knows the remaining appointments, the cadence and the physician constraint, and it can offer a cascaded set of new times in a single pass rather than a sequence of callbacks.

What it should not do is decide that a patient who has missed three in a row should come off the standing arrangement. That is a conversation between the practice and the patient, and often with the physician, and the workflow should surface it rather than settle it.

The follow-up grid will crowd out the new patient

This is the capacity failure specific to practices that run on recurring visits, and it is invisible in a utilization report that only counts fill rate.

A physician may cap new patients at a handful a day, or at one, while a large follow-up queue sits behind them. The schedule gets carved into short follow-up slots to serve that queue, and then a new patient who is ready to book today cannot be absorbed, because a thirty minute follow-up hole cannot hold a new patient visit.

The practice reads as full. It is full of the wrong thing, and the new patient goes somewhere else.

The structural fix is protected capacity rather than a bigger grid. New patient slots that the booking rules will not release to follow-ups, with a defined cutoff at which an unfilled new patient slot converts back to general availability rather than sitting empty. Both halves are required. Protection without a release rule turns into waste, and practices notice the waste and remove the protection.

Automation is well placed to run the conversion because it is a time-of-day rule rather than a judgment. Hold the slot, convert it at the cutoff, and tell nobody, because it should be invisible when it works.

Reminders assume one appointment, and a series is not one appointment

Native reminder behavior in an electronic health record commonly fires against the chronologically first appointment, which is fine for a practice booking one visit at a time and wrong for this one.

A patient on a standing cadence needs a different message. Which visit this is, how many remain before the review point, and confirmation that the rest of the run is still where they left it. That is two lines and it prevents most of the drift, because the drift starts with a patient who has lost track.

Sending it from the practice rather than relying on native behavior is the only way to control the content, and practices that do this usually turn the native reminders off for the recurring appointment type so patients are not receiving two messages that disagree.

The same channel handles the confirmation loop. A patient who confirms is a slot the practice can rely on. A patient who does not respond to two attempts on a standing appointment is the earliest available signal that the arrangement is failing, and it arrives days before the no-show does.

Content stays administrative throughout. Dates, counts, location and what to bring. How the course is going is a conversation for the treatment room.

The drifted patient and the departing physician

Two outbound campaigns matter more in this practice type than anywhere else, and both are lists the schedule can produce on its own.

The first is the patient who stopped. On a recurring cadence, absence is measurable in a way it never is for annual visits. A patient whose interval is weekly and whose last visit was five weeks ago has dropped out, and the system knows it without anyone noticing. That list, sorted by how far past cadence each patient is, is the highest yield outreach in the building, because these are people who already committed to a schedule.

The second is the physician departure, which is uniquely damaging here. Patients are attached to one physician and the standing appointments encode that attachment, so a departure does not release a panel gradually, it releases it all at once with dozens of booked future appointments that now have no provider behind them.

Handled reactively, that becomes a week of calls and a lot of patients who simply do not rebook. Handled deliberately, it is a rescheduling campaign run against a known list before the departure date, with the conversation scripted and the alternative physicians named rather than offered as an open question.

That scripting detail matters. A caller asking for a specific physician by name needs language that redirects to the physicians who do have availability without sounding like a brush-off, and writing that language in advance is the difference between retaining a panel and losing one. Administrative work like this is a recognized drag on practices, and it is worth automating precisely because the alternative is a week nobody has.

Key Takeaways

Capture the cadence, duration, physician and review point as a booking rule at the moment the physician sets it.
Give every standing arrangement an explicit review point, since one with no end date runs until the patient stops coming.
Decide once whether a cancellation moves the rest of the run or leaves it, and apply that rule across every scheduler.
Expect a slot duration change in a dense follow-up grid to require freeing neighbouring slots, so a cascade is never one edit.
Protect new patient capacity with slots the booking rules will not release, and convert unfilled ones back at a defined cutoff.
Replace native reminders for recurring appointment types, because they commonly fire against the first appointment only.
Treat two unanswered confirmations on a standing appointment as the earliest warning that the arrangement is failing.
Build the past-cadence list and the departing-physician panel as standing outreach campaigns, with redirect language written in advance.

A standing appointment is the most valuable and least managed object on an osteopathic practice’s schedule. Capture the cadence as a rule, decide the cascade before you need it, protect the capacity the follow-up grid would otherwise eat, and work the two lists the schedule can already produce. The patients who drift off are the ones who wanted to keep coming.

Sources