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.
...
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
Re the above - we don't need to remove a connection before we add it, we can’t remove connections from another DB (other than the one/ones we are responsible for) but we can add a doctor who is connected to another DB which has the effect of removing them. << [IO] It’s not required in the current system, however to ensure accuracy in the new system, it would be needed as a separate step. In future we can look at how to refine this down.
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
...
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 Trainee appears under the add connection filter | |
| 2 | GMC Refresh + no change | No change
| e.g. Ade the trainee is assigned to east midlands, when the GMC job refreshes the data at night, Ade is still assigned to east midlands - 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 Does a flag mean highlight row in red or something and added to exception queue? [IO] It would mean add to exception queue as well as moving into either the Add or Remove filter - flagging may be useful as a future requirement/enhancement | |
| 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
| Anything for review = move to exceptions queue? [IO] It would mean add to exception queue as well as moving into either the Add or Remove filter - flagging may be useful as a future requirement/enhancement | |
| 7 | Trainee programme membership removed (in TIS) + DBC | Update record in revalidation
| DBC= Programme owner | |
| 8 | Trainee programme membership end date (in TIS) is <CCT date | Update record in revalidation
| CCT date = Curriculum end date in TIS | |
| 9 | Trainee programme membership end date (in TIS) is <today | Update record in revalidation
| [IO] This is already added to list This is the same as Programme membership expired | |
| 10 | Trainee has no programme membership in TIS + today > CCT date | Update record in revalidation
| Note: Programme end date always equal to Curriculum end date except when there is a period of grace where programme end date is greater than Curriculum end date. If there are multiple curriculum then it’s the most recent one) | |
| 11 | License to practice removed from Trainee record | Update record in revalidation
| [IO] How do we know this happens in TIS/Revalidation? We can’t capture this for now until the LRMP is resolved with GMC. Reval Admin to sort out locally | |
| 12 | Trainee programme membership is < CCT date | Update record in revalidation
| Already covered above | |
| 13 | Admin selects to “Hide”/Ignore | Update record in revalidation
| https://hee-tis.atlassian.net/browse/TISNEW-4269 Hide is going to be replaced with Ignore - https://hee-tis.atlassian.net/browse/TIS21-1111 | |
| 14 | Admin selects to manually “Unhide” | Update record in revalidation
| ||
| 15 | Automatic unhide (via GMC refresh) | Update record in revalidation
| ||
| 16 | F1 trainee i.e. Grade = F1 | Update record in revalidation
| Ignore = move to hidden list? Yes, terminology updated | |
| 1617 | Military trainee i.e. Programme membership type = M | Update record in revalidation
| ||
| 1718 | Trainee has no programme membership + no designated body | Update record in revalidation
| ||
| 1819 | Programme membership type = Visitor | Update record in revalidation
| ||
| 1920 | Trainee programme membership = joint | Update record in revalidation
| Review = excpetions queue? [IO] It would mean add to exception queue as well as moving into either the Add or Remove filter - flagging may be useful as a future requirement/enhancement | |
| 2021 | Trainee programme membership overlaps between 2 regions | Update record in revalidation
| [IO] How will this be known? | 21Joint Programme membership is not possible except where dual curriculum in 1 programme. |
| 22 | GMC API failure | Update record in revalidation
| ||
| 2223 | GMC number removed in TIS | Update record in revalidation
| ||
| 24 | Programme membership with dual curriculum (in TIS) | Update record in revalidation
|