CARDIOLOGY

RPM Billing for Cardiology: CPT 93294-93299 Compliance

Jul 25, 2026 · 6 min read

Mukesh Makwana
Mukesh MakwanaFounder & CEO · Hands-on medical billing & RCM across 11 specialties

Remote patient monitoring has become one of the fastest-growing revenue streams for cardiology practices, and one of the easiest to lose to a documentation gap that has nothing to do with the clinical care itself.

What CPT 93294-93299 actually require

These codes cover remote monitoring of cardiac implantable devices, each requiring specific data-transmission windows within a defined billing period: up to 90 days for pacemaker and defibrillator monitoring (93294, 93295, 93296) and up to 30 days for implantable monitors (93297, 93298). They are a separate family from remote physiologic monitoring of external devices such as blood pressure cuffs (99453 to 99458), which has its own rules. The claim depends on the transmission data existing and being documented, not on the monitoring having clinical value, which it almost always does. A denial here is a documentation failure, not a care failure.

Where OEM data silos create the gap

Cardiac devices from different manufacturers, Medtronic, Abbott, Boston Scientific, and others, each report through their own portal. Practices monitoring patients across multiple device manufacturers end up reconciling transmission data by hand across systems that don't talk to each other, which is exactly where a missed transmission day or an undocumented window shows up at claim time.

RPM denials rarely mean the monitoring didn't happen. They mean the transmission data wasn't captured and matched to the billing cycle correctly.

Consent and documentation requirements

Beyond the transmission threshold itself, documented patient consent for remote monitoring is a foundational requirement that gets overlooked when the clinical relationship predates the RPM billing relationship. If consent isn't clearly on file, the claim is vulnerable regardless of how complete the transmission data is.

What to check before your next RPM billing cycle

1. Is transmission data reconciled per patient, per 30-day cycle, across every device manufacturer in use?

2. Is remote monitoring consent documented and on file for every RPM-billed patient?

3. Does your billing process flag incomplete transmission windows before submission, rather than after denial?

Why this needs cardiology-specific RPM logic

Reconciling multi-manufacturer device data and matching it to specific billing cycles is not something a general medical billing process is built to do. Our cardiology billing page covers how we handle RPM reconciliation across device manufacturers.

Sources

Centers for Medicare & Medicaid Services, Physician Fee Schedule, cms.gov.
Heart Rhythm Society, hrsonline.org.

Related reading

  • CPT 93294. Pacemaker remote monitoring, up to 90 days, physician analysis and report.
  • CPT 93295. Defibrillator remote monitoring, up to 90 days, physician analysis and report.
  • CPT 93296. Pacemaker or defibrillator remote monitoring, technical component, up to 90 days.
  • CPT 93297. Implantable cardiovascular physiologic monitor, remote, up to 30 days.
  • CPT 93298. Subcutaneous cardiac rhythm monitor and loop recorder, remote, up to 30 days.
  • CPT 93299. Technical-only monitor code that Medicare does not use.
  • CPT 99454. Remote physiologic monitoring device supply, the separate RPM family.

Get your RPM billing checked for free

Eligibility verification (EV), benefits verification (BV), prior authorizations, and denial management at no cost for your first 30 days.

30-Day Free Trial

No setup fee. No long-term contract.

30-Day Free Trial Call
πŸ€–Sterling AI AgentOnline Β· instant answers