Refills are the tax you pay for having a compounding program. Every GLP-1 patient, every LDN protocol, every hormone regimen: they all come back around, and each cycle demands attention that is mostly clerical and occasionally clinical. If your staff is opening every request, hunting for the last visit note, checking the pharmacy queue, and messaging the patient about payment, you are burning your best people on work a well-designed workflow should have already finished.

The goal is not to remove human judgment from refills. The goal is to make sure that by the time a human touches a request, the only thing left to do is the judgment part.

What "before staff touches it" actually means

In most practices I have looked at, a refill request lands in an inbox (portal message, fax, phone note, pharmacy request) and sits there until a medical assistant picks it up. The MA then does eight to fifteen minutes of pattern-matching work: is this patient current on labs, are they within the prescribing window, did they complete their last check-in form, have they paid for the next cycle, does the pharmacy have stock, does the provider need to sign off.

Almost none of that is judgment. It is retrieval and rule application. The right question to ask about your workflow is: what percentage of refill requests should reach a human already sorted into "auto-approve queue," "needs provider eyes," or "patient action required"? In practices with mature automation, that number is above 80%. If you are under 30%, your team is doing work the system should be doing.

The pre-touch checklist your workflow should complete on its own

Before any staff member opens a refill task, the workflow should have already answered these questions and attached the answers to the record.

  • Is the patient active and in good standing? Membership status, outstanding balance, signed consents on file, and any provider-set holds.
  • Is the prescription still within its authorized window? Refills remaining, days since last dispense, and total duration since the originating visit.
  • Are the required clinical checkpoints current? Labs within the interval your protocol specifies, most recent weight or vitals if the protocol requires them, completed check-in questionnaire for the current cycle.
  • Does the pharmacy have the formulation in stock, and at what lead time? If you work with multiple 503A or 503B partners, which one is routing this order and why.
  • Has payment been collected or authorized? Card on file charged, subscription cycle current, or invoice sent and acknowledged.
  • Is there anything in the chart that should stop this refill? New allergy, adverse event report, provider note flagging a taper, or a scheduled follow-up that has not happened yet.

Every one of those items is a rule. Rules belong in software. When they live in a staff member's head, you get variance, drift, and the specific kind of burnout that comes from doing the same mental checklist 60 times a day.

Three lanes, not one queue

Once the checklist runs, the workflow should sort each request into one of three lanes. This is where most practices leave money and hours on the table, because they treat every refill as a single undifferentiated task.

Lane 1: Clean refills

Patient is current, protocol is met, payment is captured, pharmacy is ready. The provider gets a batched review at set times of day (say, 10am and 3pm) with a one-click sign. In a compounding practice running GLP-1s or hormones at scale, this can be 60 to 75% of your volume. The provider is spending seconds per patient, not minutes.

Lane 2: Patient action required

Something is missing on the patient side: overdue labs, unpaid invoice, missing check-in form, expired card, unsigned updated consent. The workflow should message the patient automatically with the specific thing they need to do and a link to do it. It should follow up on a schedule you set. It should reopen the refill for review the moment the patient completes the action. Staff should only see these when the automated sequence has failed after a defined number of attempts.

Lane 3: Clinical review required

Something in the chart genuinely needs a clinician: reported side effect, lab out of range, protocol-defined dose adjustment window, patient message with a clinical question attached to the request. These go to the provider or the clinical lead with the relevant context already surfaced (last note, current dose, the specific trigger). This is where you want your clinical time going.

Where AI agents earn their keep

Rules engines handle the deterministic pieces. AI agents handle the messy inputs. In a refill workflow, that means:

  • Reading inbound faxes and pharmacy messages and extracting patient, medication, and quantity so the request lands on the right chart without a human keying it in.
  • Parsing patient portal messages that say "I need more of my shot" and mapping them to the right active prescription, then kicking off the checklist.
  • Drafting the patient outreach message when Lane 2 fires, using the patient's name, the specific missing item, and the correct link, in your practice's voice.
  • Summarizing the clinical context for Lane 3 so the provider does not have to click through six tabs before deciding.

None of this replaces the prescriber. It compresses the non-clinical minutes around the clinical decision.

What to measure once it is running

If you build this out, track a few numbers weekly and hold them steady. These are the ones I have found most useful:

  • Time from refill request to pharmacy dispatch, broken out by lane. Lane 1 should be measured in hours, not days.
  • Percentage of requests that hit Lane 1 on first pass. If this drops, something upstream is broken (lab ordering cadence, payment capture, consent renewal).
  • Automated patient outreach resolution rate. How many Lane 2 tasks close without staff involvement.
  • Provider seconds per Lane 1 approval. If this creeps up, your batching or context presentation needs work.
  • Rework rate. Refills that had to be reopened after "completion" because something was missed. This is your quality signal.

A practical sequencing plan

You do not have to build all of this at once, and you should not try. In practices I have helped stand this up, the order that works is: first, get every refill request into one structured intake regardless of channel. Second, codify the checklist as automation, even if the output is just a colored tag on the task. Third, split the queue into the three lanes. Fourth, turn on automated patient outreach for Lane 2. Fifth, layer in AI drafting and summarization. Each step compounds on the last, and each one is measurable on its own.

If you want to see how this looks inside an EMR built specifically for compounding and concierge practices, talk to our team and we can walk through the refill workflow with your protocols in mind.

A note on compliance

Automating refills does not change your prescribing obligations. The prescriber is still the prescriber, and the sign-off is still a clinical act. What automation does is make sure the prescriber is signing off on a complete, current, and correctly assembled record instead of an ambiguous one. State rules on refill authorization, telehealth encounters, and controlled substances vary, and 503A versus 503B routing has its own set of considerations. Confirm the specifics with your own counsel and your PIC before you flip any switch.

Frequently Asked Questions

How much of our refill volume can realistically be auto-approved?

In compounding practices with stable protocols (GLP-1s, hormones, LDN, peptide programs), 60 to 75% of refills can flow through a clean Lane 1 pathway once the checklist and patient-side automation are working. The remainder splits between patient action and clinical review, roughly two-to-one in most practices I have seen.

Do providers still have to sign every refill?

Yes. Automation prepares the request; the prescriber authorizes it. The difference is that a batched Lane 1 review takes seconds per patient because the context is pre-assembled and the checklist has already passed. The clinical act is preserved. The clerical wrapping around it is removed.

What breaks first when this workflow is under-built?

Payment capture and lab currency. If cards on file expire silently or lab orders are not renewed on a schedule tied to the protocol, Lane 2 volume balloons and staff end up doing the work anyway. Fix those two upstream processes before you scale automation, or you will just be automating the delivery of bad news.

How do we handle patients who message with a clinical question inside a refill request?

The workflow should detect that and route to Lane 3 with the message surfaced at the top of the provider's view. Do not let a clinical question ride along invisibly on a refill task. That is where errors happen, and it is the exact scenario where good sorting protects both the patient and the practice.