integration:dhis2_lmis_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
integration:dhis2_lmis_integration [2024/10/18 08:49] – [mSupply preferences] Gary Willettsintegration:dhis2_lmis_integration [2024/10/22 07:07] (current) – [mSupply preferences] Gary Willetts
Line 14: Line 14:
 The next part of the process is that the sending store sends goods to the facility that requested them with the requisition. The goods are sent with a packing list that contains a QR code. When the receiving facility receives the goods they add the consignment to the DHIS2 RTS capture app by scanning the QR code and check what has arrived. When they are happy the receiving facility marks the consignment as complete. The next part of the process is that the sending store sends goods to the facility that requested them with the requisition. The goods are sent with a packing list that contains a QR code. When the receiving facility receives the goods they add the consignment to the DHIS2 RTS capture app by scanning the QR code and check what has arrived. When they are happy the receiving facility marks the consignment as complete.
  
-On a daily schedule mSupply checks the DHIS2 database for complete consignments and retrieves them. mSupply processes the details of the consignment and sends details of the stock supplied for the consignment to the DHIS2 server. The DHIS2 server then sends the updated stock levels to the RTS capture app at the requesting facility.+On a daily schedule mSupply checks the DHIS2 database for complete consignments and retrieves them (at the same time mSupply fetches stock on hand figures for the items in the various facilities. This is not shown in the diagram below). mSupply processes the details of the consignment and sends details of the stock supplied for the consignment to the DHIS2 server. The DHIS2 server then sends the updated stock levels to the RTS capture app at the requesting facility.
  
 This process is illustrated in the following diagram:  This process is illustrated in the following diagram: 
Line 54: Line 54:
   * **Secret:** Only visible and used if **Basic authentication** is checked. The secret that is used for mSupply to access the DHIS2 database. No need to enter this if none was provided.   * **Secret:** Only visible and used if **Basic authentication** is checked. The secret that is used for mSupply to access the DHIS2 database. No need to enter this if none was provided.
   * **Test connection button:** Click this to test the connection to the DHIS2 server. You will be shown a message that tells you whether mSupply was able to connect to the DHIS2 server with the credentials you have provided.   * **Test connection button:** Click this to test the connection to the DHIS2 server. You will be shown a message that tells you whether mSupply was able to connect to the DHIS2 server with the credentials you have provided.
 +  * **Send errors to this email address textbox:** All errors will be sent to theis email address. Enter multiple email addresses by separating them with a semicolon ('';'').
   * **Data set ID:** Enter the ID of the dataset in DHIS2 that you want to push the data to.   * **Data set ID:** Enter the ID of the dataset in DHIS2 that you want to push the data to.
   * **Period format:** Enter the format to send the period information to DHIS2. Something like "YYYYMM", where YYYY represents the year, MM represents the month and DD represents the day.   * **Period format:** Enter the format to send the period information to DHIS2. Something like "YYYYMM", where YYYY represents the year, MM represents the month and DD represents the day.
Line 59: Line 60:
   * **Data element ID scheme:** This tells mSupply what kind of DHIS2 item identifiers are stored in mSupply (in the place defined by the **Item field reference** section above), item codes or UIDs.   * **Data element ID scheme:** This tells mSupply what kind of DHIS2 item identifiers are stored in mSupply (in the place defined by the **Item field reference** section above), item codes or UIDs.
   * **Round off checkbox:** If checked then mSupply will round numerical data values to the nearest whole number as some DHIS2 setups only accept integers.   * **Round off checkbox:** If checked then mSupply will round numerical data values to the nearest whole number as some DHIS2 setups only accept integers.
-  * **Name field reference textbox:** +  * **Name field reference textbox:** The name of the name custom field used to store the ID of the corresponding name in DHIS2. 
-  * **Store field reference textbox:** +  * **Store field reference textbox:** The name of the store custom field used to store the ID of the corresponding store in DHIS2 
-  * **Order program ID textbox:** . **Manual pull data** button. +  * **Order program ID textbox:** Put the ID of the DHIS2 Order program used for requisitions in this field. Click the **Manual pull data** button next to this field to immediately fetch completed requisitions from DHIS2, rather than waiting for it to be done on the automatic schedule. 
-  * **Receipt program ID textbox:** . **Manual pull data** button. +  * **Receipt program ID textbox:** Put the ID of the DHIS2 Receipt program used for shipment receipts in this field. Click the **Manual pull data** button next to this field to immediately fetch completed consignments from DHIS2, rather than waiting for it do be done on the automatic schedule. 
-  * **STR program ID textbox:** . **Manual pull data** button. +  * **STR program ID textbox:** Enter the ID of the DHIS2 STR program used for storing Stock on Hand values into this field. Click on the **Manual pull data** button next to this field to immediately fetch stock on hand figures for facilities, rather than waiting for it do be done on the automatic schedule. 
-  * **RTS SOH Raw data button:** . +  * **RTS SOH Raw data button:** Click this to display the raw stock on hand data pulled from DHIS2. 
-  * **Data elements table** In this table, select the data elements that you want to pull for each mSupply item.+  * **Data elements table** In this table, select the data elements that you want to pull from DHIS2 for each mSupply item.
     * **Active column:** Check the checkbox for each data element you want to pull for an item. Click on the checkbox to toggle it on and off.     * **Active column:** Check the checkbox for each data element you want to pull for an item. Click on the checkbox to toggle it on and off.
     * **Data element column:** Read only, the name of the element the settings in this line are for.      * **Data element column:** Read only, the name of the element the settings in this line are for. 
-    * **Program data element ID column:** . +    * **Program data element ID column:** The ID of this data element in the Program. 
-    * **Program stage ID column:** . +    * **Program stage ID column:** The ID of the program stage this data element belongs to. 
-    * **Attribute ID column:** .+    * **Attribute ID column:** The ID of the attribute this data element has in the program stage.
  
 <WRAP info center round 90%> <WRAP info center round 90%>
Line 80: Line 81:
 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.  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 pull data from and send data to the DHIS2 LMIS instance. If there are any errors these will be saved in the log (see the [[admin:the_log|]] page for details).+Once configured, a scheduler will run every 5 minutes and regularly pull data from and send data to the DHIS2 LMIS instance. If there are any errors these will be saved in the log (see the [[admin:the_log|]] page for details).
  
 \\ \\
  • Last modified: 2024/10/18 08:49
  • by Gary Willetts