IN REPLY

Article information

Anesth Pain Med. 2020;15(1):130-130
Publication date (electronic) : 2020 January 31
doi : https://doi.org/10.17085/apm.2020.15.1.130
Department of Anesthesiology and Pain Medicine, Chosun University Hospital, Gwangju, Korea
Corresponding author: Ki Tae Jung, M.D., Ph.D. Department Anesthesiology and Pain Medicine, Chosun University Hospital, 365 Pilmun-daero, Dong-gu, Gwangju 61453, Korea Tel: 82-62-220-3223 Fax: 82-62-223-2333 E-mail: mdmole@chosun.ac.kr ORCID:
Received 2019 October 18; Accepted 2019 October 18.

IN REPLY: Sir, the author agrees with the opinion raised by Dr. Choi et al. However, they misunderstood several aspects of our case. Below we have addressed the points raised in his correspondence.

First, in this case, the post-tetanic count (PTC) was assessed after confirming the absence of response of train-of-four (TOF) stimulation which indicates that the neuromuscular block (NMB) level of the patient was in a deep block. According to the suggestion of ideal neuromuscular monitoring, PTC should be assessed as soon as train-of-four count (TOFc) becomes 0 [1]. And this sequence should be repeated with time interval with more than 3–4 min until TOFc becomes more than 0 for the accurate neuromuscular monitoring and avoiding measurements during post-tetanic potentiation. We followed this sequence during the recovery of the neuromuscular blockade of the patient.

Second, as mentioned in the original report, it was regrettable that we did not use an adequate dose of sugammadex at first administration. In the case of deep NMB, sugammadex 4 mg/kg is advised for the reversal [2]. Thus, at least 300 mg of sugammadex should be used in this patient (75 kg of body weight) at the first use. However, we noticed that an inadequate dose of sugammadex was used and administered additional sugammadex 200 mg.

Third, we used sugammadex in spite of profound bradycardia because we did not notice the bradycardia was developed by sugammadex. The bradycardia lasted only about 10s without hypotension and returned to normal spontaneously. Most cases of bradycardia associated with sugammadex were clinically insignificant or easily treatable at the time of its first release [3]. However, only a few cases of severe bradycardia with the use of sugammadex was reported recently. Thus, we did not recognize the risk of bradycardia after the use of sugammadex [4]. As Dr. Choi et al. mentioned, it would be reasonable and safer to use anticholinesterase or waiting for the natural recovery from NMB.

Reports about the unknown complications associated with sugammadex are increasing as its widespread use [5]. This case reported profound bradycardia and resistance to the sugammadex after the use of excessive doses of sugammadex. The author emphasizes that we should be aware of the possibility of severe complications after the use of sugammadex and proper dosage of sugammadex should be used based on the quantitative neuromuscular monitoring.

Notes

CONFLICTS OF INTEREST

No potential conflict of interest relevant to this article was reported.

References

Biro P, Paul G, Dahan A, Brull SJ. 2019;Proposal for a revised classification of the depth of neuromuscular block and suggestions for further development in neuromuscular monitoring. Anesth Analg 128:1361–3. 10.1213/ANE.0000000000004065. 31094813.
Naguib M, Brull SJ, Kopman AF, Hunter JM, Fülesdi B, Arkes HR, et al. 2018;Consensus statement on perioperative use of neuromuscular monitoring. Anesth Analg 127:71–80. 10.1213/ANE.0000000000002670. 29200077.
Dahl V, Pendeville PE, Hollmann MW, Heier T, Abels EA, Blobner M. 2009;Safety and efficacy of sugammadex for the reversal of rocuronium-induced neuromuscular blockade in cardiac patients undergoing noncardiac surgery. Eur J Anaesthesiol 26:874–84. 10.1097/EJA.0b013e32832c605b. 19455040.
Hunter JM, Naguib M. 2018;Sugammadex-induced bradycardia and asystole: how great is the risk? Br J Anaesth 121:8–12. 10.1016/j.bja.2018.03.003. 29935599.
Kim YH. 2016;Sugammadex: watch out for new side effects. Korean J Anesthesiol 69:427–8. 10.4097/kjae.2016.69.5.427. 27703621. PMC5047976.

Article information Continued