z-logo
Premium
FUNCTIONALITY OF VETERINARY IDENTIFICATION MICROCHIPS FOLLOWING LOW‐ (0.5 TESLA) AND HIGH‐FIELD (3 TESLA) MAGNETIC RESONANCE IMAGING
Author(s) -
Piesnack Susann,
Frame Mairi E,
Oechtering Gerhard,
Ludewig Eberhard
Publication year - 2013
Publication title -
veterinary radiology and ultrasound
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.541
H-Index - 60
eISSN - 1740-8261
pISSN - 1058-8183
DOI - 10.1111/vru.12057
Subject(s) - scanner , medicine , imaging phantom , magnetic resonance imaging , biomedical engineering , nuclear medicine , nuclear magnetic resonance , radiology , computer science , physics , artificial intelligence
The ability to read patient identification microchips relies on the use of radiofrequency pulses. Since radiofrequency pulses also form an integral part of the magnetic resonance imaging ( MRI ) process, the possibility of loss of microchip function during MRI scanning is of concern. Previous clinical trials have shown microchip function to be unaffected by MR imaging using a field strength of 1 Tesla and 1.5. As veterinary MRI scanners range widely in field strength, this study was devised to determine whether exposure to lower or higher field strengths than 1 T esla would affect the function of different types of microchip. In a phantom study, a total of 300 I nternational S tandards O rganisation (ISO)‐approved microchips (100 each of three different types: ISO FDX ‐ B 1.4 × 9 mm, ISO FDX ‐ B 2.12 × 12 mm, ISO HDX 3.8 × 23 mm) were tested in a low field (0.5) and a high field scanner (3.0 Tesla). A total of 50 microchips of each type were tested in each scanner. The phantom was composed of a fluid‐filled freezer pack onto which a plastic pillow and a cardboard strip with affixed microchips were positioned. Following an MRI scan protocol simulating a head study, all of the microchips were accurately readable. Neither 0.5 nor 3 T esla imaging affected microchip function in this study.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here