MedElevator Войти в исследования
← Поиск публикаций

DOI 10.1016/j.ijcard.2016.04.114

Медицинская библиотека · International journal of cardiology · 2016

Missed bleeding events after ticagrelor in PEGASUS trial: Massive non-compliance, information censoring, or both?

Serebruany Victor, Tomek Ales

Редакционная статьяПеревод в очереди

Аннотация

PEGASUS trial reported reduction of composite primary endpoint after conventional 180mg/daily ticagrelor (CT), and lower 120mg/daily dose ticagrelor (LT) at expense of extra bleeding. Following approval of CT and LT for long-term secondary prevention indication, recent FDA review verified some bleeding outcomes in PEGASUS. To compare the risks after CT and LT against placebo by seven TIMI scale variables, and 9 bleeding categories considered as serious adverse events (SAE) in light of PEGASUS drug discontinuation rates (DDR). The DDR in all PEGASUS arms was high reaching astronomical 32% for CT. The distribution of some outcomes (TIMI major, trauma, epistaxis, iron deficiency, hemoptysis, and anemia) was reasonable. However, the TIMI minor events were heavily underreported when compared to similar trials. Other bleedings (intracranial, spontaneous, hematuria, and gastrointestinal) appear sporadic, lacking expected dose-dependent impact of CT and LT. Few SAE outcomes (fatal, ecchymosis, hematoma, bruises, bleeding) paradoxically reported more bleeding after LT than after CT. Many bleeding outcomes were probably missed in PEGASUS potentially due to massive non-compliance, information censoring, or both. The FDA must improve reporting of trial outcomes especially in the sponsor-controlled environment when DDR and incomplete follow-up rates are high.

Для цитирования: Serebruany Victor, Tomek Ales. Missed bleeding events after ticagrelor in PEGASUS trial: Massive non-compliance, information censoring, or both?. International journal of cardiology. 2016. DOI: 10.1016/j.ijcard.2016.04.114.

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

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

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

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

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