DOI 10.1016/j.ijid.2017.09.025
Planning an innovation marathon at an infectious disease conference with results from the International Meeting on Emerging Diseases and Surveillance 2016 Hackathon.
Аннотация
A hackathon is best described as an 'innovation marathon'. Derived from the words 'hacking' and 'marathon', it brings together multidisciplinary teams to collaborate intensely over a short period of time to define a problem, devise a solution, and design a working prototype. International scientific meetings are conducive to successful hackathons, providing an audience of expert professionals who describe challenges and ensure the proposed solutions address end-user needs. Collaborations with local organizations and academic centers are crucial to attracting complementary specialties such as IT advisors, engineers, and entrepreneurs to develop sustainable projects. The core process of first identifying and deconstructing a problem followed by solution iteration is applicable to challenges at workplaces around the world. Ultimately, this model can be used to drive innovation and catalyze change in the global health community. The planning, execution, and outcomes of a hackathon event organized in conjunction with the International Meeting on Emerging Diseases and Surveillance (IMED 2016) are described in this article. Physicians, public health practitioners, veterinarians, IT professionals, engineers, and entrepreneurs came together for 2days to develop solutions at the intersection of emerging infectious diseases and climate change. Projects that resulted from the IMED 2016 Hackathon included environmental impact assessment software for humanitarian organization relief efforts; enhanced communication tools to prevent disease outbreaks; a participatory mobile application to speed the elimination of rabies in Indonesia; integrated disease surveillance platforms; and an improved search function for infectious disease outbreak reports in the ProMED-mail network.
Предметные рубрики MeSH
Подготовка и перевод публикации
Обработка статьи · этапы, ошибки и управление
Ошибки и ограничения
История · было → стало
Состояние обновляется каждые 5 секунд, пока блок открыт. Процент показывается только там, где известен объём работы. Пауза останавливает продолжение этапа; текущий запрос к источнику может завершиться.
Тип публикации указан по данным источника. Уровень доказательности автоматически не присваивается.