TL;DR: A primary care group should split refill requests into two lanes: routine maintenance refills get checked against protocol rules and queued for fast sign-off, while controlled substances and flagged patients always go to a clinician with the chart context attached. That split is the core of refill workflow automation for Elation Health. The provider keeps final authority in both lanes, and every decision leaves an audit trail.
Why does refill workflow automation for Elation Health need two lanes?
Refills look like one task, but they're two different risk profiles sharing one inbox. A lisinopril renewal for a stable patient seen eight weeks ago and a request for a Schedule II stimulant do not belong in the same queue, and they don't need the same level of attention.
The volume is real. A study of 141 academic primary care physicians at UW Health, published in Annals of Family Medicine, found prescription refill messages rose from 12.0 to 14.3 per eight hours of scheduled clinic between 2019 and 2023. That's a 19.5% increase. Total inbox time over the same period grew from 57.4 to 71.4 minutes per eight hours of clinic.
Your numbers will differ, so treat this as an illustrative assumption. If the 14.3 figure held for a 12-provider group running five full clinic days a week, that's roughly 860 refill messages weekly. At two minutes of staff touch each, you're spending about 29 hours a week just moving refills around.
Most of those are routine. The dangerous move is automating all of them the same way. The safer design sorts first, then automates only the lane where a mistake is cheap to catch.
In Elation, pharmacy refill requests land in the patient's chart, get assigned to a provider, and show up under Requiring Action and in the Rx Requests inbox, per Elation's electronic prescription documentation. That's your integration point. Automation sits in front of that inbox, prepares the work, and hands it to a human.
How do you tier refill requests by medication class?
Start with a medication-class list your medical director signs off on. Keep it short enough that everyone can recite it.
A workable three-tier version looks like this:
- Tier 1, routine maintenance: long-term, non-controlled medications for stable chronic conditions. Examples: statins, ACE inhibitors, metformin, levothyroxine, inhaled controllers.
- Tier 2, needs review: non-controlled drugs where your group wants a clinician to look every time. Examples: anticoagulants, immunosuppressants, anything with a monitoring requirement, anything started in the last 90 days.
- Tier 3, clinician-only: controlled substances, plus any patient on your flagged list.
Tier 1 is the only lane where the automation pre-validates and queues. Tiers 2 and 3 get assembled into a review packet and routed to the provider without any pre-approval.
Who decides what lands in Tier 2? Your medical director, not a vendor default. The class list is a practice policy document. Version it, date it, and review it quarterly.
A tier assignment should also be sticky to the patient, not just the drug. A flagged patient (recent ER visit for a medication issue, a documented concern about early refills, a pending specialist change) moves every request to Tier 3 regardless of the drug name. Build that flag as a field the automation reads, not as a note someone has to remember to check.
What protocol rules should a routine refill pass before it's queued?
Protocol rules turn "this looks fine" into something auditable. For Tier 1, most groups check four things.
- Last visit: the patient was seen within your window, often 6 or 12 months depending on the condition.
- Lab recency: drugs that need monitoring have a result inside the required interval.
- Refill count: the request isn't asking for more refills than the original order allows, and the patient isn't requesting early.
- Active order match: the pharmacy's request matches a medication on the chart, with the same drug, strength, and sig.
Pass all four and the request is queued with a green summary: "Last visit 4/14, A1c 5/2, 2 refills remaining, matches active order." Fail any one and it's re-routed to Tier 2 with the failing rule named.
That named reason matters. A vague "needs review" flag trains staff to ignore it. "No A1c in 14 months" gives the clinician a decision in ten seconds.
Notice what the automation doesn't do: it doesn't send the prescription. Queued means ready for sign-off. In the Elation workflow, providers can approve, approve with modifications, change the number of refills, deny with a reason, or reassign, and that stays true here. The automation prepares; the provider decides.
The failure mode to watch is rule drift. Someone loosens the last-visit window "just for flu season" and nobody tightens it back. Log every rule change with a name and a date, and review the log at your monthly operations meeting so the medical director sees what shifted and why.
What happens when a request goes to a clinician?
Escalation is where the whole design earns trust. A clinician who opens a Tier 3 request should not have to hunt through the chart.
The review packet should carry the essentials: current medication list, last visit date and note headline, the last fill dates shown by the pharmacy request, recent relevant results, any open flags, and the specific rule that routed it. Two lines of context beat ten tabs. If the packet takes a clinician more than a minute to read, trim it until it doesn't.
Routing matters too. Elation lets a renewal request be reassigned to another eligible provider with an active Surescripts enrollment, and for controlled substances, EPCS capability as well. Build your escalation path around that. If the prescribing provider is out, the request goes to a named covering provider, not to a shared pile.
Many groups miss this one. For controlled substances, the staff-level shortcut doesn't exist. Elation's documentation states that authorized Rx Delegates cannot address controlled substance medication refill requests on a provider's behalf due to DEA regulations. So the automation shouldn't try to emulate one. It prepares the packet, sets the priority, and waits.
Set a service level for each tier. A reasonable starting point: Tier 1 sign-off within one business day, Tier 3 within the same day when the patient is near running out. Elation archives pharmacy requests after 30 days, so an unanswered request will quietly disappear. Alert on anything aging past your threshold.
How do PDMP checks, EPCS, and audit trails fit in?
Keep this part administrative. Your clinicians own the clinical judgment; your job is making sure the process around it is consistent and provable.
Start with EPCS. Elation says each prescriber must pass identity proofing and set up two-factor authentication to meet DEA requirements, per its EPCS FAQ. The security code from the token changes every 30 seconds, so the prescriber enters it at signing. Elation also notes that Schedule I and II drugs don't allow refills; the refill quantity on the order form is set to 0. That means a "refill request" for a Schedule II medication is really a request for a new prescription, and your workflow should label it that way.
Then PDMP. State rules vary a lot. The AAFP's PDMP background paper reported that as of May 2018, 41 states required prescribers or dispensers to check a PDMP before an initial opioid prescription, and 40 states allowed prescribers to designate delegates to use the system. That data is several years old, so confirm your state's current rules with your compliance counsel before you write them into policy.
For the audit trail, capture at minimum:
- the request as received, with a timestamp
- the tier assigned and the rule that assigned it
- who reviewed it, what they decided, and when
- whether a PDMP check was documented, where your state or practice policy requires one
- every change to the tier list or rules, with the approver
If a regulator, auditor, or malpractice carrier asks how a specific refill got approved, you should be able to answer in one screen.
How should you roll out the workflow in phases?
Don't turn it on for everyone at once. A phased rollout lets you catch bad rules while the cost is small.
Phase 1, shadow mode (2 to 4 weeks). The automation tiers and validates every request but sends nothing to the queue. Staff work refills the usual way. You compare what the automation would have done against what actually happened, and you fix the mismatches.
Phase 2, Tier 1 for one pod (4 weeks). Pick one provider team with a patient mix that's mostly chronic maintenance. Pre-validated Tier 1 requests go into the queue; providers sign off. Track override rate: how often a provider rejects or modifies a queued refill. A high override rate means your rules are too loose.
Phase 3, full Tier 1 across the group. Expand once override rates are stable and nobody's finding surprises.
Phase 4, Tier 2 and Tier 3 packets. Add the review packets and escalation timers last. These don't pre-approve anything, so the risk is low, but the value is high.
At every phase, the provider keeps final authority. That's the principle to put in writing before you start. Honey Health built its refill agent around this model, working alongside Elation with human sign-off at each decision point, but the structure above works regardless of whose software runs it.
Frequently Asked Questions
Can an automated workflow approve refills without a provider?
For a safe design, no. The automation can validate a request against your protocol rules and queue it, but a provider should sign off. This keeps clinical responsibility with a licensed prescriber and gives you a clear audit record of who approved what and when.
Why can't staff just handle controlled-substance refill requests?
Elation's documentation states that authorized Rx Delegates cannot address controlled substance refill requests on a provider's behalf due to DEA regulations. The prescriber must complete EPCS signing with their own two-factor credentials. Automation should prepare the packet and route it, not act in the prescriber's place.
What rules should define a routine refill?
Most groups check four things: a recent enough visit, recent labs where the drug requires monitoring, a refill count that matches the original order, and a match to an active medication on the chart. Failing any rule moves the request to a clinician review lane with the reason named.
How does PDMP checking fit into an automated workflow?
PDMP requirements are set by each state and by your own practice policy. The workflow can prompt the prescriber and record that a check was documented where required, but it shouldn't replace the prescriber's review. Confirm current state rules with compliance counsel before codifying them.
How long should the rollout take?
Plan on roughly three months for a mid-sized group: a few weeks in shadow mode, a month with one pilot team, then group-wide Tier 1, then review packets for the higher tiers. Move to the next phase only when override rates and turnaround times hold steady.
