Go.Data Interoperability Use Cases

Common Integration Scenarios

In December 2020, several Go.Data community members and HIS stakeholders were engaged to collect common interoperability requirements for Go.Data implementations. Key requirements for data interoperability were summarized into two main categories:

Transactional data exchange (individual-level sharing)

Integration for transactional data exchange and building shared records for enhanced collaboration. Many Go.Data implementers have requirements to share individual Case or Contact records with country HMIS/ surveillance systems, and sometimes with lab or electronic medical records systems. Such integrations may require a 1- or 2-way exchange of data between different systems.


Aggregate data exchange (summary-level sharing)

Integration for aggregate data exchange is a common requirement and primarily used for external reporting from Go.Data to another system. This is typically a 1-way data exchange flow, where Go.Data implementers want to share data collected & monitoring reports with external stakeholders, partners, and national reporting systems like DHIS2.


Common Use Cases

See this table for interoperability use cases identified by the Go.Data partners through “Interoperability” Ask The Expert sessions and conversations with Go.Data impleementers and team in December 2020.

*Table Below: 6 use cases from this list have been implemented as Interoperability Reference Implementations to showcase common interoperability scenarios and priority requirements. In the table below, we have highlighted the common use cases we will address via solutions developed as reference implementations.

# Type Use Case Solutions Comments
1 2-way contact record exchange As a MOH employee, I would like to integrate contact data from my country’s surveillance system, so that I can use Go.Data for contact tracing & follow-up in a way that does not duplicate efforts. Users may leverage available web APIs to configure 2-way data integration and share individual records, matching on unique identifiers (see reference implementation #1). Other options: Excel upload tools, integration scripts See FAQs for more guidance on building shared records, unique identifiers, & duplicate prevention.
2 Applying data standards As a Go.Data user, I would like to automatically apply the FHIR data standard to any contact information collected via Go.Data before sharing with the HMIS to ensure data interoperability and to avoid any manual data cleaning/reformatting steps during information exchange. Users may extract Go.Data data via APIs and develop a script to automate the applying of standards & integration with HMIS (see reference implementation #2). Other options: Excel upload tools, integration scripts Applying data standards later in the ETL process is common for scenarios where it’s unrealistic to apply these standards right at data collection. See Applying Data Standards section to learn more.
3 Importing lab results import As a Go.Data analyst, I would like to directly integrate lab datasets so that I can more quickly and securely register Contact and Case records to ensure data quality and save time on data entry. Users may leverage available Excel templates for building & importing new Contact and Case records (see reference implementation #3). Other options: direct integration via APIs Lab datasets are the primary data source for many Go.Data implementers, but many struggle to build Contact and Case records from lab sample data.
4 Integrating mobile surveys As a MOH employee, I would like to integrate case data collected via my mobile survey tool so that I can monitor new case registrations in real-time and quickly follow up with new contacts. Users may leverage available web APIs to configure data integration and register survey submissions as new cases and contacts (see reference implementation #4). Other options: Excel upload tools, integration scripts Many tools for mobile data collection (incl., Kobo Toolbox, ODK, CommCare, ONA, SurveyCTO) have a “data forwarding” feature for quicker integration setup. See [X section] to learn more.
5 Importing locations/ facility lists As a Go.Data analyst, I would like to import health facility lists and geographical/admin units from the HMIS so that I can more easily exchange information with the MOH and other partners. Users may leverage the web APIs or Excel import features to integrate geographic/admin units or health facility lists from DHIS2 and other HMIS to enable easy reporting and information exchange (see reference implementation #5). Other options: Excel upload tools, UPC DHIS2 integration scripts See Go.Data repository for UPC scripts for “Org Unit converter” to import from DHIS2. What is the Facility List resource Lucas mentioned? … can we demo a live sync with a HeRAMS system?
6 Aggregate reporting for KPIs As a MOH employee using DHIS2, I would like to receive a weekly summary of Go.Data data cases to monitor performance across key COVID-19 indicators (e.g., # confirmed cases, # hospitalized cases, transmission classifications). Users may leverage the Go.Data web API to extract relevant source data, develop an integration script to summarize & re-format this data, and then map and upload to DHIS2 on s scheduled basis (see reference implementation #6). Other options: Excel upload & reporting tools, Python and R scripts (see Analytics docs). DHIS2 provides a COVID-19 Surveillance Package for aggregate data capture, but countries may have their own custom modules configured for aggregate data capture & surveillance. See the Go.Data Github for links to sample Python and R scripts.

*Feedback? Solutions? New use cases to contribute? Contact godata@who.int or share on the Go.Data Community.