Key result
CT imaging detects post-sternotomy complications and guides safe planning for redo cardiovascular surgeries.
Why the study?
Imaging plays a key role in identifying various acute, subacute, and late complications after sternotomy, but comprehensive pictorial reviews are needed to guide clinicians.
Imaging, particularly CT, plays a critical role in identifying acute, subacute, and late complications following sternotomy and in planning safe surgical approaches for redo sternotomy.
Sternotomy is a widely used incision technique in cardiac and thoracic surgeries. Multiple sternotomy techniques exist, such as the Robicsek technique for redo sternotomy and transverse (clamshell) thoracosternotomy for bilateral lung transplantation. Various complications after sternotomy can occur, and imaging plays a key role in their identification. Complications may involve the hardware, sternum, and peristernal soft tissues and are divided into acute, subacute, and late. Acute complications primarily involve hemorrhage and dehiscence, while subacute complications include superficial or deep sternal wound infections and late complications are typically osseous or hardware related. Imaging also plays a critical role in assessment of cardiovascular structures and their relations to the sternum in those undergoing redo sternotomy, which has become increasingly performed. CT allows radiologists to identify the relationship of vascular anatomy to the sternum as well as other factors that may complicate repeat surgery, allowing surgeons to strategize safe surgical approaches.
No takes yet. Share an insight, caveat, or question.
Kirshenboim et al. (2025) conducted a review in Poststernotomy complications. Poststernotomy imaging was evaluated. Imaging, particularly CT, plays a critical role in identifying acute, subacute, and late complications after sternotomy and assessing cardiovascular structures for safe redo surgeries.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: