TL;DR: To automate prescription refill requests in DrChrono without adding staff, standardize your refill protocol first, then let an automation layer handle intake, chart checks, and routing so your team only touches exceptions. The sequence is five steps: audit volume, write explicit rules, consolidate channels into one queue, automate the chart check with a pre-filled decision, and track exception rate and turnaround every week.
Can you absorb more refill volume without hiring?
Yes, but not by working faster. You do it by removing the part of each refill that doesn't need a person.
Start with how much time the current process actually eats. A Journal of the American Board of Family Medicine study of five primary care practices found an average of 63 refill requests per physician per week. The American Medical Association cites 10 to 25 per day for a primary care physician and roughly 30 minutes a day spent on them. And a 2004 MGMA analysis, reported in Physicians Practice, put phone time alone for managing prescriptions at nearly 350 hours per full-time physician per year, or about $16,000. That figure is two decades old, so treat the dollar amount as a floor, not a forecast.
Those numbers are why adding a hire feels like the only option. It usually isn't, because most of the minutes sit in repeatable steps: finding the chart, checking the last visit, confirming the drug list, and typing the same denial reason again. Those steps can be standardized, and anything standardized can be automated.
Step 1: Audit your refill volume by channel and turnaround time
You can't automate what you haven't measured. Spend one to two weeks logging every refill request with four data points: how it arrived, who touched it, how long it took from arrival to decision, and what the decision was.
Pull the channel mix first. Most DrChrono practices will see some combination of pharmacy eRx renewals, patient portal requests, phone messages, and faxes. The mix matters because automation covering only the eRx queue leaves the other channels untouched. If a third of your volume comes in by phone and fax, a tool that only reads the EHR queue won't move your numbers much.
Then pull the decision mix. How many requests were approved as-is, how many were denied or redirected to a visit, how many were sent to a clinician for a judgment call, and how many were duplicates or already handled? That last bucket surprises people. The ratio of "approve as-is" to everything else tells you how much of your queue is actually automatable.
Step 2: Write explicit protocol rules
Automation runs on rules, so the biggest prep task is turning your providers' habits into written criteria. Do this as a group, in one meeting, with the medical assistants who actually work the queue in the room.
For each medication class you refill often, settle four things:
- Visit recency. How long can a patient go since their last visit before a refill needs an appointment?
- Monitoring requirements. Which drugs need recent labs, blood pressure checks, or other monitoring?
- Supply limits. How many days or refills can be approved at once?
- Exclusions. Which drugs or patient situations always go to a clinician?
Look at your state's rules while you're at it. The AMA notes that states such as Idaho, Illinois, Maine, and South Carolina allow non-controlled maintenance prescriptions to run 15 to 24 months, depending on the state, and that taking advantage of those provisions can cut request volume before you automate anything. Payer and pharmacy-benefit rules can limit that, so check both before changing your supply defaults.
Keep the first rule set conservative. It's easier to loosen a rule after you've seen the exception data than to explain a bad auto-approval.
Step 3: Consolidate intake into one queue
The point of this step is that your team should open one list, not four. Whatever you automate, the output has to land in a single place where a person can see what's waiting.
For eRx requests, that place is already DrChrono's refill queue. For the rest, you need a way to turn a fax image or a portal message into the same structured request. That means document reading for faxes and a standard intake form or message parser for the portal. A request that comes in as a scanned pharmacy form should end up looking like a request that came in electronically: patient, medication, dose, pharmacy, date.
This is also where duplicates get caught. The same refill often arrives twice: once from the pharmacy's automatic request and once from the patient's call. If both land in the same queue with the same patient and drug, the second one can be merged or closed with a note instead of worked from scratch.
Step 4: Automate the chart check and pre-fill the decision
This step produces most of the time savings. The automation layer opens the chart so your staff don't have to. For each request it matches the patient and medication, reads the last visit date, checks required monitoring against your Step 2 rules, and produces one of three outputs:
- Eligible. All rules pass. The request is queued for one-click clinician approval with the evidence attached.
- Needs action. A specific rule failed, such as an overdue visit. The request routes to the right person with the reason, and a patient message can be drafted.
- Needs clinician judgment. The case falls outside the rules, or involves a controlled substance. It goes to the prescriber with the chart context assembled.
How much time does this actually free up? One study of a clinical pharmacist-managed refill clinic estimated four to five minutes per request and reported that physician refill request volume fell by up to 60 percent. The authors couldn't measure time savings directly, so treat the minutes as an estimate. Still, if your current process takes even three minutes of staff time per request, the volume numbers from Step 1 turn into hours per week quickly.
A caution on scope: don't let the tool sign for anyone. Under 21 CFR 1311.120, an electronic controlled-substance prescription can only be signed by the prescribing practitioner. The automation prepares the decision. A licensed person makes it.
Step 5: Measure exception rate and turnaround every week
Set up a simple weekly view with five numbers:
- Requests received, by channel
- Share handled with no staff chart lookup before clinician approval
- Exception rate: the percentage routed to a person for any reason
- Median time from request to decision
- Patient callbacks about refill status
The exception rate is the number to watch. A high rate in the first month is normal, and it's information: it tells you which rules are missing or too tight. Review the top three exception reasons each week and decide whether each one is a real clinical case or a rule you should write down. In the California Health Care Foundation's evaluation of a refill automation platform at two health centers, one site's same-day refill completion rose from 57 to 68 percent. The study was small and linked to the vendor, but it shows the kind of metric worth tracking.
When is hiring still the right call?
Automation isn't always the answer, and it's worth being honest about when it isn't. If your refill volume is low, say a handful of requests per provider per day, the setup effort may outweigh the benefit. If the real bottleneck is clinician sign-off rather than staff prep, a tool that pre-fills decisions will help, but it won't shorten the queue of approvals waiting on a busy prescriber.
The cleaner test is this: look at your Step 1 audit and ask where the minutes go. If most of the time is chart lookups, re-keying, and chasing patients, automation fits. If most of it is clinical decision-making, you need provider time, a standing-order policy, or a pharmacist or nurse-led refill protocol like the one in the community health center study above. Many practices end up doing both: a clearer protocol that lets a trained medical assistant or nurse handle routine renewals, with software doing the lookup work in front of them.
What goes wrong, and how do you avoid it?
Three failure modes show up repeatedly.
Duplicate requests. The pharmacy and the patient both ask, and two staff members work the same refill. Fix it with matching on patient, drug, and date in the intake step.
Pharmacy change requests. Some "refill" requests are really asking for a different strength, quantity, or formulation. They look routine but need a prescriber's decision. Route anything that isn't a straight renewal to a clinician.
Refills that quietly require a visit. A patient who is eight months overdue for a follow-up will keep requesting a drug until someone says no. If your rules catch this, the automated message can book the visit. If they don't, it falls to a staff member to notice, and many don't.
The common thread is that automation makes your existing process visible. It won't fix a protocol your providers disagree about.
Where does Honey Health fit in this process?
Honey Health's Refill Management agent is designed for steps three through five: pulling requests from multiple channels into one queue, running the chart check against your protocol, and giving your team a labeled list of what's ready to approve and what needs attention. It works alongside your EHR rather than replacing it, so your providers keep signing in the system they already use.
Steps one and two are yours regardless of which tool you choose, and they're where most of the value comes from. A practice with a clear protocol and honest volume data will get more from any tool than a practice that skips them.
Frequently Asked Questions
How long does it take to automate refills in DrChrono?
The audit and protocol work usually take longer than the software setup. Plan on a few weeks for Steps 1 and 2, then a short pilot with a narrow set of medications. Expand once the exception data looks clean.
Which refills should I automate first?
Start with routine, non-controlled maintenance medications for established patients, where visit and lab rules are clear. Leave controlled substances and complex cases in the clinician path until you trust the rest of the workflow.
Do I need to change my EHR workflow?
Not necessarily. The goal is to keep prescribers signing in DrChrono while the automation layer prepares the work. Confirm with any vendor exactly what it reads and writes in your instance.
Will patients notice a difference?
Mostly through faster answers and fewer callbacks. A refill that used to wait in a queue for a day can be ready for approval within hours, and denials can come with a clear reason and next step.
What if my providers disagree on refill rules?
Resolve that first. Disagreement is the most common reason refill automation underperforms. Hold one meeting, settle the rules by medication class, and document them. The result is useful even if you never buy software.
