Getinge ROTAFLOW II

Console Will Not Power On or Complete Startup

On this page

Asset Type

Extracorporeal Membrane Oxygenation (ECMO) System

Manufacturer

Getinge

Model

ROTAFLOW II

What This Guide Helps With

Troubleshoots no-power, incomplete startup, repeated restart, external power, connection, accessory, battery, and environmental causes before service escalation.

Step-by-Step Troubleshooting

1. Protect the Patient and Maintain ECMO Support

Do not troubleshoot an unreliable ROTAFLOW II while a patient depends on it. Maintain circulation and oxygenation using the facility's established ECMO backup plan and a verified alternate system when required.

If the console failed during active support, clinical ECMO personnel must control the patient transition and circuit management.

Expected outcome: Patient support remains uninterrupted and troubleshooting is performed only on equipment that can be safely evaluated.

2. Confirm the Exact Startup Failure

Determine whether the console:

Document the exact point at which startup fails.

Expected outcome: The failure is reproducible and clearly identified. If the unit starts normally and remains stable after the reported condition is corrected, continue to final verification.

3. Verify External AC Power

Inspect the power cord, plug, strain relief, and accessible power inlet for damage or looseness. Confirm the outlet provides power using an approved method or known-good equipment.

Avoid unapproved extension cords, adapters, or compromised receptacles.

Expected outcome: Reliable AC power reaches the console. If restoring a valid power source corrects the problem and repeated startup is normal, troubleshooting can stop after functional verification.

4. Inspect Power Connections and External Components

Confirm all externally accessible power connections are fully seated. Look for:

Do not continue operating equipment with damaged electrical connections.

Expected outcome: Power connections are secure and undamaged. Physical or electrical damage requires removal from service.

5. Compare AC and Battery Operation

With the device removed from clinical use, determine whether the console can start from AC power and whether behavior changes when operating from its battery source.

Do not repeatedly cycle power if abnormal heat, odor, noise, or electrical damage is present.

Expected outcome: The console starts consistently from the available approved power source. A failure isolated to battery operation directs troubleshooting toward the battery or charging system.

6. Verify External Configuration and Connected Accessories

Inspect externally connected ROTAFLOW II components and accessories for improper connection, damage, or a condition that could interfere with initialization.

Disconnect or reconnect accessories only when permitted by the applicable manufacturer procedure and when the equipment is not supporting a patient.

Expected outcome: Required accessories are correctly connected and startup proceeds normally. If an external connection was responsible, correct it and proceed to verification.

7. Check the Environment

Verify the console is dry, unobstructed, and being evaluated in an appropriate environment. Look for:

Expected outcome: No external environmental condition explains the startup problem. Suspected fluid intrusion, overheating, or significant physical damage requires removal from service.

8. Perform a Controlled Restart

After external power and connection issues have been ruled out, perform one controlled restart according to normal operating procedures.

Do not repeatedly power-cycle a unit that continues to fail startup.

Expected outcome: The console completes startup and remains stable without abnormal alarms or resets. If it does, proceed to final verification.

9. Perform Final Functional Verification

Before return to service, verify:

Perform all required return-to-service testing under facility and manufacturer procedures.

Expected outcome: All required functions operate normally and the device is safe for clinical use. Troubleshooting can stop.

10. Escalate an Unresolved Startup Failure

If the console remains dead, resets, freezes, or cannot complete startup after external causes have been eliminated, stop troubleshooting.

Expected outcome: The unreliable unit is removed from clinical availability and routed for qualified service evaluation.

If the Problem Persists

Common external power, connection, accessory, configuration, and environmental causes have been ruled out. The remaining problem may involve the internal power system, charging circuitry, control electronics, software, internal communication, or another service-level condition.

The device should be:

Do not perform deep disassembly, board-level troubleshooting, or unauthorized service procedures. Following repair, complete all manufacturer- and facility-required operational, alarm, electrical safety, and functional testing before clinical release.

Knowing when to stop external troubleshooting is proper troubleshooting.

Clinical Use Tip

For an ECMO console failure, secure uninterrupted extracorporeal support before investigating the equipment; troubleshooting must never compete with maintaining patient circulation and oxygenation.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"ECMO staff reported the ROTAFLOW II console would not complete startup when prepared for use."

Cause

What was observed during troubleshooting.

Example:
"Clinical Engineering found the console connected to a receptacle that was not supplying AC power; the console and power cord showed no external damage."

Resolution

What action was taken.

Example:
"Restored the console to a verified powered receptacle, completed repeated startup and functional checks, and returned the unit to service after normal operation was confirmed."

Helpful Details to Include (If Known)

Final Thought

Protect the patient first, verify external power and connections before assuming internal failure, perform a complete functional check after correction, and escalate persistent startup faults with clear CCR documentation.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide