TL;DR: A multi-specialty group on NextGen should build one shared refill policy that routes every request by medication risk and visit status, then layer specialty-specific rules on top as documented exceptions. Biologics in dermatology and rheumatology, anticonvulsants in neurology, and controlled substances in pain management and psychiatry each get their own monitoring and visit requirements. Refill workflow automation for NextGen can then enforce the same rules at every site, while licensed providers keep the final decision on restricted medications.
Why refill handling fragments in multi-specialty groups
Most multi-specialty groups didn't design their refill process. They inherited several. Each department brought its own habits, each acquired practice brought its own staff, and NextGen got configured to support all of them at once.
The result is predictable. Cardiology renews statins for a year without a visit, while primary care down the hall wants labs every six months for the same drug. One neurology provider renews anticonvulsants over the phone, another insists on a visit. Nurses floating between departments learn three sets of unwritten rules.
That inconsistency has real costs:
- Slower turnaround, because staff can't act without checking with each provider.
- Uneven patient experience, since the same request gets different answers depending on who picks it up.
- Compliance exposure, because nobody can show auditors a single policy that's followed.
- Wasted provider time, with physicians fielding refill questions a protocol could answer.
The time pressure is growing too. A study in the Annals of Family Medicine found prescription messages per 8 hours of clinic time rose 19.5% from 2019 to 2023 for primary care physicians. Spread that growth across ten specialties and several locations, and inconsistency becomes an operations problem you can measure.
The model: one shared policy, specialty rules layered on top
Here's the approach that works: write one refill policy that applies everywhere, then let specialties add rules on top of it rather than replacing it.
The shared policy answers the questions every refill raises:
- Who can prepare a refill? MA, nurse, pharmacist, or automation, according to your delegation policy and state law.
- Who can approve one? Licensed prescribers, plus any nurse-delegated protocol your medical leadership authorizes.
- What's the default visit window? For example, seen by the prescribing specialty within 12 months.
- What's the default bridge-supply rule for patients overdue for a visit?
- What always goes to a provider? Controlled substances, dose changes, abnormal labs, new medications.
Then each specialty documents its exceptions to that baseline. The specialty can be stricter than the shared policy, never looser on safety-critical items. This keeps the structure simple: one policy document, plus a short addendum per specialty.
Route by medication risk and visit status
The shared policy works best when it sorts every request into lanes, regardless of specialty.
Lane 1, routine renewal. Maintenance medications on the protocol-eligible list, patient seen within the visit window, required labs current, no recent changes. These are prepared and queued for quick approval.
Lane 2, provider review. High-risk medications, controlled substances, out-of-range or overdue labs, dose changes, or anything not on the protocol list. These go to the prescriber with chart context attached.
Lane 3, visit required. Patients past the visit window. The policy specifies whether a bridge supply is allowed, how many days, and how scheduling happens.
Lanes make the policy usable. Staff don't need to memorize every rule for every drug. They need to know which lane a request belongs in, and the protocol tells them.
What specialty-specific rules look like
Specialty addenda are where clinical leadership adds what generic rules miss. A few common examples:
- Dermatology. Isotretinoin carries iPLEDGE program requirements and should never be in a routine lane. Systemic immunomodulators and biologics need monitoring labs and are often tied to prior authorization renewals.
- Rheumatology. Methotrexate and other DMARDs require regular blood count and liver function monitoring. Biologics frequently need prior auth re-approval alongside the refill.
- Neurology. Anticonvulsants may need drug level monitoring for some agents, and abrupt interruption carries clinical risk, so bridge-supply rules matter more here.
- Cardiology. Anticoagulants and antiarrhythmics need tighter monitoring than statins or most blood pressure medications.
- Pain management and psychiatry. Controlled substances stay in the provider lane, with PDMP checks where your state requires them.
- Primary care. Usually holds the largest protocol-eligible list: blood pressure, cholesterol, thyroid, diabetes maintenance medications, each with defined lab requirements.
Each addendum should list medication classes, the monitoring labs and frequency, the visit window, and any extra documentation. Keep it short. One page per specialty is a good target.
How to handle provider preferences without creating dozens of variants
Expect pushback. Some providers will want their own rules, and in a group with 60 physicians that can quickly mean 60 protocols. Set a clear test for exceptions: a specialty addendum can change a rule when there's a clinical reason that applies to the whole department, such as a monitoring requirement or a program like iPLEDGE. Individual preference alone doesn't qualify.
When a provider wants something different, route the request to the specialty lead. If the reasoning holds, change the addendum for everyone in that specialty. If it doesn't, the shared rule stands. This keeps the number of variants small and makes every rule traceable to a decision someone made on purpose.
Governance: who owns the protocol and the NextGen setup
Without clear ownership, a standardized protocol drifts back into chaos within a year. Assign three roles explicitly.
Clinical owner. Usually the CMO or a physician committee. Approves the shared policy and every specialty addendum, and reviews them at least annually.
Specialty leads. One physician per department who owns that addendum and signs off on changes.
Operations owner. An MSO ops leader or director of clinical operations who owns how the protocol is implemented in NextGen: task types, workgroups, routing rules, coverage when providers are out, and reporting.
That last role is often missing. The protocol says what should happen; NextGen's Workflow configuration determines what actually happens. If task types and workgroups differ by site, your standardized policy won't behave the same way everywhere. Audit task routing so every location uses the same lane structure, with workgroups named consistently and coverage rules defined.
Where EPCS, PDMP, and state rules limit automation
Standardization doesn't mean everything can be automated. Some limits are regulatory, and your protocol should name them.
Controlled substances prescribed electronically fall under DEA rules for electronic prescribing of controlled substances (EPCS), which require prescriber identity proofing and two-factor authentication at signing. Many states also require a PDMP check before prescribing or renewing certain controlled substances. Automation can assemble context, such as last fill dates and the last visit, but the prescriber completes the review and signs.
State scope-of-practice rules affect what nurses and MAs can do under a delegated protocol. A group operating in several states may need state-specific delegation language even if the clinical rules are the same.
Specialty programs like iPLEDGE have their own requirements that override general protocol logic.
Write these constraints into the shared policy so no site or specialty accidentally builds an automatic lane that shouldn't exist.
Roll out by site and specialty, then measure consistency
Don't flip the whole group at once. A phased rollout lets you prove the model and fix problems before they spread.
- Pilot one specialty at one site with high volume and a willing physician lead. Primary care is often the easiest start because its protocol-eligible list is the largest.
- Run supervised for a few weeks. Staff or automation prepare renewals by lane; a nurse reviews everything. Track disagreements and adjust.
- Extend the same specialty to other sites, checking that NextGen routing behaves identically.
- Add specialties one at a time, each with its addendum approved before go-live.
Measure consistency, not just speed:
- Turnaround time by site and specialty
- Share of requests in each lane by site and specialty
- Bridge supplies issued per 100 requests
- Exceptions overridden by providers
- Pharmacy callbacks and duplicate requests
If one site routes twice as many requests to provider review as another for the same specialty, the protocol isn't being applied the same way. That's the signal to investigate.
How automation keeps the rules consistent
Written protocols are only as consistent as the people applying them, and in a group with dozens of nurses and MAs across sites, people vary. Automation applies the same rules every time.
Refill workflow automation for NextGen reads each request, matches patient and medication, checks the chart against the shared policy and the right specialty addendum, and places the request in the correct lane. Routine renewals get prepared for approval. Everything else goes to the right workgroup with the reason attached.
Results from organizations that tried this are encouraging. The AMA reported Atrius Health cut 50% of prescription-renewal messages reaching its physicians by using automated protocols.
Honey Health's Refill agent is built for this multi-site, multi-specialty pattern. It applies a shared protocol with specialty-specific rules across every NextGen location, prepares routine renewals, and routes exceptions consistently, while licensed providers keep the decision on anything restricted. Groups that standardize refills often use the same rollout to bring prior authorization renewals for biologics into the same workflow.
Frequently Asked Questions
Should every specialty in a group use the same refill protocol?
Every specialty should share the same baseline policy: lanes, delegation rules, and what always goes to a provider. Specialties then add documented exceptions for their medications. This keeps the group consistent while respecting real clinical differences between departments.
Who should approve refill protocols in a multi-specialty group?
A CMO or physician committee should approve the shared policy, and a physician lead from each specialty should approve that department's addendum. An operations leader should own how the protocol is built into NextGen routing and reporting.
Can refill automation handle controlled substances?
Automation can gather context, such as last visit and fill history, but controlled substances should always go to the prescriber. EPCS rules require prescriber identity verification and two-factor signing, and many states require PDMP checks.
How do you measure whether refill protocols are being followed?
Compare lane distribution, turnaround time, bridge supplies, and provider overrides across sites and specialties. Large differences for the same specialty usually mean the protocol is being interpreted differently and needs clarification or retraining.
How long does it take to standardize refills across a multi-specialty group?
Writing the shared policy and first addendum usually takes a few weeks. A pilot can run in another few weeks, and adding specialties and sites typically takes several months, depending on how many departments and locations the group has.
