# | Discussion/Action | Responsible | Outcome | Status |
|---|---|---|---|---|
| 1 |
| 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 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) 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 |
| 2 | Start post funding discussion with local offices (Amending) | JW/JH | Place holder AP/JH/IO: IO To update with ticket numbers and post on DQ channel. | ON HOLD till post MVP |
| 3 | Update on data issues (James/Claire) flagged on DQ channel - Data not pulling through rather than missing placements. Progress update on the checks between Intrepid and TIS UI (Claire) | JH/CL/IO | CL: Spreadsheet uploaded with feedback - Qualifications, Assessments and Placements issues identified. | |
| CL/IO | IO to review the feedback from Claire 09/04: Claire Shared with other Data leads to test the UI and feedback - JH, AB & DS 15/04: Update? 19/04: Go through BAU tickets 30/04: Check status of those tickets and review . IO to cite the tickets here for CL to review when ready. 08/05: Former user (Deleted) to update. 14/05: Progress? | |||
| 4 | Bulk Assessment template to be reviewed. | Data leads CL/JH/AB/DS | AR: Share on DQ Slack channel AR 23/04: Alice has added her recommendations and shared on DQ channel, can other data leads review and confirm? AR: 30/04: To review comments from Alice and James AR: 08/05:
| |
| 5 | Bulk People Import - Feedback Check if the Expectations are correct on the Jira tickets | CL/AB | Check progress end of week on bug fixes. Release to users for testing. AR 23/04: Demo on people bulk upload was done on last Show & Tell. User guides being updated with to include bulk upload. Programme membership rules discussed and agreed to be made consistent on both FE and FE, i.e. where a Programme membership exist against a person where Programme name, number, membership type , start and end dates match exactly to those on the template, it will be flagged as an error. If any of those differ, multiple memberhships of the Programe name + Number allowed. 30/04: IO/Reubs: Review in progress, not ready to test. 08/05: Data leads to go through Fields validation to see if the Backend validation are in line with Bulk? | CLOSE |
| 6 | Telephone and Mobile numbers validation in TIS. Currently the bulk People upload does not allow a row on the template to be uploaded where there is an existing person in TIS with a Mobile/Telephone number that is not in the TIS accepted format and has been left blank on the template. TIS field validation:
There re currently over ~7000 records on TIS that do not meet the above. i.e. contains letters, special charaterers other than the above. https://build.tis.nhs.uk/metabase/question/179 Should there be a softer rule for telephone/mobile numbers? | Data leads | AR: Share the conversation on DQ IO: Separate discussion taking place with Reuben to discuss the solution design. There is not currently a way of identifying legacy created or TIS created data. Reubs: the initial underlying principle in TIS was that we wouldn't force users to update legacy data in order to edit a record in TIS. 08/05: James Harris to coordinate with other data leads on reviewing this along with the rest of the Backend Field Validation. Former user (Deleted) to send the links to the relevant pages. | |
| 7 | InterDeanery Transfer (IDT) process and potential issues raised:
(Trainees NE to Yorks and Humber or vice versa - no issue and trainees moving from non TIS local office to non TIS local office no perceived issues) | All | Assessment of the impact and understand implications. IDT - covered by codes of practice Understand Rebase - Speak to Reuben. CL: Given the small numbers, suggestion is to update on both Intrepid and TIS. Make the updates just before going live - Data leads to coordinate. 2) - Non-issue. CL: Claire Le Houx (Unlicensed) To send comms on the process. 08/05: ST3 to be looked at together. JH: ETL flow from Datawarehouse to Intrepid with TIS updates. | |
| 8 | Reports 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. | |
...