These tools will no longer be maintained as of December 31, 2024. Archived website can be found here. PubMed4Hh GitHub repository can be found here. Contact NLM Customer Service if you have questions.


Pubmed for Handhelds

PUBMED FOR HANDHELDS

Search MEDLINE/PubMed

  • Title: Improving health information systems during an emergency: lessons and recommendations from an Ebola treatment centre in Sierra Leone.
    Author: Oza S, Wing K, Sesay AA, Boufkhed S, Houlihan C, Vandi L, Sebba SC, McGowan CR, Cummings R, Checchi F.
    Journal: BMC Med Inform Decis Mak; 2019 May 27; 19(1):100. PubMed ID: 31133075.
    Abstract:
    BACKGROUND: The 2014-2016 West Africa Ebola epidemic highlighted the difficulty of collecting patient information during emergencies, especially in highly infectious environments. Health information systems (HISs) appropriate for such settings were lacking prior to this outbreak. Here we describe our development and implementation of paper and electronic HISs at the Sierra Leone Kerry Town Ebola treatment centre (ETC) from 2014 to 2015. We share our approach, experiences, and recommendations for future health emergencies. METHODS: We developed eight fact-finding questions about data-related needs, priorities, and restrictions at the ETC ("inputs") to inform eight structural decisions ("outputs") across six core HIS components. Semi-structured interviews about the "inputs" were then conducted with HIS stakeholders, chosen based on their teams' involvement in ETC HIS-related activities. Their responses were used to formulate the "output" results to guide the HIS design. We implemented the HIS using an Agile approach, monitored system usage, and developed a structured questionnaire on user experiences and opinions. RESULTS: Some key "input" responses were: 1) data needs for priorities (patient care, mandatory reporting); 2) challenges around infection control, limited equipment, and staff clinical/language proficiencies; 3) patient/clinical flows; and 4) weak points from staff turnover, infection control, and changing protocols. Key outputs included: 1) determining essential data, 2) data tool design decisions (e.g. large font sizes, checkboxes/buttons), 3) data communication methods (e.g. radio, "collective memory"), 4) error reduction methods (e.g. check digits, pre-written wristbands), and 5) data storage options (e.g. encrypted files, accessible folders). Implementation involved building data collection tools (e.g. 13 forms), preparing the systems (e.g. supplies), training staff, and maintenance (e.g. removing old forms). Most patients had basic (100%, n = 456/456), drug (96.9%, n = 442/456), and additional clinical/epidemiological (98.9%, n = 451/456) data stored. The questionnaire responses highlighted the importance of usability and simplicity in the HIS. CONCLUSIONS: HISs during emergencies are often ad-hoc and disjointed, but systematic design and implementation can lead to high-quality systems focused on efficiency and ease of use. Many of the processes used and lessons learned from our work are generalizable to other health emergencies. Improvements should be started now to have rapidly adaptable and deployable HISs ready for the next health emergency.
    [Abstract] [Full Text] [Related] [New Search]