HD4DP v2 MyCareNet

HD4DP v2 MyCareNet

HD4DP v.2 permits the administrative obligation of reporting to the insurance institutions. The limited necessary data are sent via HD4DP v.2 to the MyCareNet interface of the National Intermutual 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 data transmission from HD4DP v.2 to the National Intermutualist College:

Please read this documentation before its project specific use.

The study project Orthopride Total femur consists of three sections or DCD's: 

  • Primo-implantation
  • Revision and 
  • Resection.

On the following pages we explain how to submit an Orthopride Total femur MyCareNet XML for each section.

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 (https://sciensano.service-now.com/sp) 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 Thu, 08/10/2023 - 12:17

MyCareNet XML Export for Orthopride Total femur

MyCareNet XML Export for Orthopride Total femur Bart.Servaes Wed, 06/14/2023 - 18:43

MyCareNet XML Export for Orthopride Total femur - Primo implantation

MyCareNet XML Export for Orthopride Total femur - Primo implantation

In this article we describe how to submit a MyCareNet XML for Orthopride Total femur Primo implantation.

Flow

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 Orthopride Total Femur - Primo-implantation submission XML:

<RegistryRecordList>
	<RegistryRecord>
		<NIHDI>10220853000</NIHDI>
		<SSIN>84031535312</SSIN>
		<DateForRouting>2023-04-02</DateForRouting>
		<RegistrationCode>212.23.000001.43</RegistrationCode>
		<Registry>OP_MP_PRIM_IMPLT</Registry>
		<Type>NI0001</Type>
		<SubmissionDate>2023-09-06</SubmissionDate>
		<CareDeliveries>
			<CareDelivery>
				<Occurence>
					<DateOfOccurence>2023-04-02</DateOfOccurence>
					<ImplantCodes>
						<NotificationCode>000017811475</NotificationCode>
					</ImplantCodes>
				</Occurence>
			</CareDelivery>
		</CareDeliveries>
	</RegistryRecord>
</RegistryRecordList>
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 (https://sciensano.service-now.com/sp) 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!

piotr.brzyski Tue, 09/12/2023 - 17:44

MyCareNet XML Export for Orthopride Total femur - Revision

MyCareNet XML Export for Orthopride Total femur - Revision

In this article we describe how to submit a MyCareNet XML for Orthopride - Total femur - Revision.

Flow

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 Orthopride Total Femur - Revision submission XML:

<RegistryRecordList>
	<RegistryRecord>
		<NIHDI>10220853000</NIHDI>
		<SSIN>84031535312</SSIN>
		<DateForRouting>2023-04-02</DateForRouting>
		<RegistrationCode>213.23.000001.27</RegistrationCode>
		<Registry>OP_MP_REVIS</Registry>
		<Type>NI0001</Type>
		<SubmissionDate>2023-09-06</SubmissionDate>
		<CareDeliveries>
			<CareDelivery>
				<Occurence>
					<DateOfOccurence>2023-04-02</DateOfOccurence>
					<ImplantCodes>
						<NotificationCode>000017811475</NotificationCode>
					</ImplantCodes>
				</Occurence>
			</CareDelivery>
		</CareDeliveries>
	</RegistryRecord>
</RegistryRecordList>
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 (https://sciensano.service-now.com/sp) 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!

piotr.brzyski Tue, 09/12/2023 - 17:45

MyCareNet XML Export for Orthopride Total femur - Resection

MyCareNet XML Export for Orthopride Total femur - Resection

In this article we describe how to submit a MyCareNet XML for Orthopride - Total femur - Resection.

Flow

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 Orthopride Total Femur - Resection submission XML:

<RegistryRecordList>
	<RegistryRecord>
		<NIHDI>10220853000</NIHDI>
		<SSIN>84031535312</SSIN>
		<DateForRouting>2023-04-02</DateForRouting>
		<RegistrationCode>214.23.000001.11</RegistrationCode>
		<Registry>OP_MP_RESEC</Registry>
		<Type>NI0001</Type>
		<SubmissionDate>2023-09-06</SubmissionDate>
		<CareDeliveries>
			<CareDelivery>
				<Occurence>
					<DateOfOccurence>2023-04-02</DateOfOccurence>
					<ImplantCodes>
						<NotificationCode>000017811475</NotificationCode>
					</ImplantCodes>
				</Occurence>
			</CareDelivery>
		</CareDeliveries>
	</RegistryRecord>
</RegistryRecordList>
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 (https://sciensano.service-now.com/sp) 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!

piotr.brzyski Tue, 09/12/2023 - 17:46

MyCareNet integration in HD4DP v2

MyCareNet integration in HD4DP v2
Flow

Four major actions are required in order to setup MyCareNet in HD4DP v.2:

  1. Whitelisting URLs
  2. Create certificate (ehealth_certificate.p12) with labels
  3. Upload eHealth certificate in HD4DP v.2
  4. Request credentials needed to upload the eHealth certificate

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/*

Create certificate (ehealth_certificate.p12) with labels

This part requires your organization's eHealth certificate. Create a certificate that has the name ehealth_certificate.p12 using the open source GUI KeyStore Explorer. Download and install the tool from https://keystore-explorer.org/

  1. Open your organization's eHealth certificate

2. Export both certificates as a Key Pair

3. Open KeyStore Explorer, and create a new KeyStore

4. Select the type of the new KeyStore: PKCS#12

5. In the menu bar go to Tools -> Import Key Pair

6. Select the type of key pair import required:

7. Browse the authentication certificate and fill in the Decryption Password

8. Import the authentication PKCS #12 Key Pair and give it the NIHII number as alias, ex 71001129

9. Click OK and give it a password that needs to be same for all imported certs in the P12 KeyStore

10. The Key Pair is imported Successfully

11. Repeat steps 5 to 10 for importing the serial number PKCS #12 Key Pair and give it the same serial number as alias

12. Repeat step 1 to 11 to add more NIHII-HOSPITAL P12 certificates to this KeyStore (Do not execute step 3 and 4 if you already created a new Keystore)

Example of 1 Ehealth certificate import

13. In the menu bar goto File-> Save All

14. Set the KeyStore Password and give it a password that needs to be same for all certificates

15. Click OK and save the KeyStore asehealth_certificate.p12

16. Click save and the P12 for HD4DP is created

Upload eHealth certificate in HD4DP v.2

The filename of your P12 certificate must be ehealth_certificate.p12

Server: IP of HD4DP v. 2 server

Username: (your SFTP credentials)

Password: (your SFTP credentials)

Path: /data/localsftp/upload (home directory of thesftpuser)

File: ehealth_certificate.p12

Request credentials needed to upload the eHealth certificate

The server name and the sftp credentials can be requested via our Service Portal. The password of your P12 certificate can be delivered to healthdata.be either via a secure password sharing tool of your choice or via Belnet Filesender to hd-architecture-2@sciensano.be. You can request a Belnet Filesender voucher via our Service Portal as well.

Bart.Servaes Tue, 04/04/2023 - 13:58