Skip to Main content Skip to Navigation
Journal articles

A hardware and software system for MRI applications requiring external device data

Abstract : installation which might be impossible in some cases (e.g. pregnant women in lateral position, utilization of a tight flexible coil), and allows monitoring of only respiratory and heart activities. Moreover, being designed for clinical use, they offer no control over data acquisition and post-processing, which can be critical for some applications. For example, standard ECG processing can lead to incorrect QRS detection in case of steep gradient waveforms; no control over respiratory belt signal gain and offset (to avoid signal saturation) is available. Thus, often, accessory devices are thirdparty systems, which offer more flexibility, however have no communication interface with the MR system, or limited ones. Dedicated computer and electronics systems, as well as communication interfaces, are needed for use in either realtime/online applications or retrospective/offline applications. In the following we review several exemplary applications with the aim to derive typical requirements for such systems. Example applications that require real-time processing and communication include ECG denoising (7-10) and detection of the QRS complex (11-13), in order to trigger the MR sequence to the heart rate prospectively. The trigger is provided to the MR system by a TTL signal. The delays introduced by the real-time processing system, as defined by the latency (mean delay) and jitter (standard deviation of the delay), should be significantly lower that the temporal resolution of cardiac MR imaging, which is typically above 20 ms. Real-time display of the denoised ECG is also desired during anesthesia, cardiac stress MRI, or interventional MRI. Prospective motion correction (14) using external devices also relies on a real-time setup to modulate the MRI pulses (RF and magnetic field gradient pulses) in order to compensate for the effect of patient motion during spatial encoding. Low latency is also desired, ideally to be equal to the repetition time (TR) of the sequence or lower, i.e. 3 to 5 ms, though in practice it is limited by the time needed to process video images, e.g. 60 to 150 ms in (15). Software communication interfaces need to be defined with the vendor-dependent pulse sequence program in order to provide certain motion parameters (e.g. translations, rotations).
Document type :
Journal articles
Complete list of metadata
Contributor : Karyna Isaieva Connect in order to contact the contributor
Submitted on : Thursday, May 19, 2022 - 5:31:22 PM
Last modification on : Monday, May 23, 2022 - 1:51:40 PM


Files produced by the author(s)




Karyna Isaieva, Marc Fauvel, Nicolas Weber, Pierre‐andré Vuissoz, Jacques Felblinger, et al.. A hardware and software system for MRI applications requiring external device data. Magnetic Resonance in Medicine, Wiley, 2022, ⟨10.1002/mrm.29280⟩. ⟨hal-03673026⟩



Record views


Files downloads