TL;DR: To clear a clogged NextGen refill inbox, fix matching and routing first, then automate the routine renewals. Start by finding why eRx requests won't match (demographic mismatches, brand versus generic names, inactive medications), clean up the task types and workgroups refills route to, and write a refill protocol that splits requests into auto-prepare, provider-review, and visit-required lanes. Refill workflow automation for NextGen can then prepare routine renewals so nurses and providers only handle real exceptions.
Why the NextGen refill inbox gets clogged
Most refill backlogs aren't caused by volume alone. They're caused by friction on each request: a task that won't match, a task routed to the wrong workgroup, or a renewal nobody feels authorized to approve.
Volume is real, though. Researchers tracking primary care physicians in the Annals of Family Medicine found prescription messages per 8 hours of scheduled clinic time rose 19.5% between 2019 and 2023, while inbox time grew more than 24%. Specialty groups managing chronic medications for dermatology, neurology, rheumatology, or cardiology patients feel the same squeeze.
In a NextGen practice, that volume lands in the Workflow module inbox as tasks. When things work, a renewal request arrives, matches the patient and medication, routes to the right workgroup, and gets approved. When they don't, you get three kinds of stuck tasks:
- Unmatched requests that need someone to figure out which patient or medication the pharmacy means.
- Misrouted requests sitting in a workgroup nobody checks, or assigned to a provider who's out.
- Undecided requests that matched fine but need a judgment call no one has written a rule for.
Each one adds minutes. Together they turn a manageable queue into a multi-day backlog, followed by pharmacy faxes asking about the original request and patients calling to ask why it hasn't gone through. That duplicate traffic is often what tips a busy inbox into an unmanageable one.
Step 1: Measure the backlog before you fix it
You can't fix what you haven't measured, and refill backlogs are notoriously misjudged. Before changing anything, pull two to four weeks of data on:
- Volume by channel: eRx renewals, phone messages, portal messages, pharmacy faxes.
- Turnaround time: hours from request to response, ideally by provider and location.
- Unmatched rate: what share of eRx requests needed manual matching.
- Reroute rate: how often a refill task moved from one workgroup or user to another.
- Duplicate requests: the same refill requested more than once because the first one stalled.
Even a rough count is useful. If 15% of eRx renewals are unmatched, that's your first target. If most delays happen in one workgroup, start there. Many practices discover that a small number of root causes explain most of the backlog.
Step 2: Fix the causes of unmatched eRx requests
An unmatched request is one NextGen couldn't automatically connect to a patient or medication in the chart. NextGen's documentation describes how eRx refill request matching works and what happens when pharmacy data doesn't line up. In practice, the causes tend to repeat:
- Demographic differences. Nicknames, hyphenated last names, transposed dates of birth, or an old address at the pharmacy.
- Brand versus generic names, or a different strength or formulation than what's on the active med list.
- Medications no longer active in the chart, because they were discontinued, changed, or entered as historical.
- Prescriber mismatches, such as a request addressed to a provider who has left or moved locations.
- Duplicate patient records, which make the match ambiguous.
Work the list by frequency. Clean up duplicate charts. Reconcile med lists at visits so the active list reflects reality. Update provider records when people leave. Ask your highest-volume pharmacies to correct demographic data that keeps mismatching.
None of this is glamorous, but it compounds. Every percentage point you take off the unmatched rate is a set of tasks your team never has to touch by hand again.
Step 3: Clean up task types and workgroups
Routing is where good refill processes quietly decay. Task types and workgroups get set up during implementation and then drift as staff turn over, providers join, and locations open.
Audit your setup with three questions:
- Does every refill task type route to a workgroup that's actively staffed? Look for workgroups with old tasks piling up. Those are usually orphaned.
- Are workgroups organized the way you actually staff refills? If one nurse pool covers three providers, the routing should reflect that, not the org chart from two years ago.
- What happens when a provider is out? Coverage rules should send that provider's refills somewhere useful automatically, not leave them waiting until the provider returns.
A simple rule: every refill task should have one obvious owner within minutes of arriving. If your team can't say who owns a given request, the routing needs work.
Step 4: Write a protocol that splits refills into lanes
Undecided requests are the slowest kind, and the fix is a written refill protocol your providers have signed off on. Without one, every renewal is a judgment call, and judgment calls wait for the provider.
Split requests into three lanes:
- Auto-prepare lane. Routine renewals of protocol-eligible maintenance medications for patients seen within the visit window, with required labs current. These get prepared and queued for quick provider approval or delegated nurse action, depending on your policy.
- Provider-review lane. Controlled substances, high-risk medications, dose changes, abnormal labs, or anything outside protocol. These go to the prescriber with context attached.
- Visit-required lane. Patients overdue for follow-up. The protocol should say whether a bridge supply is allowed, how much, and how the patient gets scheduled.
Write the protocol by medication class, not drug by drug. Name the monitoring labs and visit windows for each class. Keep controlled substances out of any automatic lane: EPCS rules require prescriber identity verification and two-factor signing, and many states require a PDMP check.
Then make sure everyone follows the same rules. Protocol drift between providers, where one doctor renews everything for a year and another wants a visit every three months, is one of the most common reasons automation projects underperform.
Step 5: Automate the routine lane
With matching fixed, routing cleaned up, and a protocol in place, automation can do what it's good at: preparing the routine renewals so nobody has to do the same chart check 80 times a day.
Refill workflow automation for NextGen reads each request, confirms the patient and medication match, checks the chart against your protocol, and either stages a prepared renewal or routes the request to the right lane with the reason attached. Your nurses stop opening routine renewals cold. Your providers sign prepared requests instead of researching each one.
The results can be significant. The AMA described how Atrius Health cut 50% of prescription-renewal messages reaching its physicians through automated protocols, part of a broader effort that cut primary care inbox volume by 25%. A practice of any size can apply the same logic at its own scale.
This is the work Honey Health's Refill agent is built for. It handles intake from eRx, phone, portal, and fax channels, resolves clear mismatches, checks protocol against the chart, prepares renewals for provider sign-off, and sends exceptions to the right NextGen workgroup with the reason noted. It doesn't add headcount, and it doesn't replace NextGen's refill tools. It does the prep work your team is doing by hand today.
Expect the gains to show up in a specific order. Turnaround on routine renewals improves first, often within the first couple of weeks. Duplicate requests and refill-status calls fall next, because fewer requests are stalling long enough to trigger them. The unmatched rate falls last, since it depends on the data cleanup from Step 2 catching up.
Start supervised. For the first few weeks, have staff review every prepared renewal and every flagged exception. Track where the automation and your team disagree, adjust the protocol, and expand once accuracy is proven.
How to keep the backlog from coming back
Clearing a backlog once is easy compared with keeping it clear. Build a few habits into operations:
- Review turnaround weekly. Median hours from request to response, by location. If it creeps up, investigate right away.
- Watch the unmatched rate. A rising rate usually means a new pharmacy, a data entry habit, or a provider change worth fixing at the source.
- Track pharmacy callbacks and duplicate requests. These are the best leading indicator that requests are stalling.
- Re-review the protocol quarterly with clinical leadership. Add medication classes that are consistently approved, and tighten rules where exceptions keep slipping through.
- Audit stale medication lists. Encourage med reconciliation at every visit. A clean active med list prevents more refill problems than any routing rule.
A few pitfalls are worth naming. Don't let the protocol become a document no one reads. Don't let a single provider's preferences create a parallel process. And don't assume automation fixes bad data. It will surface bad data faster, which is useful, but someone still needs to fix it.
Frequently Asked Questions
What is an unmatched eRx refill request in NextGen?
It's a pharmacy renewal request that NextGen couldn't automatically connect to a patient or an active medication in the chart. Common causes include demographic differences, brand versus generic names, discontinued medications, and duplicate patient records. Staff have to reconcile these manually unless the underlying data issues are fixed or automation handles the clear cases.
How many refill requests can a nurse handle per day?
It depends on how much chart review each request needs. Routine renewals with clean data can take a couple of minutes, while unmatched or complicated requests take much longer. Measuring your own time per request for two weeks gives a far better planning number than any benchmark.
Should medical assistants handle refills in NextGen?
MAs can often handle intake, matching, and protocol checks, but scope depends on state law and your practice's delegation policy. Licensed prescribers must approve prescriptions. Many practices let MAs or automation prepare requests while nurses and providers handle decisions.
How quickly can a refill backlog be cleared?
Once matching and routing problems are fixed, most practices can clear an existing backlog within days. Keeping it clear depends on having a written protocol and automating the routine lane, which typically takes a few weeks to set up and tune.
Does automating refills create safety risks?
Done properly, it lowers risk by applying the same checks every time and flagging exceptions clearly. Keep controlled substances, abnormal labs, and dose changes with providers, start in a supervised mode, and audit decisions regularly during rollout.
