The Hidden Work Behind Medication Regimen Review

The hidden work in medication regimen review is everything a consultant pharmacist does around the clinical judgment itself: locating current resident context, comparing the regimen to the prior cycle, deciding whether a concern is new or recurring, documenting the reasoning, routing the recommendation to the right person and tracking what still needs follow-up. None of it appears in the definition of an MRR, most of it is never measured, and it consumes real time in every monthly cycle. Reducing it is a workflow design problem, not an alerting problem.

The review is one visible task inside a larger, invisible workflow

Medication regimen review is often described as a defined clinical task: evaluate the resident's regimen, identify concerns and make recommendations. That description is accurate, but incomplete.

Around the clinical review sits a second layer of work that is less visible and more fragmented. Before any judgment can be applied, the pharmacist has to find the current medication list, confirm what changed since last month, check whether a flagged issue was already addressed, and decide whether it is worth raising again.

That surrounding work rarely shows up in productivity measures. A pharmacy tracks residents reviewed and recommendations written. It does not usually track the fifteen minutes spent reconstructing a resident's situation before the first clinical thought is possible. Because it is unmeasured, it stays invisible, and invisible work never gets designed out.

MRR is recurring, not a one-time event

Consultant pharmacists do not encounter a resident's regimen once. They return to it, month after month, often for years. That recurrence changes the design problem entirely.

A workflow built for a single snapshot captures what the pharmacist found today. A workflow built for a recurring practice has to carry history forward: what was considered, what was recommended, how the facility and prescriber responded, and what remains unresolved.

When that history lives across handwritten notes, a spreadsheet, a portal and memory, the pharmacist rebuilds the situation before doing any clinical thinking. Multiply that by a census of a hundred or more residents and the cost is not marginal. It is a meaningful share of the month.

What counts as a completed review matters more than it sounds

There is a quiet measurement problem underneath all of this. If a resident is treated as reviewed simply because someone opened the chart, the number overstates how much clinical work actually happened.

A more honest definition ties review status to documented review activity inside the cycle. In Pharmacore, a resident counts as reviewed for a window when there is review activity in that window, such as a recommendation created during the period or an outcome recorded against one, rather than a chart-open timestamp alone.

That distinction is not academic. It changes what a completeness report means. It also makes the residual list useful: residents who were genuinely reviewed but produced no recommendations are a different population from residents nobody has touched yet, and a pharmacy manager should be able to tell them apart before the month closes.

Handoffs are where clinical work quietly stalls

A recommendation has to travel. It moves from the pharmacist to the facility, and often on to a prescriber. The clinical reasoning behind it does not automatically travel with it.

So the open questions pile up. Has the recommendation been sent? Has the prescriber responded? Does the change need monitoring? Should the issue reappear at next month's review if nothing happens?

These are workflow questions, not clinical ones, but they decide whether clinical work stays visible or disappears. A single disconnected note or a faxed page cannot answer any of them, so the pharmacist ends up maintaining a private tracking system on the side. That side system is pure hidden work, and it is the first thing lost when a resident transfers between pharmacists.

More alerts is not the same as less hidden work

The instinctive fix is to generate more automated findings. It rarely helps. A longer list of alerts without context simply becomes another review task layered on top of the original one, and the pharmacist still has to reconstruct why each item appeared.

Decision support becomes useful at the moment it lets the pharmacist inspect the basis for a suggestion and decide what to do with it. Every AI-generated recommendation needs a real accept, modify or reject step, controlled by the pharmacist.

Structure matters here too. Pharmacore presents AI recommendations for review in cards organized by category, with tabs and filters so the pharmacist can work through one class of issue at a time instead of scanning an undifferentiated queue. The review surface can also be detached into its own window, so the pharmacist can keep the recommendation list open beside the resident's chart rather than jumping back and forth between views. The same pattern applies to labs and orders.

The point is not volume. The point is that the pharmacist should spend attention on the decision, not on figuring out what the software was looking at.

Documentation should stay attached to the medication it concerns

Recommendation text that refers to a drug by name alone leaves room for ambiguity. Which order? Which dose? The one that was discontinued last cycle, or the current one?

Pharmacore lets the pharmacist reference a medication directly while writing the recommendation, so the documentation is bound to the specific medication on the regimen rather than to a string of text. When exactly one medication is resolvable, the recommendation links to it directly; when a recommendation covers several drugs, as with an interaction or a whole-regimen concern, the medications are carried as a list instead of being forced into a single link.

The payoff arrives later. When someone reopens the recommendation history, or looks at how many recommendations a given medication has attracted over time, the trail is traceable without anyone re-reading free text to work out what was meant. That is reconstruction work removed rather than relocated.

Recurring reviews need purpose-built views, not general-purpose ones

Some parts of the monthly cycle repeat in a predictable shape and deserve a dedicated view. Psychotropic review is the clearest example, because it is both high-scrutiny and inherently longitudinal. The question is almost never just what the resident is on today. It is what the dose has been doing over recent months.

Pharmacore includes a psychotropic worksheet with search, column ordering and month selection, a dose trend view for individual medications and an export to xlsx for facility documentation. It is a small thing described in a sentence, and it removes a recurring assembly job that many pharmacists still do by hand in a spreadsheet each cycle.

Designing for the practice, not only the screen

We are building Pharmacore around the idea that AI-powered clinical intelligence and practice workflow belong together, not as two tools that happen to be open at the same time.

Pharmacore is clinical decision support software for consultant pharmacists in long-term care, designed to support the review, the documentation and recurring follow-up in one pharmacist-controlled experience.

That does not make software the decision-maker or the authoritative clinical record. It gives professional judgment a clearer place to work and a better way to carry forward. The consultant pharmacist stays accountable for the recommendation. The system's job is to stop making them rebuild the context first.

This category has not moved much in a long time. The incumbent tooling most consultant pharmacists learned on, RxPertise, dates to 1996, and a lot of daily practice still runs through desktop-era screens, spreadsheets and paper. There is nothing wrong with software that lasted thirty years. There is something wrong with a profession still paying a reconstruction tax that modern software has no reason to charge.

A question worth asking about your own workflow

Which part of medication regimen review requires the most reconstruction in your practice? Finding current context. Comparing with the prior review. Documenting the recommendation. Tracking the response. Remembering what should return next month.

Pick one. That answer is where workflow design should begin, and it is a better starting point for evaluating any tool than a feature list. If you want to walk through the workflow in more detail, you can request a product conversation, or browse more of our writing in Resources.

Frequently asked questions

What is the hidden work in medication regimen review?

It is the non-clinical effort around the review itself: locating current resident context, comparing against the prior cycle, deciding whether an issue is new or recurring, documenting the reasoning, routing the recommendation to the right person and tracking what still needs follow-up. It is rarely counted, but it consumes real time every cycle.

Why should MRR be treated as a recurring workflow instead of a single task?

Because consultant pharmacists revisit the same resident month after month. A workflow that does not preserve what was considered, recommended and resolved forces the pharmacist to rebuild the situation from scratch before applying judgment. That rebuilding is where hidden work accumulates.

Does adding more automated alerts solve the hidden-work problem?

No. An alert without context is just another task to review. Decision support is only useful when the pharmacist can inspect the basis for a suggestion and choose to accept, modify or reject it. A longer list of findings without that step increases the workload rather than reducing it.

How should a facility know whether a resident's review is actually complete for the month?

Base it on documented review activity inside the cycle, such as a recommendation created during that window or an outcome recorded against one, rather than on whether a chart was opened. Pharmacore uses that activity-based definition, which makes completeness reporting reflect clinical work rather than access.

What does Pharmacore do differently around this hidden work?

Pharmacore is clinical decision support software built for consultant pharmacists in long-term care. It supports the review, the documentation and recurring follow-up in one pharmacist-controlled experience, with an explicit accept, modify or reject step on AI recommendations, recommendations linked to the specific medications they concern, and purpose-built views such as the psychotropic worksheet. It does not replace the pharmacist's judgment or act as the authoritative clinical record.

Who should read this, and what should they do next?

Consultant pharmacists, LTC pharmacy owners and directors of nursing who want to find where their own review workflow fragments. Identify your single biggest reconstruction point first, then book a product conversation to see how that step could work differently.

About the author

Tim Merritt (PharmD, RPh)

Tim Merritt is a co-founder of Pharmacore and a consultant pharmacist. He brings clinical practice and product perspective to the company, which he founded and built with Adam Brown and Dave Robbins.