Data transfer

Data transfer 

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!
koen.ponnet Wed, 09/28/2022 - 08:27

Technical guidelines

Technical guidelines

A. Content of the messages

Valuesets

  • In case the patient has a NISS or a NISS Bis number, the regular address information, date of birth and gender should not be provided.
  • In case the patient has no NISS or a NISS Bis number, a NISS should be created using the ConsultRN integration in EMD or HIS:
  • In case the patient is a minor (child), one of the parents, guardian or legal representative, should be provided as first contact person to (“FirstNamesContp1”; “LastNameContp1”; “TelephoneNumberMobileContp1”).

B. Format of the requested file

B.1. JAVASCRIPT OBJECT NOTATION (JSON)

Every requested field has to be provided also the optional fields, even when the values are missing or false. The reason is that this way every record will have the same structure. Although this is not necessary, this assures us that the field names are correctly spelled. If we do not find a field, we will know something is wrong and we can act upon this.
The structure of the record is completely flattened and this is done on purpose. This makes it easier and more transparent to load the data in a database and compare the original record with the result programmatically.

Here, you can find the link to an example of the “LaboratoryTestResult” in JSON format:

Name of the JSON message

We kindly ask you to use following names for the JSON messages:

  • RIZIVnrSender_LaboratoryTestResult_yymmddhhmmss

Points of attention

  • Multiple records can be included in a .json file.
  • All records should have exactly the same structure (missing values and ‘false’ have to be present also).

B.2. Comma-Separated Values (CSV)

Every requested field has to be provided, including the optional fields, even when the values are missing or false. The reason is that this way every record will have the same structure. In a csv containing more than 1 record this has of course be the case. This way the complete csv can be treated as one table.

Here, you can find the link to an example of the “LaboratoryTestResult” in CSV format:

Example of message “LaboratoryTestResult” in CSV format:

Name of the CSV messages

We kindly ask you to use following names for the csv files:

  • RIZIVnrSender_LaboratoryTestResult_yymmddhhmmss

Points of attention

  • A csv can contain multiple records.
  • All records should have exactly the same structure (missing values and ‘false’ have to be present also).

C. Description of the transportation methods

C.1. sFTP

You can send us the requested files directly to our SFTP server. We need you to give us information so we can set it up specifically for your organization. You can do this by sending a mail to covid19lab.healthdata@sciensano.be.

The mail has to contain:

  • Organization name
  • Email address of the person of your organization who will receive
    • the account information
    • the public key to use when authenticating
    • a document describing the connection information
    • a test file that we would like you to send to our SFTP server

Points of attention

We have to be sure that the complete file has arrived before reading the file. We propose to do this by means of another file with the same name as the file with the data but with extension ‘ok’. You have to send this ‘.ok’ file after sending the file with the data. This way we know which files are ready for integration.

  • The encoding of the file is expected to be in UTF-8.

koen.ponnet Mon, 07/10/2023 - 10:29

Software solutions

Software solutions

Software solutions for Laboratories

  • Amaron kan voor intramurale laboratoria zijn EAI inschakelen om bv HL7-ORU berichten om te zetten naar het gewenste Sciensano-bestand (met LOINC mapping indien code beschikbaar) en ook een koppeling maken die mappings van bepaalde velden naar SNOMED-CT toepast en het bericht in het juiste formaat zet en klaarzet voor verzending (of zelf verzenden, TBD per labo). Contact = Frederik Lenaerts frederik@amaron.be +32 495 46 57 73
  • Cegeka Corlabs: intramural laboratories are advised to contact the IT department of their hospital. Extramural laboratories can contact Cegeka for advice.
  • MIPS informed their clients about the possibilities to extract the necessary statistics from the GLIMS application to create the LaboratoryTestResult message. Monday 4.05.2020, additional information will be available for their clients in the helpdesk portal.
  • Moonchase lab-online: u Moonchase can provide a Lab Online plug-in allowing extraction of test results from the database and uploading them to Sciensano in the required format.
  • Molis: update will follow
  • MyBox: HealthConnect provides laboratories with software to manage their eHealthBox: Unified Messaging Module. The application has a graphical interface (MyBox) that allows users within the organization to receive and send messages, as well as create, send & receive structured eForms forms. NL / FR.
  • Nexuzhealth nv will provide the LaboratoryTestResult form both LIS UZ Leuven or (secundary) from Nexuzhealth HLI lab result server (if not possible from local LIMS of customer).
koen.ponnet Tue, 09/27/2022 - 12:12