Hepatic segmentectomy for curative resection of primary XXXX .

@entity1 @entity5 @entity190 @entity409 @entity1575 @entity157
OBJECTIVES: To evaluate the feasibility and results of segmentectomy for curative resection of @entity157 and to compare the clinicopathological findings of the @entity1 according to the @entity5 location in the liver. DESIGN: Case series. SETTING: A tertiary care center. @entity1 : Seventy-five @entity1 with @entity1 's grade A or B liver function who had @entity157 that was confined to one segment and who underwent segmentectomy for curative resection of the @entity5 . The @entity1 were divided into four groups: group P (posterior segmentectomy, n = 23); group A (anterior segmentectomy, n = 10); group M (medial segmentectomy, n = 16); and group L (lateral segmentectomy, n = 26). MAIN OUTCOME MEASURE: Disease-free survival rate. RESULTS: Seventy-three percent of the @entity1 had @entity1575 . The surgical mortality and morbidity rates were 5.3% and 36.0%, respectively. The 1-, 3-, and 5-year disease-free survival rates were 61.9%, 39.1%, and 26.3%, respectively, and were not significantly different among the four groups (P = .86). Group L had the least operative @entity190 and shortest operative time when compared with the other three groups (P < .05). The postoperative liver function changes were mild and transient in the four groups of @entity1 . With regard to pathological factors, only @entity5 size differed among the groups ( @entity5 in group L were significantly larger than those in the other three groups, P < .05). Forty-three percent of the recurrent @entity5 were solitary in the early stage, with 81% involving the segment(s) adjacent to the resected one and 57% being confined solely to the segment adjacent to the resected segment. @entity1 having recurrent @entity157 had significantly larger @entity5 at the time of resection than did those without recurrence (P = .03). CONCLUSIONS: Hepatic segmentectomy is an effective therapeutic approach for @entity157 and can be done safely even in @entity1 with @entity409 and @entity409 .
