Drager Babylog VN500

Apnea, Low Minute Volume, or Low Tidal Volume Alarm

On this page

Asset Type

Ventilator

Manufacturer

Drager

Model

Babylog VN500

What This Guide Helps With

Troubleshooting apnea or low-volume alarms caused by patient-circuit leaks, disconnections, flow-sensor problems, obstructions, settings, or inadequate delivered ventilation.

Step-by-Step Troubleshooting

1. Ensure Patient Safety First

Do not troubleshoot persistent apnea, low minute volume, or low tidal volume alarms while the Babylog VN500 is supporting a patient without clinical involvement.

Expected outcome: The patient is safely supported without relying on ventilation that may be inadequate.

Continue Clinical Engineering troubleshooting only after the ventilator has been removed from patient use or the clinical team confirms that evaluation can be performed safely.

2. Identify the Exact Alarm

Review and record the full alarm message, priority, displayed values, waveforms, and time of occurrence.

Determine whether the reported condition is:

The Babylog VN500 monitors expiratory minute volume, tidal volume, and apnea time. The apnea alarm delay is configurable, and the device can provide apnea ventilation when configured for the selected mode.

Expected outcome: The reported failure is clearly defined before components or settings are changed.

3. Check for an Obvious Circuit Disconnection

Inspect the complete breathing circuit from the ventilator to the patient connection or test lung.

Check:

Reconnect any loose connection securely.

Expected outcome: The circuit is complete, properly connected, and has no open ports.

If reconnecting the circuit restores normal tidal volume and minute volume without recurrence, verify operation and stop troubleshooting.

4. Inspect the Circuit for Leaks

Examine the breathing circuit and accessories for:

Compare inspiratory and expiratory volume readings when available. A substantial difference may indicate a circuit, interface, or airway leak.

The Babylog VN500 can calculate and display leakage minute volume, and leakage can affect measured tidal volume and volume-guarantee operation.

Expected outcome: No excessive external leakage is present.

If replacing or reseating an external circuit component resolves the alarm, complete the required operational check and stop.

5. Check the Expiratory Valve and Expiratory Limb

Inspect the expiratory valve assembly for:

Inspect the expiratory limb for kinks, compression, water accumulation, or obstruction.

Do not perform internal disassembly beyond normal user-removable components.

Expected outcome: Exhaled gas can travel through the circuit without an abnormal leak or restriction.

6. Inspect the Neonatal Flow Sensor

Verify that the correct compatible flow sensor is installed and oriented correctly.

Check for:

Replace the suspect sensor with a known-good compatible sensor when permitted by facility policy.

Flow-sensor failure can interfere with tidal-volume measurement and Volume Guarantee. The ventilator may continue ventilation using previously established pressure while generating an alarm.

Expected outcome: A clean, correctly installed flow sensor provides stable flow and volume measurements.

If a known-good sensor resolves the alarms, perform the required calibration and operational verification before returning the ventilator to service.

7. Check for Circuit Obstruction or Excessive Resistance

Inspect for:

Replace or correct the affected external component.

Expected outcome: The circuit permits normal inspiratory and expiratory flow.

If removing an obstructed external component restores the expected tidal volume and minute volume, verify operation and stop troubleshooting.

8. Verify Gas Supplies and Ventilator Output

Confirm that:

Insufficient gas delivery, unstable output, or failure to reach pressure can produce inadequate tidal volume and minute volume.

Expected outcome: The ventilator has stable gas supplies and produces repeatable test breaths.

9. Review Alarm Limits and Apnea Settings

Clinical settings must be reviewed with respiratory therapy or another authorized clinician.

Verify that:

Do not independently change patient-specific ventilation or alarm settings solely to eliminate an alarm.

The Babylog VN500 supports configurable apnea time, apnea tidal volume, apnea respiratory rate, and high/low minute-volume monitoring.

Expected outcome: Alarm limits and apnea settings are appropriate for the clinical plan or controlled test setup.

10. Review Ventilation Settings and Waveforms

With respiratory therapy, confirm that the selected mode and settings are capable of producing the intended ventilation.

Review:

Inspect pressure, flow, and volume waveforms for incomplete lung filling, inadequate pressure, missed triggering, excessive leakage, or early breath termination.

With Volume Guarantee, the target tidal volume may not be reached when the pressure limit is too low, inspiratory flow is insufficient, inspiratory time is too short, resistance increases, or compliance decreases. The ventilator generates an alarm when measured tidal volume remains below the required target threshold.

Expected outcome: The selected settings produce stable, repeatable breaths under controlled test conditions.

11. Perform the Device and Breathing-Circuit Check

Remove the ventilator from patient use and perform the manufacturer-prescribed device and breathing-circuit check using the correct circuit and test equipment.

Do not bypass failed checks.

If the test fails:

Drager provides a dedicated device and breathing-circuit check process for the Babylog VN500.

Expected outcome: The ventilator completes all required checks without alarms or failed test stages.

12. Test with Known-Good External Components

When available, substitute one external component at a time:

Repeat the operational test after each substitution so the actual cause can be identified.

Expected outcome: The alarm is either isolated to an external component or remains present with all known-good accessories.

13. Verify Performance Before Return to Service

After correcting the problem:

Expected outcome: The Babylog VN500 operates consistently, passes required checks, and is safe for clinical use.

If the Problem Persists

If apnea, low minute-volume, or low tidal-volume alarms continue after gas supplies, circuit integrity, accessories, flow sensing, expiratory components, alarm settings, and controlled test performance have been verified, the fault is likely internal or requires manufacturer-level evaluation.

The ventilator should be:

Possible internal causes include flow-measurement failure, pressure-control problems, gas-delivery faults, valve-control failure, or electronic malfunction.

Do not repeatedly adjust settings to make the alarm disappear. Knowing when to stop and escalate is proper troubleshooting.

Clinical Use Tip

Never troubleshoot persistent apnea or low-volume alarms on an active neonatal patient without immediate clinical support. Move the patient to verified ventilation first whenever reliable ventilation cannot be confirmed.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Respiratory therapy reported repeated “Minute volume low” and “Tidal volume low” alarms during neonatal ventilation."

Cause

What was observed during troubleshooting.

Example:
"Inspection found condensation inside the neonatal flow sensor and a loose connection at the expiratory limb, causing unstable expiratory-volume measurements."

Resolution

What action was taken.

Example:
"Replaced the flow sensor, secured the circuit connection, completed flow-sensor calibration and the device check, and verified stable ventilation on a test lung with no recurring alarms."

Helpful Details to Include (If Known)

Final Thought

Apnea and low-volume alarms may represent genuine inadequate ventilation or inaccurate measurements caused by external components. Protect the patient first, verify the circuit and sensors logically, and escalate when the ventilator cannot pass controlled testing. Accurate CCR documentation preserves the troubleshooting path and supports safe follow-up.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide