On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
External pacing does not produce expected output or capture because of pads, cables, connections, settings, patient factors, or device pacing-system problems.
Step-by-Step Troubleshooting
1. Protect the Patient and Maintain Required Pacing Support
External pacing is a therapeutic function. Do not troubleshoot unreliable pacing while a patient depends on the affected Propaq MD.
Transfer pacing support to another verified device or clinically appropriate alternative before technical evaluation.
Expected outcome: Necessary pacing support continues without dependence on the questionable device.
2. Confirm the Reported Pacing Condition
Determine whether staff reported:
- Pacing will not start
- No apparent pacing output
- Pacer markers present without expected response
- Failure to capture
- Intermittent pacing
- Difficulty adjusting pacing controls
- Pads not recognized
Differentiate an equipment-output concern from a clinical failure-to-capture condition.
Expected outcome: The exact reported problem is defined before testing begins.
3. Inspect Therapy Pads
Check compatible multifunction electrodes for:
- Expiration
- Package damage
- Dried adhesive or gel
- Contamination
- Physical damage
- Improper connection
- Evidence of prior use
Do not reuse compromised single-use therapy pads.
Expected outcome: Appropriate therapy electrodes are available and in acceptable condition.
4. Inspect the Therapy Cable
Inspect the pacing/defibrillation cable for:
- Cracks
- Cut insulation
- Damaged connectors
- Bent or contaminated contacts
- Loose locking mechanisms
- Strain damage
- Intermittency during gentle movement
Expected outcome: The external therapy cable is physically intact and securely connected.
5. Reseat All Therapy Connections
Disconnect and firmly reconnect the therapy cable and test-load or electrode connection as appropriate.
Confirm connectors are completely engaged.
Expected outcome: The device recognizes the connected therapy path. If the original complaint was caused by a loose connection and output now verifies normally, complete functional testing and stop troubleshooting.
6. Verify Pacing Controls and Operating Mode
Review the selected pacing mode and visible pacing controls.
Confirm that the unit is actually in the intended pacing function and that an unintended control setting is not preventing expected operation.
Do not make unauthorized configuration changes.
Expected outcome: Pacing is configured appropriately for controlled testing.
7. Test With Approved Defibrillator/Pacer Analyzer
Connect the Propaq MD to approved test equipment capable of evaluating external pacing.
Verify pacing output using the analyzer rather than a patient.
Expected outcome: The analyzer detects repeatable pacing output consistent with the device settings and test setup.
8. Substitute Known-Good Therapy Accessories
If output is absent or intermittent, repeat testing with a known-good compatible therapy cable and appropriate test interface.
Expected outcome: If pacing output becomes reliable with the known-good cable or connection, replace the defective accessory and proceed to final verification.
9. Perform Final Functional Verification
Verify:
- Pacing function activates normally
- Pacing controls respond
- Output is detected by approved analyzer
- ECG display and pacing indicators operate as expected
- Therapy cable remains stable during normal handling
- Applicable alarms and prompts function during controlled testing
Expected outcome: Pacing output is reliable and repeatable. Troubleshooting can stop.
10. Escalate Unresolved Pacing Failure
If pacing output remains absent, intermittent, or abnormal with verified accessories and approved test equipment, remove the Propaq MD from service.
Expected outcome: The unit is withheld from clinical use until the therapeutic pacing function receives qualified service evaluation.
If the Problem Persists
Once pads, cables, connections, test setup, controls, and known-good external substitutions have been ruled out, the remaining cause may involve the therapy output path, sensing or control system, configuration, or another internal service-level condition.
The device should be:
- Removed from service
- Labeled Out of Service
- Sent for repair or bench evaluation
- Evaluated using appropriate manufacturer documentation and approved test equipment
- Repaired or configured only by qualified personnel
After repair, perform complete manufacturer-appropriate pacing, defibrillation, ECG, alarm, battery, and electrical safety return-to-service testing.
Knowing when to stop external troubleshooting of a therapeutic function is proper troubleshooting.
Clinical Use Tip
Move the patient to another verified pacing-capable device before technical troubleshooting of questionable pacer output.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported that external pacing intermittently stopped and the therapy connection appeared unstable."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found an intermittent therapy cable that caused pacing output to drop out during controlled analyzer testing."
Resolution
What action was taken.
Example:
"The defective therapy cable was replaced and the Propaq MD passed repeated pacing-output and functional verification using an approved defibrillator/pacer analyzer."
Helpful Details to Include (If Known)
- Reported pacing symptom
- Therapy pad condition
- Therapy cable condition
- Connector condition
- Pacing mode observed
- Analyzer result
- Known-good cable substitution
- Intermittency during cable movement
- ECG and pacing indicator behavior
- Alarm or prompt behavior
- Final device status
Final Thought
Treat pacing as a critical therapeutic function, protect the patient first, verify pads, cables, connections, and settings before assuming internal failure, test with an approved analyzer, escalate any unresolved output problem, and document the full verification.
That is successful troubleshooting.