10/06/2019

Discussion/Action

#	Discussion/Action	Responsible	Outcome	Status
1	Resolve Duplicates - TISDEV-4841: Resolve the duplicate invalid GMC numbers, such as 'Retired,' and make them 'UNKNOWN'	Data leads	First discussed on DQ on 04/06: 08/01: TISNEW-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.( Sue Barrand (Unlicensed) , David Short (Unlicensed) and James Harris are going to test this on Wednesday afternoon) 21/09: The scripts have been run on Prod over the weekend. David Short (Unlicensed) has taken extracts of the data on Friday afternoon ahead of the scripts being run. 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: David Short (Unlicensed) to provide the list of Id's/template for the second round of duplication (second strongest match rule). To send the list out to all regions be checked. Jen would have done for the South - to be checked? 15/04: Still awaiting for EMD, South and London.
2	Identification and removal of Consultant data on TIS	All	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.- Chris Norman (Unlicensed) 04/02: Chris Norman (Unlicensed) , David Short (Unlicensed) : 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: Joanne Watson (Unlicensed) to check with Rob/Ben. 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.
4	Programmes with no Posts or People Posts with no Programmes Current Programmes With No People or Posts Attached RUN 21-01-2019.xlsx	Data Leads	JH 31/01/2019: From a conversation around the Placement Planner Tool, it was brought up that there were current Programmes that didn't have any People or Posts attached. It seemed like this should be something we discuss on the data leads call. From first thought it would seem we should inactivate the programmes. This spreadsheet lists those Programmes. There is a tab for programmes with both no people or posts attached, one for just no posts and one for just no people. AR 25/01: Whilst discussing the Bulk Post Upload requirements, it became apparent that 'Programme name' when creating Posts is not a mandatory field on TIS. There are Posts with no programmes at the moment. The consensus was to make this field mandatory when creating posts, however, there will need to be a tidying up exercise by the data leads regarding those posts. Tableau - Alice and James (Intrepid/TIS views for data audit will show posts with no programme attached) 04/02: Data leads/local offices to de-activate those that can be de-activated and remainder to be left. Not an urgent piece of work. 04/02: Data leads to check the report JH sent showing the placements with no start or end date or both approx. 530. 01/04: Data leads to check the spreadsheet - check with James Harris on the spreadsheet. 15/04:
5	TISNEW-2378 suggests that some Trust users may be attached to inactive trusts.		Is this an issue and who would like to take this piece of work on? 04/02: JH to create report showing the users who are attached to inactive trusts and share with group for decision on how to fix this if needed. JH found 16 users who are attached to an inactive Trust - Scarborough & North East Yorkshire Healthcare NHS Trust, Rotherham Doncaster and South Humber Mental Health NHS Foundation Trust. Kay and Helan at Y&H to be asked if the users Current trust is the right trust by JW 01/04: Joanne Watson (Unlicensed) to check with Kay and Helan. 15/04: users are attached to the correct trusts on TIS FE but in the profile service and the NDW this is different. Needs more investigation but it looks like none of these trust users has logged into TIS yet. JW has a call with the North TIS Admins on the 24th to go through UM so will cover this then.
6	Trust Users creation for LaSE	Maria Kist (Unlicensed) / Chris Norman (Unlicensed)	01/04/2019: LaSE- Creation of Trust Users. What is the priority on this? The last we had was this would be required for beginning of May, which has therefore made the IMT posts ticket a higher priority than this. TISNEW-2782 - Creation of LaSE trust users DONE 01/04: Chris Norman (Unlicensed) to check with Maria. 15/04: The users have been created, however there are some users on the template which already exist and we've made sure they are against the correct trusts. (Template sent to Maria) If the passwords do need to be reset, please get back to us.
7	Internal Medicine Training (IMT) Posts Upload for LaSE	Maria Kist (Unlicensed) / Chris Norman (Unlicensed)	01/04/2019: The following ticket has been taken into our current sprint due to the urgency LaSE requires the IMT posts to be on TIS (by mid-April). However we are still awaiting for the template to be completed and sent over to the TIS development team. TISNEW-2829 - Internal Medicine Training (IMT) Posts to be uploaded on TIS for LaSE DONE 01/04: Chris Norman (Unlicensed) to check with Maria. 15/04: We've run the IMT posts upload scripts on Production. However, we've noticed there are some posts which would need to be corrected by the Local office admins on TIS or create new ones for manually. This is because the template we've been given have some NPNs which already exist on TIS. LDN/RYJ03/015/LT/001/M LDN/RT302/007/LT/001/M LDN/RT302/034/LT/001/M LDN/RQM01/003/LT/001/M LDN/RQM01/018/LT/001/M LDN/RQM01/018/LT/002/M LDN/RQM01/034/CT/001/M LDN/RQM01/035/LT/001/M
8	Sites created with Trust code. Trust codes are not unique.		01/03/2019: Tom De Salis: Cleansing the NTS data revealed the fact that 3 of our CCGs merged into a super-CCG last year, which means their sites have the wrong Trust/Trust code on TIS. This is an issue on both the Site reference table and on all the posts related to these sites. It affects around 100 sites. Do we know when the post update tool might be available to update the posts? Is it worth waiting? Would we be able to do an update on the back-end to the site reference table? AR: Site is linked to Trust via the TrustId. When creating a Site, a valid Trust Code is entered and the Trust ID is fetched from the Trust reference table to attach to the Site. However, since the Trust Code is not currently unique in the Trust reference table, the site might be linked to incorrect Trusts. E.g. Trust Code RQ3: Trust Code VTS: Are these sites linked to the correct trusts James Harris ? 01/04: Check if the FE is displaying INACTIVE values when creating site. Need to understand what the problem is. James Harris to speak to Tom de Salis/invite him to the next data leads call . Raise a ticket to get the Trust search behave as the Site Search. Chris Norman (Unlicensed) list posted on DQ channel to be discussed. 15/04: Chris Norman (Unlicensed) : 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.
9	PPT - very long placements		General discussion/info exchange about how the PPT will work in relation to placements with long durations etc. 2003 to 2099! 01/04: Edge case. Ongoing Data quality.	CLOSE
10	Post Fundings - Bulk		01/04: In current Sprint. - DONE	CLOSE
11	Add Approvers Button on Intrepid		01/04: Reported by the South: Tickets have been raised through support. Add leave approvers to Posts on Intrepid - Not having Read/Write access to the button. However, looks fine on TIS in terms of the Post Owner. To check with John Thompson 15/04: Meeting took place on Friday to discuss. Linked to #12 below. This is the outcome of 12.
12	Owners of posts (local office) not going into Intrepid as they have a different set of ref data which means leave manager doesn't work on newly created sites	AP/JH/All	15/04: To discuss impacts. To find out what the issue is - Alistair Pringle (Unlicensed) / Ashley Ransoo Raise a ticket to investigate. Priority 1/2 - Leave manager and LM Plus affected.
13	Funding Body	All	15/04: Agreement to retain the Funding Body field in TIS. Data leads to come up with a list of criteria to autopopulate this field? For discussion Ticket to be created following this exercise. Take the discussion to DQ channel. James Harris to summarise the criteria on the channel.
14	Unknown trust codes linked to Sites	Data leads	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