A multi-specialty group should route CureMD refills by medication risk: routine maintenance medications go to a protocol-based lane where staff or software prepare the renewal, while controlled substances, high-risk drugs, and patients overdue for a visit always go to a prescriber. Automation can prepare and route, but a licensed provider decides anything restricted. The groups that get this right write one policy with specialty-specific exceptions rather than a separate policy for every clinic.
Why does a multi-specialty group need a routing policy at all?
A multi-specialty group needs a routing policy because the same refill inbox receives very different requests. A cardiology group's blood pressure renewal, a psychiatry practice's stimulant request, and a primary care thyroid refill carry different risks, and treating them the same way means either slowing everything down or taking risks nobody approved.
Without a written policy, routing depends on whoever happens to open the request. One MA sends controlled-substance requests straight to the provider, another pre-fills them. One nurse refills an overdue patient for 90 days, another for 30. The group ends up with several informal policies and no way to audit any of them.
Volume makes this worse. In a health system study of primary care out-of-visit work, refill requests accounted for 178,160 of 472,411 tasks. A group that handles a share of that volume across specialties cannot afford case-by-case improvisation.
How do you define the lanes?
Define lanes by risk and by what a request needs next, not by specialty. Three lanes cover most groups.
Routine lane. Stable maintenance medications for patients seen recently, with monitoring current and no flags. Staff or software prepare the renewal and a provider or authorized nurse confirms it, depending on your standing orders and state rules.
Provider-review lane. Requests that are plausible but need judgment: recent dose changes, specialist-managed drugs, missing labs, conflicting notes, or anything the system cannot match with confidence.
Prescriber-only lane. Controlled substances, high-risk medications your medical director names, and any request your policy says only a prescriber may handle. Preparation may happen in advance, but nothing moves without the prescriber.
A fourth outcome, visit required, can sit inside the provider-review lane or stand alone. Either way, write down what happens to the patient: a bridge supply, an appointment, a message.
Which chart data should gate each lane?
Each lane should have an explicit, checkable gate. Vague rules such as "stable patient" cannot be enforced consistently, whether by staff or by software.
For the routine lane, the gates usually include:
- Medication on the approved list. The drug appears on a list your medical director has approved for protocol refills.
- Visit recency. A visit within a defined window, often 12 months. One published family practice protocol pairs a 12-month visit requirement with a normal TSH for thyroid refills.
- Monitoring current. Labs or vitals that your protocol requires for that drug class.
- No open flags. No recent hospitalization, new allergy, interaction alert, or "do not refill without visit" note.
- Refill count. The request does not exceed the number of renewals your protocol allows.
For the prescriber-only lane, the gate is mostly the drug classification itself. Everything in a controlled-substance schedule goes there, and so does anything on your named high-risk list. Do not make the gate depend on a staff member noticing.
Specialty differences usually show up in the approved list and the monitoring rules, not in the lane structure. A rheumatology group will have different monitoring requirements than a cardiology group, but both can use the same three lanes.
How do EPCS and state rules constrain automation?
Federal and state rules set the outer boundary of what automation may do with controlled substances. The structure of the federal rule is the clearest guide.
Under 21 CFR 1311.120, an electronic prescribing application used for controlled substances must require two-factor authentication to sign, allow only the prescribing practitioner to sign, time-stamp the signing, and keep an audit trail covering creation, alteration, signing, transmission, and deletion. It also requires a prescriber to review the prescription details and mark the prescription ready for signing before the signing step.
In plain terms: a human prescriber with credentials must personally approve each electronic controlled-substance prescription. No staff member and no software can sign on a prescriber's behalf. A refill agent may collect chart context, show a prescriber the patient's history, and queue the request, but the signature step is the prescriber's alone.
State rules add another layer. Prescription monitoring program checks, quantity limits, and delegation rules vary by state, so your compliance lead or counsel should confirm what applies to your group. Build those rules into the prescriber-only lane as required steps, and review them whenever state regulations change.
How do you document decisions for audit?
Documentation is what lets you defend your routing months later. Every routed request should leave a record that answers four questions: what was requested, which lane it went to, which checks ran, and who made the final decision.
At minimum, capture the request source and time, the matched patient and medication, the checks run and their results, the lane assigned and why, the person who approved or denied, and the time of closure. Software that produces this record automatically is more reliable than staff notes written after the fact.
Review a sample monthly. Pick a handful of requests from each lane and check that the lane matched the policy. Pay particular attention to requests that were moved from the routine lane to the provider lane by a person, since those overrides show where the rules do not match clinical reality.
The record also protects your staff. When the policy says controlled substances always go to a prescriber, and the log shows they did, nobody has to defend an individual judgment call.
How do specialty differences change the protocols?
Keep the lane structure the same across specialties and let each specialty own its approved list and monitoring rules. That gives you consistency where it matters and flexibility where clinical practice really differs.
A practical approach is a short group-wide policy plus one-page specialty addenda. The group-wide policy says what the lanes are, which drug schedules always go to a prescriber, how documentation works, and who approves changes. Each specialty addendum lists the medications eligible for the routine lane, the monitoring required, and any specialty-specific hard stops.
Assign an owner for each addendum, typically a lead physician, and set a review date. Without owners, addenda go stale and staff stop trusting them.
A pharmacist-led refill program at Geisinger shows that a clear protocol can change who does the work. After the change, physicians handled about 26% of refills and the group reported roughly 41.5 hours a month returned to its rheumatologists. That was a human-run protocol, but it shows how much of the volume a well-defined routine lane can absorb.
What mistakes do groups make when they write this policy?
Four mistakes show up again and again. The first is writing the policy around job titles instead of tasks. "Nurses can refill" means little until you say which medications, for which patients, under which conditions. Tie every permission to a defined list and a defined gate.
The second is leaving controlled substances to staff judgment. If the policy says a prescriber handles them, the system should enforce that, so a busy afternoon cannot turn it into a suggestion.
The third is building one enormous policy that nobody reads. A two-page group policy plus short addenda gets followed. A twenty-page binder does not.
The fourth is forgetting the patient. A request that lands in the visit-required outcome with no message to the patient simply comes back as three phone calls. Write the patient communication step into the policy.
How do you roll the policy out across locations?
Roll it out in stages so you find problems while they are small. Start with one site and one specialty, ideally one with a clear champion and a steady refill volume.
Spend the first two weeks in shadow mode: staff keep working as usual while the new lane assignments are logged alongside. Compare the two, list the disagreements, and fix the rules that caused them. Then move the routine lane live for that single site, keeping the provider-review and prescriber-only lanes unchanged.
After a month of stable results, add the next specialty or site. Each expansion needs its own addendum and its own owner. Keep one person responsible for the group-wide policy so changes are made once, not copied site by site.
Track the same few numbers throughout: median and 90th percentile turnaround, the share of requests in each lane, how often providers change prepared renewals, and how many requests were overridden between lanes. If those numbers move the right way for a month, the policy is working.
Where does automation fit?
Automation fits in the routing and preparation steps, never in the decision on restricted drugs. It reads the request, matches it to the chart, applies your gates, assigns the lane, and prepares the renewal for approval.
Honey Health's refill agent is one way to enforce these routing rules consistently across providers and locations, working inside the group's existing EHR workflow and leaving approval with licensed providers. Whatever tool you use, test the same things: does it send controlled substances to the prescriber lane every time, does it show which checks ran, and can your team change the rules without engineering help?
Run it in review mode first. Compare its lane assignments to what staff would have done for a couple of weeks, and investigate every disagreement before the system touches live volume.
Frequently Asked Questions
Can staff or software pre-fill a controlled-substance refill for a prescriber?
Preparation can help, but the prescriber must review and sign. Under federal rules, only the prescribing practitioner may sign an electronic controlled-substance prescription, using two-factor authentication. Check your state's rules on delegation and your group's policy before allowing any pre-filling.
Should every specialty have its own refill policy?
Use one group-wide structure with specialty addenda. The lanes, controlled-substance rule, and documentation standards stay the same everywhere, while each specialty defines its own approved list and monitoring requirements.
What counts as a high-risk medication for the prescriber-only lane?
Your medical director decides. Controlled substances are the clear starting point. Many groups also include drugs with narrow therapeutic windows or heavy monitoring requirements. Write the list down and review it at least annually.
How do we handle patients who are overdue for a visit?
Route them to a visit-required outcome. Many protocols allow a short bridge supply once an appointment is booked, but that is a policy choice for your medical director and not an automatic default.
How often should we audit refill routing?
Review a sample from each lane monthly at first, then quarterly once results are stable. Look especially at overrides and at any controlled-substance request that did not end up in the prescriber-only lane.
