Guillaume Carteaux, MD; Aissam Lyazidi, PhD; Ana Cordoba-Izquierdo, MD; Laurence Vignaux; Philippe Jolliet, MD; Arnaud W. Thille, MD, PhD; Jean-Christophe M. Richard, MD, PhD; Laurent Brochard, MD  CHEST August 2012;142(2):367-376
Abstract
Background: Different kinds of ventilators are available to perform noninvasive ventilation (NIV) in ICUs. Which type allows the best patient-ventilator synchrony is unknown. The objective was to compare patient-ventilator synchrony during NIV between ICU, transport—both with and without the NIV algorithm engaged—and dedicated NIV ventilators.

Methods: First, a bench model simulating spontaneous breathing efforts was used to assess the respective impact of inspiratory and expiratory leaks on cycling and triggering functions in 19 ventilators. Second, a clinical study evaluated the incidence of patient-ventilator asynchronies in 15 patients during three randomized, consecutive, 20-min periods of NIV using an ICU ventilator with and without its NIV algorithm engaged and a dedicated NIV ventilator. Patient-ventilator asynchrony was assessed using flow, airway pressure, and respiratory muscles surface electromyogram recordings.

Results: On the bench, frequent auto-triggering and delayed cycling occurred in the presence of leaks using ICU and transport ventilators. NIV algorithms unevenly minimized these asynchronies, whereas no asynchrony was observed with the dedicated NIV ventilators in all except one. These results were reproduced during the clinical study: The asynchrony index was significantly lower with a dedicated NIV ventilator than with ICU ventilators without or with their NIV algorithm engaged (0.5% [0.4%-1.2%] vs 3.7% [1.4%-10.3%] and 2.0% [1.5%-6.6%], P < .01), especially because of less auto-triggering.

Conclusions: Dedicated NIV ventilators allow better patient-ventilator synchrony than ICU and transport ventilators, even with their NIV algorithm. However, the NIV algorithm improves, at least slightly and with a wide variation among ventilators, triggering and/or cycling off synchronization.

Weblink here