Ryan Hsi
Last active: 2/26/2019

Renal Vasoconstriction Occurs Early During Shockwave Lithotripsy in Humans.

Lee FC, Hsi RS, Sorensen MD, Paun M, Dunmire B, Liu Z, Bailey M, Harper JD
J Endourol. 2015 29 (12): 1392-5

PMID: 26239232 · PMCID: PMC4677566 · DOI:10.1089/end.2015.0315

INTRODUCTION - In animal models, pretreatment with low-energy shock waves and a pause decreased renal injury from shockwave lithotripsy (SWL). This is associated with an increase in perioperative renal resistive index (RI). A perioperative rise is not seen without the protective protocol, which suggests that renal vasoconstriction during SWL plays a role in protecting the kidney from injury. The purpose of our study was to investigate whether there is an increase in renal RI during SWL in humans.

MATERIALS AND METHODS - Subjects were prospectively recruited from two hospitals. All subjects received an initial 250 shocks at low setting, followed by a 2-minute pause. Treatment power was then increased. Measurements of the renal RI were taken before start of procedure, at 250, after 750, after 1500 shocks, and at the end of the procedure. A linear mixed-effects model was used to compare RIs at the different time points.

RESULTS - Fifteen patients were enrolled. Average treatment time was 46 ± 8 minutes. Average RI at pretreatment, after 250, after 750, after 1500 shocks, and post-treatment was 0.67 ± 0.06, 0.69 ± 0.08, 0.71 ± 0.07, 0.73 ± 0.07, and 0.74 ± 0.06, respectively. In adjusted analyses, RI was significantly increased after 750 shocks compared with pretreatment (p = 0.05).

CONCLUSION - Renal RI increases early during SWL in humans with the protective protocol. Monitoring for a rise in RI during SWL is feasible and may provide real-time feedback as to when the kidney is protected.

MeSH Terms (16)

Acute Kidney Injury Aged Blood Pressure Cohort Studies Female Hospitals Humans Kidney Kidney Calculi Lithotripsy Male Middle Aged Prospective Studies Renal Artery Vascular Resistance Vasoconstriction

Connections (1)

This publication is referenced by other Labnodes entities: