Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Logic context

Scenario description

Rules

Actions

Comments

1

F1 Doctor

They should not be visible within connections Discrepancies
Trigger: Placement grade = F1

  • Hide Doctor

2

Military Doctor

They should not be visible within connections Discrepancies
Trigger: Programme membership type = Military

  • Hide Doctor

3

Visitors (Associate Dean, Other)

They should be flagged for review
Trigger: Programme membership type = Visitor

  • 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? is it for that associated DB or all DBs?

  • When change is made, send to GMC and notify Visitor. What change(s) do we need to send to GMC?

How will notifying doctor work?

4

Update made via GMC Connect - add/remove connections

NEW: GMC Connect to TIS discrepancy

During GMC update, if

  • DBC not matching

  • Programme membership not matching

  • GMC number not matching

This should be reflected within TIS-Revalidation-Connection Discrepancies within 24 hours
Trigger: GMC refresh (nightly??)

If GMC Connect updates a connection, but it clashes with TIS programme membership detail

Flag for review

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
Trigger: current programme membership + no designated body linked

  • Add to Discrepancies Tab (Exception Queue) (also need to be able to add/remove connections and add comment reason manually)

  • Flag to add connection < can this be automated based on programme membership owner? Do we need flag?

  • When change is made, send to GMC and notify doctor

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.
Trigger: current programme membership + no designated body linked

Both must be true in relation to programme membership in this scenario

  • start date = today or older than today

  • end date = tomorrow and all future dates

  • Add to Discrepancies Tab (Exception Queue) (also need to be able to add/remove connections and add comment reason manually)

  • Flag to add connection < can this be automated based on programme membership owner? Do we need flag?

  • When change is made, send to GMC and notify doctor

How will notifying doctor work?

7

Doctor has no current programme membership in TIS, no designated body

They should be hidden
Trigger: No programme membership + no designted body

At least one of the below must be true in relation to programme membership in this scenario

  • start date = future or no date

  • end date = past, future or no date

  • Hide Doctor

  • Visible to all local offices. is it for that associated DB or all DBs?

  • When change is made, send to GMC and notify doctor

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
Trigger: No programme membership + designted body

At least one of the below must be true in relation to programme membership in this scenario

  • start date = future or no date

  • end date = past, future or no date

  • Add to Discrepancies Tab (Exception Queue) (also need to be able to add/remove connections and add comment reason manually)

  • Remove connection

  • Visible to all local offices. is it for that associated DB or all DBs?

  • When change is made, send to GMC and notify doctor

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
Trigger: failed GMC update notification ??

  • Add to Discrepancies Tab (Exception Queue)

  • Visible to Local Office associated with the connected designated body only

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
Trigger: current programme membership + no designated body linked

Both must be true in relation to programme membership in this scenario

  • start date = today or older than today

  • end date = tomorrow and all future dates

  • Add to Discrepancies Tab (Exception Queue) (also need to be able to add/remove connections and add comment reason manually)

  • Flag to add connection < can this be automated based on programme membership owner? Do we need flag?

  • When change is made, send to GMC and notify doctor

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

  • Add to Discrepancies Tab (Exception Queue

  • Remove any connection

  • Visible to all Local Offices. is it for that associated DB or all DBs?

12

No programme membership in TIS (today > Curriculum end date)

They will need to be removed

Trigger: today >programme membership date

  • Add to Discrepancies Tab (Exception Queue)

  • Remove any connection

  • Archive. Should this be hidden rather than archive?

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

  • start date = today or older than today

  • end date = tomorrow and all future dates

Optional programme membership change

  • programme name change

  • Automatically update connection

  • When change is made, send to GMC and notify Doctor & admin?

How will notifying doctor and Admin work?

14

Joint programme membership

Possibilities?

  1. No DB

  2. one DB?

  3. More than one DBs?

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

  • start date = today or older than today

  • end date = tomorrow and all future dates

  • two / joint programme name applied to doctor

  • Add to Discrepancies Tab (Exception Queue)

  • Visible to all Local Offices associated with the connected programme membership

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

  • Read only

What is the meaning of this?

16

No GMC number

They should be moved to Discrepancies Tab (Exception Queue)
Trigger: No GMC number and something else that determines they are on a “doctor” training pathway”

  • Add to Discrepancies Tab (Exception Queue)

  • Visible to all Local Offices associated with the connected programme membership

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

  • Add to Discrepancies Tab (Exception Queue)

  • Visible to all Local Offices associated with the connected programme membership

Stop

18

No current placement

Related to 20 and 23?

19

GMC number against 2+ trainees

Is it more more than one doctor having the same GMC number?

20

INACTIVE Doctors in TIS

Related to 18 and 23?

21

Hide doctor with current connection

Admin should be able to hide connected doctor though the doctor stays connected

22

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

  • Add to Discrepancies Tab (Exception Queue)

  • Visible to all Local Offices associated with the connected programme membership

23

NEW: remove list should contain any Doctor whose programme membership end date is < today

programme membership expires

Flag for remove

  • Add to Discrepancies Tab (Exception Queue)

  • Visible to all Local Offices associated with the connected programme membership

Related to 18 and 20?

24

NEW: GMC Number removed in error

No GMC number in TIS but GMC number in GMC

  • Add to Discrepancies Tab (Exception Queue)

  • Visible to all Local Offices associated with the connected programme membership

Is it possible to have a doctor without GMC number in GMC?

25

NEW: License to Practice removed due to suspension

Remove connection

How do we no this in TIS Reval?

26

“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?

  • No labels