Last updated: July 14, 2026
The 93294/93296 pair splits the service into two parts, and different entities within a practice can bill each one.
CPT 93294 covers professional review. It applies to the physician or qualified non-physician practitioner's clinical interpretation of remote transmissions from single or dual-chamber pacemakers. The clinician must review the data, assess device function, and document a substantive interpretation before billing this code.
CPT 93296 covers the technical infrastructure. It includes data acquisition, receipt of transmissions, technician review, technical support, and distribution of results for pacemakers, ICDs, or ILRs. Practices bill it alongside 93294 or 93295.
Both codes follow a 90-day, per-device billing window. CPT 93294 and 93296 may each be reported only once per 90-day period per device per patient, so practices need to track the full period rather than individual transmissions. Within that window, 93294 also requires at least 30 days of monitoring before it becomes billable. This threshold trips up practices that bill off a single symptomatic transmission.
CIED codes and RPM codes stay separate. CPT 93294-93298 are device-specific cardiac interrogation codes, while RPM codes (99453-99454, 99457-99458) cover general physiologic monitoring unrelated to a specific device. CIED remote monitoring bills under the cardiac-specific codes only. Mixing the two families creates compliance risk.
These reimbursement rates look modest per claim, but they compound quickly across a device population, which is exactly where practices start losing money. The table below reflects CY 2026 Medicare national unadjusted rates from the Medtronic 2026 Cardiac Resynchronization Therapy Coding and Payment Guide. Actual reimbursement varies by geographic locality and payer contract.
| CPT Code | Description | 2026 Physician Rate (National Unadjusted) | 2026 APC Rate |
|---|---|---|---|
| 93294 | Remote interrogation, pacemaker (single, dual, or multiple lead / leadless); professional component, up to 90 days | $29 | Physician Only (no APC) |
| 93295 | Remote interrogation, ICD (single, dual, or multiple lead); professional component, up to 90 days | $37 | Physician Only (no APC) |
| 93296 | Remote interrogation, pacemaker/leadless pacemaker or ICD; technical component, data acquisition, receipt, technician review, technical support, distribution of results, up to 90 days | National unadjusted | APC 5741 |
Missed remote monitoring billing is one of the largest preventable revenue leaks in electrophysiology practice. For high-volume practices, the gap between CMS-allowed billing and actual captured revenue can reach into six figures annually.
Payers expect a defensible claim to include specific elements for both CPT 93294 and 93296. Missing any of these creates audit risk.
A 90-day monitoring period with no documented data review will not survive an audit. Meeting these requirements consistently is harder than it sounds, largely because of how practices collect the underlying device data in the first place.
Most cardiology practices implant devices from several manufacturers, including Medtronic, Boston Scientific, Abbott, and Biotronik. Each OEM runs a separate, proprietary portal with its own login, data format, and alert structure. As a practice's device population grows, staff must navigate more non-interoperable systems just to pull the data needed for compliant billing.
Cardiac remote monitoring, including CIED monitoring for pacemakers, ICDs, and loop recorders, ranks among the fastest-growing and most underbilled revenue categories in cardiology. Multi-portal management drives much of that underbilling.
Several platforms serve this market, including Paceart, Murj, PaceMate, Implicity, Rhythm Management Group, and Octagos. Rhythm360 by RhythmScience takes a vendor-neutral approach, ingesting and normalizing data from all major device manufacturers into one unified platform.
Common leakage sources include CIED transmissions received but not billed within the 90-day cycle, RPM data missing prior minimum thresholds, and monthly RPM management time that falls short of the 20-minute billing threshold. These leaks tend to show up in a few predictable ways.
Each of these gaps compounds across a device population. For practices with large monitoring populations, the resulting gap between allowed billing hours and actual captured revenue can reach hundreds of thousands of dollars a year.
Rhythm360 is a cloud-based, HIPAA-compliant platform built for the operational and compliance demands of CIED remote monitoring. It ingests data from Medtronic, Boston Scientific, Abbott, Biotronik, and other manufacturers using API, HL7, XML, and AI-powered PDF parsing, normalizing every stream into a single source of truth.
Key capabilities supporting 93294/93296 billing compliance include:
Talk to our team about consolidating your OEM portals into one compliant workflow.
Rhythm360's onboarding process minimizes disruption to active clinical operations. EHR integration and platform configuration typically finish within a few days to a few weeks, depending on system complexity and device population size.
Key implementation milestones include:
Practices track denial-rate reduction on 93294/93296 claims, time-to-bill for completed periods, and total revenue captured against pre-implementation baselines. Pricing scales with clinic size and usage, so it fits solo EP practices and large health systems alike.
Three denial scenarios recur consistently across cardiology billing operations.
Rhythm360 by the Numbers
- Up to 300% increase in revenue generation through optimized CPT code capture and improved staff efficiency
- 80% reduction in response times for critical patient alerts
- >99.9% data transmissibility via redundant feeds and AI-powered extrapolation
- Days to weeks for full EHR integration and onboarding
A cardiology practice with 200 device patients can capture roughly $170,000 to $384,000 in annual recurring revenue from properly billed remote monitoring. These gains in revenue capture and alert response time, detailed above, also translate into fewer downstream hospitalization costs. Faster intervention on critical alerts reduces adverse outcomes and the expenses tied to emergency care.
Getting Started With Compliant Billing in 2026
Accurate, compliant billing of CPT 93294 and 93296 is a core financial function for any cardiology practice managing a CIED patient population, not a back-office detail. The 2026 Medicare rates, documentation requirements, and frequency rules are well defined. Capturing that revenue consistently still requires systems most practices do not have in place today, as the numbers above show.
Fragmented OEM portals, manual period tracking, and disconnected documentation workflows create the conditions for revenue leakage. A vendor-neutral platform that automates documentation, tracks monitoring periods per device, and integrates with the EHR removes those conditions at the source.
Rhythm360 consolidates CIED data into one AI-powered platform that surfaces billable events, generates audit-ready documentation, and connects with the EHR systems cardiology practices already use.
Frequently Asked Questions
How often can CPT 93294 and 93296 be billed for the same patient?
Both codes bill once per 90-day monitoring period per device per patient. They are per-period codes, not per-transmission codes, so the number of individual transmissions received does not affect billing frequency. As noted earlier, 93294 also requires at least 30 days of monitoring before it becomes billable. Billing either code more than once within the same window for the same device triggers a duplicate denial, so practices need accurate tracking of start and end dates for every patient.
What is the difference between CPT 93294 and CPT 93296, and who bills each?
CPT 93294 covers the physician's clinical review and interpretation of transmitted pacemaker data, and the physician's practice typically bills it. CPT 93296 covers the technical infrastructure behind receiving and formatting that data, including acquisition, technician review, and distribution of results. A practice that handles both functions in-house bills both codes together. When a third-party technical service provider handles data acquisition, that entity may bill 93296 separately. This split matters when evaluating vendor-neutral monitoring platforms, since a platform's role in the technical workflow affects billing eligibility for 93296.
Are pacemaker remote monitoring CPT codes the same as remote physiologic monitoring (RPM) codes?
No. CPT 93294-93298 apply exclusively to implanted cardiac devices like pacemakers, ICDs, and loop recorders. RPM codes, including 99453, 99454, 99457, and 99458, apply to non-device-specific physiologic data such as blood pressure, weight, and oxygen saturation from consumer-grade devices. The two families carry different documentation requirements and billing frequencies. New RPM supply codes took effect in January 2026 for 2-15 days of data collection, but they do not change the 93294/93296 rules for CIED monitoring. Practices running both CIED and RPM programs need separate compliant workflows for each.
What are the most common reasons CPT 93294 claims are denied, and how can they be prevented?
Three reasons account for most 93294 denials: billing before the 30-day minimum is met, duplicate billing within the same 90-day window, and insufficient documentation such as missing dates or interpretation notes. Prevention comes down to systematic period tracking per device, automated documentation at the point of clinical review, and pre-submission validation that flags incomplete records. Practices relying on manual processes across multiple OEM portals face the highest risk for all three.
How does Rhythm360 help practices capture more revenue from pacemaker remote monitoring?
Rhythm360 addresses leakage at its source. It consolidates data from all major device manufacturers into one platform, automates tracking of monitoring periods and minimum thresholds, and generates compliant documentation at the time of clinical review. The dashboard gives real-time visibility into billable events and documentation gaps, surfacing revenue that a fragmented, multi-portal workflow would otherwise miss. Bi-directional EHR integration removes manual transcription so completed reviews show up immediately in the billing record.
