Logic context
Scenario description | Rules | Actions | Comments | |
|---|---|---|---|---|
| 1 | F1 trainee | They should not be visible within connections discrepancies |
| (LE) Can we check what the current trigger is on this - i think it is licence to practise status and grade e.g prov registration and F1 = do not show as needing connection (IO) TBC |
| 2 | Military trainee | They should not be visible within connections discrepancies |
| |
| 3 | Visitors (Associate Dean, Other) | They should be flagged for review |
| (LE) Not all of these will be on TIS core in any format so the visitor type wouldn't always be applicable. (IO) if they’re not on TIS, then we won’t know about them. |
| 4 | Update made via GMC Connect - add/remove | This should be reflected within TIS-Revalidation-Connection Discrepancies within 24 hours |
| ify.onyenokweorhiunu (Unlicensed) should this be hide from list? |
| 5 | Trainee has current programme membership, 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 |
| (LE) Need to be careful with automated connection as if trainee has overlapping programmes in 2 regions (sometimes happens) this would start a tug of war! (IO) possible to flag for review in this instance, will add to the scenario list. |
| 6 | Trainee has current programme membership, 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
|
| (LE) If we are using programme start/end date then they will show up as needing to be connected, if dates are wrong they won’t show up in either list (if not connected) (IO) Correct, the fact that their details are incorrect would be out of scope for our logic to look for, or correct. |
| 7 | Trainee has no current programme membership, no designated body | They should be hidden At least one of the below must be true in relation to programme membership in this scenario
|
| (LE) These would be the ones that shouldn't be connected (if data is correct), if we had these in a list we would have 1000+s in here so don't think we need to see them? (IO) they can be automatically hidden instead, and searchable if needed. |
| 8 | Trainee has no current programme membership, 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
|
| (LE) We would need to be able to mark these ones to not show up in remove list if there is a reason they must stay connected even if no programme membership/valid dates - this logic would work for the non-trainees that need connecting. (IO) Yes, placing them in the exception queue would enable you to manually add/remove/ignore as required. |
| 9 | TIS to GMC API failure | The last updated date should be displayed across revalidation; resend should be made available |
| Where GMC doesn’t positively receipt an update, the state will not be updated in TIS. |
| 10 | Designated body removed | Follows scenario 5 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
|
| (LE) Need to be careful with automated connection as if trainee has overlapping programmes in 2 regions (sometimes happens) this would start a tug of war! (IO) noted. |
| 11 | No programme membership in TIS (today <CCT date) | They will need to either (i) have a programme membership added and be connected, or (ii) ignored Trigger: today <programme membership date |
| (LE) Needs to use programme end date not CCT date as the trigger date as trainees stay connected whilst in period of grace (up to 6mths after CCT date). If they don't have a period of grace then prog end date would be the same as CCT date anyway. (IO) updated |
| 12 | No programme membership in TIS (today > CCT date) | They will need to be removed Trigger: today >programme membership date |
| (LE) Needs to use programme end date not CCT date as the trigger date as trainees stay connected whilst in period of grace (up to 6mths after CCT date). If they don't have a period of grace then prog end date would be the same as CCT date anyway. (IO) updated |
| 13 | Programme membership + local office changes in TIS | Their connection should be updated Trigger: programme membership changes + owning local office changes Both must be true in relation to programme membership in this scenario
Optional programme membership change
|
| (LE) I think these scenarios (where a trainee moves into a new region) would just need to show in the new regions ‘add connection’ list rather than do it automatically. (IO) what would be the driver to doing this manually instead of automatically? (LE) Mainly not convinced data is currently robust enough for this to not cause lots of issues. Perhaps this could be an option for later on? (IO) When you say ‘robust” what do you mean specifically, in case there’s anything we can do additionally to support this challenge? I ask as this wasn’t raised as an issue with other local offices, so I want to make sure that the experience is consistent and meets everyone’s needs. |
| 14 | Joint programme membership (x2+ designated bodies) | Any of the local offices shouold 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
|
| (LE) Need to then be able mark it to ignore so the same trainees don’t continue to appear in the add/remove lists of each of the local offices. (IO) Yes, placing them in the exception queue would enable you to manually add/remove/ignore as required. |
| 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 |
| (LE) This would be the same list as the 'all doctors; list in main revalidation recommendation section. (IO) there are no designated bodies in the All doctors list, and other columns would differ, as well as the actions that can be taken, so not quite. |
| 16 | No GMC number | They should be moved to an exception queue |
| |
| 17 | Overlapping programmes in 2 regions | The record should be moved to an exception queue Trigger: start date of one programme is before end date of the next + programme in 2 regions |
| |
| 18 | No current placement | Alistair Pringle (Unlicensed) will this impact Connections at all? i don’t believe so no because the DB (Local Office) is taken from the Programme membership. | ||
| 19 | GMC number against 2+ trainees | Alistair Pringle (Unlicensed) Possibly but this is not possible on TIS so shouldn’t be an issue. GMC numbers have to be unique and cannot be duplicated on creation of a trainee record. | ||
| 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 | Reason is that full list comes from GMC, so there are edge cases | |
| 24 | NEW: GMC removed in error: move to exception queue | |||
| 25 | NEW: License to Practice removed due to suspension | Remove connection | Need to confirm how we can get this? | |
| 26 | “All” filter: requires all trainees who have been connected currently and in the past |
State-Event Flow
The below diagram illustrates the various states and actions that can be taken against a trainee record in relation to their Connection Status in TIS/GMC Connect.
Key assumptions
Users can view all programme membership types associated with their local offices via a specific filter
Users can view each “state” related record via a specific filter
Disconnected - all local offices can view all disconnected records
Connected - each local office can only view those records associated with their local office (current & past)
Exception - all local offices can view all exception records
Hidden - all local offices can view all hidden records
Users can only take the following actions
Add connection
Remove connection
Review connection
Ignore connection
Add Comment