Predictive factors of Gastrointestinal motility Dysfunction after gastrojejunostomy for XXXX .

@entity1 @entity10189 @entity6 @entity384 @entity3085 @entity344 @entity1084
BACKGROUND: Despite the establishment of effective medical therapies in @entity10189 , @entity1084 remains one of the most common health problem in Tunisia. Various operations have been attempted, which may lead to postoperative morbidity. @entity344 is the most common complications. AIM: to determine the predictive factor of @entity344 after gastrojejunostomy for @entity10189 . METHODS: We carried out a retrospective study to evaluate the postoperative recovery of the motility of the upper gastrointestinal tract after gastrojejunostomy for @entity10189 . During the 9- year study, 138 @entity1 underwent operations for @entity10189 . Among the @entity1 , 116 (84,1%) were treated with gastrojejunostomy. Descriptive statistics, univariate and multivariate analyses were performed. RESULTS: The mean age of @entity1 was 47.85 years (range: 19- 92years) and most. Were male (84, 5 %). Ninety two (79.3%) @entity1 had a documented history of @entity10189 . The duration of symptoms ranged from 10 to 372 days (mean: 135.86 days). Eighty two (71%) @entity1 were operated on through laparotomy. Laparoscopic procedure was performed in 29% of the @entity1 . There was no operative mortality. Perioperative morbidity occurred in 12.4% (14 @entity1 ). @entity344 occurred in 12 @entity1 (10.3%). It was treated by nasogastric aspiration and prokinetics. By univariate analysis; @entity6 (0,010), @entity3085 (0,049), ASA class (0.05) were all statistically associated with @entity344 in this series. Multivariate logistic regression analysis (table 2) showed that the @entity3085 (0,009), ASA class (0.02) were the main predictors of @entity344 after gastrojejunostomy for @entity10189 in the followed @entity1 . CONCLUSION: @entity344 is the most common complications after gastrojejunostomy for pyloric adult stenosis. Surgery must be preceded by careful medical preparation. It is more likely to occur in @entity1 with an ASA class 2 or greater. Those @entity1 should be considered for other treatment options, such as @entity384 .
