Go.Data is an outbreak investigation tool for field data collection during public health emergencies. The tool is an initiative of public health partners, based on their experiences in outbreak response, and was developed by WHO in collaboration Global Outbreak Alert and Response Network (GOARN) partners. Go.Data is a free tool currently in use by public health entities and institutions at the national and sub-national level in over 60 countries and 80 institutions across all six WHO regions for case investigation and contact tracing.
DHIS2 is the world's largest health information management system — developed through global collaboration led by the University of Olso (UiO). DHIS2 began in post-Apartheid South Africa and is now a global open-source project coordinated by the Health Information Systems Programme (HISP) at UiO. More than 73 countries worldwide use DHIS2 for collecting and analyzing health data.
Since Go.Data is an outbreak investigation tool and DHIS2 is used for national routine and active surveillance, we saw a need to create interoperability between them to allow the strength of Go.Data’s investigation tools to be leveraged for outbreaks during finite period while maintaining one national data repository in DHIS2 over time. The WHO Go.Data team partnered with the Polytechnic University of Catalonia (UPC) to develop an interoperability app allowing the two systems to complement each other, resulting in the Go.Data-DHIS2 Interoperability App.
Use Case 1: Send registered cases/contacts in DHIS2 to Go.Data, for further detailed case investigation and contact tracing, or purely to visualize the relationships more easily
This includes transfer of people (tracked entities, whether case or contact) or events (case-based data) in DHIS2 Tracker or Event Capture to dynamically become cases or contacts in Go.Data. Perhaps you are only registering cases in DHIS2, but would like to do more extensive contact tracing and longitudinal follow up of cases and their contacts in Go.Data, and view Chains of Transmission. The app will send all necessary metadata associated with that outbreak (locations, etc) in addition to case information that has already been captured in DHIS2 to eliminate duplicate data capture.
Use Case 2: Send cases/contacts in Go.Data to DHIS2 to ensure all systems capture field intel
This includes transfer of cases/contacts in Go.Data to become represented as cases/contacts in DHIS2. This can be useful if you are capturing minimum datapoints in DHIS2 case line-lists but have a subset of cases that need to be investigated more exhaustively in a more light-weight way. Additional field intel you collect via Go.Data can be sent back to DHIS2, or perhaps just the variables you need in DHIS2 (key attributes). If during contact tracing you find that a contact has converted to a case, this can also be sent back to DHIS2 to alert across teams in real time.
Use Case 3: Transfer cases/contacts Go.Data to DHIS2 Aggregate Reporting
This can be useful if you are using DHIS2 for aggregate reporting metrics across disease areas, including outbreaks, and would like to still capture aggregate summaries in the same place. This solution is currently WIP.
These settings have to be configured at the beginning the first time.