Medication review work can move between lists, conversations, notes and follow-up queues. Each handover is an opportunity to lose context: why the person was selected, which questions remain unanswered, or whether a requested action has an owner. Making those transitions explicit gives a team a clearer starting point for improving its process.
A structured medication review is a clinical conversation. NHS England describes clinicians and patients working as equal partners, considering the person's needs, preferences and circumstances. Organising the surrounding work should support that relationship. Collecting information does not, by itself, complete a review.
1. Define what the team is trying to complete
Start with the purpose, the people involved and the limits of the workflow. Agree how a cohort is chosen, who checks its source and who can authorise the work. Record the practice context and the version of the questions or protocol being used. A recognisable name is useful; a clear scope is more useful.
Give each stage its own completion condition. For example, preparation may be complete when the source is checked and responsibility is assigned. Collection may be complete when the agreed questions have been addressed or their missing states recorded. Clinical review requires a separate professional decision.
2. Prepare for exceptions before the conversation
A workflow needs a route for people who cannot, or do not wish to, use the expected channel. Decide how a communication need, an uncertain identity, a request to stop or a requested callback reaches a person who can respond. Use the organisation's approved wording and processes, rather than treating a successful technical connection as permission to proceed.
Keep the handover actionable: what happened, what needs attention, who owns it and when it should be reviewed. A generic warning can be easy to overlook. An owned task makes the next step easier to find without suggesting that the software has resolved the issue.
3. Keep collection, evidence and judgement separate
Information collection establishes what was said or supplied. Evidence preparation preserves the source and relevant context. Professional review interprets that information alongside the wider clinical picture. These are related activities, but they should not collapse into one status called complete.
Retain unanswered, declined and unclear responses as distinct states. An empty answer is not a negative answer. If a summary is created, make it possible for the reviewer to check the source and correct an interpretation. Record the reviewed decision separately from the original material.
A practical test: could a colleague explain why a case has reached its current stage without asking the person who last worked on it? If not, the handover needs clearer evidence or ownership.
4. Show the work that remains
A review may produce a note and one or more follow-up actions. Give those actions their own owners and states. Filing a note should not silently close an unresolved action; closing an action should not imply that the right version of the note has reached the practice record.
Report distinct facts: collected information, reviews awaiting professional attention, reviewed notes, filing acknowledgements and outstanding follow-up. Keep exceptions visible alongside ordinary progress. If a case is held, the team should be able to see the reason and the route back into work.
5. Evaluate the whole journey
Rehearse a normal case and several incomplete cases before judging the workflow. Include a declined answer, a communication need, a callback and a filing problem. Follow each through to its actual resolution. A polished dashboard cannot establish that every handover works.
Measure staff effort separately from elapsed time and transport duration. Record what the measurement includes, then compare like with like. A forecast can help plan an evaluation, but it is not a demonstrated saving.
Hannah Health is being developed around these distinctions. Its local evaluation workflow covers preparation, evidence, professional review, reviewed notes and separate follow-up. Patient use, production integrations and clinical acceptance require further approval and validation. Explore how the workflow is organised or read the current oversight approach.
Continue reading
Evidence that supports clinical judgement looks more closely at provenance and uncertainty. Follow-up and filing explains why the final handovers need separate records.