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

DOI 10.1093/jamiaopen/ooag189

Медицинская библиотека · JAMIA open · 2026

Advancing multi-database cohort studies: lessons learned from a studyathon in a pharmaceutical company.

Inan-Eroglu Elif, Rodriguez-Molina Daloha, Abdelgawwad Khaled, Dinkel-Keuthage Carina, Soriano Gabarró Montse, Vora Pareen, Candore Gianmario, Vizcaya David, Manlik Katrin

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

Аннотация

OBJECTIVES

To evaluate the feasibility and applicability of the studyathon format within a pharmaceutical company setting for generating reliable real-world evidence rapidly for a business-relevant research question.

MATERIALS AND

METHODS

Conducted at Bayer, the studyathon assessed recurrent events following a first-ever transient ischemic attack. It involved an 8-week preparatory phase, a 1-week execution phase, and a 3-week post-event phase, using multiple real-world data sources.

RESULTS

The studyathon concluded successfully with a conference abstract submission. Key learnings included the importance of defining precise research questions, organizational alignment, thorough preparation, and leveraging diverse expertise and skill sets.

DISCUSSION: The studyathon format proved suited for a pharmaceutical setting and revealed insights into its application. Our learnings highlight differences from multi-stakeholder community studyathons.

CONCLUSION

The studyathon demonstrated its potential as a valuable research approach within a pharmaceutical company. It improved study timelines and cross-functional collaboration while preserving scientific rigor.

Для цитирования: Inan-Eroglu Elif, Rodriguez-Molina Daloha, Abdelgawwad Khaled, Dinkel-Keuthage Carina, Soriano Gabarró Montse, Vora Pareen, Candore Gianmario, Vizcaya David, Manlik Katrin. Advancing multi-database cohort studies: lessons learned from a studyathon in a pharmaceutical company.. JAMIA open. 2026. DOI: 10.1093/jamiaopen/ooag189.
Подготовка и перевод публикации
Обработка статьи · этапы, ошибки и управление
Загрузка состояния…

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

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

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