- CPT 93296 RVU +60% (Jan 1, 2026): CMS increased the technical component RVU for remote pacemaker/ICD monitoring from 0.60 to 0.95 — the largest single-code reimbursement increase in remote cardiac monitoring history. Source: CMS CY 2026 Physician Fee Schedule Final Rule.
- NCD 20.39 — CCM Coverage Effective Oct 28, 2025, Implementation Apr 6, 2026: CMS now covers Cardiac Contractility Modulation (CCM) for Heart Failure under Coverage with Evidence Development. Two new Category III CPT codes (0948T/0949T) cover remote CCM device interrogation. Transmittal 13716, April 3, 2026.
- OIG Formal RPM Audit Underway (Dec 2024, Project OAS-25-05-008): OIG is auditing Medicare Part B remote monitoring billing. RPM payments hit $536M in 2024 (+31% YoY). 25% of remote cardiac monitoring providers have documentation compliance failures per a 2023 CMS study.
- New CPT 99445 & 99470 (Jan 1, 2026): CMS added two new RPM codes allowing billing for 2–15 days of remote physiologic monitoring (not just 16–30 days) and for 10-minute RPM management time (not just 20 minutes). Cardiology RPM programs can now bill for shorter monitoring windows.
- 2025 ACC/AHA AUC for CIEDs (Feb 2025, JACC): Updated Appropriate Use Criteria expand ICD/CRT/pacing indications beyond LVEF + NYHA class to include EP testing, genetic factors, and symptom burden — requiring updated device documentation workflows.
On a typical Monday morning in a busy EP practice or cardiology device clinic, a technician logs into Medtronic CareLink. Then Abbott Merlin.net. Then Boston Scientific Latitude. Then the Biotronik Home Monitoring portal. She reviews each queue separately, cuts alerts into a spreadsheet, flags the two or three that need physician attention, and tries to update the EHR — all before her first scheduled patient walk-in at 8 AM.
Multiply that by four portals, 300 active remote monitoring patients, and a billing cycle that requires accurate 90-day periods and documented physician interpretation for every transmitted device — and you have the state of remote cardiac monitoring in the average American cardiology practice in 2026: technically sophisticated devices, manually executed follow-up.
This is the gap that automation closes. And with CMS just raising the CPT 93296 technical component reimbursement by approximately 60%, the ROI of closing it has never been clearer.
The Remote Monitoring Overload Problem
The 2023 HRS/EHRA/APHRS/LAHRS Expert Consensus Statement on Practical Management of the Remote Device Clinic — co-developed with the ACC and AHA — established remote monitoring as the standard of care for cardiac implantable electronic device (CIED) follow-up. Three types of transmissions are now expected: scheduled remote interrogations (mirroring in-office visits), automatic unscheduled transmissions triggered by predefined alert events, and patient-initiated transmissions.
For a practice with 200–400 remotely monitored patients, that standard of care generates a transmission volume that grows non-linearly. A single ICD patient on a modern platform may generate dozens of automatic transmissions per year — AF burden alerts, VT/VF episode notifications, pacing threshold changes, lead impedance alerts, battery voltage readings, and ERI (Elective Replacement Indicator) flags. Not all of these are clinically urgent. In fact, studies suggest the majority of automatic transmissions are non-actionable — but every one must be reviewed and documented before the physician interpretation that supports billing can occur.
The result is a device clinic that spends hours every day triaging a mixed-severity alert queue — and that inevitably under-documents or under-bills the monitoring codes, because the volume exceeds what manual workflows can handle accurately at scale.
Medtronic CareLink, Abbott Merlin.net, Boston Scientific Latitude, and Biotronik Home Monitoring each use proprietary alert formats, transmission schedules, and data export structures. A practice with patients on all four manufacturers must maintain separate logins, separate review queues, and manually reconcile data across four systems — none of which talks to the EHR automatically.
The Remote Monitoring CPT Codes — And the 2026 Revenue Opportunity
Before diving into automation mechanics, it's worth understanding exactly what CMS pays for — because the new 2026 reimbursement structure makes the financial case for automation far more compelling than it was even 12 months ago.
| CPT Code | Description | Frequency | 2026 Rate (Est.) | Key 2026 Change |
|---|---|---|---|---|
| 93294 | Remote pacemaker interrogation — physician professional component | ≤ 1× / 90 days | ~$55–75 | No major change |
| 93295 | Remote ICD/CRT-D interrogation — physician professional component | ≤ 1× / 90 days | ~$60–80 | No major change |
| 93296 | Remote pacemaker/ICD monitoring — technical component | ≤ 1× / 90 days | ~$34–52 | ⬆ ~60% RVU increase (0.60 → 0.95) |
| 93297 | Remote ICD/CRT-D interrogation — technical component | ≤ 1× / 90 days | ~$45–60 | Separate from 93296 |
| 93298 | Remote implantable loop recorder (ILR) interrogation — technical component | ≤ 1× / 90 days | ~$35–50 | No major change |
| 0948T | CCM system remote interrogation — professional component (NEW 2026) | ≤ 1× / 90 days | Category III (not RVU-valued yet) | New code — CCM NCD coverage effective Apr 6, 2026 |
Note: Exact reimbursement amounts vary by MAC locality and conversion factor updates. Confirm with your MAC's published fee schedule. Effective date: January 1, 2026 for 93296 RVU change.
The math on the CPT 93296 change is straightforward. A practice managing 150 remotely monitored patients bills this code up to 4 times per year per patient — that's 600 technical component claims annually. At $32 additional revenue per claim (the approximate delta from the RVU increase), that's $19,200 in recaptured annual revenue from a single code change. For a practice with 300 monitored patients, the number roughly doubles. None of this requires new patients, new devices, or new contracts — it's revenue that CMS already authorized, which only flows to practices that automate the billing cycle precisely enough to capture it.
What Remote Cardiac Monitoring Automation Actually Does
The goal of automation isn't to replace the cardiologist or EP physician — it's to remove every non-clinical step that currently sits between a device transmission and a signed physician interpretation note. Here is the workflow a purpose-built automation layer executes:
Unified Vendor Data Ingestion
The automation layer authenticates with all four major device vendor portals — Medtronic CareLink, Abbott Merlin.net, Boston Scientific Latitude, and Biotronik Home Monitoring — on a scheduled basis (typically every 2–4 hours for ICDs; daily for pacemakers). It pulls all pending transmissions, normalizes the alert data into a standardized format, and eliminates duplicate alerts from the same event across portals. The device clinic technician no longer logs into four portals; they review one queue.
Automated Alert Severity Classification
Not all alerts require the same urgency. The automation engine applies configurable clinical rules to classify each alert by severity: Critical (VT storm, complete lead failure, ERI flagged within 30 days — pages physician immediately); Urgent (sustained VT episode, new AF burden above 24-hour threshold, significant lead impedance change — physician review within 4 hours); Routine (minor pacing threshold drift, battery voltage nominal check, scheduled 90-day interrogation data — 5-business-day review window). Only critical alerts break the physician's calendar. Routine alerts queue for scheduled review sessions.
ERI (Elective Replacement Indicator) Tracking
One of the highest-stakes — and most manually error-prone — tasks in any device clinic is tracking patients approaching device ERI, the battery voltage threshold indicating the device needs replacement within a defined window (typically 3–6 months). An automated ERI tracker continuously monitors battery voltage data from each transmission, maintains a rolling ERI candidate list sorted by estimated time-to-replacement, and triggers generator change scheduling workflows when a patient enters the ERI window. This prevents the scenario every device clinic dreads: a patient whose device reaches EOL (End of Life) before a generator change was scheduled.
Structured EHR Documentation
For each reviewed transmission, the automation layer pre-populates a structured note in the EHR — Epic, Athena, ModMed, NextGen, or the cardiology EHR in use — with device type, transmission date, alert summary, device parameters, and a physician signature field. The physician reviews the structured note, adds clinical commentary, and signs. This produces the documentation that supports both CPT 93294/93295 billing and OIG audit defense: a timestamped record linking every remote transmission to a physician interpretation event within the 90-day billing period.
Automated Billing Cycle Management
The billing layer tracks each patient's 90-day monitoring period, ensures the required 30-day minimum is met before generating a claim, pairs the technical component (93296 or 93297) with the physician interpretation code (93294 or 93295), and creates a clean claim in the practice management system. For loop recorder patients, the system separately tracks 93298 billing periods. The result: no missed billing windows, no 90-day period overlap errors, and no unbilled monitoring months from manual tracking gaps.
OIG Is Watching: Why Documentation Automation Is Now Non-Negotiable
The OIG's December 2024 announcement of a formal audit of Medicare Part B Remote Patient Monitoring Services (Project OAS-25-05-008) is not abstract risk — it is the OIG explicitly stating that $536 million in annual payments warrant scrutiny. In its Fall 2025 Semiannual Report to Congress, OIG identified RPM as an enhanced oversight priority and flagged three specific billing fraud patterns: unsolicited device shipments, inadequate monitoring (billing for monitoring that didn't actually occur), and inappropriate billing (incorrect period lengths or code combinations).
For cardiology practices, the most common audit trigger is the third category: billing 93296 when the monitoring period is less than 30 days, or billing it more than once per 90-day period. A 2023 CMS compliance review found that one in four remote cardiac monitoring providers had documentation gaps — most commonly, the absence of a documented physician interpretation note paired to each billed technical component claim.
Automation doesn't just make billing faster — it creates an immutable audit trail. Every transmission is timestamped. Every alert classification is logged. Every physician signature is attached to a structured note. Every 90-day billing period is calculated by the system, not by a human counting days on a calendar. When an OIG auditor requests records for CPT 93296 claims, an automated system produces a clean, structured response in hours. A manual system produces a document retrieval scramble that often reveals the gaps that triggered the audit in the first place.
Cardiac Device Vendor Integration: CareLink, Merlin.net, Latitude, and Biotronik
The four major cardiac device vendors each operate proprietary remote monitoring platforms with distinct data architectures. Medtronic's CareLink Network serves the largest installed base of pacemakers and ICDs globally. Abbott's Merlin.net platform supports the CardioMEMS pulmonary artery pressure monitor in addition to cardiac devices. Boston Scientific's LATITUDE NXT platform is widely deployed for ICD and CRT management. Biotronik's Home Monitoring system is differentiated by its daily automatic transmission capability — every morning, not just when an alert fires.
Each platform exports alert data in a different format, uses different severity terminology, and has different transmission trigger configurations. A practice with a mixed installed base — which is nearly every large cardiology practice in America — cannot manage these four systems through their native portals alone at any meaningful scale without dedicated full-time device clinic staff for every 100–150 monitored patients.
A custom integration layer resolves this by creating a single normalized data model that maps each vendor's alert types, device parameters, and transmission metadata to a common schema. An "AF burden alert" from CareLink and an "Atrial Tachycardia episode" from LATITUDE both route to the same triage rule in the same queue, with the same documentation template triggered downstream. The cardiologist reviews one interface, not four.
This is particularly important as newer devices come to market. The recently implemented CMS NCD 20.39 (Cardiac Contractility Modulation for Heart Failure, effective October 28, 2025, implementation April 6, 2026) created coverage for CCM devices — specifically the Optimizer Smart system by Impulse Dynamics — and introduced Category III CPT codes 0948T and 0949T for remote CCM interrogation. A flexible automation layer can onboard a new device vendor without rebuilding the entire monitoring workflow from scratch.
Why Epic Cardiology, Athena, and Vendor Portals Alone Aren't the Answer
Major EHR vendors have invested in cardiology modules, and some device manufacturers have built basic EHR integrations. But there is a significant gap between what the native tools offer and what a practice needs to run a high-volume remote monitoring program at full reimbursement capture.
Epic's cardiology module, for example, provides structured cardiac procedure documentation and some device data integration — but it does not provide automated alert triage across all four vendor portals, automated ERI tracking with scheduling triggers, or automated 90-day billing period management. It is a documentation tool, not a workflow engine. Similarly, Athena's cardiology extensions handle notes and orders well but rely on manual data entry from vendor portals for device monitoring documentation.
The gap is not a criticism of EHR vendors — it reflects the reality that remote cardiac monitoring is a specialized workflow with vendor-specific data formats that no general-purpose EHR can fully automate. Custom software built specifically for the monitoring workflow — and integrated into the EHR via API rather than replacing it — is the architecture that high-volume device clinics use to scale without proportionally scaling headcount.
SynergyIQ has built similar custom automation layers for healthcare IT workflows across multiple specialties. The pattern is consistent: identify the workflow steps that are purely mechanical (data retrieval, format normalization, period calculation, billing code selection), automate those completely, and leave the clinical judgment steps (alert significance, physician sign-off, patient communication) in human hands. The result is a device clinic that handles 2–3× the patient volume with the same staff, higher documentation accuracy, and complete billing cycle coverage.
The ROI Case: What Automation Is Worth to a Cardiology Practice
The financial case for remote cardiac monitoring automation rests on four pillars: increased code capture, improved billing accuracy, staff redeployment, and audit risk mitigation.
On code capture: MedAxiom data and independent cardiology practice benchmarks consistently show that 15–25% of billable remote monitoring events go unbilled in manual workflows — most commonly because the 90-day period elapsed without a clean paired claim, or because a physician interpretation note was never formally documented. Automation closes this gap entirely. For a 200-patient monitoring program billing at the 2026 93296 rate, recovering a 20% billing gap represents approximately $12,000–$18,000 in additional annual revenue.
On billing accuracy: the 93296 RVU increase alone — from 0.60 to 0.95 — generates meaningful additional revenue per claim. At 800 annual claims across a 200-patient program billed quarterly, the delta is approximately $25,600 per year simply from correctly capturing the updated rate. This revenue exists only if the billing system is correctly configured with 2026 RVU values — another manual process that automation handles automatically.
On staff efficiency: a device clinic technician managing 150 patients manually spends approximately 2–3 hours daily on portal review, alert logging, and documentation. Automation reduces that to 30–45 minutes of exception review for flagged critical and urgent alerts. The time recaptured either allows growth — managing 300+ patients with the same staffing — or allows the technician to shift toward higher-value clinical support tasks.
On audit risk: the cost of an OIG adverse finding — repayment demands, corporate integrity agreements, exclusion from Medicare programs — vastly exceeds the investment in documentation automation. Building the audit trail proactively is categorically cheaper than rebuilding it reactively under scrutiny.
How SynergyIQ Builds Remote Cardiac Monitoring Automation
SynergyIQ is a Richmond, TX-based managed IT and AI workflow automation company that works with cardiology practices, EP labs, and cardiac device monitoring centers to build custom remote monitoring automation. We don't sell generic software — we engineer workflow engines built specifically for your patient panel, your vendor mix, your EHR, and your payer contracts.
A typical engagement starts with a Free Cardiology Workflow Audit: we map your current device clinic workflow — portal login sequence, alert review process, documentation steps, billing cycle — time every step, quantify the volume of transmissions per month per device type, and identify where revenue is leaking and where audit risk is accumulating. The output is a scored automation roadmap with estimated annual revenue impact for each proposed automation layer, before you commit to anything.
From there, implementation typically follows a phased approach: vendor data ingestion and normalization in Phase 1; alert triage and EHR documentation integration in Phase 2; billing cycle automation and ERI tracking in Phase 3. Most practices see full automation operational within 60–90 days. The system integrates on top of your existing EHR — we don't require you to replace Epic, Athena, or ModMed — and expands as your monitoring program grows.
Interested in seeing how this applies to your practice? Contact us or book a free consultation to discuss your specific monitoring volume, vendor mix, and EHR environment.
The Bottom Line
Remote cardiac monitoring is one of the most technically demanding — and most undercompensated — workflows in cardiology. Devices generate transmissions around the clock. Alerts arrive from four separate vendor platforms, in four separate formats, with varying urgency. Billing requires precise 90-day period management, paired professional and technical component claims, and documented physician interpretation for every billed event. And OIG is now watching.
The 2026 CPT 93296 reimbursement increase is a signal that CMS recognizes the legitimate work involved in remote cardiac monitoring. But that increase only flows to practices that automate the billing cycle precisely enough to capture it — because manual workflows operating at scale inevitably miss billing windows, produce documentation gaps, and under-code the monitoring work that physicians are actually doing.
The practices building remote cardiac monitoring automation now are the ones that will run 300-patient device clinics in 2027 with the same staff they have today, at full reimbursement capture, and with an OIG-ready audit trail that demonstrates they earned every dollar they billed.
Frequently Asked Questions
What CPT codes cover remote pacemaker and ICD monitoring?
The primary remote cardiac device monitoring codes are: 93294 (remote pacemaker interrogation, professional component, up to 90 days); 93295 (remote ICD/CRT-D interrogation, professional component, up to 90 days); 93296 (remote pacemaker and ICD monitoring, technical component — RVU increased approximately 60% in 2026, from 0.60 to 0.95); 93297 (remote ICD/CRT-D interrogation, technical component); and 93298 (remote implantable loop recorder interrogation, technical component). All are reported no more than once every 90 days and require the monitoring period be at least 30 days.
How much did CMS change CPT 93296 reimbursement in 2026?
Effective January 1, 2026, CMS updated the total RVU for CPT 93296 from 0.60 to 0.95 — an approximately 60% increase. This reflects CMS's recognition that the technical work requires a cardiovascular technician and takes over 80 minutes per 90-day period. In dollar terms, this translates to roughly $32 more per service. A cardiac device clinic managing 100 remote monitoring patients gains approximately $38,400 more per year from this single code change — but only if billing is automated and properly documented.
What is the OIG audit risk for remote cardiac monitoring billing?
The OIG announced a formal audit of Medicare Part B Remote Patient Monitoring Services in December 2024 (Project OAS-25-05-008). Medicare and Medicare Advantage RPM payments reached $536 million in 2024 — a 31% single-year increase. A 2023 CMS study found 25% of remote cardiac monitoring providers had documentation failures. Audit-proofing requires documented alert logs, physician interpretation notes tied to each remote transmission, and proof that monitoring periods met the 30-day minimum before billing the 90-day code.
Can one automation system pull data from Medtronic CareLink, Abbott Merlin.net, Boston Scientific Latitude, and Biotronik simultaneously?
Yes — this is exactly what a custom cardiac device monitoring automation layer is designed to do. A unified automation layer ingests transmissions from all four vendor portals, normalizes the alert data into a single triage queue, applies severity rules, and posts structured notes to the EHR for physician sign-off — eliminating the 4-portal-per-morning workflow that device clinic staff currently manage manually.
How does SynergyIQ help cardiology practices automate remote device monitoring?
SynergyIQ builds custom remote cardiac monitoring automation for cardiology practices, EP labs, and cardiac device monitoring centers. We integrate with your existing EHR and all four major device vendor portals to create a unified triage and billing engine. A free Cardiology Workflow Audit is the starting point — we map your current workflow, quantify unbilled 93296/93297/93298 revenue, identify non-actionable alert burden, and model ROI before you commit to anything.
Ready to automate your cardiac device clinic?
Tell us about your monitoring program — patient volume, device vendors, EHR — and we'll build you a personalized automation roadmap with revenue impact estimates. Free, no obligation.