Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
integration:dhis2_lmis_integration [2024/10/18 09:34] – Gary Willetts | integration: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 81: | Line 81: | ||
If the connection is not successful you will see a red " | If the connection is not successful you will see a red " | ||
- | 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: | + | Once configured, a scheduler will run every 5 minutes |
\\ | \\ |