All ModuleInstance entities at providers in Wales
Records whether the Module is countable under HEFCW rules.
A module undertaken by a student should be coded as countable unless it fits the HEFCW rules not to be counted. This will be where:
The purpose of collecting this information is to ensure that no more than the maximum number of credit values per student on a course, as set out in HEFCWs definitions, is counted in the determination of the number of credit values for funding purposes. Full guidance can be found on HEFCWs data collection webpages.
If providers have difficulty in identifying modules which should not be counted, then they should contact HEFCW. This is likely to be where it is not possible to determine if modules have already been counted, for example, due to module identifiers changing or modules being taken some time in the past. APEL modules (coded ModuleInstance.APEL = 01 or 02) should be considered countable unless they fit the criteria to not be counted above.
A module should not be considered to be not countable simply because it is taken by an enrolment that is not fundable by HEFCW. Although credit value information for non-fundable students is not collected by HEFCW, the student enrolment is collected and so any associated modules should be considered countable, unless they fit the criteria above.
To identify course structures, to identify countable credit values in analysis to support funding allocation.
|Quality Rules||Quality Rules to follow|
|Revision History||No Revision History entries for this collection.|