Manual refill handling costs a CureMD practice roughly its monthly refill volume times the minutes spent per request times the loaded hourly cost of the staff doing the work, plus the hidden cost of delays and callbacks. Automating the routine requests pays back when the staff hours it returns are worth more than the automation costs to run. You can calculate that for your own practice in an afternoon using four numbers from your inbox and payroll.
What does manual refill handling actually cost?
Manual refill handling costs staff time first, and everything else second. Every request needs someone to open it, match it to the patient, check the chart against your protocol, prepare the response, and close it out. That is paid labor, whether or not anyone tracks it as a refill line item.
The scale is easy to underestimate because each request is small. In a health system study of primary care out-of-visit work, refill requests made up 178,160 of 472,411 tasks, the largest single category after results. Providers without scribe support took about three hours on average to complete a refill task. Most of that is waiting in a queue, not working, but the queue itself has a cost: patients call, pharmacies re-send, and staff chase.
The direct cost is the part you can measure precisely, so start there.
How do you calculate your own number?
Use this formula: monthly refill requests × average minutes per request × loaded cost per staff minute. Then add the cost of rework and callbacks. Each input is something you can pull or estimate.
Monthly volume. Count refill requests received per month across pharmacy, portal, phone, and fax. Use a three-month average so a bad week does not skew it.
Minutes per request. Time a sample of 30 to 40 requests from open to close. As a reference point, a Geisinger rheumatology group timed 40 physician refills at about two minutes each against more than 1,200 requests a month. Your staff time per request will depend on your workflow, so measure it rather than borrowing a number.
Loaded cost per minute. Take the hourly wage of the people who handle refills and add payroll taxes, benefits, and overhead. Divide by 60. Use your own payroll data, because wages vary widely by region and role.
Rework and callbacks. Count the calls from pharmacies and patients asking about status, and the requests that get sent twice. Multiply by the minutes each takes. This is usually smaller than the direct cost but rarely zero.
Write all four numbers down before looking at any vendor's pricing. If you start from a vendor's ROI calculator, you will inherit their assumptions.
What does a worked example look like?
The example below uses illustrative numbers, not benchmarks. Replace every figure with your own before drawing conclusions.
Assumptions (hypothetical):
- 1,000 refill requests per month
- 4 minutes of staff time per request when handled manually
- $35 per hour loaded cost (about 58 cents per minute)
- 70% of requests are routine and could be prepared by automation
- Automated preparation cuts staff time on a routine request from 4 minutes to 1 minute, since a person still confirms it
Before automation: 1,000 requests × 4 minutes = 4,000 minutes, or about 66.7 hours, costing about $2,333 per month.
After automation: 700 routine requests × 1 minute = 700 minutes, plus 300 non-routine requests × 4 minutes = 1,200 minutes. The total is 1,900 minutes, or about 31.7 hours, costing about $1,108 per month.
Difference: about 35 hours and roughly $1,225 per month, or about $14,700 per year.
Now subtract what the automation costs. If the annual cost of the tool, including your team's time to maintain the protocol, is below the annual saving, you have a positive return on direct labor alone. If it is above, the case has to rest on the softer benefits below.
Change one assumption at a time to see what drives the result. Usually it is volume and the share of routine requests. A practice with 300 requests a month and a 40% routine share will see a very different answer from the example.
What soft benefits should you count?
Direct labor is only part of the picture, but be disciplined about how you value the rest. Count a benefit only if you can tie it to a number you track.
- Provider time returned. When prepared renewals reach a provider ready to confirm, providers spend less time per request. The Geisinger group reported roughly 41.5 hours a month returned to its rheumatologists after moving routine refills to a pharmacist-led protocol. That was a human process, but it shows the scale of provider time that refill handling can absorb.
- Fewer status calls. Faster, more predictable turnaround reduces the calls from patients and pharmacies asking where a request stands.
- Consistency. Applying the protocol the same way every time reduces errors and the cost of fixing them.
- Staff retention and morale. Repetitive inbox work contributes to burnout. This is real, but hard to put in dollars, so list it separately and do not fold it into the payback number.
If you want to be conservative, leave the soft benefits out of the payback calculation and treat them as upside. That gives your partners or board a number that holds up.
What does implementation cost beyond the subscription?
The price on the proposal is rarely the whole cost. Budget for the work around it, because that is where payback estimates usually slip.
The largest item is protocol work. Your providers need to agree on refill rules by medication class, someone has to write them down, and someone has to maintain them. Expect several hours of provider and administrator time up front, and a short monthly review afterward.
Next is the pilot. Running the system in a review-everything mode for a couple of weeks means staff do the work twice for a while. Count that overlap as a one-time cost.
There is also integration and training time. Ask the vendor what they need from your CureMD configuration, who on your side has to be involved, and how long staff training takes.
Finally, there is ongoing oversight: reviewing exceptions, checking a sample of prepared renewals, and updating rules. Treat it as a recurring cost of a few hours a month, not zero.
How long does payback realistically take?
Payback time is the one-time costs divided by the monthly net savings. If your implementation effort is worth about $3,000 in staff and provider time, and your net monthly saving is the roughly $1,225 from the example minus the monthly tool cost, divide to find the months to break even. These figures are hypothetical, so run your own.
Three factors shift the answer the most. Volume matters because savings scale with request count while the protocol work is mostly fixed. The routine share matters because only routine requests get the large reduction in touch time. Staff cost matters because the same minutes are worth more where labor is expensive.
Be skeptical of any projection that assumes automation handles nearly every request. Controlled substances, overdue patients, and incomplete chart data will keep a meaningful share with people, and your model should say so.
What mistakes make refill ROI models misleading?
Four mistakes inflate or deflate the numbers most often. The first is counting freed minutes as cash. Saving 35 staff hours a month does not reduce payroll unless you change schedules or avoid a hire. More often the hours go to work that was being skipped, such as patient follow-up. That is still valuable, but name it honestly.
The second is using a vendor's average instead of your own mix. A practice with many controlled-substance and specialist-managed medications has a smaller routine share, so the same tool saves less.
The third is ignoring the exception workload. Automation reduces the routine work, but exceptions arrive with more context and often take the same time or longer. Model them at their full cost.
The fourth is forgetting that the baseline moves. If your volume grows or a provider leaves, manual handling gets more expensive over time. Show the model at today's volume and at a plausible future volume so the decision reflects where the practice is heading.
How should you present the case internally?
Give decision-makers three things: your measured baseline, a conservative scenario, and a clear test. The baseline is the four inputs. The conservative scenario uses a lower routine share and a smaller time reduction than you expect. The test is a pilot with success criteria set in advance.
Honey Health's refill agent is one option for the automation being costed here. It prepares routine renewals inside the practice's existing EHR workflow and leaves approval with the provider. Whatever you evaluate, ask the vendor to show the same four metrics from a pilot on your data instead of from a case study on someone else's.
A pilot that tracks turnaround, touch time, the share of requests handled in the routine lane, and the rate at which providers change prepared renewals will give you the real inputs for the model within a month.
Frequently Asked Questions
How much does manual refill handling cost per request?
It depends on your staff time and wages. Multiply the minutes a request takes by your loaded cost per minute. A sample of 30 to 40 requests timed from open to close will give you a reliable per-request figure for your own practice.
What share of refill requests can automation handle?
It varies by practice. Routine maintenance medications for recently seen patients are the usual candidates. Controlled substances, overdue patients, and requests with incomplete chart data stay with people. Measure your own mix before modeling savings.
Do I need to count provider time in the ROI?
Yes, but separately. Direct staff labor is easy to measure. Provider time returned is real, yet harder to convert to dollars, so present it as additional upside rather than the foundation of the case.
What if my refill volume is low?
Savings scale with volume while setup work is mostly fixed, so low-volume practices often see a long payback. If your volume is small and turnaround is fine, native tools and a clear owner may be the better investment.
How do I verify the savings after launch?
Track the same four numbers you measured before: volume, minutes per request, turnaround, and callbacks. Compare monthly for the first quarter. If minutes per request have not dropped, look at the share of requests reaching the routine lane.
