z-logo
Premium
Surgical management of traumatic tricuspid insufficiency
Author(s) -
Zhang Zhiqi,
Yin Kanhua,
Dong Lili,
Sun Yongxin,
Guo Changfa,
Lin Yi,
Wang Chunsheng
Publication year - 2017
Publication title -
journal of cardiac surgery
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.428
H-Index - 58
eISSN - 1540-8191
pISSN - 0886-0440
DOI - 10.1111/jocs.13156
Subject(s) - medicine , surgery , tricuspid insufficiency , perioperative , regurgitation (circulation) , blunt , intensive care unit , tricuspid valve , tricuspid valve insufficiency , blunt trauma
Background This study reviews our experience with traumatic tricuspid insufficiency (TTI) following blunt chest trauma. Methods From January 2010 to June 2016, 10 patients (nine males, mean age 49.0 ± 12.4 years) underwent surgical treatment of TTI following blunt chest trauma. The mean intervals between trauma and diagnosis and between trauma and surgery were 74.1 and 81.8 months, respectively. Preoperatively, all patients exhibited severe tricuspid regurgitation. Five patients underwent tricuspid valve repair, and the remaining patients underwent valve replacement. The mean follow‐up duration (with echocardiography) was 29.7 months. Results There was no early or late death. Seven patients had anterior chordal rupture, two patients had anterior papillary muscle rupture, and one patient had both anterior chordal and anterior leaflet rupture. The median postoperative intensive care unit and hospital stays were 1 and 6 days, respectively. There were no severe postoperative complications. During follow‐up, four patients exhibited trivial to mild tricuspid regurgitation, and the remaining six patients exhibited no regurgitation. Conclusions Surgical treatment of TTI via either valve repair or replacement can be performed with low perioperative morbidity and mortality. Early surgery is recommended for achieving a successful valve repair and preserving right ventricular function.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here