On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide addresses situations where the Fabius anesthesia machine emits alarms incorrectly, fails to alarm, or triggers false alarms. The focus is on simple, external, and easily verifiable causes first, such as sensor connections, power, setup, and environmental factors, before assuming internal system failures.
Step-by-Step Troubleshooting
Verify Machine Power and Backup
- Ensure the machine is plugged into a verified working outlet and powered on.
- Check battery status if operating on internal battery.
Why it matters: Low or unstable power can prevent alarm circuits from functioning correctly.
Inspect Alarm and Sensor Connections
- Verify that all breathing circuits, O₂ sensors, pressure lines, and flow sensors are properly connected.
- Check that connectors are clean, dry, and free of damage.
Why it matters: A loose or faulty sensor can trigger false alarms or prevent real alarms.
Check Gas Supply and Flow
- Confirm that O₂, N₂O, and air supply lines are connected and pressure is within normal operating range.
- Verify that flowmeters are not blocked or leaking.
Why it matters: Incorrect gas pressures or flows can trigger high/low alarms erroneously.
Examine Breathing Circuit Setup
- Ensure correct circuit type (adult, pediatric) is selected in the machine settings.
- Check for leaks or obstructions in the circuit and endotracheal tube connections.
Why it matters: Circuit misconfiguration can generate pressure or volume alarms.
Confirm Alarm Configuration and Limits
- Review the alarm limits set in the machine for O₂, CO₂, airway pressure, tidal volume, etc.
- Ensure that alarm mute buttons are not inadvertently engaged.
Why it matters: Overly tight or loose alarm limits can cause repeated false alarms or missed alarms.
Perform a Self-Test / System Check
- Run the machine’s built-in self-test (Drager Fabius includes an automated check).
- Observe any errors or warnings reported.
Why it matters: The self-test can detect internal sensor issues or software faults affecting alarms.
Environmental Factors
- Ensure the machine is not exposed to extreme temperatures, moisture, or electrical interference.
- Remove any nearby equipment that could interfere with sensors.
Why it matters: Environmental conditions can trigger spurious alarms.
If the Problem Persists
External checks and proper setup have been verified. The issue may be due to internal electronics, sensor modules, or software corruption.
- Remove the machine from service.
- Label as Out of Service (OOS).
- Send to Drager-certified repair or Clinical Engineering bench evaluation.
Reminder: Knowing when to escalate is proper troubleshooting and ensures patient safety.
Clinical Use Tip
Never troubleshoot alarms while the machine is in use with a patient. Transfer the patient to another machine before testing. Verify patient safety first—false alarms can mask true critical events.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
“User reports frequent false alarms and occasional alarm failures on the Fabius machine.”
Cause
What was observed during troubleshooting.
Example:
“Upon inspection, some sensor connectors were loose, and alarm limits were improperly set.”
Resolution
What action was taken.
Example:
“Reconnected sensors securely, verified all connections, reset alarm limits, ran self-test, and confirmed alarms functioning correctly.”
Helpful Details to Include
- Outlet tested: Yes/No
- Sensor connections checked: Yes/No
- Alarm configuration verified: Yes/No
- Self-test completed: Yes/No
- Any unusual sounds or smells: Describe
- Final device status: Operational / OOS
Final Thought
Patient safety is the top priority. Logical, stepwise troubleshooting reduces unnecessary downtime, identifies true causes, and ensures alarms function correctly. Document every step using CCR methodology for compliance and accountability.
That is successful troubleshooting.