<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://docs.msupply.org.nz/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/feed.php">
        <title>mSupply documentation wiki</title>
        <description></description>
        <link>https://docs.msupply.org.nz/</link>
        <image rdf:resource="https://docs.msupply.org.nz/_media/wiki:logo.png" />
       <dc:date>2026-09-17T07:01:59+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://docs.msupply.org.nz/other_stuff:invoice_authorization"/>
                <rdf:li rdf:resource="https://docs.msupply.org.nz/integration:coms"/>
                <rdf:li rdf:resource="https://docs.msupply.org.nz/?image=integration%3Apasted%3A20260908-155318.png&amp;ns=integration%3Apasted&amp;do=media"/>
                <rdf:li rdf:resource="https://docs.msupply.org.nz/integration:nhlmis"/>
                <rdf:li rdf:resource="https://docs.msupply.org.nz/integration:siglofa"/>
                <rdf:li rdf:resource="https://docs.msupply.org.nz/integration:ivedix"/>
                <rdf:li rdf:resource="https://docs.msupply.org.nz/integration:hl7_integration"/>
                <rdf:li rdf:resource="https://docs.msupply.org.nz/faq:label-printer-via-windows-driver"/>
                <rdf:li rdf:resource="https://docs.msupply.org.nz/?image=troubleshooting%3Aujser_login_ok_button_error_2026-08-19-16-14-13.png&amp;ns=troubleshooting&amp;do=media"/>
                <rdf:li rdf:resource="https://docs.msupply.org.nz/?image=troubleshooting%3Auser_login_error_2026-08-19-16-50-42.png&amp;ns=troubleshooting&amp;do=media"/>
                <rdf:li rdf:resource="https://docs.msupply.org.nz/?image=troubleshooting%3Aerror_in_file_import_.png&amp;ns=troubleshooting&amp;do=media"/>
                <rdf:li rdf:resource="https://docs.msupply.org.nz/?image=faq%3Apasted%3A20260731-034326.png&amp;ns=faq%3Apasted&amp;do=media"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://docs.msupply.org.nz/_media/wiki:logo.png">
        <title>mSupply documentation wiki</title>
        <link>https://docs.msupply.org.nz/</link>
        <url>https://docs.msupply.org.nz/_media/wiki:logo.png</url>
    </image>
    <item rdf:about="https://docs.msupply.org.nz/other_stuff:invoice_authorization">
        <dc:format>text/html</dc:format>
        <dc:date>2026-09-08T22:14:03+00:00</dc:date>
        <dc:creator>Mark Glover (mark.g@undisclosed.example.com)</dc:creator>
        <title>26.14. Authorisation - [Customer invoice authorisation] </title>
        <link>https://docs.msupply.org.nz/other_stuff:invoice_authorization</link>
        <description>26.14. Authorisation

Sometimes it is important that certain critical processes are not carried out until they have been authorised.  mSupply allows authorisation to be set according to local needs for:

	*  Purchase orders
	*  Goods receipt notes
	*  Supplier invoices
	*  Customer invoices

Response Requisitions can be authorised using the remote authurisation app. See the</description>
    </item>
    <item rdf:about="https://docs.msupply.org.nz/integration:coms">
        <dc:format>text/html</dc:format>
        <dc:date>2026-09-08T16:03:31+00:00</dc:date>
        <dc:creator>Gary Willetts (gary@undisclosed.example.com)</dc:creator>
        <title>23.08. COMS integration</title>
        <link>https://docs.msupply.org.nz/integration:coms</link>
        <description>23.08. COMS integration

The COMS is a control tower system, introduced to Nigeria by Chemonics. It controls the movements of stock around many facilities across a few 3PLs (third part logistics providers).

The tower gathers report files (in csv format) from all the 3PLs every night. It uses the information provided to decide who gets what stock and when. Stock movements are sent by shipment file (again in csv format) as required.</description>
    </item>
    <item rdf:about="https://docs.msupply.org.nz/?image=integration%3Apasted%3A20260908-155318.png&amp;ns=integration%3Apasted&amp;do=media">
        <dc:format>text/html</dc:format>
        <dc:date>2026-09-08T15:53:18+00:00</dc:date>
        <dc:creator>Gary Willetts (gary@undisclosed.example.com)</dc:creator>
        <title>20260908-155318.png - created</title>
        <link>https://docs.msupply.org.nz/?image=integration%3Apasted%3A20260908-155318.png&amp;ns=integration%3Apasted&amp;do=media</link>
        <description>&lt;img src=&quot;https://docs.msupply.org.nz/_media/integration:pasted:20260908-155318.png?w=500&amp;amp;h=500&amp;amp;tok=570eba&quot; alt=&quot;20260908-155318.png&quot; loading=&quot;lazy&quot; width=&quot;500&quot; height=&quot;500&quot; /&gt;</description>
    </item>
    <item rdf:about="https://docs.msupply.org.nz/integration:nhlmis">
        <dc:format>text/html</dc:format>
        <dc:date>2026-09-08T15:47:05+00:00</dc:date>
        <dc:creator>Gary Willetts (gary@undisclosed.example.com)</dc:creator>
        <title>23.07. NHLMIS integration - [Stock lines] </title>
        <link>https://docs.msupply.org.nz/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/integration:siglofa">
        <dc:format>text/html</dc:format>
        <dc:date>2026-09-08T15:46:01+00:00</dc:date>
        <dc:creator>Gary Willetts (gary@undisclosed.example.com)</dc:creator>
        <title>23.11. Siglofa integration</title>
        <link>https://docs.msupply.org.nz/integration:siglofa</link>
        <description>23.11. 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>
    <item rdf:about="https://docs.msupply.org.nz/integration:ivedix">
        <dc:format>text/html</dc:format>
        <dc:date>2026-09-08T15:45:51+00:00</dc:date>
        <dc:creator>Gary Willetts (gary@undisclosed.example.com)</dc:creator>
        <title>23.10. iVEDiX integration</title>
        <link>https://docs.msupply.org.nz/integration:ivedix</link>
        <description>23.10. 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/integration:hl7_integration">
        <dc:format>text/html</dc:format>
        <dc:date>2026-09-08T15:45:27+00:00</dc:date>
        <dc:creator>Gary Willetts (gary@undisclosed.example.com)</dc:creator>
        <title>23.09. HL7 and Tamanu/Patis Plus integration</title>
        <link>https://docs.msupply.org.nz/integration:hl7_integration</link>
        <description>23.09. 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/faq:label-printer-via-windows-driver">
        <dc:format>text/html</dc:format>
        <dc:date>2026-09-03T05:47:50+00:00</dc:date>
        <dc:creator>Kahn Wynyard (kahn@undisclosed.example.com)</dc:creator>
        <title>28.17. Zebra Label Printer : How to print via the windows driver - [Step 5: Print the labels] </title>
        <link>https://docs.msupply.org.nz/faq:label-printer-via-windows-driver</link>
        <description>28.17. Zebra Label Printer : How to print via the windows driver

This guide covers connecting a Zebra label printer on Windows (USB or Network) so it can be used to print labels from any mSupply reports.

mSupply normally prints directly to the Zebra Label Printer via the use of EPL command which does not require the normal print driver that is provided by the vendor.</description>
    </item>
    <item rdf:about="https://docs.msupply.org.nz/?image=troubleshooting%3Aujser_login_ok_button_error_2026-08-19-16-14-13.png&amp;ns=troubleshooting&amp;do=media">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-19T11:24:20+00:00</dc:date>
        <dc:creator>Ujwal Khatry (ujwal@undisclosed.example.com)</dc:creator>
        <title>ujser_login_ok_button_error_2026-08-19-16-14-13.png - created</title>
        <link>https://docs.msupply.org.nz/?image=troubleshooting%3Aujser_login_ok_button_error_2026-08-19-16-14-13.png&amp;ns=troubleshooting&amp;do=media</link>
        <description>&lt;img src=&quot;https://docs.msupply.org.nz/_media/troubleshooting:ujser_login_ok_button_error_2026-08-19-16-14-13.png?w=500&amp;amp;h=500&amp;amp;tok=2c6b35&quot; alt=&quot;ujser_login_ok_button_error_2026-08-19-16-14-13.png&quot; loading=&quot;lazy&quot; width=&quot;500&quot; height=&quot;500&quot; /&gt;</description>
    </item>
    <item rdf:about="https://docs.msupply.org.nz/?image=troubleshooting%3Auser_login_error_2026-08-19-16-50-42.png&amp;ns=troubleshooting&amp;do=media">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-19T11:06:41+00:00</dc:date>
        <dc:creator>Ujwal Khatry (ujwal@undisclosed.example.com)</dc:creator>
        <title>user_login_error_2026-08-19-16-50-42.png - created</title>
        <link>https://docs.msupply.org.nz/?image=troubleshooting%3Auser_login_error_2026-08-19-16-50-42.png&amp;ns=troubleshooting&amp;do=media</link>
        <description>&lt;img src=&quot;https://docs.msupply.org.nz/_media/troubleshooting:user_login_error_2026-08-19-16-50-42.png?w=500&amp;amp;h=500&amp;amp;tok=d908c3&quot; alt=&quot;user_login_error_2026-08-19-16-50-42.png&quot; loading=&quot;lazy&quot; width=&quot;500&quot; height=&quot;500&quot; /&gt;</description>
    </item>
    <item rdf:about="https://docs.msupply.org.nz/?image=troubleshooting%3Aerror_in_file_import_.png&amp;ns=troubleshooting&amp;do=media">
        <dc:format>text/html</dc:format>
        <dc:date>2026-07-31T09:03:41+00:00</dc:date>
        <dc:creator>Romisha Thapa (romisha@undisclosed.example.com)</dc:creator>
        <title>error_in_file_import_.png - created</title>
        <link>https://docs.msupply.org.nz/?image=troubleshooting%3Aerror_in_file_import_.png&amp;ns=troubleshooting&amp;do=media</link>
        <description>&lt;img src=&quot;https://docs.msupply.org.nz/_media/troubleshooting:error_in_file_import_.png?w=500&amp;amp;h=500&amp;amp;tok=36dfce&quot; alt=&quot;error_in_file_import_.png&quot; loading=&quot;lazy&quot; width=&quot;500&quot; height=&quot;500&quot; /&gt;</description>
    </item>
    <item rdf:about="https://docs.msupply.org.nz/?image=faq%3Apasted%3A20260731-034326.png&amp;ns=faq%3Apasted&amp;do=media">
        <dc:format>text/html</dc:format>
        <dc:date>2026-07-31T03:43:26+00:00</dc:date>
        <dc:creator>Kahn Wynyard (kahn@undisclosed.example.com)</dc:creator>
        <title>20260731-034326.png - created</title>
        <link>https://docs.msupply.org.nz/?image=faq%3Apasted%3A20260731-034326.png&amp;ns=faq%3Apasted&amp;do=media</link>
        <description>&lt;img src=&quot;https://docs.msupply.org.nz/_media/faq:pasted:20260731-034326.png?w=500&amp;amp;h=500&amp;amp;tok=aeb9e5&quot; alt=&quot;20260731-034326.png&quot; loading=&quot;lazy&quot; width=&quot;500&quot; height=&quot;500&quot; /&gt;</description>
    </item>
</rdf:RDF>
