Cardiology practices lose thousands of dollars in RPM revenue every year because patients don't transmit data often enough to meet billing requirements.
Under CMS guidelines, CPT 99454 requires at least 16 days of physiologic data transmission during a 30-day billing period. If a patient falls short of that threshold, the claim can't be billed.
For device clinics managing dozens or hundreds of monitored patients, maintaining visibility into transmission activity can quickly become an operational challenge.
Patients miss readings. Devices lose connectivity. Monitoring gaps go unnoticed until the billing cycle is nearly over, or already closed.
The 2026 CMS Physician Fee Schedule introduced new flexibility for shorter monitoring periods, but practices still need a reliable way to track transmission activity and identify patients at risk of missing key billing thresholds.
The stakes are only getting higher. Remote patient monitoring use has grown rapidly in recent years, with Medicare RPM services increasing from roughly 160,000 in 2019 to more than 5.5 million in 2023.
What CPT 99454 Requires
CPT 99454 covers device supply and physiologic data collection for remote patient monitoring.
To bill the code, a patient must transmit data on at least 16 separate calendar days during a 30-day billing period, whether through implanted cardiac devices or other connected monitoring technologies. Multiple transmissions on the same day still count as one qualifying day. The goal is 16 distinct days with transmitted data.
The 30-day billing period is a rolling cycle that begins when monitoring starts. Practices can bill CPT 99454 once per patient per cycle, creating up to 12 billable periods per year.
Understanding the 16-Day Threshold
CMS established the 16-day requirement to support ongoing monitoring rather than occasional data collection. Sixteen days represents just over half of a 30-day period, providing enough data to identify trends and support clinical decision-making.
A day counts if data is transmitted at any point during that calendar day. Even a single transmission late in the evening qualifies. Days with no transmission do not.
How Transmission Days Are Counted
Tracking transmission days becomes more challenging when patients use multiple devices. A patient may be transmitting data from a cardiac implantable electronic device, blood pressure monitor, weight scale, or other connected devices, often through different manufacturer platforms.
For clinic staff, that can mean checking multiple portals and manually tracking qualifying days throughout the billing cycle. Administrative workload is already a significant challenge in healthcare.
According to the American Medical Association, physicians spend nearly two hours on documentation and administrative work for every hour of direct patient care. Adding manual RPM compliance tracking only increases that burden.
Also, practices that rely on passive monitoring and manual tracking consistently see 16-day compliance rates fall below 70%, leaving a significant share of billable cycles unclaimed.
Automated RPM platforms simplify the process by consolidating transmission data into a single view, tracking qualifying days in real time, and identifying patients who may be at risk of missing billing thresholds before the cycle ends.
Where Clinics Lose Revenue
Meeting the 16-day threshold is straightforward in theory.
In practice, it's one of the most common points of failure in an RPM billing cycle. The reasons vary, but they tend to cluster around three problems: patients who disengage, staff who can't track transmission gaps in real time, and billing teams who find out too late.
The Early Drop-Off Problem
Patients don't stop transmitting data because they stop caring about their health.
They forget. They travel. A device battery dies and doesn't get replaced. A Bluetooth connection drops and nobody notices.
For patients managing a chronic cardiac condition alongside the rest of their lives, a week without transmitting can happen without any awareness that a billing threshold is at risk.
By the time a device clinic nurse notices the gap, the 30-day window may already be closed.
A patient who transmitted on 12 days instead of 16 generates no CPT 99454 revenue for that cycle, and if the pattern repeats across even a fraction of a practice's monitored patients, the cumulative loss adds up quickly.
Manual Tracking Gaps
The multi-portal problem compounds the drop-off issue.
When transmission data lives across four manufacturer platforms, clinics often end up working across multiple data silos that make compliance tracking more difficult.
Checking compliance status requires logging into each system separately, cross-referencing dates, and manually counting qualifying days — a process that's time-consuming enough that it often only happens at the end of the billing cycle, when it's too late to intervene.
What a Missed Claim Actually Costs
As per CMS's 2026 Physician Fee Schedule, a single missed CPT 99454 claim costs roughly $47. That number sounds manageable in isolation, but it compounds.
A practice with 200 monitored patients, losing one cycle per patient per quarter, is looking at nearly $38,000 in annual lost revenue from device supply billing alone. And that’s before factoring in the downstream impact on care management codes like 99457 and 99458 that depend on an active monitoring record.
What Changed in 2026
The 2026 CMS Physician Fee Schedule didn't overhaul the 16-day rule. Instead, it built around it.
CPT 99454 remains the standard code for device supply and data collection, with the same threshold and roughly the same reimbursement rate.
What changed is that CMS added new codes to address a gap that had been costing practices money for years.
The New CPT 99445 Code (2–15 Days)
Prior to 2026, there was no billing pathway for patients who transmitted data for fewer than 16 days in a 30-day period.
A patient who monitored for 12 days generated nothing, not because the care wasn't delivered, but because the code structure didn't accommodate it. That meant post-discharge patients, those in short-term monitoring programs, and anyone whose engagement was intermittent fell into a billing dead zone.
CPT 99445 closes that gap. Effective January 1, 2026, practices can bill for monitoring periods of 2 to 15 days, capturing revenue from patient populations that were previously unbillable.
The reimbursement rate is comparable to CPT 99454, and the documentation requirements follow the same logic — transmission logs, physician orders, and patient consent.
One important constraint: the two codes are mutually exclusive within the same 30-day period. If a patient transmits on 16 or more days, the claim goes under 99454. If they transmit on 2 to 15 days, it goes under 99445. Practices cannot bill both for the same cycle.
How the Two Codes Work Together
The practical effect of having both codes is that nearly every active monitoring period is now billable.
A patient who consistently hits 16 days generates CPT 99454 revenue each cycle. A patient who struggles with adherence but transmits on at least 2 days still generates CPT 99445 revenue. The billing dead zone that once swallowed partial-compliance months has effectively been eliminated.
For device clinic teams, this creates a new documentation responsibility. Staff need to know which threshold a patient hit before the claim goes out, and the codes need to be applied correctly.
For example, billing 99454 when a patient only transmitted 14 days is an audit risk.
Accurate day counting isn't just about maximizing revenue anymore. It's about billing the right code.
How Automation Closes the Gap
Understanding the 16-day rule is straightforward. Enforcing it across a full patient panel, every billing cycle, without gaps, is where manual workflows break down.
Automated RPM platforms address this at the point where compliance is most likely to fail, before the billing window closes, not after.
Real-Time Transmission Tracking
The foundation of automated compliance is continuous, unified tracking.
Rather than requiring staff to log into separate manufacturer portals and manually count qualifying days, an automated platform pulls transmission data from all connected devices into a single dashboard.
Every qualifying day is recorded as it happens, giving clinic teams an accurate count at any point in the billing cycle.
For cardiology practices managing patients with CIEDs alongside other monitoring devices, this consolidation is particularly valuable. A patient's data may arrive from multiple sources on any given day, and an automated system captures all of it without staff intervention.
Automated Alerts Before the Window Closes
Real-time tracking is only useful if it triggers action in time to matter.
Automated platforms flag patients who are at risk of missing the 16-day threshold while there is still time to intervene, typically by reaching out to patients to troubleshoot device issues, replace batteries, or re-establish a dropped connection.
The difference between catching a gap on day 12 versus day 29 is a recoverable situation versus a lost claim.
Practices relying on passive monitoring consistently fall below the 70% compliance threshold; active, alert-driven programs push that number significantly higher.
Audit-Ready Documentation
CMS and private payers expect complete transmission logs, physician orders, and patient consent documentation for every billed monitoring period.
Assembling that manually at the end of each cycle creates both administrative burden and audit exposure. Automated platforms generate compliant documentation in real time, maintaining a running audit trail that does not require reconstruction at billing time.
With OIG signaling increased oversight of RPM billing following recent reimbursement expansions, audit-ready records are no longer optional. They are the baseline expectation for any practice running a compliant program.
That scrutiny reflects the growth of RPM itself. Medicare and Medicare Advantage payments for RPM exceeded $500 million in 2024, with nearly one million beneficiaries receiving RPM services.
What to Look for in an RPM Platform
Not all RPM platforms handle compliance tracking the same way.
For cardiology practices where monitoring data flows from multiple device manufacturers and patient engagement is variable, the platform's approach to 16-day tracking matters as much as its clinical features. A few capabilities separate platforms that protect revenue from those that simply collect data.
Multi-Vendor Device Integration
A platform that only pulls data from one manufacturer creates the same fragmentation problem as manual tracking.
Practices need a vendor-neutral solution that consolidates transmissions from all major CIED manufacturers and peripheral monitoring devices into a unified view. If staff still need to log into separate portals to get a complete picture of a patient's transmission days, the compliance risk remains.
Proactive Gap Detection
The platform should identify at-risk patients mid-cycle, not at the end of it.
Look for alert functionality that flags patients who are trending toward a missed threshold with enough lead time to intervene. End-of-cycle reporting is useful for billing; mid-cycle alerts are what actually protect the claim.
Automated Day Counting Across Devices
In multi-device environments, day counting needs to be device-agnostic.
A patient who transmits from a blood pressure cuff on one day and a cardiac monitor on another has transmitted on two qualifying days.
The platform should aggregate across all sources and apply CMS counting rules automatically, without requiring manual reconciliation.
Billing Documentation That Holds Up to Audit
The platform should generate transmission logs and supporting documentation that align with CMS audit requirements, not documentation that needs to be supplemented or reformatted before submission. Complete, timestamped records for every qualifying day are the standard.
Scalability Across a Patient Panel
Compliance tracking for five patients is manageable manually. At 50 or 150, it is not. The platform should handle growing patient panels without requiring proportional increases in staff time, and reporting should surface the patients who need attention without requiring staff to review every account individually.
Building a Compliance-First RPM Program
The 16-day rule is not going away, and CMS scrutiny of RPM billing is only increasing.
Practices that build compliance into their workflows now are better positioned to protect revenue and scale their programs without adding administrative overhead.
The operational reality is that compliance and revenue capture are the same problem. A practice that consistently hits the 16-day threshold captures more reimbursement, generates cleaner claims, and carries less audit exposure. The gap between that practice and one managing the same patient panel manually is almost always the platform.
Octagos consolidates transmission data across device manufacturers, tracks qualifying days automatically, and surfaces at-risk patients before the billing window closes.
See how Octagos can work for your practice today.
References
- Trends in utilization of remote monitoring in the United States - https://pmc.ncbi.nlm.nih.gov/articles/PMC12198758/
- Allocation of physician time in ambulatory practice - https://www.ama-assn.org/practice-management/digital-health/allocation-physician-time-ambulatory-practice?utm_source=chatgpt.com
- RPM Compliance Checklist 2026: Avoid Audits & Denials - https://ccnhealth.com/articles/blog/rpm-compliance-checklist-2026
- Physician Fee Schedule - https://www.cms.gov/medicare/payment/fee-schedules/physician
- Billing for Remote Patient Monitoring in Medicare - https://oig.hhs.gov/reports/all/2025/billing-for-remote-patient-monitoring/