Puritan Bennett 560

Oxygen Sensor Errors

On this page

Asset Type

Ventilator

Manufacturer

Puritan Bennett

Model

560

What This Guide Helps With

This guide assists Clinical Engineering in troubleshooting oxygen sensor errors on Puritan Bennett 560 ventilators. Oxygen sensor errors can prevent the ventilator from delivering the prescribed FiO₂ accurately, trigger alarms, or restrict clinical use. Most causes are external or easily verifiable, such as loose connections, contamination, or depleted sensors, before assuming internal sensor failure.

Step-by-Step Troubleshooting

Verify power and device readiness

Inspect the oxygen sensor physically

Check connections and wiring

Review sensor calibration status

Swap with a known good sensor (if available)

Verify FiO₂ delivery and readings

If the Problem Persists

If external checks do not resolve the error, the sensor or sensor electronics may have failed internally.

Knowing when to stop and escalate is proper troubleshooting.

Clinical Use Tip

Do not troubleshoot on an active patient. Move the patient to another ventilator if oxygen delivery is compromised. Only perform bench testing when the circuit is not connected to a patient.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
“Ventilator shows oxygen sensor error during pre-use check.”

Cause

What was observed during troubleshooting.

Example:
Sensor cable was loose, or sensor tip contaminated (observed during inspection).

Resolution

What action was taken.

Example:
Reconnected the sensor securely and cleaned the sensor tip. Tested ventilator; error resolved. If unresolved, note sensor replacement or device sent to service.

Helpful Details to Include

Final Thought

Proper troubleshooting of oxygen sensor errors ensures patient safety and reliable oxygen delivery. Begin with external checks and simple solutions, and escalate to service when necessary. Document all steps clearly using the CCR method to provide a clear record of actions taken.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide