Skip to main content

HESA Student Record 2007/08

Back to C07051

HESA Student Record 2007/08

The Managing Information Across Partners (MIAP) programme

Click here for the MIAP web site


return to index

Version 1.2 Produced 2007-10-17

MIAP is a DIUS-led programme supported by a large number of partner organisations, including HESA. The MIAP programme contains a number of strands of activity including the implementation of the UK Register of Learning Providers (UKRLP) and the development a Unique Learner Number (ULN) registration service. MIAP has also created a standard set of data definitions and policies through the Common Data Definitions (CDD) project. Details of the CDD standards can be found on the MIAP web site.

This document describes the adoption of the CDD standards on the HESA Student Record.

UK Register of Learning Providers

Adoption of the UK Provider Reference Number (UKPRN) is a key element in the standardisation of data definitions between stakeholders' systems. It is envisaged that, over time, all stakeholders will adopt the UKPRN as the primary identifier for institutions. See the the UK Register of Learning Providers (UKRLP) web site for further information.

A software developers toolkit - to support the development of UKRLP web services - can be found by following the Software Development Kit link from http://schemas.lsc.gov.uk/

Unique Learner Number (ULN)

The allocation of ULNs is currently being piloted with a first major roll out planned for 2007 covering students who are currently on the National Pupil Database. Systems will be put in place to issue ULNs to mature students and students from overseas. Students who have been allocated a ULN should be aware of this fact and should have access to their number. However, it is likely to be a number of years before all students entering higher education are able to provide this information. In the long term, it is anticipated that the ULN will replace the HESA Unique Student Identifier (HUSID) and will also be used by UCAS, SLC etc.

Fields affected by the MIAP CDD project

The following table shows those fields affected by the CDD project. Fields marked as a CDD field are contained within the current set of CDD; those marked as a CDD standard are not specifically included in the current set of CDD, but are affected by CDD standards and/or data policy. Details of the specification can be found in the documentation for each field.

FieldCDD fieldCDD standardNotes
Institution.UKPRNYValid UK Provider Reference Number from the UKRLP. This replaces the INSTID field.
Student.ULNYStandard structure with checksum.
Student.BIRTHDTEYISO8601 date format. Representation of not known with reason code.
Student.SURNAMEYStandard character set. Maximum field length of 35 characters.
Student.SNAME16YStandard character set. Maximum field length of 35 characters.
Student.FNAMESYStandard character set. Maximum field length of 35 characters. Representation of not applicable with a reason code.
Student.GENDERYStandard coding frame based on ISO 5218.
Student.NATIONYStandard coding frame based on the ISO-3166-1 Alpha-2 list of country codes and adapted by the Office for National Statistics.
Student.TTPCODEYBS7666 format. Representation of not known with reason code.
Instance.COMDATEYISO8601 date format.
Instance.ENDDATEYISO8601 date format. Representation of not applicable with reason code.
Instance.MCDATEYISO8601 date format. Representation of not applicable with reason code.
Instance.PHDSUBYISO8601 date format. Representation of not applicable with reason code.
Instance.SPLENGTHYRepresentation of not applicable with reason code.
Instance.YEARLGTHYRepresentation of not applicable with reason code.
EntryProfile.DOMICILEYStandard coding frame based on the ISO-3166-1 Alpha-2 list of country codes and adapted by the Office for National Statistics.
EntryProfile.POSTCODEYBS7666 format. Representation of not known with reason code.
Course.CTITLEYStandard character set.
Module.MTITLEYStandard character set.

Contact Liaison by email or on 01242 211144.