The following is a summary of conditions and scenarios that must be in place when the 4 specific actions are taken against a trainee’s record.
...
Add / Remove / Ignore / Review connection lists
Display trainees in editable mode to Local Offices who in current connection
Display trainees in non-editable (read only) mode to Local Offices with a past connection
Ignore connection list
Display trainees in editable mode to all Local Offices, where no current connection
Do not send to GMC
Flag for Review connection list
Display trainees in editable mode to all Local Offices, where no current connection
Do not send to GMC
Display a red flag
Designated body displayed in Revalidation app should align with GMC data, not TCS
Interaction rules
For all manual changes, move the trainee record to applicable filterable list i.e. change the status field, do not automatically update the connection status unless the GMC refresh dictates change
Add connection can only be done where there is no existing connection i.e. “Current connection = no” - restrict Admins from adding connection until they have removed existing one
Remove connection can only be done where there is an existing connection i.e. “Current connection = yes” - restrict Admins from removing connection until they have removed existing one
Ignore connection can be done whether current connection = yes/no
Flag for review can be done whether current connection = yes/no
When a reason is applied because of a change made to a connection, the date that the change is made should fall within the programme membership start and end dates, in order to be associated with a particular trainee + programme membership + DB
Display rules
Display all connections for each programme membership
Refresh add / remove connections intra day
Display confirmation on success
Display confirmation on failure
Add new rows to
Trigger scenario | Action in RevalConnections | Comments | |
|---|---|---|---|
| 1 | New trainee in TIS | Update record in Revalidation
| (LE) All add connections should be manual? At least for the time being |
| 2 | GMC Refresh + no change | No change | |
| 3 | GMC refresh + update | Update record in revalidation:
| |
| 4 | GMC Refresh + update + DBC does not match programme membership | Update record in revalidation
| [IO] Add / remove depends on GMC refresh request |
| 5 | GMC refresh + update + programme membership expired | Update record in revalidation
| [IO] Add / remove depends on GMC refresh request |
| 6 | GMC refresh includes new GMC number + not held in TIS | Update record in revalidation
| |
| 7 | Trainee programme membership removed (in TIS) + DBC | Update record in revalidation
| |
| 8 | Trainee programme membership end date (in TIS) is <CCT date | Update record in revalidation
| |
| 9 | Trainee programme membership end date (in TIS) is <today | Update record in revalidation
| [IO] This is already added to list |
| 10 | Trainee has no programme membership in TIS + today > CCT date | Update record in revalidation
| |
| 11 | License to practice removed from Trainee record | Update record in revalidation
| [IO] How do we know this happens in TIS/Revalidation? |
| 12 | Trainee programme membership is < | Update record in revalidation
| |
| 13 | Admin selects to “Ignore” | Update record in revalidation
| |
| 14 | Admin selects to “Unhide” | Update record in revalidation
| |
| 15 | F1 trainee | Update record in revalidation
| |
| 16 | Military trainee | Update record in revalidation
| |
| 17 | Trainee has no programme membership + no designated body | Update record in revalidation
| |
| 18 | Programme membership type = Visitor | Update record in revalidation
| |
| 19 | Trainee programme membership = joint | Update record in revalidation
| |
| 20 | Trainee programme membership overlaps between 2 regions | Update record in revalidation
| [IO] How will this be known? |
| 21 | GMC API failure | Update record in revalidation
| |
| 22 | GMC number removed in TIS | Update record in revalidation
|
...