BEFORE 27th

1. Set up PRs in preparation for go-live

Revalidation (New/current)

1. Jira Legacy
   server System JIRA serverId 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 key TIS21-4235

   - see subtasks

2. Jira Legacy
   server System JIRA serverId 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 key TIS21-4239

   - see subtasks

3. ALSO (see “TIS” section) For Revalidation API calls to work:

   1. the admin needs to have the correct DBC assigned in usermanagement/profile service

   2. And the RO for that DBC needs to be correct (in User Management)

   3. Modify/Add reference “DBC” data

Revalidation (Old)

Not currently for this release plan

TIS

1. Jira Legacy
   server System JIRA serverId 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 key TIS21-4236

   - see subtasks

   1. Note: Flyway script to merge users for North Central & East London and North West London into new DBC (choose one to preserve and migrate the other for now) -

      Jira Legacy
      server System JIRA serverId 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 key TIS21-4245

2. Jira Legacy
   server System JIRA serverId 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 key TIS21-4246

   - just subtask 4250 for now

NDW

Could check reports ahead of time, but fairly confident that they’re fine.

2. Disable Reval Cron Jobs Temporarily from the 24th onwards

Set the following Parameter Store values to “-” and force redeployment of recommendations service in ECS:

• /tis/revalidation/preprod/recommendation/cron/nightlysync

• /tis/revalidation/preprod/recommendation/cron/recommendationstatuscheck

• /tis/revalidation/prod/recommendation/cron/nightlysync

• /tis/revalidation/prod/recommendation/cron/recommendationstatuscheck

...

AFTER 27th-29th

1. Get the new codes from GMC

We need the codes soon as they are available. This will require liaising with Holly via email.

2. Update and merge PRs when new codes are received

See section 1 for PRs

3. Deploy services once PRs are merged and Terraform changes applied

1. TIS TCS

2. TIS Reference

3. TIS Profile

4. GMC-Client

5. Revalidation Recommendations

6. Revalidation FE

4. Run jobs

1. GMC doctor sync - will take some time

2. Reval ES Rebuild - will take ~ 2 hours

5. Force log in for all users

Do we need to be concerned about application users (e.g. for scheduled jobs)

6. Ask users to test

1. Can they log in

2. Can they see the doctors they should be able to see

3. Can they not see doctors they shouldn't be able to see

4. Can they submit a recommendation