Merger-Designated body change by GMC

• Every existing DB will be mapped to a brand new DB, and doctors will be "lifted and shifted" to new DBCs -meaning old DBCs will be invalid/return no doctors.

• That API we use will remain the same (but may need to check we're still authenticated?)

Stuff we might need to change for production:

1. In reval services, we have a hard-coded list of DBCs, we need to make a new list (I suggest we keep the old list rather than replace it for historical reasons)

2. In user management we need to create new roles/DBC codes for admins to be assigned to and ensure they are all assigned the correct new one

3. In TIS we need to bulk update all DBCs -> new DBCS and new names etc

In terms of performing a quick test on stage, we can just use the DoctorsForDB template that lives on STAGE-GREEN(?) and pass it one of the "test" New DBCs they'll provide, then do whatever validation on the list that's returned that we need.

Background : Merger of the HEE requires changes to the DB - Meeting with the operation manager from the GMS hoping we can get to a position where we can do/have testing environment

Discussion: essentially what we need in generic terms isGiven we have a mapping of oldDBC -> newDBC, where does this mapping apply, and can we maintain the oldDBC where necessary (e.g. history)My optimistic brain tells me that even though we don't have the old -> new mapping, as long as we know where it's effects will be felt, we can write migration scripts or whatever, and when the time comes just plug in the DBC mappingFor Reval it's:

• The list of DBCs we use to call GetDoctorsForDB

• The DBC role given to each admin in usermanagement

• The RO name we send along with requests that's used for authentication

And I think that's it?So we need the same kind of list for the other areas - TIS, user management etc.

Aim: Migration system -27 March and go live day to be 1st April 2023

This is the follow-up from the GMC (16 February) – Holly Chadwick holly.chadwick@gmc-uk.org → GMC Operations Manager for Revalidation

• Test at least two mergers as soon as possible (hopefully next week if that’s good for you).

• We want to make the changes on the live environment on Monday 27 March.

• We estimate minimal system outage. I’m meeting with team who will be updating the systems next week to get an estimation of how long it will take to get the new codes for you.

Excel sheet from GMC of proposed changes. Note that the DB codes are generated at the time, so these will be given for the test and the final ones will be given (we assume) on 27th March (TBC)

Planning: To make GMC aware that London has changes office address(Please raise a ticket-done)

Impact : ?Tis , revalidation(both 1 and 2), we currently do not have a DB code-

• To inform our users of changes and possible impact

• Ensure we are managing expectation of our users

• ?How we manage change and the NDW?-

Requirement : Test code to be made available by the GMC for our testing , Investigation ticket? to establish whether the Trainee product team would need to be involve?

Concerns: Change in name likely would impact our tis service , The need for notification on name change.

• How much knowledge of the change is Daniel Smith (GMC Data lead)

Stakeholders involvement : ?users of the Reval service

Process map:

EPIC Link: TIS21-4233 - Getting issue details... STATUS