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: 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. 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: 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. 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 | |||||||||
| 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.- 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: 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. 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. | On hold until Point 1 has been completed to the group's satisfaction for People area | ||||||||
| 3 |
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 on the spreadsheet.24/06: JH to rerun to see what programmes/posts are still an issue. | |||||||||
| 4 | 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: 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. | CLOSED | |||||||||
| 5 | Trust Users creation for LaSE | / | 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.
01/04: 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. | CLOSED | ||||||||
| 6 | Internal Medicine Training (IMT) Posts Upload for LaSE | / | 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.
01/04: 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 | CLOSED | ||||||||
| 7 | 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.
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 ?
01/04: Check if the FE is displaying INACTIVE values when creating site. Need to understand what the problem is. to speak to Tom de Salis/invite him to the next data leads call .
15/04:
24/06: Regions to act on report created by Chris. Not for immediate attention due to the current work ongoing in Local Offices. | ||||||||||
| 8 | 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 15/04: Meeting took place on Friday to discuss. Linked to #9 below. This is the outcome of 9. | Closed - as point 9 is the outcome/ | |||||||||
| 9 | 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 - /Raise a ticket to investigate. Priority 1/2 - Leave manager and LM Plus affected.
| |||||||||
| 10 | 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. to summarise the criteria on the channel. 24/06: Data leads have agreed and approved the logic. Ticket to be raised (and ensure that part of the function allows manual override of the auto-populated field) | |||||||||
| 11 | 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 24/06: 49 records still left to be looked at. https://build.tis.nhs.uk/metabase/question/275 Regions to look at when they have the time. South has completed their part. | |||||||||
| 12 | Potential data conflict in NDW between Funding Body (from Post on Intrepid) and Funding Organisation (from Post Funding on Intrepid) | Data leads | 24/06: Issue is that on TIS we have a Funding Body field from which the info is NOT getting into the NDW. However..................in the NDW there are two legacy fields from Intrepid which are Funding Body (from Post on Intrepid) and Funding Organisation (from Post Funding on Intrepid). Very big potential for conflicting/incorrect data being reported on from the NDW. Need to consider what the solution could be and report back in the next call. | |||||||||
| 13 | Erroneous Assessment records to be removed from TIS FE (ticket to be raised) | Data Leads and AP | 24/06: AP has received an email from EM and WM. POs to check if this affects other local offices on Teams 01/07: JW posted request to other local offices to provide the Assessment IDs of any assessments they wish to have deleted. This info is to be provided by Monday 22nd July and will be added to the ticket TISNEW-3121 | |||||||||
| 14 | Dental data on TIS | All | 24/06: No DFT in the NW and Orthodontics in KSS. To revisit |
...