Puritan Bennett 560

Pre-use Self-test Failures

On this page

Asset Type

Ventilator

Manufacturer

Puritan Bennett

Model

560

What This Guide Helps With

This guide assists Clinical Engineering in troubleshooting Puritan Bennett 560 ventilators that fail their pre-use self-test. Pre-use self-test failures prevent the ventilator from entering clinical service, may trigger alarms, or indicate potential safety risks. Most causes are external or easily verifiable, such as setup errors, disconnections, or environmental factors. Internal component failures are less common but possible.

Step-by-Step Troubleshooting

Verify Power Source

Check Battery Status

Inspect Circuit and Connections

Confirm Environmental Conditions

Reset the Ventilator

Swap Known Good Accessories

Check for Active Alarms or Error Logs

If the Problem Persists

If external factors and accessories are verified functional and self-test continues to fail:

Do not attempt internal repairs beyond authorized Clinical Engineering procedures. Knowing when to escalate is part of proper troubleshooting.

Clinical Use Tip

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
“Ventilator fails pre-use self-test; displays error codes and will not enter clinical service.”

Cause

What was observed during troubleshooting.

Example:
“External verification showed patient circuit disconnected and low battery. All accessories reseated, power verified, environmental conditions normal.”

Resolution

What action was taken.

Example:
“Ventilator reset and self-test rerun after reconnections. If failure persists, removed from service and labeled Out of Service for repair.”

Helpful Details to Include

Final Thought

Effective troubleshooting prioritizes patient safety, logical stepwise evaluation, and knowing when to escalate. Proper documentation ensures clarity, supports future maintenance, and reduces risk. Always verify external factors before assuming internal failure.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide