Logic context
Scenario description | Rules | Actions | Tab | Comments | MVP? | |
---|---|---|---|---|---|---|
1 | F1 Doctor | Trigger: Placement grade = F1 |
| Hidden Tab only | Doctor appear in All Doctors Tab? Do we really need the All doctor tab? | Y |
2 | Military Doctor | Trigger: Programme membership type = Military |
| Hidden Tab only | Doctor appear in All Doctors Tab? | Y |
3 | Reval Admin manual hide current connected Doctor | Trigger: Manually hide doctor |
| Hidden Tab only? | Should the Doctor still appear in connected? I want to think ‘No’. Doctor appear in All Doctors Tab? | Not Required at all |
4 | Visitors |
|
| If disconnected: Discrepancies Tab (Exception Queue) & Historic Connections tab (Disconnections) only If Connected: Discrepancies Tab (Exception Queue) & Current Connections tab ( Connections) only | How will notifying GMC and doctor work? Nothing to do from our end - Admin will contact doctor Doctor appear in All Doctors Tab?No Visitors in TIS- need to know how to deal with them. Stop: 20/04/2022 | Y |
5 | Update made via GMC Connect During GMC update;
| Should these update be reflected within TIS-Revalidation-Connection Discrepancies within 24 hours? |
| GMC update
Should the update appears in Historic Connections tab (Disconnections) only and also the doctor appear in Discrepancies Tab (Exception Queue)? 2. Doctor is Connected to BDC: Should the update appears in Current Connections tab ( Connections) only and also the doctor appear in Discrepancies Tab (Exception Queue)? | Doctor appear in All Doctors Tab? No | |
6 | DBC not matching | If GMC Connect updates a connection, but it clashes with TIS DBC, should this update be reflected within TIS-Revalidation-Connection Discrepancies within 24 hours | DBC not matching If disconnected; Should the update appears in Historic Connections tab (Disconnections) only and also the doctor appear in Discrepancies Tab (Exception Queue)? If Connected: Should the update appears in Current Connections tab ( Connections) only and also the doctor appear in Discrepancies Tab (Exception Queue)? | |||
7 | Programme membership not matching | If GMC Connect updates a connection, but it clashes with TIS programme membership detail, should this update be reflected within TIS-Revalidation-Connection Discrepancies within 24 hours | Programme Membership not Matching If disconnected; Should the update appears in Historic Connections tab (Disconnections) only and also the doctor appear in Discrepancies Tab (Exception Queue)? If Connected: Should the update appears in Current Connections tab ( Connections) only and also the doctor appear in Discrepancies Tab (Exception Queue)? | |||
8 | GMC number not matching | If GMC Connect updates a connection, but it clashes with TIS GMC Number, should this update be reflected within TIS-Revalidation-Connection Discrepancies within 24 hours | 5GMC number not matching If disconnected; Should the update appears in Historic Connections tab (Disconnections) only and also the doctor appear in Discrepancies Tab (Exception Queue)? If Connected: Should the update appears in Current Connections tab ( Connections) only and also the doctor appear in Discrepancies Tab (Exception Queue)? | |||
9 | Programme Owner removed or changed | Programme Owner removed or changed If disconnected; Should the update appears in Historic Connections tab (Disconnections) only and also the doctor appear in Discrepancies Tab (Exception Queue)? If Connected: Should the update appears in Current Connections tab ( Connections) only and also the doctor appear in Discrepancies Tab (Exception Queue)? | ||||
10 | Programme Membership removed or changed | Programme Membership removed or changed If disconnected; Should the update appears in Historic Connections tab (Disconnections) only and also the doctor appear in Discrepancies Tab (Exception Queue)? If Connected: Should the update appears in Current Connections tab ( Connections) only and also the doctor appear in Discrepancies Tab (Exception Queue)? | ||||
11 | GMC provide trainee not in TIS |
| Connected: Discrepancies Tab (Exception Queue) & Current Connections tab ( Connections) only | |||
12 | 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 |
| If disconnected; Historic Connections tab (Disconnections) only If Connected: Discrepancies Tab (Exception Queue) & Current Connections tab ( Connections) only | How will notifying doctor work? | |
13 | 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
|
| If disconnected; Historic Connections tab (Disconnections) only If Connected: Discrepancies Tab (Exception Queue) & Current Connections tab ( Connections) only | How will notifying doctor work? | |
14 | 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
|
| If disconnected; Historic Connections tab (Disconnections) only If Connected: Discrepancies Tab (Exception Queue) & Current Connections tab ( Connections) only | How will notifying doctor work? | |
15 | 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
|
| If disconnected; Historic Connections tab (Disconnections) only If Connected: Discrepancies Tab (Exception Queue) & Current Connections tab ( Connections) only | How will notifying doctor work? | |
16 | TIS to GMC API failure | The last updated date should be displayed across revalidation; resend should be made available |
| If disconnected; Historic Connections tab (Disconnections) only? should the update appears in Discrepancies Tab (Exception Queue)? If Connected: Discrepancies Tab (Exception Queue) & Current Connections tab ( Connections) only | Doctor appear in All Doctors Tab? | |
17 | 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
|
| If disconnected; Historic Connections tab (Disconnections) only If Connected: Discrepancies Tab (Exception Queue) & Current Connections tab ( Connections) only | How will notifying doctor work? | |
18 | Programme Membership not expired |
| If disconnected; Historic Connections tab (Disconnections) and in Discrepancies Tab (Exception Queue) only If Connected: Discrepancies Tab (Exception Queue) & Current Connections tab ( Connections) only | |||
19 | Programme membership Expired |
| If disconnected; Historic Connections tab (Disconnections) only If Connected: Discrepancies Tab (Exception Queue) & Current Connections tab ( Connections) only | Should it be automatic move to Discrepancies and disconnection or Admin must be allowed manually to disconnect? | ||
20 | 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 |
| If disconnected; Historic Connections tab (Disconnections) only If Connected: Discrepancies Tab (Exception Queue) & Current Connections tab ( Connections) only | ||
21 | No programme membership in TIS (today > Curriculum end date) | They will need to be removed Trigger: today >programme membership date |
| If disconnected; Historic Connections tab (Disconnections) only If Connected: Discrepancies Tab (Exception Queue) & Current Connections tab ( Connections) only | ||
22 | 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
|
| If disconnected; Historic Connections tab (Disconnections) only If Connected: Discrepancies Tab (Exception Queue) & Current Connections tab ( Connections) only | How will notifying doctor and Admin work? | |
23 |
Possibilities?
2. Programme end date not expired but dual curriculum | 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
|
| If disconnected; Historic Connections tab (Disconnections) only If Connected: Discrepancies Tab (Exception Queue) & Current Connections tab ( Connections) only | ||
24 | All trainees | Display full list of trainees associated with admin's local office Trigger: trainee programme membership owning local office = same as admin’s |
| What is the meaning of this? | ||
25 | No GMC number GMC send a GMC number for a doctor who had no GMC number in TIS | They should be moved to Discrepancies Tab (Exception Queue) |
| If disconnected; Historic Connections tab (Disconnections) only If Connected: Discrepancies Tab (Exception Queue) & Current Connections tab ( Connections) only | If there is no training pathway, should the doctor be moved to discrepancies tab? | |
26 | 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 |
| If disconnected; Historic Connections tab (Disconnections) only If Connected: Discrepancies Tab (Exception Queue) & Current Connections tab ( Connections) only | Stop | |
27 | No current placement | Related to 20 and 23? | ||||
28 | GMC number against 2+ trainees | Is it more more than one doctor having the same GMC number? | ||||
29 | INACTIVE Doctors in TIS | Related to 18 and 23? | ||||
30 | Hide doctor with current connection | Admin should be able to hide connected doctor though the doctor stays connected | ||||
31 | 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
| |||
32 | NEW: remove list should contain any Doctor whose programme membership end date is < today | programme membership expires | Flag for remove
| Related to 18 and 20? | ||
33 | NEW: GMC Number removed in error | No GMC number in TIS but GMC number in GMC |
| Is it possible to have a doctor without GMC number in GMC? | ||
34 | NEW: License to Practice removed due to suspension | Remove connection | How do we no this in TIS Reval? | |||
35 | “All” filter: requires all trainees who have been connected currently and in the past | Are we saying All filter should have all doctors connected and disconnected? |
0 Comments