[an error occurred while processing this directive]

Muscle geometry affects accuracy of forearm volume determination by magnetic resonance imaging (MRI)

Eng CM, Abrams GD, Smallwood LR, Lieber RL, Ward SR.
J Biomech, 2007 40(14):3261-6. Epub 2007 May 22.

Abstract:

Upper extremity musculoskeletal modeling is becoming increasingly sophisticated, creating a growing need for subject-specific muscle size parameters. One method for determining subject-specific muscle volume is magnetic resonance imaging (MRI). The purpose of this study was to determine the validity of MRI-derived muscle volumes in the human forearm across a variety of muscle sizes and shapes. Seventeen cadaveric forearms were scanned using a fast-spoiled gradient echo pulse sequence with high isotropic spatial resolution (1mm(3) voxels) on a 3T MR system. Pronator teres (PT), extensor carpi radialis brevis (ECRB), extensor pollicis longus (EPL), flexor carpi ulnaris (FCU), and brachioradialis (BR) muscles were manually segmented allowing volume to be calculated. Forearms were then dissected, muscles isolated, and muscle masses obtained, which allowed computation of muscle volume. Intraclass correlation coefficients (ICC(2,1)) and absolute volume differences were used to compare measurement methods. There was excellent agreement between the anatomical and MRI-derived muscle volumes (ICC=0.97, relative error=12.8%) when all 43 muscles were considered together. When individual muscles were considered, there was excellent agreement between measurement methods for PT (ICC=0.97, relative error=8.4%), ECRB (ICC=0.93, relative error=7.7%), and FCU (ICC=0.91, relative error=9.8%), and fair agreement for EPL (ICC=0.68, relative error=21.6%) and BR (ICC=0.93, relative error=17.2%). Thus, while MRI-based measurements of muscle volume produce relatively small errors in some muscles, muscles with high surface area-to-volume ratios may predispose them to segmentation error, and, therefore, the accuracy of these measurements may be unacceptable.

Full text (pdf)
[an error occurred while processing this directive]