Logic context
Scenario description | Rules | Actions | Comments | |
---|---|---|---|---|
1 | F1 Doctor | They should not be visible within connections Discrepancies |
| |
2 | Military Doctor | They should not be visible within connections Discrepancies |
| |
3 | Visitors (Associate Dean, Other) | They should be flagged for review |
| How will notifying doctor work? |
4 | Update made via GMC Connect - add/remove connections | This should be reflected within TIS-Revalidation-Connection Discrepancies within 24 hours |
| |
5 | Doctor has current programme membership in TIS, but no designated body connected | They should be added to a designated body if they have a programme membership and today is within the start/end date; only the local office who own the programme should see this |
| How will notifying doctor work? |
6 | Doctor has current programme membership in TIS, but no designated body connected & programme information out of date | They should be added to a designated body if they have a programme membership and today is within the start/end date; only the local office who own the programme should see this. It’s not possible for the system to know their programme membership details are out of date. Both must be true in relation to programme membership in this scenario
|
| How will notifying doctor work? |
7 | Doctor has no current programme membership in TIS, no designated body | They should be hidden At least one of the below must be true in relation to programme membership in this scenario
|
| How will notifying doctor work? |
8 | Trainee has no current programme membership in TIS, has designated body | They should be moved to an exception queue At least one of the below must be true in relation to programme membership in this scenario
|
| How will notifying doctor work? |
9 | TIS to GMC API failure | The last updated date should be displayed across revalidation; resend should be made available |
| |
10 | Designated body removed | They should be added to a designated body if they have a programme membership and today is within the start/end date; only the local office who own the programme should see this Both must be true in relation to programme membership in this scenario
|
| How will notifying doctor work? |
11 | No programme membership in TIS (today <Curriculum end date) | They will need to either (i) have a programme membership added and be connected, or (ii) ignored Trigger: today <programme membership date |
| |
12 | No programme membership in TIS (today > Curriculum end date) | They will need to be removed Trigger: today >programme membership date |
| |
13 | Programme membership and local office changes in TIS | Their connection should be updated Trigger: programme membership changes and owning local office changes Both must be true in relation to programme membership in this scenario
Optional programme membership change
|
| How will notifying doctor and Admin work? |
14 | Joint programme membership Possibilities?
| Any of the local offices should be able to determine which designated body and there should be no further action required; all should be able to view/edit Trigger: no designated body + shared programme membership Both must be true in relation to programme membership in this scenario
|
| |
15 | All trainees | Display full list of trainees associated with admin's local office Trigger: trainee programme membership owning local office = same as admin’s |
| |
16 | No GMC number | They should be moved to Discrepancies Tab (Exception Queue) |
| If there is no training pathway, should the doctor be moved to discrepancies tab? |
17 | Overlapping programmes in 2 regions | The record should be moved to Discrepancies Tab (Exception Queue) Trigger: start date of one programme is before end date of the next + programme in 2 regions |
| Stop |
18 | No current placement | |||
19 | GMC number against 2+ trainees | |||
20 | NEW: GMC Connect to TIS discrepancy | If GMC Connect updates a connection, but it clashes with TIS programme membership detail Flag for review | Flag record for remove | |
21 | NEW: Manual add connection in TIS-Reval to Programme Membership discrepancy | If manual change (add connection) conflicts with TIS programme membership Flag for review | Flag record for remove | |
22 | NEW: remove list should contain any trainee whose programme membership end date is < today | Flag for remove | ||
23 | NEW: GMC number held, but no corresponding TIS record | Flag for remove | ||
24 | NEW: GMC removed in error: move to exception queue | |||
25 | NEW: License to Practice removed due to suspension | Remove connection | ||
26 | “All” filter: requires all trainees who have been connected currently and in the past |