/
Manually "force" update of TIS person to Reval Elasticsearch

Manually "force" update of TIS person to Reval Elasticsearch

If for some reason we need to force TIS to re-send doctor details across to reval, this is now possible using the reval.queue.trainee.update.tcs RabbitMQ queue - without having to make a change to the doctor’s details.

First simply follow the instructions here to access the RabbitMQ UI:
https://hee-tis.atlassian.net/wiki/spaces/NTCS/pages/2968944641

Under the Queues tab, find the queue reval.queue.trainee.update.tcs and click the link.

From here, you can use the publish message feature (pictured below) to pass an array of TIS Person Numbers. These will be sent to TCS, and TCS will get all the current TIS data for that doctor and send it across to Revalidation to update the record in Elasticsearch

 

Related content

Elastic Search Rebuild Sync Job
Elastic Search Rebuild Sync Job
More like this
2023/4: Q2| Admin Team Review#4(2023-09-12 to 2023-09-26)
2023/4: Q2| Admin Team Review#4(2023-09-12 to 2023-09-26)
Read with this
TIS Change Data Capture
TIS Change Data Capture
More like this
Revalidation, Concerns, ETL (outdated)
Revalidation, Concerns, ETL (outdated)
More like this
Elastic Search Index Update Event for Connections (outdated)
Elastic Search Index Update Event for Connections (outdated)
More like this
2022-12-06 Reval recommendation AllDoctors/UnderNotice lists not updated
2022-12-06 Reval recommendation AllDoctors/UnderNotice lists not updated
More like this