Student record 2015/16
Version 1.0 Produced 2015-09-24
The HESA student record specification is based on a logical data model which defines the entities covered by the record and the relationship between these entities.
In data modelling terms, an entity is a thing about which information needs to be held. Examples in the Student record include the student, the course, the instance of engagement, and the provider.
The data model differs from the file structure required for the submission of the data, as a number of attributes are expressed as repeating elements for efficiency. For further details, please see File structure.
HESA Student record entity relationship diagram
|Provider to Student||A Provider must have one or many Students|
A Student must belong to a Provider
|Student to Instance||A Student must have one or many Student Instances|
A Student Instance must belong to a Student
|Course to Instance||An Instance must belong to one Course|
A Course can have zero, one or many Student Instances
|Instance to Student on Module||An Instance can have zero, one or many occurrences of Student on Module|
A Student on Module must belong to one Instance
|Module to Student on Module||A Student on Module must belong to one Module|
A Module can have zero, one or many Students on Module
|Instance to Entry Profile||An Instance can have zero or one Entry Profiles|
Entry Profile is compulsory during the first year of an Instance
An Entry Profile must belong to one Instance
|Entry Profile to Qualifications on Entry||An Entry Profile can have zero, one or many Qualifications on Entry|
A Qualification on Entry must belong to one Entry Profile
|Instance to Qualifications Awarded||An Instance can have zero, one or many Qualifications Awarded|
A Qualification Awarded must belong to one Instance
|Instance to Mobility||An Instance can have zero, one or many occurrences of Mobility|
An Mobility entity must belong to one Instance
Contact Liaison by email or on +44 (0)1242 388 531.