Versions Compared

Key

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

...

No.

Change

Comments

GMC approved Programme Name and Programme Number to be made mandatory for HEE and NIMDTA at the Post details level on Oriel when setting up vacancies.

GMC approved Programme Names and Numbers will be a reference list supplied by HEE and NIMDTA. Programme names and number combinations are unique to each Local Office in HEE and NIMDTA, and would therefore need to be accommodated when setting up the preferences on Oriel vacancies.


Applicable to the following staff groups programmes within HEE and NIMDTA:

  1. Medical & Dental

  2. Public Health

  3. Foundation

17/03: It was eventually agreed that the programme info could not be made mandatory on Oriel as it would affect other staff groups and nations.

‘Dual Training Programme’ field to be made mandatory in the vacancy setup with the option of 'N/A' for HEE and NIMDTA Preferences (Programme and Post level) and supply this in the Offer details and reporting area of Oriel. 

Image RemovedImage Added

Note: For Foundation Programmes and Academic Foundation Programmes, the Programme name and Programme number to be made mandatory on the vacancy setup for HEE and NIMDTA Foundation schools programmes and posts and supply this in the Offer details of the applicant.

Image RemovedImage Added

Applicable to the following staff groups programmes within HEE and NIMDTA:

  1. Medical & Dental

  2. Public Health

  3. Foundation

Programme name and Programme number to be supplied in the Offer details in addition to the below for HEE and NIMDTA posts and programmes in the Oriel reporting area and Oriel workforce extract.

Applicable to the following staff groups programmes within HEE and NIMDTA:

  1. Medical & Dental

  2. Public Health

  3. Foundation

Nationalities on Oriel to be aligned with TIS

...

No.

Dicussions/Assumptions

Comments

1

Moving from current XML based files to the Leave Manager/Accent ETL extension of by Mid March 2021

2

Additional views will be provided by Hicom on the ETL, pulled in the NDW nightly.

3

The assumption is the nightly refresh from Hicom will provide additional rows to the DR rather than only new Offer Accepted applicants on subsequent refresh.

NDW will pull the full set of rows from Hicom DR into the NDW.

Discuss with JT.

4

The data will be kept beyond 13 months of trainees being appointed in their programmes in the NDW.

5

These could be used as a basis to then convert into the TIS bulk upload format

6

Upload and Maintain Oriel Applicant ID’s (Oriel PIN) on TIS

https://hee-tis.atlassian.net/browse/TIS21-1179

  • This will be needed for Foundation applicants without a registration number

  • For potential future linking of Oriel Data in the NDW with TIS data.

  • To link Oriel documents to be pulled across to TIS

7

There would be some level of comparison and tracking of what applicants have/have not been uploaded in the NDW

8

Documents - the links/paths to the files will be provided in the views but not the actual files from Hicom - Further discussion on how to provide the files, might be an S3 bucket that TIS give access to Hicom.

9

Following recent discussions with Hicom, Programme name and number are not going to be mandatory fields on Oriel, therefore leaving scope for potentially unfilled programme info.

10

Current process of onboard Oriel Trainees to TIS is an industry – It needs to be changed but needs careful planning 

Phased approach (Time Frames dependent on Hicom development) 

  • Phase 1: Work in parallel with current process (August intake) 
    - Construct data outputs to exactly match the input requirements of the TIS Person Bulk Upload including Programme Membership Data 
    - Compare outputs of the above to what local teams are adding on to TIS. What is the cause of any difference? Is there anyone ‘missing’ from TIS? 
    - What do we do when the Programme information wasn’t completed in Oriel? How do we decrease this? 

  • Phase 2: Semi-automation (Round 2 Applicants) 
    - Use the lessons learnt above: 
    - Produce an output that can be copied directly into the TIS bulk upload 
    - Produce reports to look at gaps, edge cases, data quality 

  • Phase 3: To be determined by stakeholders 
    - Further integration? 
    - Oriel – TIS API? 

...