RPM Billing for Cardiology: CPT 93294-93299 Compliance

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 cycle, typically 30 days. 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.

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.

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.