Celebrate the milestone, then keep its scope clear
On May 11, ASCP said Consonus Pharmacy and Siler Pharmacy became the first pharmacies recognized through its Age-Friendly Pharmacy program. It is a welcome marker of a broader conversation in senior-care pharmacy: how to organize medication work around older adults and the people involved in their care, not merely record that a review happened.
The mark still needs boundaries. It is recognition through an ASCP program, not a blanket endorsement of every product, facility, pharmacist, or clinical decision involved. Nor can it make a software platform age-friendly by association. A tool may support a disciplined process; the people using it remain responsible for judgment, communication, and accountability.
A recognition announcement also cannot answer every diligence question for an outside reader. Before using the mark in a buying or partnership decision, ask for the current program materials, what the recognition covers, when it was assessed, and how its status is maintained. That is not skepticism for its own sake. It is how a useful signal stays connected to a defined scope instead of becoming shorthand for conclusions the announcement does not establish.
Let the signal improve the questions you ask
For a consultant pharmacist, the announcement is an invitation to inspect the space between a thoughtful review and an understandable operating record. Can the recipient follow the recommendation? Can the pharmacist find what is still open? Can a facility leader see a pattern without reading every report? Can a covering consultant understand why an earlier decision was made?
Those are warmer, more useful conversations than a generic feature checklist because they start with the people who need the record. The answers may lead to structured recommendations, follow-up states, psychotropic workflows, audience-specific reports, role controls, or a shared worklist—but only when a vendor can demonstrate the feature in the buyer's own use case.
- Resident or representative: Where can goals, preferences, and unresolved questions be recorded without being reduced to a checkbox?
- Consultant pharmacist: Which medication context, source date, reasoning, and next review point remain attached to the recommendation?
- Prescriber and facility team: Can each recipient see the requested action, record a response or rationale, and identify what happens next?
- Covering consultant: Can another authorized pharmacist reconstruct the history without relying on a private handoff or memory?
- Facility leader: Can a summary be reconciled to the individual records behind it without presenting a process count as a clinical outcome?
Test whether the record still makes sense to the next person
Age-friendly work crosses roles, and each person approaches the record with a different question. A consultant may need the clinical context; a director of nursing may need the requested action and timing; a prescriber may need the reason and available alternatives; a resident or representative may need a plain explanation of what is being considered. One long report can technically contain all of that and still leave everyone searching.
Use one synthetic or appropriately protected case to test the handoff. Ask each intended reader to find the current recommendation, response, rationale, unresolved question, and next owner. Note where they hesitate or reach different conclusions. The exercise does not prove that a workflow is age-friendly or clinically sound. It reveals whether the operating record supports a shared conversation rather than forcing every reader to reconstruct it alone.
Start with one care handoff, not a new shopping list
A small practice can begin before buying anything. Choose one recurring area of care—perhaps high-risk medications, anticholinergic burden, or psychotropic follow-up—and trace the handoff from observation to recommendation to response. Where does another person lose the thread? That break makes a better requirement than a long wish list.
If reporting is the gap, bring an actual facility packet to the next software conversation. If follow-up is the gap, ask to see open, deferred, and closed recommendation states. If coverage is the gap, test a realistic handoff between consultants. A careful pilot is less glamorous than a badge or polished demo, but it tells you more about the work.
Close the pilot with a short, honest record: what worked, what required explanation, what could not be demonstrated, and who will decide the next step. Recognition can open the door to that conversation. The evidence gathered in the practice's own workflow is what makes the conversation useful.