case studyCycle Desk

How did one small clinic cut phone tag on dose changes after adding same day confirmations?

A two physician practice restructured how afternoon dose calls go out and how patients confirm receipt. What they changed, what broke first, and what they deliberately kept manual.

Two clinic staff conferring at a bright white nurses station in afternoon daylight
Two clinic staff conferring at a bright white nurses station in afternoon daylight.

The short answer is that they stopped treating the afternoon dose call as a conversation and started treating it as a delivery with a receipt. The order was changed so that the written dose instruction goes out first, the patient taps to confirm she has read it, and the phone call happens only for the patients whose confirmation has not landed by a set cutoff. The call volume did not disappear. It shrank to the patients who genuinely needed a voice.

This was a two physician practice running roughly forty stimulation patients at a time in season, with two nurse coordinators and one part time medical assistant covering the phones. Before the change, every monitoring patient got a call after labs resulted, whether her dose was unchanged or not. After the change, an unchanged dose became a push notification and a written confirmation, and the coordinators spent their calls on dose increases, cancellations, and the patients who had questions.

What follows is what they actually altered, in what order, what broke in the first two weeks, and the parts they refused to automate. The last section is the part worth stealing: the sequencing they would use if they started over.

The old afternoon call queue and where it stalled

The old rhythm will be familiar. Morning monitoring runs from about 6:45 to 8:30. Estradiol and progesterone go to the reference lab or the in house analyzer, ultrasound measurements get entered, and the physician reviews the list somewhere between eleven and two depending on the OR schedule. Orders land in a batch. Then the calls start.

The stall was never the calling. It was the not reaching. A coordinator dials, gets voicemail, leaves a HIPAA appropriate message that says almost nothing because it cannot say the dose over an unverified voicemail, and moves on. The patient calls back forty minutes later during a different coordinator's ultrasound coverage. That coordinator does not have the chart open. She takes a message. The first coordinator calls again.

Count the touches. One outbound, one voicemail, one inbound, one message, one outbound. Five touches to deliver one sentence that reads: continue 225 units Gonal-f and 75 units Menopur tonight, return Thursday. At an average of four minutes per touch including charting, that is twenty minutes of coordinator time for a patient with no change at all.

Run that against a panel. If twenty five patients are called each afternoon and eight of them turn into phone tag, the tag alone consumes about two and a half hours. Those are stated assumptions, not measured figures, but any coordinator can substitute her own touch count and get an answer she recognizes.

Keep reading: What actually happens on retrieval day from the coordinator side, hour by hour?

What the clinic changed in the notification sequence

The clinic inverted the order. Instead of call, then chart, then maybe send something written, they made the written instruction the primary channel and the call the exception handler.

The sequence now runs like this. The physician signs the plan. The coordinator releases the dose instruction to the patient's cycle calendar, which pushes a notification and updates tonight's medication entry with the exact drug, units, and time. The patient sees the change against the calendar she has been following since baseline, not as a free floating message she has to reconcile against a paper sheet.

Two details mattered more than the technology.

  • The release time became fixed. Instructions go out in one batch, targeted at 2:00 pm, not trickled from noon to four. Patients learned to expect it. A predictable delivery window kills a surprising amount of inbound calling, because the patient who has not heard by 2:15 knows that is unusual rather than normal.
  • The instruction carries the next monitoring date in the same message. The old workflow separated the dose from the return date, so a patient who understood her dose still called to ask when to come back. Merging them removed a whole category of callback.

The coordinators kept a working list of the day's patients sorted by whether the plan changed. Unchanged plans go out first because they are fast. Increases, decreases, coasting instructions, and cancellations get held for a second pass with more care.

Requiring an explicit patient confirmation and its fallback

Sending is not delivering. The change that made the difference was requiring the patient to tap a confirmation on the instruction, which writes a timestamp back to the clinic side.

The coordinator's screen then shows three states: not yet opened, opened but not confirmed, and confirmed. That is a triage list. At 4:00 pm the coordinator works only the unconfirmed rows.

The fallback ladder they settled on:

  1. 4:00 pm. Any patient unconfirmed gets one phone call. Live answer resolves it, and the coordinator marks the confirmation manually with a note that it was verbal.
  2. 4:30 pm. Still unconfirmed after one call gets a second attempt to the alternate number in the chart, usually a work line or a partner.
  3. 5:00 pm. Still unconfirmed goes on the handoff list to the on call physician with the plan attached, so the answering service call is a thirty second read rather than a chart hunt.

Trigger night is carved out of this entirely. A trigger instruction is never considered delivered on a tap. It is called, read aloud, and read back by the patient, every time, and the confirmation tap is treated as supporting documentation rather than proof.

The first thing that broke was confirmation fatigue. In the first week they asked patients to confirm every daily calendar entry, not just changes. Patients stopped reading and started tapping. They cut it back to confirmations on new or changed instructions only, and attention recovered.

Keep reading: Where is fertility coverage and clinic demand heading over the next few years in the US?

Which calls stayed on the phone by design

The practice wrote a short rule and posted it at the nurses station. A call is required, not optional, for any of the following.

SituationWhy the phone stays
Trigger timingSingle point of failure. A misread hour costs the cycle.
Cycle cancellation for poor responseThe patient needs to hear a person, and the next step conversation happens immediately.
Suspected OHSS risk requiring coasting or a freeze all decisionSymptom questions have to be asked live.
Any dose increase above the patient's prior maximumHigher chance of an ordering or pharmacy supply problem.
A new medication the patient has never mixedMixing instructions need a back and forth.
Negative beta resultNever a notification. Never.

Everything not on the list defaults to written first. The value of writing it down was that new staff stopped having to guess, and the coordinators stopped relitigating the same judgment call every afternoon.

How the team handled patients without smartphones

Roughly one patient in a panel of forty either had no smartphone, had a phone she could not reliably use, or had a data plan she rationed. The clinic did not build a special workflow. They built an explicit flag.

At the baseline visit, the coordinator asks a direct question: how do you want to receive daily instructions, and what happens if we cannot reach you at that number. The answer sets a preference on the chart. Patients flagged as call preferred are simply excluded from the confirmation triage and appear at the top of a call list every afternoon, unchanged from the old workflow.

Two smaller accommodations proved useful. A partner or a designated support person could be added as a second recipient with the patient's written authorization, which solved the night shift worker who could not check anything before nine. And any instruction could be printed at checkout for the current week, so a patient who preferred paper left the building with a schedule in hand and used the notification only as a nudge.

See how FertilityWindow handles this for fertility clinic patient coordination

Effects on staff end of day and on documentation

The most visible effect was the shape of the afternoon. Calls no longer spread across four hours. They compressed into the 4:00 to 5:00 window and, crucially, became a finite list rather than an open queue. A coordinator could see how many were left.

Documentation improved for a boring reason: the timestamp exists whether or not anyone remembers to chart it. The old record was a coordinator's note saying she spoke with the patient. The new record shows when the instruction was released, when it was opened, when it was confirmed, and if a call was needed, who made it and when. In a records request, that sequence answers questions the note never could.

One unglamorous benefit. The end of day handoff to the answering service went from a verbal summary to a short list of unconfirmed patients with their plans attached. On call physicians noticed within a month.

What did not improve: total instruction preparation time. The physician still reviews the same charts and the coordinator still reads every plan before release. The savings sat entirely in the delivery layer.

What they would sequence differently now

Three things, in their own words, more or less.

Fix the release time before doing anything else. Batching instructions to a predictable window produced a share of the benefit on its own, with no confirmation mechanism at all. It is free and it can be done next Monday.

Write the call required list before turning on notifications, not after. They turned on the technology first and spent two weeks arguing case by case about what still deserved a call. Writing the rule first would have prevented a near miss where a coasting instruction went out written only.

Set patient expectations at consult, not at baseline. Patients who learned at their consultation how afternoon instructions would arrive confirmed faster and called less than patients who learned it on stimulation day one, when they are absorbing injection training and everything else at once.

Where to start

If your afternoon looks like the queue described at the top, the first move is not buying anything. It is counting your touches for one week and finding out how many of your calls delivered no change at all.

When you are ready to put the written instruction first, FertilityWindow gives each patient a cycle calendar with her medication schedule and monitoring dates on it, pushes dose changes to that calendar, and sends her confirmation back to your desk so your four o'clock list is short and specific. The phone stays exactly where you decide it belongs.

Portrait photograph of Jimenez Julien, founder of MLJ

Jimenez Julien

Jimenez Julien builds coordination software for small clinical teams and spends his weeks with fertility nurse coordinators watching how a protocol turns into a patient's week. He writes Cycle Desk to put the cycle logistics, monitoring flow and coverage questions that fill a coordinator's afternoon into plain, checkable form.

More about the author and how FertilityWindow is built