A new review, with an older evidence window
Published in Digital Health on September 9, the scoping review searched literature from 2010 through March 27, 2025. Its 13 included studies were published between 2013 and 2023. The subject was medication records actively managed by patients or caregivers, using paper, apps, or electronic tools. This was a mapping of existing research, not a newly completed trial of consultant-pharmacist software.
The authors reported significant adherence improvements in three of seven studies and clinical improvements in two of four. Interventions and outcome measures varied, and some tools came with professional support or additional app functions. The authors did not undertake formal quality appraisal. Their findings cannot isolate the benefit of a list from the services surrounding it or establish effectiveness in U.S. nursing facilities.
Start with the copy that reaches the consultant
For a small consultant pharmacy practice, a useful purchasing question follows: when someone arrives with a medication list, can the review process establish what it represents? A printout may describe an earlier visit. A caregiver may have added information since then. An imported record may carry a recent transfer timestamp even though nobody has confirmed its contents.
The five checks below are our editorial acceptance questions, prompted by the review. They are not a validated assessment instrument, a clinical protocol, or features attributed to any reviewed vendor. Use de-identified purchasing examples and ask the demonstrator to carry the same example through each step.
Five checks to put in the demonstration
- 1. Identify the source and the last check. Ask the demonstrator to show who supplied the list, when it was received, and when its contents were last confirmed. Those dates should remain distinguishable after import. If the source or verification date is unknown, the record should make that uncertainty visible. A freshly generated PDF can still contain old information.
- 2. Follow a correction into every copy. Introduce a difference between the supplied list and the record used for review. Ask where the discrepancy is recorded, who is expected to resolve it, and how the resulting correction reaches the next export. Inspect whether the earlier value and reason for the change remain available. A silent overwrite makes the next conversation harder to reconstruct.
- 3. Test what the reader can understand. Examine the actual patient or caregiver view, including a printed version. Can a reader distinguish active entries from historical ones, recognize the schedule, and find the contact for questions? Ask how the practice would check understanding with its intended users. The demonstrator knowing where to click does not answer that question.
- 4. Take the list outside the application. Request the ordinary export and print it. Check whether long medicine names, directions, dates, and unresolved notes remain legible without clipped columns or unexplained abbreviations. Establish what the receiving person needs to open a digital copy and what happens when that access is unavailable. Record any extra license, manual re-entry, or separate portal step in the purchasing requirements.
- 5. Close the discrepancy loop. Leave one difference unresolved and move the example to the receiving professional. Ask how that person can find the question, respond, and see the answer return to the review record. Keep receipt, confirmation, and correction as separate events when the workflow needs them. A downloaded file alone does not demonstrate that anyone reviewed or acted on its contents.
Evaluate the work around the list
The review describes implementation barriers including limited digital literacy, unclear abbreviations, connectivity problems, and gaps in communication. That is a reason to include patient and caregiver access in the evaluation. It does not justify selecting a particular app or assuming that a paper copy will meet every need.
Keep the acceptance record concrete: the task attempted, the output inspected, the unresolved limitation, and the person responsible for checking it. Apply the same example to each shortlisted product. If a step depends on a separate system or a manual process, describe that dependency in the comparison so the practice can judge the whole workflow.
A patient-held list contributes information to medication reconciliation and review; its existence does not establish that either is complete. The immediate buying decision is whether the proposed process can preserve context and return corrections to the people who need them. Claims about better adherence or fewer adverse events require evidence for the particular intervention, population, and outcome being claimed.