Welcome
- out loud on the call - really, we’d appreciate you doing this!; |
---|
Live Issues:
| Incident logs Left-over from last iteration, now fully written up 2021-09-08 Person Placement Employing Body Trust sync job failed affecting Person Search |
---|
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 | |
---|---|---|---|---|
TISSSTrainee Self-service (TSS) | Full list of Designated Bodies Allow trainees to select from a wider list of Designated bodies when their Previous Revalidation Body is not a Local Office. | Prod demo | Reval||
Improvements to sync of Specialty data | Previously when Trainee Self-Service received an updated Specialty an attempt would be made to update all associated placements in a single action. There are many large specialties, with more than 190,000 placements related to a single specialty at the extreme. These large specialties would take a very long time trying to update the placements and if there were any issues then all placements would fail to be updated. With the latest improvements the placements are now updated one-by-one by added some additional steps
This change in approach allows a much more consistent experience regardless of the size of any particular specialty, as well as making the volume of pending updates much more transparent. | |||
Revalidation | Snapshot Migration - Approved Recommendation not showing as historical data in doctor's detail | Live Demo together with the next part | ||
Snapshot Migration - Approved Recommendation not showing as historical data in doctor's detail | Live Demo | |||
Record Level Notes Investigation | Brief talk through | |||
Trainee Information System (TIS) | Reference data management improvements | Previously many reference types could not be properly managed due the status field being missing. The status field has now been added to most of the reference types, there are a few outliers remaining (e.g. Specialty Group) that will be addressed separately. In addition, the “Role Category” field has been added to the Role reference type so that it can be properly managed. | ||
Admins UI Designated Body Codes (DBC’s) Filter the full list of Designated Bodies to only show the Local Office DBC’s in Admins UI ‘Designated body codes’ list. | ||||
Two issues resolved | Assessment programme membership ID’s When creating an assessment through the TIS user interface, the ID for the programme membership (otherwise known as the programme curriculum ID) was not being set in the background. The assessment details would still include the applicable curriculum, however. Assessments uploaded in bulk did not have this issue. The impact of this was that reporting on assessments could be slightly more cumbersome. Email address validation in bulk uploads: | |||
Make Role mandatory for a Person | live demo | |||
Electronic Staff Record (ESR) | ||||
Northern Ireland Medical and Dental Training Agency (NIMDTA) | ||||
Objective Key Results (OKRs) 2021/22 Q2:
OKR | 1st | 2nd | 3rd | 4th | 5th | 6th | 7th |
Objective: Solve MFA and prepare for the second live pilot | |||||||
Key Result#1: Run an experiment with existing pilot Trainees on using an Authenticator App. | Too early | 0.1 | 0.5 | 0.6 | 0.6 | 0.7 | 0.8 |
Key Result#2: | Too early | 0.1 | 0.1 | 0.2 | 0.3 | 0.6 | 1.0 |
Key Result#3: Run the 2nd pilot to include live ARCP Form R completion via the app | Too early | 0.1 | 0.1 | 0.1 | n/a | 0.3 | n/a0.5 |
Key Result#4: Ensure data from all fields in Form R is stored in a format enabling | Too early | 0.5 | 0.6 | 0.6 | 0.6 | 1.0 | 1.0 |
Following on from a TISSS call (2021-08-17) where it was confirmed that running the 2nd TISSS pilot within this Quarter was not going to be possible, we removed it from the KR list for our OKRs. Spare effort we have as a result will go towards supporting other services and looking at where we can take KR#4.
Reinstated KR#3 in Iteration #6 as we were able able to begin the 2nd Pilot this Quarter. Well done everyone involved!
...
TIS Dev team roadmap:
Trello card | ||
---|---|---|
|
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!
...