Skip to main content

Module instance (ModuleInstance)

Back to Student


Key Value
Name Module instance
Short Name ModuleInstance
Version 1.4.0
Description The Module instance records a Student's specific engagement with a Module and the Module outcome.
Uniquely Identified by

Each Module instance (ModuleInstance) is uniquely identified by:

Applicable to England Northern Ireland Scotland Wales
Coverage An entity is required for each interaction a student has with a Module at providers in Northern Ireland, Scotland and Wales and Approved (fee cap) providers in England where Engagement.INCOMINGEXCHANGE does not exist and Qualification.QUALCAT starts with E, M, H, I, J or C.

Optional for each interaction a student has with a Module at Approved providers in England or where Engagement.INCOMINGEXCHANGE exists or where Qualification.QUALCAT starts with D or L.
Notes


Providers in England that are registered with the Office for Students in the 'Approved' category are not required to return Module data but can do so optionally.


Providers in England that are registered with the Office for Students in the 'Approved (fee cap)' category must return Module data.


Further information regarding the OfS register can be found here


Module data is optional to return for postgraduate research students and incoming exchange students.


This entity associates a StudentCourseSession with a Module that a student is engaging with as part of that StudentCourseSession, including the module outcome.


ModuleInstances should be submitted against the StudentCourseSession, not just the reference period in which they occurred. Therefore all of the ModuleInstance associated with the StudentCourseSession will be returned for the reference period in which the StudentCourseSession finishes.


Modules spanning StudentCourseSessions


One Module instance can only be associated with one StudentCourseSession and therefore cannot span StudentCourseSessions. If a student's engagement with a Module spans two or more StudentCourseSessions, then multiple Module instances are required, one associated with each StudentCourseSession. The first would have an associated module outcome where ModulInstance.MODULEOUTCOME= 06 'Will complete Module in a subsequent StudentCourseSession'. Both ModuleInstances returned could be linked to the same Module.


If at the end of the StudentCourseSession the student has completed activity but the result is not yet known, a ModuleInstance.MODULEOUTCOME of 05 Module result not yet known can be returned for students where module result information is required to indicate this


Where a student is resitting a module in a subsequent StudentCourseSession (whether resitting teaching or just exams), the ModuleInstance.CONTINUING field would not be returned as they are resitting assessment rather than continuing the module. If returning fees on a modular basis, any fees associated with this resit would be returned in ModuleInstance.MIFEEAMOUNT. If returning fees on a StudentCourseSession basis, any fees associated with this resit would be returned in StudentCourseSession.SCSFEEAMOUNT.


In some cases a ModuleInstance may be returned to record the outcome of a module only, this may be because the student is resitting exams, or the outcome was not confirmed at the end of the previous StudentCourseSession. In these cases, the ModuleInstance.INACTIVEMOD field would be returned to indicate that there was no activity associated with the ModuleInstance. The start and end dates for the ModuleInstance would align with the start date for the associated StudentCourseSession.


Providers in England and Northern Ireland


Whilst providers may recognise prior learning and allow students to take APEL modules, APEL modules should not be returned in the student record by providers in England and Northern Ireland. This is to prevent confusion over those modules taken through APEL and those not undertaken through APEL, to avoid FTE being allocated incorrectly.


Quality Rules Quality rules to follow
Reason Required To record the Modules that Students engage with, to record module outcomes.
Minimum Occurrences unbounded
Maximum Occurrences unbounded
Fields
Field Field Length Optional?
Module instance identifier (MODINSTID) 50 No
Accreditation of prior experiential learning (APEL) 2 Yes
Continuing module (CONTINUING) 2 Yes
Inactive module flag (INACTIVEMOD) 2 Yes
Language percentage (LANGPCNT) 4 Yes
Module instance fee amount (MIFEEAMOUNT) 10 Yes
Module count (MODCOUNT) 2 Yes
Module identifier (MODID) 50 No
Module instance end date (MODINSTENDDATE) 10 Yes
Module instance start date (MODINSTSTARTDATE) 10 No
Module outcome (MODULEOUTCOME) 2 Yes
Module result (MODULERESULT) 2 Yes
Parent Entity Student course session (StudentCourseSession)
Revision History
Coding Manual Version Element Version Notes
1.4.0 1.0.2 Guidance added regarding modules spanning StudentCourseSessions and inactive ModuleInstances.
1.2.0 1.0.1 Guidance added to clarify that Module instances need to be submitted against the StudentCourseSession, not just the reference period they occurred in.

Contact Liaison by email or on +44 (0)1242 388 531.