TL;DR: You cut the refill request backlog in Elation Health by standardizing refill protocols, automating the chart-check and queuing steps, and saving provider time for true exceptions. Refill workflow automation for Elation Health works in five steps: measure volume and turnaround, codify protocols by medication class, route requests by risk tier, pre-populate each refill for provider review, and track turnaround and callback rates. Most practices see the gain in staff minutes per request, not in fewer requests.
What actually clogs the refill queue in Elation?
Elation sends every pharmacy refill request to the patient's chart and assigns it to a provider. According to Elation's own help documentation, requests land in the Rx Requests inbox on the provider's Practice Home page and in the Requiring Action section at the top of the chart. Requests older than 30 days get archived automatically, which tells you something: Elation expects some of them to sit.
Here's the part operators miss. The queue isn't slow because the software is slow. It's slow because each request needs the same small set of checks, and a person does them by hand. Someone opens the request, scrolls the chart for the last visit, checks the last fill, looks for overdue labs, and then decides whether to approve, modify, or deny.
Elation gives you six responses for a non-controlled request: Approve, Approve with modifications, Change Number of Refills, Deny, Deny & add reason, and Reassign to Provider. Those are the right buttons. The backlog builds in the minutes before anyone presses one.
Three failure modes show up again and again:
- Everything routes to the provider by default. Rx Delegates can handle many requests, but if the practice never defined what a delegate may approve, they escalate to be safe.
- Controlled substances sit in the same pile. Elation's documentation says Authorized Rx Delegates can't address controlled substance refill requests on a provider's behalf. Those requests need a provider, so they age behind routine ones unless you separate them.
- Nobody owns the queue. If four people can clear it, none of them is responsible for it at 4:45 on a Friday.
None of this needs a new hire. Good refill workflow automation for Elation Health starts with a defined process and a way to remove the repetitive lookup work.
How do you measure your refill backlog before changing anything?
Start with three numbers, pulled for a typical four-week stretch: requests per week, median hours from request to response, and the share of requests that come back to the practice as a patient call ("did you send my refill?").
Then do the simple math. Requests per week times minutes per request times loaded staff cost per hour gives you the weekly cost of the queue. These are illustrative assumptions, so swap in your own:
- 300 requests per week
- 6 minutes of staff time per request, counting chart review, the decision, and any follow-up
- $32 per hour loaded cost (wages plus benefits and payroll taxes) for a medical assistant or nurse
That's 1,800 minutes, or 30 hours a week. At $32 an hour, it comes to about $960 a week, or roughly $50,000 a year. If automation brings the touch time to 2.5 minutes, you've freed about 17.5 hours a week without cutting a single refill.
Why does this matter now? Hiring your way out is getting harder. In MGMA's 2026 Management and Staff Compensation report, 56% of practices said medical assistant hiring became harder over the past year, while 7% said it got easier. Medical assistant median pay rose 4.3% in 2025 and 20.6% over five years. Adding a body to the refill desk costs more and takes longer than it did.
Keep the baseline honest. Pull the data twice if the first week looks unusual, and don't count requests that were archived untouched as "handled."
Which refill protocols should you codify by medication class?
A written protocol is what lets a delegate say yes without a provider. Without one, every request is a judgment call, and judgment calls travel up the chain.
The clinical content belongs to your medical director and prescribers. You aren't deciding what's safe to refill. You're making sure those decisions get written down once instead of re-made 300 times a week. A usable protocol answers, for each medication class:
- Who may approve (delegate, nurse, pharmacist, provider only)
- The conditions that allow a standard refill, such as a visit within a set window or required labs on file
- The quantity and number of refills the practice will issue
- What forces an escalation to a provider
There's good evidence that this pays off. A multidisciplinary refill protocol at a family medicine residency in Milwaukee moved most routine requests to a dedicated refill nurse, and physicians only saw what the protocol couldn't cover. In the PRiMER study, median time to complete a refill among residents dropped from 383 to 79 minutes after implementation. Refill volume didn't fall, which is the point: the protocol changed who did the work and how fast, not how many requests came in.
That's one clinic, and a teaching clinic at that, so treat the exact numbers as a direction rather than a promise. But the mechanism carries over to a private practice.
A common failure here is writing a 30-page policy nobody opens. Aim for a one-page grid by medication class. If a delegate can't find the answer in under 30 seconds, they'll escalate.
How should you route requests by risk tier?
Routing is where you stop treating a blood pressure refill and a controlled-substance request as the same kind of work. Three tiers cover most practices:
- Green: routine, protocol-eligible. Stable maintenance medications where the patient meets your protocol conditions. A delegate or an automated pre-check handles these, and a provider signs off in batch.
- Yellow: needs a human look. The patient is overdue for a visit or labs, the dose request changed, or the pharmacy asked for something different from the original prescription. A nurse or MA reviews, then routes.
- Red: provider only. Controlled substances, anything outside protocol, and anything with a flag in the chart. In Elation, these also need a provider with an EPCS-capable account, per the help documentation.
The tiers do two jobs. They keep the provider's inbox short, and they stop the dangerous requests from hiding behind a hundred easy ones.
Set a turnaround target for each tier. Something like same business day for green, within one business day for yellow, and a named provider-of-the-day for red. Elation lets you reassign a request to another eligible provider, which the documentation shows as Reassign to Provider. That target provider needs an ePrescribing account and active Surescripts enrollment, so check that your coverage plan matches who can actually receive a reassigned request.
One more detail: decide who handles requests when the assigned provider is out. Unowned queues are where 30-day archives come from.
What does refill workflow automation for Elation Health look like in practice?
The steps that eat time are predictable, which makes them good candidates to automate: reading the request, pulling the last visit and last fill, checking protocol conditions, and building the refill so a provider only has to review it.
Here's a workable split of labor:
- The automation does the lookup. It reads the incoming request, matches it to the patient and the original prescription, checks the chart for last visit date and required labs, and sorts the request into green, yellow, or red.
- The automation pre-populates the refill. For green requests, it prepares the refill with the right drug, sig, quantity, and number of refills, ready for a one-click approval.
- A person decides. Providers review the pre-built refills in batch. Red requests go straight to them with the relevant chart facts attached.
Honey Health is one example of this model: an AI refill agent that works alongside Elation rather than replacing it. Your prescribers still approve in Elation, your pharmacy connections still run through Surescripts, and the audit trail stays in the chart. The agent takes over the chart-check and queuing steps that currently eat staff minutes.
Whatever tool you use, test it the way you'd test a new hire. Run it in shadow mode for a couple of weeks, with a human making every real decision, and compare its sort against what your nurse would have done. Count the misses by tier. A tool that puts a red request in the green pile is a worse problem than a slow queue, so don't turn on auto-routing until the red-to-green error rate is effectively zero in your sample.
Refill workflow automation for Elation Health won't fix a bad protocol. If your rules are vague, an agent will apply them vaguely and at higher speed.
How do you track turnaround and callback rates once it's running?
If you can't see it, the backlog comes back in three months. Track four numbers weekly and review them in your regular operations meeting:
- Median turnaround by tier, from request received to response sent
- Share completed within 48 hours, the measure the PRiMER clinics used to judge their protocol
- Callback rate, meaning patient calls asking about refill status per 100 requests
- Provider touches per request, which should fall as your green tier grows
The callback rate is the one operators skip, and it's the most honest. A queue can look fast on paper while patients keep calling because the pharmacy never got the answer. If callbacks per 100 requests don't drop within a month, something is wrong upstream, often a denial that never reached the patient or a request reassigned and forgotten.
Watch the denial and "approve with modifications" rates too. A sudden jump in modifications can mean your protocol quantities don't match what prescribers want, and a jump in denials can mean the routing is sending ineligible requests to the green tier.
Review the protocol grid every quarter. Formulary changes, new medications, and new prescribers all shift the rules. Assign one person, often the practice administrator with a clinical lead, to own the grid and the dashboard.
Frequently Asked Questions
Can you automate refills in Elation Health without replacing your EHR?
Yes. Refill workflow automation for Elation Health works beside the EHR. Elation stays the system of record where providers approve, modify, or deny requests. Automation sits beside it, reading incoming requests, checking the chart against your protocol, and preparing refills for provider review. Prescribers keep final authority, and the action is saved in the patient's chart as usual.
How long does it take to clear a refill backlog?
It depends on volume and how much protocol work exists already. A realistic path is two to four weeks to measure and write the protocol grid, then two weeks of shadow testing, then a gradual cutover by tier. Expect the existing backlog to shrink once green requests stop reaching providers individually.
Who can process refill requests in Elation?
By default, the provider the pharmacy addressed, and typically their Rx Delegates. Requests can be reassigned to another eligible provider who has an ePrescribing account and active Surescripts enrollment. Per Elation's documentation, Authorized Rx Delegates can't address controlled substance refill requests on a provider's behalf.
What's the fastest way to estimate the cost of refill requests?
Multiply requests per week by minutes per request, then by your loaded hourly staff cost. For example, 300 requests at 6 minutes and $32 an hour is about $960 a week. Use your own numbers, and include time spent on patient callbacks about refill status.
Should every refill request be automated?
No. Controlled substances and anything outside your written protocol should go to a provider. The goal is to automate the repetitive chart-check and queuing steps for protocol-eligible requests, so provider time goes to the exceptions that need judgment. Your medical director should sign off on which medication classes qualify.
