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

DOI 10.1080/14740338.2023.2251390

Медицинская библиотека · Expert opinion on drug safety · 2023

Evaluating Ubrogepant-related adverse events using the FDA adverse event reporting system.

Cao Bing, Gu Shanshan, Shen Zhisen, Zhang Yuna, Shen Yiming, Chen Hang

СтатьяПеревод в очереди

Аннотация

BACKGROUND

Migraine has a high prevalence in the population and accounts for 12% of primary headaches. Ubrogepant is used for the treatment of acute migraine, and although some clinical trials have demonstrated the safety of Ubrogepant, its long-term safety in a large sample of the population remains to be investigated.

METHODS

We collected data from the US Food and Drug Administration Adverse Event Reporting System (FAERS) database. We used reporting odds ratio (ROR), the proportional reporting ratio (PRR), the information component (IC) and the empirical Bayes geometric mean (EBGM) to evaluate Ubrogepant-induced adverse events (AEs).

RESULTS

We screened out 2,067 reports of Ubrogepant as primary suspected (PS) and 6,190 reports of Ubrogepant-induced AEs as PS. Our results showed that Ubrogepant-induced AEs targeted 4 system organ classes (SOCs), detected 32 Preferred terms (PTs) signals in 9 SOCs, including common Ubrogepant label consistent with Migraine, Nausea, Somnolence, Paraesthesia oral and Dizziness, It also includes the AEs of Hemiparesis, Mental impairment, Dysstasia, Tinnitus, Chest pain, Cold sweat, Neck pain, etc. that have not been demonstrated in previous studies.

CONCLUSIONS

Our study identified new AEs that have not been reported, which provides a new guidance to deepen the comprehension of the safety of Ubrogepant.

Для цитирования: Cao Bing, Gu Shanshan, Shen Zhisen, Zhang Yuna, Shen Yiming, Chen Hang. Evaluating Ubrogepant-related adverse events using the FDA adverse event reporting system.. Expert opinion on drug safety. 2023. DOI: 10.1080/14740338.2023.2251390.

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

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

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

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

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