#	Discussion/Action	Responsible	Outcome	Status
1	Reports requested by each region have been submitted to JT, Alice and James for writing up in SQL. JT, AB and JH had a meeting on the 8/12 to identify themes in the reporting requirements to allow a suite of reports to be written but with filterable criteria to allow each local office/region to run the reports they need,	JW AB and JH - to write the reports	JW provided the initial list of reports for creation JH/AB: Pushed into Tableau as data sources. Completed 1 of the reports. JT to publish for users to test. Logins to be setup for users. To present what's done so far (Tuesday 16/01) with Reporting SMLs. JW/JT to coordinate the access to Tableau for the SMLs to test the reports. - In Progress with JT List of names sent to JW Quick guide to send to SMLs	CLOSED
2	Oriel Integration:	AR	Tasks created and summarised in the table here. Create an Oriel Integration Channel on Teams - Done To schedule a quick presentation of the Oriel trainees import process. - People SMLs, a message on General 05/02 AR: Will schedule on my return. 12/02 AR: Scheduled for 16/02 @ 11a.m, will be emailing People SMLs.
3	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. - 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 - Getting issue details... STATUS
4	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
6	ESR Integration - Data Quality TISDEV-3620 - Investigate the proportion of Dental trainees with/without GDC dates TO DO - Investigate the proportion of Dental trainees with/without GDC date - JH TISDEV-3663 - GDC Number of N/A - Investigate TO DO - GDC Number of N/A - Investigate - AB	JH/AB	TISDEV - 3620 - Done JH: Assumption: Dental trainees to be any person record that has a GDC number which is not Null, N/A or blank Total Number of Person Records: 13376 Number with a Start and Expiry Date: 622 Number with a Null Start or Expiry Date: 12754 % with valid dates: 4.65% % without valid dates: 95.35% TISDEV - 3363 - In Progress JH/AB/CL/DS - To get rid of the N/A for records that have a valid other registration number. We can only remove it for all if we are definitely not going to have person records which would not have an applicable reference number I think the validation rule should stay the same But what are we going to do with the practice manager records? AR: To find out with ESR how they handle a GMC/GDC number of 'N/A' - 05/02: If the professional body detail is provided in the applicant file, then ESR would expect to see the registration number and the expiry date in the subsequent fields. Where a value of N/A is being passed, the assumption is no professional body is being passed therefore does not represent an issue for ESR. Next Steps: CL/JH: To be written down of what each means and share with SMLs? - to be documented: Trainnees should have at least 1 registration number populated, if that is not known at the time the record is created, then populate one of the relevant registration numbers with 'Unknown' and the rest as 'N/A'. AB: PH numbers - what is the standard format? Not consistent across LOs. JH: 2 PH schools for assigning the numbers, also not mandatory to have one - make this a non-mandatory field? - Ashley Ransoo Joanne Watson (Unlicensed) - to verify this on TIS.
7	Absence TISDEV-3529 - Absence - Review proposed Study Leave template for TIS bulk import TO DO - Absence - Review proposed Study Leave template for TIS bulk import	CL	AR/CL: To discuss and feed into the design work for Absence. 05/02: Matt/Ashley/Claire have met and discussed on the templates for recording Study leave and costs/expenses which will feed into the solution design for TIS. Claire - any update from Martyn Clarke (Lead BM for absence) with regards to the national process? Trusts access to Intrepid and how they are currently recording study leave not necessarily the way forward for TIS. - To be clarified with Rob
10	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.	OPEN
14	Added Date and amended date for placements- Added date and amended date fields are needed for audit purposes.	IO	Audit data needs to be reportable - add as a NFR	CLOSED
15	Comments for Placements - A comments box is needed for placements.	IO	Add story for comments box - add ticket TISDEV-3810 - Getting issue details... STATUS	CLOSED
18	Added Date and amended date for posts - Added date and amended date fields are needed for audit purposes.	IO	These dates will be displayed within the record, also should be possible to extract it for reporting purpose from the data warehouse, but this is TBC (IO) See example in #9	CLOSED
29	Slot Share in placements - Have this field been removed from TIS?		Yes it has been removed - TBC is required, check Teams No further comments on this Addressed separately. - Removed	CLOSED
30	Honorary for placements - Have this field been removed from TIS?		Yes it has been removed - TBC is required, check Teams No further comments on this Removed	CLOSED
31	ITP for placements - Have 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. Workaround for MVP? e.g. comments box. To be discussed/prioritised on Woraround meeting this week.	OPEN
32	SLA placements - Have this field been removed from TIS?		Yes it has been removed - TBC is required, check Teams No further comments on this	CLOSED
33	Local Team acronyms - data leads to agree on terminology	Data Leads	Data leads to agree on the list. CL: List from Intrepid Consolidation to be sent
34	P1 and P2 data related tickets - more info needed

Browser not supported