#	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 favoured approach is to change the programme number <max limit (Alice Thompson / Alistair Pringle (Unlicensed)) see dental spreadsheet prepared by JH	ON HOLD till post MVP launch
2	ESR Integration Data Quality tasks. Some of the fields are mandatory for ESR to create records. TISDEV-3322 - Missing mandatory Person details: First Name, surname and DOB TO DO TISDEV-3330 - Investigate and fix trainee records missing email address. TO DO TISDEV-3324 - Fix data for missing address details TO DO	IO:	Discuss with Reubs on the next course of action. All tickets clarified, require the report to be looked at again to confirm there are still issues pending 3322: DS: Duplicate issues to be fixed to reduce the numbers of missing details. - Update? DS: Checking 120 items manually. To be completed asap. Follow up with Hicom. CL/IO: To identify which of those are current trainees records; who is in a current/future programme/placement? AB: Which of those have self-service access? IO to confirm - check whether there is a trainee is in a current or future programme membership or placement and re-do reports, update data leads 19/02: DS: ~7000 records found. Outcome posted on DQ channel: check duplicate types v impact on TIS (ify) confirm how many record types affected per type (ify) confirm with DEV what fixes could be (reubs) - update vulnerabilities on TIS fix hard data issues by type (data leads / LOs) IO - Records with duplicate GMC/GDC/PH numbers to be checked, confirm records affected per type. (CLH) Impact to ESR already exists; what problem will this pose going forward with integration? Ashley Ransoo local offices need to know which records arent' going through (notifications should help?) confirm with ESR team that this will continue to be an issue Former user (Deleted) / Joanne Watson (Unlicensed) / Alistair Pringle (Unlicensed): AR 26/02: (Nazia AKHTAR cc'ing you here as this will need to feed into the support model as discussed with Victoria on 22/02) These will be handled through Error/Exceptions handling Reports by the TIS-ESR interface for the following. 1. Applicants with Missing Mandatory details - Report (every morning after receiving RMT file and when generating the APP file on TIS) 2. RMT - exceptions, ESR DPNs not matched to TIS NPNs - Report (created on TIS every morning on receipt of the RMT files for each Deanery.) 3. APC warnings - Report (missing GMC end date etc. This can take upto 2 days to be received from ESR) 4. Notifications - TIS mailbox to be supplied to ESR (Report to be received from ESR everyday if there are any errors, generally before midday) For 1-3, we will hook metabase to generate some slack/email notifications on errors to a generic mailbox to be looked at. This could be run per local office and sent to a nominated address for each Local Office. Or, sent to service desk to coordinate with Local Offices. Following the reports received for 1 & 2, if the Local Offices wish to fix/make change to the records within the SLA (where Projected start date <3 months > 2 days), these will be picked up by the next ESR ETL run at 5 p.m. in the afternoon of the same day, else on the afternoon of the following day. For 3, these are generally warnings and trainee records would have already been created successfully on ESR, if LO makes changes to the personal detail on TIS against those trainees, they will need to be made manually on ESR directly as well since changes to the personal details do not flow from TIS to ESR.	ON HOLD till post MVP
3	Data Quality dashboard to be shared with other regions from LASE		John to schedule time to review it 05/03 Claire to prod on what the progress is on this 05/03 JT to chase up when he's back in London on 06/03 12/03 Demo to be arranged, check if JH is back. Chris Norman to share SQl script. 26/03 JT to setup doodle poll to arrange date for demo.	OPEN
4	Placement import template. Confirmation on Update and Add fields from data leads.	CL	Data leads to confirm. Error validation for bulk imports to be confirmed as MVP. - IO Which validation have already been implemented if any? - AR AR 19/03: Validations expected to be surfaced in error reports for bulk people upload: 1. Structural errors, e.g. incorrect template uploaded 2. Mandatory fields errors 3. Reference/dropdown values mismatch 4. Programme name and/or Programme number mismatch (although this should be part of dropdow value mismatch) 5. Curriculum 1/2/3 mismatch (although this should be part of dropdow value mismatch) 6. Duplicate registration number (GMC/GDC/PH No.) on the template against 2 or more rows 7. Registration number (GMC/GDC/PH No.) exists against against a different Surname on TIS. (Note: as per the template above, Surname and Registration number are the matching criteria) 8. *All endpoints validations to be surfaced in the error reports where applicable* to be verified with dev Rules: 1. Fields marked as 'Addition' in the template can only be added to a person record if populated 2. Fields marked as 'Addition' in the template, if left blank, and are not mandatory, will be left as blank 3. Fields marked as 'Update' in the template, if person matching criteria are met, will be updated with the populated values. 4. Fields marked as 'Update' in the template, if person matching criteria are met, but left blank, will not update existing values held on TIS. 5. If matching criteria are not met, i.e. Both Surname AND Registration number in combination (GMC/GDC/PH No.) do not match to an existng person, a new person record created. 6. Role - If the same role already exists against the person, don't add in duplicate Definition of Error validation to be further look into if required - Claire to support. 19/03: Increment for additional validations when we have a stable version of the bulk upload. Create and Update scenarios validations to be defined. AR 26/03: Provide dev with a sample templates populated for Placements and Posts.
5	London Aprprovals tool and Trainer records	AP/IO	CL - To check what's been done already then schedule a demo. AP - Recording of trainers against placements. Arrange call with SMLs to discuss.
6	Data related support what should the escalation path be? does a new service desk channel need to be created?		individual logins for data leads need to be set up if not already existing.
7	Absence related identifiers for NW office During conversation with Keith Davies & James Owen, they mentioned that there were some identifiers that were managed in Intrepid, that were used in their process for absence management - is this something that we should be concerned with for TIS? For other local offices?	DS	schedule a user research session with NW for study leave.
8	Start post funding discussion with local offices	JW/JH	Place holder	ON HOLD till post MVP

Browser not supported