How Pacemakers Are Interrogated
A pacemaker is interrogated using a specialized device programmer, not by a standard 12-lead electrocardiogram. The ECG can provide valuable information about pacing function and capture, but it cannot access the device's internal diagnostics, stored data, or programmable parameters 1, 2, 3.
The Interrogation Process
Device Programmer Method (Primary)
Pacemaker interrogation requires a manufacturer-specific programmer that communicates wirelessly with the implanted device 1, 2. This interrogation retrieves:
- Device type, manufacturer, and model
- Battery status and anticipated longevity
- Programmed settings (pacing mode, rate, sensitivity)
- Lead impedances and capture thresholds
- Stored diagnostic data (pacing percentages, arrhythmia episodes)
- Event logs and stored electrograms 3, 4, 5
The programmer must be placed over or near the device to establish telemetric communication 2, 3.
What a 12-Lead ECG Can and Cannot Do
The ECG is complementary but not sufficient for interrogation 6, 7. It can show:
- Whether pacing spikes are present
- If capture is occurring (paced QRS complexes following spikes)
- The pacing mode based on pattern recognition
- Potential lead malfunction (loss of capture or sensing) 8, 9, 10
However, the ECG cannot:
- Access stored diagnostic data
- Determine battery status
- Reveal programmed parameters
- Show lead impedances
- Reprogram the device 1, 2, 5
Clinical Context for When Each Method Is Used
When Programmer Interrogation Is Required:
- Preoperatively (within 3-6 months before major surgery involving electrocautery) to determine device type, pacing dependency, and battery status 2
- After device implantation to verify proper function and optimize settings 11, 4
- When pacemaker malfunction is suspected based on symptoms or ECG findings 6
- Postoperatively to restore original settings if the device was reprogrammed 2
- During routine follow-up (typically every 6 months, more frequently near end-of-life) 11, 4
When ECG Is Useful:
- Immediate post-implant assessment to document pacing pattern 6
- Emergency situations when programmer unavailable, to assess basic capture and sensing 3
- Screening for pacing dependency - if intrinsic rhythm visible without pacing artifacts, patient likely not pacemaker-dependent 3
- Detecting obvious malfunction like complete loss of capture 6, 8
Critical Pitfalls
Beware of ECG artifacts mimicking malfunction 8, 9. What appears as loss of capture on surface ECG may be:
- Pseudo-noncapture from timing artifacts
- Manufacturer-specific algorithms causing expected behavior
- Bipolar pacing spikes too small to visualize
Always confirm suspected malfunction with device interrogation before assuming lead dislodgement or device failure 8, 9.
Remote monitoring systems now allow wireless interrogation between clinic visits but cannot replace periodic direct evaluation 4, 5. These systems transmit device data via internet or radiofrequency but do not allow remote reprogramming 4.
Practical Algorithm for Pacemaker Assessment
If routine follow-up or preoperative evaluation: Use device programmer for complete interrogation 2, 11, 3
If emergency and programmer unavailable:
- Obtain 12-lead ECG to assess basic function
- Look for intrinsic rhythm to gauge pacing dependency
- Contact manufacturer 24-hour support if needed 3
- Arrange formal interrogation as soon as feasible
If ECG shows concerning findings: Always confirm with programmer interrogation before intervening 8, 9
The bottom line: Standard ECG monitoring is surveillance; programmer interrogation is diagnostic evaluation. Both have distinct roles, but only the programmer provides complete device assessment 1, 2, 5.