Getinge Cardiosave Hybrid / Rescue

Startup failure, boot error, or system self-test failure

On this page

Asset Type

Intra-Aortic Balloon Pump

Manufacturer

Getinge

Model

Cardiosave Hybrid / Rescue

What This Guide Helps With

Troubleshooting Cardiosave startup, boot, or self-test failures caused by power, battery, docking, accessories, or system readiness issues.

Step-by-Step Troubleshooting

Ensure Patient Safety First

Confirm the IABP is not supporting an active patient before troubleshooting.

Action:

Expected outcome: Patient support is maintained using a reliable device.

Why it matters: An IABP with startup, boot, or self-test failure may not be available for urgent circulatory support.

Verify the Reported Failure

Confirm exactly what the device is doing during startup.

Action:

Expected outcome: The failure is confirmed and described clearly.

Why it matters: “Won’t start” can mean power failure, battery issue, software lockup, failed self-test, or internal hardware fault.

Check AC Power Source

Rule out a bad outlet or missing facility power.

Action:

Expected outcome: The Cardiosave receives stable AC power.

If the unit starts normally on another outlet, stop troubleshooting and document the failed outlet or power source issue.

Inspect the Power Cord and External Power Connection

Check for simple external power problems.

Action:

Expected outcome: Power is delivered through a safe, secure cord connection.

If a damaged cord is found, remove the cord from service and retest with a known-good cord.

Confirm Battery Condition and Seating

Check whether the startup issue is related to weak, missing, or poorly seated batteries.

Action:

Expected outcome: The device powers up with adequate battery support and AC input.

Why it matters: IABPs may require healthy battery support for transport readiness, startup checks, or power transition testing.

Check Docking or Cart Connection

For Cardiosave Hybrid configurations, verify the pump is properly seated in its cart or docking arrangement.

Action:

Expected outcome: The system recognizes its power and interface connections correctly.

If startup succeeds after reseating, document the docking connection issue and verify repeat startup.

Disconnect Nonessential External Accessories

Rule out an accessory or external connection interfering with startup.

Action:

Expected outcome: The pump boots normally without external accessory interference.

If the unit boots successfully after removing an accessory, reconnect items one at a time to identify the cause.

Inspect External Connectors and Ports

Check for obvious damage that could cause self-test failure.

Action:

Expected outcome: No damaged external connection is causing the startup or self-test fault.

Why it matters: Some self-test failures can be caused by damaged or shorted external cables rather than internal pump failure.

Check for Environmental or Physical Damage

Look for signs that the unit may have been dropped, exposed to fluid, overheated, or stored improperly.

Action:

Expected outcome: No obvious environmental or physical issue is affecting startup.

If fluid intrusion, burning smell, unusual heat, or impact damage is found, stop troubleshooting and send for repair evaluation.

Perform a Controlled Power Cycle

Attempt one clean restart if there are no safety concerns.

Action:

Expected outcome: The system completes startup and passes self-test.

If the issue clears, repeat startup to confirm the failure does not return before releasing the device.

Review Alarm or Error History if Accessible

Use available device information without entering deep service procedures.

Action:

Expected outcome: The work order includes specific failure information for repair or vendor support.

Why it matters: Exact boot or self-test errors help determine whether the issue is power, battery, software, pneumatic, sensor, display, or internal electronics related.

Repeat Startup Verification

Confirm whether the startup failure is repeatable.

Action:

Expected outcome: The final device status is clear: passed startup consistently or failed/recurred.

If the failure repeats or is intermittent, remove the device from service.

If the Problem Persists

If AC power, power cord, battery seating, docking, accessories, external connections, environmental conditions, and controlled restart have been checked, the remaining cause is likely internal.

The device should be removed from service, labeled Out of Service, sent for repair, bench evaluation, or vendor service, and documented with the exact startup behavior, self-test message, and all external checks performed.

Knowing when to stop is proper troubleshooting. An IABP with unreliable startup should not be placed back into clinical circulation.

Clinical Use Tip

Do not troubleshoot startup or self-test failures while the Cardiosave is supporting an active patient. Transfer support to another IABP first if clinically required. Startup reliability is a patient safety issue because the device may be needed urgently for circulatory support.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Staff reported the Getinge Cardiosave Hybrid / Rescue IABP would not complete startup and displayed a self-test failure during power-on."

Cause

What was observed during troubleshooting.

Example:
"Verified failure on known-good AC power; power cord, outlet, battery seating, docking connection, and external accessories were checked with no external cause found."

Resolution

What action was taken.

Example:
"Removed device from service, labeled Out of Service, documented startup failure behavior, and sent unit for bench evaluation/vendor repair."

Helpful Details to Include (If Known)

Final Thought

Startup and self-test failures on an intra-aortic balloon pump should be treated seriously. Start with the basics: patient safety, AC power, cord condition, battery condition, docking, and external accessories. Once external causes are ruled out, escalation is the correct action. Clear CCR documentation helps repair teams understand the failure and protects the clinical record.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide