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 5 Next »

The following is a summary of conditions and scenarios that must be in place when the 4 specific actions are taken against a trainee’s record.

General rules

  • Display trainees in editable mode to Local Offices who in current connection

  • Display trainees in non-editable (read only) mode to Local Offices with a past connection


Trigger

Action in RevalConnections

Comments

1

New trainee in TIS

Update record in Revalidation

  • Add connection

(LE) All add connections should be manual? At least for the time being

2

GMC Refresh + no change

No change

3

GMC refresh + update

Update record in revalidation:

  • Add connection

  • Remove connection

4

GMC Refresh + update + DBC does not match programme membership

Update record in revalidation

  • Flag for review + add connection

  • Flag for review + remove connection

[IO] Add / remove depends on GMC refresh request

5

GMC refresh + update + programme membership expired

Update record in revalidation

  • Flag for review + add connection

  • Flag for review + remove connection

[IO] Add / remove depends on GMC refresh request

6

Remove Connection

  • Update in Revalidation immediately

    • If GMC refresh is the same, then no further change required

    • If GMC refresh is not the same, then update the record in Revalidation

    • Show to Local Offices who in current connection

    • Show to Local Offices with past connection

  • Update list to include

    • Trainee has no current programme membership, has designated body

    • No programme membership in TIS (today <CCT date) - this needs to be programme end date not CCT date

      i.e. trainee who is connected but whose programme end date is before today needs to appear in Remove Connection list

    • No programme membership in TIS (today > CCT date)

    • License to Practice removed due to suspension

    • GMC number sent by GMC, but there is no corresponding TIS record

    • trainee whose programme membership end date is < today



Ignore (hide) Connection

  • Allow for trainees who have a current connection

    • Show to Local Offices who in current connection

    • Show to Local Offices with past connection

  • Allow for trainees who do not have a current connection

    • Show to all Local Offices

  • Do not change connection status when applied

  • Do not send to GMC, store on TIS-Reval only

  • Allow refresh via GMC feed, keep in “Hidden” status until removed < new ticket required

  • Automatically update list to include

    • Hide automatically all F1 trainees

    • Hide automatically all Military trainees

    • Trainee has no current programme membership, no designated body



Flag for review

  • Allow for trainees who have a current connection

    • Show to Local Offices who in current connection

    • Show to Local Offices with past connection

  • Allow for trainees who do not have a current connection

    • Show to all Local Offices

  • Display a red flag against trainee in “All” list

    • Show to Local Offices who in current connection

    • Show to Local Offices with past connection

  • Display when filtered against “Review” tab

    • Show to Local Offices who in current connection

    • Show to Local Offices with past connection

  • Do not send to GMC, store on TIS-Reval only

  • Update list to include

    • Allow refresh via GMC feed, keep in review status until removed < new ticket required

    • Add automatically where Programme Membership type = Visitor

    • TIS to GMC API failure

    • Joint programme membership (x2+ designated bodies)

    • No GMC number

    • Overlapping programmes in 2 regions


  • No labels