Abnormal Spinopelvic Motion and Spine Deformity are Associated With Native Femoral Retroversion in the Setting of Total Hip Arthroplasty

Background: The effect of spinopelvic pathology on femoral version is unclear. This study investigated variability in native femoral anteversion in patients undergoing total hip arthroplasty (THA) and its relationship to the patient’s underlying spinopelvic pattern. Methods: A retrospective chart review was performed to include in the study all patients undergoing robot-assisted THA over a 3-year period. Native femoral version was measured for each patient using a preoperative computed tomography scan and categorized as excessive, normal, or retroverted. Additionally, a subset analysis was performed for all patients with sit-to-stand dynamic pelvic radiographs available, and cases were classified by spinopelvic pattern. Results: A total of 119 patients were included in the study with a mean age of 68.6 years; 61 (51%) were female. The median femoral anteversion for the entire study group was 6.0° (−32° to 40°, interquartile range 13.5°). Eleven patients (9.2%) had excessive femoral anteversion, 54 of the 119 (45.4%) had normal femoral version, and 54 of the 119 (45.4%) had native retroversion. Forty-two patients (35.3%) had sit-to-stand radiographs available and were subclassified by femoral version type and spinopelvic parameters. Welch’s analysis of variance demonstrated a significant difference in femoral version among spinopelvic patterns (F = 7.826, P =.003), with Games-Howell post hoc analysis showing increased retroversion in deformity-stiff patients compared to deformity-normal mobility patients (P =.003). Conclusions: This study demonstrates that native femoral retroversion is present in a significant number of patients undergoing THA and is more common in patients with stiff spine deformities. Based on this observation, currently available spinopelvic classification systems should be modified to account for native femoral version.

Abstract licence: CC BY-NC-ND

A person counts once a day per paper. We keep no cookie and no address: a reader is a hash that changes every day. Any month under five reads shows no number.