TL;DR: A PE-backed MSO standardizes refill protocols across athenahealth practices by building one governed protocol library, organized by medication class and specialty, and enforcing it centrally so every site routes, approves, and escalates requests the same way. Athenahealth refill request automation is how the library gets applied consistently, because a document in a shared drive changes nothing until software checks every request against it. Clinical leadership signs off on the rules; operations owns the rollout and the reporting.
Why does refill handling vary so much across acquired practices?
Every practice you acquire arrives with its own refill habits, and almost none of them are written down. One site renews stable maintenance medications after a visit within twelve months. The next one wants six. A third lets the front desk approve anything the pharmacy faxes over, while the fourth routes every request to a nurse who has done it the same way since 2014.
None of this is irrational. Each site built its process around its own providers, staffing, and risk tolerance. The trouble shows up when you try to run them as one company. You can't compare turnaround times between sites if the sites measure different things. You can't forecast staffing if one site's refill load is three times another's for the same panel. And you can't make a credible case to your board that integration is working when the refill inbox, the most visible daily friction for patients, behaves differently in every building.
Even on the same EHR, the variation sits above the software. The rules about who approves what, in which order, with which checks, live in people's heads, not in the system.
What does a governed refill protocol library look like?
A protocol library is a set of written rules, one per medication class, that says what must be true for a request to be approved, routed to staff, or sent straight to a provider. It is short, specific, and signed by clinical leadership.
Start with the classes that make up most of your volume. A typical first pass covers:
- Stable maintenance medications such as blood pressure and cholesterol drugs, with a visit window and any required lab.
- Thyroid and diabetes medications, with the lab window that applies to each.
- Medications that need monitoring, where a missed lab changes the answer.
- Controlled substances, which go to the provider every time at every site.
- Everything unusual, with a default of provider review.
Each rule should read like a checklist, not an essay. "Last visit within 12 months, no active chart flag, refills remaining, same pharmacy" is a rule. "Use clinical judgment" is not, and it's the phrase that lets sites drift apart.
The AMA notes that yearly visits aren't always required to continue non-controlled maintenance medications, and that renewal rules vary by state. That matters for a multi-state MSO. Your library needs a state layer, so the rule for a site in one state doesn't quietly contradict the law in another. Have counsel and your medical director review it before launch.
How do you get clinical buy-in without a year of committee meetings?
The fastest route is a small protocol group, not a full medical staff vote. Pick three to five physicians and one nurse leader from different sites and different specialties. Give them a draft library and a deadline of a few weeks.
Draft the first version for them. Pull the actual rules in use across your sites, find where they agree, and write the common version. Your clinicians will react to a concrete draft much faster than they will build one from a blank page.
Settle disagreements with data when you can. A PRiMER study of a multidisciplinary refill protocol in two Milwaukee family medicine residency clinics found that median refill completion time fell significantly after the protocol was adopted. For residents it dropped from 383 minutes to 79 minutes. It's a small, academic setting, so don't over-read it. The useful takeaway for your group is that clear ownership and clear rules moved the turnaround, and your protocol group can argue for the same thing at your scale.
Then ratify it. A signed library, with a named owner and a revision date, gives every site manager something to point to when a provider asks why the rule changed.
Should you centralize the refill queue or leave it with each site?
Both models work. The choice depends on how many sites you have and how much your sites differ.
A centralized queue routes refill requests from all sites to one team. You get consistent decisions, easier staffing, and clean reporting. The cost is distance: central staff don't know the local providers, and sites may feel they've lost control of their patients.
Site-level ownership keeps the work local. Staff know the providers and the patients. The cost is the variation you started with, plus uneven workloads.
Most MSOs land on a hybrid. The protocol, the routing logic, and the reporting are central. The exceptions go back to site staff, because they need local knowledge: an overdue visit that needs scheduling, a provider who's out, a patient with a complicated history. The routine pre-checks happen once, the same way, everywhere. The human work stays close to the patient.
How do you enforce the protocol the same way at every site?
A written library only changes behavior when something applies it to every request. Training and memos fade within a quarter.
This is where automation earns its place. Honey Health offers a Refill agent that applies a written protocol to each request and routes the result, so the same logic runs at every site. When your protocol group changes a rule, the change applies everywhere at once instead of site by site.
Whatever tool you choose, test it against these requirements:
- One rule set, many sites. Can you maintain a single library and apply site or state variations on top, rather than copying rules into each location?
- Reasons on every routing decision. A flag that says "no visit in 14 months, schedule appointment" is a task. A flag that says "needs review" is the old problem.
- A full audit trail. You need to see what was checked, what was found, and where the request went, across all sites.
- Human handoff. Controlled substances, dose changes, and low-confidence matches always reach a person.
- A clear integration path with athenahealth. Ask what the tool reads, where it writes, and how it behaves across separate practice setups.
Roll out in waves. Pilot at one or two sites, keep provider approval on every refill at first, and widen once the flags prove accurate. Early on, tune toward flagging too much. A false alarm costs a minute. A missed exception costs your providers' trust.
Which numbers should you report across sites?
Pick a short dashboard and keep it identical for every site. Otherwise you're back to comparing different things.
- Median turnaround from request arrival to resolution.
- Touches per request, meaning how many people handled it before it closed.
- Share of requests that reached a provider already pre-checked.
- Exception rate by site and by reason code.
- Aging, meaning how many requests are open past your time standard.
The exception rate is the most useful number for an MSO. A site with a high rate for "overdue visit" has a scheduling problem. A site with a high rate for "low-confidence match" probably has a data-quality problem. A site with a high rate of provider overrides may have a protocol the physicians don't trust, which is a signal to revisit the rule, not to push harder.
Measure for a month before you change anything. Without a baseline, you can't show your board what changed.
How do you handle change management with front desk and nursing staff?
Your front desk and nurses will decide whether this works. They know where the current process breaks, and they notice first when a rule is wrong.
Tell them plainly what changes. The chart lookups go away. Their time shifts to exceptions, patient calls, and scheduling overdue visits. Don't promise that nothing will change, and don't let the first they hear about it be an email from corporate.
Name a refill champion at each site, ideally a nurse or lead MA who works the queue daily. Give that person a direct line to the protocol group, so a bad rule gets reported and fixed in days. Staff who see their feedback change the rules stop treating the project as something done to them.
Expect resistance from providers who prefer their own approach. Handle it with a documented exception process: a provider can request a rule change through the protocol group, and until it's approved the standard applies. That keeps one provider's preference from becoming a fifth variation at one site.
What goes wrong in the first 90 days?
Three problems show up in almost every multi-site rollout, and all three are cheaper to plan for than to fix.
The first is a library that's too ambitious. Teams try to codify every medication on day one and stall. Ship the five or six highest-volume classes, send everything else to a provider by default, and expand the library as you learn.
The second is unclear ownership of exceptions. When a request is flagged, someone at the site has to own it, with a time standard. If no one does, flagged requests pile up in a new place and your backlog just changes address.
The third is inconsistent data. Protocol checks depend on clean visit dates, medication lists, and lab results. Sites that code or document differently will produce different flags from the same rule. Treat the first month of flags as a data-quality audit as much as a workflow test.
Frequently Asked Questions
How long does it take to standardize refill protocols across an MSO?
Most of the time goes to agreeing on the rules, not configuring software. If your protocol group moves quickly, a first library for the highest-volume medication classes can be drafted and signed in a few weeks. Rolling it out site by site takes longer.
Who should own the refill protocol library?
Clinical leadership should own the rules, usually a medical director with a small physician and nursing group. Operations owns the rollout, training, and reporting. Splitting it this way keeps clinical decisions with clinicians and keeps the process moving.
Do all sites need to follow the identical protocol?
The core rules should be identical. Add state-specific and specialty-specific layers where regulation or clinical practice requires it, and document each variation. Anything else is drift that makes your reporting unreliable.
Can automation approve refills without a provider?
That's a policy decision for your clinical leadership. Many MSOs keep provider approval on every refill at first and widen the fast path as the data builds trust. Controlled substances should go to a provider every time.
What should we measure first?
Median turnaround, touches per request, and the share of requests reaching providers pre-checked. Capture a month of baseline before you change the process, then compare site by site.
