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? To ask Users again All tab logic is complex to implement, we want to suggest Post MVP is required. | Y |
2 | Military Doctor | Trigger: Programme membership type = Military |
| Hidden Tab only Y | Doctor appear in All Doctors Tab? | Y |
3 | Reval Admin manually 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? 29/06/2022:Hide connection should only be in Exception | Required |
4 | Visitors | Trigger: Programme membership type = Visitor |
| If doctor current connection is YES
| Doctor appear in All Doctors Tab?No Stop: 20/04/2022 | Y |
5 | Update made via GMC Connect Doctor is Connected to a DBC (Add connection) | Should these update be reflected within TIS-Revalidation-Connection Discrepancies within 24 hours? |
| If doctor current connection is NO:
| Doctor appear in All Doctors Tab? No This is overnight sync | OK |
6 | Update made via GMC Connect Doctor is disconnected from a DBC (Remove connection) | Should these update be reflected within TIS-Revalidation-Connection Discrepancies within 24 hours? |
| If doctor current connection is YES
| Doctor appear in All Doctors Tab? No This is overnight sync | OK |
7 | DBC removed/remove connection | 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 YES
| If a doctor/Admin mistakenly remove DBC or disconnect a doctor either from TIS- Reval or GMC Connect. | OK |
8 | 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? | <<Current connection according to GMC>> | If doctor current connection is YES
| OK | |
9 | 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 YES
| OK | ||
10 | 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 | If doctor current connection is YES
| GMC never changes. ? Can the doctor edit their number on GMC Connect ? ? Assumption that a changed GMC No on TIS will lead to that doctor being “unmatched” - thus move doc to discrepancy. | see question | |
11 | No GMC number in TIS GMC send a GMC number for a doctor who had no GMC number in TIS |
| If doctor current connection is YES
| This also should cover if GMC Number is 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? If yes, should we also send to discrepancies? ? Assumption that if NO GMC No on TIS will lead to that doctor being “unmatched” - thus move doc to discrepancy. ? How is GMC recorded when unknown or null. | see question | |
12 | GMC number against 2+ doctors | Two doctors having the same GMC number |
| If doctor current connection is YES
| There’re existing GMC numbers against 2+ doctors in TIS (see https://build.tis.nhs.uk/metabase/question/461) | Not required as not possible to duplicate GMC No as this is flagged and record cannot be saved |
13 | No training pathway in TIS |
| If doctor current connection is YES
| If there is no training pathway in TIS, should the doctor be moved to discrepancies tab? Any update to the Training Pathway should move to discrepancies? This refers to the programme training pathway CCT, CESR, NA etc… | <<< Next session start >>> | |
14 | Programme Owner removed or changed in TIS | Their connection should be updated Trigger: owning local office changes |
| If doctor current connection is YES
| ||
15 | 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 YES
| ||
16 | GMC provide doctor not in TIS |
| 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)? | ||
17 | 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:
| ||
18 | 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 | ||
19 | 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
| ||
20 | 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 YES
| We don’t think this possible in TIS | |
21 | 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 YES
| We don’t think this possible in TIS | |
22 | Doctor Connected to a DBC and Programme Membership not expired |
| If doctor current connection is YES
| |||
23 | Doctor Connected to a DBC and Programme membership Expired |
| If doctor current connection is YES
| Admin allowed to manually to disconnect Should this be automated? | ||
24 | Manually add connection in TIS-Reval to Programme Membership and there is discrepancy with TIS programme membership | If manual change (add connection) and there is conflicts with TIS programme membership |
| If doctor current connection is YES
| ||
25 | No current placement Scenarios
| |||||
26 | TIS to GMC API failure | The last updated date should be displayed across revalidation; resend should be made available |
| If doctor current connection is YES
| For individual doctor connection/disconnection using API | |
27 |
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 YES
For Dual curriculum If doctor current connection is YES
| Expired programme membership for the two scenarios? If doctor current connection is NO:
| |
28 | 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? | |
29 | Overlapping programmes in 2 regions | Trigger: start date of one programme is before end date of the next + programme in 2 regions |
| If doctor current connection is YES
| ||
30 | INACTIVE Doctors in TIS | If doctor current connection is YES
| ||||
31 | Hide doctor with current connection | Admin should be able to hide connected doctor though the doctor stays connected | Hidden Tab Current Connections Tab | |||
32 | NEW: License to Practice removed due to suspension | Remove connection | How do we no this in TIS Reval? |
Add Comment