A Cardiac Device CPT Code Billing Guide for Clinics
Struggling with cardiac device CPT billing? Rhythm360's clean-claim workflow reduces denials and keeps your clinic fully compliant. Get the guide now.
Last updated: October 18, 2026
Key Takeaways
- Cardiac device claims most often fail because of fragmented cycle tracking across OEM portals and mismatched professional and technical splits, not incorrect CPT code selection.
- Follow the four-step clean-claim decision path for every encounter, then run a quick documentation audit before you file.
- Pacemaker and ICD remote monitoring (93294, 93295, 93296) follow 90-day cycles. Physiologic monitors (93297) and loop recorders (93298) follow 30-day cycles, each tracked as a rolling period from the patient’s own start date.
- Verify device type against implant records and confirm there are no same-date service overlaps, such as RPM 99454 with CIED codes, to avoid bundling denials.
- Rhythm360 pulls all OEM data into one dashboard, tracks CPT pairings and cycle windows automatically, and generates auditable documentation so claims go out clean the first time.
Schedule a demo with Rhythm360
The Clean-Claim Decision Path: Device Type, Service, Component, Cycle
Work through these four steps in order before you touch a claim.
- Identify the device type: pacemaker, ICD, CRT, implantable cardiovascular physiologic monitor, or subcutaneous cardiac rhythm monitor / implantable loop recorder.
- Identify the service: remote interrogation and review, in-person evaluation, or programming.
- Determine the billing component: global, modifier -26 (professional), or modifier -TC (technical).
- Confirm the billing cycle window: 90 days for pacemaker and ICD remote monitoring, and 30 days for physiologic monitors and loop recorders.
The table below maps each device type to its code, cycle, and component options for remote monitoring services. For raw code descriptors, see Remote Cardiac Monitoring CPT Codes Explained and Cardiac Implant Monitoring CPT Codes: 2026 Billing Playbook.
| Device Type | Code(s) | Cycle Length | Component Options |
|---|---|---|---|
| Pacemaker remote monitoring | 93294 (professional), 93296 (technical) | Up to 90 days; not reportable under 30 days | 93294 and 93296 billed separately by the entity performing each component |
| ICD remote monitoring | 93295 (professional), 93296 (technical) | Up to 90 days; not reportable under 30 days | 93295 and 93296 billed separately by the entity performing each component |
| Implantable cardiovascular physiologic monitor (e.g., CardioMEMS-style hemodynamic sensor) | 93297 | Up to 30 days; not reportable under 30 days | Global, -26, or -TC |
| Subcutaneous cardiac rhythm monitor / implantable loop recorder | 93298 | Up to 30 days; not reportable under 10 days | Global, -26, or -TC |
The table settles which code applies to which device. The next question billers ask is how often each code can be reported, and that depends on the cycle window.
How Often You Can Bill Each Code The 90-day cycle for pacemaker and ICD remote monitoring (93294, 93295, 93296) allows one billable unit per monitoring window of up to 90 days. This rule applies to a rolling period, not a calendar quarter. The 30-day cycle for physiologic monitors (93297) and loop recorders (93298) allows one billable unit per monitoring window of up to 30 days. Track this as a rolling period anchored to each patient’s own window start date, not the calendar month. CPT instructs that 93298 is not reportable when the monitoring period runs under 10 days. 93297 is not reportable for a period shorter than 30 days.
Check: Confirm device type against the implant record before you touch the claim.
90-Day vs. 30-Day Cycle Mechanics and Cross-OEM Tracking
Cycle tracking, not code choice, drives most denials in this space. The 90-day cycle applies to pacemaker and ICD remote monitoring (93294, 93295, 93296), billable once per window. The 30-day cycle applies to implantable cardiovascular physiologic monitors (93297) and subcutaneous cardiac rhythm monitors (93298), each billable once per 30-day window. These are rolling service periods, not calendar resets. The next due date runs from each patient’s own period end date.
Fragmented data across OEM portals makes those rules hard to follow in real time. When a clinic pulls data from Medtronic, Boston Scientific, Abbott, and Biotronik portals separately, the same monitoring window can be billed twice or missed entirely because no single system holds the cycle start date. A single patient can sit on three different billing clocks at once. That mix can include a 90-day CIED window, a 30-day loop recorder window, and a 30-day home monitoring device supply period. A billing process that assumes one monthly cycle will drop claims.
Anchor every claim to a documented monitoring window start date. That single record replaces the portal-by-portal date math that causes double-billed and missed windows.
Rhythm360 addresses this directly. It is a vendor-neutral platform that consolidates all OEM data, including Medtronic, Boston Scientific, Abbott, Biotronik, and others, into one dashboard. It automatically tracks device-specific CPT pairings and 90-day and 30-day cycle windows and generates auditable documentation so the claim is clean before submission. Other platforms operate in this space, including Murj, Implicity, Rhythm Management Group, and Octagos.

See how Rhythm360 tracks every cycle window
Professional vs. Technical Components: -26, -TC, and Global
For pacemaker and ICD remote monitoring, CPT represents the professional and technical components with separate codes rather than modifiers on a single code. When a single billing entity performs both the professional and technical components of remote pacemaker monitoring, report both 93294 and 93296. Do not look for a single global code. The same logic applies to ICD monitoring. Report 93295 (professional) paired with 93296 (technical) when separate entities performed the respective components.
For 93297 and 93298, the modifier structure changes. These are device-specific codes, with 93297 for implantable cardiovascular physiologic monitors and 93298 for subcutaneous cardiac rhythm monitors, and each carries its own global, -26, and -TC structure. Bill 93298 globally when one entity performs and documents both the technical and professional portions. Append modifier -26 when the entity performed only the physician or QHP analysis, review, and report. Append modifier -TC when the entity performed only the technical work. The same pattern applies to 93297.
The most common device-type mismatch denial occurs when a pacemaker claim goes out with an ICD code or the reverse. The fix is straightforward. Before submission, verify the device type against the implant record: model, manufacturer, and lead configuration.
Rule: If one entity performs both components for pacemaker or ICD remote monitoring, bill both codes, such as 93294 and 93296, instead of searching for a single global code.
The RPM and CIED Exclusion and Same-Date Bundling
Component splits are only half the clean-claim problem. The other half involves what happens when two service families land on the same date.
Consider a common denial. A patient with an implanted pacemaker also has a remote physiologic monitoring (RPM) service billed on the same date as a remote device interrogation. The denial fires because the service families are distinct and their billing rules do not stack cleanly.
Remote physiologic monitoring codes, such as 99454, and CIED remote monitoring codes, such as 93294 and 93296, are distinct service families governed by separate CPT parenthetical rules and CMS guidance. CPT blocks reporting 93298 together with 99454, among other codes. The same exclusion applies to 93297. Overlapping same-date billing of a remote device evaluation with an in-person device evaluation is a separate and equally frequent denial source. CPT parentheticals, National Correct Coding Initiative edits, and payer-specific policy govern those combinations.
The pre-submission check has three steps.
- Confirm the service family, such as CIED remote monitoring, RPM, or in-person evaluation, and verify that the code selected matches the service actually performed.
- Confirm that no same-date in-person device evaluation was billed alongside the remote monitoring code for the same device.
- Document which service was performed, by whom, and on what date. The record must also state the monitoring window’s start and end dates explicitly.
CMS guidance, CPT parentheticals, and AAPC cardiology coding guidance govern these exclusions. Verify current NCCI edits and payer-specific policies before finalizing any same-date claim combination.
External MCT Codes 93228 and 93229 in the Same Split-Component Framework
The same professional and technical split that governs CIED codes also trips up clinics billing external mobile cardiovascular telemetry, or MCT. Two questions come up most often.
Yes, 93228 and 93229 can be billed together for the same MCT episode when separate entities performed the professional and technical components. CPT 93229 is not durable medical equipment.
93228 is the professional component of external mobile cardiovascular telemetry, billed by the interpreting physician for review and interpretation of transmitted ECG data with a signed report. 93229 is the technical component, billed by the monitoring service, IDTF, or facility for device supply, patient instruction, attended surveillance, and transmission of daily and emergent data reports. CMS billing and coding article A57476 states that modifiers -TC and -26 are not used with CPT codes 93224 through 93229, because those codes are already split at the code level. A component modifier would describe a component of a component.
The DME confusion arises because 93229 carries 0.00 physician work RVUs and its Medicare payment is built entirely from practice expense and malpractice value. That structure makes it look like a supply or equipment charge. CPT 93229 is not classified as durable medical equipment in CMS fee-schedule data; it is a nationally priced Physician Fee Schedule technical monitoring service whose payment bundles the device and attended surveillance work. It functions as a diagnostic ECG service. CPT 93229 is not remote patient monitoring. RPM codes cover physiologic data collection and management time for ongoing care, whereas 93229 is a diagnostic ECG test with attended surveillance ordered for a set episode.
Check: Confirm which entity performed the technical work, staffed the attended surveillance center, supplied the device, and transmitted the data before either code goes out. Submitting both codes under a single tax ID when two separate entities performed the work appears as duplicate billing on payer edits and is difficult to unwind after payment.
The Pre-Submission Documentation Audit Checklist
Run this checklist before every CIED remote monitoring claim to keep documentation aligned with CMS expectations. CMS documentation requirements for cardiac device monitoring require records to stay available to the contractor, carry patient identification and a legible practitioner signature, support the selected diagnosis and procedure, and include the monitoring interpretation with the interpreting physician's name.
Each item below supports one of three goals: confirming device identity, locking in the monitoring window dates, and tying the interpretation to a signed clinical decision.
- Device type and manufacturer confirmed against the implant record.
- Model number and serial number documented.
- Implant date recorded.
- Lead configuration verified and matched to the correct code family.
- Monitoring window start date and end date explicitly stated.
- Interpretation and report signed by the interpreting clinician, with name and credentials.
- Care plan or follow-up action documented in the record.
Rhythm360 generates auditable documentation automatically as part of its CPT capture workflow. Each item on this checklist is populated at the time of the clinical review rather than reconstructed before billing.
See how Rhythm360 automates documentation
2026 Code Changes and Payer Rules to Confirm Before Filing
One code transition affects CIED billing directly. CMS deleted G2066 effective January 1, 2024, and instead folded the technical component work into 93297 and 93298 by adding practice expense inputs and assigning global, professional, and technical indicators for 2024, per CMS MLN Matters MM13568. Any workflow or superbill still referencing G2066 for the technical component of remote CIED monitoring should be updated.
CMS publishes the CY 2026 Medicare Physician Fee Schedule data on its PFS Data portal. The Indicators and Localities datasets supply payment-policy indicators and locality-specific amounts. CMS's RVU26D file is the official 2026 Physician Fee Schedule relative value file, containing the code-level work, practice-expense, malpractice, and total RVUs used to calculate Medicare payments. Verify current-year Medicare Physician Fee Schedule status for all cardiac device codes before finalizing claims. Avoid relying on prior-year fee schedule amounts or internally generated rate estimates.
MAC-specific LCD and billing article updates also affect covered indications and diagnosis code lists. Palmetto GBA's billing and coding article A60286, revised October 1, 2026, updated the ICD-10-CM codes supporting medical necessity for ambulatory cardiac monitoring in its jurisdiction. Verify the applicable LCD and billing article for your MAC before submission.
Quick Answers to Common Cardiac Device Billing Questions
How Often Can You Bill 93294 and 93296?
Bill 93294 and 93296 once per 90-day monitoring window, as covered in the cycle-mechanics section above. The window runs from each patient’s own start date, so the next billable date does not follow the calendar quarter. CPT does not permit reporting either code when the monitoring period runs under 30 days.
Can You Bill RPM 99454 with CIED Monitoring Codes?
Remote physiologic monitoring codes and CIED remote monitoring codes belong to separate service families. CPT parentheticals explicitly exclude 99454 from being reported alongside 93297 and 93298. Confirm the service family and check for same-date overlap before submission, because billing both for the same patient in the same period creates a known denial pattern.
Is 93229 Considered DME?
CPT 93229 is the technical component of external mobile cardiovascular telemetry, a nationally priced Physician Fee Schedule service. Its payment is built from practice expense and malpractice value rather than physician work RVUs, which reflects the nature of attended surveillance work. CPT 93229 is reported by an IDTF or physician office on the CMS-1500 or its 837P electronic equivalent, while a hospital outpatient department bills it institutionally through the OPPS.
Can 93228 and 93229 Be Billed Together?
These codes function as a professional and technical pairing for the same MCT episode and can be billed together when separate entities performed the respective components. The interpreting physician bills 93228. The monitoring service, IDTF, or facility bills 93229. Modifiers -26 and -TC do not apply to either code, because the split is already built into the code structure. Submitting both under one tax ID when two entities performed the work creates a duplicate-billing edit.
Conclusion: Make the Clean Claim Your Default Outcome
Cardiac device claims often fail on fragmented cycle tracking and component mismatches, even when billers know the codes cold. The monitoring window start date can live in four separate OEM portals. The professional and technical split can be matched to the wrong device type. The same window can be billed twice or missed entirely. These problems sit in the workflow, so they need a workflow-level fix.
Rhythm360 is the platform that automates cycle tracking, CPT capture, and compliant documentation in one place. It consolidates all OEM feeds, including Medtronic, Boston Scientific, Abbott, Biotronik, and others, into a single vendor-neutral dashboard. It tracks device-specific CPT pairings and 90-day and 30-day cycles automatically and integrates bi-directionally with Epic, Cerner, Athenahealth, eClinicalWorks, and Greenway Health. Clinicians can review transmissions and sign reports from anywhere through a HIPAA-compliant mobile app. Practices using Rhythm360 have achieved up to an 80% reduction in critical alert response times and up to a 300% increase in revenue capture and profitability.
The clean claim becomes a repeatable default when the workflow is built correctly and supported by the right tools.
Streamline your cardiac device billing workflow
.avif)