Mapping Troubleshooting
Good troubleshooting is structured reasoning: define the change, localize the problem, verify it independently, and communicate precisely.
Learning objectives
The EP Tech Hub troubleshooting framework
Scenario lab
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.
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.
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?
Progress is stored locally in this browser.