Abstract

The impact of pelvis type on percutaneous fixation of the superior pubic ramus was investigated in this study. One hundred fifty pelvic CTs (female/male: 75/75) without anatomical changes in the pelvis were studied. Pelvis CT examinations with 1mm section width, pelvis typing, anterior obturator oblique, and inlet section images were created using the MPR and 3D imaging mode of the imaging system. In these images, whether a linear corridor could be obtained for the superior pubic ramus, corridor width, length, and angle values in the transverse and sagittal planes were measured in pelvic CT where linear corridor could be obtained. In 11 samples (7.3 %) (group 1), no linear corridor for the superior pubic ramus could be obtained in any way. All pelvis types in this group were gynecoid, and all belonged to female patients. A linear corridor in the superior pubic ramus could be easily obtained in all pelvic CTs with Android pelvic type. The superior pubic ramus was 8.2±1.8 mm in width and 116.7±12.8 mm in length. The corridor width was measured below 5 mm in 20 (13.3%) pelvic CT images (group 2). Corridor width showed a statistically signif-icant difference depending on the pelvic type and gender. The pelvic type is a determinat factor for the fixation of the percutaneous superior pubic ramus. For this reason, pelvic typing using MPR and 3D imaging mode in preoperative CT examination; is effective in surgical planning, implant, and surgical position selection.

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.