MedElevator Войти в исследования
← Поиск публикаций
Медицинская библиотека · Kyobu geka. The Japanese journal of thoracic surgery · 2026

[Mitral Valve Repair in a Patient With Ischemic Cardiomyopathy].

Yokoyama Yuichiro, Emmoto Takeshi, Higashino Hiroshi, Fujieda Hiroyuki, Abe Yumiko, Abe Mitsunori

СтатьяКлинический случайАннотация на английскомПеревод в очереди

Аннотация

In patients with severe ischemic mitral regurgitation, annuloplasty alone results in early recurrence due to deterioration in tethering. Therefore, additional procedures targeting the subvalvular tissue, such as approximation or suspension of papillary muscle, have been considered. Ischemic mitral regurgitation mainly results from tethering due to left ventricular enlargement, with varying severity among cases and difficult prediction of reverse remodeling. Residual mitral regurgitation affects prognosis, necessitating reliable regurgitation control during mitral repair procedure. In some cases, valve replacement with chordal preservation may be preferable. We performed mitral valve repair for severe ischemic mitral regurgitation due to leaflet tethering. The patient was a 75-year-old male who had an acute myocardial infarction 10 years prior, which led to the progression of ischemic cardiomyopathy. Anterior leaflet augmentation using an autologous pericardial patch, suspension of the papillary muscles, and implantation of an artificial ring were performed. Six years postoperatively, the mitral valve remains in good condition and left ventricular reverse remodeling is favorable, with no heart failure observed. This procedure is considered an effective surgical option for ischemic mitral regurgitation and is hereby reported.

Для цитирования: Yokoyama Yuichiro, Emmoto Takeshi, Higashino Hiroshi, Fujieda Hiroyuki, Abe Yumiko, Abe Mitsunori. [Mitral Valve Repair in a Patient With Ischemic Cardiomyopathy].. Kyobu geka. The Japanese journal of thoracic surgery. 2026.

Предметные рубрики MeSH

Подготовка и перевод публикации
Обработка статьи · этапы, ошибки и управление
Загрузка состояния…

История · было → стало

Состояние обновляется каждые 5 секунд, пока блок открыт. Процент показывается только там, где известен объём работы. Пауза останавливает продолжение этапа; текущий запрос к источнику может завершиться.

Тип публикации указан по данным источника. Уровень доказательности автоматически не присваивается.