Remote Patient Monitoring Billing: CPT 99453–99458 & 2026 Codes
Remote patient monitoring pays practices to manage patients using data their devices transmit from home — but payment turns on day counts, time logs, and device rules. This guide covers the code set and the new 2026 codes.
Remote patient monitoring billing covers services in which a patient uses a connected medical device at home to collect physiologic data — blood pressure, weight, blood glucose, pulse oximetry, respiratory flow — transmitted to the practice for review and treatment management. RPM gives clinicians visibility between visits, catches deterioration earlier, and creates a recurring monthly service line.
It is also a program where the details decide payment. RPM claims turn on how many days data was transmitted, whether the device meets the definition of a medical device, whether management time included a live interactive communication, and whether the same minutes were claimed under another program. Payers review RPM closely because it is delivered without a face-to-face encounter. This guide explains what RPM is, the established code set, the new 2026 codes, and the rules that decide whether claims pay or deny.
What Remote Patient Monitoring Is
RPM is the collection and analysis of physiologic data from a patient in one location — usually the home — transmitted to a provider in another location for use in developing and managing a treatment plan. Three elements define a billable RPM service:
- Physiologic data — the device measures a parameter such as weight, blood pressure, pulse oximetry, respiratory flow rate, or blood glucose. Patient-reported symptoms are not physiologic data; those fall under remote therapeutic monitoring instead.
- An FDA-defined medical device — the device must meet the Food and Drug Administration's definition of a medical device. A wellness app or consumer gadget does not qualify, and the device itself must collect the data rather than the patient entering it manually.
- Automatic upload — data must transmit automatically to the practice. Readings a patient phones in or types into a portal do not satisfy the device supply requirement.
RPM can be furnished for chronic or acute conditions or a single monitoring episode, with no fixed diagnosis list — the ordering practitioner documents why monitoring is medically reasonable and necessary. The patient must consent, and cost sharing may apply, which should be explained before enrollment.
The Established RPM Code Set: 99453–99458
The core RPM family separates the work into setup, device supply, and treatment management. Setup and supply codes are reported by the billing practitioner, and treatment management time may be performed by clinical staff under general supervision.
| Code | Description | Requirement notes |
|---|---|---|
| 99453 | Initial device setup and patient education | Once per episode of care, not per device; not billable if the monitoring episode lasts fewer than 16 days |
| 99454 | Device supply with daily recording and programmed alert transmission, each 30 days | Requires data transmission on at least 16 of the 30 days for the standard code; one unit per 30-day period regardless of device count |
| 99457 | Treatment management, first 20 minutes per calendar month | Requires at least one interactive communication with the patient or caregiver during the month, plus at least 20 minutes of management time |
| 99458 | Treatment management, each additional 20 minutes | Add-on to 99457; each unit requires a full additional 20 minutes in the same calendar month |
Two structural points matter. First, the device supply code runs on a 30-day period, while treatment management codes run on a calendar month — two clocks your tracking system must keep separate. Second, 99454 is reported once per 30 days even if the patient uses two devices, and 99453 is once per episode even if a device is swapped.
New for 2026: CPT 99445 and 99470
Two new codes take effect for 2026 and close gaps that practices have flagged since RPM began. Previously, a patient who transmitted data on, say, 10 days in a 30-day period generated no billable device supply at all, and a month with 12 minutes of management time generated no billable treatment management. The 2026 codes recognize those shorter periods:
- CPT 99445 — device supply for remote monitoring of physiologic parameters, covering patients who transmit data on 2–15 days within the 30-day period. It is the short-period counterpart to 99454, which continues to require 16–30 days. A given 30-day period supports one or the other, never both.
- CPT 99470 — the first 10 minutes of RPM treatment management in a calendar month, with interactive communication. It is the short-increment counterpart to 99457, which requires 20 minutes. As with the supply codes, the practice bills the code that matches the time actually documented in that month.
For billing operations, the change is in day-count and time tracking: periods previously written off as non-billable now need to be captured and coded to the short-period option when thresholds fit, kept separate from full-period claims. Expect payer system updates to lag the release, so confirming how each payer has loaded 99445 and 99470 belongs on your January follow-up list.
Key Rules Behind RPM Payment
- The 16-day rule — for the standard codes, data must be transmitted on at least 16 days of the 30-day period to bill 99454, and the same threshold supports 99457 and 99458. Below 16 days, use the new 2026 short-period codes instead.
- One billing practitioner per patient per period — only one practitioner may bill RPM for a patient in a 30-day period, even if different specialists review different data streams. Coordinate before enrollment.
- Consent and medical necessity — document patient consent, the order, and medical necessity, and confirm the patient understands cost sharing may apply.
- Interactive communication is mandatory — 99457, 99458, and 99470 require at least one real-time communication with the patient or caregiver during the month. Silent data review alone does not support a management claim.
- Time is counted once — RPM management minutes cannot also count toward CCM, PCM, transitional care management, or other timed services that month.
RPM vs CCM: No Double-Counting
RPM and chronic care management pair naturally — a hypertensive patient may be enrolled in both — and both can be billed in the same month. What cannot happen is double use of the same minutes. Time reviewing transmitted readings and speaking with the patient about them is RPM time; time coordinating referrals or revising the broader care plan is CCM time. If one activity fits both narratives, assign it to one program in the log. Practices that run both programs from a single undifferentiated time pool are the ones that fail audits. Keep separate logs with dated entries, staff attribution, and a note of the interactive communication.
Common RPM Denial Causes
- Fewer than 16 days of data billed under the standard codes — the period did not meet the threshold for 99454 or 99457, and no short-period code was used.
- Manual or self-reported data — readings entered by the patient rather than automatically uploaded by a qualifying device, which fails the device requirement.
- Missing interactive communication — management time billed for a month in which the only activity was silent data review.
- Two practitioners billing the same period — an avoidable denial when enrollment is not checked against other treating practices.
- Setup billed per device or per month — 99453 is once per episode of care; repeat setup claims deny as duplicates.
- Overlapping time with CCM or other programs — the same minutes appearing in two care management logs, surfacing on review or audit rather than at first submission.
Elite Bill Care manages RPM billing as a tracking discipline: day counts verified against transmission records before 99454 or the new 99445 is released, management time reconciled against CCM logs so minutes are never counted twice, and interactive communication confirmed before 99457 or 99470 is billed. We work inside Epic, athenahealth, eClinicalWorks, AdvancedMD, Tebra, and NextGen, follow HIPAA-compliant processes, support practices in all 50 states, and bring 10+ years of experience to care management billing. That discipline is how our clients maintain a 98% first-pass clean claim rate and achieve up to 30% denial reduction.
Related pages
- Remote Therapeutic Monitoring Billing: CPT 98975–98981 Guide
- Telehealth Medical Billing Guide
- Internal Medicine Medical Billing Services
- Primary Care Medical Billing Services
Frequently asked questions
What is the 16-day rule in remote patient monitoring?
For the standard RPM codes, the device must record and transmit data on at least 16 days within the 30-day period to bill CPT 99454, and the same 16-day threshold applies to the treatment management codes 99457 and 99458. From 2026, patients transmitting on 2–15 days can be billed under the new short-period code 99445 instead.
What are the new RPM codes for 2026?
CPT 99445 covers device supply when a patient transmits data on 2–15 days in the 30-day period, below the 16-day threshold of 99454. CPT 99470 covers the first 10 minutes of RPM treatment management with interactive communication, below the 20 minutes required for 99457. Each period or month is billed under the standard or the short-period code, not both.
Can RPM and CCM be billed in the same month?
Yes. A patient may receive both remote patient monitoring and chronic care management in the same month, and both may be billed. The restriction is on time: minutes counted toward RPM treatment management cannot also count toward CCM, so each program needs its own dated time log.
Does the RPM device have to be FDA-cleared?
The device must meet the FDA's definition of a medical device, must collect the physiologic data itself, and must upload it automatically. Consumer wellness tools and patient-entered readings do not meet these requirements and will not support RPM claims.
Why did our 99454 claim deny?
Frequent reasons are fewer than 16 days of transmitted data, another practitioner already billing RPM for that patient in the same period, self-reported rather than device-uploaded data, or a second unit within the same 30 days. Verify the day count from the transmission record before resubmitting.
