What changed—and what did not
ASCP's May 21 update called for congressional action to expand Medicare coverage of pharmacist services. That is a policy-development signal, not a reimbursement rule change. There is a wide distance between a bill, an advocacy campaign, a legislative vote, implementation guidance, payer behavior, and the actual payment rules a practice can rely on.
The sensible response is neither to ignore the signal nor to forecast it as revenue. Track the policy through official legislative and payer channels, and make sure any claims or service plans use current, confirmed requirements. This site does not provide legal, reimbursement, or billing advice.
The work worth doing before policy catches up
A service is easier to explain, price, and defend when its operating record is clean. Define the population, the trigger for a review, the interventions available, who receives the recommendation, what counts as an outcome, and how follow-up is documented. Many practices have parts of that information in separate reports, email threads, and calendars; a single view is much easier to improve.
Software helps only when it preserves the evidence you need. That might mean a structured recommendation, a report to a particular audience, a worklist of unresolved items, time associated with an activity, or an export for a facility. It does not mean every practice needs the same platform. It means the system should make the actual service easier to run and inspect.
Avoid a familiar compliance mistake
Do not describe a proposed policy, vendor feature, or care-management aspiration as a billable benefit before the relevant payer and regulatory requirements are in place. The safest language is precise: state what your current service does, what documentation you create, and what rule or contract supports payment today.
If a vendor demo emphasizes claims, billing, or documentation, ask the vendor to distinguish workflow support from a promise of reimbursement. The latter depends on much more than software.