Core system |
Datasets |
Must include 1) Integrated Disease Surveillance and Response (IDSR, received weekly) 2) Infection, Prevention and Control (IPC, received monthly), and 3) Alerts data (received daily). |
|
Input |
Must accept tabular data formats (e.g. Excel and CSV). Must integrate with common mobile data collection APIs (KoboToolbox and CommCare). |
|
Output |
Cross-browser web interface. |
Analytics |
IDSR, IPC |
Must follow current MoHS guidelines. |
|
Alerts |
Use baseline mortality rates for Sierra Leone for thresholds. |
|
Reporting |
Must include whether facilities reported on-time for IDSR and IPC. |
|
Risk score |
Provide aggregate risk statistics for all three datasets. |
|
Smart search |
Ability to geographically and semantically search over related datasets that are collected ad hoc and are not included in the district health information system (DHIS2). |
Network |
Loading time |
The initial loading of the page should take no longer than 5 seconds under normal conditions in Port Loko DHMT. |
Usability |
Data subsets |
System must provide functionality to select data by district, chiefdom and section. |
|
Data visualization |
Data should be represented on graphs and maps, and visualizations should be exported as PDFs. |
|
Training requirements |
The system should require minimal training (less than a day) and should not require specialized software skills (e.g. GIS data skills). |
Security |
Access privileges |
Due to the sensitive nature of the data stored, each user requires secure, individual access to the server. |