Key result
An MRI FFE sequence caused a Terumo guidewire tip to heat from 26°C to 74°C after 30 seconds of scanning, demonstrating excessive heating driven by resonating RF waves.
Why the study?
Does MRI scanning cause unwanted radiofrequency heating of endovascular guidewires?
Does MRI scanning cause unwanted radiofrequency heating of endovascular guidewires?
MRI scanning can cause excessive and unpredictable heating of endovascular guidewires due to resonating RF waves, posing significant safety risks.
Answers are grounded in this paper and cite their sources.
May signal MRI safety risks with guidewires; challenges consensus on device MR safety but leaves open translation to humans.
We examined the unwanted radiofrequency (RF) heating of an endovascular guidewire frequently used in interventional magnetic resonance imaging (MRI). A Terumo guidewire was partly immersed in an oblong saline bath to simulate an endovascular intervention. The temperature rise of the guidewire tip during an FFE sequence [average specific absorption rate (SAR) = 3.9 W/kg] was measured with a Luxtron fluoroscopic fiber. Starting from 26°C, the guidewire tip reached temperatures up to 74°C after 30 seconds of scanning. Touching the guidewire may cause sudden heating at the point of contact, which in one instance caused a skin burn. The excessive heating of a linear conductor like the guidewire can only be explained by resonating RF waves. The capricious dependencies of this resonance phenomenon on environmental factors have severe consequences for predictability and safety guidelines. J. Magn. Reson. Imaging 2000;12:79–85.
No takes yet. Share an insight, caveat, or question.
Konings et al. (2000) studied Interventional MRI safety. MRI FFE sequence was evaluated on Temperature rise of the guidewire tip. An MRI FFE sequence caused a Terumo guidewire tip to heat from 26°C to 74°C after 30 seconds of scanning, demonstrating excessive heating driven by resonating RF waves.
Synapse has enriched 10 related papers. Consider them for comparative context: