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:
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)
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
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
Aim: Migration system -27 March and go live day to be 1st April 2023
Planning:
Impact : ?Tis , revalidation(both 1 and 2), we currently do not have a DB code-
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?
Awaiting licence
Concerns: Change in name likely would impact our tis service , The need for notification on name change
Process map:
Add Comment