After the Pilot: How to Know When Pharmacy Automation Is Ready for the Next Workflow

Once the first workflow is running cleanly, the question independent pharmacy owners ask about pharmacy automation moves on. When do I give it more? And what should the next workflow be? It is a better question than the one that came before the pilot and it deserves a better answer than "whenever you feel ready." Most owners have a story about the last piece of pharmacy technology that did one thing well and then got stretched across three things it was never set up for. The goal is to expand on evidence at a pace the team trusts.

Here is how to read that evidence, how to pick what comes next, and how PAT (Pharmacy AI Technician) takes on a new workflow.

The Pharmacy Automation Question That Comes After the First Workflow

A first workflow is chosen to be safe. It is usually e-prescription entry or refills: work that repeats, lives on screens the team knows, and is easy to check. We wrote in April about why the boring stuff is where pharmacy AI should start, and most owners take that advice.

The second workflow is where judgment comes in. Expand too early and the team stops trusting the first one because every new problem looks like a problem with the whole tool. Wait too long and the time the first workflow gave back gets absorbed into the day without anyone deciding what to do with it. The question underneath is how to tell, from the pharmacy's own records, that the automation has earned more.

Three Signs Pharmacy Automation Is Ready for the Next Workflow

The exception reasons have become familiar. When PAT meets a prescription its task logic does not cover, it skips that one, keeps the rest of the queue moving, and sends the reason for review. The pharmacist makes the call and the logic expands to cover the case. In the first weeks the reasons are new. Later, the same reasons stop arriving because the rules now handle them and what is left is the work that belongs with a pharmacist anyway. Exceptions will never reach zero nor should they. The sign to look for is that new kinds of exceptions have stopped showing up.

The skeptic has run out of corrections. If the most skeptical technician on staff has been reading the log each morning, as we suggested in Run It Alongside First, their notes are the best readiness test available. When they stop finding things to correct, that is evidence the whole team will accept.

The team has stopped working around it. Staff route work into PAT's queue without being asked and nobody keeps a private list of the prescriptions they would rather do themselves. The pharmacist's verification step has not moved at any point and it will not move for the next workflow either.

How to Choose the Next Workflow

Start next door. The best next workflow sits close to the first: the same pharmacy management system screens, the same family of queues, a task the team already thinks of as related. E-prescription entry leads to refills; refills lead to cycle fills. The path most pharmacies describe looks like onboarding a new technician: start with the simplest work then hand over the next piece once the first is done well.

Pick the work that repeats more than it varies. A workflow with the same steps most of the time, and a short list of known exceptions, is a good candidate. A workflow where every case is a judgment call is a poor one however much time it takes.

Keep clinical judgment where it is. ASHP's policy on AI in pharmacy (Policy 2428, November 2024) reserves fully automated AI for algorithmic tasks where its performance is comparable to a person's, and keeps final decision-making authority with the pharmacist. That is the line for expansion too. However well the first workflow went, anything that needs clinical judgment stays with the pharmacist and the automation takes the algorithmic work around it.

How PAT Takes On a New Workflow

PAT (Pharmacy AI Technician) is a governed AI Technician that drives your existing pharmacy management system through the screen, over an encrypted tunnel, with no API required and nothing new installed at the pharmacy. A second workflow uses the same AI Technician and the same deployment.

New task logic, written from your team's way of working. The next task starts the way the first one did: Sonet's team watches how your staff work it today and writes it down as plain-English instructions and your team reads and edits that page before anything runs. We wrote about why the rules should belong to the pharmacy. Changes to task logic are included at no additional charge.

The same queue discipline. The new workflow gets its own queue, separate from the staff's, so the team can judge it on its own record. Every action is logged with the logic it applied, in the same format as the first workflow, so the morning review does not change shape.

The same pharmacist, the same pricing model. The pharmacist stays in the loop on every clinical decision. PAT is paid per completed task so a new workflow is billed as it runs. It does not need a new vendor, a point we made about the hidden cost of a new vendor for every new task.

A Practical Way to Decide

Three steps, in order.

Read the exception reasons from the last few weeks and group them. If new kinds are still appearing, give the first workflow more time. If the list has settled into a handful of familiar reasons, it is ready.

Ask your most skeptical technician what they would hand over next. They know which task repeats and which one hides judgment calls. Their answer is usually right and their agreement is what makes the next rollout stick.

Write the next task's page before you turn anything on. One page, plain sentences, how your best technician works that queue today. If the page fills up with "it depends," that workflow needs a pharmacist more than it needs automation.

How e-prescription, refill, and cycle fill tasks are written, reviewed, and run step by step is laid out in the PAT Solution Brief.

Frequently Asked Questions

How do I know PAT is ready to take on another workflow?

Look at three things: the exception reasons in the log have settled into a familiar list, your most skeptical technician has stopped finding corrections, and your team routes work to PAT's queue without being asked. The pharmacist's verification step stays where it is throughout.

What workflow should come after e-prescription entry and refills?

Usually the one next door: a task on the same pharmacy management system screens that repeats more than it varies. For many pharmacies that is cycle fills. Anything that needs clinical judgment stays with the pharmacist.

Does adding a workflow mean new software or a new vendor?

No. A new workflow uses the same AI Technician and the same deployment with new task logic written in plain English from how your staff work the task today. Nothing new is installed at the pharmacy and pricing stays per completed task.

Does the pharmacist's role change as PAT takes on more work?

No. Every clinical decision stays with the pharmacist for every workflow. PAT works ahead of pharmacist verification, never around it, and every action is logged with the logic it applied.