Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »


Data leads:

Discussion/Action

#
Discussion/Action
Responsible
Outcome
Status
1Resolve Duplicates - TISDEV-4841Resolve 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 - Getting issue details... STATUS  - 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



2Identification and removal of Consultant data on TISAll

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



4
  • Programmes with no Posts or People 
  • Posts with no Programmes

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



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


6Trust Users creation for LaSEMaria 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 - Getting issue details... STATUS


7Internal Medicine Training (IMT) Posts Upload for LaSEMaria 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 - Getting issue details... STATUS


8Sites 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.
  1. Do we know when the post update tool might be available to update the posts? Is it worth waiting?
  2. 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?


9PPT - very long placements
General discussion/info exhange about how the PPT will work in relation to placements with long durations etc. 2003 to 2099!




  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.