Welcome
- out loud on the call - really, we’d appreciate you doing this!; |
|---|
Live Issues:
| Incident logs 2021-12-03 GMC sync for old & New reval were blocked by the GMC |
|---|
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) | Self sign-up (new components allow for password confirmation and toggling password visibility) | Live demo (stage environment due to the pilot still in progress) | |
Revalidation | RO details update in prod | Brief Discussion: Different Responsible Officers (or Deans) delegate different levels of responsibility to their teams in different Local offices/Designated Bodies. When a recommendation is submitted to the GMC, corresponding DB’s Responsible Officer’s surname, gmc id, designated body code are also submitted to GMC along with the doctor’s detail. The RO details are cross checked in the GMC’s database. If the details are correct only then recommendation is allowed to be submitted. | |
Fix login issue for users who have long email address | Brief Discussion | ||
Trainee Information System (TIS) | |||
Extend filtering by ‘CURRENT’ to the ‘Other Specialities’ for extended options added by the user | Before:  After:  | ||
Add validation to TIS Email field to make unique | Trainees set up their account to access TIS Trainee Self Service by the Email address, so we need to add validation on TIS (UI/Bulk Upload) to prevent duplicates happening. https://apps.tis.nhs.uk/admin/people/person/3/edit-personal-details | ||
Spike - Recording of Curriculum membership and Programme membership to be refactored | Curriculum membership/s is abstracted in the current TIS model, we need a refactor so that curriculum memberships can be distinctly identified from programme memberships. This causes problem in accurately reporting on a trainee's curriculum membership/s which is abstracted in the current model. The pain point to refactor is that the current data model is widely used in all of our applications. So during this iteration, we did the spike on how to carry out the refactor. We investigated how to normalise the current data model, found a robust solution to do the data migration and roll out the changes in a non disruptive way. And then we analysed the effects on all the downstream services. | ||
Placement sub-specialty exported to the NDW | Placement sub-specialty data is now exported to the NDW. This information is also available in Metabase, and can be included in queries and reports. | ||
Electronic Staff Record (ESR) | |||
Northern Ireland Medical and Dental Training Agency (NIMDTA) | |||
Objective Key Results (OKRs) 2021/22 Q3:
OKR | 1st | 2nd | 3rd | 4th | 5th | 6th | 7th (Xmas) |
Objective: Complete the TSS 2nd pilot and release Reval MVP | |||||||
Key Result#1: Negative TSS User feedback declines as a proportion of overall feedback | 0.2 | 0.3 | 0.5 | 0.5 | 0.5 | ||
Key Result#2: Number of users that have authenticated and submitted their Form R using TSS exceeds 90% of pilot Trainees | 0.2 | 0.5 | 0.8 | 0.8 | 0.9 | ||
Key Result#3: All Reval Admins switch to using Reval rather than GMC for Recommendations | 0.1 | 0.1 | 0.1 | 0.2 | 0.3 | ||
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:
...
Ongoing work around how to split the team into multiple squads/small multi-disciplinary teams
Started reviewing the Performance Analyst capabilities in the team, with a view to formally ensuring we address them as a team, or we look to recruit to fill the every increasing need to measure success and identify improvement opportunities.
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!
...