Configure Paradigm for TCSI Reporting
Overview
To make your Paradigm site ready for TCSI reporting, a number of configuration changes must take place before your site is able to successfully start reporting data via TCSI. This article should be used as a checklist to ensure that your Paradigm site is TCSI-ready and compliant.
This article outlines a series of configuration steps that must take place to prepare a Paradigm site for successfully reporting TCSI data.
NOTE:
The following configuration checklist below assumes that you have already actioned the PRODA Account Registration.
TCSI Configuration Checklist:
Workflow
Provider Configuration
Provider Configuration
Primary accredited Higher Education Provider (HEP) record
All Paradigm sites that are required to report data via TCSI will need to include a provider record that represents the primary reporting HEP. This provider record must be assigned ONE of the following provider roles:
TCSI VET
TCSI PIR
TCSI Higher Education
Parent Reporting Provider
BE ADVISED:
The “Parent reporting provider” field for the primary HEP provider record in Paradigm must be set to the primary HEP provider. In this way, the primary record is a parent of itself.
NOTE:
The following workflow needs to be completed for ALL providers that are connected to one or more of the following data types that are linked to Higher Education accredited courses or programs:
Base course
Base unit
Scheduled unit
Course enrolment
One of the triggers used to identify TCSI data within Paradigm is whether a specific record is associated with an accredited Higher Education Provider (HEP). This is achieved using the field “Parent Reporting Provider” found on the Provider Edit screen, see Add a Provider Record.
Dual sector providers
Providers who operate within both Higher Education and VET sectors will need to have 2 primary provider records within Paradigm: one for Higher Education and one for VET.
New required fields for TCSI providers
Parent reporting provider
Billing address postcode populates element 477
Billing address country populates element 660
Element 609 - Effective from date
Element 610 - Effective to date (optional, submitted only when known)
Implications
Silverband uses the abbreviation field of the primary accredited Higher Education Provider (HEP) record within Paradigm to authenticate with PRODA. This means the abbrev field must not be changed without first notifying the Silverband support team.
This workflow applies to provider records that are not accredited HEPs, including providers that reflect a delivery location, campus or subset of the overall reporting HEP
Paradigm only supports provider nesting that is one layer deep as reflected in the examples below:
SUPPORTED Provider as a campus of an accredited HEP
SUPPORTED Provider as a delivery location of an accredited HEP
SUPPORTED Provider as a (department/school/faculty) of an accredited HEP
NOT SUPPORTED Provider as a faculty of a campus of an accredited HEP
Workflow
1. Choose Providers > Search menus on the side.
2. Use the search fields to load the primary HEP of your Paradigm site
3. Scroll down the page and locate the field labelled “Parent Reporting Provider”
4. Select the primary HEP from the available option(s)
5. Update any missing required fields from the list defined above
6. Click the “Save Details” button to save the changes
back to TCSI Configuration Checklist
Base Courses Configuration
Base Courses Configuration
The Base Course Edit Details screen has been updated to contain the new TCSI elements. The historical HEIMS fields have been permanently moved to the new Program HEIMS Edit screen. This change ensures that Paradigm as a system can be simultaneously compliant with both the HEIMS and TCSI reporting standards.
Base Course Edit Screen
This screen has been updated to include the TCSI fields. The standard is higher for producing a valid base course under TCSI, compared with HEPCAT.
The following fields are compulsory to form a valid TCSI Course record:
Accredited (Yes / No)
Accreditation Date
Accreditation Date Due
Element 307 - Course Code
Element 308 - Course Name
Element 310 - Course of study type
Element 350 - Course of study load
Element 394 - Course of study name
Element 455 - Combined course of study indicator
Element 533 - Course of study code
Element 596 - Standard Course Duration
Element 619 Course Assurance Indicator (VET)
In addition to the above fields, the following sections must also be completed:
Campus
Program HEIMS Edit screen
The Program HEIMS Edit screen offers a simplified view of the base course together with the relevant legacy HEIMS reporting fields. This screen is intended to support providers who have not yet fully reported all of their 2020 student-related data.
back to TCSI Configuration Checklist
Map [E329] Mode of Delivery to TCSI Values
Map [E329] Mode of Delivery to TCSI Values
NOTE:
The following workflow needs to be completed for ALL method of delivery options that are connected to students studying Higher Education accredited courses or unit
The TCSI element 329 will be derived from the existing Paradigm field “Method of Delivery” found on the Base Unit and Scheduled Unit screens. Each provider will need to configure their own mapping between the Paradigm field and the equivalent element 329 option.
Implications
Scheduled unit must not contain a mix of different delivery methods. A new scheduled unit is therefore required when ANY of the following scheduled unit fields change:
Unit Code
Unit Name
Start Date
End Date
Census Date
Mode of Delivery
Home Institution
Workflow
1. Choose System > Search Code Type menus on the side
2. Enter “METHOD_OF_DELIVERY” as the search criteria
3. Click the “SEARCH CODE TYPES” button
4. Use the blue pencil icon to edit a data record
5. Click on the field labelled “HEIMS Code” and select the appropriate element 329 option
6. Click the “SAVE CODE ITEM” button to save the changes
Refer to the Map Status and Code Items to TCSI Values knowledge article for the details of this workflow.
back to TCSI Configuration Checklist
Map [E355] Unit Enrolment Statuses to TCSI Values
Map [E355] Unit Enrolment Statuses to TCSI Values
BE ADVISED:
New unit enrolments are normally created with a default status such as applied or enrolled. This can be configured on a per Paradigm site basis. Users should be aware that if this default status is associated with a value for element 355 then the unit enrolment will be reported to the government as part of the unit enrolment creation event.
NOTE:
Paradigm will only send a unit enrolment record to TSCI when the unit enrolment status has been associated with a valid E355 option.
The TCSI element 355 will be derived from the existing Paradigm field “Unit Enrolment Status”. This means providers may still use their own internal enrolment status values while still conforming to the requirements of TCSI reporting. Each provider will need to configure their own mapping between the Paradigm field and the equivalent element 355 option.
Workflow
Refer to the instructions on this workflow: Map Status and Code Items to TCSI Values
back to TCSI Configuration Checklist
Map [E599] Course Enrolment Statuses to TCSI Values
Map [E599] Course Enrolment Statuses to TCSI Values
The TCSI element 599 will be derived from the existing Paradigm field “Course Enrolment Status”. Each provider will need to configure their own mapping between the Paradigm field and the equivalent element 599 option.
Workflow
Refer to the instructions on this workflow: Map Status and Code Items to TCSI Values
back to TCSI Configuration Checklist
Last updated
