RESOURCES | BLOG
January 27, 2026

Maximize Remote Heart Rhythm Monitoring CPT Codes in 2026

Boost revenue from cardiac remote monitoring CPT codes in 2026. Rhythm360 delivers the workflows and expertise to maximize every claim.

Last updated: October 16, 2026

Key Takeaways For 2026 Cardiac Remote Monitoring

  • Remote heart rhythm monitoring programs most often lose revenue to documentation gaps, device-type mismatches, and missed transmission thresholds, not coverage limits.
  • The 2026 CPT 99445 code now pays for 2–15 day monitoring episodes at the same rate as 99454, which covers 16–30 days.
  • Each CPT code carries specific thresholds, common failure modes, and concrete documentation fixes that prevent automatic denials and audit exposure.
  • Strong documentation includes day-by-day transmission logs, detailed time logs with interactive communication, device-type verification, and consent recorded before services start.
  • Rhythm360 tracks devices, documentation, and billing across major manufacturers so practices capture compliant revenue consistently.

Talk With Rhythm360 About Your Monitoring Program

Key 2026 CPT Changes For Cardiology Remote Monitoring

The CY 2026 Physician Fee Schedule final rule (Federal Register document 2025-19787, published November 5, 2025) created two new RPM codes effective January 1, 2026: CPT 99445 and CPT 99470. CPT 99445 covers device supply with daily recordings or programmed alert transmissions for 2–15 days in a 30-day period. CPT 99470 covers the first 10–19 minutes of RPM treatment management in a calendar month.

CPT 99445 closes a revenue gap that previously affected many practices. Before January 1, 2026, a patient who transmitted data for only 12 days in a 30-day period generated no billable device-supply code, so the entire period went unpaid. CMS introduced 99445 to address the previous 16-day rule gap for acute post-operative monitoring or medication titration episodes. CMS set 2026 national-average non-facility Medicare reimbursement for 99445 at parity with 99454, both around $52, reflecting CMS's view that shorter-duration monitoring carries equivalent clinical and administrative value. Practices that have not yet configured their billing software to recognize 99445 for short-duration episodes leave that revenue unbilled.

Code-By-Code Playbook: Thresholds, Risks, And Fixes

CPT 99453: Setup And Patient Education

CPT 99453 covers remote monitoring setup and patient education on use of equipment. CPT 99453 is billed once per patient per device by a qualified health professional or clinical staff.

Threshold: Billed once per episode of care.

Failure Mode: Billing more than once per episode or billing without documented consent on file before services begin. CMS requires patient consent, verbal or written and documented, before RPM services begin; Medicare does not allow retroactive consent.

Documentation Fix: Capture consent before the episode starts. Include the date, staff name, and education content delivered in the setup note.

CPT 99454: Meeting The 16-Day Transmission Threshold

CPT 99454 requires at least 16 days of readings in a 30-day period.

Threshold: The device must transmit physiological data on at least 16 days out of a 30-day billing cycle. If data is transmitted for 15 days or fewer, CPT 99454 cannot be billed for that period.

Failure Mode: ASP-RCM Solutions describes a common failure mode called "the 16-day cliff," in which CPT 99454 is dropped for an entire 30-day period because the device fell a day or two short of the 16-day data threshold and no one flagged it for the next billing window. Industry data indicates that 20% to 30% of RPM claims are delayed or rejected on initial submission due to failure to verify the 16-day transmission threshold or lack of clinical time logs.

Documentation Fix: Maintain a day-by-day transmission log that reconciles to the claim. Run a mid-month check around day 20 to identify patients trending toward 2–15 days and route them to 99445 for that period.

CPT 99445: Short-Duration Monitoring Episodes

CPT 99445 covers device supply with daily recordings or programmed alert transmissions for 2–15 days in a 30-day period, effective January 1, 2026.

Threshold: 2–15 days of data transmission in a 30-day period.

Failure Mode: CPT 99454 and 99445 are mutually exclusive. Code 99454 applies when a patient transmits device data for 16 or more days in a 30-day period, while 99445 applies for 2 to 15 days, and only one may be billed per period. Billing both 99454 and 99445 in the same 30-day period triggers an automatic mutual-exclusivity edit rejection.

Documentation Fix: Configure billing software to default up to 99454 only when transmission data supports it. Run a pre-bill audit on any claim involving 99445 for the first two full billing cycles after implementation, since new codes attract more payer scrutiny in their first year.

CPT 99457 And 99458: Time Tracking And E/M Separation

CPT 99457 covers the first 20 minutes of RPM treatment management per calendar month. CPT 99458 is an add-on for each additional 20 minutes beyond the initial 99457 in the same calendar month.

Threshold: The 20 minutes of RPM treatment-management time under 99457 is cumulative across the calendar month and does not have to be met in a single session. The count resets on the first of each month regardless of when the claim is submitted.

Failure Mode: Common 99457 denial reasons include no interactive communication documented (CO-16 or CO-50), time below the 20-minute threshold (CO-151), and patient consent not on file (CO-16 or CO-50). Double-counting monitoring time against E/M encounter time creates a separate audit risk. E/M visits and chronic care management can run concurrently with RPM in the same month. However, RPM treatment management time must be clearly separated from the E/M encounter. CCM time thresholds also cannot share minutes with 99457, 99458, or 99470.

Documentation Fix: Maintain a time log with date, duration, activity description, and the name of who performed the activity. Document the interactive communication event separately. CMS defines interactive communication for 99457 as a real-time, synchronous, two-way audio interaction, which can be enhanced with video. Asynchronous messages, patient portal notes, and SMS exchanges do not qualify even when medically relevant and well documented. Round-number time logs may invite scrutiny. Use specific, activity-level entries rather than unsupported aggregate totals.

CPT 93294, 93295, And 93296: Pacemaker And ICD Remote Interrogation

CPT 93294 is the professional component for remote pacemaker interrogation. CPT 93295 is the professional component for remote ICD interrogation. CPT 93296 is the technical component covering remote data acquisition, receipt of transmissions, technician review, technical support, and distribution of results, applicable to both pacemaker and ICD systems.

Threshold: Pacemaker and defibrillator remote monitoring (CPT 93294/93295/93296) runs on a 90-day monitoring period and should be billed once per period, not monthly.

Failure Mode: Billing on the wrong cycle, such as monthly instead of once per 90 days. Modifier 26 does not apply to CPT 93296 because a separate professional component code already exists for each device family. Mismatching the professional code to the device, such as billing 93294 on a defibrillator or 93295 on a pacemaker, is a frequent denial trigger.

Documentation Fix: Record the device type and model and the implant date. Also document the monitoring period start and end dates. Include at least one transmission received and reviewed within the 90-day period, the specific data elements reviewed, and a dated, signed report. A transmission reviewed without a dated, signed report does not support CPT 93294, which pays for analysis, review, and a report.

CPT 93297: Implantable Cardiovascular Physiologic Monitor

CPT 93297 covers remote monitoring of an implantable cardiovascular physiologic monitor, such as a CardioMEMS pulmonary artery pressure sensor, on a cycle of up to 30 days. It is billable once per 30 days and can be reported global, with modifier -26 for the professional component, or with modifier -TC for the technical component.

Threshold: CPT 93297 is reported once per 30-day period, and CMS applies a medically unlikely edit of one unit per date of service. Consecutive periods must not overlap.

Failure Mode: Duplicate global billing is a key audit risk. If a monitoring company has already billed 93297-TC directly to Medicare, a practice that then submits the global 93297 duplicates that charge, and MACs recoup the difference on audit. Applying 93297 to a loop recorder is a device-type mismatch, because loop recorders bill under 93298.

Documentation Fix: Produce a dated, signed review and report naming the reviewer and clinical decisions made. Include the explicit 30-day date range. When billing 93297-26 only, note which entity supplied the equipment and billed the technical component.

CPT 93298: Subcutaneous Cardiac Rhythm Monitor And Loop Recorder

CPT 93298 covers remote monitoring of a subcutaneous cardiac rhythm monitor, including implantable loop recorders, on a cycle of up to 30 days. Like 93297, it is billable once per 30 days and can be reported global, -26, or -TC.

Threshold: Billable once per 30-day cycle.

Failure Mode: Applying 93297 to a loop recorder or 93298 to a physiologic monitor. A subcutaneous cardiac rhythm monitor is identified by implant CPT code 33285, which points to remote interrogation code 93298 rather than 93297. Missing a signed review is the other primary denial trigger.

Documentation Fix: Confirm device type via the implant code, since 33285 points to 93298. Produce a signed review naming the reviewer and clinical decisions. Include the explicit 30-day date range.

Billing CPT 93228 And 93229 Together For MCOT

Practices can bill CPT 93228 and 93229 together when they perform both the interpretation and the technical monitoring service. CPT 93228 is the professional component of mobile cardiovascular telemetry, paying the interpreting physician for reviewing transmitted ECG data and signing the interpretive report. CPT 93229 is the technical component covering device supply, patient hookup, attended surveillance, and daily data transmission. When both services are furnished, 93228 and 93229 are reported as separate companion codes on their own claims without -26 or -TC modifiers.

A practice can bill CPT 93228 and CPT 93229 together only when it performs both the interpretation and the technical monitoring service. Holding a contract with a monitoring vendor is different from running the surveillance center. Billing CPT 93228 alongside Holter codes 93241 or 93245 for the same monitoring period is an unbundling error.

A compliant 93228 record requires a signed physician order naming MCT that predates the monitoring start date, a signed interpretive report, evidence of event response, and patient consent documentation. CMS Billing and Coding Article A60279 requires that the medical record connect the monitoring service to a documented clinical indication consistent with LCD L40255, and that documentation support the medical necessity for the specific type of monitoring utilized.

Designing Workflows That Achieve 16 Days For CPT 99454

The 99454 documentation fix above only works when the workflow reliably produces 16 days of transmissions. That reliability starts with device selection and patient support.

Device selection sets the ceiling on compliance. Cellular-connected devices transmit automatically without patient action, while Bluetooth-dependent devices require the patient to keep a hub powered and nearby. Because that burden falls on the patient, a short education script at enrollment that explains daily transmission expectations and what to do if the indicator light changes can materially improve compliance.

When a patient still trends short at day 20, a brief outreach call both supports the patient and creates a documented touchpoint. The 16-day threshold does not automatically apply to the implantable cardiac monitor codes 93297/93298, which operate on their own 30-day cycle rules. Proving 16 days in an audit means producing a platform export that shows each transmission date and cross-references those dates to the claim's billing period.

Device-To-CPT-Family Mapping For Faster, Cleaner Claims

The fastest way to prevent device-type mismatch denials is to match each device to its correct CPT family before the claim is built. The table below shows which CPT family applies to each device type and the cycle it bills on. The device-to-code assignments in this table are drawn from CMS Billing and Coding Article A60279, issued by Noridian Healthcare Solutions with an original effective date of 06/21/2026 and a revision effective date of 10/01/2026, supporting LCD L40255.

Device Type CPT Family Cycle / Duration Key Notes
External ECG (Holter) 93224–93227 Up to 48 hours Global (93224) or split professional, technical, and scanning components
Long-Term Continuous ECG (>48 hrs–15 days) 93241–93248 >48 hours up to 15 days Do not report with 93228/93229 for the same monitoring period
Mobile Cardiac Outpatient Telemetry (MCOT) 93228 (professional) / 93229 (technical) Up to 30 days No -26 or -TC modifiers; bill together only when the practice performs both services
Event Monitoring (patient/auto-activated) 93268–93272 Up to 30 days Attended surveillance variant; do not overlap with 93228/93229
Implantable Cardiovascular Physiologic Monitor 93297 30-day cycle Global, -26, or -TC; once per 30 days; applies to devices like CardioMEMS
Subcutaneous Cardiac Rhythm Monitor / Loop Recorder 93298 30-day cycle Global, -26, or -TC; implant code 33285 confirms 93298 applies
Pacemaker Remote Interrogation (professional) 93294 90-day cycle Professional only; pair with 93296 for technical
ICD Remote Interrogation (professional) 93295 90-day cycle Professional only; pair with 93296 for technical
Pacemaker / ICD Technical Component 93296 90-day cycle No -26 or -TC; do not apply to loop recorders or physiologic monitors

When Remote Physiologic Monitoring Does And Does Not Pay Off

Even with the right code mapped to the right device, RPM only pays when the practice can actually bill for it. Remote physiologic monitoring is not financially viable for every practice or every patient panel.

CMS MLN901705 (December 2025) states that only one practitioner can bill for remote monitoring per patient in a 30-day period, so practices must verify that patients are not already enrolled elsewhere. Payer mix also shapes results. Cigna Policy 0563 covers RPM only for COPD, Diabetes Mellitus, Gestational Diabetes, Heart Failure, and Hypertensive Disorders of Pregnancy, excluding isolated hypertension and other indications.

A practice with a predominantly commercial payer mix and a broad chronic disease population will see different returns than one with a narrow Medicare panel. Volume thresholds matter as well. The administrative infrastructure required to track transmission days, log treatment management time, and generate audit-ready documentation needs a patient census large enough to justify the investment. For a deeper look at the revenue cycle impact, see Revenue Cycle Management: Cardiac Remote Device Monitoring.

Executing This Operational Playbook With Rhythm360

The documentation fixes in this playbook work best when a system tracks them automatically instead of relying on manual spreadsheets. Rhythm360 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 tracking prevents device-type mismatch denials and missed technical components. The platform also automates data ingestion, report generation, and billing documentation across all major device manufacturers.

Practices using Rhythm360 have reported up to an 80% reduction in critical alert response times and up to a 300% increase in revenue capture. Other platforms in this space include Murj, Implicity, Rhythm Management Group, and Octagos.

Rhythm360
Rhythm360

See Rhythm360 In Action

Conclusion: Turning Codes And Cycles Into Reliable Revenue

Remote heart rhythm monitoring revenue often leaks through three consistent gaps: documentation that cannot survive an audit, device-type mismatches that trigger automatic denials, and missed transmission thresholds that drop entire billing periods. The 2026 addition of CPT 99445 now pays for short-duration episodes that previously generated no device-supply revenue, provided billing software uses the code correctly and workflows route patients to the right code.

The 90-day CIED cycle, the 30-day implantable monitor cycle, and the 20-minute interactive communication requirement for 99457 each carry distinct failure modes. Each also has a clear documentation fix that prevents the denial before submission. Rhythm360 automates this tracking, generates audit-ready documentation, and helps practices capture every billable episode compliantly.

See How Rhythm360 Captures Every Billable Episode

Frequently Asked Questions

How Do CPT 99445 And CPT 99454 Work Together In 2026?

CPT 99454 covers device supply with daily recordings or programmed alert transmissions for 16–30 days in a 30-day period. CPT 99445, effective January 1, 2026, covers the same type of service for 2–15 days in a 30-day period. The two codes are mutually exclusive, so only one can be billed per patient per 30-day period.

Before 99445 existed, a patient who transmitted data for fewer than 16 days generated no billable device-supply code for that period. Practices can now capture reimbursement for short-duration monitoring episodes such as post-operative monitoring or medication titration windows. Billing software should apply 99454 only when transmission data supports 16 or more days and should default to 99445 for 2–15 day periods.

What Documentation Supports A CPT 99457 Claim?

A valid 99457 claim requires five elements before submission. The record must show patient consent on file before services begin and an eligible diagnosis that links monitoring to medical necessity. It must also include a time log with the date, duration, and activity description for each entry, a separately documented interactive communication event, and confirmation of the device's FDA-clearance status.

The interactive communication must be a real-time, synchronous, two-way audio interaction, such as a live phone call or video visit. Asynchronous messages, patient portal notes, and SMS exchanges do not satisfy this requirement, regardless of documentation quality. A single aggregate note at month-end without individual time entries will not survive an audit. Each entry must identify who performed the activity, what they did, and how long it took. RPM treatment management time must also be clearly separated from any E/M encounter time billed in the same month.

How Do The 90-Day And 30-Day Cycles Work For Implantable Device Monitoring?

Remote interrogation of pacemakers and ICDs operates on a 90-day cycle. CPT 93294 is the professional component for pacemakers, CPT 93295 is the professional component for ICDs, and CPT 93296 is the technical component for both, covering data acquisition, technician review, and distribution of results. These codes are billed once per 90-day period, not monthly.

Remote monitoring of implantable cardiovascular physiologic monitors, such as CardioMEMS, uses CPT 93297. Remote monitoring of subcutaneous cardiac rhythm monitors and implantable loop recorders uses CPT 93298. Both 93297 and 93298 operate on a 30-day cycle, billable once per 30 days. Each can be billed global, with modifier -26 for the professional component, or with modifier -TC for the technical component. The 16-day transmission threshold that applies to RPM device-supply codes like 99454 does not apply to 93297 or 93298. Billing either code family on the wrong cycle remains the most common denial in this group.

Can A Practice Bill Both The Professional And Technical Components Of MCOT?

Practices can bill both components of MCOT when they actually perform both services. CPT 93228 is the professional component of mobile cardiovascular telemetry, covering physician review, interpretation, and the signed report. CPT 93229 is the technical component, covering device supply, patient hookup, attended surveillance, and data transmission.

When a practice furnishes both, the codes are reported as separate companion codes on their own claims without -26 or -TC modifiers, because each code already describes a single component. A practice that contracts with a monitoring vendor for the surveillance center function does not perform the technical service and cannot bill 93229. Billing 93228 alongside Holter codes 93241 or 93245 for the same monitoring period is an unbundling error. A compliant 93228 record requires a signed physician order naming MCT that predates the monitoring start date, a signed interpretive report, and evidence of event response.

What Are The Biggest Audit Risks For Remote Heart Rhythm Monitoring In 2026?

The HHS Office of Inspector General added remote patient monitoring to its 2026 high-priority work plan after Medicare payments for RPM surpassed $500 million annually. The highest-risk patterns include billing CPT 99454 without 16 days of readings in a 30-day period and billing CPT 99457 without documented real-time interactive communication.

Other common risks include submitting both 99454 and 99445 in the same 30-day period, billing CIED codes on the wrong cycle, and mismatching the professional code to the device type. Time logs that cluster at exact code thresholds, such as always exactly 20 minutes, draw scrutiny, as do device transmission counts that do not reconcile between the platform export and the claim. Practices that can produce a clean paper trail from device transmission to claim submission, with day-by-day logs and separately documented interactive communications, are far better positioned in an audit than those relying on aggregate monthly summaries.

Read Next

Related posts