How to Bill Remote Patient Monitoring: CPT Codes, Setup, and Stacking With CCM Without Double-Counting

Remote patient monitoring billing runs on a setup code billed once per device, plus two recurring monthly components: one for device data collection and one for clinical management time. The data code is CPT 99445 for 2 to 15 days of readings, or 99454 for 16 or more days. The management code is CPT 99457, with 99458 for each added 20 minutes. RPM stacks with both CCM and APCM. The only hard rule is that minutes spent on each program must stay separate, with no single minute counted twice.

I run a Medicare-only house-call practice, and RPM is some of the cleanest recurring revenue a small panel can build. It is also, like CCM, one of the easiest to lose on a post-payment review when the minutes and the device data aren't documented separately. This is the breakdown I use: which code does what, how to get the setup charge right, and how to run RPM alongside CCM without billing a combination that collapses on audit.

What are the RPM CPT codes and what does each one pay?

There are now six RPM codes, and they fall into three buckets: one setup charge per device, a monthly device-and-data charge, and monthly management-time charges. The descriptions below are written in plain language. They are not the official AMA CPT descriptors, which are copyrighted, so confirm the exact official wording in your encoder before billing. The dollar amounts are CY2026 national non-facility estimates, computed from the CMS published RVUs multiplied by the 2026 conversion factor of $33.4009. They are estimates: your actual payment is adjusted for your locality and will differ.

These are national estimates, not your number. Medicare pays by locality, and the gap matters: the California non-facility amount for 99454 runs higher than the $52.11 national figure (your own Area 18 schedule has it near $56). Pull your exact rate from the CMS Physician Fee Schedule Look-Up Tool using your MAC and locality before you build any revenue model on it.

Two structural facts worth knowing regardless of locality, both from the CY2026 PFS Final Rule. First, 99445 (2 to 15 days) and 99454 (16+ days) pay the identical rate and are not additive, so you bill one or the other based on days of data. Second, 99470 (10 to 19 minutes) was valued at 0.31 work RVUs against 99457's 0.61, which is why it lands at roughly half the payment.

How does RPM setup billing work, and how do I maximize it?

The setup code, 99453, is billed once per device after the patient begins transmitting data. It is not a per-month code. You bill it one time per device when monitoring on that device begins.

Here is the lever. You can bill only one device setup per calendar month. So if a patient is going to use multiple devices, you don't onboard them all at once. You stagger them, one device per month, and capture a separate 99453 each month.

A patient who needs a blood pressure cuff and a scale and a glucometer is three separate 99453 charges if you space the setups across three months. Onboard all three in January and you bill 99453 once, losing the other two. Same devices, same patient, different revenue, purely a function of timing.

A new device counts for a fresh 99453 only when it is a genuinely different device, not a replacement for a broken unit of the same kind. Document the start date and the data transmission for each device so each setup stands on its own in an audit.

What are the two monthly RPM charges?

Every billable RPM month has two distinct recurring components: the device data charge and the management time charge. They are separate codes with separate requirements, and conflating them is a documentation error.

The first is the data code. It pays for supplying the device and transmitting readings. Two options now exist, and they are mutually exclusive in the same period:

• 99445 if the patient transmits 2 to 15 days of data.
• 99454 if the patient transmits 16 or more days of data in the 30-day window.

You bill one or the other, never both for the same period. The 2-day floor is a CY2026 change that opened RPM to patients who don't hit 16 days, which matters for acute and episodic use, not just chronic monitoring.

The second is 99457, the management code. It covers the first 20 minutes of clinical staff time spent on RPM treatment management, and it requires interactive communication with the patient or caregiver during the month. Live contact, a phone or video touch, not just chart review. Beyond the first 20 minutes, each additional 20 minutes is 99458. For lighter-touch months, the CY2026 code 99470 covers 10 to 19 minutes. So a standard billable month for one patient on one device looks like: a data code (99445 or 99454) plus a time code (99457, or 99470 for lighter touch) plus 99458 as warranted. Setup (99453) appears only in the first month of that device.

Can I bill RPM and CCM in the same month?

Yes. CMS treats RPM and CCM as complementary code bodies, and you can bill both for the same patient in the same month as long as you independently meet the requirements for each. This is a real dual-reimbursement structure, not a gray area.

The one hard rule is minutes. A minute counted toward CCM cannot also be counted toward RPM. Time spent coordinating care under CCM (99490) is not the same time as reviewing RPM data and talking to the patient about it (99457). Each program needs its own clock.

The clean way to document this is two separate, labeled blocks in the note. One example of how that reads: an RPM block noting 22 days of blood pressure data reviewed, elevated readings on specific dates, and 20 minutes on a call about medication timing; then a separate CCM block noting 15 minutes coordinating with the patient's podiatrist and 10 minutes updating the care plan. Different work, different minutes, different headings. The chart is your proof.

RPM also stacks with APCM (G0556 through G0558), since CMS classifies RPM as complementary to APCM rather than overlapping. Note the contrast: APCM does not stack with CCM, PCM, or TCM, because those overlap substantially with what APCM already pays for. RPM sits outside that exclusion.

How should RPM time be documented to survive an audit?

Track RPM minutes in their own bucket, time-stamped, attributed to a named staff role, and tied to the interactive-communication requirement for 99457. Reconstructed or estimated time is the fastest way to lose a claim.

A defensible RPM time record shows three things: who performed the work, when (contemporaneous time entry, not a month-end estimate), and what the interactive patient contact was. RPM management time must be synchronous. Unlike CCM, where asynchronous work counts, RPM management time is built around live patient interaction.

The 2020 Medicare fee-for-service CCM improper payment rate was 67.4 percent, driven largely by reconstructed time and overlapping codes. Concurrent RPM and CCM done sloppily is precisely that failure mode. Done with clean minute separation, it is a legitimate revenue structure. Here is the clean-documentation checklist I use:

1. RPM minutes logged contemporaneously, never reconstructed at month-end.
2. Each entry attributed to a specific staff role and time-stamped.
3. The interactive communication for 99457 documented with date and method.
4. The data code (99445 or 99454) supported by a device-transmission log showing the day count.
5. When CCM also applies, separate labeled blocks for CCM minutes and RPM minutes, with zero shared time.
6. 99453 billed once per device, one device setup per month, with each device's start date documented.

Frequently asked questions

Start with separation, not the codes

If you take one thing from this: RPM revenue is clean only when the minutes are. Build the wall between RPM and CCM time at the moment the work happens, log every entry contemporaneously with a name and a timestamp, and bill the setup once per device on a staggered cadence. Get that right and the six codes take care of themselves.

That separation is the core of the care management software I'm building and piloting at Mobile Health Providers: a single platform for CCM, APCM, RPM, PCM, and BHI that enforces the compliance rules instead of leaving them to a biller's memory. RPM minutes and CCM minutes live in separate program buckets that can't borrow from each other, the device-transmission log backs the data code, and the interactive-contact note is captured at the time of the call, so the record defends itself before anyone requests it.

Dr. Wyzscx Patacxil, MD, CWSP

Physician-Owner, Mobile Health Providers

Dr. Patacxil is the physician-owner of Mobile Health Providers, a house-call primary care and advanced wound care practice serving patients across San Bernardino, Riverside, Los Angeles, and Orange counties. He treats homebound and mobility-limited Medicare beneficiaries in their homes, skilled nursing facilities, and assisted living communities. His clinical focus includes chronic wound management, chronic care management, and preventive medicine. He writes about wound care, aging, health technology, and what modern house-call medicine actually looks like.

Read more about Dr. Patacxil →