On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting failed self-test caused by power, gas supply, cable, accessory, setup, or device fault conditions.
Step-by-Step Troubleshooting
Ensure Patient Safety First
Confirm the Datascope System 98 / 98XT is not connected to or supporting an active patient.
If the pump is in clinical use or urgently needed, have staff obtain another verified intra-aortic balloon pump before troubleshooting.
Expected outcome: Patient support is maintained using a safe alternate device.
If resolved by using another pump for patient care, stop troubleshooting the in-use situation and document the issue.
Confirm the Reported Self-Test Failure
Power the pump on and observe the self-test sequence from a normal startup condition.
Note whether the self-test stops immediately, fails partway through, repeats, displays an error, alarms, or shuts the unit down.
Expected outcome: The failure is confirmed and the exact behavior is documented.
Why it matters: “Will not complete self-test” can be caused by several different external or internal conditions.
Verify AC Power Source
Confirm the pump is connected to a known-good hospital-grade outlet.
Check that the power cord is fully seated at the wall and at the pump.
Test the outlet with another device or outlet tester if appropriate.
Expected outcome: The pump receives stable AC power during startup.
If the pump completes self-test on a different verified outlet, remove the faulty outlet from use and notify Facilities. Stop.
Inspect the Power Cord and Plug
Check the AC cord for cuts, crushed insulation, bent blades, loose strain relief, burn marks, or signs of overheating.
Swap with an approved compatible power cord if available.
Expected outcome: Damaged or intermittent AC cord issues are ruled out.
If replacing the cord allows the pump to complete self-test, replace the defective cord and perform required safety/function checks. Stop.
Check Battery Condition and Charging Status
Observe battery indicators, low-battery messages, or abnormal startup behavior on battery power.
If the unit has been stored unplugged, connect it to AC power and allow charging per facility practice before repeating self-test.
Expected outcome: A depleted or weak battery is not preventing startup or self-test completion.
If the pump completes self-test after adequate charging, document low battery/storage condition and return only after required checks. Stop.
Inspect Helium Supply
Confirm the helium cylinder is installed correctly, has adequate pressure, and is not empty.
Verify the cylinder valve is open and that the regulator/cylinder connection is secure.
Expected outcome: The pump has an adequate helium source for pneumatic checks during self-test.
If replacing or opening the helium cylinder resolves the self-test failure, document the helium supply issue. Stop.
Check for Obvious Pneumatic Connection Problems
Inspect external helium tubing, fittings, and accessible connections for looseness, kinks, damage, or improper seating.
Do not open the pump or perform internal pneumatic repair during initial troubleshooting.
Expected outcome: External pneumatic restrictions or leaks are ruled out.
If reseating an external connection allows self-test to complete, perform a functional check and document the correction. Stop.
Remove Unneeded External Accessories
Disconnect nonessential external connections such as recorder cables, data cables, auxiliary cables, or external trigger cables.
Leave only required power and normal startup connections.
Restart the pump and repeat self-test.
Expected outcome: A faulty accessory or external connection is not interfering with startup.
If self-test completes after removing an accessory, reconnect one item at a time to identify the suspect accessory. Stop once identified.
Inspect ECG/AP Trigger Cables and Patient Input Connections
Check ECG lead cables, pressure input cables, and external trigger cables for damage, bent pins, contamination, or loose connectors.
Remove questionable cables and repeat self-test if the pump allows self-test without them.
Expected outcome: A damaged signal cable or connector is not causing the pump to fail its startup checks.
If removing or replacing a cable resolves the issue, tag the defective cable and document the replacement. Stop.
Check Control Panel and Display Response
During startup, verify that the display illuminates, buttons respond normally, and no keys appear stuck.
Look for liquid intrusion, cracked overlays, damaged knobs, stuck buttons, or abnormal display behavior.
Expected outcome: The control interface is usable and not preventing self-test completion.
If a stuck key or damaged interface is found, remove the pump from service for repair evaluation. Stop.
Listen and Observe During Self-Test
Note unusual sounds such as repeated clicking, compressor/pneumatic cycling, no pneumatic activity, alarms, fan noise changes, or sudden shutdown.
Check for unusual heat, burning odor, smoke, or visible damage.
Expected outcome: Abnormal mechanical, pneumatic, or electrical symptoms are identified without disassembly.
If heat, odor, smoke, or visible damage is present, unplug the device, remove it from service, and escalate immediately. Stop.
Repeat Self-Test After Basic Corrections
After confirming AC power, battery charge, helium supply, external cables, and accessories, restart the pump and allow the self-test to run again.
Expected outcome: The pump either completes self-test normally or the failure remains reproducible.
If the pump completes self-test, perform facility-required operational and safety checks before returning to service. Stop.
If the Problem Persists
If the Datascope System 98 / 98XT still will not complete self-test after external power, battery, helium supply, cables, accessories, and visible damage checks have been ruled out, the issue is likely internal.
Possible internal causes may include pneumatic system faults, power supply issues, battery/charging circuitry problems, processor/control faults, display/control panel failure, internal sensors, or other startup diagnostic failures.
The device should be:
- Removed from service
- Labeled Out of Service
- Sent for repair or bench evaluation
Knowing when to stop is proper troubleshooting. Do not continue into internal repair during basic clinical troubleshooting unless you are trained, authorized, and following approved service procedures.
Clinical Use Tip
Do not troubleshoot an intra-aortic balloon pump self-test failure on an active patient. Move the patient to another verified pump first, then evaluate the suspect pump only when patient support is protected.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported the Datascope System 98 / 98XT intra-aortic balloon pump would power on but would not complete startup self-test."
Cause
What was observed during troubleshooting.
Example:
"Verified failure during self-test; AC outlet, power cord, battery charge, helium cylinder, and external cables were checked with no external cause found."
Resolution
What action was taken.
Example:
"Removed pump from service, labeled Out of Service, and sent for bench evaluation due to persistent self-test failure."
Helpful Details to Include (If Known)
- Outlet tested or alternate outlet used
- AC power cord condition
- Battery charge status or low-battery indication
- Helium cylinder pressure
- Cylinder valve open or closed
- External cables removed or swapped
- Any displayed error message or alarm
- Point in self-test where failure occurred
- Indicator lights or display behavior
- Unusual sounds during startup
- Unusual heat, odor, smoke, or visible damage
- Whether self-test passed after corrections
- Final device status
Final Thought
A failed self-test on an intra-aortic balloon pump should be treated seriously because the device may not be safe or ready for patient support. Start with external causes, verify power and helium supply, remove questionable accessories, and document the exact failure behavior. If the fault persists, remove the pump from service and escalate appropriately.
That is successful troubleshooting.