Drager Fabius GS

Alarm: MINUTE VOLUME HIGH !!

On this page

Asset Type

Anesthesia Machine

Manufacturer

Drager

Model

Fabius GS

What This Guide Helps With

The MINUTE VOLUME HIGH !! alarm indicates that the measured minute ventilation exceeds the configured upper alarm limit. This may be caused by incorrect ventilator settings, improper alarm limits, or inaccurate readings due to flow sensor miscalibration or failure. This condition can lead to over-ventilation or incorrect clinical interpretation of patient status.

Step-by-Step Troubleshooting

1. Ensure Patient Safety First

2. Verify the Reported Alarm and Behavior

3. Check Alarm Limit Settings

4. Check Ventilator Settings

5. Inspect Breathing Circuit and Accessories

6. Check Flow Sensor Connection and Condition

7. Perform Flow Sensor Calibration

8. Substitute with a Known Good Flow Sensor (If Available)

If the Problem Persists

If the alarm continues after verifying settings, checking the circuit, and calibrating or replacing the flow sensor, external causes have been ruled out. Remove the device from service, label it Out of Service, and send it for repair or bench evaluation.

Clinical Use Tip

Never troubleshoot on an active patient. Always transition the patient to a backup device before investigating ventilation or measurement issues.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Unit alarming MINUTE VOLUME HIGH !! during ventilation with elevated displayed minute volume."

Cause

What was observed during troubleshooting.

Example:
"Flow sensor miscalibrated causing inaccurate volume measurement."

Resolution

What action was taken.

Example:
"Verified alarm, checked settings and circuit, performed flow sensor calibration and confirmed normal readings."

Helpful Details to Include (If Known)

Final Thought

Alarms like MINUTE VOLUME HIGH !! often reflect measurement inaccuracies rather than true ventilation problems. Always verify settings and sensor performance first, and escalate appropriately if accuracy cannot be restored.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide