Engagement expected end date(ENGEXPECTEDENDDATE)
Navigation: Index / Data Dictionary / Engagement / ENGEXPECTEDENDDATE
Key | Value |
---|---|
Name | Engagement expected end date |
Short Name | ENGEXPECTEDENDDATE |
Parent Entity | |
Type | Field |
Applicable To | England Northern Ireland Scotland Wales |
Coverage | All Engagements where Engagement.INCOMINGEXCHANGE does not exist and there is a defined normal length for the programme of study |
Description | This field records the expected end date for the Engagement |
Notes | This field should reflect the expected end date of the structured part of the course and therefore should not be updated when extensions are granted to assessments. For taught students, this should include any planned assessment periods but not retakes (of exams or assessments). For research students where the programme includes a planned writing-up period, this should be included in the expected period of study. This field does not need to be returned where there is not a defined normal length for the programme of study, for example fully flexible courses (Course.FULLYFLEX = 01). This field must be updated where there are any changes to the expected end date of the Engagement. Examples will include but are not limited to:
This field should not be updated if the student withdraws from their Engagement. All date fields must be completed using the ISO8601 format of YYYY-MM-DD. |
Reason Required | To allow a forecast of when an Engagement is expected to end and compare this to the actual end date, to assist in calculating the NSS population. GMC are reporting on when medical students are expected to be taking the Medical Licensing Assessment Applied Knowledge Test (AKT) and when they will graduate. |
Field Length | 10 |
Quality Rules | Quality Rules to follow |
Minimum Occurrence | 0 |
Maximum Occurrence | 1 |
Primary Key? | False |
Revision History | https://www.hesa.ac.uk/support/coding-manual-tools/revision-histories?Collection=22056 |