Page Comparison

1.

Application Status/Window

• Track progress of applications from Applied> Longlisted > Declined > Shortlisted > Offered > Offer Accepted

Dynamic - Dynamic Data PID - Not in NDW?

2.

Core recruitment data by applicants - by Specialty/ Grade/ Round/ Rounds/ Demographics

Dynamic

3.

Table showing count of crossover applications within and across rounds for each vacancy, this can be filtered by round, Specialty, specialty grouping . The report options are:

• Crossover count at application

• Crossover at application as a percentage

• Crossover count of those who accept

• Each of the above reports also have the count of applicants, applications (generally the same as applicants other than where devolved nations run their own recruitment eg. NI CST) and unique applicants by specialty

3.

Core vacancies/posts advertised -

by Grades/ Specialty/ Competition ratios

• Posts filled, comparisons over the years

• Posts re-advertised (avoid double counting)

4.

Equality and Diversity Monitoring

• Flag for investigation by ethnicity

• Specialty/Local Office/Nation/CoQ

• Review GDPR

5.

Where are people applying from?

• By address fields?

• By Preferences (region, sub-regions, sectors etc.)

6.

Applications behaviours during the application window?

• How many applications?

• How many unique applications by specialty?

• How many cross-overs?

7.

Evidence of Recruitment Activity

• Count of applicants per status

Static - after recruitment round ended

Overseas Sponsorship Team

Training Programme

Date advertised

Date opened

Date closed

Number of applicants applied

Number of applicants longlisted   

Number of applicants shortlisted

Number of applicants offered

1.

In order to build all the reports required for national reporting, HEE requires its data from Hicom to be available more frequently (more than daily, perhaps hourly).

In principle this will be fine. Minute-by-minute queries would cause issues but a more frequent than daily shouldn’t be an issue. Will need to work with the Data Service team what their refresh schedule could be.

2.

Oriel Custom Reporting and Scheduled Custom Reporting are currently available. Both allows us to get a CSV file of a subset of Oriel recruitment data.

It is currently resource-heavy on the Data Service team to have to download the data, manipulate and upload back. This is almost manual ETL process. Having the data available to HEE refreshed more frequently from Hicom would allow us to focus on reports creation rather than the process of getting the data.

DR3 currently seems the best option. May need to create an independent DR3 for Oriel depending on the volume of data requested.

3.

Workforce Extract is a piece of work that was commissioned to automate the process of bringing Offer Accepted applicants from Oriel into TIS without the need for administrative intervention.

HEE still requires the Workforce Extract work that was previous commissioned from Hicom. (Addition of Programme Name, number etc. ).

Is it independent from this work from a Hicom perspective?

Idea to keep the Workforce Extract independent despite there being potential duplication of fields. This will This will help with IG concerns as well as ensuring only relevant records are brought to TIS as the Workforce Extract is PID but reporting requirements are pseudonymised.

Workforce Extract includes documents which are not required for reporting.

4.

New Managed instance of NDW - separating Applicants (PID) from pseudonymized data. What are the IG implications/constraints of bringing the data in-house for National reporting?

As per above reporting requirements pseudonymised data only. Will need to have a conversation with IG team around transactional Oriel data and Oriel data kept for research purposes. Suggestion of using the Oriel Applicant ID as the pseudonymised unique identifier which can also potentially link records to TIS.

5.

HEE recruitment timeline dictates when a round start and finishes. The Hierarchy deadline date on Oriel is not strictly following those dates. How does that impact an automated data solution?

To be dealt with at the reporting side not the data side. Hicom will continue to send dynamic data.

6.

Who are the end users of the National Reporting? (National, Local Office and Specialty)

What are the general needs of those users?

What are the specific reporting needs of those users?

Internal - Discovery work will be required once we have the data.

Internal