ResMed Lumis Ventilator

Pressure or Tidal Volume Delivery Inconsistencies

On this page

Asset Type

Ventilator

Manufacturer

ResMed

Model

Lumis

What This Guide Helps With

This guide assists Clinical Engineering in troubleshooting situations where a ResMed Lumis ventilator delivers inconsistent pressure or tidal volumes. Symptoms may include patient alarms for high or low pressure, tidal volume deviation, or noticeable fluctuations in delivered breaths. The guide emphasizes simple, external checks before assuming internal device failure.

Step-by-Step Troubleshooting

Verify Power and Battery Status

Inspect Circuit and Connections

Check for Mask Fit and Leak

Evaluate Filters and Humidifier

Verify Ventilator Settings

Observe Patient Interface and Compliance

Perform a Quick Functional Test

If the Problem Persists

If external checks fail to resolve inconsistencies, the ventilator should be:

Clinical Engineering should not attempt internal board-level repairs. Knowing when to escalate is critical for patient safety.

Clinical Use Tip

Do not troubleshoot the device on an active patient if possible.

Switch the patient to a backup ventilator first.

Ensure all interventions maintain uninterrupted patient support.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
“Patient alarms indicate inconsistent tidal volume and pressure delivery.”

Cause

What was observed during troubleshooting.

Example:
“External circuit leak detected at mask interface; filter partially clogged; settings verified as correct.”

Resolution

What action was taken.

Example:
“Adjusted mask fit, replaced filter, verified proper delivery with test lung. Patient returned to therapy.”

Helpful Details to Include

Final Thought

Patient safety is paramount. Use a logical, stepwise approach starting with external checks. Escalate to repair only after ruling out simple causes. Document all observations and actions clearly to support future troubleshooting and continuous quality improvement.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide