Demo - https://tabanalytics.data.england.nhs.uk/#/projects/1272
data refreshed
...
As not all records have a status of ‘Applied’, for Application Counts an ApplicationID with any status except ‘In Progress’, 'Application withdrawn before submission' is considered to be an application. Are there any other statuses which should not be included? Distinct List of Application Statuses.csv
...
Application Status of ‘Longlist Unsuccessful’ produces a record with a NULL Grade. Is this expected? Should those with this status be excluded from Application Counts completely or just those with NULL Grades?
...
Should all NULL Grades be excluded from Application Counts no matter the status?
...
Previous Actions
Questions from Data Analytics Team
Application Counts Questions:
:
Fiona’s access for the dashboards - Organisation code NHS Education for Scotland has been added - SD037, which was needed for OKTA sign up.
Registered but waiting for another team to review. Cannot access the dashboard though.
Null grades examples sent to Chad to investigate
Comments from Christopher Baily:
“Grade is "grade applied to" so it's only set when the application is submitted.
If admins run a "Longlist process by status" process, then this will change the status of any "In progress" applications to "longlist unsuccessful", hence why that status appears in there. ”
What is a ‘longlist process by status’ process?
Take them out of the longlist. Application In Progress after the closing date when the longlisting process is run they are given ‘longlist unsuccessful’. Look at a field Submitted Yes/No to add.
Can we safely filter out all NULL grades as it means it isn’t an application?
Should be the case but there should hopefully be an easier way?
Should we filter out all ‘Longlist unsuccessful’ or are some of these different from the above?
No. They can be either In progress after closing OR they have submitted but did not meet some of the essential criteria.
Medical round grouping using newly added fields -
- Looking at the data quality of the fields. In ProgressJira Legacy server System Jira serverId 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 key TIS21-6785 Fill rate dashboard modifications suggested -
Regional view, different slicing of data - These will be ticketed and completed
Cross over applications - Further details of crossover applicant behaviour (how many applied for the same specialty in other offer years / other offer rounds in the same offer year/ applied for different specialties in different offer years & rounds) - Work to be ticketed and completed
Competition ratios -
- In ProgressJira Legacy server System Jira serverId 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 key TIS21-6675
Questions from Data Analytics Team
Priority of the above?
Q&A / Feedback