Cardiology Device Monitoring Billing (93294-93299): Stop the 90-Day Revenue Leak

By Rcmaxis Revenue Cycle Team  ·  September 24, 2026  ·  9 min read

A cardiology practice with 600 patients on pacemakers and ICDs should bill about 2,400 remote interrogation cycles a year. Four per patient. Say the clinic bills 2,150 of them. That gap of roughly 250 sessions doesn't show up as denials. It shows up as nothing, because the claim never left the building.

Put a number on it. At a $100 combined allowed amount for a 90-day session (that's an illustration, so pull your own figure from your payer fee schedules), 250 missed sessions is $25,000 a year walking out the door. Add the claims that do go out on the wrong interval and bounce, and you're closer to $35,000.

Cardiac device remote monitoring billing isn't hard because the codes are exotic. It's hard because the clock is invisible. Nobody's calendar says "day 91."

The Root Operational Friction: Why Device Claims Fail

Remote interrogation runs on time windows, not visits. That one fact breaks most billing workflows, which are built around encounters.

A pacemaker or ICD patient gets a transmission every few weeks or months. The device clinic reviews each one. But payment is tied to a 90-day period for pacemakers and ICDs (93294, 93295, 93296) and a 30-day period for implantable cardiovascular monitors and loop recorders (93297, 93298, 93299). The billable event isn't the transmission. It's the closing of the window, plus proof the data was reviewed.

Here's where it usually goes wrong, roughly in this order:

• Nobody owns the window. The device nurse knows when transmissions arrive. The biller knows when claims drop. Nobody owns the date in between.
• The EHR bills what's charted. If the nurse charts every transmission as a visit, the biller either bills all of them (denials for excessive frequency) or picks one at random (underpayment).
• Professional and technical get split wrong. Two codes, two pieces of work, two possible billers. When the practice owns the equipment and the staff, it can bill both. When an outside monitoring vendor does the technical work, the practice can only bill the physician review. Guessing costs money either way.
• Reviews aren't documented as reviews. A transmission sitting in a portal isn't a physician review. The interpretation has to be in the record with a date, and it has to be by the billing provider.

Specific Payer Edits, Modifiers, and Coding Traps

Start with what each code actually covers. Confirm the professional/technical indicator for each code in the current Medicare Physician Fee Schedule file before you load or change anything in your charge master.

The traps that cost real money

1. Billing pacemakers on a monthly cycle. This is the classic. A billing team that's already set up monthly cycles for loop recorders copies the logic to pacemakers. Twelve claims a year go out. Four are payable. Eight deny for frequency, and if you've been doing it for two years, you've created audit exposure on every one that got paid by mistake.

2. Missing the technical code entirely. If the practice owns the monitoring equipment and staff, 93296 (or 93299) is separate revenue. Plenty of practices bill 93294 for years and never once bill 93296. It's a quiet leak because nothing denies. Nothing gets submitted.

3. Billing the technical component when a vendor did the work. The reverse trap. If an outside remote monitoring company performs the data acquisition and technical support, the practice doesn't bill 93296. Check the vendor agreement, then check what the vendor is billing. Two claims for the same technical service will get you an overpayment letter.

4. Overlap with in-office device checks. In-person interrogation evaluations (93288 for pacemakers, 93289 for ICDs, 93290 for ICMs, 93291 for loop recorders) and programming evaluations sit in the same family. Run the NCCI procedure-to-procedure edits and the Medically Unlikely Edits for the code pairs you actually bill, and read your MAC's article for the interaction between in-person and remote services inside the same window. If you also bill an E/M on the day of an in-person check, expect the payer to look for modifier 25 and a note showing the E/M stood on its own.

5. Overlap with remote patient monitoring. RPM (the 99453 to 99458 family) and cardiac device interrogation aren't interchangeable. If a patient with a pacemaker is also enrolled in a blood pressure RPM program, those are two services with two sets of documentation. Bundle them in the same note and an auditor will call it duplicate billing. Our RPM billing guide covers the RPM side.

6. Documentation that stops at "transmission received." Payers want to see a dated physician interpretation of the data, what was reviewed (battery, lead impedance, arrhythmia log, therapies delivered), and the clinical action, even if that action is "no change."

Prior auth and payer rules: what to actually do

Original Medicare doesn't require prior authorization for remote device interrogation. Many Medicare Advantage and commercial plans don't either, but some route it through device registration, enrollment or eligibility flags instead. Don't assume. Do this:

1. Call each top-ten payer once and ask three questions: Is prior auth or device registration required for 93294 to 93299? What's the frequency limit and does it reset on a rolling or calendar basis? Do they pay the technical code to a practice that owns the equipment?
2. Write down the answers with the rep's name and date. When a denial arrives, this note is your appeal.
3. Record the device enrollment date and the window start date in the patient's device record, not just the chart. The window is what you're tracking, not the visit count.
4. If a payer requires registration and denies for it, the fix is to register and resubmit with proof of the original date of service, inside timely filing. Ask what the payer's retro-registration window is before you need it.
5. Track expiration by date, not by count. A 90-day window that started on March 3 closes on June 1. Put that date in a worklist, not in someone's memory.

The Tactical Workflow Fix: Step by Step

You can clean this up in about three weeks with the staff you already have.

Week 1: Build the device roster. Export every patient with an implanted device. Columns: device type, monitoring code family (90-day or 30-day), enrollment date, window start, last billed window, monitoring vendor (if any). Split the file by code family. That alone will show you who's been billed on the wrong cycle.

Week 2: Fix the calendar. Give each patient a window-close date. Build a weekly worklist that shows windows closing in the next 14 days. The device nurse confirms the physician review is documented. The biller confirms the code, the modifier and the rendering provider. Nothing drops without both initials.

Week 3: Clean up the past. Run a look-back on the last 12 months. Three lists come out of it: windows that closed and never billed (bill them if timely filing allows), windows billed at the wrong interval (correct them), and windows billed without documented review (talk to compliance first).

Ongoing:

• One person owns the roster. Not "the team."
• The physician signs a review note every window. A template with battery, leads, arrhythmias, therapies and plan takes under a minute.
• Once a month, compare transmissions received to windows billed. A gap over 5 percent gets a root-cause note.
• Send denials to a weekly review, sorted by reason code. If frequency denials show up twice for the same payer, that's a payer rule you haven't learned yet. Our denial management service is built around exactly this kind of loop.

Revenue Impact: Days in AR and Collection Benchmarks

Device monitoring is a small-ticket, high-volume line. That's why the leaks hide. Here's how the math tends to move once the window discipline is in place.

• Recovered revenue. For a 600-patient device clinic, closing a 10 percent capture gap at a $100 combined allowed amount adds about $24,000 to $25,000 a year. Your figures will differ, but the shape doesn't.
• Denial reduction. Eliminating monthly billing on 90-day codes removes the frequency denials outright. If you were sending eight bad claims per pacemaker patient per year, that's rework you stop paying for. Even at a conservative $25 per reworked claim, 600 patients is a five-figure line.
• Days in AR. Device monitoring should pay quickly because the claims are simple. A healthy target is under 35 days in AR for this line, and under 30 for Medicare fee-for-service. If yours sits above 45, look for unbilled technical components and windows waiting on documentation.
• Net collection rate. For this line, 95 percent or better of allowed amounts is a fair benchmark. If you're at 88 percent, the gap is almost always unposted denials or write-offs that should've been appeals.
• Clean claim rate. Above 95 percent on first submission is realistic once the roster is running.

The CY 2027 Physician Fee Schedule proposed rule (released July 14, 2026) has proposals on remote physiologic and therapeutic monitoring services (the RPM and RTM families), not on 93294 to 93299. But it's a signal about where CMS is looking. If you also run RPM programs, read the proposal and see our cardiology billing page for how we keep the two service lines separated.

OIG, RAC and MAC Audit Exposure for Device Monitoring

Nobody has published a "cardiac device interrogation" audit report the way they have for RPM. Don't take comfort in that. Here's what does apply:

• OIG's RPM work sets the tone. OIG's report Additional Oversight of Remote Patient Monitoring in Medicare Is Needed (OEI-02-23-00260) found that Medicare payments for RPM reached $536 million in 2024 and that a large share of enrollees didn't receive all three components of the service. OIG also has an open Work Plan audit of Part B RPM services. Cardiac device interrogation isn't RPM, but reviewers who're trained on one look at the other.
• RAC and MAC reviews use frequency. Data analytics flag any provider billing 93294 to 93296 more than once per 90 days per patient. That's the easiest audit to run and the easiest to lose.
• Typical error patterns in this space: excessive frequency, missing physician review, and billing of the technical component when someone else performed it.
• Lookback. RACs generally review claims up to three years back. The federal 60-day overpayment rule (42 CFR 401.305) has a six-year lookback for reporting and returning identified overpayments. If your monthly-cycle habit is two years old, you're inside both windows.
• What to do now. Pull a payer-level report of patients with more than four paid 90-day claims in a rolling year. If it's not empty, someone should look at it this month.

Frequently Asked Questions About Cardiac Device Monitoring Billing

Can we bill 93294 and 93296 for the same 90-day period?

Yes, when the practice performed both the physician review and the technical work. 93294 is the professional review and 93296 is the technical support. If an outside vendor did the technical work, only the physician review belongs on your claim.

How often can we bill remote pacemaker interrogation under Medicare?

Once per 90-day period per patient for 93294 to 93296. Loop recorders and implantable cardiovascular monitors (93297 to 93299) run on a 30-day period. Check your MAC's article for any additional conditions.

Do we need prior authorization for remote cardiac device interrogation?

Original Medicare doesn't require it. Some Medicare Advantage and commercial plans use device registration or enrollment flags instead. Call your top payers, write down the answers, and store them with the payer profile.

What's the most common reason 93294 to 93299 claims get denied?

Frequency. Billing pacemaker or ICD monitoring monthly is the leading cause, followed by billing a technical code that a vendor already billed.