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 08/07: David to resend file to Gwil and Jen is no longer confused 22/07: Ongoing, waiting for South and EMD data | |
| 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. 22/07: Still waiting on the de-duplication work. To discuss about Supervisors after this piece of work. | On hold until Point 1 has been completed to the group's satisfaction for People area |
| 3 | 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. 19/08: Ongoing | Not for immediate attention as priority in LOs is August intake and ARCPS | |
| 5 | 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.
08/07: AP to undertake mapping exercise, add to the ticket | |
| 6 | 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) 08/07: JW to raise ticket... 22/07: Check with Joanne. (applies to only newly created posts) 15/08: TISNEW-3241 (auto-population on TIS) created - data leads to review please and discuss this in relation to Point 8 below | |
| 7 | 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. 08/07: work ongoing | |
| 8 | 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. 08/07:
| |
| 9 | Erroneous Assessment records to be removed from TIS FE | 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 15/08: No other local offices responded to the offer to remove the erroneous records. Ticket TISNEW-3121 has been updated with the confirmed correct list from EM and WM supplied by Gwil. | |
| 10 | Dental data on TIS | All | 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. | |
| 11 | Missing data from placements is causing entire specialties not to render on the PPT FE | All | 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 | |
| 12 | POG placement type | Data Leads | 08/07: Check what is happening about managing all of the POG processes on the PAG Teams channels 22/07: awaiting PAG/POG decision | |
| 13 | Varchar max causing issues in Tableau | All | 08/07: Workarounds in place but would be good to know the scale of the issue - JT to provide more info when he returns from leave (again.... 22/07: Determine data type TIS is sending to NDW? awaiting for JT, post on tis-ndw channel. 19/08: Recommendations for length required. James Harris Speak to JT | |
| 14 | Associating trainers with Programmes | David | 22/07: Work out the best way of recording/reporting on Trainers on TIS. Intrepid had a ProgrammeSupervisor table. Lookup table to be considered as an interim option. 19/08: PAG discussion on Trainers data to get agreement. Raise ticket subsequently on how to record on TIS. | |
| 15 | Post Fundings Bulk Update | All | 12/08: This was discussed on Teams by Helan Raynor and others: Is there a possibly a way that Post Funding Start/End date could be updated without it adding a brand new funding row? This way when we have to inactivate a post we can do this via bulk upload without having to individually going into each post in TIS. 19/08: AR/AP: The whole 'inactive' status will be going away at some point. The funding dates will drive the post being inactive/active. A separate bulk post fundings update is envisaged, the below is to be discussed: TISNEW-3248 - Getting issue details... STATUS Ashley Ransoo Send Post Funding to NDW - Create ticket to include Funding Body. TISNEW-3249 - Getting issue details... STATUS | |
| 16 | Curriculum GMC Reference Number | All | 19/08: Needs adding to TIS for ARCP return. Add to Assessments bulk upload. Can be done via Intrepid avoiding the need to add it to TIS Assessments upload. Add to NDW - TISNEW-1547 - Getting issue details... STATUS |
as she now understands that this part of the exercise will not remove ALL erroneous records. Work is continuing........
0 Comments