MyCareNet XML Export for ZEPHYR - Primo-implantation

Last updated: 2023-09-13 14:03

In this article we describe how to submit a MyCareNet XML for ZEPHYR - Primo-implantation.


This configuration is by default active in HD4DP v2.

The files can be found on the SFTP share inside the directory /nippin/valid. The XML files can be downloaded with an SFTP client of your choice. The XML files you download can be sent with the MyCareNet component available in your organization.

Structure of the XML filename

The XML filename is a combination of different values: RIZIVnumber-random_uuid-inputReference.xml. The files are ready for use, thus contain the required fields. No additional editing is required.

How to link an XML file within the Nippin database

You can attach the XML files to the Web Service call to MyCareNet and sign the message with your eHealth P12 certificate. If you would like to search inside the Nippin database for the correct entry you can filter with the following query for the correct entries:

 select count(*) from nippin_message where input_reference = '<inputReference>' and identification_value = '<RIZIVnumber>';

  • Example: 11111130-6d59369f-11c8-4636-929a-86449f4dde3b-1701979200058.xml
    • RIZIVnumber: 11111130
    • random_uuid: 6d59369f-11c8-4636-929a-86449f4dde3b
    • inputReference: 1701979200058

SFTP Connection

The server name and the SFTP credentials can be requested via our Service Portal 

  • Server: IP of HD4DP v.2 server  
  • Port: 22  
  • Username: (your SFTP credentials)  
  • Password: (your SFTP credentials) 
  • Path: /data/localsftp/upload/nippin (Upload is the home directory of the sftp user)  

Example XML

An example file of a ZEPHYR - Primo-implantation submission XML:

This documentation is being updated regularly. We try to provide as correct, complete and clear as possible information on these pages. Nevertheless, if you see anything in the documentation that is not correct, does not match your experience or requires further clarification, please create a request (type : request for information) via our portal ( or send us an e-mail via to report this documentation issue. Please, do not forget to mention the URL or web address of the page with the documentation issue. We will then adjust the documentation as soon as possible. Thank you!