2021/2: Q2 | Review#7 (2021-09-15 to 2021-09-28)

Incident logs

2021-09-08 Person Placement Employing Body Trust sync job failed affecting Person Search

TISSS

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.

john o

Prod demo

Improvements to sync of Specialty data

Andy Dingley

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

1. Specialty update received

2. Identify all related placements

3. Add all identified placements to a queue

4. Process each individual placement in the queue one-by-one

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.

Reval

Snapshot Migration - Approved Recommendation not showing as historical data in doctor's detail

Doris.Wong

Live Demo together with the next part

Snapshot Migration - Approved Recommendation not showing as historical data in doctor's detail

Doris.Wong

Live Demo

Record Level Notes Investigation

Doris.Wong

Brief talk through

TIS

Reference data management improvements

Andy Dingley

Previously many reference types could not be properly managed due the status field being missing.
Creation required help from the TIS team to set the status properly and it was not possible to change the status of many of the reference types.

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.

Marcello Fabbri (Unlicensed)

Two issues resolved

Reuben Roberts

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.
This has now been fixed, and we are reviewing how to patch existing assessment records with this detail where it is missing.

Email address validation in bulk uploads:
When bulk-loading people records, no validation was conducted on email addresses. This could allow typos or otherwise badly formatted email addresses to be added to TIS. When administrators then view or edit those people records, they would be unexpectedly prompted to correct the email address before any other changes could be saved, which could cause uncertainty or delay.
This has now been fixed, so people records with invalid emails are flagged for correction before they can be imported.

Make Role mandatory for a Person

Yafang Deng

live demo

ESR

NIMDTA

OKR

1st
Iteration

2nd
Iteration

3rd
Iteration

4th
Iteration

5th
Iteration

6th
Iteration

7th
Iteration

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. Get sufficient feedback to develop it into a solution for the next pilot.

Too early to score

0.1

0.5

0.6

0.6

0.7

Key Result#2: Coordinate Prepare for a 2nd pilot (confirm with teams running ARCPs - ask monthly. Any number would be insightful, ideally between 30-50).

Too early to score

0.1

0.1

0.2

0.3

0.6

Key Result#3: Run the 2nd pilot to include live ARCP Form R completion via the app (with associated HEE admin unlocking of Form Rs submitted in error, if needed).

Too early to score

0.1

0.1

0.1

n/a

0.3

n/a

Key Result#4: Ensure data from all fields in Form R is stored in a format enabling it to be extracted on demand for the purposes of reporting.

Too early to score

0.5

0.6

0.6

0.6

1.0