@article{KreuzerPourmoghaddamLeffersetal.2016, author = {Kreuzer, Stefan W. and Pourmoghaddam, Amir and Leffers, Kevin J. and Johnson, Clint W. and Dettmer, Marius}, title = {Computed Tomography Analysis of Postsurgery Femoral Component Rotation Based on a Force Sensing Device Method versus Hypothetical Rotational Alignment Based on Anatomical Landmark Methods: A Pilot Study}, series = {Advances in orthopedics}, volume = {16}, journal = {Advances in orthopedics}, publisher = {Hindawi}, address = {London}, issn = {2090-3464}, doi = {10.1155/2016/4961846}, pages = {1189 -- 1203}, year = {2016}, abstract = {Rotation of the femoral component is an important aspect of knee arthroplasty, due to its effects on postsurgery knee kinematics and associated functional outcomes. It is still debated which method for establishing rotational alignment is preferable in orthopedic surgery. We compared force sensing based femoral component rotation with traditional anatomic landmark methods to investigate which method is more accurate in terms of alignment to the true transepicondylar axis. Thirty-one patients underwent computer-navigated total knee arthroplasty for osteoarthritis with femoral rotation established via a force sensor. During surgery, three alternative hypothetical femoral rotational alignments were assessed, based on transepicondylar axis, anterior-posterior axis, or the utilization of a posterior condyles referencing jig. Postoperative computed tomography scans were obtained to investigate rotation characteristics. Significant differences in rotation characteristics were found between rotation according to DKB and other methods (P < 0.05). Soft tissue balancing resulted in smaller deviation from anatomical epicondylar axis than any other method. 77\% of operated knees were within a range of +/-3 degrees of rotation. Only between 48\% and 52\% of knees would have been rotated appropriately using the other methods. The current results indicate that force sensors may be valuable for establishing correct femoral rotation.}, language = {en} }