#	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	Role in Person- This is a comma separated field in the DR. Will this be a comma separated field pushed to the warehouse from TIS too?	AP	If you want to create a single row per person in the person table coontaining roles, this (or something like it) will need to be the case. The alternative would be to export person role as a separate table / view (this would be my preference). I would imagine that TIS stored person role as a separate table. The ETL into the warehouse can setup the data more or less however we like. I would separate out role, as it gets messy packing lots of them into one field and it is tricky for users to handle. John Thompson Considerations for reports changes - Post on Data_Warehouse channel on slack to get clarification. 19/02: AB: To follow up with JT Suggestion: Have a row per PersonID per role. Clarification on the Person table required. 26/02 JT confirmed that rols will continue as currently mapped; tbc whether there is an ongoing impact/changes reequired	OPEN
4	ITP for placements - Has this field been removed from TIS?		For the teams that are using this field, check where the secondary sites are in the back end; check Teams for further feedback on usage To be discussed and agreed with all regions: what should the standard usage process be? how should it be recorded? How many trainees does this affect? AP/CL: Needs to be looked into for post MVP. 19/02: Workaround for MVP? e.g. comments box. To be discussed/prioritised on Workaround meeting this week. Will need to be managed offline; will become needed in early April (either ITP field or comments box, or field) IO to create a ticket	OPEN
9	P1 and P2 data related tickets - more info needed	Data Leads	Ify Posted the list for Data leads to have a look. Data leads? 26/02 tickets reviewed	CLOSED

Browser not supported