How Much Revenue Can RPM Generate for a Practice? The 2026 Economics

Every practice considering remote patient monitoring eventually asks the same question: what does this actually generate? The honest answer requires arithmetic, not adjectives — per-patient monthly revenue built from the current CPT codes, multiplied across a realistic panel, minus the real costs of running the program. This guide works through that math using the 2026 code structure, with a standing caveat: every dollar figure here is a national average non-facility amount from secondary rate tables. Verify each against the CMS Physician Fee Schedule lookup before building a budget on it, because geographic adjustment and payer mix will move your actual numbers.

What does one RPM patient generate per month?

The 2026 code structure bills along two axes — device supply per 30-day period, and management time per calendar month — plus a one-time setup code. The hedged national averages:

From those parts, the recurring monthly scenarios:

• The full month — 16 or more transmission days plus 20 or more documented minutes — bills 99454 + 99457: roughly $99.
• The light-touch month — full data, 10–19 minutes — bills 99454 + 99470: roughly $73.
• The partial-data month — 2–15 transmission days — substitutes 99445 at parity, so the device-supply revenue holds at roughly $47 regardless of which side of 16 days the patient lands on, as long as they clear 2 days.
• The high-touch month adds 99458: roughly $140 at 40+ documented minutes.

A patient who bills the full combination every month represents roughly $1,190 per year at national averages, plus the one-time setup. That number is a ceiling, not a forecast — which is what the next section is for.

What does a realistic panel actually produce?

No panel bills the ceiling. Some patients transmit 25 days a month; others plateau at 10. Some months need three calls; others need six minutes of review. An honest model assumes a mix. As a purely illustrative assumption set — not a benchmark from any published source — suppose in a given month 60% of enrolled patients hit the full combination ($99), 25% land in partial or light-touch tiers ($73), and 15% fall below the billing floors entirely ($0). That blend yields roughly $78 per enrolled patient-month.

Change the engagement mix and the totals move with it — which is the real lesson. RPM economics are engagement economics: the difference between a program where 60% of patients hit full thresholds and one where 80% do is worth more than most pricing negotiations. Model your own assumptions rather than borrowing these; our reimbursement calculator exists for exactly that — it lets you set panel size and adherence rates and see the revenue math under the current code structure.

What does it cost to run?

Revenue is half the model. The recurring cost lines:

Devices. Cellular-connected devices are purchased or leased per patient, with replacement and logistics overhead. Whether devices are bought outright or bundled into a platform fee changes cash flow more than total cost — compare on cost per managed patient.

Clinical staff time. This is the dominant cost, and it scales with the codes themselves: a 99457 month requires 20 documented minutes, and a 99458 unit requires 20 more. A useful planning frame is capacity — each staff hour covers roughly three full management months at the 20-minute minimum, before accounting for alert triage, outreach to non-transmitting patients, and documentation. Programs underestimate the outreach time most.

Billing and administrative overhead. Claims work, transmission-day reconciliation, time-log review, and denial follow-up. The 2026 pairing rules — one device-supply code per period, one management path per month — are simple to automate and expensive to get wrong. Practices without in-house bandwidth often pair the program with billing support.

Enrollment effort. Identifying eligible patients, obtaining consent, and onboarding devices is front-loaded work that the one-time setup code only partly offsets.

Can RPM revenue stack with other care-management programs?

For many chronic-disease patients, yes — and the stack changes the per-patient math materially. Medicare has allowed remote patient monitoring and chronic care management (CCM) to be billed for the same patient in the same month since CY 2021, provided no minute of staff time counts toward both programs. A patient in both programs can generate the RPM combination above plus a CCM claim — the base CCM code 99490 runs roughly $66 at national averages — in the same month, pushing a full concurrent month toward roughly $165 before add-on codes.

The condition is operational: separate, unambiguous time logs for each program. The same twenty minutes cannot support both claims, and blended logs are how concurrent programs fail audits. Practices that build clean time attribution from the start can treat the CCM layer as a genuine second revenue line on the same panel; practices that cannot should run one program well before adding the second.

One boundary to model around: RPM and remote therapeutic monitoring (RTM) are mutually exclusive for the same patient in the same month, so there is no RPM+RTM stack.

Which caveats matter most?

Payer mix. The figures above are Medicare national averages. Your Medicare share of panel determines how much of the model applies at these rates; commercial payer policies for RPM vary and must be verified plan by plan.

Cost-sharing. Medicare beneficiary cost-sharing applies to these services, which affects collections and patient conversations at enrollment. Patients asked to pay something monthly disenroll differently than patients who owe nothing — factor collection rates into the model.

Geographic adjustment. National averages are exactly that. Your locality's fee schedule amounts differ, in either direction. This is why every figure in this article carries the same instruction: check the CMS PFS lookup for your locality.

Adherence decay. Engagement in month one is not engagement in month nine. Sustainable programs budget staff time for re-engagement, not just monitoring.

Rate stability. For 2026 specifically, the ground held: the conversion factor rose 3.26% (3.77% for qualifying APM participants), and the fee schedule's new efficiency adjustment explicitly exempts care-management and time-based codes, leaving the RPM family untouched by the year's most discussed cut. Rates remain subject to annual rulemaking, though — a model built today should be re-checked against each year's final rule.

How did the 2026 codes change the economics?

Before this year, RPM billing was all-or-nothing: fewer than 16 transmission days meant zero device-supply revenue, and fewer than 20 management minutes meant zero management revenue. The CY 2026 final rule, in effect since January 1, added 99445 and 99470 — and with them, a revenue floor.

The effect on the model is specific: the worst realistic outcomes got better. A month with 12 transmission days now bills roughly $47 instead of nothing. A month with 14 minutes of management bills roughly $26 instead of nothing. In the illustrative panel above, the middle tier — partial and light-touch months at roughly $73 — largely did not exist as revenue in 2025. Programs whose billing logic still assumes the old cliff are forfeiting exactly the months the new codes were created to pay.

The floor changes program design, too. Short monitoring episodes — a two-week post-discharge protocol, a medication-titration window — now carry device-supply payment at parity with full months, which makes deliberately brief programs economically rational for the first time. The details of the new codes and their pairing rules are covered in our guide to the 2026 RPM and RTM changes.

How should a practice run this analysis?

1. Count the eligible panel — patients with conditions worth monitoring and a physiologic parameter that changes management.
2. Set honest engagement assumptions, ideally from a vendor's real transmission data for comparable populations, and model a range rather than a point estimate. Remember the ramp: month one of any program bills setup plus whatever fraction of the cohort establishes the habit, and steady-state economics arrive only after the enrollment and engagement curves settle — budget the first quarter as an investment period, not a sample of the run rate.
3. Model the tiers, not just the ceiling — full months, light-touch months, partial-data months, and zero months.
4. Load the costs — devices, staff minutes per patient-month, billing overhead, enrollment effort.
5. Run it through the calculator, then stress-test the result at lower adherence before committing.

A well-run program on a modest panel produces meaningful, recurring revenue for care the practice arguably should be delivering anyway — that is the honest case for RPM, and it survives conservative assumptions. What it does not survive is neglect: the economics follow engagement, staffing discipline, and billing precision. Our RPM service overview describes how Neuvora's physician-led program handles those operational determinants.

This article is general billing information, not billing, legal, or medical advice. Verify current rates and payer policies against the CMS Physician Fee Schedule and your MAC before billing.