Thayer has attempted but been unable to get any additional information about this incident from (b)(6).On (b)(6) 2018, (b)(6), informed thayer that (b)(6) had determined thayer's minispacer was not responsible for patient adverse event.She also did not respond to further inquiries by thayer on patient status.
|
(b)(6) employee, (b)(6), reports to thayer that one of their nurses set up a non-invasive ventilator circuit for a patient who was to be released from the hospital and return home for a follow-up oxygen breathing treatment via trachea.Equipment assembled by the nurse included an air compressor, an oxygen concentrator with connected tubing and a thayer minispacer device for in-line mdi treatment.The nurse connected the out-going oxygen tubing to the in-going actuator port of the minispacer with intent to introduce concentrated oxygen into the patients airway.This is not the intended use of the minispacer.(b)(6) also stated that once the patient was home again and connected to the circuit, the nurse was certain the patient was receiving oxygen as intended up to and including a flow rate of 4 l/min.Once the nurse increased flow to 6 l/min, there was some (unstated) indication that the flow was too high and the patient was likely not receiving a full 6 l/min of concentrated oxygen.(b)(6) informed that the paramedics were called when there appeared to be a problem with the patient's trach.When the paramedics arrived, one of the emt's observed the "oxygen portal" into the vent line and stated that the adapter was not to be used at a flow rate as high as 6 l/min as it cannot handle it.It appears that both the nurse and the emt thought the mlnispacer was an in-line oxygen adapter.Regardless of their packaging differences, apparently the actual devices look visually similar.(b)(6) explained that the patient was taken lo the hospital because of the need for a repair to his trach, not due to in appropriate oxygenation.Thayer has been advised that the patient is currently undergoing surgery to repair the trach and there is no further update at present (12:30 pm, (b)(6) 2018).
|