Pharmacy Operations Guide

Telepharmacy vs. Clinic-Partnered Remote Care

An operational guide for independent pharmacies choosing between remote dispensing and clinic-partnered care management

Both models use technology and pharmacist labor. They are not the same business. Telepharmacy is primarily remote dispensing under state board rules. Clinic-partnered remote care is a clinical services operating model tied to eligible billing practitioners.

Published: June 24, 2026

For Independent Pharmacy Owners and Operators

Important: This is operational guidance, not legal, coding, or billing advice. Confirm payer rules with the billing team and review pharmacy-clinic contracting with counsel.

The Decision

Choose telepharmacy when

The strategic goal is prescription access in a pharmacy desert or underserved geography.

Choose remote care when

The strategic goal is clinical services revenue and local clinic relationships between visits.

Near-term edge

For many independents, the faster path is becoming an operating partner for clinics running APCM, CCM, RPM, or RTM.

Key takeaways

Telepharmacy is remote dispensing

Telepharmacy can be valuable when the goal is remote dispensing access, especially in pharmacy deserts or underserved areas. It is state-specific, and state rules may address distance limits, pharmacist-to-site ratios, technician requirements, remote supervision, site licensing, inspection, and prescription volume.

Remote care is not remote dispensing

APCM, CCM, RPM, and RTM are Medicare Physician Fee Schedule services billed by eligible practitioners or entities when requirements are met. A pharmacy generally does not bill Medicare for these services as a pharmacy.

The workable model is clinic-pharmacy services

The clinic owns the patient relationship, billing decision, medical record, and supervision. The pharmacy supplies trained personnel and workflow capacity under the clinic's direction.

Compliance risk is real

Arrangements should be reviewed for Anti-Kickback Statute risk, state law, fee-splitting rules, licensure, scope of practice, and payer requirements. Compensation should be for bona fide services, not referrals.

The evidence trail is the operating core

Each month should produce consent evidence, care plan status, outreach logs, device data where applicable, time records where applicable, escalation notes, billing readiness checks, and an EMR-ready documentation snapshot.

Why this matters now

Independent pharmacy economics remain under pressure. NCPA’s 2025 Digest described independent pharmacy as a $103 billion marketplace in 2024, while reporting a 10-year high in cost of goods and a 10-year low in gross profits. It also pointed to high-cost and high-volume prescriptions, low or below-cost third-party reimbursement, inflation, wages, and overhead as persistent operating pressures.¹

At the same time, pharmacies remain one of the most reachable healthcare sites in the country. A nationwide JAPhA analysis found 88.9% of the U.S. population lived within 5 miles of a community pharmacy.² JAMA Network Open has also described community pharmacies as a major access point while noting that closures and pharmacy deserts create serious access problems.³

The strategic issue is that access does not automatically translate into payment. Medicare payment for APCM, CCM, RPM, and RTM generally flows through eligible billing practitioners or entities, not through a pharmacy simply because a pharmacist did the work.

Section index

Key takeaways
Decision point: telepharmacy or remote care?
Why telepharmacy is hard to scale
What remote care is instead
How a pharmacy fits
Operating model
What to have before launch
Recommended first month workflow
Common failure modes
What to save to the EMR
Minimal example
When this model is a poor fit
Where FairPath fits
Sources

Decision point: telepharmacy or remote care?

Question	Telepharmacy	Clinic-partnered remote care
Primary job	Remote dispensing access, counseling, and pharmacist supervision for a remote site or kiosk.	Between-visit clinical workflows that help a clinic run APCM, CCM, RPM, or RTM.
Rule set	State board of pharmacy rules, remote site licensing, technician rules, inspection, supervision, inventory, and prescription volume limits.	Medicare Physician Fee Schedule requirements, practitioner supervision, payer rules, medical record documentation, and contracting compliance.
Who controls billing?	The pharmacy dispenses under pharmacy law and existing prescription payment arrangements.	The clinic or eligible practitioner decides whether requirements are met and submits the claim when appropriate.
Best fit	Pharmacy deserts, underserved communities, and access-extension strategies.	Local clinics that need documented care management capacity between visits.

What makes telepharmacy hard to scale

Telepharmacy can be valuable when the goal is remote dispensing access, especially in underserved areas. The difficulty is that it is not one national model. A 2023 JAMA Network Open study reported telepharmacy was permitted in 28 states at the time and that rules varied across geographic limits, distance requirements, pharmacist-to-telepharmacy ratios, prescription count limits, and technician ratio or training rules.⁴

NABP has continued to discuss a movement toward less restrictive telepharmacy models and has published Model Act material that discourages unnecessary volume, mileage, and other restrictions. That does not replace state board rules. Before opening a remote dispensing site, an operator still has to confirm the current board requirements for site licensing, inspection, technician presence, remote supervision, counseling, controlled substance handling, and pharmacist coverage.⁵

For a single rural site, telepharmacy may be worth the licensing work. For a multi-clinic clinical services strategy, the state-by-state dispensing framework may be the wrong tool.

What remote care is instead

Remote care is not remote dispensing. APCM, CCM, RPM, and RTM are Medicare Physician Fee Schedule services billed by eligible practitioners or entities when requirements are met. A pharmacy generally does not bill Medicare for these services as a pharmacy.

APCM

Advanced Primary Care Management began January 1, 2025. CMS describes APCM as billable by physicians and certain non-physician practitioners responsible for primary care and serving as the continuing focal point for needed services. Codes G0556, G0557, and G0558 are billed once per patient per calendar month when requirements are met, with G0557 and G0558 tied to patients with two or more chronic conditions.⁶

Operational elements include consent, an initiating visit when required, 24/7 access and continuity, care management, an electronic patient-centered care plan, transitions, enhanced communication, population-level management, and performance measurement. Auxiliary personnel may help under general supervision, subject to requirements.

CCM

Chronic Care Management generally applies to patients with two or more chronic conditions expected to last at least 12 months or until death, or that create significant risk. Eligible practitioners bill CCM. Clinical staff may provide services under the practitioner’s direction on an incident-to basis, subject to state law, licensure, and scope of practice.⁷

The evidence trail usually includes an initiating visit for new patients or patients not seen in the prior year, consent, cost-sharing and duplicate-billing disclosures, and a comprehensive electronic care plan.

RPM and RTM

RPM covers physiologic metrics such as blood pressure, oxygen saturation, blood sugar, and weight. RTM covers non-physiologic therapeutic data such as therapy adherence or response. CMS remote monitoring guidance describes remote monitoring as billable by physicians and non-physician practitioners eligible to bill evaluation and management services, requires an established patient relationship for RPM, and states that only one practitioner can bill remote monitoring for a patient in a 30-day period.⁸

RPM and RTM should not be billed together for the same patient during the same period. Monitoring must be medically reasonable and necessary, consent is required, RPM physiologic data must be electronically collected and automatically uploaded, and the device must meet the FDA definition of a medical device.

How a pharmacy fits without pretending to be the billing provider

The workable model is usually a clinic-pharmacy services arrangement. The clinic owns the patient relationship, billing decision, medical record, supervision model, and escalation policy. The pharmacy supplies trained personnel and workflow capacity under the clinic’s direction.

That arrangement needs more discipline than a referral handshake. Pharmacy-clinic arrangements involving federally reimbursed services should be reviewed for Anti-Kickback Statute risk, state law, fee-splitting rules, licensure, scope of practice, and payer requirements. Compensation should be for bona fide services actually performed, not for referrals or federal program volume.⁹

The agreement should describe services, supervision, documentation, compensation, data access, privacy obligations, record retention, escalation rules, and billing review responsibilities. It should not look like payment for patient referrals or a percentage bounty for billable claims.

Compliance constraint: do not treat the contract as an afterthought

A pharmacy-clinic arrangement can create Anti-Kickback Statute risk when money changes hands in connection with federally reimbursed health care services. The federal personal services and management contracts safe harbor at 42 CFR 1001.952(d) includes requirements such as a written and signed agreement, a term of at least one year, services specified in the agreement, compensation methodology set in advance, fair market value, commercial reasonableness, and compensation not determined in a manner that takes into account the volume or value of referrals or other federally reimbursable business.⁹

That safe harbor is not automatic, and it is not the only issue. State law, pharmacy scope, clinical licensure, fee-splitting rules, corporate practice rules, payer policies, supervision rules, privacy requirements, and the clinic's own compliance policies may also matter. Confirm structure with counsel before launch.

Operationally, the cleanest position is that the pharmacy is paid for documented services actually performed. The clinic bills only after its billing team determines the patient, service, month, and documentation meet the relevant requirements.

Operating model: clinic responsibilities vs. pharmacy responsibilities

Clinic owns	Pharmacy can supply under agreement
Determines whether the patient is clinically appropriate and confirms payer eligibility.	Provides outreach support, medication complexity input, adherence checks, and eligibility worklists for clinic review.
Verifies initiating visit requirements where applicable and obtains or supervises consent.	Supports consent workflow documentation, device onboarding, education, follow-up calls, and SMS follow-up under clinic direction.
Maintains the medical record, owns care plan authority, sets supervision and escalation protocols, and reviews monthly documentation.	Supports medication reconciliation, care plan updates, monitoring review, structured call notes, time capture where applicable, and escalation of clinical issues.
Submits the claim only when the clinic's billing team determines requirements are met.	Prepares monthly documentation packages, device data summaries, outreach logs, billing readiness inputs, and EMR-ready patient snapshots.

What you need to have in hand before launch

A clinic-pharmacy remote care program should not start with software alone. It should start with a controlled evidence model.

Roster fields: provider, payer, diagnosis, medication, contact, insurance, and risk information.
Program-fit decision rule: APCM, CCM, RPM, RTM, or exclusion.
Consent workflow: when consent was obtained, who obtained it, which service it covered, what cost-sharing and duplicate-billing language was communicated, and where evidence is stored.
Initiating visit check: a documented process where an initiating visit is required.

Care plan workflow: creation, updates, clinical review, patient goals, and care-team access.
Supervision and escalation protocol: what pharmacy staff may do, when to escalate, and who closes the loop.
Monthly work queue: next actions for outreach, SMS, device review, education, escalation, and documentation.
Billing readiness and EMR export: where monthly checks live and how the clinic saves the evidence package.

In FairPath, the first operational step can be a spreadsheet roster import with diagnoses, medications, insurance fields, contact information, and custom fields selected by the team. FairPath supports program eligibility scoring for RPM, CCM, RTM, and APCM so the clinic and pharmacy can review likely candidates before patient outreach begins.

Recommended workflow for the first month

Start with one clinic, one cohort, one billing review process, and one documentation export. A 50 to 100 patient pilot is usually large enough to reveal workflow problems without making the first month impossible to audit manually.

The clinic selects the cohort. The pharmacy may help identify medication complexity, adherence barriers, uncontrolled chronic conditions, refill gaps, or frequent communication needs, but the clinic should make the clinical enrollment decision.
The team assigns a program strategy. A patient may fit CCM, APCM, RPM, RTM, or exclusion depending on clinical need, payer rules, device use, medical necessity, data collection, and billing requirements.
The clinic confirms consent and initiating visit status. Consent should be obtained before services begin where required, and the record should show the patient was informed about the service, possible cost sharing, duplicate billing limitations, and the right to stop services.
The team builds or updates the care plan. A defensible care plan should reflect diagnoses, medications, goals, barriers, functional issues, escalation thresholds, communication preferences, and planned interventions.
The team runs the month from a work queue. Each patient should have a next action: call, SMS follow-up, device reading review, medication issue, education delivery, provider escalation, care plan update, or documentation review.
The billing team reviews readiness before submission. The review should confirm patient eligibility, consent, initiating visit status where required, care plan status, service activity, time records where applicable, device data where applicable, duplicate billing, incompatible combinations, payer rules, and billing provider attribution.
The clinic saves the monthly evidence package to the EMR. The pharmacy's platform should not become the only place where the clinical record exists.

FairPath supports care plans built from condition pathways, with generation, editing, approval, publishing, and review cadence. It can also generate clinical summaries and suggested next steps tied to the care plan and patient context, but the clinic should retain clinical review and approval where required.

FairPath handles work queue execution through a priority queue and scheduled events. Staff can call inside the platform, use configurable caller ID options, record calls where permitted, generate transcripts and summaries, capture post-call time, send two-way SMS, and keep message history tied to the patient record.

FairPath tracks minutes across programs and shows progress in a billing grid. Its billing queue can surface overlap or conflict warnings, such as CCM and APCM being prepared for the same patient in the same month or RPM and RTM being mixed in a way that requires review. The purpose is not to guarantee payment. The purpose is to catch operational conflicts before claim submission.

Common failure modes

Wrong patients: chronic disease alone does not prove that a patient meets requirements for a given service, payer, month, device, or billing provider.
Missing consent: consent is easy to operationalize and hard to fix after the month is billed.
Weak care plan: generic care plans do not support patient-specific clinical work well.
End-of-month reconstruction: rebuilding activity from phone notes, text messages, and memory is not audit-ready.

Duplicate or incompatible billing: RPM and RTM cannot be billed together for the same patient, and time or effort should not be counted twice.
Wrong compensation model: payment should not look tied to referrals, prescription volume, or a percentage of claims.
APCM reporting confusion: APCM performance measurement and reporting pathways are not a substitute for patient-level operational evidence.⁶

What to save to the EMR each month

The clinic should retain a monthly patient-level record that can be reviewed without logging into multiple systems.

Consent record or consent status, including date, method, and required patient disclosures.
Care plan or care plan update.
Outreach logs, call summaries, SMS history where clinically relevant, and patient education delivered.
Device data summary where applicable.

Clinical escalations, provider responses, medication issues, and unresolved barriers.
Billing readiness status.
For time-based services, time records with enough detail for the billing team to determine whether the time counts.
For monitoring services, device onboarding status, data collection status, transmission summary, and treatment management activity where applicable.

The export should answer a simple audit question: for this patient, this provider, this service, and this month, what happened and why was the clinic comfortable billing?

Minimal example: one clinic, one patient, one month

A primary care clinic identifies a Medicare patient with hypertension and diabetes who has medication adherence barriers and recent uncontrolled readings. The clinic determines that the patient may be appropriate for a care management or monitoring program.

The pharmacy, working under a written services agreement, uses the clinic-approved consent workflow. Consent is documented. The clinic confirms initiating visit status. The care plan is updated to include medication adherence barriers, home reading review, patient education, follow-up cadence, and escalation thresholds.

During the month, pharmacy staff complete outreach, document the patient's medication issue, review home readings where applicable, send education, and escalate an out-of-range blood pressure pattern to the clinic. The clinic reviews the escalation and updates the plan.

Before billing, the clinic's billing team checks the patient, provider, program, month, consent, care plan, activity, time or device data where applicable, and overlap rules. If the requirements are met, the clinic bills. If they are not met, the month is not billed.

At month end, the clinic saves the patient snapshot to the EMR. The pharmacy is paid under its services agreement for the work performed.

When this model is a poor fit

This model is not appropriate when the clinic does not want to supervise the work, the pharmacy wants to control billing without the patient relationship, or the compensation model depends on claims volume rather than services.

It is also a poor fit when staff cannot document consistently, when no one owns monthly billing review, when payer rules are unclear, or when counsel has not reviewed the clinic-pharmacy arrangement.

A pharmacy should not start clinic-partnered remote care as a workaround for telepharmacy restrictions. It should start only if the pharmacy can perform real clinical support work under the clinic's direction and produce clean monthly evidence.

Where FairPath fits

FairPath fits where the work becomes too detailed for spreadsheets and too risky for informal tracking. It is built for the part of the model where work has to be assigned, documented, supervised, and exported without pretending the pharmacy is the Medicare billing provider.

The practical outputs are roster imports, program-fit scoring, consent records, care plan version history, priority queues, scheduled follow-ups, call transcripts, call summaries, post-call time capture, SMS history, education delivery records, billing grid progress, billing queue warnings, and patient snapshot exports.

Those outputs matter because the clinic needs evidence before billing, the pharmacy needs proof of work performed, and the patient needs consistent follow-up that does not depend on staff memory. Teams running FairPath can generate patient snapshot exports and billing readiness views as part of a clinic-pharmacy remote care pilot. The useful next step is not a broad rollout. It is a 50 to 100 patient pilot with one clinic, one cohort, one monthly billing review, and one EMR documentation export.

FairPath does not bill Medicare and does not provide legal compliance. The billing practitioner, practice billing team, and counsel remain responsible for payer interpretation, claims, supervision design, and contracting.

How to choose a starting model

If the goal is prescription access

Investigate telepharmacy. Start with the state board rule text, remote site licensing, supervision mechanics, technician qualifications, inspection requirements, prescription volume assumptions, and whether the target geography can support the dispensing operation.

If the goal is clinical services revenue

Pilot clinic-partnered remote care with one clinic and one cohort. Define the services agreement, map scope of practice, select APCM, CCM, RPM, or RTM based on patient need, and prove the monthly evidence trail before expanding.