HD4DP v2 MyCareNet

HD4DP v.2 permits the administrative obligation of reporting to the insurance institutions. The limited necessary data are sent via HD4DP v2 to the MyCarenet interface of the National Intermutualistic College (NIC). This transmission of nominative data occurs in parallel with the transmission of pseudonymized data to the healthdata.be platform.

Two options are available to enable the transmission of data from HD4DP v.2 to the National Intermutualistic College (NIC):

Only for the following DCDs a message will be sent to MyCareNet:

'DEFIB_ELECT',
'DEFIB_PRIM_IMPLT',
'DEFIB_REPL',
'MVO_IMP',
'OP_HIP_PRIM_IMPLT',
'OP_HIP_RESEC',
'OP_HIP_REVIS',
'OP_KNEE_PRIM_IMPLT',
'OP_KNEE_RESEC',
'OP_KNEE_REVIS',
'OP_MP_PRIM_IMPLT',
'OP_MP_RESEC',
'OP_MP_REVIS',
'PITTER',
'QERMID_Pacemaker_ Remplacement',
'QERMID_Pacemaker_Ajout_remplacement_electrode',
'QERMID_Pacemaker_Primo_implantation',
'SPIN_SURG',
'TAVI_IMPLT',
'ZEPHYR_PRIM_IMPLT',
'ZEPHYR_REPLAC',

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 support ticket via our portal (https://healthdatabe.atlassian.net/servicedesk/customer/portals) or send us an e-mail via support.healthdata@sciensano.be 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!

manager Mon, 09/23/2024 - 11:57

Option 1: MyCareNet XML Export for [DCD name]

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)

johanvanbussel Fri, 05/24/2024 - 17:18

Option 2: MyCareNet integration in HD4DP v2

Whitelisting URL's

The following URLs must be whitelisted to communicate with MyCareNet and E-health. Without a direct connection from HD4DP v.2 server to these URLs, a registration to MyCareNet will not work.

https://prod.mycarenet.be:9443/*

https://services.ehealth.fgov.be/*

https://tsl.ehealth.fgov.be/*

https://servicelist.ehealth.fgov.be/*

http://ocsp-eh-ptpki.confidens.zetes.com/*

http://crl-eh-ptpki.confidens.zetes.com/*

How to upload a certificate using SSP

You can find the documentation describing the procedure to upload a certificate via this link: Add and manage certificates

Please make sure to inform Servicedesk when you upload a certificate in the Self-Service Portal application as there is one last action that needs to be performed on their end to enable MyCareNet flow.

johanvanbussel Tue, 03/11/2025 - 10:15

Nippin validation

Scope

To support the Data Provider with the validation of the MyCarenet message, every night a CSV file is generated with the latest MyCareNet message information.

NexuzHealth hospitals are not able to validate this.

Requirements

The data provider needs access to the sftp folder of HD4DP2.0.

Request the credentials if you did not receive this in our support portal.

Server: IP of HD4DP v. 2 server

Username: (your SFTP credentials)

Password: (your SFTP credentials)

Path: /data/localsftp/upload (home directory of the user)

Output

Example output CSV file:

head -n2 output.csv
localdwh_id,localdwh_created_on,localdwh_registration_code,localdwh_register,nippin_message,nippin_interface_type,nippin_status,nippin_created_on,nippin_payload_after_validation,nippin_postresponse_tack_reference,result
16686,2024-06-18T06:38:01.449820+00:00,206.24.000214.88,OP_KNEE_PRIM_IMPLT,208f3aab-c97a-4ea0-aa70-6cba5e23ce72,REST,SENT,2024-06-18T06:38:01.938909+00:00,,11b7aeb0-4e41-496c-a9f0-8e506744b064,urn:nip:tack:result:major:success,valid

Interface type

Interface type	Info
FILE_SYSTEM	HD4DP2.0 is configured with option 1 (DP will deliver the xml files to mycarenet)
REST	HD4DP2.0 is configured with option 2 (HD4DP2.0 will deliver the xml files to mycarenet)

Status

Status	Info
valid	A valid status means the payload looks okay and the nippin_status is SENT or TO_SEND.
invalid	An invalid status means the payload is wrong and the nippin_status is INVALID or ARCHIVED. The issue needs to be investigated by healthdata.be. Please create a ticket in our support portal.
not_found	No nippin message was created for the localdwh message. The issue needs to be investigated by healthdata.be. Please create a ticket in our support portal.
not_sent	This status is used when a payload is not able to be delivered to MyCareNet. The communication problem needs to be resolved and the messages need to be resend to MyCareNet. Please create a ticket in our support portal.

jeroen.maelbrancke Fri, 03/28/2025 - 09:48