Revalidation Process, Issues & Considerations

Recommendation/Concerns/Connections

1

Revalidation CCT date discrepancy.

Different dates appearing on the system when they should align

There is a difference in the CCT date displayed in different areas of the system. For example in TCS we are seeing the trainee curriculum completion date as X and in the Revalidation service it is showing as Y.

This will be captured as test criteria

https://hee-tis.atlassian.net/browse/TISNEW-4506

2

Some columns are not populated for some local offices within the 'Under Notice' tab

Users are unable to see data in the appropriate columns meaning they cannot use the service.

This will be captured as test criteria

No Ticket required. Data quality to be tested overall.

3

Placements in Revalidation section not pulling through when no site added on front end of the TIS system.

Placements section within the Revalidation service not showing necessary information.

This will be captured as test criteria

No Ticket required. Data quality to be tested overall.

4

Move revalidations' GMC outcome status updating from Revalidation to the GMC Sync

Fault in the original build meaning the revalidation episodes are not being tied off which results in trainees not coming back onto the under notice list when they should be.

To be considered in UX design

No Ticket required. Data quality to be tested overall.

5

TIS not updating GMC Connect with a Revalidation recommendation

Users may think that a recommendation has been made to GMC but the GMC have not received.

This will be captured as test criteria

https://hee-tis.atlassian.net/browse/TISNEW-4210

6

Under notice list not tallying with GMC connect under notice list

There was a 30 day ‘hold’ period for a trainee who had had a submission made and then was back under notice again (e.g. if the submission was for a minimum deferral period or the trainee then was brought forward).  This was done to stop trainee’s appearing on the under notice list ahead of the GMC approving the previous submission but we have had this sorted out so on TIS they will only reappear on the under notice list once the submission has been approved (which is how the GMC connect list works).  We thought this was sorted but still happens

This will be captured as test criteria

https://hee-tis.atlassian.net/browse/TISNEW-5551

7

CCT date visible and sortable on ‘all doctors’ list

Fixed in current implementation.

To be captured as a high priority requirement

https://hee-tis.atlassian.net/browse/TISNEW-5554

8

All columns on both lists to be sortable on columns e.g. managing team, db, programme

TBC if this is still an issue - this has been tasked, not certain that all columns are sorting a-z correctly or sorting the full list and not just the page you are on

To be captured as a high priority requirement

https://hee-tis.atlassian.net/browse/TISNEW-5555

9

IDT trainees to appear on drs to add list

Additional flag for certain trainees to be applied.

We think that there is no longer an option to give trainees the membership type of ‘IDT’ which had historically been used on Intrepid and then caused the issue.

To be captured as a requirement

10

Labelling to change back to Revalidation from Concerns (Tab heading on main TIS screen) – 

Fixed in current iteration

UI design consideration

11

Revalidation submission date to be pushed through onto main TIS record for each trainee

Previously tasked but not done

To be captured as a requirement

12

Live data refresh from main TIS rather than overnight

Previously tasked but not done

To be captured as a requirement - intraday GMC refreshing

13

Form R solution

This will be part of the trainee self service module and Alistair views Form R as one of the key things to do first but we also need to get our Business Managers to push for this as they will be asked to identify the priority areas for TIS. - NO PROGRESS

Dependency, but out of scope for Revalidation workstream

@Ashley Ransoo

14

Upload of previous form r data (nb multiple formats)

this is already in progress as part of document management but we have requested a quick link through from reval app to access the docs. - NOT DONE

Dependency, but out of scope for Revalidation worktream

@Ashley Ransoo

15

Bring forward via TIS option rather than having to use GMC connect

Amending of dates should ideally happen within TIS and be fed through to GMC, however to be determined by GMC.

GMC doesn’t want to offer as will require another API set up - TBC

16

Identifying correct Designted Body on the doctors to add/remove list

This is something London needs as currently there is no information pulling thorough to ID which is the correct DB (managing team isn’t enough for the way London programmes are split) still an issue

To be captured as a requirement

Connection Discrepancies

17

There are a number of issues with the connections function which works on a complex algorithm.

For some local offices it has become unusable as there are too many erroneous records sitting in either the ‘create’ or ‘break’ connections UI.

To be captured as a requirement

Infrastructure

18

Add Circuit breaker to Connection Discrepancies service

Make requests to other services safely

Will be reviewed against solution design to confirm if required

TISNEW-2138

• Add Circuit breaker to Connection Discrepancies service 

TO DO

19

Add Circuit breaker to GMC Connect service

Make requests to other services safely

Will be reviewed against solution design to confirm if required

TISNEW-2142

• Add Circuit breaker to GMC Connect service 

TO DO

20

Reval (& Concerns and Notifications) rebuild architecture workshop

Revalidation is running Angular version 1.x. The other services are running Angular 7.x

It is likely that Reval is behind in terms of other tool / versions used to create / support it.

Will be reviewed against solution design to confirm if required

A Workshop with devs to assess how we can improve the architecture of the app.

TISNEW-2792

• Reval (& Concerns and Notifications) rebuild architecture workshop

DONE

Performance / quality issues

21

Speed

It’s not any known IF THERE ARE system wide issues, but it might be local teams own server/internet speed – not as much of an issue as before

To be reviewed against NFRs

22

Log in failures/time out errors etc/frozen screens particularly moving within the lists pages or from all doctors to under notice – 

We have provided some examples of this for them to look at – we still have this issue occasionally (see attachments)

To be reviewed against NFRs

23

Overnight refreshes

Failures and knowing if failed - requested some form of notification to show if the overnight refresh did/didn’t work

To be reviewed against NFRs

24

Stuck submissions and what happens to the record once they are unstuck (some still showing that they didn’t go through/get approved even though they did)

Please send details of any of these through (via your regional IMT support service) on an individual basis to request sorting. Still happening plus not able to find these pro-actively only notice when trying to revalidate them again

To be reviewed against NFRs

25

Data pull through from TIS core

Inconsistent, missing data, pulling in from and to wrong fields e.g. OOP placements that have no site and appear on main TIS placement list with ( ) do not pull through onto TIS reval – still an issue

To be reviewed against NFRs

26

‘Current placement’ and ‘Grade’ on summary box doesn’t always show current, has on occasion shown future one.  

Not sure why – is this because it is pulling the latest date even if it is in the future? still an issue

To be reviewed against NFRs

27

Random re-ordering of under notice list still an issue

Needs to be the same ordering as used on GMC Connect

To be reviewed against NFRs

TIS Admin related

28

Not being able to delete errors (e.g. ARCP outcomes/episodes) or placements (can be done but not easy as requires placement date to either be a current date or be edited to a current date before deletion allowed)

they are already looking at this. - RESOLVED

To be captured as a requirement

29

Order of assessments tab in main TIS – no logic, hard to read through when trainees have been in programme several years. – this is definitely already tasked and being reviewed.

The plan is for the placements tab format to be replicated for the others including assessments. - RESOLVED 

To be captured as a requirement

30

ID number showing incorrect

Should be GMC/GDC number as the TIS ID number is meaningless (and distracting) – I added this in post meeting as had forgotten. - still an issue

To be captured as a requirement

New requirements

31

Reporting – high level and detailed – need to tie in with revalidation ‘KPIs’ – will include things such as deferral sub-reason, late submissions, not revalidated at CCT (e.g. trainee revalidation submission not made within +/- period of time from outcome 6), also need to report against trainee demographics (e.g. protected characteristics).  Will need to do this for fitness to practice concerns data when this is more comprehensively on TIS (may not sit directly under revalidation module but some teams will be responsible for both)

We are looking at what is / could be provided via the current Tableau report tool – in the South Phil is talking to the IMT team about this and we can share reports / report requirements once we know more. North West have their own front end (Lemon) to pull reports off.  Need to come up with some standard requests??  Nothing available currently via Tableau

To be captured as a requirement

32

Any option for bulk upload for this concerns log (from excel exception report logs or similar)

Still required

To be captured as a requirement

33

Audit - Drs no longer connected – where has all their data gone?

A task has been raised to look at this and how we can access the data.  This is still an issue

To be captured as a requirement

34

F1s – don’t appear on Reval module as not connected but still have fitness to practise issues

We need to think more on this in terms of where anything gets flagged and how we ensure access once they become fully registered (I think that’s what we concluded!)

To be captured as a requirement

35

Ignore button on Drs to add / drs to remove list for those that will always appear but need to stay on or off

Still an issue

To be captured as a requirement