On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
This guide assists Clinical Engineering in troubleshooting situations where a ResMed Astral ventilator fails to recognize or trigger alarm conditions. Symptoms may include missing or delayed alarms, no audible or visual alert for apnea, disconnection, high/low pressures, or other patient-related alarm conditions. The focus is on external, easily verifiable checks before assuming internal device failure.
Step-by-Step Troubleshooting
Verify Power and Battery Status
- Ensure the ventilator is properly plugged in or the battery is charged.
- Reason: Some alarm circuits may not function correctly if the device detects low power.
Check Ventilator Setup and Mode
- Confirm that the ventilator is in the correct mode for the patient (e.g., CPAP, ST, or PSV) and that settings are applied.
- Reason: Certain modes may suppress or delay specific alarms if not configured correctly.
Inspect Alarm Volume and Settings
- Check the alarm volume and audible alarm settings on the device. Ensure that “Alarm Silence” is not active.
- Reason: Alarms may not be perceived if the volume is low or muted.
Examine Patient Circuit and Connections
- Verify that all tubing, sensors, and patient connections are secure, free from leaks, kinks, or obstructions.
- Reason: Alarms may not trigger if the device does not detect a patient-related event due to poor circuit integrity.
Test Alarm Function Using Built-In Test
- Use the ventilator’s self-test or alarm test function if available. Follow on-screen prompts to simulate alarm conditions.
- Reason: Confirms whether the alarms can trigger independently of patient factors.
Check for External Interference or Environmental Factors
- Ensure there are no high levels of ambient noise or electrical interference that could impact alarm detection.
- Reason: Environmental factors may cause false suppression or prevent alarm audibility.
If the Problem Persists
External checks have ruled out common causes (power, settings, patient connections).
The device may have an internal fault affecting alarm circuits or software.
Actions:
- Remove the ventilator from service.
- Label it Out of Service.
- Send the device to a certified ResMed service or bench evaluation.
Knowing when to escalate is a key part of proper troubleshooting.
Clinical Use Tip
- Do not rely on a ventilator with uncertain alarms for an active patient.
- Move the patient to another functioning ventilator immediately if alarms are not responding correctly.
- Only test alarms when patient safety is ensured.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
“Clinician reports that the ventilator alarms do not trigger during disconnection or high-pressure events.”
Cause
What was observed during troubleshooting.
Example:
“Observed that alarm volume was muted and patient circuit had a loose connection. Device passed self-test once connections were secured and volume adjusted.”
Resolution
What action was taken.
Example:
“Reconnected all tubing securely, increased alarm volume, verified alarm function using built-in test. Device returned to service.”
Helpful Details to Include
- Outlet tested and confirmed functional.
- Battery charged or AC power verified.
- Tubing connections checked for leaks or kinks.
- Alarm volume and settings verified.
- Self-test results logged.
- Any unusual behavior (e.g., delayed alarm triggering) documented.
- Final device status: returned to service or removed for repair.
Final Thought
Proper alarm functionality is critical for patient safety. Following a logical, stepwise troubleshooting process ensures that easily correctable issues are addressed first, and internal failures are escalated appropriately. Documenting all findings and actions enhances safety, continuity of care, and regulatory compliance.
That is successful troubleshooting.