RPM Manual
The practical 2026 guide to device rules, day thresholds, management time, and audit defensibility for Remote Patient Monitoring.
Read the RPM Guide →How pharmacies can operationalize APCM using incident to rules without waiting for federal provider status
Operational strategy for pharmacy-led care management
Compliance note: This resource is educational and does not constitute legal advice. Incident to billing, APCM participation, and any financial arrangement between a pharmacy and a billing practitioner should be reviewed for compliance with applicable federal and state requirements, including payer policies and program integrity expectations.
Many pharmacy owners have a reasonable frustration: pharmacists deliver high-value clinical work, but Medicare billing is still tied to specific practitioner types and billing structures. Congress may eventually expand pharmacist provider status, but your operating plan cannot depend on an uncertain timeline.
Medicare already has an established mechanism that can allow pharmacy staff to contribute to care management workflows today: the “incident to” benefit in 42 CFR 410.26. In general, incident to services require direct supervision. However, the regulation explicitly allows designated care management services to be furnished under general supervision when provided incident to the services of a billing physician or other practitioner. (Legal Information Institute)
Separately, CMS created Advanced Primary Care Management (APCM) as a monthly bundle starting January 1, 2025 using HCPCS codes G0556, G0557, and G0558. APCM is not time-based, is billed once per patient per month, and is designed around clinical staff delivering services under the direction of the responsible billing clinician. (CMS)
The practical strategy is not a loophole. It is an operating model: the billing practitioner bills APCM, the pharmacy supplies defined clinical operations through a compliant agreement, and documentation is engineered so the billed service is real, attributable, and defensible.
Two different questions get conflated:
Often yes, subject to state scope of practice and program design.
Often no, because Medicare Part B billing is tied to eligible billing practitioners and coverage rules.
The incident to benefit is one of the bridges between these realities, but only if you design it correctly and you do not double bill under Part D for the same work.
Medicare Part B pays for services and supplies “incident to” a physician’s (or other practitioner’s) professional services only when specific conditions are met. Those conditions include that the services are furnished in a noninstitutional setting, are an integral though incidental part of the practitioner’s diagnosis or treatment, and meet the supervision and state law requirements. (Legal Information Institute)
The default supervision requirement is direct supervision. However, the regulation explicitly states: “Designated care management services can be furnished under general supervision of the physician (or other practitioner) when these services or supplies are provided incident to the services of a physician (or other practitioner).” (Legal Information Institute)
General supervision means the supervising practitioner provides overall direction and control, but is not required to be physically present during performance of the service. The constraint is not physical proximity. The constraint is responsibility, clinical direction, documentation, and correct attribution under the billing practitioner. (Legal Information Institute)
The incident to regulation defines “auxiliary personnel” to include individuals acting under the supervision of a physician or other practitioner “regardless of whether the individual is an employee, leased employee, or independent contractor,” and the definition includes additional eligibility requirements such as not being excluded and meeting applicable state requirements. (eCFR)
CMS explicitly addressed that pharmacists fall within the regulatory definition of auxiliary personnel under 410.26 and may provide services incident to the billing physician or NPP under the appropriate level of supervision, as long as payment for the services is not made under the Medicare Part D benefit. (CMS)
This last clause is not optional. It is the “Pharmacy Firewall” principle applied to incident to: you cannot use Part B to get paid for work that is already being paid under Part D.
APCM is designed to remove the minute-by-minute documentation burden of time-based care management codes and replace it with a monthly bundle reflecting essential elements of advanced primary care. CMS finalized new coding and payment for APCM effective January 1, 2025. (CMS)
CMS states that starting January 1, 2025, APCM can be billed by a physician or non-physician practitioner (NPP) such as NP, PA, or CNS who is responsible for all the patient’s primary care services and serves as the focal point for all needed health care services, and who has obtained patient consent. (CMS)
CMS states APCM can be billed once per patient per calendar month. It is not time-based. (CMS)
CMS defines three APCM codes and their core differences: (CMS)
| Code | Description |
|---|---|
| G0556 | Clinical staff provide the APCM services, directed by a physician or other qualified health care professional who is responsible for all primary care and serves as the continuing focal point. |
| G0557 | Patient has two or more chronic conditions meeting duration and risk criteria, and the service includes all G0556 requirements. |
| G0558 | Patient is a Qualified Medicare Beneficiary with two or more chronic conditions meeting the same duration and risk criteria, and the service includes all G0556 requirements. |
Do not publish payment amounts as fixed values: APCM payment varies by locality and other factors. If you need precise numbers for your ROI model, use CMS PFS data sources and compute rates for your locality and setting. CMS does not present APCM payments on the APCM overview page itself, and blog tables are not authoritative. (CMS)
CMS lists a detailed set of billing requirements. For pharmacy-led execution, the high-impact requirements are the ones that force real operations rather than “paper care management.” (CMS)
These elements are exactly where pharmacies can deliver disproportionate operational value.
The cleanest way to describe the model is not “leased employee.” It is “operational delegation under clinical direction.”
The billing practitioner remains responsible for the patient’s overall care and the billed service. Pharmacy staff can execute defined operational tasks as auxiliary personnel under the billing practitioner’s direction, consistent with state law and supervision requirements. (Legal Information Institute)
This is an operating template, not a legal instruction.
If you want the model to survive scrutiny, treat the contract as part of the compliance design.
CMS’s own language reinforces that incident to services must comply with applicable state law and supervision requirements and that payment cannot also be made under Part D for pharmacist-provided incident to services. (Legal Information Institute)
APCM is not time-based, but it is not documentation-free. A defensible program produces the artifacts that map to the requirements.
If you cannot produce these artifacts quickly, the program is not operationalized.
This model fails without a real care management system that can separate dispensing from clinical documentation and can assemble audit artifacts without manual reconstruction. Any platform you use should be evaluated against APCM’s explicit operational requirements and the incident to supervision and role constraints. (CMS)
Waiting for provider status is a policy strategy. Implementing APCM through an incident to operating model is an operational strategy. The difference is that operations can be executed now, if you respect the actual regulatory mechanics:
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 →