RPM Manual
The practical 2026 guide to device rules, day thresholds, management time, and audit defensibility for Remote Patient Monitoring.
Read the RPM Guide →Independent pharmacies are being forced to evolve. A large national analysis found that about 29% of retail pharmacies operating between 2010 and 2021 had closed by 2021, with disproportionate impact in underserved communities. The survival path is not more square footage. It is more reach and more clinical contribution.
Compliance note: This resource is educational and does not constitute legal advice. Telepharmacy is state-regulated, and Medicare billing depends on the billing practitioner, enrollment, supervision, and documentation. Validate program design with your compliance team and qualified counsel.
This report describes how a modern independent pharmacy can operate as an integrated access and clinical services organization without pretending that federal and state rules are simpler than they are.
The key concept is separation of concerns:
The integrated pharmacist model wins when you treat those as two distinct operating systems that share a patient relationship but do not contaminate each other’s workflows and records.
The integrated pharmacist model is not a marketing slogan. It is an operating design that combines remote dispensing reach with a care-management execution layer that supports eligible billing practitioners. The differentiator is not intent. It is audit-proof workflow separation, consistent documentation, and measurable clinical outcomes.
The closure wave is not a narrative. It is data. A Health Affairs analysis found that 29.4% of retail pharmacies operating during 2010 to 2020 had closed by 2021, and independent pharmacies had higher closure risk across neighborhood and market characteristics. This impacts access, adherence, and basic public health services.
The operational consequence is that independent operators need a strategy that does not depend on per-fill margin stability. That usually means two parallel moves:
A practical definition of value-based alignment for pharmacies: take measurable responsibility for adherence, medication safety, and access, then contract around that capability.
Telepharmacy is not one thing. It is a family of models that all attempt to decouple dispensing supervision from physical co-location. State boards define what is allowed, and the constraints matter more than the technology.
Technicians at a spoke site, pharmacist supervision from a hub via audio-video.
A registered remote site where the practice of pharmacy occurs through a telepharmacy system.
Automated dispensing with pharmacist verification and counseling using live audio-video.
Although state-by-state rules vary, telepharmacy regulations tend to focus on:
A peer-reviewed policy analysis reported telepharmacy permitted in 28 states as of the study period and highlighted wide variation in constraints that affect real-world deployment. [2]
Industry summaries report adherence improvements associated with telepharmacy, with reported gains in Medicaid populations in some implementations. [3]
Do not treat state telepharmacy legality as static. Always confirm the current board rule text and the permitted model type for your planned deployment.
There are two separate questions that operators often conflate:
CMS publishes the list of provider types eligible to bill Medicare for telehealth professional services. Pharmacists are generally not on that list, which is why pharmacies should not build a strategy that depends on direct telehealth billing. [4]
This does not mean pharmacists are excluded from telehealth-delivered care. It means the billing shell is usually an eligible physician or non-physician practitioner.
CMS has clarified that pharmacists fall within the definition of auxiliary personnel under Medicare incident to rules and may provide services incident to the services of the billing physician or NPP, if payment is not made under Medicare Part D and the services are within state scope of practice. [6]
This is a compliance-sensitive area. The billing practitioner must retain responsibility for the patient’s care and documentation must support the billed service.
The integrated pharmacy does not try to “do everything.” It chooses a small number of program archetypes where pharmacies have structural advantage: adherence, medication optimization, and high-frequency patient contact.
Daily data plus monthly clinical actions.
CMS materials bundle telehealth and remote monitoring policy in a single reference and summarize key constraints including eligible billing provider types and documentation expectations. [4]
Pharmacies tend to win when they operationalize data collection, outreach cadence, and escalation pathways, while the billing practitioner performs and documents the required clinical decisions and patient communications.
Monthly continuity for complex patients.
CCM becomes pharmacy-friendly when it is treated as a medication-risk management workflow: adherence gaps, side effects, interactions, high-risk meds, and care plan reinforcement.
The operational trap is time contamination with dispensing. The defensible model uses role-based work separation, a clean care log, and explicit clinical intent in notes.
Monthly bundle, not minute-by-minute.
CMS created APCM starting January 1, 2025 and describes billing requirements, including consent, “one provider per month,” and the expectation that clinical staff provide services under direction of the responsible clinician. [7]
The pharmacy fit is obvious: medication management and coordination are core, and many practices lack the staff capacity to execute these workflows reliably.
The reason practices and payers pay for these programs is not sentiment. It is measurable outcome movement and reduced utilization. A pharmacist-supported remote hypertension management program reported 67% blood pressure control at 6 months and 74% at 12 months using a less than 140/90 threshold. [9]
Do not overfit your business model to any single study. The takeaway is that pharmacists are structurally positioned to move outcomes when the program has tight workflow design.
Most independent pharmacies will participate in Medicare Part B care management through a contracting relationship with a billing practitioner or group. That is normal. The mistake is treating the contract as a footnote.
The billing practitioner bills Medicare for the covered service. The pharmacy is paid a contracted fee for defined operational work (outreach, adherence coaching, survey administration, triage, documentation assistance), subject to scope of practice and the program design.
Separate from any single billing code, the pharmacy contracts for measurable deliverables: adherence improvement, gaps in care closure, medication safety interventions, and access extension. This works well when the practice is under quality-linked reimbursement.
A safe contracting posture is simple: avoid payment tied to volume of referrals, avoid duplicative billing for the same work, and ensure documentation supports medical necessity and the billed service. This page is educational. Program contracts should be reviewed for applicable federal and state requirements.
The integrated pharmacy model fails when technology is treated as an app list. The stack must produce auditable artifacts across dispensing access and clinical operations.
FairPath is designed to run the clinical operating layer that sits beside your dispensing system. The objective is not to replace your PMS. The objective is to produce a care-management execution engine with artifacts that are defensible when a billing practitioner or payer requests documentation.
FairPath supports operational separation between dispensing-associated work and clinical episodes by using a dedicated care log with time stamps, user attribution, and structured clinical intent selection.
FairPath is built around the reality that the eligible billing practitioner submits the claim. The platform supports communication, escalation, and documentation workflows that allow the billing clinician to supervise and document care decisions while the pharmacy executes operational tasks.
Software supports workflow discipline and documentation consistency. It does not determine billing eligibility. Eligibility and billing decisions remain the responsibility of the billing practitioner and the program’s compliance design.
Generally, no. CMS limits Medicare telehealth billing to defined practitioner types. Pharmacists typically participate by delivering clinical work under a team model and under the billing practitioner’s supervision and documentation framework.
It depends. Telepharmacy is governed by your state board of pharmacy and rules vary across supervision requirements, remote site permitting, distance limits, and controlled substance constraints. A peer-reviewed analysis reported telepharmacy permitted in 28 states at the time of study, but you should validate your current board rule text for your planned model.
Mail-order is primarily fulfillment and shipping. Telepharmacy remote dispensing is a state-regulated model where pharmacist supervision and patient counseling are provided using real-time audio-video to support safe dispensing at a remote site or kiosk.
Outcome movement is the lever. Published results from a pharmacist-supported remote hypertension management program reported 67% blood pressure control at 6 months and 74% at 12 months using a less than 140/90 threshold. Programs that reliably produce adherence and safety artifacts become easier to contract for.
No. APCM is billed by a physician or certain non-physician practitioners and does not require a pharmacist by rule. In practice, APCM depends on ongoing medication management and coordination workflows, which makes pharmacies a high-leverage operational partner when structured correctly.
While most platforms simply record what happened, FairPath actively runs the program. It continuously monitors every patient, staff action, and billing rule across CCM, RPM, RTM, and APCM, intervening immediately when a requirement is missed.
This allows you to scale your own program without losing quality, breaking trust with physicians, or losing control of your revenue. We provide the precision of an automated medical director without the chaos.
FairPath is built on operational work, not theory. We publish the playbooks and checklists we use to keep programs compliant and profitable. Use them whether you run FairPath or not.
Browse the Expert Library →The practical 2026 guide to device rules, day thresholds, management time, and audit defensibility for Remote Patient Monitoring.
Read the RPM Guide →How to run Remote Therapeutic Monitoring for MSK, respiratory, and CBT workflows with the correct 9897x and 9898x rules.
Read the RTM Guide →Calendar-month operations for CCM: consent, initiating visit, care plan requirements, time counting, and concurrency rules.
Read the CCM Guide →The operator blueprint for Advanced Primary Care Management: eligibility, G0556–G0558 tiers, and monthly execution.
Read the APCM Playbook →