Last updated: July 14, 2026
Compliant cardiology RPM billing in 2026 spans two distinct code families. Cardiac-device-specific codes, 93294 through 93298, govern professional interpretation and technical infrastructure for pacemakers, ICDs, CRT-D devices, and implantable loop recorders. CPT 93298 continues to cover remote interrogation device evaluations for up to 30 days under the 2026 Medicare Physician Fee Schedule.
General RPM codes, including 99453, 99454, 99457, 99458, and the two new 2026 codes 99445 and 99470, govern chronic disease monitoring for conditions like heart failure and hypertension. 2026 Medicare national averages run about $22 for CPT 99453, $47 to $52 for 99454 and 99445, and $26 for 99470. The 99445 pathway captures work that used to go unbilled.
Rhythm360 automates documentation for every one of these codes. The platform time-stamps each transmission, records the monitoring period, logs clinical staff interaction minutes, and generates audit-ready interpretation notes without manual entry. Every record carries a complete audit trail, satisfying the OIG's 2025 recommendation that practices validate documentation across all RPM components.
A cardiology practice implanting devices from Medtronic, Boston Scientific, Abbott, and Biotronik cannot manage four separate, non-interoperable portals efficiently. Fragmented CIED workflows are a primary driver of the data integration challenges that slow down timely, high-quality care in cardiology.
Rhythm360 resolves this through a vendor-neutral ingestion layer. It normalizes data via API, HL7, XML, and PDF parsing powered by computer vision and AI-driven extrapolation. Redundant data feeds act as a fail-safe when any OEM server goes down, and gap-filling logic maintains data fidelity across all transmission types.
The result is greater than 99.9% transmissibility. This standard enabled University of Chicago Medicine to review more than 73,000 CIED reports in 2025, averaging over 18,000 reports per quarter. Device technicians log into one dashboard to see a complete, normalized record for any patient, regardless of which manufacturer implanted the device. That consolidation eliminates redundant logins, reduces transcription errors, and gives every clinician a single source of truth.
Device clinics process thousands of transmissions each year. Many generate clinically non-relevant alerts, a volume that drives the burnout and missed events behind alert fatigue. A 2026 five-year study of 402 ICD and CRT-D patients confirmed that automated alert prioritization speeds evaluation of at-risk patients.
Rhythm360's AI triage engine filters non-actionable transmissions before they reach the clinical queue and surfaces only events that need immediate intervention. Picture a Saturday morning: a patient's ILR transmits new-onset atrial fibrillation. Without intelligent triage, that alert sits behind hundreds of routine transmissions. With Rhythm360, the system classifies the event as urgent and routes it to the on-call clinician's phone. By Saturday afternoon, the patient is evaluated and anticoagulation begins, potentially preventing a stroke.
Practices that need additional coverage can add optional 24/7/365 oversight by certified cardiac technicians supervised by physicians. This ensures no critical event goes unreviewed regardless of staffing hours. AI-driven triage reduces alert fatigue while maintaining high data reliability, moving clinical teams from reactive triage to proactive patient management.
Documentation that lives only inside a monitoring platform creates its own data silo. Rhythm360 offers deep, bi-directional integrations with Epic, Cerner, Athenahealth, eClinicalWorks, Greenway Health, and additional systems via HL7. Completed reports, interpretation notes, and billing-ready documentation flow directly into the EHR workflow, eliminating manual re-entry and the transcription errors that come with it.
On-call mobility matters just as much. A cardiologist covering a weekend shift should not need to sit at a specific workstation to review a flagged transmission. Rhythm360's HIPAA-compliant mobile app lets clinicians review transmissions, sign reports, and coordinate care from any location. University of Chicago Medicine clinicians reported addressing issues earlier by calling patients in for evaluation instead of waiting for a three-month visit, a workflow made possible by real-time mobile access.
Implementation, including EHR integration setup, typically takes a few days to a few weeks, minimizing disruption to existing clinical operations.
Revenue leakage in cardiology RPM is structural, not incidental. Before 2026, Medicare required patients to transmit readings on at least 16 unique days per month and clinical staff to document at least 20 minutes of engagement. Work falling short of either threshold generated no reimbursement, even when it was documented and clinically meaningful.
The 2026 CMS Physician Fee Schedule Final Rule added CPT 99445 and 99470 to close those gaps. Capturing the new codes still requires precise, time-stamped documentation of transmission days and staff minutes. Rhythm360 automates that layer, tracking transmission days per patient, accumulating clinical staff time against the applicable threshold, and flagging the correct code before the billing period closes.
A 2025 Health Affairs study of 754 primary care practices found RPM-adopting practices saw a 20% increase in Medicare revenue compared with matched controls, with direct RPM billing as the primary driver. Downstream visits added roughly another 25%. As noted above, practices implementing Rhythm360 have achieved up to 300% more revenue through this kind of optimized CPT capture and new service lines for heart failure and hypertension, without adding significant administrative headcount. Pricing scales with clinic size and usage, and the fast implementation timeline means revenue capture begins quickly.
These five capabilities matter because the alternative, managing OEM portals manually, creates real operational damage. A device technician at a mid-sized EP clinic managing 500 patients across four OEMs starts each morning logging into four separate portals, each with its own interface, alert logic, and export format. Reconciling one patient's transmission history across portals can eat 20 to 30 minutes. Multiply that across a full patient panel and the burden becomes unsustainable.
Alert fatigue compounds the problem. As device populations grow, manual triage workflows get harder to sustain, and when every transmission carries equal visual weight, clinicians develop coping habits like skimming, deferring, or dismissing alerts. Those habits raise the risk of missing a genuinely critical event, such as ventricular tachycardia or a lead malfunction approaching elective replacement indicator status.
Revenue leakage follows directly from these gaps. Without a centralized system tracking transmission days and clinical staff minutes per patient, billing staff cannot reliably tell which patients crossed the 99454 threshold versus the 99445 threshold, or whether interaction time qualifies for 99457 versus 99470. A September 2024 OIG review found that about 43% of Medicare enrollees who received remote patient monitoring, primarily between 2019 and 2022, did not receive all three components. That documentation gap triggers denials and audit exposure.
These pain points explain why the criteria below matter when comparing vendors. A platform that solves the portal, triage, and documentation problems above should also meet the following standards.
These questions come up often during vendor evaluations, so the answers below address them directly.
Can you bill for remote patient monitoring in cardiology? Yes. Cardiology practices can bill for remote monitoring of CIEDs using CPT codes 93294 through 93298 and for chronic disease RPM using codes 99453, 99454, 99445, 99457, 99470, and 99458. Each code family has distinct documentation requirements, and both can apply to the same patient when services are clearly separated.
What documentation is required for audit-ready RPM billing? Audit-ready RPM billing requires records covering consent, orders, device usage, data transmission, and clinical staff time. Vague entries are an increasing audit trigger in 2026.
CIED remote monitoring uses cardiac-specific codes, 93294 through 93298, covering professional interpretation and technical infrastructure for pacemakers, ICDs, CRT-D devices, and implantable loop recorders. These codes carry their own monitoring period requirements, separate from the general RPM codes used for chronic disease monitoring. A cardiology practice can bill both families for the same patient when services are clinically distinct and separately documented. Practices must maintain separate audit trails for each code family to satisfy CMS review requirements.
CMS added two new RPM codes effective January 1, 2026. CPT 99445 covers device supply and data transmission for patients who transmit on 2 to 15 days within a 30-day period, reimbursing at roughly $47, the same rate as 99454, which requires 16 or more days. CPT 99470 covers the first 10 to 19 minutes of clinical staff time per month at about $26, filling the gap left by the 20-minute minimum for 99457. A practice bills either 99445 or 99454 per patient per month, and either 99470 or 99457, never both pairs at once. For heart failure or hypertension patients who previously fell below billing thresholds, these codes open a new revenue path without extra clinical work, just accurate documentation of days and minutes already being logged.
The OIG classified RPM as a compliance risk area in its Fall 2025 Semiannual Report to Congress, and CMS has signaled increased claims review for 2026. Audit-ready documentation needs written patient consent obtained before billing begins, a valid physician order specifying a qualifying chronic condition, FDA-cleared device confirmation, transmission day logs, and time logs showing dates, durations, activity descriptions, and staff identity. For CPT 99445, records must show the exact number of days readings were received. For CPT 99470, records must show precisely 10 to 19 minutes rather than a generic statement. Quarterly internal audits on a random 10 to 20% sample of RPM records are considered best practice for high-volume clinics.
Alert fatigue ranks among the most significant patient safety risks in cardiac remote monitoring. When clinical teams receive hundreds of non-actionable transmissions daily alongside genuinely critical events, the cognitive load increases the odds that a critical alert gets delayed or missed. AI triage classifies each transmission at ingestion, filtering routine signals before they reach the queue and escalating events like new-onset atrial fibrillation, ventricular tachycardia, lead malfunction, or ERI/RRT indicators immediately. This shifts teams from reactive, volume-driven triage to proactive, priority-driven intervention. Practices using AI triage maintain higher patient-to-staff ratios without sacrificing response quality, and faster response times support better outcomes, including earlier anticoagulation, device reprogramming, and hospitalization prevention.
The cardiology practices getting the most value from remote patient monitoring in 2026 share common infrastructure: a single vendor-neutral platform that aggregates CIED data, automates CPT-compliant documentation, triages alerts intelligently, and integrates with the EHR in both directions. Rhythm360 delivers on that checklist, including the transmissibility and report-volume benchmarks described earlier at University of Chicago Medicine, plus automated documentation for the full 2026 CPT code set and AI-powered triage that cuts critical response times by up to 80%.
Fragmented OEM portals, manual documentation, and missed billing thresholds are operational choices, not inevitable constraints. Rhythm360 is built to eliminate all three, and the revenue gains described earlier reflect what practices see once they do.
Schedule a demo and see how Rhythm360 can transform your cardiology RPM billing and clinical workflow.
