A randomized crossover trial compares intubation outcomes in medical trainees using two video laryngoscopes, suggesting no significant differences.
Background: It is important especially for medical novices to select an appropriate laryngoscope by which tracheal intubation is performed efficiently and easily. Video laryngoscopes are divided into two types based on the presence or absence of a channel for inserting a tracheal tube into the blade. The Airway Scope (AWS) with a channel and the McGrath MAC (MG) without a channel were compared. Methods: This study was designed as an open randomized crossover manikin trial. Participants were 40 medical trainees. The intubation success rate, the intubation time, number of tooth injuries, and percent of glottic opening (POGO) of the initial intubation maneuver were measured. Results: Regarding the primary outcome, the success rate (actual figure [proportion] {95% confidence interval}) was comparable between the AWS and the MG (34 [85%] {73.8-96.2} and 32 [80%] {76.4-92.6}). The intubation time (median [interquartile range, IQR]) was also comparable between the AWS and the MG (33.3 [22.2-50.6] s and 33.7 [20.3-85.4] s). The same was true for the following: the frequency of dental trauma (median [IQR]), was comparable between the AWS and the MG (0 [0-0.15] and 0 [0-0.25]); POGO (median [IQR]), was comparable between the AWS and the MG (80 [60-92.5] % and 80 [60-90] %). All measures were not significantly different. The frequency dental trauma was clearly lower in these video laryngoscopes. Conclusions: The success rate of intubation, intubation time, POGO, and frequency of dental trauma were comparable between the AWS and the MG by medical trainees. No significant differences were found. The AWS and the MG have roughly equivalent intubation performance for medical trainees.
No takes yet. Share an insight, caveat, or question.
Yuasa et al. (2023) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: