Versions Compared

Old Version 17

changes.mady.by.user Ade Oduwole

Saved on

compared with

New Version 18

changes.mady.by.user Ade Oduwole

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Data mismatch scenarios and related business decision  

Status
colourYellow
titleDraft



Data issueScenario Business Decision
1

Not connected to

Local Office

Designated Body

____

Start Date of Programme is in the future

  • New starter recruited but has not started working and not working clinically anywhere else.
  • Overseas doctors

    • These doctors will have records and assigned to programmes to commence in the future

    		Connect to relevant DB
    2
    No Programme Record
    Non Trainee Doctors

    Non-trainee doctors

    - these

    employed directly by HEE and not working clinically anywhere else .

    These are usually Associate/Deputy Deans

    /

    and Programme Managers.

    These are doctors with no Programme record.

    		Connect to relevant DB
    3
    Designated Body Mismatch
    Vistor Trainee

    Visiting training on an Out of

    Programme

    Placement (OOP)

    doctors
  • Doctors on visiting placement

    • These doctors are classed as being outside the flow of training - whilst an OOP doctor is on absence from a programme, they retain the DB of their last programme.

    A doctor on a visiting placement will also retain the DB and of

    arrangement :

    • OOPC - Out of Programme ( on a career break)
    • OOPT - Out of Programme (Training)
    • OOPR - Out of Programme (Research)
    • OOPE - Out of Programme (Experience)

    A visitor trainee will retain their 'home' DB.

    Flag up these records to the Revalidation Administrator however ; this Defence

    The visitor trainee must not be connected to recipient/host DB.

    This is an exception that should not be connected

    4
    Designated Body Mismatch
    Military Trainee Military trainees are managed by the Defence Deanery and not HEE
    Flag up these records to the Revalidation Administrator however ; this
    This is an exception that should not be connected
    5
    No Designated Body
    Provisionally Registered DoctorsProvisionally registered
    doctors -
    trainees on F1 placements
    Flag up these records to the Revalidation Administrator however ; this
    This is an exception that should not be connected
    6Programme End Date has Passed
    • On completion of training programme - ARCP Outcome 6
    • Released from training - ARCP Outcome 4
    • Resignation from programme
    		Disconnect from DB
    7Attached to the wrong Designated BodyTrainees that a wrongly attached to a DB. This discrepancy is likely to be identified on the GMC list of trainees and on investigation, the trainee will not be attached to a programmeDisconnect from DB



    User needs

    Functionality in TIS to enable a Revalidation Administrator to connect or disconnect individual trainees from the designated body**
    Functionality in TIS to enable a Revalidation Administrator to bulk connect or disconnect trainees

    Functionality to flag up to a Revalidation Administrator where a trainee is joining a training programme and needs to be connected:

    • new starters
    • they have had an application to transfer between local offices (Inter-Deanery Transfer) approved and the date of the transfer **
    • have been disconnected inappropriately (i.e. before the end of their training programme or at the end date but before Final ARCP - they don't have an outcome 4/6 - or revalidation has taken place)

    Functionality to flag up to a Revalidation Administrator where trainees are not on a training programme with the DB:

    • they have not yet started their programme and have attached too early
    • they are beyond their Curriculum Completion Date and have an Outcome 6
    • they have an Outcome 4
    • they have resigned from a programme and the date of their last day
    • they have had an application to transfer between local offices (Inter-Deanery Transfer - IDT) approved and the date of the transfer **
    Functionality to flag up to a Revalidation Administrator discrepancies between the GMC Connect list and HEE's database of who should be connected to the local team
    ** As we develop the new core there could/should be functionality to transfer trainees between designated bodies in a single step i.e. not require one local team to disconnect and another team to connect separately. Will need to be built with appropriate approval workflow based on agreed policy and business rules - e.g. which local office (outgoing or incoming) responsible for changing connection NB: IDT's require approval from Postgraduate Deans (Responsible Officers) from both local teams

    ...