Remote patient monitoring is billed in three pieces, each with its own code, threshold and clock. A practice that treats those codes as interchangeable, or that bills 99454 off a device that transmitted on nine days, invites a takeback. What decides payment is not the technology. It is documented consent, days of transmitted data, and minutes somebody wrote down.
What this covers
- RPM runs on three components: setup and education (99453), device supply (99454 or the 2026 code 99445), and treatment management (99457, 99458 or 99470).
- 99454 needs at least 16 days of transmitted data in a 30-day period. 99445 covers 2 to 15 days and is not billed in the same period.
- Consent is required at the time RPM services are furnished, and it belongs in the medical record the practice owns.
- 99457 pays for the first 20 minutes of treatment management in a calendar month and requires a live interactive communication.
A device that transmits data is not a billable service. Setup, device supply and treatment management are three codes with three tests, and a claim is only as good as the weakest one it reports.Most RPM recoupments come from reporting the strongest code against the weakest documentation.
The three components, and the code that pays for each
Medicare does not pay for remote patient monitoring as one service. CMS treats it as three parts with separate codes: setup and education, device supply with transmission, and treatment management.
| Code | What it covers | Threshold that has to be met |
|---|---|---|
| 99453 | Setup and patient education, initial | Once per episode of care, one practitioner |
| 99454 | Device supply, daily recording or alerts | 16 or more days of data in a 30-day period |
| 99445 | Device supply, new for 2026 | 2 to 15 days of data, not with 99454 |
| 99457 | Treatment management, first 20 minutes | 20 minutes in a calendar month, with a live conversation |
| 99458 | Treatment management, each additional 20 minutes | Add-on to 99457, same date of service |
| 99470 | Treatment management, first 10 minutes, new for 2026 | One real-time interactive communication, not with 99457 |
The 2026 additions close a gap without lowering the old thresholds, so a patient with 16 days of data still belongs under 99454.
Medicare allows one practitioner to bill RPM per patient in a 30-day period, even when two specialties monitor different parameters. Name the billing practitioner in the record before the device ships.
Consent: what to document, and when to get it
CMS requires patient consent at the time the practice furnishes RPM services. That is more flexible than a signed form and easier to get wrong, because verbal consent leaves no trace until someone writes it into the chart.
State Medicaid manuals spell the record out. Alabama requires consent, verbal or written, to be documented with cost sharing and the right to stop. California allows verbal consent and requires the same documentation.
CMS allows auxiliary personnel under general supervision to obtain consent. The consent belongs in the chart the practice owns, not only in a vendor platform, and one collected by a call center the practice does not control cannot be produced on request.
- The condition being monitored and why monitoring is medically necessary.
- The device, who trained the patient on it, and the training date.
- The consent, the date obtained, and who obtained it.
- The cost sharing the patient may owe, and the right to stop.
The 16-day threshold, and where the count goes wrong
The device supply codes carry the most objective test in RPM. 99454 pays once in a 30-day period when the device transmits on at least 16 of those days. The count is days of data, not readings.
The data has to arrive on its own. The device must meet the FDA definition of a medical device and upload the data automatically. A reading a patient types into a portal or photographs from a meter display is not RPM data.
Billing 99454 for a month with nine days of transmission is not a gap a better note can close. The descriptor was not met, so the service was not furnished. That is a refund with interest, and the transmission log makes it easy to find.
Two counting rules trip up busy practices. Device supply is a 30-day code while treatment management is a calendar-month code, so a practice that runs both from the first of the month will eventually bill a period with fewer than 16 days. Place of service matters too: the RPM codes are not on the Medicare telehealth list, and NC Medicaid files them with the provider’s usual place of service, not place of service 02.
The record that supports 99457, and the one that does not
99457 pays for the first 20 minutes of treatment management in a calendar month and requires interactive communication during that month. CMS defines it as a conversation in real time, with synchronous two-way audio, which can be enhanced with video or transmitted data. A text exchange, or a review the patient never hears about, does not.
The 20 minutes are wider than the call. CMS has said the time can include the care management work around the conversation, such as interpreting readings and adjusting the plan. It cannot include time already reported under another code, and RPM may be billed alongside chronic care management only when no minute is counted twice.
Start time, end time, who took part, and what was decided.
Name the values reviewed and how the plan changed.
Clinical staff, physician and QHP time, not platform time or patient time.
Noridian’s RPM documentation list asks for the monitored condition, 16 days of data out of 30, medical necessity, consent at the time of service, an FDA-defined device, a live interactive communication, and time documentation.
What RPM denials look like on the remittance
RPM denials arrive in a few shapes, and the remark code usually names the requirement that failed. Payers pair the two codes differently, so read them together.
| What went wrong | What comes back |
|---|---|
| Consent missing or undocumented | RARC N3, missing consent form, or RARC N228, incomplete consent form |
| Documentation does not support necessity | CARC 96, non-covered charge, with RARC N661 |
| Records requested and not produced | RARC M127, missing patient medical record, or RARC N706 |
| Diagnosis does not support the service | CARC 11 with RARC M76 |
| Device supply billed twice in one period | CARC 151, frequency not supported, or CARC 119 |
| Medicare Advantage authorization missing or stale | CARC 197, 284 or 302 |
| Service not covered under the plan | CARC 96 or CARC 204 |
Some denial libraries still list CARC 15 for a missing authorization. X12 deactivated it on May 1, 2018, so expect CARC 197, 198, 284, 296 or 302 instead. A worklist built on the retired code mis-groups the work.
A cluster of CARC 96 with RARC N661 on the management codes means the notes are thin, not that patients were ineligible. CARC 119 or CARC 151 on device supply means two claims went in for one period.
What CMS has proposed for 2027
A July 14, 2026 CMS proposal for the 2027 physician fee schedule would tighten remote monitoring. Remote therapeutic monitoring would be limited to established patients. A separately reportable initiating visit would become a condition of payment. And the clinical staff who furnish the service would have to be employed by the practice, not supplied by a third-party monitoring company.
The rule also proposes to revalue the codes and asks for comment on replacing them with four bundled G codes, citing OIG recommendations. The OIG reported in September 2024 that remote monitoring use grew sharply from 2019 to 2022 and that about 43% of enrollees who received it did not get all three components.
Comments closed on September 14, 2026 and the final rule is expected in early November. None of it changes billing today. The direction is clear: the practitioner’s own record, the practitioner’s own staff, and a real visit that starts the episode. A medical billing services team that handles cardiology revenue cycle management and endocrinology revenue cycle management work sees the same thresholds in blood pressure and glucose programs.
Questions about remote patient monitoring billing
99453 pays for device setup and teaching the patient to use it, once per episode of care. 99454 pays for the device supply and its transmission, once per 30-day period. Both require 16 days of data and one practitioner per period.
Medicare requires at least 16 days of transmitted data in a 30-day period for device supply under 99454. The 2026 code 99445 covers the same supply when the patient transmits on 2 to 15 days. Treatment management codes run on minutes per calendar month.
Medicare requires consent when RPM services are furnished but does not require it in writing. State Medicaid programs are stricter. Alabama and California allow verbal consent while requiring the consent to be documented, so note who obtained it and when.
Yes, when the call meets the definition. CMS describes interactive communication as a real-time conversation with synchronous two-way audio, which can be enhanced with video or transmitted data, so a call counts and a text does not. The month also has to reach 20 minutes of countable time.
99445 is a device supply code that CMS pays for monitoring periods with 2 to 15 days of transmitted data in a 30-day period. It covers patients who do not reach the 16 days that 99454 requires, such as someone coming out of a hospital stay.
No. Medicare allows one practitioner to bill remote monitoring per patient in a 30-day period, even when two practices monitor different parameters. The same limit applies to 99453, once per episode of care.
The bottom line
Setup, device supply and treatment management are different services with different tests, and a claim that blurs them will not hold up in review. The tests are not complicated: 16 days of transmitted data, a consent written into the chart when the service was furnished, and a monthly note showing minutes and a real conversation.
Who is counting your RPM minutes, and where are they written down?
Send us one month of RPM claims with the progress notes and transmission dates. We will check each claim against the descriptor it was billed under and flag the periods that fall short of the 16-day or 20-minute test, with the appeal time left on each.
Request a free RPM billing reviewThis article describes general billing practice and the Medicare and Medicaid rules in force at the time of writing, and code descriptors, thresholds and documentation expectations vary by payer, plan and state program, so confirm them with your MAC before relying on them.
