目的 探讨腹腔镜左半结肠癌根治术中采用肠系膜下动脉优先解剖联合完全内侧入路(Priority Anatomy of the Inferior Mesenteric Artery Combined with Complete Medial Approach,IMA-CMA)技术对淋巴结清扫的影响。方法 回顾性选取2019年...目的 探讨腹腔镜左半结肠癌根治术中采用肠系膜下动脉优先解剖联合完全内侧入路(Priority Anatomy of the Inferior Mesenteric Artery Combined with Complete Medial Approach,IMA-CMA)技术对淋巴结清扫的影响。方法 回顾性选取2019年5月-2023年5月南平第一医院治疗的81例腹腔镜左半结肠癌根治术患者的临床资料,根据手术方法不同分为IMA-CMA组和对照组,其中IMA-CMA组44例,对照组37例。对照组采用传统入路技术,IMA-CMA组采用IMA-CMA技术,比较两组患者的手术相关指标、淋巴结清扫情况、术后肠功能恢复情况、并发症发生情况及复发率和转移率。结果 同对照组相比较,IMA-CMA组手术时间较短,术中出血量较低,253组淋巴结清扫数目较多,差异有统计学意义(P均<0.05)。同对照组相比较,IMA-CMA组腹痛腹胀持续时间、术后排便时间及术后排气时间均较短,差异有统计学意义(P均<0.05)。IMA-CMA组并发症发生率为4.55%,低于对照组的18.92%,差异有统计学意义(χ^(2)=4.204,P<0.05)。术后1年,IMA-CMA组和对照组复发率、转移率比较,差异无统计学意义(P均>0.05)。结论 腹腔镜左半结肠癌根治术中采用IMA-CMA技术能够缩短手术时间,减少术中出血量,对淋巴结的清扫情况更佳,且可以改善术后肠功能恢复情况及并发症发生情况,不增加复发和转移风险。展开更多
On the basis of software testing tools we developed for progrmnming languages, we firstly present a new control flowgraph model based on block. In view of the notion of block, we extend the traditional program-based s...On the basis of software testing tools we developed for progrmnming languages, we firstly present a new control flowgraph model based on block. In view of the notion of block, we extend the traditional program-based software test data adequacy measurement criteria, and empirically analyze the subsume relation between these measurement criteria. Then, we define four test complexity metrics based on block. They are J-complexity 0; J-complexity 1 ; J-complexity 1 + ; J-complexity 2. Finally, we show the Kiviat diagram that makes software quality visible.展开更多
文摘On the basis of software testing tools we developed for progrmnming languages, we firstly present a new control flowgraph model based on block. In view of the notion of block, we extend the traditional program-based software test data adequacy measurement criteria, and empirically analyze the subsume relation between these measurement criteria. Then, we define four test complexity metrics based on block. They are J-complexity 0; J-complexity 1 ; J-complexity 1 + ; J-complexity 2. Finally, we show the Kiviat diagram that makes software quality visible.
