# | 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 | |
| 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 | |
| 3 |
| JH, AP, IO | Proposed Solution (JH)
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 | |
| 4 | ESR Integration Data Quality tasks. Some of the fields are mandatory for ESR to create records.
| IO: |
| |
| 5 | Fields comparison/review between TIS and Intrepid. Fields removed from Intrepid when coming across to TIS JW/AP/CL to review Next Monday (15/01). | JW/AP/CL | Separate spreadsheet reviewed - to be attached DR2 to TIS Field Mapping. with Actions_IO update.xlsx (now added to the able, see below items 10-32) AP/CL to provide an update. | |
| 6 | ESR Integration - Data Quality
| JH/AB | JH - AB - | |
| 7 | Absence
| CL | ||
| 8 | Reference Data - Status of the values Intrepid Current reference values/tables - Can possibly be on DR2? | |||
| 9 | JH - Report on Audit trails in the Datawarehouse. To start with Placements. What are the Criteria? | |||
| 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? | Ask John Thompson | OPEN | |
| 11 | SecurityEmail in Person- This is missing from TIS. Will the email used for self-service / security be the normal EmailAddress? | Consolidation issue fixed, so need to pull report again and confirm, there are some trainees who use different self service address v email address on their profile
| OPEN | |
| 12 | Associated Site, Associated Trust, Associated Specialty in Person- Have these fields not been developed yet? They are used to manage Supervisors. | Ticketed and awaiting development | CLOSED | |
| 13 | SiteID and GradeID in Placement- These fields are missing from the TIS placement table. Some posts are bucket posts so several different sites can be chosen for placements belonging to the same post so SiteID is needed against placements.. A specific placement grade is chosen from the other grade list in a post so the Grade ID is needed against placements. | known issue that we are working on. | CLOSED | |
| 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 | OPEN |
| 15 | Comments for Placements - A comments box is needed for placements. | Add story for comments box | OPEN | |
| 16 | SupervisorType for PlacementSupervisor- A SupervisorType field is needed in the PlacementSupervisor table as supervisors can be added to placements as Clinical Supervisors or Educational Supervisors. Personally, I think it would be better to just have an Educational Supervisor field and a Clinical Supervisor field directly in the placements table in order to restrict the recording of only a single Educational Supervisor and a single Clinical Supervisor against each placement record. It also simplifies the database table structure. | Need to display both clinical supervisor and educational supervisor within a placement, with lables for each - there may be multiple for each type? Tickets created There is a need to simplify back end for supervisor allocation and reporting | CLOSED | |
| 17 | OtherGrades in Posts - I'm assuming OtherGrades are being stored in the PostGrade table? | Other grades can be selected from the same list at the main; they all come from the same table - it's essentially a multiadd feature | 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) | OPEN |
| 19 | FundingBody in Post - Is this field being discontinued in TIS? | How are we mapping the funding information.
| CLOSED | |
| 20 | Comments for Posts - A comments box is needed for posts. | NEW ticket - to be confirmed whether it is an should be possible to | OPEN | |
| 21 | OtherSites for Posts - This is required in order to create "bucket" posts where several sites are against single posts so that specific site details can be chosen at placement level. | Current functionality to add multiple sites to a post; also need to confirm what the max upper limit is on adding sites (needs to be v high) | OPEN | |
| 22 | Comments for Programmes - A comments box is needed for programmes | NEW ticket required | OPEN | |
| 23 | CurriculumStartDate for ProgrammeMembership - Why in the TIS ProgrammeMembership table is there a CurriculumStartDate field? The minimum curriculum start date within the programme membership would always match the programme start date. The CurriculumCompletionDate field in ProgrammeMembership needs to match the maximum curriculum end date within the related programme membership as the ProgrammeCurriculumCompletionDate does in DR2. | Do we need currciulum start date as well as programme start date? They should always be the same date in most scenarios - TBC with SMLs | OPEN | |
| 24 | Rotation in ProgrammeMembership - I don't understand what the rotation field is in the TIS ProgrammeMembership table. | Field to display the rotation a trainee has been added to, must be amended to multiple | CLOSED | |
| 25 | AddedDate in ProgrammeMembership - ProgrammeMembership already has an amended date field but it also needs an added date field | IO | To be reviewed (IO) | |
| 26 | ProgrammeNTN, ProgrammePost, Site, Trust, Administrator, Assessment, Course, CourseAttendance, CurriculumMembership, Entitlement, Grade, Leave, LeaveExpense, LocalOffice - Have these tables not been developed yet? | IO | To be reviewed (IO) | |
| 27 | PostSpecialty, PlacementSpecialty, CurriculumSpecialty in Specialty - Are we no longer making a distinction between PostSpecialty, PlacementSpecialty, and CurriculumSpecialty? If so, why? Or are SpecialtyTypes related to this maybe? | IO | To be reviewed (IO) | |
| 28 | Grades in Curriculum - We need a grade list for each curriculum. | check if grade cn be added to curriculum. | ||
| 29 | Slot Share in placements - Have this field been removed from TIS? | Data Leads to confirm necessity | ||
| 30 | Honorary for placements - Have this field been removed from TIS? | Data Leads to confirm necessity | ||
| 31 | ITP for placements - Have this field been removed from TIS? | check where the secondary sites are in the back end. | ||
| 32 | SLA placements - Have this field been removed from TIS? | Data Leads to confirm necessity |
Page Comparison
General
Content
Integrations