Mapping & Ablation · Module 7 of 7

Mapping Troubleshooting

Technologist focusedInteractive lessonPrinciples first

Good troubleshooting is structured reasoning: define the change, localize the problem, verify it independently, and communicate precisely.

Learning objectives

RecognizeIdentify whether a problem appears electrical, localization-related, reference-related or display-related.
Cross-checkUse independent sources instead of trusting one screen.
CommunicateEscalate clearly and follow approved platform procedures.

The EP Tech Hub troubleshooting framework

LOOKWhat exactly changed?
LOCALIZEWhich part of the system?
VERIFYWhat independent source can confirm it?
COMMUNICATEState the finding clearly

Scenario lab

Scenario 1

One intracardiac channel becomes noisy

Compare neighboring channels and surface signals. Consider whether the issue follows a single electrode pair, catheter, cable/connection, environmental noise source or recording configuration. Follow approved equipment checks.

Scenario 2

Multiple catheters shift together on the map

A simultaneous visual shift raises a different question than one catheter moving alone. Cross-check actual catheter position and investigate reference/localization integrity using the platform's approved workflow.

Scenario 3

Automatic annotations suddenly move to a different electrogram component

Check whether electrogram morphology, rhythm, reference, filtering, catheter contact or annotation settings changed. Automation should trigger review—not automatic acceptance.

Communication example

Instead of “the map is wrong,” communicate the observable finding: “All displayed catheters shifted together while intracardiac signals and the independent position check appear unchanged.” Specific observations make troubleshooting faster.

What is the best first troubleshooting question?

Educational scope: This lesson does not replace institutional competency training, manufacturer instructions for use, or physician-directed procedural decision-making.
Lesson progress

Progress is stored locally in this browser.