Last updated: July 14, 2026
Practices running legitimate monitoring programs bill less than half of entitled revenue due to gaps in billing workflows rather than fraud. The industry-wide claim denial rate sits between 10-15% in 2026. RPM claims face particular exposure because many practices still bill against outdated thresholds. For cardiology practices with large device populations, the gap between CMS-allowed billing hours and actual monitoring time can represent hundreds of thousands of dollars in annual uncollected revenue.
Staff must log into separate, non-interoperable OEM portals for Medtronic, Boston Scientific, Abbott, Biotronik, and others. This creates data silos that delay alert response and make complete CPT documentation nearly impossible. This fragmentation directly feeds the denial problem. A Kodiak Solutions report found a 25% increase in net revenue leakage at hospitals in 2025 due to higher final denial rates from payors, which shows why pre-submission documentation accuracy matters when data starts out scattered across disconnected sources.
The seven strategies below tackle each of these leakage points in order, starting with the root cause: disconnected device data.
A single aggregation layer eliminates portal sprawl. Data fragmentation across device vendors ranks as a top challenge for RPM platforms because of varying data formats, transmission protocols, and measurement standards. The practical fix is a device-agnostic layer that converts incoming data into one internal format, isolating vendor complexity from clinical and billing pipelines.
Pairing a device abstraction layer with FHIR and IEEE 11073 standards cuts integration friction and lets new devices onboard without touching core pipelines. For cardiology practices, pacemakers, ICDs, loop recorders, CRT devices, and CardioMEMS monitors all feed into one workspace.
Rhythm360 achieves this through API, HL7, XML, and PDF parsing via computer vision, normalizing data from all major OEMs into a single dashboard. A device technician reviews a holistic patient report without switching portals. This saves hours of administrative time and reduces transcription errors that trigger denials.
Automated, audit-ready documentation replaces manual logging. CPT 93298 is billed once per 30-day period on day 31 as the global code covering technical and professional components; modifiers -TC and -26 apply when split between facilities. Required documentation includes patient demographics, device type, monitoring dates, and a clinician interpretation note on device function, programmed parameters, and findings.
CMS requires contemporaneous time documentation for RPM codes, meaning exact start and stop times rather than retrospective estimates. Manual logging against this standard invites errors. Rhythm360's AI-powered alert triage and automated reporting generate timestamped, billing-ready documentation at the point of clinical review, removing the guesswork that causes denials. University of Chicago Medicine used this system to review more than 73,000 reports in 2025, proving automated documentation scales without adding headcount.
Precise code selection replaces the old all-or-nothing rule. Effective January 1, 2026, 99445 covers 2-15 days of transmitted data while 99454 covers 16-30 days per 30-day period. The two codes are mutually exclusive, and most practices have not yet built 99445 into their workflows, forfeiting revenue that was previously unbillable.
The prior 16-day threshold remains the most commonly violated RPM requirement, and it's also the leading cause of 99454 denials and recoupments. That's exactly why real-time transmission tracking matters now more than ever: platforms that count transmission days and flag patients before thresholds are missed prevent denials before they happen, rather than fighting them after submission.
Redundant feeds close data gaps caused by OEM server outages. A single missed transmission can drop a patient below the 16-day threshold, turning a billable month into lost revenue. Standard single-feed setups have no recovery mechanism when an OEM server goes offline.
Rhythm360 uses a redundant feed system as a fail-safe, combined with computer vision OCR for unstructured PDFs and AI-powered gap-filling. The result is over 99.9% transmissibility across the patient population. Clinicians make decisions confident the data represents the most complete view available. UCM's deployment let clinicians review more transmissions daily and catch more abnormalities, a direct result of reliable data rather than gap-driven guesswork.
Bi-directional EHR integration closes the loop between monitoring data and the billing record. Native integration using FHIR and SMART-on-FHIR apps prevents clinicians from bouncing between disjointed interfaces.
Rhythm360 connects bi-directionally with Epic, Cerner, Athenahealth, eClinicalWorks, Greenway Health, and others via HL7. Monitoring findings push into the EHR as structured documentation, while patient demographic and order data pull back to pre-populate billing fields. Onboarding, including integration setup, typically takes a few days to a few weeks.
When monitoring data flows automatically into clinical records with timestamps, organizations capture revenue more reliably and cut leakage. Clinical leadership at University of Chicago Medicine put it plainly: "We have improved billing and accountability for our patients after the integration."
See Rhythm360's bi-directional EHR integration in action, schedule a walkthrough with our team.
Filtering non-actionable noise gets clinically significant events seen first. Alert fatigue is a documented patient safety risk in CIED monitoring. When staff face an overwhelming volume of notifications, critical events, including new-onset atrial fibrillation, ventricular tachycardia, lead malfunction, and ERI/RRT indicators, get delayed or missed.
Rhythm360's AI-powered triage prioritizes significant events and filters non-actionable transmissions before they reach the clinical queue. The platform also offers optional 24/7/365 oversight by certified cardiac technicians supervised by physicians, so a critical arrhythmia flagged on a Saturday morning reaches a clinician the same day. This architecture cuts critical alert response times by up to 80%. As Andrew Beaser, MD, Associate Professor of Medicine at UCM, observed, "Decision support, including AI-assisted decision support, will become increasingly important as data volumes grow."
Capturing every billable code a patient's care plan supports requires monthly tracking, not year-end review. RPM-enrolled patients with two or more chronic conditions generate up to $145.30 monthly when billed for RPM alone, but $211 or more when CCM is added. CMS allows simultaneous billing when staff meet the distinct time and service requirements for each program and track activities separately.
An IDN with 500 eligible patients across five facilities generates an estimated $80,000-$112,000 in monthly Medicare reimbursement through stacking, revenue that fragmented single-facility programs routinely miss. Missing CPT 99458 add-on codes for RPM management beyond 20 minutes leaves significant money unclaimed. Rhythm360's administrative dashboard shows captured and potential revenue in real time, enabling monthly audits that catch stacking opportunities before the billing window closes.
Together, these seven strategies target every stage of the billing cycle: intake, documentation, compliance, data reliability, records, alert response, and code capture. The table below shows what practices achieve when they implement all seven.
The following metrics summarize the measurable impact of these seven strategies when implemented together.
| Metric | Rhythm360 Performance | How It Is Achieved |
|---|---|---|
| Data Transmissibility | >99.9% | Redundant data feeds, computer vision OCR, and AI-powered extrapolation across API, HL7, XML, and PDF sources |
| Critical Alert Response Time Reduction | Up to 80% | AI-powered alert triage with optional 24/7/365 CCT oversight supervised by physicians |
| Revenue Lift | Up to 300% | Automated CPT code capture, bi-directional EHR documentation, and RPM plus CCM stacking workflows |
| Annual Report Volume (UCM, 2025) | >73,000 reports/year | Centralized multi-vendor CIED data ingestion supporting high-volume review without added staff |
| EHR Integration Onboarding | Days to weeks | Native HL7 connections to Epic, Cerner, Athenahealth, eClinicalWorks, Greenway Health, and others |
Use this checklist to assess your practice's readiness for a unified cloud-based cardiology remote monitoring platform.
CPT 93298 is a cardiac-specific code for implantable loop recorder or insertable cardiac monitor remote monitoring. It bills once per 30-day period on day 31 and applies specifically to CIED monitoring, not general physiological RPM. CPT 99454 is a general RPM device supply code for monthly supply of an FDA-cleared device with automatic data transmission, requiring at least 16 days of data within 30 days. The codes serve different populations: 93298 applies to implantable cardiac devices, while 99454 applies to wearable or external RPM devices for conditions like heart failure or hypertension. Both require contemporaneous, audit-ready documentation.
CPT 99445 is a new 2026 CMS device supply code covering RPM when a patient transmits data on 2-15 days within a 30-day period. Before 2026, practices had to meet the 16-day threshold for 99454 or receive nothing for that period. Now, patients who transmit fewer than 16 days of data, whether due to connectivity issues, travel, or non-compliance, generate a billable claim instead of a lost month. CPT 99445 and 99454 are mutually exclusive; only one applies per patient per 30-day period based on actual transmission days.
Rhythm360 addresses the primary causes of RPM and CIED denials through automated, pre-submission compliance checks. The platform tracks transmission counts in real time and flags patients approaching or falling below the 16-day threshold, allowing staff to intervene before the billing window closes. Automated report generation produces timestamped documentation that meets CMS requirements for codes including 93298, 99457, and 99458. Bi-directional EHR integration ensures consent records, physician orders, and diagnosis codes populate the billing record before submission. The administrative dashboard supports monthly audits that catch documentation gaps before they become denials.
Yes. CMS permits simultaneous billing of RPM codes and chronic care management codes for the same patient in the same month, provided the time and activities for each program are tracked separately with no overlap. CMS finalized an approximate 10% increase in CCM payment rates in 2026, making stacking more valuable than in prior years. Practices must maintain distinct time logs, interaction notes, and care plan documentation for each program to withstand audit review.
Implementation, including EHR integration setup, typically takes a few days to a few weeks depending on the complexity of the existing technology environment. The platform supports native bi-directional HL7 connections with Epic, Cerner, Athenahealth, eClinicalWorks, Greenway Health, and other systems. Because Rhythm360 is a cloud-based SaaS platform with pricing that scales by clinic size and usage, practices avoid the capital expense and long deployment timelines of on-premise systems. Staff training focuses on one unified dashboard instead of multiple OEM portals, cutting the learning curve.
Fragmented OEM portals, manual time-logging, and outdated billing workflows cost cardiology practices hundreds of thousands of dollars annually in missed CPT 93298, 99454, 99445, and 99458 revenue. The seven strategies above, from centralizing multi-vendor data ingestion to stacking RPM and CCM billing monthly, address every major leakage point with measurable outcomes. Rhythm360 delivers on the transmissibility, response-time, and revenue results outlined earlier, and University of Chicago Medicine's experience shows those results hold at scale.
The 2026 CPT landscape rewards practices that automate compliance and penalizes those that do not. Every month without a unified cloud platform is another month of preventable revenue loss.
Schedule a demo today and find out how much revenue your practice can recover.
