DEEWR has developed a set of validation "rules". These rules are listed in the Data Validations section of this website. Some rules are very simple. Other rules are very complex, requiring data in one file to be checked for consistency with data in one or more other files.
The rules are of these types:
- Checking that codes are valid
- This type of check makes sure that only valid codes are provided for a single data element in a single record. In the Data Element Dictionary, the codes that are valid for each element are listed. For example data for Element 315 (Gender code) can only be "M" or "F". For other elements, data must only be numeric. In some cases, data for an element cannot be spaces. In other cases, the specifications indicate that the data are to be in a particular range (e.g. between 22 and 34). Other types of rules are evident in the specifications.
- Checking that codes for one element are consistent with codes for another element in the same record
- This type of check makes sure that data provided for two elements in a single record are consistent. For example, if a student is coded as an Australian citizen on one element, they cannot be coded as being a fee-paying overseas student on another element within the same record.
DEEWR's software products HEPCAT and HEIMS are to be used to undertake all validations. Details about HEPCAT and HEIMS are provided in User Guides and System Requirements.
The validation rules are listed in the following section. For each rule the following data are provided:
The validation number. This is simply a unique number identifying the rule (e.g. 1080).
The error message that will be produced by HEPCAT and HEIMS. This is a short description of the nature of the rule violation.
Whether the rule, if violated, involves a FATAL or a WARNING condition.
The rule. This is a long description of the rule.
The number of the element or elements to which the rule applies. These element numbers correspond with element numbers used for elements in the Data Element Dictionary.
The file that contains the record for which data are being checked. The following abbreviations are used;
- CO: Course of Study File
- CU: Student Unit of Study Completions File
- EN: Student Enrolment File
- LL: Student Load/Liability File
- PS: Past Course Completions File
- OS: Student OS-HELP File
- SS: Commonwealth Learning Scholarship File
- DU: HELP Due File
- PO: Electronic Commonwealth Assistance File
- RF: Revisions File
- CM: Campus File