Abstract
Background
Total laryngectomy (TL) is an appropriate oncologic operation for many patients with laryngeal cancer delivering excellent oncologic outcomes, however it remains beset with significant functional consequences. Following TL, the upper and lower airways are permanently disconnected, which causes unfiltered, cold air with reduced humidity to enter the tracheobronchial tree, resulting in mucus overproduction and an increase in the viscosity of the mucus. In response to this, Heat and moisture exchangers were developed to compensate for the lost functions of the upper respiratory tract and their effect on the patients' respiratory performance in addition to their quality of life.
Methods
The case records of 48 patients undergoing total laryngectomy were reviewed and data concerning demographics, surgical details, post-operative care requirements and adverse events was retrieved. Post hoc analysis of the case patients was undertaken to identify any benefit of using a heat and moisture exchanger (HME) system with particular reference to post-operative respiratory outcomes.
Results
There was no significant difference between case and control subjects based on demographics, extent of surgery or need for flap repair. 16 patients had used a HME and 32 patients had used external humidification (EH). Of those experiencing mucous plugging, only 3/24 (12.5 %) had used a HME system, in contrast to 21/24 (87.5 %) who used EH (Chi square = 9.375, p = 0.002). The odds ratio of having an adverse event if not using HME was 8.27 (CI = 1.94 – 35.71). Use of HME also significantly reduced the number of days requiring physiotherapy (1.75 days vs. 3.20 days, p = 0.034).
Conclusion
Use of an HME system can reduce in-hospital complications, in particular episodes of mucus plugging, and post-operative care requirements. Furthermore, there is a cost benefit to using HME systems that warrants more widespread introduction of these devices in head and neck surgery centers.
from #ORL via xlomafota13 on Inoreader http://ift.tt/29Cpxxg
via IFTTT
Δεν υπάρχουν σχόλια:
Δημοσίευση σχολίου