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

DOI 10.1111/bcp.12474

Медицинская библиотека · British journal of clinical pharmacology · 2015

Adverse drug reactions - examples of detection of rare events using databases.

Chan Esther W, Liu Kirin Q L, Chui Celine S L, Sing Chor-Wing, Wong Lisa Y L, Wong Ian C K

СтатьяОбзорПеревод пока не подготовлен

Аннотация

It is recognised that randomised controlled trials are not feasible for capturing rare adverse events. There is an increasing trend towards observational research methodologies using large population-based health databases. These databases offer more scope for adequate sample sizes, allowing for comprehensive patient characterisation and assessment of the associated factors. While direct causality cannot be established and confounders cannot be ignored, databases present an opportunity to explore and quantify rare events. The use of databases for the detection of rare adverse events in the following conditions, sudden death associated with attention deficit hyperactivity disorder (ADHD) treatment, retinal detachment associated with the use of fluoroquinolones and toxic epidermal necrolysis associated with drug exposure, are discussed as examples. In general, rare adverse events tend to have immediate and important clinical implications and may be life-threatening. An understanding of the causative factors is therefore important, in addition to the research methodologies and database platforms that enable the undertaking of the research.

Для цитирования: Chan Esther W, Liu Kirin Q L, Chui Celine S L, Sing Chor-Wing, Wong Lisa Y L, Wong Ian C K. Adverse drug reactions - examples of detection of rare events using databases.. British journal of clinical pharmacology. 2015. DOI: 10.1111/bcp.12474.

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

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

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

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

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