Page Content
- Background
- Diagram for Proposed Business Process to Import Trainees from Oriel into TIS
- Excel workbook with fields from Oriel that will be extracted and stored and those that will not
- Excel workbook with Reference Data mapping
- Immigration Statuses Reference data from Oriel for 2017 and 2018
- Discussion and Assumptions
1. Background:
The TIS-Oriel integration is a file based export from Oriel of Trainee details and the programmes they've been accepted on to. This will include Trainees that are new to TIS and those who have already been on TIS programmes. New Trainees will cause Trainee record creation and user on-boarding within Trainee User Management.
2. MVP - Proposed Business Process to Import Trainees from Oriel into TIS:
TIS Recruitment Import Template:
TIS Recruiment Import Template v0.3.xlsx
Oriel Custom Report
Custom Oriel Report for TIS v0.1.xlsx
3. Excel workbook with fields from Oriel that will be extracted and stored and those that will not.
Oriel - Trainees Import to TIS v0.1.xlsx
4. Excel workbook with Reference Data mapping
Reference Data - Oriel to Intrepid mapping v2.xlsx
Reference Data - Oriel to Intrepid and ESR mapping v5.xlsx
5. Immigration Statuses Reference data from Oriel for 2017 and 2018
Immigration Statuses Discrepancies - v3.0.xlsx
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
6. Discussion and Assumptions:
...
Agreed that wherever possible we will adopt Oriel ref tables to avoid having differences and having to map the data. Ashley to check impact on ESR interface to determine which tables we can do this for.
Agreed that nationality will have to align with ESR as data passes through interface so this must be mapped.
...
Data Leads
...
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
...
Data Leads
...
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
...
In the workbook on sub heading 3, there are fields that are on the Recruitment Import template but not Oriel. Which of these fields are required in the template and where would these be sourced from?
Which of these should be mandatory?
...
Feedback received from Claire and Alice as to which one to keep on the template and which one to remove.
Draft version consolidated and added to dev story.
Concern over mandatory fields in the template. E.g. DOB may not be available for non-trainees.
Data Leads
...
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
...
Data Leads
...
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
...
Agreed not to map and just take Oriel values as Intrepid data is not accurate and up to date.
Regarding the 2 new questions added for immigration on 2018 application form in Oriel, the recommendation is to record these as 2 new fields on TIS.
- 1) Blue card registration question,
- 2) Is this your own visa or are you a dependent?
Oriel to fix their extract to send those values.
...
Data Leads
...
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
...
Data Leads
...
Table of Contents |
---|
Items Definition
Items | Definition | Comment |
---|---|---|
Trainee Records | ||
Programme | ||
Curriculum | ||
Placement | ||
Rotation | ||
Specialty | ||
Core Specialty | ||
Academic Specialty | ||
Higher Specialty | ||
Foundation |
(Current Work) Draft Presentation Slide
View file | ||
---|---|---|
|
(Current Work) High Level as-is Activity Flow
Drawio sketch | ||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
(Current Work) Analysis of the current Process
Activity | E&W Midlands | Y&H | NW | NE | SW | London | Wessex | TV | EOE |
Download Records with relevant documents: Who performs this role? |
|
|
|
|
|
|
|
| |
---|---|---|---|---|---|---|---|---|---|
Download Records with relevant documents: How many people in the LO has got access to Oriel to the full report- Super User? |
|
|
|
|
|
|
|
| |
Download Records with relevant documents: How often is the download made? |
|
|
|
|
|
After the recruitment team saved the CSV file as XIsx file in SharePoint; At 10pm, BI/Dev app;
At 8:30am
|
| Reports are ran based on National timeline | |
Download Records with relevant documents: Any Document downloaded with Report? |
|
|
|
|
|
|
|
| |
Reports Type: Type of reports? |
| 4 reports generated without Foundation:
3 Foundation Reports:
|
|
|
|
|
|
| |
Reports Type: What format? |
|
|
|
|
|
|
|
| |
Reports Type: Where is the report saved? |
|
|
|
|
|
|
|
| |
Mapping of reports: Who does the mapping? |
|
|
|
|
|
|
|
| |
Mapping of reports: Link to process |
|
|
|
|
|
|
|
| |
Mapping of reports What template is use? |
|
|
|
| Other Programmes:
Foundation:
|
| Foundation
GP:
Other Programme
|
| |
Mapping of reports: What software/app is used? |
Note:
|
|
Note
|
|
|
|
|
| |
Bulk Upload data Person Record to TIS: Is TIS People Bulk Template used? |
|
|
|
|
|
|
|
| |
Bulk Upload data Person Record to TIS: Who Upload to TIS |
|
|
|
|
|
|
|
| |
Bulk Upload data Person Record to TIS: What Template? |
|
|
|
|
|
| Foundation:
GP:
Other Programmes:
| Foundation
Other specialties
| |
Bulk Upload/Upload Placement: Is TIS template in use to add Placement? |
|
|
|
|
|
|
|
| |
Bulk Upload/Upload Placement: Who add placement |
|
|
|
|
|
|
|
| |
Bulk Upload/Upload Placement: What Template? |
|
|
|
| Bulk placement template |
| Foundation:
GP
Other Programme
|
| |
Is it the same process for Foundation and other specialties? |
|
|
|
|
|
|
|
| |
Pains/Challenges |
|
| Pain Point form Other Specialties:
Pain Points from Foundation
| Pain Point
| Pain Point
| Pain Points
| Pain Points
|
| |
Other Comments | See body of the process | See body of the process | See body of the process | See body of the process | See body of the process | See body of the process | See body of the process | See body of the process |
(Current Work) Pain Point Summary
Theme | Pain Point | Note |
---|---|---|
Oriel - TIS fields Mapping |
| |
Visa and Qualification |
| |
Oriel Fields and data |
| |
Rotation; Programme and Curriculum |
| |
Post Number and Oriel Reference Number |
| |
Access to Oriel |
| |
Reports creation |
| |
TIS and LO Spreadsheet Templates |
| |
CoP Deadline |
|
(Current Work) Issues/Questions/Feedback/Discussion and Assumptions
# | Question/Feedback/Issue | Description | Who raised it? | Owner | Jira Ticket | |||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Mapping and Analysing LOs process | This ticket was raised by the TIS data team. Mapping sessions was carried out by the BA and the TIS data Team with each LO 20/05/2024: Closed | Data Lead |
|
Custom report can be built on Oriel to extract a list of trainees for specific programme/s where they have accepted an offer or withdrawn after accepting. This task is to:
- Define the fields for the Custom Report
- Create the report template with support from Ashley on Oriel to be run by LO
- Test the Report
Ashley and Claire met to discuss and Recruitment lead is currently working on this.
Concern raised over Dental trainees. They are expected to use the agreed approach in order to import trainees from Oriel into TIS.
Ashley - To speak to Joanne Watson (Unlicensed) Alistair Pringle (Unlicensed), to add channel on Microsoft Teams to get feedback over: - Done
- Agreed process
- Recruitment Import Template fields
- Oriel Custom Report/extraction to support bulk upload
Data Leads
| ||||||||||||
2 | ‘Offer Accepted’ in more than one region | Investigate why PersonApplicationIDs have multiple rows of OfferAccepted in different regions. For PersonApplicationID 16167B26-EF31-44B8-AD64-6001EC9D0DCA there are two records with ApplicationStatus of OfferAccepted for the VacancyID GPNRO/24-25/3864/800/1-R1A, one is in the Northwest and the other in the West Midlands. 20/05/2024: Oriel Team raised with Hicom and no update from Hicom. Action: To be part of discussion around minimum dataset 23/05/2024: Met with Oriel Team. They will get an update from Hicom on this issue. | Lauren Squires | |||||||||
3 | Address lines 2 and 3 having validation in Bulk Upload template | This is not the case in the UI yet 20/05/2024: Option1 - Oriel to make a change Option 2 : James to write an sql change Option 3: Do something on TIS bulk upload? Action: James Harris James to raise with Oriel Team for option 1 and if no appetite, then options 2 or 3 23/05/2024: Met with Oriel Team. Option 1 is not currently possible but may be in the future. Will action Option 2 and investigate Option 3 in the medium term. | ||||||||||
Request for the following fields to be added
Should Public health applicant type be added to the list? | OfferPreference is different to OfferDescription. This field allows for users to know the difference between rotation zones, e.g. GP Programmes in the Midlands if they are North/South/etc. Lauren: Only relevant for PH, but it determines whether they've been appointed to the Medical or Non-Medical route. James Response: We can but I'll wait to here an update on the above first as I am concerned giving a series of new requests before the others are completed will slow the above down. Lauren: That's fine, I'm not sure if other regions split these out by programme so it might just be the Midlands that cares about that information, I already have the information for this first intake and there's not likely to be much change in applicants so not urgent for being able to use the data for Round 2 like some of the other requested fields 20/05/2024: Oriel Team raised with Hicom and no update from Hicom. Action: To be part of discussion around minimum dataset 23/05/2024: Met with Oriel Team. They will get an update on those already requested and submit those not as an additional request. | James Harris Lauren Squires |
|
|
The Recruitment Import template may need to be changed to have new columns or some columns removed if not needed. For e.g. ApplicantID may need to be added to accomodate for the above Process.
Some of the columns in the current Recruitment import template in its current format, will overlap with the fields that are received from Oriel. Do we want to keep them in the template?
Which of the overlapped fields would be best to be manually filled?
ApplicantID will be added. - Done
Next steps are:
a) Map the reference values for ESR to Oriel/TIS
b) Confirm the mandatory fields in the ESR inbound file.
SImilar action to #3.
ApplicantID = ORIEL PIN
Data Leads
| ||||||||||||
Oriel-TIS Data Mapping to person upload template: Some records having Visitor, visa / PLAB visa / Business Visitor visa' in the permit to work column. Does anyone know what the suitable TIS value is? | Mike Richardson Response: None of the values on the dropdown seem appropriate for that. James Response: I think Skilled worker is probably correct but I can check with Gemma Walker who is the lead for OST. Is that the only value in question? Andrew’s Response: That's the only one on my particular download that didn't upload and on checking have an obvious other value. Having a google over lunch it appears most people can visit the UK for 6 months without requiring a VISA, and that includes allowing them to do to things like the PLAB exam. So they probably don't actually have or have a need for a VISA, at the point of application anyway. They will likely need one now I imagine as they've been appointed, but that will be different to that value on their application form. James Response: That doesn't really seem like a 'Permit to work' as it's a visitor visa Gemma has confirmed that leaving it blank would be the best option as they will not be on a visitor visa when they actually start. James: Made PersonalImmigrationStatus out as blank for 'Visitor visa / PLAB visa / Business Visitor visa' in the SQL 20/05/2024: Closed | Andrew Horton | ||||||||||
Are the values on TIS going to be updated, to be in line with Oriel (assuming they are using the up to date list)? | James Harris Response : Oriel is not actually the best list. I went through this with the lead for the Overseas Sponsorship Team and the TIS list is accurate. The misalignment on this specific table/value keeps happening and is quite frustrating 20/05/2024: Already written in the script. To also be part of the minimum data set discussion. | Jenny Albon | ||||||||||
Nationality issue | James Harris Response :That is definitely in the works.I have raised the question with Gemma. 20/05/2024: A bug ticket is raised. Action: Admin team to prioritise ticket | Lauren Squires |
|
|
The Recruitment Import template will be used both for creating and updating records on TIS.
In a scenarion where records already eixist on TIS, what should be the best course of action by the Upload function? For e.g. should all or a selection of fields on TIS be updated/overwritten?
The template will be used with the relevant fields populated so that existing person record on TIS can be matched with to update the record. The rules for finding a matching person record are
1. Applicant ID match if it exists
2. else If ApplicantID does not exist on the template, then use Surname AND GMC/GDC number match
3. else if 1 & 2 are false, then create new Person record
If an existing person exists on TIS, then update with populated values from the spreadsheet and pull Oriel stored data from Azure storage to update the person record with programme and curriculum details.
| |||||
Person Upload Template: add a column for programme membership between programme number and programme end date. Even if it's just a placeholder column, it aligns everything up better then to allow a copy and paste across all the columns | James: Yes will do! Missed that column as the intention was to have at least a placeholder for all columns. For adding the Programme Membership Type field, is there any harm in putting that in as Substantive as doesn't Military come through a different recruitment route? James Added 'Programme Membership Type' placeholder column to match the Person Upload Template in the SQL 20/05/2024: Closed | Andrew Horton | |||
Offers made offline which do not end up showing as 'offer accepted' on Oriel. Not sure how that's going to work when it comes to being able to rely on this data, but hopefully is only small numbers? | 20/05/2024: Is it not mandatory to use Oriel? Action: To be discussed with Claire Wright 23/05/2024: Met with Oriel Team. There is no functionality in Oriel to handle individual appointments outside the main recruitment process due to errors and specific circumstance. This means there will always be a few in the current Oriel system. This has been noted as a requirement for future Oriel systems. | Lauren Squires |
(Current Work) Jira Tickets
Summary | Jira Ticket | ||||||||
---|---|---|---|---|---|---|---|---|---|
1 | Understanding process followed in local offices for onboarding new PGDiTs from Oriel to TIS |
|
|
|