Revalidation, Concerns, ETL (outdated)

The act of getting data into the Revalidation and Concerns services takes place via two ETL's that run during the early hours. The following shows a high level overview of the process with more details below

There are 2 ETLs, Gmc Sync and Intrepid Reval ETL. Both ETLs are basically the same the main difference is that they will get data from different sources.

Gmc Sync extracts doctor data from the GMC via a soap request, with this data it transforms it into different things Revalidation, Concerns, Connection Discrepancy, Trainee data.

Depending on the env this doctor data will either be directly from GMC (Production) or will be from the GMC Connect mock service (which we run and maintain) 

The transformed data is then pushed to Elasticsearch. Once all the data has been pushed, the ETL triggers sync endpoints in both Reval and Concerns. This sync process looks at local data in their respective databases (Reval,Concerns DB) and updates the ES records with any data / actions occured within the Reval/Concerns app

Intrepid Reval ETL follows the same steps but it retrieves the data via SQL queries, the data is then transformed to Assessment, Trainne, Placement, Contact and Connection Discrepancy data and pushed to ES