Versions Compared

Version Old Version 31 New Version 32
Changes made by

Jayanta Saha

James Harris

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

  • 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?)

...

Stakeholders involvement : ?users of the Reval service

Process map:

Principles of the change of ‘Owner’ on TIS for the NHSE Merger

  • The concept of ‘Owner’ on TIS is defined as the organisational body which has current ownership of a data item and its associated records whether that record is past, current or future. The values of ‘Owner’ are defined by the Designated Body reference table on TIS.

  • With the merger into NHSE on the first of April, the Designated Body which was Health Education England will be replaced by NHSE Education and there is a one-to-one correlating organisation from Health Education England to NHSE Education, e.g. NHSE Education East of England directly correlated to what was Health Education England East of England.

  • Given the above, when the NHSE merger takes place on the 1st of April, the ‘Owner’ of the records associated with a Health Education England body will have the new ‘Owner’ of the correlating NHSE Education body, e.g. a record with the ‘Owner’ of Health Education England East of England will now have the ‘Owner’ of NHSE Education East of England. This will apply to all associated records relating to that Health Education England body whether past, current or future.

  • The above principle represents the definition of a data ‘Owner’. Furthermore, it is not possible for Health Education England, its related bodies and its users to be the owner of data items or records on TIS whether past, current or future after the 1st of April as Health Education England as an organisation will no longer exist as an organisation. It also allows the transition to be enacted with the least amount of risk and complication.

EPIC Link:

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4233

...

Service

Tasks/

Ticket(s)

Revalidation

  • Awaiting to receive new/modified Designated body name, code and RO details from GMC on stage.

  • Test new DBC by CURLing from STAGE-GREEN/BLUE

  • Add the new DBCs to parameter store to map to the Recommendation

  • Add the new DBCs to TIS-GMC-Client service

  • Add the new DBCs to tis-revalidation-connection service (probably parameter store like recommendations)

  • ALSO: For Revalidation API calls to work, the admin needs to have the correct DBC assigned in usermanagement/profile service And the RO for that DBC needs to be correct (wherever that comes from), needs a full sync from TIS

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4234

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4235

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4236

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4239

Jira Legacy
serverSystem JIRA
serverId4c843cd5-e5a9-329d-ae88-66091fcfe3c7
keyTIS21-4240

Legacy Revalidation

  • Find the location where we need to accommodate the new DBC changes

  • Can we use this as an opportunity to close down old reval? need to ask users

TIS

  1. TIS-Reference: update reference.DBC table

  2. TIS-Profile: update auth.UserDesignatedBody table

  3. TIS-TCS:

    1. update tcs.Programme , tcs.Post table

    2. update tcs.PersonOwner table by PersonOwnerRebuildJob in Sync service

    3. update class DesignatedBodyMapper

User Management

Should be okay when db tables of reference and profile are updated.

Needs verification and investigation to see the DBCs reference elsewhere.

TSS

NDW

Table structures should not be affected.

Needs verification.

  • Speak to the NDW Team about potential impact

    • Initial conversation with John Thompson on 17/02/23. A wider meeting with NDW Team taking place 23/02/2023.

  • Coordinate with NDW of potential comms to regions and other downstream users of TIS data

ESR

Further investigation on how ESR communicate across the ?changes

Hicom Leave Manager

  • Update TIS-Accent ETL to use or include the new Owner names

  • Confirm with Hicom the impact on their ETL and Accent Leave Manager system changing DBCs/Owners would have and identify mitigating actions

NDW-Tableau

  • Identify scripts in the NDW which are or are a dependency for Tableau data sources which use DBC/Owner to extract relevant data

  • Identify Tableau workbooks which use DBC/Owner to group, filter, etc

...