Relation of epicardial adipose tissue to XXXX .

@entity1 @entity453 @entity460 @entity299 @entity731
Adipose tissue surrounding the coronary arteries has been suggested to induce development of @entity731 . We explored the relation between epicardial adipose tissue (EAT) volume and @entity453 using multislice computed tomography. The study population consisted of 190 @entity1 who had undergone multislice computed tomographic coronary angiography. Coronary artery @entity460 score was assessed. In addition, @entity1 were classified as having (1) no @entity731 , (2) nonobstructive @entity731 (luminal narrowing <50%), (3) obstructive @entity731 (luminal narrowing >or=50%) in a single vessel, or (4) obstructive @entity731 in the left main coronary artery and/or multiple vessels. @entity299 (3.00-mm thickness, range 35 to 40 slices per heart) were traced semiautomatically from the border of EAT below the apex to a point at the center of the left atrium. Tissue with values from -250 to -30 HU was assigned as EAT. EAT volume within the traced area was then automatically quantified. Mean EAT volume was 84 +/- 41 ml. @entity1 with a coronary artery @entity460 score >10 had significantly larger average EAT volume (100 +/- 40 ml) compared with @entity1 with @entity460 scores <or=10 (59 +/- 27 ml, p <0.001). Sensitivity and specificity for prediction of a @entity460 score >10 were 77% and 70% with a cut-off EAT value of 73 ml. In @entity1 with normal coronaries mean EAT volume (63 +/- 31 ml) was significantly smaller than in @entity1 with @entity731 (99 +/- 40 ml, p <0.001). Using a cut-off EAT volume of 75 ml, the sensitivity and specificity for presence of @entity731 were 72% and 70%. Interestingly, quantity of EAT did not significantly increase with increasing extent or severity of @entity731 . After adjustments for risk factors EAT volume remained a significant predictor of @entity453 (p = 0.001). In conclusion, a significant relation was shown between EAT volume and presence of @entity453 . Quantification of EAT may be useful to identify @entity1 at risk for @entity453 .
