Logic context
...
Scenario description
...
Rules
...
Actions
...
Appear in which Tab? Y/N
...
Comments
...
MVP?
...
F1 Doctor
...
Trigger: Placement grade = F1
...
Hide Doctor
...
Hidden Tab only- Y
Doctor appear in All Doctors Tab? Do we really need the All doctor tab?
...
Y
...
Military Doctor
...
Trigger: Programme membership type = Military
...
Hide Doctor
...
Hidden Tab only Y
...
Doctor appear in All Doctors Tab?
...
Y
...
Reval Admin manual hide current connected Doctor
...
Trigger: Manually hide doctor
...
Hide Doctor
...
Hidden Tab only? N/R
...
Should the Doctor still appear in connected? I want to think ‘No’.
Doctor appear in All Doctors Tab?
...
Not Required at all
...
Visitors
...
Add to Discrepancies Tab (Exception Queue) (also need to be able to add/remove connections and add comment reason manually)
...
Visible to all local offices Associated to the DB? is it for that associated DB or all DBs?
...
Logic context
Scenario description | Rules | Actions | Appear in which Tab? Y/N | Comments | MVP? | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | F1 Doctor | Trigger: Placement grade = F1 |
| Hidden Tab only- Y | 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 Y | Doctor appear in All Doctors Tab? | Y | |||||||||||
3 | Reval Admin manual hide current connected Doctor | Trigger: Manually hide doctor |
| Hidden Tab only? N/R | 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 doctor current connection is NO:
If doctor current connection is YES
| 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? |
| If doctor current connection is NO:
If doctor current connection is YES
| Doctor appear in All Doctors Tab? No | ||||||||||||
6 | DBC removed | They should be added to a designated body if they have a programme membership and today is within the start/end date; Both must be true in relation to programme membership in this scenario
|
| If doctor current connection is NO:
If doctor current connection is YES
| |||||||||||||
7 | DBC not matching for both TIS and GMC | 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 | If doctor current connection is NO:
If doctor current connection is YES
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
| ||||||||||
8 | 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 | If doctor current connection is NO:
If doctor current connection is YES
| ||||||||||||||
9 | 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? Add to Discrepancies Tab (Exception Queue)? Connection Discrepancies within 24 hours | If doctor current connection is NO:
If doctor current connection is YES
| Doctor appear in All Doctors Tab? No | 6 | DBC removed | They should be added to a designated body if they have a programme membership and today is within the start/end date; Both must be true in relation to programme membership in this scenario
| ||||||||||
10 | No GMC number GMC send a GMC number for a doctor who had no GMC number in TIS |
If doctor current connection is NO:
| If doctor current connection is YESNO:
| 7 | DBC not matching for both TIS and GMC | 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
If doctor current connection is NO:YES
If doctor current connection is YES
| This also should cover if 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? | ||||||||||
11 | GMC number against 2+ trainees |
| 8 | 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
| If doctor current connection is NO:
If doctor current connection is YES
| 9 | 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|||||||||
12 | No training pathway |
| If doctor current connection is NO:
If doctor current connection is YES
| 10
| If there is no training pathway in TIS, should the doctor be moved to discrepancies tab? | ||||||||||||
13 | Programme Owner removed or changed in TIS | Their connection should be updated Trigger: owning local office changes |
| If doctor current connection is NO:
If doctor current connection is YES
| |||||||||||||
1114 | Programme Membership removed or changed in TIS | Their connection should be updated Trigger: programme membership changes Both must be true in relation to programme membership in this scenario
Optional programme membership change
|
| If doctor current connection is NO:
If doctor current connection is YES
| |||||||||||||
1215 | GMC provide doctor not in TIS |
| If doctor current connection is NO:
If doctor current connection is YES
| Can TIS- Reval app capture such doctors from GMC? Is All Doctor tab populated from GMC or TIS (Question for the devs)? | |||||||||||||
1316 | Doctor has current programme membership in TIS, not connected to DBC & programme end date is today or in the future | They should be added to a designated body if they have a programme membership and today is within the start/end date. Both must be true in relation to programme membership in this scenario
|
| If doctor current connection is NO:
| |||||||||||||
1417 | Doctor has no current programme membership in TIS, and not connected to DBC | They should be hidden At least one of the below must be true in relation to programme membership in this scenario
|
| Hidden Tab only | |||||||||||||
1518 | Doctor has no current programme membership in TIS, but connected to a DBC | 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 doctor current connection is YES
| |||||||||||||
1619 | No programme membership in TIS but with curriculum (today <Curriculum end date) | They will need to either (i) have a programme membership added and be connected, or (ii) Hidden Trigger: today <programme membership end date |
| If doctor current connection is NO:
If doctor current connection is YES
| |||||||||||||
1720 | No programme membership in TIS but with curriculum (today > Curriculum end date) | They will need to either (i) have a programme membership added and be connected, or (ii) Hidden Trigger: today >programme membership end date |
| If doctor current connection is NO:
If doctor current connection is YES
| |||||||||||||
1821 | Doctor Connected to a DBC and Programme Membership not expired |
| If doctor current connection is YES
| ||||||||||||||
1922 | Doctor Connected to a DBC and Programme membership Expired |
| If doctor current connection is YES
| Admin allowed to manually to disconnect | |||||||||||||
2023 | Manual add connection in TIS to GMC API failureThe last updated date should be displayed across revalidation; resend should be made available | If manual change (add connection) and there is conflicts with TIS programme membership |
| If doctor current connection is NO:
If doctor current connection is YES
| 21 |
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
| ||||||||||
24 | No current placement | Also without current but with future placement? | |||||||||||||||
25 | TIS to GMC API failure | The last updated date should be displayed across revalidation; resend should be made available |
| If doctor current connection is NO:
If Connected:doctor current connection is YES
| 22 | 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? | 23 | 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)||||||
26 |
Possibilities?
2. Dual curriculum and Programme end date not expired | Trigger: no designated body + shared programme membership Both must be true in relation to programme membership in this scenario
|
| For Joint programme If doctor current connection is NO:
If doctor current connection is YES
For Dual curriculum Add toIf there is no training pathway, should the doctor be moved to discrepancies tab? | 24 | 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 | doctor current connection is NO:
If doctor current connection is YES
If disconnected; Historic Connections tab (Disconnections) only If Connected
| Expired programme membership for the two scenarios? If doctor current connection is NO:
| Stop | 25 | No current placement | Related to 20 and 23? | 26 | GMC number against 2+ trainees | Is it more more than one doctor having the same GMC number
| |
27 | INACTIVE Doctors in TIS | Related to 18 and 23? | 28 | Hide doctor with current connection | Admin should be able to hide connected doctor though the doctor stays connected | 29 | NEW: Manual add connection in TIS-Reval to Programme Membership discrepancy | If manual change (add connection) conflicts with TIS programme membership Flag for review | 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? | Not Required? | ||||
28 | Overlapping programmes in 2 regions | Trigger: start date of one programme is before end date of the next + programme in 2 regions |
| 30 | NEW: remove list should contain any Doctor whose programme membership end date is < today | programme membership expires | Flag for remove
| If doctor current connection is NO:
If doctor current connection is YES
| |||||||||
29 | INACTIVE Doctors in TIS | 31 | NEW: GMC Number removed in error | No GMC number in TIS but GMC number in GMC | If doctor current connection is NO:
| Related to 18 and 20? |
If doctor current connection is YES
| Is it possible to have a doctor without GMC number in GMC? | 32
| ||||||||
30 | Hide doctor with current connection | Admin should be able to hide connected doctor though the doctor stays connected | |||||||||||||||
31 | NEW: License to Practice removed due to suspension | Remove connection | How do we no this in TIS Reval? | 33 | “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? |