z-logo
Premium
Are predictive factors in sperm retrieval and pregnancy rates present in nonobstructive azoospermia patients by microdissection testicular sperm extraction on testicle with a history of orchidopexy operation?
Author(s) -
Ozan Tunc,
Karakeci Ahmet,
Kaplancan Tansel,
Pirincci Necip,
Firdolas Fatih,
Orhan Irfan
Publication year - 2019
Publication title -
andrologia
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.633
H-Index - 59
eISSN - 1439-0272
pISSN - 0303-4569
DOI - 10.1111/and.13430
Subject(s) - sperm retrieval , testicular sperm extraction , azoospermia , microdissection , sperm , medicine , obstructive azoospermia , testicle , pregnancy , urology , pregnancy rate , andrology , gynecology , biology , infertility , biochemistry , genetics , gene
The aim in this study is to evaluate predictive factors on sperm retrieval and pregnancy rates by microdissection testicular sperm extraction in non obstructive azoospermia patients with a history of orchidopexy operation. A total of 148 patients were included, and their medical files were evaluated. Data related to possible predictive factors on sperm retrieval and pregnancy rates such as age at orchidopexy operation, unilateral or bilateral presence of undescended testis before orchidopexy, testis volumes and hormone levels were statistically analysed. It revealed that the mean ages in patients with unilateral and bilateral orchidopexy operations were 35.37 (±4.84) and 33.94 (±5.91) respectively. Mean testis volume in the unilateral orchidopexy group was 7.59 (±3.12) ml on the right testis and 7.37 (±2.86) ml on the left testis. Mean FSH levels were detected as 22.71 (±11.86) mIU/ml in the unilateral group and 28.19 (±12.40) mIU/ml in the bilateral group. In our study, we have shown that the age at which patients undergo orchidopexy and the unilateral or bilateral presence of cryptorchidism has no correlation with sperm retrieval and pregnancy rates.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here