Cardiology Billing Services · 2026 Update

The money in remote cardiac monitoring hides in three separate billable events. Most groups only catch two.

Here is the short answer: the piece cardiology groups drop most is not the device. It is the monthly interpretation and treatment-management minutes. Device supply gets billed because it is tied to the shipment. The clinician time gets forgotten because nobody owns the clock. Below, we split cardiac remote monitoring into device supply, transmission, and interpretation so a mid-size practice can see exactly which event it is leaving on the table.

3separable billable components per patient

30-daybilling cycle for 99454, 93297 and 93298

16 daysminimum data required to bill 99454

20 minincrement that unlocks 99457, then 99458

The stat wall

One patient, three revenue events. Bill them as three, not one.

Cardiac remote monitoring is not a single code. It is device supply, data transmission, and clinician interpretation, and each can carry its own claim line under the CMS CY2026 Physician Fee Schedule. Group them mentally like this and the gaps become obvious.

COMPONENT 01

Device supply

The equipment and the data it collects. Tied to a shipment or an implant, so it is the easiest event to remember.

99453RPM setup and patient education, billed once per episode of care
99454Device supply with daily recordings or programmed alerts, each 30 days
93297Implantable cardiovascular physiologic monitor, up to 30 days
93298Implantable/subcutaneous cardiac rhythm monitor, up to 30 days

●

Catch rateUsually captured. The claim rides along with the device.

COMPONENT 02

Transmission & technical support

Getting the data off the device and into a readable form. Often bundled or handled by a monitoring vendor, so ownership blurs.

99454The data-transmission half of the RPM device code, per 30 days
93299Technical support for implantable monitor remote data, up to 30 days

●

Catch ratePartial. When a vendor owns the technical component, the practice must not also bill it, and vice versa. Contract terms decide.

COMPONENT 03

Interpretation & management

The clinician actually reading the data, acting on alerts, and talking to the patient. This is the event that drives care, and the one that quietly goes unbilled.

99457First 20 minutes of RPM treatment management per calendar month
99458Each additional 20 minutes, add-on to 99457
99091Collection and interpretation of physiologic data, per 30 days

⚠

Most-dropped eventThe management minutes exist but no one logs the clock, so 99457/99458 never fire. This is where mid-size groups leak the most.

Where the claim falls off

Follow one patient from device to claim

The revenue does not disappear all at once. It falls off at four predictable points. The further right you go, the more often the billable event is missed.

STEP 01

Device placed

Patient set up on the monitor and educated on how to use it.

miss: 99453 not billed once

STEP 02

Data collected

Recordings accrue across the 30-day window.

miss: 99454 billed under 16 days

STEP 03

Data transmitted

Technical support processes the feed for review.

miss: 93299 double-billed vs vendor

STEP 04

Clinician acts

Alerts reviewed, patient contacted, plan adjusted.

miss: 99457/99458 minutes untracked

The two code families

Generic RPM vs cardiac-specific monitoring

A big source of confusion: the 99453-99458 RPM family and the 93297-93299 implantable cardiac family live side by side, and they answer different questions. Know which family the device belongs to before you code the month.

CPT	Family	What it pays for	Cycle
99453	RPM	Set-up and patient education on the monitoring device	Once per episode
99454	RPM	Device supply plus daily recording or alert transmission	Each 30 days, needs 16 days of data
99457	RPM	Treatment management, first 20 minutes of clinician time	Per calendar month
99458	RPM	Each additional 20 minutes of management time	Add-on to 99457
93297	Cardiac	Remote monitoring of an implantable cardiovascular physiologic monitor	Up to 30 days
93298	Cardiac	Remote monitoring of an implantable or subcutaneous cardiac rhythm monitor	Up to 30 days
93299	Cardiac	Technical support for 93297/93298 remote data	Up to 30 days

Note the frequency guardrails: the implantable-monitor codes carry a 30-day floor, so you cannot report them more than once in a 30-day span for the same patient, and 99454 needs at least 16 days of data before it can be billed for the period. These are the rules the CPT descriptors and the CMS CY2026 Physician Fee Schedule hold you to.

Where mid-size groups leak

Three patterns we see over and over

The orphaned management minute

Staff review alerts and call patients, but the time never lands in a log. Without a captured clock, 99457 and its 99458 add-on simply never generate. The work happened; the claim did not.

The 16-day cliff

99454 gets dropped for the whole 30-day period because the device fell a day or two short of the 16-day data threshold and nobody flagged it for the next window. One short month erases the device revenue.

The vendor overlap

A monitoring vendor bills the technical support (93299) while the practice bills it too, or neither does because each assumed the other would. Contract language, not habit, should decide who owns which component.

The 2026 guidance this is built on

Every rule above traces to a named, current source. Verify against your own payer policies, but start here.

Federal fee scheduleCMS Calendar Year 2026 Medicare Physician Fee Schedule Final Rule, which sets the national payment structure and utilization rules for remote monitoring services.
RPM code familyCPT remote physiologic monitoring codes 99453, 99454, 99457 and 99458, plus 99091 for physiologic data interpretation.
Cardiac monitoring codesCPT 93297, 93298 and 93299 for remote monitoring of implantable cardiovascular monitors and their technical support.
Specialty coding guidanceAmerican College of Cardiology (ACC) coding guidance on remote monitoring documentation and component reporting.

Find out which of the three components your group is dropping

ASP-RCM Solutions runs cardiology billing as three tracked events, not one. We tie the management clock to the workflow so 99457 and 99458 fire when the work is done, hold the line on the 16-day rule so device revenue does not fall off a cliff, and settle the vendor-overlap question in writing before a single 93299 goes out. A short review of a recent month of your remote monitoring claims will show you the leak in dollars.

Book a remote monitoring revenue review →

This page is coding and reimbursement education for cardiology billing operations, not legal, compliance, or clinical advice. Confirm every code, frequency limit, and component split against the current CMS CY2026 Physician Fee Schedule, CPT descriptors, ACC guidance, and your specific payer contracts before billing.