<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://docs.msupply.org.nz/docs/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://docs.msupply.org.nz/docs/feed.php">
        <title>mSupply documentation wiki - integration</title>
        <description></description>
        <link>https://docs.msupply.org.nz/docs/</link>
        <image rdf:resource="https://docs.msupply.org.nz/docs/_media/wiki:logo.png" />
       <dc:date>2026-04-06T16:49:31+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://docs.msupply.org.nz/docs/integration:dhis2_integration"/>
                <rdf:li rdf:resource="https://docs.msupply.org.nz/docs/integration:dhis2_lmis_integration"/>
                <rdf:li rdf:resource="https://docs.msupply.org.nz/docs/integration:elmis_interface"/>
                <rdf:li rdf:resource="https://docs.msupply.org.nz/docs/integration:frontlinesms_integration"/>
                <rdf:li rdf:resource="https://docs.msupply.org.nz/docs/integration:hl7_integration"/>
                <rdf:li rdf:resource="https://docs.msupply.org.nz/docs/integration:ivedix"/>
                <rdf:li rdf:resource="https://docs.msupply.org.nz/docs/integration:moneyworks"/>
                <rdf:li rdf:resource="https://docs.msupply.org.nz/docs/integration:myob"/>
                <rdf:li rdf:resource="https://docs.msupply.org.nz/docs/integration:nhlmis"/>
                <rdf:li rdf:resource="https://docs.msupply.org.nz/docs/integration:siglofa"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://docs.msupply.org.nz/docs/_media/wiki:logo.png">
        <title>mSupply documentation wiki</title>
        <link>https://docs.msupply.org.nz/docs/</link>
        <url>https://docs.msupply.org.nz/docs/_media/wiki:logo.png</url>
    </image>
    <item rdf:about="https://docs.msupply.org.nz/docs/integration:dhis2_integration">
        <dc:format>text/html</dc:format>
        <dc:date>2026-02-16T14:43:30+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>23.01. DHIS2 integration</title>
        <link>https://docs.msupply.org.nz/docs/integration:dhis2_integration</link>
        <description>23.01. DHIS2 integration

DHIS2 is an open source data warehouse that can be used to store, aggregate and display health data. mSupply can push data periodically to a DHIS2 instance. Before this can happen, the data to be sent and any calculations that need to be made will need to be configured, as shown below.</description>
    </item>
    <item rdf:about="https://docs.msupply.org.nz/docs/integration:dhis2_lmis_integration">
        <dc:format>text/html</dc:format>
        <dc:date>2024-10-22T07:07:54+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>23.02. DHIS2 LMIS integration</title>
        <link>https://docs.msupply.org.nz/docs/integration:dhis2_lmis_integration</link>
        <description>23.02. DHIS2 LMIS integration

DHIS2 is an open source data warehouse that can be used to store, aggregate and display health data. It has also been modified to be used as a simple stock reporting and ordering tool at small health facilities. mSupply can interact with this functionality to receive the stock on hand reports and requisitions and create replenishment orders for the facilities based on that information. This page describes how it works and what setup must be carried out in mSupply.</description>
    </item>
    <item rdf:about="https://docs.msupply.org.nz/docs/integration:elmis_interface">
        <dc:format>text/html</dc:format>
        <dc:date>2024-10-17T11:30:58+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>23.04. mSupply eLMIS interface</title>
        <link>https://docs.msupply.org.nz/docs/integration:elmis_interface</link>
        <description>23.04. mSupply eLMIS interface

eLMIS stands for Electronic Logistics Management and Information System and is a version of OpenLMIS developed under the USAID Deliver project. mSupply has an interface for receiving orders from eLMIS and sending shipment details back to it.</description>
    </item>
    <item rdf:about="https://docs.msupply.org.nz/docs/integration:frontlinesms_integration">
        <dc:format>text/html</dc:format>
        <dc:date>2024-11-01T16:38:37+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>23.03. FrontlineSMS integration</title>
        <link>https://docs.msupply.org.nz/docs/integration:frontlinesms_integration</link>
        <description>23.03. FrontlineSMS integration

mSupply has the ability to integrate with your FrontlineSMS installation. This allows you to send your current stock levels to mSupply using an SMS (text) message from any mobile phone. This is particularly useful if, for example, you are a mobile or remote health post or dispensary which doesn&#039;t have internet access and only needs to send in information about a few items at a time.</description>
    </item>
    <item rdf:about="https://docs.msupply.org.nz/docs/integration:hl7_integration">
        <dc:format>text/html</dc:format>
        <dc:date>2025-05-07T04:10:24+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>23.08. HL7 and Tamanu/Patis Plus integration</title>
        <link>https://docs.msupply.org.nz/docs/integration:hl7_integration</link>
        <description>23.08. HL7 and Tamanu/Patis Plus integration

mSupply supports HL7 integration with HL7 compliant APIs. Currently, this is limited to retrieving information from HL7 Servers, mSupply does not send patient data.

When using mSupply Synchronisation systems, this must be configured on the central server. Data retrieved from the integration is stored on the mSupply Central Server and distributed via sync to remote sites. Data is also available via</description>
    </item>
    <item rdf:about="https://docs.msupply.org.nz/docs/integration:ivedix">
        <dc:format>text/html</dc:format>
        <dc:date>2026-01-29T13:09:55+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>23.09. iVEDiX integration</title>
        <link>https://docs.msupply.org.nz/docs/integration:ivedix</link>
        <description>23.09. iVEDiX integration

mSupply has an interface with the iVEDiX reporting API. The interface allows the automatic sending of batch and transaction information to the iVEDiX reporting platform.

Set up

Preferences

The preferences that define how this interface works are managed on the</description>
    </item>
    <item rdf:about="https://docs.msupply.org.nz/docs/integration:moneyworks">
        <dc:format>text/html</dc:format>
        <dc:date>2024-10-17T11:31:08+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>23.05. Moneyworks integration</title>
        <link>https://docs.msupply.org.nz/docs/integration:moneyworks</link>
        <description>23.05. Moneyworks integration

For information regarding exporting date to the accounting software Moneyworks please refer to the 17.20. Exporting invoices to Moneyworks section.





    Previous:  23.04. mSupply eLMIS interface | | Next: 23.06. MYOB</description>
    </item>
    <item rdf:about="https://docs.msupply.org.nz/docs/integration:myob">
        <dc:format>text/html</dc:format>
        <dc:date>2024-10-17T11:31:23+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>23.06. MYOB</title>
        <link>https://docs.msupply.org.nz/docs/integration:myob</link>
        <description>23.06. MYOB

For information regarding exporting date to the accounting software MYOB please refer to the 17.21. Exporting to MYOB section.





    Previous:  23.05. Moneyworks integration | | Next: 23.07. NHLMIS integration</description>
    </item>
    <item rdf:about="https://docs.msupply.org.nz/docs/integration:nhlmis">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-06T12:10:04+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>23.07. NHLMIS integration</title>
        <link>https://docs.msupply.org.nz/docs/integration:nhlmis</link>
        <description>23.07. NHLMIS integration

Before you turn on the NHLMIS integration two important setup steps must be taken:

	*  All store, item, customer and supplier codes must match those used in NHLMIS. If this step is not taken;
		*  stock data you send will be rejected by NHLMIS because the items the stock belongs to will not be recognised</description>
    </item>
    <item rdf:about="https://docs.msupply.org.nz/docs/integration:siglofa">
        <dc:format>text/html</dc:format>
        <dc:date>2025-05-15T04:05:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>23.10. Siglofa integration</title>
        <link>https://docs.msupply.org.nz/docs/integration:siglofa</link>
        <description>23.10. Siglofa integration

mSupply has an interface with Siglofa, a variant of OpenLMIS.

Settings

Choose File &gt; Preferences from the menus and click on the Siglofa tab on the left hand side:



	*  Use Siglofa integration: if checked then the other fields will be unlocked and mSupply will do what is described in the</description>
    </item>
</rdf:RDF>
