Note 01
A question about the systems, routines, and people behind the day-to-day operation of an independent pharmacy.
A pharmacy can tell you where prescriptions are processed.
It can tell you where claims are submitted, where inventory is managed, where schedules are maintained, and where financial information is recorded.
But ask a different question:
Where does pharmacy operations live?
The answer may be less obvious.
There is a layer of work inside every pharmacy that exists around the primary work of filling prescriptions and caring for patients. It is the work required simply to keep the operation functioning.
Someone needs to know when equipment requires service.
Someone needs to remember a recurring responsibility.
Someone needs to follow up when something goes wrong.
Someone knows which vendor to call.
Someone knows that a particular task happens every month, even if it is not written down anywhere.
Someone remembers what was tried the last time a problem occurred.
In many pharmacies, these things are managed perfectly reasonably. There may be a spreadsheet, a calendar reminder, a binder, a checklist, an email folder, a shared drive, or a piece of software that handles a particular part of the work.
And often, there are experienced people who simply know how the pharmacy runs.
None of those things is inherently a problem.
The interesting question is what happens when they exist together.
The pharmacy already has systems
Technology is not foreign to pharmacy.
Modern pharmacies depend on sophisticated technology to dispense medications, adjudicate claims, manage inventory, communicate with patients, coordinate clinical services, process payments, and perform many other functions.
The question is not whether pharmacies need more technology.
The question is whether there is a part of the operation that existing technology does not naturally bring together.
Consider the operational information surrounding five areas:
People
Who is responsible for what?
Operations
What needs to happen, when does it need to happen, and who owns it?
Quality
What happened, how was it addressed, and is the problem recurring?
Assets
What equipment and operational resources require attention, maintenance, documentation, or service?
Insights
Across all of this, what actually requires management attention today?
Each piece may already exist somewhere.
The challenge is that somewhere may be several different places.
Fragmentation can work
This distinction matters.
A fragmented operating model is not necessarily a dysfunctional operating model.
People are remarkably good at creating ways to make organizations work.
A pharmacy manager may have developed a spreadsheet that has been used successfully for years. An employee may maintain an excellent checklist. A calendar reminder may reliably trigger a quarterly responsibility.
The pharmacy operates.
But over time, another question becomes relevant:
How much of the system depends on people remembering how the system works?
That is different from asking whether the work gets done.
When operational knowledge is distributed among individual people, documents, calendars, inboxes, and systems, the people running the pharmacy often become the integration layer themselves.
They know where to look.
They know whom to ask.
They know what needs to happen next.
They know when something does not look right.
In effect, the manager can become the operational dashboard.
Complexity changes the equation
For a very small operation, this may be entirely manageable.
But complexity accumulates.
More employees. More services. More equipment. More vendors. More locations. More regulatory obligations. More recurring responsibilities.
And more things that can be forgotten, delayed, duplicated, or misunderstood.
This raises a hypothesis we believe is worth investigating:
As pharmacy operations become more complex, the cost of managing operational information across disconnected places increases.
We do not assume this is equally true for every pharmacy.
That is precisely why we are asking.
What would a connected approach look like?
Rx Process began with the idea that the operational side of pharmacy may deserve a system of its own.
Not another dispensing system.
Not another clinical platform.
And not technology for technology’s sake.
Rather, a lightweight operational layer that helps connect the people, operations, quality, assets, and information required to keep a pharmacy running.
The goal would not be to replace every tool a pharmacy already uses.
It would be to make the operation easier to see.
What needs attention?
Who owns it?
What happened previously?
What is coming next?
What does the pharmacy depend on that currently lives primarily in someone’s memory?
Those are the questions we are exploring.
We are starting by listening
Rx Process is currently working with independent pharmacy teams to understand how the operational side of their pharmacies actually works.
We are particularly interested in the informal systems – the spreadsheets, binders, calendars, checklists, conversations, routines, and institutional knowledge that rarely appear on a software diagram but often make the business function.
Some of our assumptions will probably be correct.
Others probably will not be.
That is part of the process.
Before deciding what pharmacy operations software should look like, we think it is worth understanding something more fundamental:
Where does pharmacy operations live today?
End of Note 01