A manufacturer-specific programmer paired with a telemetry wand pulls stored diagnostics, real-time measurements, and programmed parameters from an implanted cardiac device during this procedure. The full check pulls battery voltage, lead impedance, pacing and sensing thresholds, and stored arrhythmia events in one transmission. You place a wand over the device pocket, wait for a complete telemetry signal, and review a printed report that drives every clinical decision at that visit.
This guide walks through interrogating a pacemaker from equipment setup through final documentation, built around the three device families you will see most often in a follow-up clinic. You will move from wand placement to parameter interpretation, red-flag triage, and CPT-coded documentation.
What Pacemaker Interrogation Actually Involves
Interrogation is a read-only retrieval of everything the device has tracked since the last check. The programmer pings the implanted pulse generator through a telemetry wand held over the skin, and the device returns battery status, lead measurements, threshold trends, event counters, and any stored electrograms (EGMs) it has recorded. You review the results first, then decide whether any setting needs to change.
Interrogation, Programming, and Remote Monitoring Are Not the Same Thing
Interrogation reads data. Programming writes new settings to the device, a separate step that requires a deliberate command and a confirmation prompt. Remote monitoring through Medtronic CareLink, Boston Scientific Latitude, or Abbott Merlin transmits a compressed subset of the same data over the patient’s home transmitter, usually overnight, without a wand or a programmer in the room. Each workflow carries its own cadence and its own blind spots, which is why in-clinic checks still matter even when remote transmissions are arriving regularly.
The Three Device Families You Will Encounter
Pacemakers treat bradyarrhythmia, implantable cardioverter-defibrillators (ICDs) add shock therapy for ventricular arrhythmias, and cardiac resynchronization therapy (CRT) devices add a third lead to coordinate contraction in heart failure. Every interrogation workflow applies to all three, but ICDs and CRTs surface additional data such as shock therapy history and biventricular pacing percentages that influence interpretation.
A complete check pulls battery, leads, thresholds, and stored events every time, even when the patient feels fine. Skipping one of those categories because the last visit looked normal is how early lead failure gets missed.
Equipment, Programmer Heads, and Manufacturer Compatibility
Each manufacturer sells its own programmer, telemetry wand, and software, and a wand from one brand will not talk to a device from another. Confirming the device make and model before the patient walks in is the single biggest time-saver in a device clinic.
| Manufacturer | Programmer Family | Telemetry Wand | Compatible Devices |
|---|---|---|---|
| Medtronic | CareLink 2090 / Encore | Medtronic telemetry wand | Medtronic pacemakers, ICDs, CRTs |
| Boston Scientific | Latitude / Zoom | Zoom Latitude programming wand | Boston Scientific pacemakers, ICDs, CRTs |
| Abbott (formerly St. Jude Medical) | Merlin PCS | Abbott telemetry wand | Abbott and legacy St. Jude devices |
BIOTRONIK devices use the Renamic programmer and a dedicated wand, and Micra leadless pacemakers from Medtronic communicate through a different protocol that still requires the CareLink system. The implant card, patient diary, or a quick call to the implanting center clears up any ambiguity before the visit.
Pre-Clinic Workflow That Prevents Wasted Time
Run a quick mental checklist before the patient arrives. Confirm the manufacturer from the chart or implant card, then confirm the device family (pacemaker, ICD, or CRT). Next, confirm whether the patient is enrolled in remote monitoring, since that changes what you expect to see between visits. Have the matching wand plugged into the programmer and the software booted up, because a dead battery in the wand or an unlicensed laptop will halt the entire schedule.
The Interrogation Procedure From Wand Placement to Final Report
The physical act of interrogation takes about five to fifteen minutes once telemetry is established, and most of that time is spent waiting for the device to transmit a complete data set rather than actively clicking through screens.
Positioning the Patient and the Wand
Seat the patient so the device pocket faces up and is easy to reach. Hold the wand flat against the skin directly over the pulse generator, with the manufacturer’s logo or active face oriented toward the device. A slow lateral sweep across the pocket often improves signal pickup on older implants where the antenna sits at an angle.
Establishing Telemetry and Running a Full Check
Initiate telemetry from the programmer and wait for a full, uninterrupted transmission. A partial transmission leaves you with stale event counters and missing EGM segments, which forces a re-interrogation. Once telemetry is solid, run the complete diagnostic bundle: battery voltage, lead impedance for each conductor, pacing threshold, sensing threshold, and the full stored-event log. Resist the urge to spot-check only the parameter you are worried about, because trends only show up when every parameter is read at the same visit.
Printing, Exporting, and Labeling the Report
Print the full interrogation report or export it as a PDF, then label it immediately with the patient’s name, medical record number, device serial number, and the date and time of the interrogation. A report without identifiers is medicolegally weak and useless for trending across visits.
Those identifiers matter because the procedure now generates dozens of discrete data streams that a clinician must sort into clinically meaningful categories.
Save the raw device file alongside the PDF whenever the software allows it. The raw file contains parameters that the printed summary sometimes rounds or omits.
Reading the Five Parameters That Drive Every Clinical Decision
Every interrogation funnels down to the same five categories. Once you know what normal looks like in each, the report reads itself.
| Parameter | What to Look For | Threshold for Concern |
|---|---|---|
| Battery voltage | Trend across visits, not a single number | ERI (Elective Replacement Indicator) reached |
| Lead impedance | Stable baseline, sudden shifts | Rise or fall of more than 1,000 ohms in a short interval |
| Pacing threshold | Output needed to capture reliably | Output climbing close to programmed output |
| Sensing threshold | R-wave or P-wave amplitude | Drop below the programmed sensitivity floor |
| Stored events / EGMs | Mode switches, high-rate episodes, noise reversion | Any unexplained high-rate ventricular episode |
Battery Status: BOL, ERI, and EOS
Battery voltage moves through three stages that every device labels the same way. Beginning of Life (BOL) is the fresh-implant range. Elective Replacement Indicator (ERI) is the manufacturer’s signal that the device should be exchanged within a defined window, often a few months. End of Service (EOS) means the battery is functionally dead. The clinical action changes sharply at ERI, which is why that single line of the report gets checked first.
Lead Impedance Trends
A sudden rise in impedance often points to a conductor fracture or insulation breach at the connector, and a sudden fall suggests an insulation defect creating a current leak. Stable impedance over years is the goal, and any sharp shift in either direction deserves a closer look at the lead itself.
Thresholds and the Margin Worth Acting On
Pacing threshold testing temporarily lowers the output to find the minimum pulse that still captures the chamber. Sensing threshold testing lowers the sensitivity until intrinsic beats stop being detected. A pacing threshold that creeps above 2.5 V at 0.4 ms, or a sensed R-wave that drops below 2 mV, usually prompts a programming change or an image to rule out lead displacement.
Stored Events and EGM Interpretation
The event log is where the device tells you what it has been doing between visits. Mode switches suggest atrial fibrillation or atrial tachycardia that the device tracked and rerouted around. High-rate ventricular episodes may represent VT, VF, or noise reversion, and only the stored EGM distinguishes between them. Always open the EGM, never trust the episode label alone.
Programmed Settings Versus Measured Behavior
Rate response curves, mode switch thresholds, and hysteresis settings all look correct on paper but may behave differently once the patient is upright and active. Comparing what was programmed to what the histograms show over the last 90 days often catches a feature that is technically on but functionally useless.
Red Flags, Troubleshooting, and When to Escalate
Most interrogation sessions end with no changes and a six-month return. A smaller group produces a finding that demands same-day action, and knowing which is which protects both the patient and the clinic schedule.
| Finding | Likely Cause | Immediate Next Step |
|---|---|---|
| Battery at ERI | Normal depletion | Schedule generator replacement within the elective window |
| Sudden impedance rise (>1,000 ohms) | Conductor fracture | Image the lead, notify electrophysiology |
| R-wave drop below 2 mV | Lead dislodgement or exit block | Chest X-ray, sensitivity adjustment |
| Unexpected high-rate ventricular episode | True VT/VF vs. noise reversion | Review stored EGM before any therapy change |
| Frequent mode switches in sinus tachycardia | Mode switch rate set too low | Reprogram mode switch threshold if clinically appropriate |
Common Telemetry Failures
Failed telemetry usually traces back to wand placement, electromagnetic interference (EMI), or a wand that is not the right one for the device. Move the wand slowly across the pocket, step away from any active electrical equipment, and confirm the wand model before assuming the device is the problem.
Distinguishing Malfunction From Physiology
Mode switches during sinus tachycardia are physiologic, not malfunction, and the fix is a programming tweak rather than a lead revision. Atrial undersensing in a patient with low-amplitude P-waves is also a sensing issue, not a broken lead. Pulling the EGM before escalating keeps the differential honest.
When to Involve an Electrophysiologist
Refer to electrophysiology for any suspected lead failure, any ERI battery, any unexplained high-rate ventricular episode, and any threshold change that does not respond to a routine output adjustment. Adjusting settings independently is appropriate for stable, expected shifts; suspected hardware problems are not.
A suspected hardware failure moves the encounter out of routine adjustment and into documentation territory, where every action needs a paper trail.
Documentation, CPT Coding, and Building a Follow-Up Plan
The interrogation is not finished until the findings are documented in a way that supports both clinical decision-making and the billing tied to the visit.
Billing Codes Tied to Interrogation
- 93288: Interrogation device evaluation (in-person), pacemaker
- 93289: Interrogation device evaluation (in-person), ICD
- 93294: Remote interrogation evaluation, pacemaker
- 93295: Remote interrogation evaluation, ICD
Each code has its own documentation requirements, and a clean note that captures the right parameters is what supports the claim on audit.
A Practical Note Template
A workable structure covers indication, battery, leads, thresholds, events, and plan. Indication justifies the visit. Battery captures voltage and ERI status. Leads summarize impedance trends. Thresholds record the latest capture and sensing values. Events summarize stored arrhythmias with EGM correlation. The plan spells out any programming changes and the next follow-up date.
Closing the Loop
Tie the in-clinic findings to the patient’s remote monitoring cadence. A device that showed no abnormalities today can move to annual in-clinic visits with quarterly remote checks, while a device with a borderline parameter stays on a tighter schedule. Communicate the result to the referring physician in writing so the plan does not stall at the device clinic door.
The Bottom Line
A clean pacemaker interrogation depends on matching the right programmer and wand to the device, pulling every parameter at every visit, and translating the report into a documented plan with a follow-up date. Skipping any one of those steps turns a five-minute check into a missed lead fracture or a stalled billing claim.
FAQ
How is a pacemaker interrogated?
A clinician places the manufacturer-specific telemetry wand over the device pocket, initiates telemetry through the programmer, and waits for the device to transmit battery, lead, threshold, and stored-event data. The full session usually takes five to fifteen minutes once telemetry is established.
What does a pacemaker interrogation show?
Battery voltage, lead impedance for each conductor, pacing and sensing thresholds, the percentage of time paced in each chamber, and any stored arrhythmia events or mode switches since the last check all appear in the readout. Together these data points describe how the device and the leads are performing.
How long does a pacemaker interrogation take?
The actual wand-to-report process takes roughly five to fifteen minutes in an experienced clinic. Total visit time runs longer because of rooming, programming changes when needed, and documentation.
Who can perform a pacemaker interrogation?
Trained device clinic staff, including cardiologists, electrophysiologists, nurse practitioners, and device clinic nurses with manufacturer-specific training, perform interrogations. The Heart Rhythm Society outlines scope-of-practice expectations for each role.
What is the difference between interrogation and programming a pacemaker?
Interrogation reads existing data from the device without changing any settings. Programming writes new parameters back to the device, such as adjusting pacing output or rate response, and requires a deliberate command on the programmer.
Is pacemaker interrogation the same as a device check?
A device check typically bundles the interrogation together with a brief physical assessment, threshold testing, and any programming changes that the findings indicate. The interrogation itself is the data-retrieval step inside the broader device check.
