- Pharmacies use dedicated systems for dispensing, claims, inventory, scheduling, payroll and payments. Each does its own job, and that is a strength.
- Connecting those jobs, by noticing, following up, handing over and remembering, tends to stay with people. We call this the work around the systems.
- Our hypothesis is that much of the operational burden may sit in that coordination rather than in any broken process. More software is not automatically the answer, and could make it worse.
Specialized systems are a strength
A dispensing system should be excellent at dispensing. A payroll system should be excellent at payroll. An inventory system should be excellent at inventory. Independent pharmacies already rely on technology like this for the most important parts of the business.
We don't start from the idea that these systems should be replaced, or merged into one very large application. Our question sits somewhere else.
Work that no single system owns
However good each system is, the pharmacy still has to operate around them. Someone notices that a refrigerator is due for service. Someone makes sure a recurring duty was done, follows up with a vendor, gets a new employee ready, updates a procedure, or remembers what happened last time the same problem appeared.
Much of this work crosses boundaries:
- a task that starts in one system and needs action in another;
- an issue that one person notices and another has to follow up;
- a piece of equipment whose service record lives in one place while the reminder to check it lives on a calendar;
- a procedure stored on a shared drive, while the knowledge of when to use it lives with an experienced team member.
None of these arrangements is inefficient by itself. Together they add a layer of work: the work around the systems.
The cost may be coordination
Operational burden doesn't always show up as something broken. Often the work gets done precisely because someone is paying close attention. A manager remembers the deadline. A technician knows whom to call. The pharmacist spots the issue that keeps coming back. Someone checks the spreadsheet because they know it needs checking.
The pharmacy succeeds because people make up for the gaps between tools, responsibilities and information. That suggests a distinction worth testing:
A process can work and still take a great deal of coordination to keep working.
The cost appears as following up, searching, checking, asking, reconciling, and keeping a mental list of what mustn't slip. Each of these looks small on its own. As an operation grows more complex, the coordination itself may become substantial work.
Handoffs are often where it happens
We are increasingly interested in what happens between systems and between people. A system can record that something happened; that doesn't say what happens next.
- Who owns the follow-up?
- How does someone else know it is waiting?
- Where is the history if the issue comes back?
- What happens when the person who usually remembers is away?
- Of many small responsibilities, which needs attention today?
These aren't questions about whether a pharmacy has enough software. They are questions about continuity and visibility. The handoff, from information to responsibility, from issue to action, and from one person to another, may be where a large share of operational friction lives.
More software is not automatically the answer
It would be easy to conclude that pharmacies simply need another application. We don't think that conclusion should be assumed. A new system that adds another place to check, another sign-in, another duplicate record or another administrative step could make the problem worse.
Anything new would have to reduce coordination, not add to it. That means understanding what belongs in the specialized systems, and where a reminder, a shared view or clear ownership would be enough. We are just as interested in evidence that a current approach works well and shouldn't change.
What we're looking for
In our conversations with independent pharmacy teams, we look for the places where people have built their own spreadsheets, checklists, calendars, binders, databases, reminders and routines, and for the reasons those exist. The question we try to ask isn't how a piece of work could be moved into software. It is:
What is the pharmacy trying to accomplish here, and does the current way of managing it cost enough to justify a different one?
Our working hypothesis
There appears to be a layer of pharmacy operations that sits across specialized systems rather than inside any one of them. It spans our four areas of research: operational work and coordination, equipment and records, quality and readiness, and operational capacity.
We are still testing that. One question keeps guiding the work: at what point does managing the work around the systems become work in its own right?
Method, evidence and limits
- Type
- Research Note: analysis. It sets out a question and a hypothesis; it doesn't report measured findings.
- Based on
- Conversations with independent pharmacy teams and the experience of the Rx Process team. No survey data.
- Examples
- Illustrative. They describe common situations and are not drawn from any named pharmacy.
- Limits
- Not representative of independent pharmacies. Whether coordination is a meaningful burden, and for which pharmacies, is what our survey program sets out to measure.
Rx Process Research is part of Rx Process LLC, which makes software for pharmacy operations, and this note informs that work. An earlier version appeared on rxprocess.com as "Note 02". Rewritten in the Research Note format in November 2026. This version drops the description of Rx Process product areas, which belongs on rxprocess.com, and frames the hypothesis around the four areas of research.