Description du flux de données du projet EPILABO

Dernière mise à jour: 2023-04-26 13:50

Nous décrivons ci-dessous (à un niveau élevé) le flux de données du projet EPILABO entre le fournisseur de données et la plateforme healthdata.be.

Step 1. Laboratory (clinical biology) sends message “LaboratoryTestResultCB” 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 message “LaboratoryTestResultCB” towards HERA ODS. This message contains ID’s of patient, HCO (requestor), HCP (requestor), HCO (executor), HCP (executor), sample, test …

Step 5. HERA ODS sends messages “LaboratoryTestResultCB” towards HD Integration engine. These message contains a unique technical key, ID’s of HCO (requestor), HCP (requestor), HCO (executor), HCP (executor), sample, WGS test, … (no-NISS of patient).

Step 6. HERA ODS sends unique technical key and NISS of patient included in messages “LaboratoryTestResultCB” towards HERA UM / EM. These messages do not include any business data.

Step 7. HERA UM / EM sends unique technical key and NISS of patient included in messages “LaboratoryTestResultCB” towards eHealth TTP-service. These messages do not include any business data.

Step 8. eHealth TTP-service sends unique technical key and PSEUDO-NISS of patient included in messages “LaboratoryTestResultCB” towards HD UM/EM. These messages do not include any business data.

Step 9. HD UM/EM sends unique technical key and PSEUDO-NISS of patient included in messages “LaboratoryTestResultCB” towards HD Integration engine. These messages do not include any business data.

Step 10. HD Integration engine consolidates technical key, PSEUDO-NISS and business data from “LaboratoryTestResultCB” and result of Primary BioIT analyses and sends it towards HD Staging environment (HD DWH).

Step 11. Further processing of “LaboratoryTestResultCB” on HD DWH including publication into healthstat.be and fair.healthdata.be portal.

Cette documentation est encore en construction. Nous essayons de présenter les informations aussi correctes, complètes et aussi claires que possible. Cependant, si vous voyez un élément dans la documentation qui est incorrect, ne correspond pas à votre expérience ou nécessite des éclaircissements supplémentaires, veuillez créer ticket support via notre portail (https://healthdatabe.atlassian.net/servicedesk/customer/portals) ou nous envoyer un e-mail à support.healthdata@sciensano.be pour signaler ce problème de documentation. N'oubliez pas d'inclure l'URL ou l'adresse Web de la page avec le problème de documentation. Nous ajusterons ensuite la documentation. Merci!