Last updated: July 14, 2026
Medicare covers remote patient monitoring as a billable service under the Physician Fee Schedule. CMS pays separately for three components: device setup and education, device supply and data transmission, and treatment management. RPM counts as a care-management service, not telehealth, so it carries no geographic or originating-site restrictions.
CMS introduced two new CPT codes effective January 1, 2026. These codes lower prior billing thresholds and expand reimbursement eligibility to patients with lighter engagement patterns. Here is the full 2026 RPM CPT code family with national average rates:
CIED interrogation uses separate codes. CPT codes 93294 and 93296 cover remote electronic analysis of pacemakers and ICDs, while CPT 93297 covers remote interrogation of implantable cardiovascular physiologic monitor systems, including heart failure devices. Audit-ready documentation requires written patient consent, a physician order establishing medical necessity, automated transmission logs confirming the applicable day threshold, and linked ICD-10 diagnosis codes. A September 2024 OIG review found that roughly 43% of enrollees did not receive all three required service components. That gap points directly to the compliance risk built into manual, fragmented billing workflows.
Program costs stack across three categories: devices, platform fees, and staffing. Basic RPM devices run $30 to $100 each, while cellular-enabled devices cost $80 to $200 or more for connectivity that removes patient-side setup steps. Layered on top of hardware, software platform fees add $10 to $40 per patient per month, bringing a full-service RPM solution to $40 to $80 per patient monthly in total.
Medicare reimbursement for a fully enrolled patient generates $150 to $200 or more per month. That leaves a profit margin of $40 to $160 per patient monthly against the cost structure above. Many cardiology practices implementing RPM reach positive ROI with steady enrollment.
The ROI case is strongest in cardiac populations. RPM for congestive heart failure patients reduces readmission rates and avoided hospital costs follow directly from that drop. Practices using Rhythm360 have reported revenue gains up to 300% through optimized CPT code capture, improved staff efficiency, and new RPM service lines for heart failure and hypertension management. Rhythm360's SaaS pricing scales with clinic size, and implementation, including EHR integration, typically takes days to weeks.
The most consistently documented disadvantage of remote patient monitoring is unmanageable alert volume combined with data fragmentation. Together they create alert fatigue and documentation burden that can paradoxically slow down clinical response.
A cross-manufacturer analysis of 2,659 rhythm episodes from 1,710 patients found that 32.9% of episodes in AI-equipped devices were non-actionable and 30.6% were indeterminate. Niraj Varma, MD, PhD, Professor of Medicine and Consultant Electrophysiologist at the Cleveland Clinic, put it this way: "False-positive alerts remain one of the biggest operational challenges in remote cardiac monitoring. Every episode flagged by an implantable cardiac monitor must be reviewed by a clinician, yet even devices equipped with manufacturer AI algorithms still generate a substantial number of non-actionable alerts."
Other documented challenges compound the alert problem:
Rhythm360 tackles alert fatigue directly. AI-powered triage filters non-actionable notifications and prioritizes clinically significant events, cutting critical-alert response times by up to 80%. Redundant data feeds and computer-vision PDF parsing push transmissibility above 99.9%, closing connectivity gaps that used to cause missed events or lost billing. Optional 24/7/365 oversight by certified cardiac technicians adds a clinical layer for practices managing high transmission volumes.
Solving the alert and connectivity problems above depends on understanding how the underlying devices transmit data in the first place. Remote pacemaker monitoring, and CIED monitoring broadly, relies on wireless telemetry between an implanted device and a bedside transmitter or smartphone-connected reader. Implantable cardiac devices, including pacemakers and defibrillators, transmit diagnostic data nightly through this wireless link, letting clinicians spot battery depletion, lead issues, or arrhythmic burden without a clinic visit.
A comprehensive cardiac remote monitoring program supports this full range of devices:
Remote monitoring of CIEDs is linked to fewer hospitalizations, faster clinical decisions, better follow-up adherence, and higher patient satisfaction. Rhythm360 supports all major manufacturers, including Medtronic, Boston Scientific, Abbott, and Biotronik, and maintains transmissibility above 99.9% through redundant data feeds that act as a fail-safe when an OEM server goes down.
Any practice implanting devices from more than one manufacturer ends up juggling separate, non-interoperable portals. Each new vendor requires its own login and workflow, which deepens fragmentation across the cardiovascular service line. Troy Leo, MD, MHCM, FACC, Service Line Leader for Heart and Vascular at Atrium Health, said it directly: "Physicians' time is too valuable to manually process every transmission."
Rhythm360 consolidates all CIED and RPM data into one AI-powered, vendor-neutral dashboard. Key operational capabilities include:
The University of Chicago Medicine (UCM) implemented Rhythm360 to overhaul its cardiovascular remote monitoring program. UCM reviewed more than 73,000 reports in 2025, averaging over 18,000 per quarter. Andrew Beaser, MD, Associate Professor of Medicine at UCM, explained the shift: "We are able to address these issues earlier; rather than waiting for a 3-month visit, we can call patients in for evaluation." Gaurav A. Upadhyay, MD, at UCM added: "We have improved billing and accountability for our patients after the integration."
Schedule a demo to see the alert triage workflow that cut UCM's response times.
Each capability below maps to one of the fragmentation problems described above. Here is how they work together to close those gaps.
| Feature | How It Works | Clinical Benefit | Operational Benefit |
|---|---|---|---|
| Vendor-Neutral CIED & RPM Dashboard | Ingests data from all major OEMs via API, HL7, XML, and computer-vision PDF parsing | Single view of the entire device population, no missed transmissions | Eliminates multiple portal logins and manual data reconciliation |
| AI-Powered Alert Triage | Filters non-actionable alerts, prioritizes clinically significant events in near real-time, optional 24/7/365 CCT oversight | Up to 80% reduction in critical-alert response times | Reduces alert fatigue and staff burnout |
| Bi-Directional EHR Integration | Connects with Epic, Cerner, Athenahealth, eClinicalWorks, Greenway Health, and others via HL7 | Accurate, complete patient records without manual transcription | Eliminates duplicate documentation; implementation in days to weeks |
| Automated CPT Documentation & Billing Support | Tracks billable events against CPT thresholds and generates audit-ready reports | Compliant documentation for every monitored patient | Revenue gains up to 300% through optimized CPT capture |
| Redundant Data Feeds & >99.9% Transmissibility | Fail-safe architecture activates when an OEM server is unavailable; AI extrapolation fills data gaps | No critical events missed due to connectivity failures | Consistent billing eligibility; no gaps that void CPT claims |
| HIPAA-Compliant Mobile App | Secure app for reviewing transmissions, signing reports, and coordinating care from any device | On-call clinicians act on critical alerts immediately, including weekends | Reduces dependence on workstation access; supports distributed care teams |
Practices preparing to deploy or upgrade a cardiac remote monitoring platform should work through these steps before go-live:
Schedule a demo to map your current CPT workflow against the 2026 code changes.
The 2026 Medicare Physician Fee Schedule covers cardiac remote monitoring through two code families. General RPM, including heart failure and hypertension monitoring with connected scales, blood pressure cuffs, and wearable ECG patches, uses codes 99453, 99445, 99454, 99470, 99457, and 99458 (see rates above). CIED interrogation uses codes 93294 and 93296 for pacemakers and ICDs, and 93297 for implantable cardiovascular physiologic monitor systems. Every RPM code requires written patient consent, a physician order establishing medical necessity, automated transmission logs confirming the day threshold, and linked ICD-10 codes. Only one practitioner may bill RPM per patient per 30-day period, though RPM can be co-billed with Chronic Care Management when each program's requirements are met independently.
Rhythm360 is a fully HIPAA-compliant, cloud-based platform. All patient data moving through the platform, including device telemetry, clinical reports, and communications, is handled under HIPAA-required security standards. The integrated communication hub, powered by Twilio, keeps a full audit trail of every patient interaction, including phone call logs, inside each patient record. The mobile app uses secure, encrypted connections so clinicians reviewing transmissions and signing reports remotely meet the same compliance bar as workstation access. This architecture supports audit-ready documentation for every billable event, cutting compliance risk from incomplete or manually generated records.
Implementation, including EHR integration setup, typically takes a few days to a few weeks. Timing depends on practice size, the number of OEM data feeds being connected, and EHR system complexity. The platform integrates bi-directionally with Epic, Cerner, Athenahealth, eClinicalWorks, Greenway Health, and other systems via HL7. Onboarding support covers data feed configuration, staff training, alert threshold setup, and CPT code workflow alignment. Because Rhythm360 is cloud-based and SaaS-priced, there are no large upfront infrastructure costs, and pricing scales with clinic size and usage.
Practices using Rhythm360 have documented the response-time and revenue gains noted earlier, alongside measurable improvements in early intervention. At UCM, the platform enabled review of the 73,000-plus annual reports mentioned above while helping clinicians catch more abnormalities and intervene sooner. Dr. Beaser noted the team can now call patients in for evaluation rather than waiting for a scheduled three-month visit. Dr. Upadhyay reported improved billing and accountability following integration. These results reflect the combined effect of AI-powered alert triage, redundant data feeds, and automated CPT documentation working together.
Rhythm360 runs distinct but integrated service lines for CIED monitoring (Rhythm-CIED) and chronic-condition RPM for heart failure and hypertension (HF/HTN RPM). The CIED line ingests data from all major implantable device manufacturers and supports interrogation reporting for pacemakers, ICDs, CRT devices, loop recorders, and CardioMEMS sensors. The HF/HTN line supports connected weight scales, blood pressure cuffs, and wearable ECG devices, with automated billing support across the full 2026 RPM CPT code family. Both lines operate within the same dashboard, so device technicians, nurses, electrophysiologists, and administrators manage rhythm disorders, heart failure, and hypertension patients from one workspace without switching platforms.
Fragmented OEM portals are a structural source of missed critical events, staff burnout, and revenue leakage, not a minor inconvenience. Organizations that fail to actively pull data or confirm patient transmissions lose both clinical visibility and the ability to bill for services. The 2026 Physician Fee Schedule expanded reimbursement eligibility with new codes 99445 and 99470, but capturing that revenue requires infrastructure that tracks every transmission day and every minute of clinical engagement automatically.
Rhythm360 is that infrastructure. It unifies all CIED and RPM data into one AI-powered, vendor-neutral dashboard, integrates bi-directionally with major EHR systems, automates compliant CPT documentation, and delivers the transmissibility rate cited throughout this guide. Dr. Beaser at UCM put the trajectory plainly: "Decision support, including AI-assisted decision support, will become increasingly important as data volumes grow." Practices that invest in unified monitoring infrastructure now can handle that growth without adding headcount or accepting clinical risk from fragmented workflows.
