Remote Patient Monitoring Reimbursement in 2026: CPT Codes, Time Rules, and What Changed

Medicare reimburses remote patient monitoring (RPM) in 2026 through a set of CPT codes covering three things: the one-time device setup, the monthly device supply and data transmission, and the clinical time spent managing that data. The headline change this year is that CMS added two new codes — 99445 and 99470 — that lower the old thresholds, so practices can now bill for as few as 2–15 days of data (previously 16 days were required) and for a 10-minute increment of treatment management (previously the floor was 20 minutes). Legacy codes 99453, 99454, 99457, and 99458 all remain in use. Every rate below is a national-average starting point that varies by locality and updates annually — verify current CMS and payer figures before you bill.

This article is educational and operational, written for clinicians and practice administrators. It is not coding, billing, legal, or medical advice. Codes, rates, and coverage rules change; confirm current CMS guidance and each payer's policy before submitting claims.

The short version

• The 2026 RPM code family has six codes. Setup (99453), device supply for 16+ days (99454) or the new 2–15 days (99445), and treatment management for a first 10 minutes (new 99470), a first 20 minutes (99457), or each additional 20 minutes (99458).

• The big 2026 change is lower thresholds. CMS added 99445 (2–15 days of data) and 99470 (first 10 minutes of management), closing the gap for patients who need shorter or lighter monitoring. The old "16-day / 20-minute" floors no longer lock you out of billing.

• Core rules still apply. Generally an established patient, patient consent, a device meeting the FDA definition that transmits data automatically, and only one practitioner billing RPM per patient per 30-day period.

• RPM is not "telehealth." It's a separately billed care-management service, so it isn't bound by Medicare's telehealth geographic or originating-site limits.

• Telehealth flexibilities are extended through Dec 31, 2027 by the Consolidated Appropriations Act, 2026 — relevant context if your RPM program pairs with telehealth visits.

• A bigger shift is coming. CMS is actively reworking how it pays for software- and AI-driven services (a CY2026 request for information and a CY2027 proposed rule). Treat it as a watch item, not settled policy.

What Medicare pays for RPM in 2026

Remote patient monitoring — sometimes called remote physiologic monitoring — is the collection and clinical review of a patient's physiologic data (blood pressure, weight, pulse oximetry, glucose, and similar) using a connected device that transmits readings automatically. Medicare pays for it through Part B under the Physician Fee Schedule, and the payment breaks into three functional buckets: getting the patient set up, supplying the device and its data, and spending clinical time acting on that data.

The table below lists the 2026 RPM codes with approximate national-average payment. Rates are unadjusted national averages that vary by geographic locality and are updated each year; use them for planning, not as the amount you will be paid.

A typical monthly claim for an established RPM patient combines a device-supply code (99454 or 99445, never both in the same 30-day period) with a treatment-management code (99470, or 99457 with 99458 as time accrues). Setup (99453) is billed once when the patient starts.

What changed for RPM in 2026

For years, RPM billing had two hard floors that left real clinical work unpaid: you needed 16 days of transmitted data to bill the device-supply code, and 20 minutes of monthly management time to bill for clinical review. Patients who transmitted for a week, or who needed only a brief check-in, generated no billable RPM even though staff still did the work. The CY2026 Medicare Physician Fee Schedule Final Rule addressed both gaps.

A shorter device-supply code: 99445. Effective January 1, 2026, CMS created 99445 for 2–15 days of data in a 30-day period, reimbursed at roughly $47 nationally. Practices now bill 99445 for 2–15 days and 99454 for 16 or more days — but not both for the same patient in the same 30-day window. This makes RPM viable for episodic monitoring (a post-discharge blood-pressure check, a short medication-titration window) that the old 16-day rule effectively excluded.

A shorter management code: 99470. CMS also added 99470 for the first 10 minutes of monthly treatment management, at roughly $26 nationally, still requiring at least one real-time interactive communication with the patient or caregiver during the month. It gives practices a paid pathway for lighter-touch oversight below the 20-minute 99457 threshold. The 20-minute (99457) and additional-20-minute (99458) codes remain for higher-intensity management.

Broader "interactive communication." CMS has also read the interactive-communication requirement more flexibly, recognizing modes beyond a live phone call. Confirm the current definition and documentation expectations with CMS and your payers, because this area is still settling.

The practical takeaway: 2026 rewards programs that were previously stuck below the old thresholds. If your practice deferred RPM because short monitoring windows didn't pay, the math has changed.

The core billing rules every RPM program must meet

New codes don't change the fundamentals. To bill Medicare for RPM in 2026, a program generally must satisfy each of the following. Because CMS interpretations and payer policies vary, treat this as a checklist to verify locally, not a guarantee of payment.

• An established patient relationship. RPM generally requires the patient to be established with the billing practitioner. Confirm current CMS guidance, as this requirement has shifted over time.

• Patient consent, documented. Obtain and record the patient's consent to RPM, including their cost-sharing responsibility (RPM is subject to Medicare deductible and coinsurance).

• A qualifying device. The device must meet the FDA's definition of a medical device and must transmit data automatically — patient-reported readings typed in by hand don't qualify.

• Enough days of data. At least 2 days of readings in the 30-day period to bill 99445, or 16+ days to bill 99454.

• One biller per patient per 30 days. Only a single practitioner may bill RPM for a given patient in a 30-day period, so coordinate across a care team.

• Documented management time and communication. Treatment-management codes require logged clinical time and at least one interactive communication with the patient or caregiver in the month.

Missing any one of these is the most common reason RPM claims are denied or clawed back on audit, so build the checks into your workflow rather than the claim.

How to bill RPM step by step

Use this sequence as an operational workflow. It is a general process, not a substitute for your certified coder's review or current CMS instructions.

1. Confirm eligibility. Verify the patient is established, has a clinical reason for monitoring, and has Medicare Part B (or a payer that covers RPM). Check whether a Medicare Advantage or commercial plan has its own RPM policy.

2. Obtain and document consent. Explain what RPM is, that cost-sharing may apply, and that they can stop anytime; record consent in the chart.

3. Set up the device and educate the patient — bill 99453 once. Provide the connected device, teach the patient to use it, and confirm data is transmitting automatically.

4. Track the days of data each 30-day period. At month's end, bill 99445 for 2–15 days or 99454 for 16+ days of transmitted data — never both.

5. Log management time and the required communication. Capture clinical staff or clinician time reviewing data and at least one interactive patient/caregiver communication.

6. Bill the management code that matches the time. Use 99470 for a first 10 minutes, 99457 for a first 20 minutes, and 99458 for each additional 20 minutes once 99457 is met.

7. Confirm only your practice is billing RPM for that patient in the period, and keep documentation audit-ready.

RPM vs. RTM: which set of codes applies

RPM has a close cousin — remote therapeutic monitoring (RTM) — and mixing them up creates denials. RPM (99453/99454/99445/99457/99458/99470) monitors physiologic data such as blood pressure, weight, and glucose. RTM (codes in the 98975–98981 family) monitors non-physiologic therapeutic data such as musculoskeletal or respiratory system status, medication adherence, and therapy response, and it can be furnished by a broader set of practitioners, including some who cannot bill RPM. A patient is generally monitored under one framework or the other for a given purpose. If your program spans both physiologic and therapeutic monitoring, have your coding team map each service to the correct family; a dedicated RPM-vs-RTM comparison is a natural next resource in this cluster.

Telehealth coverage through 2027 — and why RPM isn't telehealth

A frequent point of confusion: providers assume RPM lives or dies with Medicare's telehealth flexibilities. It doesn't. RPM is billed as a care-management service, not a telehealth service, so it is not subject to the geographic or originating-site restrictions that historically limited telehealth — RPM can be furnished to a patient at home regardless of those rules.

That said, many RPM programs pair with telehealth visits, so the current telehealth landscape matters. The Consolidated Appropriations Act, 2026 (enacted February 3, 2026) extended major Medicare telehealth flexibilities through December 31, 2027 — including the patient's home as an originating site, removal of geographic limits, audio-only coverage for non-behavioral care, expanded eligible practitioners (physical therapists, occupational therapists, speech-language pathologists, and audiologists), and FQHC/RHC distant-site authority. The in-person requirement for Medicare behavioral-health telehealth is likewise deferred. Because a few provisions have moved on short timelines during recent funding cycles, verify the current status of any specific flexibility before you rely on it.

What's on the horizon: paying for software and AI

The most important medium-term signal for digital-health programs isn't a single code — it's that CMS is rethinking how it pays for software- and AI-driven services. In its CY2026 rulemaking, CMS issued a request for information acknowledging that its practice-expense methodology doesn't capture subscription software, analytics, and the physician work of interpreting AI outputs. For CY2027, a July 2026 proposed rule floated designating dozens of HCPCS codes as "Software as a Medical Service" and reshuffling how they're paid.

This is emerging policy, not settled law — a proposed rule and an RFI, not a final rule. Don't build a 2026 program around it. But if your practice is investing in connected devices, RPM, or AI-enabled tools, it belongs on your watch list, because it signals a multi-year shift in how this category gets reimbursed. Revisit it each PFS and OPPS rulemaking cycle.

How Manifold helps practices build sustainable remote-care programs

Reimbursement is only half of a viable RPM program; the other half is a steady flow of the right patients. Manifold Health operates the preventive-healthcare platform behind Sidewalk, which helps people understand their health data and find the providers who fit their needs — including practices that offer remote monitoring and connected care. For clinicians, that means being discoverable to patients who are actively looking for the kind of proactive, technology-enabled care an RPM program delivers. If you're growing a practice around better patient discovery, a well-run RPM program and a strong digital presence reinforce each other. (For the patient-facing view of what RPM is and how it helps, see our explainer on how remote patient monitoring works.) Manifold connects patients with providers; it does not practice medicine or direct clinical care.

Frequently asked questions

Does Medicare cover remote patient monitoring in 2026?
Yes. Medicare Part B covers RPM under the Physician Fee Schedule through CPT codes for device setup (99453), device supply (99454 for 16+ days or 99445 for 2–15 days), and treatment management (99470, 99457, and 99458). RPM is subject to the standard Part B deductible and coinsurance. Coverage under Medicare Advantage and commercial plans varies by payer.

What are the new RPM CPT codes for 2026?
CMS added two: 99445 for device supply with 2–15 days of data in a 30-day period (about $47 nationally), and 99470 for the first 10 minutes of monthly treatment management (about $26 nationally). Both lower the previous thresholds. The legacy codes 99453, 99454, 99457, and 99458 remain in effect.

How many days of data do you need to bill RPM in 2026?
At least 2 days of transmitted readings in a 30-day period now supports billing 99445; 16 or more days supports 99454. You cannot bill both for the same patient in the same period. This is a change from the pre-2026 rule that required 16 days before any device-supply code could be billed.

What's the difference between 99457 and the new 99470?
Both are treatment-management codes requiring at least one interactive communication with the patient or caregiver in the month. 99470 covers the first 10 minutes of management time (about $26); 99457 covers the first 20 minutes (about $52), with 99458 for each additional 20 minutes. Choose the code that matches the documented time.

Is telehealth still covered by Medicare in 2026 and 2027?
Yes. The Consolidated Appropriations Act, 2026 extended major Medicare telehealth flexibilities through December 31, 2027, including home as an originating site, no geographic restrictions, and audio-only coverage for non-behavioral care. Confirm the current status of specific provisions, which have shifted during recent funding cycles.

Is RPM considered telehealth for billing purposes?
No. Medicare treats RPM as a care-management service, not a telehealth service, so it isn't subject to the geographic or originating-site limits that apply to telehealth. That's why RPM can be delivered to a patient at home regardless of telehealth rules.

Can more than one provider bill RPM for the same patient?
No. Only one practitioner may bill RPM for a given patient in a 30-day period, so coordinate across the care team to avoid duplicate claims and denials.

Key takeaways

• The 2026 Medicare RPM code family spans setup (99453), device supply (99454 or the new 99445), and management (the new 99470, plus 99457 and 99458).

• The defining 2026 change is lower thresholds — 2–15 days of data (99445) and a 10-minute management increment (99470) — which make short or light monitoring billable for the first time.

• The fundamentals still govern: established patient, documented consent, an automatically transmitting FDA-defined device, and one RPM biller per patient per 30 days.

• RPM is not telehealth and isn't bound by telehealth's site rules; separately, telehealth flexibilities run through December 31, 2027.

• Every rate here is a national-average planning figure — verify current CMS rates and each payer's policy before billing, and watch the emerging CMS work on paying for software and AI.

Grow your remote-care program with Manifold

If your practice runs — or is building — a remote patient monitoring program, being discoverable to the patients who want proactive, connected care is what makes it sustainable. List your practice with Manifold to reach patients navigating toward the right providers, and see how better patient discovery supports a durable digital-health program.

This content is for education and general information for healthcare professionals. It is not coding, billing, legal, or medical advice, and it does not guarantee coverage or payment. CPT codes, payment rates, and coverage policies change and vary by locality and payer; verify current CMS guidance and payer policy before submitting claims. CPT is a registered trademark of the American Medical Association.

References

• CMS — Medicare Physician Fee Schedule Final Rule Summary: CY 2026 (PDF). https://www.cms.gov/files/document/mm14315-medicare-physician-fee-schedule-final-rule-summary-cy-2026.pdf

• Federal Register — CY 2026 Payment Policies Under the Physician Fee Schedule (final rule, Nov 5, 2025). https://www.federalregister.gov/documents/2025/11/05/2025-19787/medicare-and-medicaid-programs-cy-2026-payment-policies-under-the-physician-fee-schedule-and-other

• Telehealth.HHS.gov — Billing for remote patient monitoring. https://telehealth.hhs.gov/providers/best-practice-guides/telehealth-and-remote-patient-monitoring/billing-remote-patient

• Telehealth.HHS.gov — Telehealth policy updates. https://telehealth.hhs.gov/providers/telehealth-policy/telehealth-policy-updates

• American College of Physicians — Remote Patient Monitoring Billing, Coding and Regulations. https://www.acponline.org/practice-career/business-resources/telehealth-guidance-and-resources/remote-patient-monitoring-billing-coding-and-regulations-information

• ThoroughCare — 2026 Remote Patient Monitoring CPT Codes. https://www.thoroughcare.net/blog/remote-patient-monitoring-billing-rules

• Prevounce — Remote Care Management: Key FAQs From the 2026 Medicare PFS Final Rule. https://blog.prevounce.com/faqs-from-the-2026-medicare-physician-fee-schedule-final-rule

• Rimidi — CMS Finalizes RPM Code Expansion in 2026. https://rimidi.com/news/2026-rpm-code-expansion

• PYA — Medicare Extends Telehealth Coverage Through 2027. https://www.pyapc.com/insights/medicare-extends-telehealth-coverage-through-2027-updates-and-reminders-for-providers/

• McDermott+ — CMS Proposes RPM Reimbursement Updates, Requests Information on Reimbursing for SaaS. http://www.mcdermottplus.com/insights/cms-proposes-rpm-reimbursement-updates-requests-information-on-reimbursing-for-saas/