Skip directly to site content Skip directly to page options Skip directly to A-Z link Skip directly to A-Z link Skip directly to A-Z link
Volume 31, Number 1—January 2025
Online Report

Development and Implementation of a Public Health Event Management System, Nigeria, 2018–2024

James Elston1Comments to Author , Womi-Eteng Oboma Eteng1, Chikwe Ihekweazu, Isabel Oliver, Everistus Aniaku, Anwar Abubakar, Christopher T. Lee, Emmanuel Benyeogor, Iain Roddick, Sophie Logan, Ebere Okereke, Leena Inamdar, Olusola Aruna, Rejoice Luka-Lawal, Christine Manthey, Lawrence Hinkle, Gloria Nunez, Emmanuel Agogo, Rabi Usman, Emmanuel Lucky Sunday, Muntari Hassan, John Oladejo, and Ifedayo Adetifa
Author affiliation: United Kingdom Health Security Agency, London, UK (J. Elston, I. Oliver, I. Roddick, S. Logan, L. Inamdar, O. Aruna); Africa Centres for Disease Control and Prevention, Addis Ababa, Ethiopia (W.-E.O. Eteng); Nigeria Centre for Disease Control and Prevention, Abuja, Nigeria (W.-E.O. Eteng, C. Ihekweazu, E. Ariaku, A. Abubakar, E. Benyeogor, R. Luka-Lawal, E.L. Sunday, M. Hassan, J. Oladejo, I. Adetifa); World Health Organization, Geneva, Switzerland (C. Ihekweazu); Resolve to Save Lives, New York, New York, USA (C.T. Lee, G. Nunez); Reaching the Last Mile Foundation, Abu Dhabi, United Arab Emirates (E. Okereke); Centers for Disease Control and Prevention, Atlanta, Georgia, USA (C. Manthey); CDC Foundation, Atlanta, Georgia, USA (L. Hinkle); Resolve to Save Lives, Abuja, Nigeria (E. Agogo, R. Usman)

Main Article

Table 1

Institutional and user system requirements for SITAware, the public health event management system developed and implemented in Nigeria, 2018–2024*

Perspective Requirement Considerations
Organizational
 Low cost Limited funding was available for development and the system had to be designed and implemented at a low cost relative to de novo software solutions. No additional funding for staffing or to address IT infrastructure was available initially
Minimal hardware or software requirements The requirement was to work within a given infrastructure. No funding was available for the provision of software or hardware
Minimal need for maintenance NCDC would host the system on its web server and maintain the system without additional resources
Optimal performance over low internet bandwidth
 In view of context, the system would need to perform well with low internet bandwidth
Users: data entry (e.g., surveillance staff)
 Simple, easy-to-use interface The system would need to be straightforward to use and easy to understand for users
Minimal time commitment for the user In view of competing demands for a limited workforce, the system should permit rapid data entry
Benefit to user
 The user should see benefit or reward in using the system relevant to their day-to-day role
Users: leadership
 Overview of events, incidents outbreaks An ‘at a glance’ overview or display of current incidents and outbreaks was required
Auditable trail of events, evolution, public health response
 A full history of entries to enable oversight and facilitate identification of lessons arising
Data Sharing Real-time sharing of incident information within and across organizational boundaries The system should permit real-time sharing internally between NCDC departments and teams and externally across organizational boundaries (e.g., between states and NCDC)

*IT, information and technology; NCDC, Nigeria Centre for Disease control and Prevention.

Main Article

1These authors are co–first authors

Page created: December 16, 2024
Page updated: December 22, 2024
Page reviewed: December 22, 2024
The conclusions, findings, and opinions expressed by authors contributing to this journal do not necessarily reflect the official position of the U.S. Department of Health and Human Services, the Public Health Service, the Centers for Disease Control and Prevention, or the authors' affiliated institutions. Use of trade names is for identification only and does not imply endorsement by any of the groups named above.
file_external