RESOURCES | BLOG
February 2, 2026

Automated CPT Billing for Chronic Disease RPM: 2026 Guide

Rhythm360 automates chronic disease RPM CPT billing for 2026 compliance. Reduce denials & maximize reimbursement. Explore the compliance playbook.

Last updated: October 12, 2026

Key Takeaways

  • Automated CPT code billing for chronic disease RPM enforces CMS thresholds for codes 99453, 99454, 99445, 99457, 99458, and 99470 before claims are generated, closing manual tracking gaps that cause denials.
  • The 2026 code set splits into mutually exclusive pairs for device supply (99445 vs. 99454) and management time (99470 vs. 99457), with separate 30-day device and calendar-month management clocks that require independent tracking.
  • A four-step automated workflow (data ingestion, rule-based tracking, compliance validation, and claim generation) bills only services that meet documented consent, transmission-day, and clinical-minute requirements.
  • Common disqualifiers such as missing consent, insufficient transmission days, non-FDA-cleared devices, and duplicate billing are flagged before submission, reducing audit exposure under the False Claims Act.
  • Rhythm360 delivers vendor-neutral, AI-powered automation that integrates with major EHRs and produces auditable documentation, helping practices achieve up to an 80% reduction in alert response times and up to a 300% increase in revenue capture.

Talk to a Compliance-First RPM Specialist

The 2026 Chronic Disease RPM Code Set

The CY 2026 Medicare Physician Fee Schedule Final Rule (CMS-1832-F) finalized six codes for chronic disease RPM and grouped them into device and management pairs that cannot overlap. The table below shows how the six codes split into two mutually exclusive pairs, one for device supply and one for management time, and what each code requires before it can be billed.

CPT CodeDescriptionThreshold2026 Non-Facility Rate
99453One-time device setup and patient educationOnce per episode of care; requires at least 2 days of monitoring~$21.71
99445Device supply and data transmission, 2–15 days2–15 transmission days in a 30-day period; mutually exclusive with 99454~$47–$52
99454Device supply and data transmission, 16–30 daysAt least 16 transmission days in a 30-day period; mutually exclusive with 99445~$52.11
99470RPM treatment management, first 10 minutes10–19 minutes per calendar month; requires live interactive communication; cannot be billed with 99457~$26.05
99457RPM treatment management, first 20 minutes20+ minutes per calendar month; requires live interactive communication; cannot be billed with 99470~$51.77
99458RPM treatment management, each additional 20 minutesAdd-on to 99457 only; not an add-on to 99470; billable up to 2 units per month~$41.42

Key mutual-exclusivity rules: 99445 and 99454 cannot both be billed for the same patient in the same 30-day period, and 99470 and 99457 cannot both be billed in the same calendar month. Additionally, device codes run on a 30-day period while management codes run on the calendar month, so teams must track two separate clocks for every enrolled patient.

How to Automate CPT Billing for Remote Patient Monitoring provides additional context on operationalizing this code set.

How Automated Eligibility Tracking Works: The Four-Step Workflow

Because those thresholds and exclusivity rules must be checked for every patient every cycle, Rhythm360 converts RPM eligibility tracking from a manual spreadsheet exercise into a four-step rules-based process.

Step 1: Data Ingestion

The platform ingests patient-generated physiologic data from connected devices such as blood pressure cuffs, weight scales, glucose meters, and pulse oximeters across all major manufacturers. Rhythm360 normalizes disparate data streams using API, HL7, XML, and AI-powered PDF parsing via computer vision. Redundant data feeds push transmissibility above 99.9%.

A reading the patient types into a portal does not count as an RPM data day. A data day requires the device to send a reading automatically and upload it electronically to a secure location the billing practitioner can review. The ingestion layer enforces this distinction at the point of data receipt.

Step 2: Rule-Based Tracking

The system counts transmission days per patient per 30-day device cycle and accumulates clinical minutes across all qualifying staff in the calendar month. These two clocks, the 30-day device window and the calendar-month management window, do not always align, so the platform tracks them separately for every patient. Staff time accumulates across the whole care team, but each minute is counted only once.

Step 3: Compliance Validation

Before any claim is generated, the system checks six conditions: documented patient consent, an established patient relationship, device FDA-clearance status, transmission day count against the applicable threshold, management minute count against the applicable threshold, and co-billing restrictions. Consent is the most common failure point, because CMS requires documented patient consent before RPM services begin and does not permit retroactive consent under Medicare. If any of the six checks fails, the claim is flagged for human review rather than submitted.

Step 4: Claim Generation

Claims that pass all validation checks are generated with the correct code selection, 99445 or 99454 based on actual transmission days and 99470 or 99457 based on documented management minutes, and then routed into the practice's billing workflow. Human review remains required for patients who fall short of transmission thresholds mid-month, ambiguous clinical minute allocations, and consent exceptions. Automation surfaces these cases and presents the facts so staff can make compliant decisions.

See the Four-Step Workflow in Action

The 16-Day vs. 2-Day Transmission Window Problem (99454 vs. 99445)

The correct device-supply code depends entirely on actual transmission days in that specific month. A patient who transmits on 18 days in March and 12 days in April requires 99454 in March and 99445 in April.

Manual tracking systems routinely miss this switch and bill 99454 by default, creating the exact pattern, identical code selection regardless of actual days, that Medicare Administrative Contractors flag when comparing device transmission logs against billed codes.

Automated software tracks both windows in real time. When a patient reaches day 14 without a transmission, the platform generates an alert to clinical staff and can trigger automated patient outreach through Rhythm360's integrated Twilio-powered communication framework. If the patient reaches the end of the 30-day period with 15 transmission days, the system selects 99445. If the patient reaches 16, it selects 99454. The decision is made on documented fact.

The HHS OIG's August 2025 data snapshot on RPM billing flagged device charges without a corresponding month of management time and overlapping claims from multiple providers as patterns under review. Proactive transmission-day tracking reduces the first risk by ensuring device codes are only generated when the data actually supports them.

RPM and CCM Co-Billing: Time-Splitting Rules That Prevent Denials

RPM and CCM may be billed concurrently in the same month when each service is medically necessary and independently satisfies its requirements, with actual activities and time recorded separately and no time or effort counted twice. The same clinical minute cannot count toward both programs.

In practice, a 20-minute RPM management session and a 20-minute CCM coordination session must be documented in separate time logs with distinct timestamps, activities, and staff identifiers. Practices must maintain a separate interpretation log for cardiac device monitoring time as well, because time spent interpreting implanted cardiac device data for codes 93294–93298 cannot also be counted toward RPM treatment management codes 99457 or 99458.

Rhythm360 enforces this during compliance validation by maintaining separate time logs for each program. When a clinical staff member logs time, the system allocates it to the designated program and prevents the same minute from appearing in a second program's accumulation. To avoid overlapping-minute denials when stacking RPM and CCM, practices should take three steps: document patient consent for each service, log RPM data-review minutes and CCM coordination minutes in separate timestamped records, and meet each threshold with its own distinct minutes.

For hypertension and heart failure panels where RPM and CCM co-enrollment is clinically appropriate, see CPT Code Billing for Hypertension Remote Monitoring for program-specific guidance.

What Disqualifies an RPM Claim

The HHS OIG and Recovery Audit Contractors reviewing RPM claims look for specific failure modes that signal noncompliance. The most common disqualifiers are:

Automated RPM billing software flags each of these conditions during the compliance validation step before claim submission. Where human review is still required, such as when a patient's transmission count is borderline or consent documentation is incomplete, the platform surfaces the case to the billing team rather than generating a claim that will be denied or later recouped. The False Claims Act defines liability to include reckless disregard of claim accuracy, so pre-submission validation functions as a legal control as well as an operational safeguard.

How Automated RPM Billing Integrates with EHR and RCM Workflows

Compliance-first automation delivers full value only when it fits into existing clinical and billing systems. Rhythm360 offers bi-directional EHR integration with Epic, Cerner, Athenahealth, eClinicalWorks, and Greenway Health, with onboarding typically completed in days to a few weeks.

Data flows in both directions: device readings and compliance documentation write back to the patient record, and patient demographic and consent data flow into the platform to support eligibility tracking. Rhythm360 automates CPT code capture and generates the documentation that supports defensible claims, including transmission logs, time logs, consent records, and interactive communication notes.

The billing team retains ownership of the claim and submits it through the existing revenue cycle workflow. Rhythm360 does not manage revenue cycles; it produces the structured, auditable documentation that allows the billing team to submit claims with confidence. Documentation for a 99457 claim must include a time log with date, duration, and activity description for each entry, plus a separately documented interactive communication event noting date, time, duration, modality, and participants. Rhythm360 captures and organizes all of these elements automatically.

Check Your EHR Integration Options

Chronic Disease RPM Codes vs. Cardiac Device Monitoring Codes

Chronic disease RPM codes and cardiac device monitoring codes often appear together in cardiology workflows, yet they represent distinct code families with different covered devices, billing intervals, and clinical purposes.

The chronic disease RPM codes cover physiologic data from connected home devices such as blood pressure cuffs, weight scales, glucose meters, and pulse oximeters. They bill on a 30-day device cycle and a calendar-month management cycle.

The cardiac device monitoring codes cover implanted and subcutaneous devices:

  • 93294 — Professional code for remote interrogation of implanted pacemakers (up to 90-day billing window)
  • 93295 — Professional code for remote interrogation of implantable cardioverter-defibrillators (up to 90-day billing window)
  • 93296 — Technical code for remote interrogation of pacemakers and ICDs (up to 90-day billing window)
  • 93297 — Device-specific code for implantable cardiovascular physiologic monitors; billable once per 30-day interval; can be billed global, with modifier -26, or with modifier -TC
  • 93298 — Device-specific code for subcutaneous cardiac rhythm monitors and implantable loop recorders; billable once per 30-day interval; can be billed global, with modifier -26, or with modifier -TC

Codes 93297 and 93298 are device-specific codes rather than a professional and technical pair. 93297 applies to implantable cardiovascular physiologic monitors, and 93298 applies to subcutaneous cardiac rhythm monitors and loop recorders. Time spent interpreting implanted cardiac device data for codes 93294–93298 cannot also be counted toward RPM treatment management codes 99457 or 99458. The two code families follow different billing intervals and must be kept in separate reimbursement models. For device-specific billing guidance, see Best Practices for CPT Code Billing CIED Devices.

Why Rhythm360 Is Built for Compliance-First RPM Billing

Rhythm360 is a vendor-neutral, AI-powered platform that ingests and normalizes data from all major device manufacturers, including Medtronic, Boston Scientific, Abbott, Biotronik, and others, into a single compliance-ready workflow. The platform automates CPT code capture, tracks eligibility against CMS thresholds in real time, generates compliance documentation, and integrates bi-directionally with major EHR systems.

Rhythm360
Rhythm360

Other platforms operating in this space include Murj, Implicity, Rhythm Management Group, and Octagos. Rhythm360 focuses on automated eligibility tracking, compliance validation before claim generation, and auditable documentation that supports the billing team’s existing workflow, without requiring manual spreadsheet reconciliation across device cycles and calendar months.

Practices implementing Rhythm360 have achieved up to an 80% reduction in critical alert response times and up to a 300% increase in revenue capture and profitability. The HHS OIG has made clear that RPM billing patterns are under active scrutiny. For practices running chronic disease RPM at scale, a compliance-first automation platform is the only defensible strategy.

Before diving into specific implementation questions, many teams want a concise recap of how these rules play out in daily operations. The following FAQs build on the sections above and tie the code set, workflow, and integration model together.

Frequently Asked Questions

How Does Automated RPM Billing Track 99454 Transmission Days?

Automated RPM billing platforms ingest device data directly from connected home monitoring devices such as blood pressure cuffs, weight scales, glucose meters, and pulse oximeters, and count each day on which the device automatically transmitted a reading to a secure, reviewable location. A day counts only when the device sends the reading electronically; patient-entered portal readings do not qualify.

The platform tracks this count per patient per 30-day device cycle, separate from the calendar month. When a patient approaches the end of a 30-day period with fewer than 16 transmission days, the system alerts clinical staff and can trigger automated patient outreach. At the close of the period, the system selects 99454 if 16 or more days were recorded or 99445 if 2–15 days were recorded. The correct code is determined by actual documented transmission days in that specific period.

What Is CPT 99470 and When Is It Billable in 2026?

CPT 99470 is a new 2026 RPM treatment management code covering the first 10 to 19 minutes of monthly management time. CMS added it in the CY 2026 Medicare Physician Fee Schedule Final Rule (CMS-1832-F) to make shorter but genuine management interactions billable.

To bill 99470, the practice must document at least 10 minutes of qualifying management time and at least one real-time, synchronous two-way audio interaction with the patient or caregiver during the calendar month. Asynchronous messages, portal notes, and automated check-ins do not satisfy the interactive communication requirement. CPT 99470 cannot be billed in the same month as 99457, because once documented management time reaches 20 minutes, 99457 applies. CPT 99458, the add-on for each additional 20 minutes, follows 99457 only and cannot be added to 99470.

Can You Bill RPM and CCM for the Same Patient?

RPM and CCM can be billed for the same patient in the same calendar month when each service independently meets its requirements and is independently documented. The critical rule is that the same clinical minute cannot count toward both programs.

A staff member who spends 20 minutes reviewing RPM device data and managing the patient's blood pressure, and then spends a separate 20 minutes on CCM care coordination activities, can support billing for both when those activities are logged in separate time records with distinct timestamps and activity descriptions. If a single interaction involves both RPM and CCM activities, the practice must allocate actual time to each program without duplication. Rhythm360 enforces this by maintaining separate time logs for each program during the compliance validation step, preventing the same minute from accumulating toward two thresholds simultaneously. RPM and remote therapeutic monitoring (RTM) cannot be billed together for the same patient in the same period.

What Disqualifies an RPM Claim?

The disqualifiers listed earlier, missing consent, insufficient transmission days, non-FDA-cleared devices, no live interactive communication, duplicate billing, cross-program time, and no established patient relationship, are the same conditions the platform flags before submission. Automated RPM billing software checks for each of these issues and routes any unresolved case to human reviewers instead of generating a claim.

How Does Automated RPM Billing Integrate with My EHR?

Rhythm360 offers bi-directional integration with Epic, Cerner, Athenahealth, eClinicalWorks, Greenway Health, and other systems via HL7. Bi-directional means data flows in both directions: patient demographic, consent, and care plan data flow from the EHR into Rhythm360 to support eligibility tracking, and device readings, transmission logs, time logs, and compliance documentation write back to the patient record in the EHR.

This approach eliminates manual data transcription between systems and ensures the billing team has access to complete, auditable documentation when submitting claims. Onboarding, including integration setup, typically takes from a few days to a few weeks. Rhythm360 does not manage the revenue cycle; the billing team retains ownership of claim submission and payer relationships. The platform's role is to automate CPT code capture and produce the structured documentation that makes each claim defensible under audit.

Conclusion: Compliance-First Automation as a Billing Standard

Manual RPM billing tracking using spreadsheets, manual transmission day counts, and informal time logs creates denial risk and revenue leakage. The 2026 chronic disease RPM code set is more complex than its predecessor, with two device-supply codes that are mutually exclusive, two management codes that are mutually exclusive, separate 30-day and calendar-month tracking clocks, and co-billing rules that require minute-level documentation separation.

The HHS OIG has flagged RPM billing patterns for additional oversight, and audit contractors are actively comparing transmission logs against billed codes. Rhythm360 turns eligibility tracking, compliance validation, and claim generation into a rules-based, auditable system. The platform ingests device data, counts transmission days per patient per cycle, accumulates clinical minutes in separate program logs, validates consent and co-billing restrictions before any claim is generated, and routes compliant claims into the billing team's existing workflow.

As noted earlier, practices on Rhythm360 have seen up to an 80% reduction in alert response times and up to a 300% increase in revenue capture. Automation ensures that every eligible service is billed correctly, every cycle.

Start a Compliance-First RPM Billing Review

Read Next

Related posts