worldhealthorganization / godata-dhis2-interop-app

DHIS2-based application to enable secure and flexible metadata exchange between DHIS2 and Go.Data.

DHIS2-Go.Data Interoperability App

Documentation site here: https://go-data.gitbook.io/go.data-dhis2-interoperability-app/

Overview

The DHIS2-Go.Data Interoperability App enables metadata to be securely exchanged between DHIS2 (a widely used system for national health information management developed by the University of Oslo) and Go.Data (an outbreak response tool developed by WHO). This includes exchange of reference metadata used across both platforms (i.e. location hierarchies, facility lists); and case/contact data (cases being registered and investigated; and their contacts who are being listed and traced).

Such an integration enables field teams to make use of additional visualizations for chains of transmission and contact tracing follow up in Go.Data during an acute outbreak scenario while ensuring key field intel gets reflected back into overarching DHIS2 system.

This project was bootstrapped with DHIS2 Application Platform.

Available Scripts

In the project directory, you can run:

yarn start

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

yarn test

Launches the test runner and runs all available tests found in /src.

See the section about running tests for more information.

yarn build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
A deployable .zip file can be found in build/bundle!

See the section about building for more information.

Learn More

You can learn more about the platform in the DHIS2 Application Platform Documentation.

You can learn more about the runtime in the DHIS2 Application Runtime Documentation.

To learn React, check out the React documentation.

Feedback and contact

For any questions or feedabck, please contact [email protected] or post on the Go.Data Community of Practice here: https://community-godata.who.int/

Bidirectionality tasks note

The bidirectional tasks endpoint is /livetask, its logic can be found in ./src/views/interop_tasks/LiveForm folder.

godata-dhis2-interop-app's Issues

Namespace (Petar to add)

Petar to add in description of what is needed.

Loading default configuration fails

Critical bug that renders the app not usable at present
Tested on UPC server (http://dtim.essi.upc.edu:8082/dhis2/) and 2 DHIS2 play servers
Failure to load default configurations
cc @silviaemorreale @metabig @petarjov

Error when sending outbreaks from DHIS2 to Go.Data

When sending outbreaks from DHIS2 to Go.Data the second application "breaks".

• Existing Go.Data outbreaks disappear. It seems that they are still in Go.Data, but not visible (they are not deleted, but not available in the platform or the database)
• The icons from the action column are no longer visible, which means that the outbreak can not be seen, modified or activated for work

@sarahollis @petarjov

Change to semantic versioning & submit latest version to App Hub

The version submitted to the app hub 1.0.0 is about one month older than the latest release on GitHub (1.0.1) - it's recommended to set up automatic publication (or at least manually publish to both places). Recommend that you use semantic versioning - version 1.0.1 introduces new functionality to the app and so it should be named 1.1.0 to indicate to app users that this is new functionality and not just a fixed bug.
cc @silviaemorreale @metabig

Failure to load Interoperability Tasks tab

Critical bug that renders the app not usable at present:
Tested on UPC server (http://dtim.essi.upc.edu:8082/dhis2/) and 2 DHIS2 play servers
"Interoperability Tasks" tab shows a loading spinner forever, and many HTTP requests fail, at least when the app is first opened, not able to get the Interoperability Tasks tab to load at all
cc @silviaemorreale @metabig @petarjov please advise if you are able

Utilize Personal Access Token vs. username/pw

The app still requires the user to enter a DHIS2 server, username, and password, which as previously mentioned is less secure than using the existing session connected to the DHIS2 instance where the app is installed. It would be much better to remove the dhis2 configuration and just request data directly from the local DHIS2 instance. If communicating with an external DHIS2 server it is strongly recommended to support and prefer Personal Access Tokens instead of usernames and passwords.
cc @silviaemorreale @metabig

Add questionnaire variables when loading Go.Data mapping

When mapping Go.Data-DHIS2 variables, include a feature to load, in addition to the Go.Data core variables, the ones that have been created in the case, contacts or lab questionnaires.

To load these variables, the DHIS2 interoperability app should use the outbreak UiD as the questionnaires might vary from one outbreak to another.

cc @sarahollis

Invalid HTTP request headers

Many of the headers added to requests in the source code (such as here) are not valid HTTP request headers - these are CORS response headers which are set by the server, not the client.
cc @silviaemorreale @metabig @petarjov please let us know if you may have any insights

Failure when saving metadata mapping

Saving metadata mappings often fails, but no error message or other information is shown to the user.
@silviaemorreale @metabig @petarjov

more specific and intuitive error messages

Could leave it vague, in a few categories, for example:

1. incorrect credentials to one of the servers
2. incorrect mapping

etc.