On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide assists Clinical Engineering in troubleshooting situations where a ResMed Lumis ventilator fails to trigger alarms or alarms appear misconfigured. Symptoms may include missing or delayed alarms, no audible or visual alert for high/low pressures, apnea, disconnection, or battery/power warnings. The focus is on external verification, simple configuration checks, and ensuring patient safety before escalating.
Step-by-Step Troubleshooting
Verify Device Power
- Ensure the ventilator is connected to a reliable AC source or fully charged battery.
- Power cycling the device can reset minor configuration glitches.
- Why: Some alarms may not trigger if the device detects a low-power condition.
Check Alarm Volume and Settings
- Access the alarm menu and confirm volume levels are audible.
- Check that alarm thresholds are set appropriately for the patient.
- Why: Misconfigured thresholds or muted alarms are a common cause of missed alerts.
Inspect Connections and Circuit
- Confirm patient circuit, tubing, and humidifier connections are secure.
- Ensure the device recognizes all attached accessories.
- Why: Some alarms depend on detecting a complete circuit or accessory.
Review User Profile and Mode Settings
- Ensure the ventilator mode matches the patient therapy requirements.
- Verify that alarm limits correspond to the selected mode.
- Why: Switching modes can reset or alter alarm parameters.
Perform Self-Test / System Check
- Run the built-in ventilator self-test (if available).
- Observe for any system alerts or error messages during the test.
- Why: Self-tests can detect sensor or internal issues that prevent alarm triggering.
Check for Software or Firmware Alerts
- Confirm that the device firmware is current.
- Look for messages indicating the need for calibration or update.
- Why: Outdated software can cause alarm logic errors.
If the Problem Persists
Common external causes have been ruled out. The device should be:
- Removed from service
- Labeled Out of Service
- Sent to the vendor or Clinical Engineering bench for further evaluation
Note: Avoid patient use until fully verified. Proper escalation is part of safe troubleshooting.
Clinical Use Tip
- Never attempt alarm troubleshooting with a patient actively dependent on the ventilator.
- Move the patient to another verified device first.
- Confirm alarms are functional before returning the ventilator to service.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
Ventilator alarms not triggering during therapy or appear misconfigured.
Cause
What was observed during troubleshooting.
Example:
Alarm settings incorrect, low volume, or device failed self-test.
Resolution
What action was taken.
Example:
Adjusted alarm thresholds, verified volume, confirmed circuit connections, ran self-test. Device passed or escalated to repair if still nonfunctional.
Helpful Details to Include
- Alarm volume and threshold settings checked
- Circuit and humidifier connections secure
- Mode and patient profile reviewed
- Self-test performed
- Firmware version checked
- Final device status (functional or out of service)
Final Thought
Always prioritize patient safety. Begin with logical, external checks before assuming internal failure. Proper documentation and timely escalation protect both the patient and the device.
That is successful troubleshooting.