Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Objective

This article outlines a series of configuration steps that must take place in prepare a Paradigm site for successfully reporting TCSI data.

Complexity: EXPERT

Page Contents

Introduction

In preparation for the production launch of TCSI reporting there are a number of necessary configuration changes that need to take place before a 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.

TCSI configuration checklist:

  • Provider

  • Base course

  • Element 329 - Mode of attendance code

  • Element

  • Scheduled unit

  • Student and student course enrolment

Provider

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 enrollment

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. The contents of this drop-down menu is made up of providers with an active status and the assigned role of “DEST Higher Education Provider”.

Implications

  • This workflow applies to provider records that are not accredited HEP's, 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

Additional 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)

Workflow

  1. Navigate to PROVIDER > Search

  2. Use the search fields to load the primary HEP of your Paradigm site

  3. Scroll down the page and locate the field labelled “Provider Reporting Provider”

  4. Select the primary HEP from the available option(s)

  5. Click the “Save Details” button to save the changes

Base course

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

The following fields are compulsory to form a valid TCSI Course record

  • Accredited

  • Accreditation Date

  • Accreditation Date Due

  • Element 310 -

  • Element 533 - Course of study code

  • Element 394 - Course of study name:

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.

The historical

Element 329 - Mode of attendance code

NOTE

The following workflow needs to 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.

Workflow

  1. Navigate to SYSTEM > Search Code Type

  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

Further reading

Element

Note

With the scope of the TCSI solution, there are two status fields that are required to be reported. Rather than creating new fields for these elements, we linked them to our status item table.

  • Providers are required to open the System tab from the side menu, click on Search Status Type button. In the search box type in ‘Enrolment’, and click on Search Status Types. If more than one row of data is returned, choose the row for ‘ENROLMENT_STATUS’ by clicking the blue hyperlink at the left side of the screen. For each listed status item, click on its pencil icon to edit the record. Each enrolment status item must have matching entries for the HEIMS Unit of Study Status Identifier and HEIMS Course Outcome Identifier. Only status items that have this correct mapping will be sent to TCSI. Once each status item has matching values, click the Save Status Item button and proceed to edit the next status item in the list.

Scheduled unit

Student and student course enrolment

TCSI System Preparation

  • Complete entering data for the courses provided by your institution. This will need to be completed before you can enter any course admission records.

  • Complete the set-up tasks including campus records. This will need to be entered and completed before you can enter courses on campus records and this data will not be imported from HEIMS.

  • Complete the set-up tasks for units on campus. This will need to be completed before you can add any unit enrolment records.

Further reading

TCSI Packets (Higher Education Providers)

TCSI Packets (VET Student Loans)

TCSI Push Rules

TCSI Remapped Elements

TCSI Elements with changed options

We highly recommended that all users who will be performing data entry read the following documents so that they gain a strong understanding of the elements that are required to be reported.

FINAL 2020 Data element specifications (24 September 2019)

FINAL HE Data framework and element list (24 September 2019)

HE 2020 reporting requirements v1.0 (24 September 2019)

  • No labels