integration:dhis2_integration

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revisionBoth sides next revision
integration:dhis2_integration [2021/04/29 09:57] – [Requisites] Gary Willettsintegration:dhis2_integration [2021/04/29 10:18] – [mSupply connection to DHIS2] Gary Willetts
Line 21: Line 21:
  
 ===== mSupply connection to DHIS2 ===== ===== mSupply connection to DHIS2 =====
-Now mSupply can be connected to DHIS2 using the preferences to enter the database credentials+Before you can send mSupply data to DHIS2 instance, you need to tell mSupply where the data has to go. To do that, go to //File > Preferences// and click on DHIS2 tab to get to this window
  
 {{ :integration:preferences_dhis2_connection.png?600 |}} {{ :integration:preferences_dhis2_connection.png?600 |}}
 +
 +  * **Url:** The URL of the DHIS2 database including the port if any.
 +  * **Username:** The username mSupply will use to access the DHIS2 database
 +  * **Password:** The password mSupply will use to access the DHI2 database
 +  * **Client:** The client name mSupply must use to access the database.
 +  * **Secret:** The secret that is used for mSupply to access the DHIS2 database. No need to enter this if none was provided.
 +
 +<WRAP info center round 90%>
 +If this page already has settings entered and they have been used to successfully connect to the DHIS2 database then a "Last successful connection: //date & time//" message will show next to the **Test connection** button.
 +</WRAP>
 +
 +After entering the values you should click on the **Test connection** button to save the credentials and check that mSupply can now access the DHIS2 database. If the connection is successful you will see a green "Connection successful" message next to the button.
 +
 +If the connection is not successful you will see a red "Authentication failed" message next to the button. Check your settings, edit them as necessary and try again. The connection problem may not be the credentials, it could be something else like the settings for firewalls between mSupply and the DHIS2 database. 
  
 Once configured, a scheduler will run and regularly send data from mSupply to DHIS2. In order for this to work, you first need to have a DHIS2 instance that has links with mSupply for each organisation unit and data element.  Once configured, a scheduler will run and regularly send data from mSupply to DHIS2. In order for this to work, you first need to have a DHIS2 instance that has links with mSupply for each organisation unit and data element. 
Line 29: Line 43:
 Contact our team to help you to create the specific data elements on DHIS2 accordingly with the data that you want to be sent. We will configure it for your specific situation. Contact our team to help you to create the specific data elements on DHIS2 accordingly with the data that you want to be sent. We will configure it for your specific situation.
  
-This has been done already for Laos and countries that are part of the [[https://tupaia.org | Tupaia]] project including Kiribati, Tonga, Solomon Islands, Cook IslandsVanuatuwith some more to come.+This has been done already for Laos and countries that are part of the [[https://tupaia.org | Tupaia]] project including Kiribati, Tonga, Solomon Islands, Cook Islands and Vanuatu with some more to come!
 \\ \\
 \\ \\
  • Last modified: 2021/10/08 11:06
  • by Gary Willetts