On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Addresses low-volume or apnea alarms caused by disconnection, leakage, circuit problems, sensor issues, settings, patient interaction, or measurement errors.
Step-by-Step Troubleshooting
1. Protect the Patient and Confirm Adequate Ventilation
Apnea and low-volume alarms may indicate inadequate ventilation. Clinical staff should immediately assess the patient.
If ventilation is inadequate or the ventilator's reliability is uncertain, move the patient to another verified ventilator or approved backup ventilation before technical troubleshooting.
Expected outcome: Adequate patient ventilation is maintained independently. Technical troubleshooting can proceed safely.
2. Confirm the Exact Alarm
Determine whether the complaint is:
- Apnea alarm
- Low minute volume
- Low tidal volume
- Intermittent low-volume readings
- Multiple related alarms
Record whether the alarm occurred during spontaneous breathing, controlled ventilation, handling, suctioning, or circuit movement.
Expected outcome: The specific alarm condition and circumstances are known.
3. Inspect for Circuit Disconnection
Trace the breathing circuit from the ventilator toward the patient connection.
Check all joints, adapters, filters, humidification components, and sensor interfaces for loose or partially disconnected fittings.
Expected outcome: The circuit is securely connected. If reconnecting a loose component restores normal volumes and stops the alarm, troubleshooting can stop after verification.
4. Inspect for External Leaks
Check circuit tubing and accessories for:
- Cracks
- Split tubing
- Loose caps or ports
- Poorly seated connectors
- Damaged adapters
- Open sampling or accessory ports
Use approved leak testing where appropriate.
Expected outcome: No significant unintended external leak is present. If correcting the leak restores expected volume readings, troubleshooting can stop.
5. Inspect the Flow Sensor
Verify the flow sensor is properly seated, dry, clean, and undamaged.
A contaminated, wet, or incorrectly installed sensor may affect tidal-volume and minute-volume measurement.
Expected outcome: The sensor is correctly installed and measurement is stable. If sensor correction resolves the alarm, troubleshooting can stop after calibration and verification.
6. Check Circuit Positioning and Water Accumulation
Inspect for tubing that is compressed, kinked, pulled loose, or holding significant condensate.
Correct routing or replace affected components as appropriate.
Expected outcome: The breathing circuit remains open and stable throughout normal positioning. If this resolves the alarm, troubleshooting can stop.
7. Review Alarm and Ventilation Configuration
Confirm alarm settings and ventilation configuration match the intended clinical setup.
Do not independently alter prescribed therapeutic parameters. Have questionable patient-specific settings reviewed by the clinical team.
Expected outcome: The alarm is not caused by an unintended setting or configuration mismatch.
8. Test With a Known-Good Circuit or Test Lung
When appropriate, connect a known-good approved circuit and suitable test lung or ventilator analyzer.
Observe delivered and measured tidal volume, minute volume, respiratory activity, and alarms.
Expected outcome: The ventilator produces stable measurements and appropriate alarms under controlled conditions. If so, the original issue was likely external, circuit-related, or clinical.
9. Perform Final Functional Verification
Complete the applicable operational checks after correction.
Verify delivered volumes, displayed measurements, flow sensing, circuit integrity, and alarm operation using approved test equipment.
Expected outcome: Volume measurements and apnea detection behave normally and required return-to-service checks pass.
If the Problem Persists
If low-volume or apnea alarms persist during controlled testing after circuit integrity, connections, sensor condition, configuration, and accessories have been verified, common external causes have been ruled out.
The remaining cause may involve an internal flow measurement system, pneumatic delivery system, pressure or flow sensing pathway, software control, or service-level configuration issue.
The ventilator should be:
- Removed from service
- Labeled Out of Service
- Sent for repair or bench evaluation
- Evaluated using appropriate Drager documentation and approved ventilator test equipment
- Repaired or configured only by qualified personnel
Do not return the ventilator to service if delivered or measured ventilation remains unreliable.
Knowing when to stop external troubleshooting and escalate is proper troubleshooting.
Clinical Use Tip
Treat low-volume and apnea alarms as possible loss-of-ventilation events until the patient, circuit, and ventilator have been assessed.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Respiratory Therapy reported repeated low tidal volume alarms on the Babylog VN600."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found a partially disconnected circuit adapter creating an external leak."
Resolution
What action was taken.
Example:
"The adapter was securely reconnected, circuit integrity was verified, and delivered volume and alarm performance passed bench testing before return to service."
Helpful Details to Include (If Known)
- Exact alarm
- Patient or bench occurrence
- Circuit connections checked
- Leak locations
- Flow sensor condition
- Condensation present
- Settings observed
- Known-good circuit substitution
- Delivered versus displayed volume
- Alarm-test results
- Final device status
- Exact alarm
- Patient or bench occurrence
- Circuit connections checked
- Leak locations
- Flow sensor condition
- Condensation present
- Settings observed
- Known-good circuit substitution
- Delivered versus displayed volume
- Alarm-test results
- Final device status
Final Thought
Respond to low-volume alarms as potential ventilation failures, inspect connections and leaks before assuming an internal problem, verify measurements un### Helpful Details to Include (If Known)