The role of XXXX in blunt @entity130 .

@entity1 @entity548 @entity1661 @entity1416 @entity130
PURPOSE: The aim of study was to evaluate the results of our experience with transarterial embolization based on a modified algorithm in @entity1 with @entity130 . MATERIALS AND METHODS: We collected data of @entity1 admitted to our hospital from January 2006 to August 2008 for blunt @entity130 . During this period, 46 @entity1 were admitted for @entity130 , of whom 17 were treated surgically, 15 conservatively and 14 with percutaneous embolisation (13 @entity1 , mean age 44.8, mean injury severity score 18.5, six with grade IV and eight with contrast blush). @entity1 in shock were referred for laparotomy and splenectomy, whereas those who were haemodynamically stable or responsive to fluid resuscitation were further evaluated with computed tomography (CT). In the presence of imaging evidence of @entity130 ranging from grade I to grade III (n=15) a conservative approach was adopted, whereas haemodynamically unstable @entity1 with grade V injury (n=17) were treated with splenectomy. Embolisation was performed in 14 @entity1 with @entity130 or in the event of contrast extravasation, regardless of injury grade. In @entity1 with diffuse organ damage, we embolised the main splenic artery, whereas in the case of @entity130 , embolisation was selective. RESULTS: Proximal embolization was required in eight cases and distal coil embolization in six. In 13 cases, we placed magnetic-resonance-compatible coils 4-6 mm in diameter; only one @entity1 was treated with gel-foam injection. Immediate technical success was achieved in all cases. In 13/14 @entity1 (92.9%), no periprocedural complications were observed, whereas the remaining @entity1 underwent splenectomy within 24 h due to recurrent @entity548 . CONCLUSIONS: On the basis of our algorithm, it is possible to reach a quick decision on the most appropriate treatment for @entity1 presenting with blunt @entity1661 , and @entity1416 seems to offer a reliable option in those with high-grade @entity130 or active @entity548 .
