Drager Evita V500

Inspiratory/Expiratory Flow Sensor Contamination or Failure

On this page

Asset Type

Ventilator

Manufacturer

Drager

Model

Evita V500

What This Guide Helps With

This guide addresses situations where the Drager Evita V500 ventilator displays:

The guide focuses on logical, external troubleshooting first, minimizing unnecessary disassembly and prioritizing patient safety.

Step-by-Step Troubleshooting

Verify Power and Connections

Reason: Loose or intermittent connections can mimic sensor failure.

Inspect Patient Circuit

Reason: Contaminated or obstructed circuits can trigger false flow sensor alarms.

Check Sensor Orientation and Installation

Reason: Misalignment can cause inaccurate readings or contamination warnings.

Clean or Replace Disposable Flow Sensors

Reason: Contamination buildup affects sensor accuracy.

Run Sensor Calibration/Auto-Zero Procedure

Reason: Ensures sensor electronics are reading correctly after cleaning or replacement.

Observe for Alarms or Unusual Behavior

Reason: Confirms functional correction before returning device to patient use.

If the Problem Persists

External causes have likely been ruled out. The flow sensor or internal measurement module may be defective.

Note: Knowing when to escalate is proper troubleshooting and ensures patient safety.

Clinical Use Tip

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
“Ventilator displayed expiratory flow sensor failure during pre-use check; tidal volumes appear inaccurate.”

Cause

What was observed during troubleshooting.

Example:
“Inspection revealed moisture accumulation in the expiratory flow sensor and tubing; calibration failed before cleaning.”

Resolution

What action was taken.

Example:
“Flow sensor and circuit replaced per protocol, sensor cleaned/replaced, calibration successfully completed, ventilator returned to service with no alarms.”

Helpful Details to Include

Final Thought

Patient safety is paramount. Start with simple, external checks and escalate only when necessary. Accurate documentation ensures future reference and supports proper device management.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide