Page Comparison

08/01:  Image AddedTISNEW-2364 - Merging, then removal of Duplicate Person Records - Round 1 DONE  - Work completed for Round 1 on Stage and testing began. Since this was a flyway script, the importance was stressed on completion of the testing on stage as this would block anything else from being released to Production in out release pipeline

DS: Has done some testing. SB: leave manager tests carried out. JH/DS/AH: re-use some of the scripts that were used during consolidation for testing on metabase for next week.

DS: Prog membership, placements and assessments - Looks good so far. 

How long more this would need? - conclude by Wed 16/01.( and  are going to test this on Wednesday afternoon)

21/09: The scripts have been run on Prod over the weekend. 

4/02: Round two will be needed. LaSE still to advise DS on what to do with the records that weren't an easy match. Chris picking this up - London may be ok but KSS need more attention

4/02: Leave manager - need to do checks for the circa 500 records to make sure that the round 2 de-duping would not leave orphaned records (as per the procedure for Round 1

01/04: 

15/04: Still awaiting for EMD, South and London.

24/06: Jen to speak to David tomorrow (25th) re queries she has found in the South. 

James to ask Gwil where has gotten to with this - returns from leave on the 1st July

08/07: David to resend file to Gwil and Jen is no longer confused   as she now understands that this part of the exercise will not remove ALL erroneous records. Work is continuing........

22/07: Ongoing, waiting for South and EMD data

02/09 EM have submitted, awaiting the South (ongoing)

14/10: Back with DS - to compare and rebuild the new list of what's been merged

• Might be useful for bringing in the Northern Ireland data into TIS (Adewale Adekoya) 

Removal of consultant data has a dependency on De-duplication work.

22/10: Dependency on the De-dupe work. Follow up with Chris after the de-dupe work has taken place. This is to identify which Consultant data belongs to which Trust so that they can have this if the trust wants.

29/10: Linked to the removal of the consultant information from TIS we also need to address the issue of the non-trainee posts. So a further piece of work needs to take place to identify and hard delete these posts. Will need to take a copy of this so that (like with the non-trainee records) we can pass this to the trusts if needed. JW to create ticket related to the deletion of posts.

19/11 - Once de-dupe is done, check the full list of People from Chris. Please review against the surviving records (IDs) on TISNEW-2057.

14/01: Wait until the testing of the de-dupe has been done on stage then carry on.- 

04/02: Awaiting on DS on testing outcome for TISNEW-2057 to prioritise TISNEW-2083. Does the script attached to 2083 has everything? 

Check with Rob about urgency of this re IG - JW to do this

01/04: 

15/04: response from Rob 'From an IG perspective - of we don't need it then we should not keep it.'

Supervisors and Leave approvers taken into account on Chris's script.

24/06: The South has undertaken a post audit and set to Inactive Consultant/non current posts which has resulted in a reduction of approx. 2000 posts

Suggestion that this is something that the other three regions can do while the Person de-dup is in the process of being completed.

Suspect most of the Consultant posts in the North and Mids and East are now inactive meaning that the majority of outstanding posts belong to KSS (possibly)

Once this has been completed for Posts they can remain as Inactive rather than undertake another unnecessary step.

22/07: Still waiting on the de-duplication work. To discuss about Supervisors after this piece of work.

01/04: Check if the FE is displaying INACTIVE values when creating site. Need to understand what the problem is. 

• Raise a ticket to get the Trust search behave as the Site Search.
•  list posted on DQ channel to be discussed.

15/04:

• Identify duplicate Sites (Site codes not unique) in Site Reference Table- 
• Identify duplicate Trusts codes in Trust reference table
• Identify association between Current Sites to Inactive Trusts
• Each Region data Lead to review on DQ channel.

24/06: Regions to act on report created by Chris. Not for immediate attention due to the current work ongoing in Local Offices.

19/08: Ongoing

07/11/2019 Similar issue raised Lynn Bradley team 

Are there any possible potential data conflict in NDW and Intrepid post fundings?

24/06: No DFT in the NW and Orthodontics in KSS. 

08/07: David to be in receipt of this info in near future - suspect for David to import  into TIS  

22/07: KSS: Nothing to be done, NW: Will be done imminently

19/08: Awaiting on NW. 

30/09: It's in progress. 

08/07: Ashley to produce a report showing any current placements are missing mandatory information so this can be added to the placements in question.

09/07:https://build.tis.nhs.uk/metabase/question/279

The last column tells you what's missing. I have limited it to placements with an end date greater than 08-07-2018 assuming the placement end date itself is not missing. It is still a large number - 4546 records 

Placements with a missing end date and the highest start date available in the database (1/03/2017):

Ola spotted that there are 56 sites which have an unknown Trust code attached to them.

Data leads have been asked to investigate the ones that belong to their region and update the unknown trust code with a known trust code where needed/possible (posted in Data Leads channel on the 3/6/2019) TISNEW-3041

24/06: 49 records still left to be looked at. 

https://build.tis.nhs.uk/metabase/question/278275

Solution could be to only get the PPT to show the placements for the past 24 months - AP to speak Ola about this.

19/08: Ongoing piece of work to tidy up data

Regions to look at when they have the time. South has completed their part. 

08/07: work ongoing

24/06: No DFT in the NW and Orthodontics in KSS. 

08/07:

David to be in receipt of this info in near future - suspect for David to import  into TIS  

22/07

: KSS: Nothing to be done, NW: Will be done imminently

19/08:

Awaiting on NW. 

 Speak to JT

30/09:

https://healtheducationengland.sharepoint.com/:x:/s/ProgrammesAnalysisTeam-MaE/ETqG9iCIN8ZJpSRZ7cGUb68BBMVNkj7bL5N2VC1ghrapUg?e=4%3arpzUBP&at=9

16/09: JT: The only one I would potentially query is vwPerson.Role, as this is a commonly used search term and ergo might benefit from an index, which can’t be added for Varchar(MAX).

I wonder if there is a data quality issue worth investigating? I find it hard to believe there is a legitimate person record with over 4000 characters in role. Ultimately, a separate PersonRole table might be the best solution (I will check with Pavel).

JH/DS: To have another look at Roles and rationalise.

Work would be required on both TIS and NDW side to change to the defined size. 

30/09: To ticket this up.

It's in progress. 

08/07: Ashley to produce a report showing any current placements are missing mandatory information so this can be added to the placements in question.

09/07:https://build.tis.nhs.uk/metabase/question/279

The last column tells you what's missing. I have limited it to placements with an end date greater than 08-07-2018 assuming the placement end date itself is not missing. It is still a large number - 4546 records 

Placements with a missing end date and the highest start date available in the database (1/03/2017):

https://build.tis.nhs.uk/metabase/question/278

Solution could be to only get the PPT to show the placements for the past 24 months - AP to speak Ola about this.

19/08: Ongoing piece of work to tidy up data

30/09:

• This is not in Assessment. 
• Ticket to be tidied up: ProgrammeCurriculum needs to include another field called ProgrammeCurriculumGMCReferenceNumber both in the FE and BE. 
• Does not need to be under Programme membership. 
• It's like a Programme number format, 6 character format alphanumeric. (non-mandatory)
• This field needs to be sent to NDW.
• To get the data from GMC via GMC Connect, to input into this field on TIS.

29/10: 

• DS: "...the list of programme codes is the best I'd get, there's no matrix of programme to curriculum."
• There are gaps for some programmes, where a GMC Curriculum Reference number could not be provided
• Why the gaps and why some regions/programmes have no such matrix to curriculum? Are they not being used/not required for GMC ARCP return for these programmes?

E&T Currencies:

Build a report which derives the currency code from data we already have on TIS

16/09: 

• Education and Training currencies to be added to TIS 
• Only Postgraduates are on TIS
• Instead of Adding a field onto TIS to be maintained by a national process and team, in the short term a report to be produced in NDW based on
  • Post information to determine if higher specialty
  • Longer term, look at TIS if needed, as finance do not really use TIS nationally.
  • Possibility of this changing in the future as well as to how this is recorded
  • to be done by the end of this month - James and Chris very keen on 

30/09: Awaiting for dental and PH and some other specialties from Rozeen. In progress... Needs to get raised with BM's re timescales.

14/10: A report is being run nationally (agreed by Jon Howes).JH to share the output. 

30/09: AR: There are users on TIS that have been setup with the incorrect roles combination.

e.g. HEE Admin and one of the other roles in (Trust Observer/Admin, Programme Observer/Admin) or user has HEE Admin and one of the Trust/Programme roles. 

• To be looked at along with the User Management enhancements
• Tidying up of roles not needed
• Look at a better way of managing roles for TIS
• IG implications

14/10: User management reviewed and stories for improving ahead of the above ticket being tackled.

Ashley Ransoo - ticket this up. 

30/09: AR: There are users on TIS that have been setup with the incorrect roles combination.

e.g. HEE Admin and one of the other roles in (Trust Observer/Admin, Programme Observer/Admin) or user has HEE Admin and one of the Trust/Programme roles. 

• To be looked at along with the User Management enhancements
• Tidying up of roles not needed
• Look at a better way of managing roles for TIS
• IG implications