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 5 Current »


Data leads:

Chris Norman (Unlicensed)

Alice Thompson

David Short (Unlicensed)

James Harris

Sue Barrand (Unlicensed)

Andy Nash (Unlicensed) could you invite Andy Horton (Unlicensed) to have access to confluence, please (Done)?

#
Discussion/Action
Responsible
Outcome
Status
1

Programme names/numbers aren’t provided for Dental trainees, they’re created by Admins

JH, AP, IO


Proposed Solution (JH)

  • 3 letter use the prefix of the local office + 3 digit acronym based on specialty
  • 3 digit specialty acronym should be consistent across all

Action: AP/IO to impact assess

JH: Done mapping and need to do some more work and send to AP.

AP has received James ssheet.

More generally, we should look to standardise naming conventions around programmes (not just Dental) to be discussed separately

Next to put on Microsoft Teams and get SMLs feedback - AP

JH/AP - Setup call to briefly explain next week. - Was decided that it should be postponed for the moment on advice from James.

IO/AP: Recommendation: show a concatenated display of the programme name in the dropdown list with the Local Office name? To check with DEV on the possible solutions. (P1) TISDEV-3767 - Add indicator to drop downs to highlight "ownership" of values to the user TO DO

19/02: AP/JH: Field limit for programme number? Check field validation (Alistair Pringle (Unlicensed))  Max number of characters is 20 including spaces / special characters

09/04: Sent to Andy, Programme number being changed as this was too long. 

30/04: Leave on for next 2-3 data leads call. 

ON HOLD till post MVP launch

Revisit in July 2018.

Revisit September 2018 due to other priorities.

2Reports on Deleted records requested from Hicom. (Status of 'Delete' on Hicom but still 'Current' on TIS).  (#intrepid_Integration slack channel conversation).AP/IO

08/05: Alistair Pringle (Unlicensed): Chase up with Martin.

DS: In Intrepid, Programme is a hard delete, whereas Programme membership is soft delete. 

14/05: AB sent details of report criteria to the Intrepid Analysis team. No response from them yet

JW to set up meeting with Data Leads, BAs, POs and Reubs on how to manage deleted records on TIS in future. 

JH/AB: Checked the deleted records. Next step to flag what records on TIS are to be deleted. Send to CL/DS to check. 

Hicom has not provided the full requested set of deleted records but will follow. 

04/06: Programme, Posts and Prog. memberships Id's send and TIS to action the delete next. Tickets are on Jira. 

Former user (Deleted) - check the priorities of those.

11/06: They are all P1's as they affect reporting, move up the BAU list.

18/06: awaiting updated/consolidated view of changes (IO)

02/07: Dev work has started, some of them have been done. (label of 'NDW UAT') 

16/07: 'Deleted' tickets are in this sprint TISDEV-5125

23/07: Former user (Deleted)Jayanta SahaAlice Thompson - Work in progress, will be carried on to the next sprint. To discuss at sprint planning.

30/07 - work progressing.

13/08: Check on which environment they are?


3 Data/Field level analysisAll

IO: Suggested approach:

1. Sit with Chris and review the output he shared with DQ leads + delete report
2. identify areas of concern
3. coordinate through Reubs/Ashley to fix areas of concern
4. re-test later on versus DQ analyses

04/06: Tickets being created 

11/06: Former user (Deleted) to update? 

18/06: reviewed with Data Leads, Reuben and Devs, updates to tickets underway and should be compete by COP tomorrow. Resource has been allocated to implement changes and I believe work has started on the tickets that are ready

16/07: on going refinement

23/07:Ify : 

  • 1. missing fields from NDW and TIS identified
    the tickets written and being worked on
  • 2. I'm currently looking into discrepancies between Intrepid , TIS and NDW where fields exist, but data appears to be inconsistent

    30/07 Call today to discuss.
  • 13/08: Ify handed over to the POs and Ashley - work to be looked at when capacity/demand allows

4Resolve Duplicates - TISDEV-4841: Resolve the duplicate invalid GMC numbers, such as 'Retired,' and make them 'UNKNOWN'Data leads

Discussed on DQ on 04/06:

  • Agreement re changing '0', 'Retired', 'TBC' or 'u' to UNKNOWN in the GMC/GDC/PH number
  • Changing blank to UNKNOWN not recommended as it may legitimately be blank because they have a GDC or PH number
  • What we should do to those with blank/null in all 3?
  • JH: Among those none have programmes and very few have placements. There are Staff, Both, Contact, Admin.
  • JW: 
    • Admin and Contact = N/A ?
    • Staff and Both = UNKNOWN ?
      is that the agreement?

04/06: The following has been agreed:

  • GMC for Contacts, Staff and Both = UNKNOWN
  • GMC for Admin = N/A

DS: List of persons with same GMC's, check the DW to see if some of those have been resolved?

TISDEV-4841 to be paused from releasing to Prod until David Short (Unlicensed) has done his investigation of the ones that could potentially be merged. Merge Rules to be shared. To create tickets following that.

11/06: Ongoing and will probably be ready mid-week.

18/06: On hold until the document uploads are available on People records? The idea being if de-duplicated before the documents have been added, we won't be able to attach the documents to the deduped person records. 

Get an update from Ben/Anita regarding document management in a couple of weeks. 

02/07: Benjamin Witton are you able to give an update on this?

09/07: Ben: We are expecting the document delta from Hicom this week. The next step will be to get them onto Azure and then apply the agreed meta tags.  Do let me know if you need any other details/updates. 

16/07: Delta received. Document work to continue in this sprint. Following which David can work his magic on the duplicates. David Short (Unlicensed)  does your  initial work need to be revisited? and will there be any dev requirement related to your dup work? We will need to include this in Planning so will need to know (smile) Complexity and volume - David may need to work with Dev in next sprint in order to prepare this. Prioritisation required. 

23/07: Work in progress, script modified. (David Short (Unlicensed),  bullet points of what's required to bring into the sprint as User Stories)

13/08: Document Management migration complete - when can work start on the duplicate records David Short (Unlicensed) ?


5New NTN format workAP/JH

Daniel Smith and Angela tasked me with speaking to you guys about what we can do about NTN format. 

11/06: Alistair Pringle (Unlicensed) to work with data leads and nominated people to look at the various options, also considering maintaining this outside TIS.

18/06: JW shared DRN spec with JH on 11th June

18/06: Meeting with Daniel Smith (GMC contact) to discuss further. 

2/7/18: New format agreed in principle. To be socialised at the ODG on 4/7/18. Internal meeting amongst HEE BMs required to discuss rollout.

02/07: Output of the conversation sent to BMs to decide the next steps forward. 

16/07: Alistair Pringle (Unlicensed) ticket TISDEV-4966 in this sprint relates to what NTN fields are needed on the TIS FE and BE. Are the NTNs and DRNs James Harris is creating to be shown on the TIS FE? And what about reporting?

23/07: Rob trying to set up a discussion to take this forward with BMs.

30/07: Meeting with Angela tomorrow. Ashley is creating a ticket relating to ability to add NTN via the bulk upload as Angela wants to know timeframe for getting this onto TIS.

13/08: Agreement reached with GMC. Angela F and BMs accept there will be a mix this year with some trainees having the 'old' style NTN and some who will be issued with the 'new' style NTN. Alistair Pringle (Unlicensed) are you able to add more info here?


6Post Funding - management of posts with multiple current post funding episodesJW

02/07: 

  • TIS to show only one funding record for a post - current and where there are two current TIS shows only the one with the most recent start date
  • Where there are multiple current episodes ask the local offices if this is by accident or design
  • If by accident remove/update the appropriate record in the database
  • If by design this requirement will need to be fed into the future requirement document for consideration

16/07: Panos is implementing TISDEV-5030 in this sprint to correct this issue (note that posts with more than one current funding episode will show multiple records on the post list)

23/07: Will be carried over to the next sprint.

30/07 hopefully the work will be completed during this sprint.

13/08: work complete and will be released on Wednesday



7Post Funding - vision documentJH

02/07:

 Post Funding

  • Process around Vacant posts
  • Reporting aspect
  • Meeting organised by Nazia AKHTAR to discuss

16/07: Document by James H to be shared with the Post and Funding Reporting group for initial comments. Final outcome is to be an agreed dataset to be recorded on TIS (aim is to meet national reporting requirements). 

23/07: Review of James's document in progress, further discussions to then take place based on feedback from BMs. 

30/07 National team involvement in the calls. Requirements seem reasonable. 

13/08: Local Offices are having difficulty agreeing on the values for Post Funding Type. Naz is still waiting for all local offices to respond to the document created by James 



8Posts with no Local Office ownerAll

23/07:

  • Spreadsheet shows the Current and Inactive posts on TIS that have no local office owner
  • Solution from James H is to source local office owner in the following priority:
    • Post Programme
    • Post Prefix
    • Post Trust - using Trust of the Site rather than the employing or training body
  • Next step is to agree the above, find the local owners and then add to ticket for inclusion in a sprint

    30/07 - James to do the necessary report.
  • 13/08: report created and the vast majority of the posts now have a derived local office. However in a small number of cases the derived owner is in fact old deanery. DQ leads have been asked to confirm which local office these posts belong to now. 

9Post specialty and sub-specialty confusion in TIS InterimAll

23/07:

  • James H to describe please (smile) 
  • Schedule an investigation task for a dev to look at the BE and FE on TIS.
  • Raise a story/bug, James HarrisAlice Thompson - could you send some examples please? To be prioritised on sprint planning as a high priority. (cc Alistair Pringle (Unlicensed)Joanne Watson (Unlicensed))
  • 30/07 - this development is in the current sprint. Simon will be working on it.
  • 13/08: carried over into this sprint (Sprint 55)
10Identification and removal of Consultant data on TISAll

13/08: 

  • Need to ID those Consultants who aren't on TIS as trainers and remove them
  • Those who are on a trainers we need to udnerstand what information we should surface on their records e.g. Assessment information perhaps isn't required.
  • All open for discussion and agreement - Ben to set the scene
  • Other regions to review Alice's scripts. 
  • How were consultants recorded on intrepid?
  • Benjamin Witton to update with some bullet points of what's been discussed. (not about the mulberry bushes) 
  • 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.