Value-Based Care and Community Pharmacy: Where the Evidence Supports Participation

Value-based care can sound like an invitation for every community pharmacy to become a care-management organization. It is not. A credible opportunity begins with a specific arrangement, a defined population, a measurable service, reliable data, accountable partners, and a financial model that survives the work required to deliver it.

Answer first: an independent pharmacy should participate only after it can describe the contract or pilot in plain language: which patients are included, what service is expected, what measure is used, where the data come from, who owns each handoff, how performance is validated, and how payment works. CMS value-based programs provide policy context, but a pharmacy should not assume that a broad national program creates a direct community-pharmacy opportunity.

This article is general business and operational education, not legal, financial, or payer-contract advice. Review any arrangement with qualified counsel, an experienced reimbursement adviser, and the relevant payer or partner documentation before committing resources.

Contents

• Define the arrangement
• Where evidence supports participation
• Test the data and measure
• Model the operating work
• Build a conservative economic case
• Set governance and boundaries
• Go/no-go checklist
• FAQ

Key takeaways

• “Value-based care” is not a payment term until the parties define the service, population, measure, and payment trigger.
• Do not accept a performance target before verifying the denominator, exclusions, data lag, attribution, and dispute process.
• Start with a service the pharmacy can operate consistently, such as a defined outreach, transition, adherence, or clinical-support workflow.
• Model staff time, technology, documentation, billing, and escalation work before calculating potential revenue.
• Use a written governance process for privacy, clinical boundaries, reporting, and exceptions.

Define the arrangement before calling it value-based

CMS describes a range of value-based programs and innovation models across the health system. Those programs are important context for how purchasers and providers think about quality, cost, and accountability. They do not mean that an independent pharmacy automatically participates, receives shared savings, or is responsible for a measure. A pharmacy owner should start with the actual offer: a payer contract, network program, care-partnership proposal, employer arrangement, grant, or pilot.

Ask for the written terms and translate them into operational questions. What population is attributed? Which service is required? Is participation voluntary? What constitutes a completed intervention? Which organization calculates performance? Is payment fee-for-service, per-member-per-month, milestone-based, quality-contingent, shared savings, or another structure? Are there withholds, clawbacks, audit rights, or minimum-volume conditions? A verbal assurance that “the pharmacy will be rewarded for outcomes” is not enough to staff a program.

Separate a quality objective from a contractual obligation. A pharmacy may choose to improve refill follow-up, immunization outreach, or medication reconciliation because it supports patients. That does not itself make the activity a value-based arrangement. Conversely, a contract may include an operational service requirement without proving that the service improves every clinical outcome. Precise language keeps expectations realistic.

Where evidence supports participation

The best starting point is a narrow problem that the pharmacy can observe and influence. Examples may include an incomplete medication list after a transition, an unaddressed refill barrier, an overdue preventive-service prompt, or a patient who needs a pharmacist-led education or referral path. The service should have a defined action, qualified staff, escalation route, documentation standard, and appropriate patient communication. Avoid a broad promise to “improve adherence” or “reduce total cost” without a measurable, supportable mechanism.

Evidence supports using structured processes and measurement, but it does not justify a guarantee that one pharmacy program will change utilization, clinical outcomes, or plan spending in a particular population. Patient outcomes are affected by prescribers, caregivers, coverage, access, social conditions, clinical complexity, and the patient’s own decisions. The pharmacy’s contribution should be described accurately: identify a need, provide an authorized service, document the action, and coordinate the next step.

Test the data and measure

A measure is usable only when the pharmacy can understand it. Obtain the written definition, eligible population, exclusions, measurement period, source data, refresh schedule, calculation method, attribution rules, and dispute or correction path. If a payer uses a proprietary measure, ask for enough documentation to understand what the pharmacy can influence and how a completed service will be recognized. Do not sign up for a score that cannot be audited or reconciled.

Data lag deserves special attention. A pharmacy may complete a service today while a payer report updates weeks later. A patient may obtain medication elsewhere, change plans, move, be hospitalized, or have a therapy change. These events can affect a metric without indicating that the pharmacy failed. Create a reconciliation process that preserves the pharmacy’s own contemporaneous record and compares it with partner reporting without altering patient documentation to match a dashboard.

CMS publishes quality-measure and value-based-program materials that can help owners understand the importance of specifications and data governance. The contract or program documents, however, determine the pharmacy’s actual obligations. A national measure name does not prove that a local payer uses the same numerator, denominator, exclusions, or reporting period.

Model the operating work

Map the real workflow before accepting a target. Who receives the eligible-patient list? How are patients contacted? What information can staff discuss? Which steps require a pharmacist? What happens when the patient has a clinical question, coverage barrier, prescriber change, or urgent concern? How are results documented and sent to the partner? Who closes the loop? A program that depends on undocumented overtime or one highly experienced employee is not ready to scale.

Build exception paths from the beginning. An unreachable patient, inaccurate contact file, therapy discontinuation, language need, caregiver question, delivery barrier, clinical escalation, and data mismatch are not failures of the program. They are expected conditions that need an owner and a documented disposition. Review recurring exceptions to decide whether the service design, staffing, partner data, or contract needs adjustment.

Build a conservative economic case

Model direct and indirect costs: pharmacist and technician time, training, documentation, technology, data integration, outreach, supplies, privacy controls, quality review, management, and any partner reporting. Then model payment conservatively. Do not count contingent incentives as guaranteed revenue, and do not assume a quality bonus will cover an unpriced clinical service. Include a scenario in which the pharmacy performs the work but the partner data do not show the expected result.

Start with a limited pilot when the arrangement permits it. Define a population cap, duration, workflow, measures, reporting cadence, cancellation or exit rights, and review point. A pilot is useful only if it creates evidence for a decision; it should not become an indefinite unpaid service while the pharmacy waits for a partner to clarify data or payment.

Decide what the pharmacy will not do

A launch plan should include explicit exclusions. The pharmacy may decide not to make treatment recommendations outside the applicable protocol, not to perform services without a documented compensation path, not to use unverified contact lists, not to accept retrospective measure changes without review, and not to take on obligations that require technology or staffing it does not have. These limits are not a lack of commitment to patients; they make the service more likely to remain reliable for the patients it can serve.

Use a staged staffing plan. During a pilot, designate a small trained team, document time by task, and review the exceptions that force pharmacist involvement. If the service expands, decide whether tasks can safely be standardized, whether a technician role is permitted and trained for the work, and whether pharmacist coverage remains sufficient for clinical questions. A program that treats clinical escalation as an interruption will eventually either delay patients or push staff beyond their role.

Partner communication should follow the same discipline. Establish who receives routine reports, who can answer a data question, who authorizes a workflow change, and who can make a contractual representation. Request written confirmation of material changes. A verbal discussion about a new target, a changed population, or a modified data file can have major operational consequences even when neither side intends to change the deal.

Review patient experience alongside performance

Patients experience a value-based workflow as calls, messages, counseling, referrals, refill discussions, or help navigating a barrier. Invite feedback through an approved, limited channel and examine complaints or opt-outs with the same seriousness as a missed metric. A program that produces a favorable report but confuses patients, duplicates prescriber work, or creates unwanted contact is not demonstrating durable value.

Assess equity and access in the workflow. Check whether contact methods work for people with language needs, disability accommodations, limited transportation, limited digital access, or caregiver involvement. The pharmacy may not be able to solve every access barrier, but it can avoid designing a service that assumes every patient can use the same portal, phone number, pickup schedule, or communication style. Document what the pharmacy can offer and identify referral paths for needs outside its service.

Keep the pilot review evidence-based. Compare the initial assumptions with actual completed work, patient responses, data discrepancies, staff time, and payment. If the program did not meet a target, determine whether the issue was eligibility, workflow execution, partner data, population complexity, or an unrealistic design. Do not rewrite the historical record to make the pilot look successful. A transparent negative finding can prevent a larger investment in an unworkable arrangement and can inform a better scoped future proposal.

Document the decision after the review. The pharmacy may continue, expand, pause, renegotiate, or close the arrangement. Record the evidence used, the unresolved risks, and the person accountable for the next decision. This closes the loop for the owner and prevents a pilot from quietly becoming a permanent service without a current assessment of patient benefit, staffing capacity, or financial sustainability.

When an arrangement is expanded, repeat the readiness review rather than assuming that a small pilot scales linearly. A larger population may change call volume, clinical escalation frequency, data reconciliation, partner reporting, inventory needs, and management oversight. Growth should be an intentional operating decision supported by current evidence and written responsibilities.

Set governance and boundaries

Use a written governance process. Assign an executive owner, operational lead, pharmacist lead, data owner, and contract reviewer. Keep approved protocols, partner contacts, data definitions, privacy requirements, staff training, escalation routes, and monthly review records in a controlled location. Clarify what the pharmacy may represent to patients and providers, particularly when it is acting on behalf of a plan or partner.

Protect clinical and legal boundaries. Do not turn a performance target into individualized advice or pressure a patient to accept a refill, vaccine, service, or therapy. Do not represent an outcome as caused by the pharmacy without appropriate evidence. If the arrangement raises issues about scope, referral relationships, data use, compensation, or patient inducement, obtain qualified legal review before launch.

Value-based care go/no-go checklist

1. Obtain the written arrangement and identify the actual population, service, measure, and payment trigger.
2. Verify measure definitions, data sources, lag, attribution, exclusions, and dispute rights.
3. Map the workflow, staffing, documentation, escalation, and partner handoffs.
4. Model conservative costs and contingent payment scenarios.
5. Define privacy, clinical, communication, and legal boundaries.
6. Start with a bounded pilot when possible.
7. Review exceptions, data discrepancies, and patient experience regularly.
8. Exit or renegotiate if the program cannot be operated safely and transparently.

Frequently asked questions

Does a CMS value-based program automatically include community pharmacies?

No. CMS programs provide policy context, but participation and payment depend on the specific program or arrangement and its written terms.

What is the first document an owner should request?

Request the full written program or contract description, including measure specifications, data rules, payment terms, privacy obligations, and escalation contacts.

Can a pharmacy guarantee that a value-based program will reduce costs?

No. A pharmacy can define and document its services, but cost and clinical outcomes depend on many factors beyond one workflow.

Conclusion

Value-based care is a disciplined operating decision, not a marketing label. The right opportunity gives the pharmacy a clear role, credible data, workable economics, and patient-safe boundaries. For a related operational view of measuring pharmacy services, see Dispense Times’ medication-adherence measurement framework.

References

1. Centers for Medicare & Medicaid Services. Value-Based Programs. Accessed July 19, 2026. CMS.
2. Centers for Medicare & Medicaid Services. Innovation Models. Accessed July 19, 2026. CMS.
3. Centers for Medicare & Medicaid Services. Measures Management System. Accessed July 19, 2026. CMS.