Check the data mapping between HESA and Register trainee teachers
Use the table to check how data maps between HESA and Register trainee teachers (Register) for the 2024 to 2025 academic year.
Where possible, these tables follow the same order as the CSV export and a trainee’s record in Register.
| Register CSV column | Register field in the service | HESA field | More information |
|---|---|---|---|
| hesa_id | HESA ID | HUSID (HESA unique student identifier) | A trainee should only ever have one unique student identifier. Where training is being provided by a lead partner in partnership with an accrediting provider, the UKPRN component of the HUSID should be that of the lead partner. |
| provider_trainee_id | Provider trainee ID | OWNSTU (provider’s own identifier for student) | The ‘Provider trainee ID’ can be used in Register to search and find trainees. |
| trn | TRN | TRN (teacher reference number) | – |
| trainee_status | Trainee status | MODE (reason for ending instance) | HESA field ‘MODE’ will impact ‘Trainee status’. If codes 63 or 64 (dormant trainees) are used, the trainee’s status will change to ‘Deferred’ in Register. To reinstate a trainee from deferral, 01, 02 or 31 can be used. ‘Dormant’ in HESA means ‘Deferred’ in Register. |
| hesa_record_last_changed_at | not displayed | STATUS_TIMESTAMP | The date the trainee record was last changed in HESA or the TRA portal. This is not the date the record was uploaded to HESA. For example, if you change and then upload a trainee record in September, this CSV column will show a date for September. If you then upload the same record in January and April without any changes, this CSV column will still show the date in September. |