Oriel-TIS Integration (Legacy)
- Ashley Ransoo
This page contains previous artefacts gathered from the initial discovery in order to link Oriel to TIS for the transfer of trainees information from Oriel following recruitment into TIS.
Some history
Prior to TIS, the process on Intrepid has been been to input the curriculum and programme details via Intrepid (a Hicom legacy system for management of trainees prior to TIS) at the point of importing them from Oriel (another Hicom system used for National Recruitment of trainees) into Intrepid, to create their records.
Post and programme details were not captured on Oriel and therefore unable to do a direct mapping & transfer to the Intrepid system of the Offer Accepted Oriel Applicants.
Oriel workforce Extract
The Oriel Workforce Extract is a file based (XML) export from Oriel of Trainees' details, the programmes they've been accepted on along with documents submitted with their Oriel application during recruitment.
There was previously an ETL that received those files and documents from Oriel and stores them on Azure (decommissioned cloud HEE TIS platform). This extract includes Trainees that are new to TIS (e.g. Foundation trainees) and those applying for Higher Specialties.
N3 Location
TIS used the following share location for Oriel:
Service | Server | Share |
|---|---|---|
Oriel | 10.196.16.50 | C:\WorkforceExtract |
Objectives
The desired state is to at some point be able to automatically ingest trainees into TIS when Intrepid is retired as a system. For the MVP, it was initially proposed to have a semi-automated ingestion of some of the Oriel trainee details whilst HEE Admins perform a bulk upload of trainees to TIS.
TIS went live in April/May 2018 with a bulk upload solution as an MVP, but this did not include the semi-automated transfer of Oriel details from the Oriel Workforce Extract files. In order to deliver a potential full automation of extracting and creating trainees records from Oriel to TIS there are potential changes to be done on both TIS and Oriel sides.
In December 2023, pre-discovery work was started by the TIS Business Analyst and The TIS data team to Understand the process followed in each local office for onboarding new postgraduate trainees from Oriel to TIS. The aim was to achieve an understanding of the processes followed by each local office so that all perspectives and pain points can be considered when deciding solution options, ensuring alignment with local office practices.
Proposed Business Process to Import Trainees from Oriel into TIS
26/08/2020: The below process was not fully achieved and excluded the semi-auto ingestion of Oriel trainee details from Azure extracted Oriel Files.
A bulk upload tool was developed in TIS for MVP for uploading Oriel trainees which requires pre-population from Oriel Reporting tool or in some Local Office’s what is known as the Rotor tool to transform/map the Oriel data along with Reference data (e.g. Nationality, sexual Orientation etc.) to what TIS can successfully upload on the designed rationalised template. Bulk Upload Templates
Pre-Discovery Discussion and Assumptions
# | Question | Comment | Owner | Jira Ticket |
|---|---|---|---|---|
1 | In the workbook on sub heading 3, there are fields that are reference data from Oriel and require further data mapping to be done. | 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 |
|
2 | In the workbook on sub heading 3, there are fields that are not necessarily mandatory on Oriel and would therefore only pull through if the applicant/trainee has provided the information on their application form, e.g. National Insurance number, Religious belief, Sexual Orientation etc. | Recommendation is that if completed in Oriel that it is pulled through into TIS. | Data Leads
| |
3 | 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
| |
4 | Workbook on sub heading 4 was put together with input provided by Claire Lehoux. Although separate from Reference data mapping, there still need to have legacy data tidied up in the DR. Not related to the Oriel integration but for data quality in general. |
| Data Leads | |
5 | Workbook on sub heading 5 has a list of Immigration statuses discrepancies that requires mapping. Oriel reference data for 2017 and 2018 have different list of values that will be passed on to TIS. | 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.
Oriel to fix their extract to send those values.
| Data Leads | |
6 | Reference data changes on Oriel will need to be coordinated with TIS going forward. |
| Data Leads | |
7 | 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:
| 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
| Data Leads | |
8 | Documents will be be extracted from Oriel and stored on TIS in a data structure on Azure to be consumed by the Bulk Upload function during trainee records creation. | For info only. | Data Leads |
|
9 | 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: SImilar action to #3. ApplicantID = ORIEL PIN | Data Leads | |
10 | 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
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. | Data Leads | |
11 | Oriel XML file format |
|
|
Jira Tickets
Ticket No | Summary | Created | Reporter |
|---|---|---|---|
30/Jan/18 11:37 AM | Reuben Noot | ||
11/Jan/18 11:06 AM | Ashley Ransoo | ||
Review GMC LRMP Fields to see see if an ETL is required to bring any of them | 05/Jan/18 4:43 PM | Ashley Ransoo | |
14/Dec/17 11:11 AM | Ashley Ransoo | ||
14/Dec/17 9:28 AM | Ashley Ransoo | ||
Oriel Integration - Confirm the Recruitment Import template fields for TIS going forward | 11/Dec/17 2:17 PM | Ashley Ransoo | |
Oriel Integration - Create Oriel Custom Report | Fields Definition | 11/Dec/17 2:12 PM | Ashley Ransoo | |
Oriel Integration - Immigration statuses Reference data mapping | 11/Dec/17 2:08 PM | Ashley Ransoo | |
Oriel Integration - Confirm fields required in the Recruitment Import template | 11/Dec/17 1:48 PM | Ashley Ransoo | |
11/Dec/17 1:40 PM | Ashley Ransoo | ||
Oriel Integration - Oriel Reference data requiring further mapping | 11/Dec/17 1:27 PM | Ashley Ransoo | |
Create mapping document for Oriel-TIS-Recruitment Import fields for data leads | 07/Dec/17 11:48 PM | Ashley Ransoo | |
Create high level business process for Oriel Trainees Import | 07/Dec/17 11:41 PM | Ashley Ransoo | |
19/Nov/17 8:37 PM | Ashley Ransoo | ||
19/Nov/17 8:33 PM | Ashley Ransoo | ||
15/Nov/17 1:40 PM | Former user | ||
06/Nov/17 3:24 PM | Graham O'Regan | ||
18/Oct/17 11:18 AM | Graham O'Regan | ||
18/Oct/17 8:37 AM | Graham O'Regan | ||
18/Oct/17 8:37 AM | Graham O'Regan |
Documents
Explorations + Decisions
To continue the work started in order to achieve full automation as the future desired state between Oriel and TIS.
Related content
Slack: https://hee-nhs-tis.slack.com/
Jira issues: https://hee-tis.atlassian.net/issues/?filter=14213