Last updated: 2023-04-11 15:03
In this article we describe how to submit a MyCareNet XML for Spine Surgery.
This configuration is by default active in HD4DP v.2. 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. You can attach the XML files to the Web Service call to MyCareNet and sign the message with your eHealth P12 certificate. The XML files are ready for use, thus contain the required fields. There is no additional edit required.
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)
An example of an Spine Surgery submission XML is available here:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <RegistryRecordList> <RegistryRecord> <NIHDI>10860366052</NIHDI> <SSIN>87032710560</SSIN> <DateForRouting>2023-02-01</DateForRouting> <RegistrationCode>02042300010177</RegistrationCode> <Registry>Spine chirurgie</Registry> <Type>Notification</Type> <SubmissionDate>2023-02-27</SubmissionDate> <CareDeliveries> <CareDelivery> <BillingCode>224092-224103</BillingCode> <Occurence> <DateOfOccurence>2023-02-01</DateOfOccurence> <ImplantCodes> <NotificationCode>000017803953</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 email@example.com 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!