Status first: advocacy moved; payment policy did not
On May 21, ASCP called for congressional action to expand Medicare coverage of pharmacist services. The verb matters: ASCP advocated. The update did not itself enact legislation, revise a reimbursement rule, publish implementation guidance, or establish payer behavior. Each of those would be a separate event with its own date and scope.
Track the issue through official legislative and payer channels without ignoring it or booking it as revenue. Any billing claim or service plan must rest on the requirements currently in force and confirmed for that payer and arrangement. This article is not legal, reimbursement, or billing advice.
The source also has a defined role. ASCP's notice is useful evidence of the association's position and the action it requested. It is not the legal authority for a coverage rule, evidence that Congress acted, or confirmation that a payer will reimburse a particular service. Keep that attribution attached whenever the update is summarized for a partner, forecast, or planning document.
Keep a status record that survives the next headline
A small policy log prevents an advocacy update, bill, rule, and payment instruction from blending together over time. Use one row for each development and preserve the source that supports it. The record does not need to be elaborate; it needs to make the current effect and the next verification step unmistakable.
- Source and date: Link the original document and record when it was published and checked.
- Actor: Name who spoke or acted—an association, legislator, agency, payer, contractor, or another body.
- Action: Use the source's verb, such as advocated, introduced, passed, finalized, implemented, or instructed.
- Current stage: Record whether the item is a position, proposal, legislative action, final policy, guidance, or payer-specific direction.
- Operational effect: State what changes today, if anything, and which practice, service, payer, or setting is within scope.
- Next check: Name the official source, decision, date, or implementation document that would justify updating the record.
Preparation can be useful without assuming an outcome
Whatever Congress does next, a defined service is easier to explain, price, and inspect. Record the population, review trigger, available interventions, recommendation recipient, outcome definition, and follow-up method. When those facts are split across reports, email, and calendars, it is difficult to describe the service accurately or improve it consistently.
Software is relevant only to the extent that it preserves the necessary evidence: perhaps a structured recommendation, an audience-specific report, a worklist of unresolved items, time associated with an activity, or a facility export. That does not prescribe one platform for every practice, and it does not create coverage. It makes the service actually being delivered easier to run and examine.
Keep four different claims in four different boxes
A policy proposal, an advocacy position, a vendor capability, and a billable benefit are not interchangeable. Until the relevant payer and regulatory requirements are in place, describe the current service, the documentation it creates, and the rule or contract that supports payment today—no more and no less.
When a vendor demo emphasizes claims, billing, or documentation, ask which part is workflow support and which part is a reimbursement assertion. Require the authority, effective date, payer, eligible billing entity, and conditions behind the latter. Software alone cannot supply them.
Before changing a service description, contract assumption, or forecast, recheck the official authority that would make the change real. Record who is eligible, what service is covered, which documentation is required, when the policy takes effect, and what exclusions or overlap rules apply. If any of those remain unknown, label the issue pending instead of filling the gap with the advocacy language.