The Orthopride Hip Dataflow description

Last updated: 2022-09-18 16:25

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

Step 1. Automatic data export from systems of data provider towards HD4DP v2 and prefill of forms if not complete

Step 2. Manual registration (de novo or completion) of data in form component of HD4DP v2

Step 3. Direct real time transfer of registry variables and technical ID of record from HD4DP v2 towards HD

Step 4. Transfer of patient identifiers and technical ID of record from HD4DP v2 towards eHBox messaging client of HCO (HCO UM/EM)

Step 5. Transfer of patient identifiers and technical ID of record from eHBox messaging client of HCO (HCO UM/EM) towards TTP service of eHealth

Step 6. Transfer of pseudonymized patient identifiers and technical ID of record from TTP service of eHealth towards eHBox messaging client of HD (HD UM/EM)

Step 7. Transfer of pseudonymized patient identifiers and technical ID of record from eHBox messaging client of HD (HD UM/EM) to HD Integration engine

Step 8. Join and Transfer of pseudonymized patient IDs, registry variables and technical ID of record from HD Integration engine towards Data Validation environment on DHW

Step 9. Direct real time transfer of patient identifiers, NIC-CIN variables and technical ID of record from HD4DP v2 towards NIC-CIN (optional).

This documentation is under construction. 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 send us an email 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!