Welcome
| Please ask questions, that’s what this Review is primarily for - your constructive interrogation of what we’re doing:
|
|---|
Live Issues:
| Incident logs This iteration 2022-01-18 Reference Service failed to start after upgrade 2022-01-26 Overnight jobs failed to run Carryover from previous iterations |
|---|
Dev team demo 'done' work contributing to those goals (no reference to specific Jira tickets, and no reference to work not 'done')
Area | Description | Team Representative | Demo - from Prod URL where feasible |
|---|---|---|---|
Trainee Self-service (TSS) | Display message advising trainees that only those invited to partake in pilot should sign-up | Demo from live | |
Tech improvement: Simplify state management i.e. how and when data is shared and updated as a trainee uses TSS. | Demo      | ||
Trainee feedback - Display a message/information showing the trainee who maintains their personal details data and how they go about updating incorrect details. | Demo    | ||
Remove non-ARCP/test Form Rs created during initial pilot | Our forms list was still showing forms created as part of the initial pilot, so those trainees who took part would have seen forms which were not used as part of their ARCP. | ||
Revalidation | Display curriculum end date instead of programme end date in Recommendations summary page | Before:   After:   | |
Display correct GMC Status and TIS Status for pass recommendations | GMC Status and TIS Status for pass recommendation should be displayed as <blank> and “Not started” Before:  After:  | ||
Replace custom:preferred_username with OOTB Cognito attribute | Brief discussion | ||
Trainee Information System (TIS) | Investigate user auth token and decide how to deal with the non-required attribute “perferred_username” | ||
Limit list of Post’s subspecialties to specialties of type |  The creation and update of a Post involves the optional indication of the post’s sub specialties. This field used to be populated with a list of all Specialties whose status was Now it’s populated with a list of Specialties whose status is The Specialties eligible to be a Post’s subspecialty are 32. (List) Restricting a post’s list of sub specialties to Specialties that are of type
| ||
Make Front end deletion for assignments hard-delete | Previously when a assessment was deleted in TIS this would update a column in the database (DB) for that assignment called “softDeleteDate”.  when this column has a value it is filtered out of the FE but allowed it to be kept in the DB. this has now been changed to a Hard delete method meaning that the assessment being deleted is not retained in the DB. the warning before deletion has been updated to reflect its permeance. this removes the need for filtering further down the NDW and brings the deletion method in line with the BulkUploads delete. | ||
Electronic Staff Record (ESR) | |||
Northern Ireland Medical and Dental Training Agency (NIMDTA) | |||
Objective Key Results (OKRs) 2021/22 Q4:
1st | 2nd | 3rd | 4th | 5th | 6th | |
OKR #1: Prepare and launch 3rd TSS pilotPreparing for the wider release of TSS in 3 tranches from April 2022 | ||||||
Key Result#1: 99% of trainees successfully able to login using self-sign up and the MFA. | too early | too early / 0.1 | ||||
Key Result#2: 25% of trainees complete a survey. | too early | too early / 0.1 | ||||
Key Result#3: Support materials enriched based on feedback. | too early | too early / 0.1 | ||||
Key Result#4: 95% of admins agree that the process has been made more efficient by TSS. | too early | too early / 0.1 | ||||
OKR #2: Keycloak to Cognito authentication migrationExtricating us from our reliance on an outdated application (Keycloak), several major versions behind what is supported | ||||||
Key Result#1: All TIS apps can accept authentication from Cognito. | too early | 0.3 | ||||
Key Result#2: Keycloak is no longer used for authentication by any TIS apps. | too early | 0.1 | ||||
TIS team development (following external review)
Last Review I highlighted that we recently had an external review of how we work within the TIS team. From that review, a number of recommendations were put forward for how we can alter things going forward. The whole team is actively working towards implementing these recommendations. As we are a team that at its core believes in transparency and openness, we decided to give you a flavour of what we have been working on:
...
Agreed we need to reach out to gain more context for what we do in TIS, within the wider HEE and NHS. And we’ve started having these sessions (one from Jon Howes on PGMDE and another on Digital First). If anyone reading this would like to volunteer to do a session, please let us know!
Started the process of agreeing standard team events (TIS team meetings, stakeholder sessions etc), and central comms (Teams, Sharepoint, mailboxes, etc), so that communicating within the team is more efficient and communicating with us will be, too.
TIS interim roadmap:
| Trello board | ||||
|---|---|---|---|---|
|
Feedback
We really do welcome any feedback you have for us - whether it be negative or positive, or whether it be a suggestion of something we could try/incorporate in a future Review. We absolutely don’t want to stand still. We’re very happy applying the 12th Agile principle of ‘becoming more productive’ to our Reviews themselves! Your contributions to this survey are entirely anonymous, should you wish to include anything others might perceive as controversial. We welcome any and all feedback, as long as it is constructive!
...