Skip to content

NEW pipeline step Notify-Einstein to share with Einstein the new patients details

Nicola Stoira requested to merge sphnc-404 into main
  • New architecture diagram: https://git.dcc.sib.swiss/sphn-semantic-framework/sphn-connector/-/blob/sphnc-404/api/app/static/architecture.png?ref_type=heads
  • New step Notify-Einstein that can be triggered via /Start_pipeline. It is automatically executed after the Validation step. The step can be chosen in other endpoint as well where the step parameter is available.
  • After the validation step, the patient details are stored in the new table einstein_data_sharing which mimic the one present in Einstein database.
  • The Notify-Einstein step, then takes the data available for the project marked as ready and sends it to Einstein. In case the connection fails, we wait 60 seconds and then retry. We perform a maximum of 15 retries. Logs are then written for the patients depending on the result.
  • Backup and restore adapted to export/import data stored for Einstein in Minio, but ONLY in the case the SPHN Connector does not use an external S3 for storing Einstein data. In that case we do not touch the data and assume it stays where it currently is.

Check Einstein merge requests for the changes related to Einstein. FYI @katie.kalt

Merge request reports