...
- Calls the GetDoctorsForDB method on the GMC API to retrieve basic Doctor records. (GMC Revalidation API is a SOAP API provided by the GMC.)
- The basic record includes GMC ID,
Firstname, Surname,various GMC specific dates and status (including Sanction - a flag to highlight a doctor's licence has a sanction against it.) (we ignore the GMC's Firstname and Surname in preference to the TIS one) - It uses the Revalidation service (Swagger definition of the Revalidation Service) to check whether the GMC ID exists in TIS which uses the Profile service to create a TISId in its Traineeprofile table if not.
(Sunil checking - we suspect it might go directly to the Profile service to get a current TISId or create one if the GMC ID isn't present in the Traineeprofile table) - It then writes the basic record for all doctors to the Revalidation ES index (directly or via the Revalidation service - think directly)
...
It uses the GMC ID stored in ( the Profile service TraineeProfile / Trainee ES index ?) to identify the Person record (Person.Id) in TCS
It then retrieves the Person and Assessment data from the TCS and Assessment services and directly updates the appropriate Revalidation ES indexes
...
Note: Revalidation was developed before TCS and wasn't refactored as part of TCS, which is why it identifies Trainees by GMC ID and a Trainee.TISid in the Profile service but isn't more cleanly integrated into TCS.Person. This is a clear area to refactor as apart of a wider Revalidation service rework.
Revalidation (UI + Service)
Sumary
An Angular 1.x UI app and a springboot application presenting a RESTful API that provides the endpoints to support the Revalidation UI. Combined they enable HEE to review the data on Trainee Doctors due to be Revalidated, make recommendations regarding a Revalidation and submit these to the GMC.