The end of a conversation is easy to identify. The end of the work can be less clear. A professional may have completed a review, documented their decision and assigned a further action, while the note still needs to reach the practice record. One completion marker cannot describe all of those facts accurately.
Medication review is a wider process than collecting answers. NHS England's SMR overview describes multidisciplinary support for the review process and follow-up. For the surrounding operational workflow, it helps to make each responsibility and handover visible.
1. Give each state a precise meaning
Agree what the team means by collected, reviewed, exported, filed and closed. Collected describes the information-gathering stage. Reviewed describes a professional decision. Exported describes an output being prepared. Filed describes an acknowledged record handover. Closed describes the agreed work being resolved.
These states may happen at different times. A case can be reviewed and filed while a further action remains open. It can also have a resolved action while the filing step needs attention. Let the screen show both situations without forcing the team to choose a misleading overall label.
2. Make follow-up an owned piece of work
A useful follow-up record explains what needs to happen, who is responsible and when it should be reconsidered. Its wording should be specific enough for another authorised colleague to understand. The clinical content and urgency remain matters for the responsible professional and local process.
Record a change of owner explicitly. When somebody completes the action, retain the outcome and the person recording it. If the action cannot be completed, keep the unresolved state visible and record the next agreed step rather than closing it to tidy the list.
A useful question: if the original reviewer is unavailable tomorrow, can the next person identify the outstanding action and who is expected to take it?
3. File the current reviewed version
A note may change during review. Make its version and approval state visible so that an older export cannot be mistaken for the current record. The filing acknowledgement should refer to the reviewed version that was actually handed over, with an appropriate reference for the method used.
Downloading a document is not proof that it was filed. Nor does an export establish a working connection to a clinical system. Where the process is manual, describe it as manual and ask for the agreed acknowledgement. Where an integration is proposed, verify its contract, authority, failure behaviour and acceptance before relying on it.
4. Expect interruptions and uncertain outcomes
A save can be interrupted by a connection problem or an expired session. The user needs to know whether the action is confirmed, unsuccessful or still uncertain. Retain enough context to check the result before repeating it. A generic success message should never stand in for a verified acknowledgement.
Rehearse what happens if a note is amended after export, if filing fails, or if the wrong revision is selected. Check that the current reviewed version stays clear and that the action history remains understandable. Keep the actual follow-up state separate throughout these exercises.
Also consider the person receiving the work. A handover is incomplete if a task has an owner in name only, with no practical way for that person to see and manage it. Agree responsibility and visibility together.
5. Report facts that lead to action
Useful reporting separates reviews awaiting attention, notes awaiting filing and open follow-up. It should help a team decide where to look next. Counts need clear definitions, particularly when one case appears in more than one queue. Avoid adding unlike statuses together and calling the result completed reviews.
Hannah Health's local workflow keeps reviewed notes, filing acknowledgements and follow-up closure separate. Manual reviewed-note export is the current development route; a presumed connection to an EHR is not part of that claim. Production integration and patient-use acceptance remain separate work.
Explore the product workflow and the oversight approach, or return to the complete workflow guide. These operational suggestions support local process design; they do not replace professional judgement or your organisation's approved policy.