Cardiology RPM Billing & CPT Codes: 2026 Guide
Master 2026 cardiology RPM billing with Rhythm360. Get CPT codes, threshold workflows, and margin strategies to maximize practice revenue.
Last updated: October 6, 2026
Key Takeaways
- Cardiology RPM software increases CPT reimbursement by automating time tracking, capturing data transmissions, and enforcing 2026 Medicare thresholds, including new short-duration codes 99445 and 99470.
- Automatic threshold enforcement protects revenue because the platform routes each claim to the correct code based on actual transmission days and clinical management time.
- Cardiology practices running both CIED monitoring and physiologic RPM manage two billing worlds at once, so they need one platform that tracks 90-day and 30-day cycles in a single audit trail.
- The CY2027 proposed employed clinical staff rule creates vendor risk, so practices should choose platforms that support both vendor-supplied and practice-employed clinical models with automated compliance features.
- Rhythm360 is the recommended platform for cardiology practices that want to maximize CPT reimbursement through automated threshold enforcement and comprehensive audit trails.
Talk With Rhythm360 About Your RPM Billing Workflow
Core Cardiology RPM CPT Codes and 2026 Updates
The CY 2026 Medicare Physician Fee Schedule final rule introduced two new RPM codes and increased reimbursement rates across the existing code family. The following definitions mirror the structure CMS uses for coverage determinations.
- 99453 — One-time initial setup and patient education, billed once per episode of care at $21.71 nationally in 2026, up from $19.73 in 2025.
- 99454 — Device supply with daily recording or programmed alert transmission, requires at least 16 days of data in a 30-day period, reimbursed at $52.11 in 2026, up from $43.02 in 2025.
- 99445 (new 2026) — Short-duration device supply. Requires at least 2 days but fewer than 16 days of data in a 30-day period. Reimbursed at $52.11, the same rate as 99454 because CMS determined the practice expense of supplying the device remains the same. 99445 and 99454 are mutually exclusive per patient per 30-day period.
- 99470 (new 2026) — Short-duration treatment management. Covers the first 10 to 19 minutes of clinical management per calendar month, including at least one real-time interactive communication, reimbursed at $26.05. Not additive with 99457.
- 99457 — First 20 minutes of treatment management per calendar month, including at least one real-time interactive communication, reimbursed at $51.77 in 2026.
- 99458 — Each additional 20 minutes of treatment management, reimbursed at $41.42 in 2026. Billable only as an add-on to 99457.
- 99091 — Collection and interpretation of physiologic data by a physician or qualified healthcare professional, at least 30 minutes per 30-day period. Cannot be billed for the same patient and period as 99454.
The 99445 and 99470 codes close revenue gaps that older content ignores. Before 2026, a patient who transmitted 11 days of data or a month where a nurse spent 14 minutes on management produced zero billable revenue. These two codes close that gap. Software that routes claims to the correct code automatically captures that revenue consistently.
For additional context on the full CPT billing workflow, see 7 Essential Strategies to Maximize CPT Code Billing.
Threshold-Enforcement Workflow: Where Most Platforms Fail
Threshold enforcement is the core product requirement for RPM software. A device-data dashboard that displays transmission counts leaves the billing decision to the user. A platform that enforces billing boundaries routes each claim to the correct code automatically.
The operational failure point is specific when a patient hits 15 days of data instead of 16. The correct response is that the software routes the claim to 99445 rather than 99454, and the audit trail shows the exact calendar days of transmission. The correct device-supply code depends entirely on actual transmission days in a given month, not on which code was used previously. So a patient hitting 18 days one month and 12 days the next requires switching codes between billing cycles automatically, without manual intervention.
The same enforcement logic applies to treatment management time. Ten to 19 minutes maps to 99470. Twenty minutes maps to 99457. Each additional 20 minutes maps to 99458. CMS has specifically flagged concern around artificially fragmenting clinical management time to maximize billing under 99457 and 99458. Auditors scrutinize claims that show consistent billing at maximum thresholds every month with little natural variation.
The audit-trail export must contain specific elements to survive a CMS review. First Coast Service Options' Medicare RPM documentation checklist requires documentation for the correct beneficiary and date of service, patient consent, FDA- and HIPAA-compliant device confirmation, and for 99454 specifically: 30-day device supply, 16 qualifying days of physiologic data transmission, automatic transmission, and only one provider per 30-day period. For 99457, the checklist requires at least 20 minutes of monitoring time plus interactive communication via real-time audio or video.
Most RPM audits fail because of small documentation gaps such as missing consent, untracked time, incomplete device data, or no record of patient communication. A platform that prevents those gaps at the point of service is the platform that survives review. Audit-trail export capability belongs on the vendor-selection checklist, not as a feature to evaluate after signing a contract.
See How Rhythm360 Enforces Your Billing Thresholds
CIED Billing Alongside Physiologic RPM: The Two-Clock Problem
A cardiology practice running both CIED monitoring and physiologic RPM manages two distinct billing worlds simultaneously, each with its own code family, billing interval, and documentation requirements. A single patient can sit on three different billing clocks at once. Pacemaker and defibrillator interrogation run on a 90-day window. Loop recorders and pressure sensors run on 30 days. Home physiologic monitoring device supply runs on a 30-day period while management time runs on the calendar month.
The CIED code families are:
- 93294 — Pacemaker remote interrogation, professional component, billed up to once per 90-day period.
- 93295 — ICD remote interrogation, professional component, billed up to once per 90-day period.
- 93296 — Pacemaker/ICD remote interrogation, technical component, shared across 93294 and 93295.
- 93297 — Implantable cardiovascular physiologic monitor (for example, CardioMEMS), device-specific code for hemodynamic monitoring, billable once per 30 days, billable global, with the -26 professional component modifier, or with the -TC technical component modifier.
- 93298 — Subcutaneous cardiac rhythm monitor or implantable loop recorder (ILR/ICM), device-specific code, billable once per 30 days, billable global, with the -26 professional component modifier, or with the -TC technical component modifier.
Codes 93297 and 93298 are device-specific codes. They are not a professional and technical pair. Code 93297 applies to implantable cardiovascular physiologic monitors such as CardioMEMS. Code 93298 applies to subcutaneous cardiac rhythm monitors and implantable loop recorders. Mismatching device type to code, such as billing 93298 for a physiologic monitor or 93297 for a loop recorder, is one of the most common CIED monitoring billing errors and a direct path to denial.
The physiologic RPM codes (99453–99458, 99445, 99470) and the CIED interrogation codes operate under different rules and cannot be conflated. The CPT parenthetical under home monitoring setup and device supply codes instructs that 99453 and 99454 are not reported alongside codes for more specific physiologic parameters, citing 93296 and 94760 as examples. Coding references list 99454 and 99091 among the exclusions under 93297 and 93298.
A cardiology practice needs one platform that tracks both billing worlds in a single audit trail. Rhythm360 provides that unified view.
For a deeper look at CPT performance across both code families, see CPT Code Billing Workflow Optimization for Cardiology RPM.
CY2027 Employed Clinical Staff Proposal: Vendor Risk Questions
On 2026-07-14, CMS issued the CY2027 Medicare Physician Fee Schedule Proposed Rule. The proposal would allow payment for RPM and RTM services only when clinical staff are directly employed by the billing practice, which would prohibit the use of third-party contracted monitoring staff. The comment deadline was 2026-09-14. At publication, this remained a proposal with a proposed effective date of 2027-01-01.
The proposed rule would not bar practices from purchasing software, connected devices, or data platforms from third-party vendors. It targets clinical staffing specifically. Many vendors sell bundled technology-plus-staffing packages that blur this distinction. CMS is also soliciting comments on consolidating the 17 existing RPM and RTM billing codes into four new HCPCS G-codes.
Every cardiology practice should ask each vendor a direct question before signing a 2026 contract. The question is whether the platform can still support the practice with its own employed clinical staff if CMS finalizes the 2027 restriction on contracted clinical staff, while preserving automated time capture, documentation, eligibility tracking, and claims generation.
Rhythm360 supports both vendor-supplied and practice-employed clinical models. The platform's automated threshold enforcement, time logging, and audit-trail generation function independently of staffing model. Practices that sign contracts in 2026 with vendors whose revenue model depends on bundled contracted staffing accept structural risk if the proposed rule is finalized.
Net RPM Margin Framework for Cardiology Practices
Remote patient monitoring produces strong margins for cardiology practices that enforce billing thresholds and control clinical labor costs. The margin calculation is collected reimbursement minus device cost, vendor fee, clinical labor, billing labor, and denied claims.
Using 2026 national non-facility Medicare rates, a practice with 100 active RPM patients generating 99454 and 99457 each month, with 20% also qualifying for 99458, produces approximately:
- $5,211 from 99454 (100 patients × $52.11)
- $5,177 from 99457 (100 patients × $51.77)
- $828 from 99458 (20 patients × $41.42)
This totals about $11,433.50 in gross monthly Medicare reimbursement, or about $137,202 annualized, before program expenses, per HealthArc's illustrative model. Operating cost in an illustrative 100-patient model runs about $53.25 per active patient per month for device cost, platform fee, clinical staffing, and connectivity. That structure produces meaningful contribution before fixed overhead. Break-even rises materially when clinical labor runs higher than modeled.
Margins erode quickly when thresholds go unenforced. A practice with 200 monitored patients that loses one 99454 cycle per patient per quarter faces nearly $38,000 in annual lost revenue from device supply billing alone, before downstream management codes. Software that prevents that loss is the software that keeps RPM profitable.
Practices using Rhythm360 have reported up to a 300% increase in revenue capture and up to an 80% reduction in critical alert response times. University of Chicago Medicine reported improved billing and accountability for patients after integrating Rhythm360, processing more than 73,000 reports annually through the platform.
Vendor Landscape: How Rhythm360 Fits Your Options
Those margin results depend on the platform's ability to enforce thresholds. That capability is exactly where many alternatives that cardiology practices cross-shop fall short. Most platforms focus on vitals tracking or device supply rather than precise enforcement of 90-day and 30-day billing boundaries.
Other platforms operating in the cardiac remote monitoring space include Murj, Implicity, Rhythm Management Group, and Octagos. These vendors serve important roles in the ecosystem. Rhythm360 focuses specifically on unified CIED and physiologic RPM billing with automated threshold enforcement and a single audit trail.
Rhythm360 is the recommended platform for cardiology practices that need to manage both CIED and physiologic RPM billing in a single vendor-neutral, HIPAA-compliant audit trail.
Explore Rhythm360 for Dual CIED and RPM Billing
Common Billing Failures and How Software Prevents Them
Remote patient monitoring carries real clinical labor cost and compliance risk when billing for time that was not actually spent. An OIG review found that of more than $500 million in Medicare RPM payments in 2024, roughly 43% of enrollees did not receive all three required components: device supply, data transmission, and treatment management. That finding now drives the CY2027 proposed rule and active audit contractor scrutiny.
Software-preventable billing failures in cardiology RPM include:
- Device Disconnects Counted as Qualifying Days — A day with no automatic transmission does not count toward the 16-day threshold for 99454 or the 2-day minimum for 99445, regardless of whether the device was powered on. Software must distinguish transmission days from enrollment days.
- Missing Consent Documentation — Missing or vague consent documentation is consistently cited as a top reason RPM claims fail audit review. Consent must be documented before services begin, must reference cost-sharing, and must confirm the one-provider-per-month rule.
- Time-Log Gaps — Detailed documentation of at least 20 minutes of qualifying RPM treatment-management time, including the required interactive communication, is required when billing CPT 99457. Time must be logged contemporaneously, not reconstructed before claim submission. Rounded estimates applied uniformly across a patient panel trigger audits.
- Code-Mismatch Denials — Billing 99454 when a patient transmitted 14 days, billing 93297 for a loop recorder, or billing 93298 for a CardioMEMS device each produce denials that software with device-type mapping can prevent automatically.
- Duplicate or Overlapping Billing — Only one practitioner may bill RPM for a given patient in a 30-day period. Codes 99454 and 99091 cannot be billed for the same patient and period. Codes 99470 and 99457 are mutually exclusive in the same calendar month.
Why Rhythm360 Is The Recommended Platform
Rhythm360 is the recommended cardiology RPM platform for practices that want to maximize CPT reimbursement while maintaining compliance. It is a vendor-neutral, HIPAA-compliant, cloud-based platform that ingests and normalizes data from all major device manufacturers, including Medtronic, Boston Scientific, Abbott, and Biotronik, using APIs, HL7, XML, and computer vision for PDF parsing, with greater than 99.9% data transmissibility.

Rhythm360 automatically tracks device-specific CPT pairings, including 90-day cycles for pacemakers and ICDs (93294, 93295, 93296) and 30-day cycles for physiologic monitors and loop recorders (93297, 93298). This automation prevents device-type mismatch denials and unbilled technical components. The platform enforces billing boundaries automatically, routes each claim to the correct code, and generates an audit trail that documents the exact days of transmission and minutes of clinical time.
Key platform capabilities include:
- Bi-directional EHR integrations with Epic, Cerner, Athenahealth, eClinicalWorks, Greenway Health, and others via HL7
- AI-powered alert triage that can reduce critical alert response times by up to 80%
- Optional 24/7/365 oversight by certified cardiac technicians supervised by physicians
- Integrated Twilio-powered patient messaging with full audit trails for every communication
- A secure, HIPAA-compliant mobile app for remote transmission review and report signing
- Implementation, including EHR integration, that typically completes within days to a few weeks
University of Chicago Medicine reviewed more than 73,000 reports annually through Rhythm360 in calendar year 2025, averaging more than 18,000 reports per quarter, which demonstrates the platform's capacity to handle high-volume CIED monitoring at scale.
Rhythm360 also supports both vendor-supplied and practice-employed clinical models, so practices remain positioned for compliance regardless of how CMS finalizes the CY2027 proposed employed-staff rule.
Frequently Asked Questions About Cardiology RPM
How Much Does Medicare Pay for Remote Patient Monitoring in 2026?
Medicare's 2026 national non-facility rates for the core RPM code family appear in the code table above. The key change for 2026 is the addition of 99445 and 99470, which cover short-duration device supply and treatment management respectively. Rates still vary by locality based on the Geographic Practice Cost Index. A practice that enforces all thresholds and captures all applicable codes for an active patient can generate over $100 per patient per month in recurring Medicare reimbursement from management and device supply codes alone, before CIED monitoring codes billed on separate cycles.
Is Remote Patient Monitoring Profitable for Cardiology Practices?
Remote patient monitoring becomes profitable when practices control threshold enforcement, clinical labor cost, and denial rate. A 100-patient active RPM program can generate over $130,000 annually in Medicare reimbursement from device supply and management codes alone. Margin depends on how much of that revenue the practice actually collects. Practices that rely on manual tracking often see transmission compliance rates fall below 70%, which leaves a large share of billable cycles unclaimed. Clinical labor cost is the largest variable expense and a common reason RPM programs underperform financial projections.
What Is One Disadvantage of Remote Patient Monitoring?
The main disadvantage of remote patient monitoring is the combination of clinical labor cost and documentation burden. RPM requires documented interactive communication with patients, contemporaneous time logs, device transmission records, and consent documentation for each 30-day billing period. When documentation requirements are not met, claims face denial or recoupment at audit. Rhythm360 reduces this disadvantage by automating consent tracking, time logging, transmission day counting, and audit-trail generation, which shifts the compliance burden from manual processes to software-enforced workflows.
What Are the Billing Guidelines for RPM in 2026?
The 2026 RPM billing guidelines, finalized in the CY 2026 Medicare Physician Fee Schedule final rule effective 2026-01-01, define specific requirements for each code. Code 99453 requires documented patient education and device setup, billed once per episode. Code 99454 requires at least 16 days of automatic device data transmission in a 30-day rolling period, documented patient consent, a physician order, and only one billing provider per period. Code 99445 covers 2 to 15 days of transmission in the same 30-day period and is mutually exclusive with 99454. Code 99457 requires at least 20 minutes of clinical management time per calendar month and at least one real-time interactive communication with the patient or caregiver. Code 99470 covers 10 to 19 minutes of management time with the same interactive communication requirement and is mutually exclusive with 99457. Code 99458 requires an additional 20 minutes beyond 99457 and the same interactive communication standard. All treatment management codes require live, two-way synchronous communication. At audit, missing documentation is treated the same as services not rendered.
Does Medicare Cover Remote Cardiac Monitoring?
Medicare covers two distinct categories of remote cardiac monitoring, and each category uses its own code family and billing rules. Physiologic RPM, which monitors blood pressure, weight, pulse oximetry, and similar parameters using connected home devices, is covered under the 994xx code family (99453, 99454, 99445, 99457, 99458, 99470) on 30-day billing periods and calendar months. CIED monitoring, which covers remote interrogation of pacemakers, ICDs, implantable cardiovascular physiologic monitors, and implantable loop recorders, is covered under the 932xx code family (93294, 93295, 93296, 93297, 93298) on 90-day or 30-day intervals depending on device type. The two code families operate under different rules and cannot be combined or substituted for one another. A cardiology practice running both types of monitoring needs a platform that tracks both billing cycles in a single audit trail. Rhythm360 is purpose-built for that dual-billing environment.
Conclusion: Turning Thresholds Into Reliable Revenue
The core problem in cardiology RPM billing comes from fragmented thresholds, unenforced boundaries, and audit trails that do not survive review. A patient who transmits 15 days instead of 16 should generate a 99445 claim. A nurse who spends 14 minutes on management should generate a 99470 claim. A loop recorder patient should generate a 93298 claim. These scenarios represent daily operational reality for cardiology practices that run both CIED and physiologic RPM billing simultaneously.
Rhythm360 enforces every threshold automatically, routes every claim to the correct code, and tracks both billing worlds in a single HIPAA-compliant audit trail. The platform also supports both vendor-supplied and practice-employed clinical models, so practices stay prepared for whatever CMS finalizes in the CY2027 rule. For cardiology RPM programs that need reliable reimbursement, Rhythm360 provides a focused, threshold-aware solution.
Start a Conversation With Rhythm360 About Your Cardiology RPM Program
.avif)