Skip Navigation
Skip to contents

J Trauma Inj : Journal of Trauma and Injury

OPEN ACCESS
SEARCH
Search

Articles

Page Path
HOME > J Trauma Inj > Volume 29(4); 2016 > Article
The Risk Factors for Developing Contrast-induced Nephropathy after the Evaluation of Trauma Patients at a Regional Trauma Center in Korea
Yoo Mi An, Soon Chang Park, Hyung Bin Kim, Young Mo Cho, Dae Seop Lee, Yong In Kim, Sang Kyun Han
Journal of Trauma and Injury 2016;29(4):124-128
DOI: https://doi.org/10.20408/jti.2016.29.4.124
Published online: December 31, 2016
  • 2,201 Views
  • 10 Download
  • 0 Crossref
  • 0 Scopus
Department of Emergency Medicine, Pusan National University Yangsan Hospital, Busan, Korea. orion0811@daum.net
Received: 9 October 2016   • Revised: 24 October 2016   • Accepted: 7 November 2016

PURPOSE
Computed tomography (CT) with intravenous (IV) contrast is an important step in the evaluation of trauma patients; however, the risk factors for contrast-induced nephropathy (CIN) in these patients remain unclear. This study determined the rate of CIN in trauma patients at a regional trauma center in Korea and identified the risk factors for developing CIN.
METHODS
We retrospectively reviewed the medical records of 138 patients for the patient demographics, creatinine levels, and vital signs. CIN was defined as an increase in creatinine by 0.5 mg/dL from admission after undergoing CT with IV contrast.
RESULTS
Of the patients, 7.2% developed CIN during their admission after receiving IV contrast for CT. In the multivariate analysis, only the creatinine level at presentation (Adjusted odds ratio [aOR], 5.944; 95% confidence interval [CI], 1.486-23.733; p=0.012) and an injury severity score (ISS) greater than 22 (aOR, 1.096; 95% CI, 1.021-1.176; p=0.011) were independently associated with the risk of CIN.
CONCLUSION
CIN is uncommon in trauma patients following CT with IV contrast. The creatinine level at presentation and ISS were independent risk factors for developing CIN in trauma patients.

Comments on this article

DB Error: no such table