Abstract

Objective: To investigate the relationship of renal parenchymal thickness and the risk of developing post-procedure hematoma. Methods: Ultrasound-guided percutaneous renal biopsy was performed in 122 patients who underwent percutaneous kidney biopsy between January 2013 and ­December 2013 at Tai-he hospital. Post-biopsy renal ultrasound was performed within 12 h after the biopsy to assess the presence of hematoma in biopsied kidney. Logistic regression analysis was used to determine the effect of parenchymal thickness on formation of hematoma adjusted for other nonstructural patient-related factors such as age, sex, systolic and diastolic blood pressure, serum creatinine, and urea. Results: The incidence of complication was 19.4%, all of which were hematoma less than 5 cm. None of the patients went on to have severe complications that required clinical, surgical, or radiological intervention. Out of the collected clinical and anatomical parameters, renal parenchymal thickness of the biopsied kidney was found to be the only factor with strong association with complication risks. Conclusion: This is the first study investigating the impact of structural perimeters on complication risks of percutaneous renal biopsy. Renal parenchymal thickness is a significant predictor of presence of hematoma evident on post-biopsy ultrasound evaluation, which would be used in the early prevent the complications of percutaneous renal biopsy.

Full Text
Paper version not known

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.