Cardiology Billing Services · Case Study

A clean 30-day cardiac remote monitoring cycle, with zero frequency overlap

The fastest way to kill remote cardiac monitoring denials is not appeals. It is a calendar. When every device stream is anchored to the right clock, cycles never overlap, never gap, and never trip a frequency edit.

93296 PM / ICD technical · 90-day clock 93297 physiologic monitor · 30-day clock 93298 subcutaneous rhythm · 30-day clock

The short answer

Remote cardiac monitoring denials for a 12-provider cardiology group were almost never about medical necessity. They were about timing. CPT 93297 and 93298 bill once per 30 days, while 93296 bills once per 90 days. Treating all three as a single monthly routine restarts the 30-day codes too early and reports 93296 twice inside its 90-day window. The fix is one shared cadence calendar that assigns each device to its own clock and closes each window before it can overlap the next.

The archetype

One group, three device types, two different clocks

The practice ran a mixed device panel: pacemakers and ICDs on remote interrogation, pulmonary-artery pressure sensors, and implantable loop recorders. Every device transmitted, but the codes that captured that work did not all live on the same calendar. That single fact drove the denials.

12Providers

3Device families

2Billing clocks

1Unit per period (MUE)

The 30-day cycle, step by step

Anchoring the technical and professional work to one window

Below is the cadence built for the 30-day codes (93297 and 93298). The technical component builds across the window; the professional interim report closes it; the claim goes out on day 30; the clock resets on day 31 with no overlap and no gap.

Day 0 · Enroll

Device paired, consent on file, clock started

The monitoring start date is recorded once and becomes the anchor for the entire 30-day window. Every downstream code references this date, not the calendar month.

Days 1 to 29 · Acquire

Transmissions land and are triaged

Data receipt, technician review, and distribution of results accumulate across the window. This is the technical component the 30-day code is built to capture, and it is not billable in fragments.

Technical component

Day 28 to 30 · Interpret

Physician interim analysis and signed report

The qualified provider reviews the interim data and produces the report. CPT instructs that the 30-day codes are not reported for monitoring periods of fewer than 30 days, so the report waits for a full window.

Professional component

Day 30 · Bill

Close the window, submit one unit

A single unit of 93297 or 93298 is coded for the completed period. The Medically Unlikely Edit is one unit per patient per period, so the window must be whole before the claim leaves.

One unit only

Day 31 · Reset

Fresh clock, no overlap, no gap

The next 30-day window opens the day after the last one closed. Because the reset is tied to the anchor date rather than the month, two windows can never share a calendar day and trigger a duplicate-frequency denial.

Why denials happen

Two clocks, and the trap in mixing them

The single most common frequency denial comes from assuming all remote cardiac monitoring is monthly. It is not. The pacemaker and ICD technical code runs on a 90-day cadence, so a monthly habit reports it three times inside one payable window.

The 30-day clock

Implantable cardiovascular physiologic monitors and subcutaneous cardiac rhythm monitors
Reported once per 30 days
Not reported for periods under 30 days

CPT 93297 · 93298

The 90-day clock

Pacemaker and implantable defibrillator remote interrogation
Reported once per 90 days, professional and technical
Not reported for periods under 31 days

CPT 93294 · 93295 · 93296

The three failure modes we designed out

Where the cadence stops the bleed

DENIAL PATTERN 01

93296 billed monthly

Reporting the pacemaker or ICD technical code every 30 days puts it inside its own 90-day window twice more, hitting a frequency edit on the second and third claims.

Fix: 93296 is anchored to a 90-day clock, billed once per window.

DENIAL PATTERN 02

The 30-day clock restarted early

Closing a window on the calendar month instead of the anchor date lets two 30-day periods share a day, so 93297 or 93298 reads as a duplicate within the period.

Fix: reset is tied to the enrollment anchor, never the month.

DENIAL PATTERN 03

Short windows billed anyway

Reporting a 30-day code for a partial monitoring period, or splitting the technical work across fragments, violates the CPT instruction against periods under the stated length.

Fix: the claim waits until a full window has elapsed.

Code reference

The remote cardiac monitoring family at a glance

CPT	What it captures	Component	Cadence
93294	Remote pacemaker interrogation, interim analysis, review and report	Professional	90 days
93295	Remote implantable defibrillator interrogation, interim analysis, review and report	Professional	90 days
93296	Remote pacemaker or ICD, data receipt, technician review, technical support, distribution of results	Technical	90 days
93297	Remote implantable cardiovascular physiologic monitor, analysis of recorded data, review and report	Global	30 days
93298	Remote subcutaneous cardiac rhythm monitor, analysis of recorded rhythm data, review and report	Global	30 days

Global codes may be split into professional and technical work with modifiers 26 and TC where the interpretation and the monitoring service are furnished by different parties.

What this is built on

Real 2026 guidance, cited by name

CMS Physician Fee Schedule Final Rule, CY2026, for remote physiologic and cardiac device monitoring payment policy and the professional and technical component split.
CPT 2026 code set (AMA), codes 93294, 93295, 93296, 93297, and 93298, including the reporting-frequency instructions and the minimum monitoring-period language.
CMS National Correct Coding Initiative Policy Manual, Chapter 11 (Cardiovascular System), and the associated Medically Unlikely Edits that cap these services at one unit per patient per period.
Medicare Claims Processing Manual, Publication 100-04, Chapter 13, for radiology and diagnostic remote-service billing conventions.
HRS / EHRA / APHRS / LAHRS 2023 Expert Consensus Statement on the practical management of the remote device clinic, for clinical cadence and interim-review expectations.

Archetype for illustration. No real client is named and no outcome figures are represented as a specific client result. Verify every code, frequency limit, and payer policy against the current CMS and AMA source and your payer contracts before billing.

Put your remote monitoring on a calendar that pays

ASP-RCM builds the cadence, the anchor-date tracking, and the frequency guardrails so your cardiology group captures every 93296, 93297, and 93298 window once, cleanly, on the right clock. Fewer frequency denials, faster cash, no overlap and no gap.

Talk to our cardiology billing team →