Key result
4D flow MRI revealed substantially decreased blood flow velocity at the left atrium-left superior pulmonary vein junction (3.55 cm/s) and stump (3.57 cm/s) compared to healthy volunteers (13.34 cm/s).
Why the study?
Does 4D flow MRI reveal altered hemodynamics underlying thrombus formation in a patient with cardioembolic cerebral infarction after left upper lobectomy?
Case Report (n=9)
No
Does 4D flow MRI reveal altered hemodynamics underlying thrombus formation in a patient with cardioembolic cerebral infarction after left upper lobectomy?
4D flow MRI demonstrated localized blood flow stagnation at the left superior pulmonary vein stump, providing a hemodynamic mechanism for thrombus formation and subsequent stroke after left upper lobectomy.
Answers are grounded in this paper and cite their sources.
Localized flow stagnation may underlie post-lobectomy thrombus risk; hypothesis-generating from one case and requires prospective validation.
We present the case of a 76-year-old woman who underwent left upper lobectomy for lung adenocarcinoma. Three days after the surgery, a thrombus was observed in the pulmonary vein (PV) stump. Four months after the surgery, we performed 4D flow MRI, which revealed decreased blood flow, not only in the left superior PV stump, but also over a widespread region around the left atrium-left superior PV junction. 4D flow MRI can clarify the altered hemodynamics underlying thrombus formation.
No takes yet. Share an insight, caveat, or question.
Matsumoto et al. (2020) conducted a case report in Cardioembolic cerebral infarction after pulmonary left upper lobectomy (n=9). 4D flow MRI vs. Healthy volunteers was evaluated on Blood flow velocity at the left atrium-left superior pulmonary vein (LA-LSPV) junction. 4D flow MRI revealed substantially decreased blood flow velocity at the left atrium-left superior pulmonary vein junction (3.55 cm/s) and stump (3.57 cm/s) compared to healthy volunteers (13.34 cm/s).
Synapse has enriched 10 related papers. Consider them for comparative context: