The EPILABO Dataflow description

Below we describe (high level) the EPILABO dataflow between the data provider and the healthdata.be platform.

Step 1. Laboratory (clinical biology) sends message “LaboratoryTestResultCB” in HL7 FHIR format from LIMS towards HD4DP v2 using API. This message contains ID’s of patient, HCO (requestor), HCP (requestor), HCO (executor), HCP (executor), sample, test …

Step 2. Laboratory staff can manually complete information of message “LaboratoryTestResultCB” provided by LIMS in HD4DP v2 using form version of the messages (optional step). This message contains ID’s of patient, HCO (requestor), HCP (requestor), HCO (executor), HCP (executor), sample, test …

Step 3. HD4DP v2 sends message “LaboratoryTestResultCB” towards HERA Integration Engine. This message contains ID’s of patient, HCO (requestor), HCP (requestor), HCO (executor), HCP (executor), sample, test …

Step 4. HERA Integration engine sends HL7 FHIR message “LaboratoryTestResultCB” towards HERA ODS. This message contains ID’s of patient, HCO (requestor), HCP (requestor), HCO (executor), HCP (executor), sample, test …

Step 5.

Step 6.

Step 7.

Step 8.

Step 9.

Step 10.

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!