RESOURCES | BLOG
February 14, 2026

CPT Code Billing for Remote Patient Monitoring in 2026

Master 2026 RPM CPT code billing with Rhythm360's audit-ready documentation guide. Protect revenue and prevent denials — explore the full guide now.

Last updated: October 21, 2026

Key Takeaways

  • CPT code billing for remote patient monitoring in 2026 relies on four core artifacts: transmitted device days, documented management minutes, a signed order, and recorded patient consent.
  • Two new 2026 codes fill previous gaps: CPT 99445 covers 2–15 transmission days and CPT 99470 covers 10–19 management minutes, each with strict mutual-exclusivity rules.
  • Most denials trace back to missing or incomplete artifacts, including raw transmission logs, individual time entries, and predated consent records.
  • Concurrent-billing conflicts and payer coverage gaps must be cleared before submission, because commercial payers are adopting the new codes unevenly.
  • Rhythm360 automates artifact production and mid-cycle tracking so every claim is defensible and revenue capture improves.

Talk With Rhythm360 About Your RPM Billing

New 2026 CPT Codes For Remote Patient Monitoring

CPT 99445, new for 2026, covers remote physiologic monitoring device supply and data transmission when a patient transmits readings on 2–15 days during a 30-day period. It applies instead of 99454 when transmission days fall in that range. The two codes are mutually exclusive for the same 30-day period, and Noridian's 2026 RPM update for Part B providers confirms they cannot both be reported for the same monitoring period. CPT 99445 fills the former gap where 2–15 transmission days produced no device payment at all.

CPT 99470, also new for 2026, covers the first 10–19 minutes of remote physiologic monitoring treatment management in a calendar month and requires at least one real-time interactive communication with the patient or caregiver. It applies instead of 99457 when documented management time falls in that range. CPT 99458 never attaches to 99470. It remains an add-on to 99457 only, and a full 40 minutes of total management time is required before 99458 can be appended.

The practical 2026 decision rules, as confirmed by CMS and Noridian, are:

  • Fewer than 2 transmission days: no device code
  • 2–15 transmission days: 99445
  • 16–30 transmission days: 99454
  • Fewer than 10 management minutes: no management code
  • 10–19 management minutes: 99470
  • 20–39 management minutes: 99457
  • 40–59 management minutes: 99457 + one unit of 99458
  • 60–79 management minutes: 99457 + two units of 99458

A patient who transmits on 18 days one month and 12 days the next requires switching between 99454 and 99445 across billing cycles. Mid-cycle transmission-day tracking is necessary so staff can intervene before the period closes. Verify coverage for 99445 and 99470 with each payer before billing, because commercial payers are not adopting the 2026 codes in lockstep with Medicare.

For a deeper look at how automation supports these new thresholds, see How To Automate CPT Billing For Remote Patient Monitoring.

Code-By-Code Audit-Artifact Map For RPM Billing

Each RPM code ties to a specific audit artifact. The map below explains what a reviewer expects to see and where that record should live.

99453 — Setup And Patient Education

For 99453, an auditor looks for proof that the device was set up and the patient received education. The note should list the device type, the date of setup, the education provided, and the patient's acknowledgment. This information belongs in the EHR encounter note from the setup visit, along with a signed or verbally documented acknowledgment from the patient.

99445 / 99454 — Device Supply And Transmission

For device supply codes, the auditor wants the raw transmission log showing qualifying days, the clinician order, and a consent record that predates the monitoring start date. The log must show 2–15 days for 99445 or 16+ days for 99454. These elements should live in a single normalized record that pulls from the device portal, with the order and consent stored in the patient chart.

99470 / 99457 — Treatment Management

For treatment management, the auditor expects individual time entries rather than a month-end aggregate. Each entry needs the date, duration, activity description, and the staff member with credentials. The record must also show at least one real-time interactive communication. These details should live in a time log in the EHR or RPM platform, with a call or video record that captures date, duration, modality, and clinical substance.

99458 — Additional Management Time

For 99458, the auditor confirms that 99457 appears on the same claim and that total documented time reaches at least 40 minutes. The same time log that supports 99457 should display the cumulative minutes clearly so staff do not need to reconstruct totals.

99091 — Physician/QHP Data Collection And Interpretation

For 99091, the auditor looks for 30 minutes of physician or QHP time personally performed, with no RPM management code billed in the same period. This time should appear in a physician-authenticated note, and a claim-scrubbing edit should confirm that 99091 does not pair with 99470, 99457, or 99458.

Producing all five artifact types on demand creates the main operational challenge. Rhythm360 is a vendor-neutral, HIPAA-compliant cardiac data platform that consolidates data from all major device manufacturers, including Medtronic, Boston Scientific, Abbott, Biotronik, and others, into a single source of truth. The platform tracks device-specific CPT pairings across both billing cycles. Pacemakers and ICDs bill on a 90-day cycle: 93294 (pacemaker professional), 93295 (ICD professional), and 93296 (technical). Physiologic monitors and loop recorders bill on a 30-day cycle: 93297 for implantable cardiovascular physiologic monitors such as CardioMEMS, and 93298 for subcutaneous cardiac rhythm monitors and implantable loop recorders. Each 30-day code is billable once per period and can be split into professional (-26) and technical (-TC) components. Rhythm360 automates data ingestion, report generation, and billing documentation so every artifact listed above is produced reliably and remains retrievable on demand. Other platforms operate in this space, including Murj, Implicity, Rhythm Management Group, and Octagos.

Rhythm360
Rhythm360

Remote Patient Monitoring Billing Requirements 2026 covers the full compliance framework in detail.

See How Rhythm360 Produces Every Audit Artifact

99453 Billing Requirements At Device Setup

CPT 99453 is billed once per episode of care, so the note from that single setup visit must support the entire claim. Documentation must include the device type, the date of setup, the education provided, and the patient's acknowledgment. Clinical staff may perform the setup under general supervision of a physician or qualified healthcare professional, and the supervising QHP must be reachable. The claim depends on a note that identifies who performed the setup, what the patient was taught, and that the device transmitted successfully. A shipment record proves only that a device was sent. The 99453 note has to show that education actually happened.

CPT 99453 cannot be billed more than once per patient enrollment, even when multiple devices are supplied in the same period. Confirm your MAC's position on whether 99453 can be reported once monitoring reaches 2 days rather than 16 on a short first episode.

Consent For Remote Patient Monitoring: Required Elements

Medicare RPM consent may be verbal or written when documented in the patient's medical record before services begin. Some billing guidance recommends written or electronically signed consent for stronger audit protection. Retroactive consent is not permitted, so the chart must show the date consent was obtained before the first billable service.

The consent record must contain:

  • Patient name and consent date
  • Description of the RPM service and how data will be used
  • Device type and basic operating instructions
  • Patient's right to stop participation at any time
  • How the practice responds to abnormal readings
  • Cost-sharing the patient may incur (Medicare Part B deductible and 20% coinsurance generally apply)
  • Identity of the staff member who obtained consent

The consent record must be retrievable by a colleague in under a minute. A status label reading "active" in an enrollment field does not meet that standard. Store consent as a structured EHR note or signed enrollment form. Re-consent is not required for each new 30-day period as long as the original consent covers ongoing monitoring. Payer-specific requirements can be stricter, particularly for Medicare Advantage and commercial plans, so verify them before standardizing the workflow.

99457 CPT Billing: Time Tracking And Communication Rules

CMS defines interactive communication for 99457 as a real-time, synchronous, two-way audio interaction that can be enhanced with video. Asynchronous portal messages, SMS exchanges, and patient portal notes do not qualify, regardless of their clinical relevance. The 20-minute threshold is cumulative across the calendar month and resets on the first of each month.

Time-log requirements for 99457 and 99458 to survive audit:

  • Individual entries for each activity, because a single month-end aggregate note will not survive audit
  • Each entry must identify the staff member and credentials, the activity performed, and the duration
  • The interactive communication must be documented as a separate event noting date, time, duration, modality (phone or video), participants, the substance of the conversation, and the clinical rationale tying the monitored parameter to the diagnosis
  • Total qualifying minutes for the month must be visible without reconstruction
  • Time logged by clinical staff without general supervision by an enrolled QHP does not count
  • Automated data aggregation or algorithmic alerts without human QHP review do not count

Double-counting rules apply across programs. Time documented for RPM management cannot be counted toward CCM, TCM, or BHI time requirements. Each program requires its own separately documented, non-overlapping time log. CPT bars reporting 99091 with 99457 or 99470 in the same period for the same patient.

Concurrent-Billing Conflicts: Pre-Bill Checklist

Use this checklist before submitting any RPM claim:

  • RPM vs. RTM: CMS allows only one remote monitoring program per patient per period, so RPM and RTM cannot be billed for the same patient in the same period
  • One-practitioner rule: only one practitioner may bill RPM for a patient in a given 30-day period, so confirm no other practice has billed RPM for the same patient
  • Global surgery package: RPM codes billed during a global surgery period require verification that the monitoring is for a separate condition outside the surgical package
  • 99091 conflict: confirm 99091 is not on the same claim as 99470, 99457, or 99458
  • 99445/99454 mutual exclusivity: confirm only one device supply code appears per 30-day period
  • 99470/99457 mutual exclusivity: confirm only one starting management code appears per calendar month
  • 99458 attachment: confirm 99458 is attached to 99457 only and that total documented time reaches at least 40 minutes
  • Separate time logs: confirm RPM time is not double-counted against CCM, TCM, or BHI
  • Payer coverage: confirm the patient's plan covers 99445 and 99470 before submitting, because commercial payers are not uniformly adopting the 2026 codes

For a detailed denial-to-fix guide on device supply codes, see CPT 99454 Remote Monitoring Billing: Denial-To-Fix Guide.

Medicare Payment Levels For Remote Patient Monitoring

Payment for RPM codes is locality-specific and set annually by the Medicare Physician Fee Schedule. The 2026 conversion factor differs for qualifying APM participants versus other clinicians, and geographic practice cost indices adjust rates by locality. Medicare Advantage plans must cover Medicare-covered benefits but may apply their own medical policy, prior authorization requirements, and network rules. Commercial payers set their own coverage terms independently, and some have not adopted 99445 and 99470 as of 2026. Practices should verify current rates against their MAC's locality file and confirm coverage terms in each payer contract before billing.

RPM Profitability And Revenue Capture

RPM profitability depends on how much eligible work reaches a clean, payable claim. Before 2026, a patient transmitting RPM data for only 10 days in a 30-day period generated no device payment under the 16-day-only rule, and CPT 99445 now covers that work. Practices that run staff across multiple OEM portals to reconstruct time logs at month end lose hours that could support billable management time. Device-type mismatch denials, such as billing a device supply code against the wrong transmission count or pairing 99458 with 99470, create clean-claim failures that require rework without additional revenue.

In a survey of practices managing their own remote patient monitoring programs, 56% said they were receiving less than half of the eligible reimbursement for RPM services, which shows how much revenue often remains uncollected. The denial-prevention workflow below highlights where that revenue leaks. Rhythm360 automates each checkpoint, and practices using the platform have achieved up to a 300% increase in revenue capture and up to an 80% reduction in critical alert response times by replacing fragmented OEM portal workflows with a single, automated source of truth.

See How Rhythm360 Increases RPM Revenue Capture

Denial-Prevention Workflow For RPM Claims

This sequence connects data transmission integrity to claim readiness. Each step produces or verifies a specific artifact that supports payment.

  1. Device data ingestion and normalization: Ingest transmission data from all OEM portals into a single normalized record. Confirm data completeness, because gaps in transmission do not count as billable days. Rhythm360 achieves greater than 99.9% transmissibility through redundant data feeds, computer vision, and AI-powered extrapolation.
  2. Transmission-day counting against the 99445/99454 split: Count actual days on which the device transmitted at least one data point. Apply the threshold: 2–15 days selects 99445, 16–30 days selects 99454, and fewer than 2 days supports no device code. Check around day 20 so staff can prompt patients and still reach the 99454 threshold before the period closes.
  3. Time-log capture against the 99470/99457 split: Confirm individual time entries are in the record instead of a month-end aggregate. Apply the threshold: 10–19 minutes selects 99470, 20+ minutes selects 99457, and each additional full 20 minutes adds one unit of 99458 to 99457 only. Confirm the interactive communication event is documented separately with date, modality, duration, and clinical substance.
  4. Consent and order verification: Confirm the consent record predates the monitoring start date and contains all required elements. Confirm the clinician order names the condition being monitored and appears in the patient chart before the claim is submitted.
  5. Code selection: Apply the mutual-exclusivity rules. Use one device supply code per 30-day period, one starting management code per calendar month, attach 99458 only to 99457, exclude 99091 when management codes appear, and avoid concurrent RPM and RTM. Confirm payer coverage for 99445 and 99470 if the patient is on a commercial or Medicare Advantage plan.
  6. Claim submission: Submit the claim only after confirming that all artifacts are retrievable on demand. A denial at this stage means one of the five artifacts above is missing or incomplete. RPM billing succeeds or fails on data integrity, which is why each step in this sequence produces a specific record.

Frequently Asked Questions

How Do The 2026 Codes Change RPM Thresholds?

Codes 99445 and 99470 both took effect January 1, 2026. In short, 99445 pays for 2–15 transmission days and 99470 pays for 10–19 management minutes. The sections above explain the thresholds, mutual-exclusivity rules, and documentation requirements in detail.

How Do I Check Current RPM Reimbursement?

Medicare RPM payment comes from the Medicare Physician Fee Schedule and varies by locality and participation status. Medicare Advantage and commercial payers layer their own policies on top. The safest approach is to pull your MAC's locality file for current rates and confirm RPM coverage, including 99445 and 99470, in each payer contract.

How Do The 2026 Codes Affect RPM Profitability?

The new codes convert previously unreimbursed work into billable episodes and reduce write-offs when documentation aligns with the thresholds. The revenue-capture gains described above come from automating artifact production, which removes the manual portal work that drives most denials.

What Documentation Keeps 99457 Claims Audit-Ready?

A 99457 claim needs four documentation categories to stay audit-ready. The record must show individual time entries that identify the staff member, activity, and duration. It must include a separately documented real-time interactive communication event with full visit details. The chart also needs a clinician order and a consent record that predates the monitoring start date. Total qualifying minutes for the month must be visible without reconstruction, and time without QHP general supervision or based only on automated data does not count.

Conclusion: Build Defensible RPM Claims Up Front

RPM billing depends on clean data and complete artifacts. The 2026 code additions, 99445 and 99470, recover revenue from monitoring work that previously went unbilled, and they introduce new mutual-exclusivity rules and artifact requirements that work best with mid-cycle tracking instead of month-end reconstruction. The pattern behind most denials is the same: one artifact is missing, undated, or reconstructed after the fact.

Rhythm360 is the vendor-neutral, HIPAA-compliant cardiac data platform that produces those artifacts reliably. By consolidating data from all major device manufacturers into a single source of truth, automating transmission-day counting, time-log capture, and report generation, and tracking device-specific CPT pairings across both 90-day CIED cycles and 30-day physiologic monitoring cycles, Rhythm360 makes every claim auditable before submission and keeps it defensible if a reviewer asks for documentation years later.

Get A Rhythm360 RPM Workflow Review

Read Next

Related posts