RESOURCES | BLOG

October 7, 2026

Loop Recorder Monitoring Guidelines: ILR Clinic Protocol

Master ILR remote monitoring with Rhythm360's step-by-step clinic protocol — covering alerts, follow-up intervals, CPT codes, and more.

Key Takeaways

Implantable loop recorders (ILRs) continuously monitor cardiac activity for up to three years and transmit electrograms to remote platforms for clinician review and alert management.
Effective ILR monitoring relies on a repeatable workflow: indication-specific alert programming, EGM verification, structured follow-up intervals, removal planning, and auditable billing documentation.
The 2023 HRS/EHRA/APHRS/LAHRS consensus provides an evidence-based framework for alert-based remote monitoring, staffing, workflows, and patient education in device clinics.
CPT 93298 governs ILR remote monitoring on a 30-day cycle and demands complete physician-signed documentation to ensure compliance and reimbursement.
Rhythm360 brings ILR data from all major manufacturers into one AI-powered dashboard with automated CPT capture and EHR integration.

Schedule a Demo With Rhythm360

How ILR Monitoring Fits Into the Healthcare Ecosystem

ILR monitoring involves a layered ecosystem in which each role hands off to the next. Implanting electrophysiologists (EPs) select the device and set the initial indication, then hand ongoing management to device clinic staff. Cardiac device technicians (CCTs), RNs, NPs, and PAs handle daily transmissions, EGM review, and escalation. Those reviews flow to ordering physicians, who receive clinical summaries and sign interpretations, and to billing teams, who translate completed monitoring periods into CPT claims. EHR systems such as Epic, Cerner, Athenahealth, eClinicalWorks, and Greenway Health provide the documentation backbone.

The four major ILR device families each transmit through proprietary manufacturer portals. Medtronic Reveal LINQ and LINQ II insertable cardiac monitors transmit patient data to the Medtronic CareLink network via the MyCareLink patient monitor, Abbott Confirm Rx via Merlin.net, Boston Scientific LUX-Dx via LATITUDE, and Biotronik BIOMONITOR via Home Monitoring. The 2023 HRS/EHRA/APHRS/LAHRS consensus endorses alert-based remote monitoring that relies on continuous connectivity, which allows extended intervals between in-office device interrogations. The consensus notes that ILRs are designed for alert-based management and warns that this approach requires near-perfect connectivity and excellent patient compliance to replace structured intermittent follow-up effectively.

Structural challenges persist across most device clinics. Staff must log into multiple non-interoperable OEM portals to retrieve data, and manual retrieval creates alert fatigue when non-actionable transmissions accumulate alongside true events. Documentation for CPT 93298 is often inconsistent, which leads to denials and lost revenue. Rhythm360 by RhythmScience is a vendor-neutral, AI-powered platform that unifies ILR data from Medtronic LINQ, Abbott Confirm, Boston Scientific LUX-Dx, and Biotronik BIOMONITOR into one dashboard with automated CPT capture and bi-directional EHR integration.

How to Monitor a Loop Recorder in Daily Practice

The following seven-step workflow turns the 2023 HRS/EHRA/APHRS/LAHRS consensus into a repeatable clinic protocol that applies to any ILR device family.

Transmission Received. A remote transmission arrives, either automatically on a scheduled interval or patient-activated after a symptom. The platform timestamps the receipt and queues it for review.
Verify Patient and Device Identity. Confirm the transmission matches the correct patient record and device model (for example, Medtronic LINQ II, Abbott Confirm Rx, Boston Scientific LUX-Dx, Biotronik BIOMONITOR) before opening the EGM. Device-type mismatch at this step causes downstream billing errors.
Review the EGM. Open the stored electrogram. Assess ventricular rate and V-V intervals, examine the atrial-ventricular relationship (V>A suggests ventricular tachycardia; A>V suggests AF or atrial tachycardia; A=V 1:1 requires further discrimination), evaluate onset pattern, and compare waveform morphology against the stored sinus-rhythm baseline EGM.
Classify the Event: True Arrhythmia vs. Artifact. An alert does not automatically represent a true arrhythmia. Compare the near-field (bipolar) EGM with the far-field EGM: genuine arrhythmias appear on both channels, while lead noise appears only on the affected channel. When the two channels disagree, artifact is the likely cause, so look for non-physiologically short intervals, irregular non-reproducible intervals, or signals absent from the far-field channel. T-wave oversensing appears as a regular extra beat between true R waves, and myopotential oversensing produces fine, irregular signals that correlate with arm movement. MRI-related artifacts, which can mimic both tachyarrhythmias and bradyarrhythmias, should remain provisional until the tracing is reviewed in context, per guidance on ILR MRI interactions.
Assess Clinical Significance Against the Original Indication. Evaluate each detected rhythm against the reason for implantation. A 6-second pause in a syncope patient is actionable, while the same pause in an AF-screening patient may require different escalation logic. Obtain patient context, including what the patient was doing at the time of the event, before finalizing interpretation.
Contact the Patient and/or Ordering Physician Per Escalation Protocol. Distinguish urgent (red) alerts from non-urgent (yellow) alerts. Document all communications, including phone call logs, with timestamps in the patient record. The 2026 JHRS consensus supports this two-tier alert classification in ILR workflows.
Document and Reprogram Alerts as Needed. Complete the signed interpretation with a clinical impression. Vendor printouts alone do not suffice. Adjust alert thresholds if false-positive rates are high, and update the monitoring period start date for the next 30-day CPT 93298 cycle.

Indication-Specific Alert Programming

The 2026 JHRS consensus explicitly recommends customizing ILR alert settings to the clinical indication rather than applying a universal template, because ILRs generate a high rate of false-positive arrhythmia detections. Three indication-specific programming frameworks apply.

Syncope: Prioritize pauses, bradycardia, and asystole thresholds. Enable patient-activated event marking so symptom-correlated EGMs are preserved. Policy guidance supports programming that prioritizes bradycardia, pauses, tachycardia, and symptom correlation for syncope indications.
Cryptogenic Stroke / AF Detection: Prioritize AF burden and duration thresholds. The CRYSTAL AF trial found ILRs detected AF in 30% of cryptogenic stroke patients at 36 months versus 3% with 24-hour Holter monitoring, which underscores the value of sustained AF-burden monitoring.
General Arrhythmia Surveillance: Prioritize ventricular tachycardia detection and high-rate episode thresholds. Minimize sensitivity settings that generate myopotential noise.

Follow-Up Intervals for ILR Patients

Alert-based remote monitoring reduces the need for scheduled in-person interrogations. In-person checks usually occur at implant, at an optional mid-monitoring visit if clinical questions arise, and at removal. Remote transmission review serves as the primary follow-up mechanism throughout the device's monitoring life.

Strategic Considerations and Trade-Offs

Organizations building or scaling an ILR monitoring program face several structural decisions. Centralized monitoring, where a dedicated team reviews all transmissions, improves consistency and escalation accountability but requires sufficient volume to justify staffing. Decentralized models distribute review across clinic staff but risk inconsistent alert handling and documentation gaps.

Staffing models vary by where clinical judgment enters the workflow. CCT-led review offers device-specific expertise but keeps clinical judgment late in the process. RN- or NP-led models move that judgment earlier. AI-assisted triage reduces non-actionable transmission volume before any human review. Each choice carries different cost, scalability, and governance implications.

EHR integration complexity is a material trade-off. Bi-directional integration with Epic, Cerner, or Athenahealth eliminates manual transcription but requires implementation planning. Practices that manage ILR transmissions across multiple OEM portals without a unified platform face compounding documentation risk as volume grows. For workflow parallels in pacemaker and ICD monitoring, see Pacemaker ICD Remote Monitoring: A Clinic Workflow Guide.

See How Rhythm360 Unifies Your ILR Data

Readiness and Implementation Considerations

Organizational readiness for a structured ILR monitoring program depends on six factors.

Stakeholder alignment among EPs, clinic staff, and administrators
Workflow maturity, including defined escalation paths and documentation standards
Data quality, including complete patient and device enrollment
EHR integration needs
Compliance processes for CPT 93298 documentation
Staff training on EGM interpretation and alert triage

Readiness starts with stakeholder alignment, because without it the remaining factors stall. From there, clinics build workflow maturity, improve data quality, plan EHR integration, tighten compliance processes, and train staff on EGM review.

A phased rollout reduces implementation risk. Start by standardizing alert programming by indication across all enrolled ILR patients. Then conduct EGM verification training for all staff who review transmissions. Finally, integrate billing documentation workflows so CPT 93298 claims are submitted only after the full 30-day monitoring period closes with a signed physician interpretation.

Rhythm360's implementation process, including EHR integration, typically takes a few days to a few weeks. The platform ingests data from all major ILR manufacturers and normalizes it into a single dashboard, which eliminates the need for staff to log into separate OEM portals.

Common Pitfalls and Risks

Even with a phased rollout, ILR programs tend to fail in predictable ways. The most common operational failures in ILR monitoring programs fall into four categories, with a fifth patient-education risk that clinics often overlook.

Generic Alert Programming: Applying the same alert thresholds regardless of indication generates excessive false positives in AF-screening patients and may miss pauses in syncope patients. Indication-specific programming forms the foundation of a defensible protocol.
Skipping EGM Verification: Accepting the device's event classification label without reviewing the underlying EGM tracing leads to both over-treatment of artifact and under-treatment of true arrhythmias. Always verify the device label against the underlying EGM tracing, because the label reflects the algorithm's interpretation rather than the actual rhythm.
Unclear Escalation Ownership: When no staff member is explicitly responsible for urgent alert response, critical events are delayed. The CONNECT study found remote monitoring reduced median time from clinical event onset to clinical decision from 22 days to 4.6 days, and that benefit depends on a defined escalation owner.
Weak CPT 93298 Documentation: Vendor printouts alone do not satisfy the CPT 93298 interpretation requirement. A physician-authored clinical impression with a signature and date is required for every billing period.
Treating Remote Monitoring as Emergency Monitoring: ILRs do not replace emergency evaluation for acute symptoms. Patients must understand that acute symptoms require urgent medical evaluation rather than reliance on the ILR transmission cycle.

Additional limitations include connectivity gaps that delay transmissions, finite device storage that can overwrite important EGMs if data are not downloaded promptly, and false-positive AF alerts driven by premature beats misinterpreted by the detection algorithm, as documented in a systematic review of false alarms in ILR remote monitoring. These pitfalls affect care quality, staff efficiency, and billing performance simultaneously.

Loop Recorder Monitoring CPT Codes 93297 and 93298

Because weak CPT 93298 documentation is one of the most common pitfalls, clinics benefit from a clear view of what these codes cover. CPT 93297 and CPT 93298 are device-specific codes, each covering a different type of monitor. CPT 93297 covers remote interrogation of an implantable cardiovascular physiologic monitor that reports hemodynamic data, such as a CardioMEMS pulmonary artery pressure sensor. CPT 93298 covers remote interrogation of a subcutaneous cardiac rhythm monitor, the ILR or ICM, and applies to devices such as the Medtronic LINQ II, Abbott Confirm Rx, Boston Scientific LUX-Dx, and Biotronik BIOMONITOR. Applying 93297 to a loop recorder or 93298 to a hemodynamic monitor creates a device-type mismatch and is a leading cause of claim denial, per CPT 93298 billing guidance.

Both codes run on a 30-day monitoring cycle, which differs from the 90-day cycle used for pacemakers (93294/93296) and ICDs (93295/93296). Each is billable once per completed 30-day period and can be billed globally, with modifier -26 when the physician bills only the analysis and signed report, or with modifier -TC when the monitoring entity bills for data acquisition and technician review. CMS deleted HCPCS code G2066 effective January 1, 2024, and assigned technical components directly to CPT 93297 and 93298, enabling the -26 and -TC modifier split, per CPT 93298 billing analysis.

Five documentation elements are required for an auditable CPT 93298 claim:

Proof of a completed remote transmission with timestamp and correct patient/device identification
Evidence the monitoring period covered the full 30 days
Review of recorded rhythm data and stored or patient-triggered episodes
A physician-authored interpretation with a clinical impression
A signature and date matching the date of service

CPT 93298 is captured on a 30-day cycle, so practices file up to twelve claims per year, per CPT 93298 billing guidance. Rhythm360 automates CPT capture and documentation for each completed 30-day monitoring period, which reduces denials from unsigned reports, premature submission, and device-type mismatch. For compliance documentation frameworks applicable across device types, see Pacemaker Monitoring Compliance Documentation & Audit Tools.

Measurement and Ongoing Optimization

Avoiding those pitfalls requires measurement. A mature ILR monitoring program tracks performance across four metric categories.

Clinical: Time from transmission receipt to true event detection, alert accuracy rate by indication, and time from symptom-activated transmission to physician review.
Operational: Staff hours per transmission reviewed, escalation response times by alert tier, and portal login time eliminated through platform consolidation.
Financial: CPT 93298 capture rate per enrolled patient per year, denial rate by denial reason, and revenue recovered from previously unbilled 30-day periods.
Compliance: Percentage of claims with complete five-element documentation, audit-ready report availability, and signed interpretation turnaround time.

Practices implementing Rhythm360 have achieved up to an 80% reduction in critical alert response times and up to a 300% increase in revenue capture and profitability. Ongoing optimization involves periodic review of alert programming thresholds by indication, staffing model adjustments as ILR volume grows, and system configuration updates as new device firmware changes detection algorithms. For monitoring frequency benchmarks across device types, see Pacemaker Monitoring Schedule: Intervals & Guidelines.

Measure the ROI of Your ILR Program

Frequently Asked Questions (FAQ)

How Often Should a Loop Recorder Be Interrogated?

ILR patients enrolled in remote monitoring do not require frequent scheduled in-person interrogations. Alert-based remote transmissions, sent automatically on a device-defined schedule or triggered by the patient after a symptom, serve as the primary follow-up mechanism. In-person visits are typically limited to the implant appointment, an optional mid-monitoring check if clinical questions arise, and the removal visit. As noted earlier, the 2023 consensus endorses alert-based monitoring, but it depends on near-perfect connectivity and patient compliance.

What Should You Not Do With a Loop Recorder?

Patients with an ILR should avoid relying on the device for acute or emergency symptoms. The ILR records and transmits stored data on a scheduled or patient-activated basis, so it does not function as a real-time emergency monitoring system. Patients experiencing severe palpitations, loss of consciousness, chest pain, or other acute symptoms should seek immediate medical evaluation rather than waiting for a transmission to be reviewed. Patients should also keep active mobile phones at least 15 cm (6 inches) from the device to reduce electromagnetic interference, and should inform MRI operators of the device before any scan, because MRI environments can create artifacts on stored recordings and, in some cases, alter stored data.

What Are the Downsides of Loop Monitoring?

ILR monitoring has several documented limitations. The device captures a single subcutaneous ECG channel, which has lower signal amplitude than a surface ECG and can affect P-wave visibility and atrial arrhythmia classification accuracy. The main downsides also include the connectivity, storage, and false-positive alert issues described in the pitfalls section, plus the fact that the ILR cannot deliver therapy. Finally, implantation and eventual removal each require a minor surgical procedure under local anesthesia.

Does It Hurt to Have a Loop Recorder Removed?

ILR removal is performed under local anesthesia as a day-case procedure, typically taking 30 to 45 minutes including pre- and post-procedural care. Patients are awake and should not feel pain during the procedure, though some pressure or pushing may be noticeable. The removal incision is slightly larger than the implant incision to allow forceps to grasp the device. Devices that have been in place longer may be more difficult to remove, though this is not always the case. Bruising and mild discomfort at the site are common and typically resolve within days. Serious complications, including infection and hematoma, occur in less than 1% of cases. Patients are generally advised to avoid strenuous activity and heavy lifting for 3 to 5 days after removal.

How Much Does It Cost to Remove a Loop Recorder?

ILR removal is billed under CPT 33286, which covers explantation of a subcutaneous cardiac rhythm monitor. The specific reimbursement amount varies by payer, geographic locality, and whether the service is performed in an office or facility setting. Patients should contact their insurance provider or the performing clinic for an estimate of out-of-pocket costs. The removal procedure itself is typically straightforward and does not require hospitalization.

Should a Loop Recorder Be Removed?

An ILR is typically removed when it has fulfilled its monitoring purpose, meaning a diagnosis has been confirmed or excluded, when the battery is depleted, when a device or implant-site problem such as persistent infection or erosion requires it, or when the patient elects removal for any reason. If ILR findings indicate a treatment is needed, such as a slow rhythm requiring a pacemaker, the ILR may be removed during the same procedure as the new device implant. When monitoring must continue beyond the current device's battery life, the old ILR can be removed and a new one placed in the same subcutaneous pocket as a single procedure. A depleted ILR is safe to leave in place, although removal is generally recommended once it can no longer record data.

Can I Go Through TSA With a Loop Recorder?

Patients with an ILR can go through airport security as normal. Presenting the device identification card to security personnel is recommended. The ILR does not deliver shocks or therapies and poses no safety risk in the airport security environment. Patients should carry their device ID card when traveling and ensure they have adequate travel insurance, as recommended by clinical centers managing ILR patients.

Will My Loop Recorder Set Off a Metal Detector?

The ILR is a very small device and may or may not trigger a metal detector, depending on the sensitivity of the equipment. Patients are advised to carry their device identification card and inform security personnel of the implant if asked. Standard airport security screening, including walk-through metal detectors and millimeter-wave scanners, does not damage the ILR or alter its programmed settings. The device does not interfere with and is not affected by standard household electronic devices such as mobile phones used at a safe distance.

Conclusion

Loop recorder monitoring guidelines are as much an operational challenge as a clinical one. The 2023 HRS/EHRA/APHRS/LAHRS Remote Device Clinic consensus provides a framework that includes alert-based remote monitoring as the standard follow-up model, indication-specific programming, EGM verification, and auditable documentation. Translating that framework into a defensible clinic protocol requires structured workflows, trained staff, and systems that can unify data across device manufacturers. CPT 93298 on a 30-day cycle, rather than the 90-day pacemaker or ICD calendar, is the correct billing model for ILR remote monitoring, and consistent documentation often determines whether revenue is captured or lost. Rhythm360 operationalizes each layer of this protocol, from multi-manufacturer data ingestion to automated CPT capture, so device clinic teams can focus on clinical decisions rather than administrative overhead.

Get Started With Rhythm360 ILR Monitoring