...
This page outlines all important matters related to 2020 reporting requirements about Transforming the Collection of Student Information (TCSI).
Complexity:
Status | ||||
---|---|---|---|---|
|
Page Contents
Table of Contents | ||||
---|---|---|---|---|
|
Assumptions
...
...
The user is familiar with the previous HEPCAT / HEIMS reporting
...
The user has an understanding of TCSI Element Numbers
2020 Reporting Requirements
Info |
---|
NoteThese documents are working in progress and therefore subject to change, update and alteration. Click on the below hyperlink to read further information. |
...
In implementing the new TCSI requirements Silverband analysed the two methods on sending data to the government. These two main methods include TCSI Data Upload (known as Portal method) and B2G real-time solution (known as real-time solution). In the intial initial specification we considered the TCSI Data Upload method as this matches match closely to with the existing HEIMS reporting with in different file formats. However the government required that updates be sent weekly at a minumum minimum which Silverband thought was to erroneous of work effort to place on providers. Additionally Furthermore, the government recommended suggested that TCSI Data Upload method was only suitable for very small providers (approx. 20 students) where the data is does not changing oftenchange frequently.
According to the government the TCSI web interfaces are meant to be resposonsive responsive near in real-time. This allowed the implemention implementation of our solution that is known as single touch. The single touch soultion solution allows data to be sent to the government as it saved in Paradigm and return to the interface the response from the web interfaces for the submitted piece of data.
See TCSI Migration 2020Summary for further notes on the development and how data packets are created.
Changing Fields Cause Bulk Operation
In our solution
Implications
Changing fields can cause bulk operation
Warning |
---|
WARNING: Do not change the following fields unless required, always consult Silverband team prior to making changes to the following fields. |
In Paradigm we push individual records one at a time. Due to a change the made by the government back in August, 2020, changing any of the following fields will cause a bulk operation which may take a while in the system.
We suggest you do not change the the following fields unless required.
Also because Another impact of this change is that you can no longer have flexible unit enrolments that have a variable start and end dates, and census dates that do not match the scheduled unit.
In this bulk operation the following actions will happenbe taken:
All the unit enrolments will be deleted from TCSI 1 one at a time.
Then the The minimum required fields will be send to TCSI to create the unit enrolment.
Then a An update will be sent to TCSI to completed the record as it stands in Paradigm.
The critical fields that will could cause this the bulk operation to occur areas follows:
Element number | Paradigm Field | Screen/URL |
---|---|---|
E464 | HEIMS Discipline | Unit Edit/unit_edit.php |
E337 | HEIMS Work Experience Indicator | Unit Edit/unit_edit.php |
E551 | HEIMS Summer School | Edit scheduled unit details/scheduled_unit_edit.php |
E622 | Unit of Study Year Long Indicator | Edit scheduled unit details/scheduled_unit_edit.php |
E489 | HEIMS Census Date | Edit scheduled unit details/scheduled_unit_edit.php |
TCSI Moved Fields
The introduction of TCSI has presented us with an opportunity to move around some fields in a way that closer reflects the intent of the element from the perspective of the government.
The following elements
...
have been moved from the course enrolment screen to the student screen:
...
E572 (Year left school)
E573 (Highest educational attainment parent 1)
E574 (Highest educational attainment parent 2)
TCSI Remapped Fields
The introduction of TCSI has presented us with an opportunity to remap some internal fields to TCSI fields as the TCSI implementation has deuplicated duplicated the meaning of a field into a single field.
E319 - Previously this field had a dual value being either a post code or country and hence a country code. In HEPCAT context, It was a separate field in Paradigm. In TCSI context, this elment element purely represents the Term Address Postal Code and postcode. Whereas element E661 has been added to capture the Term Address country code. These address fields have been now mapped to the Residential/Semester Address fields for the student and hence . So it has been removed from the application.
E320 - Previously this field had a dual value either a post code or country and hence a separate field in Paradigm. In TCSI this elment element purely represents the Term Address Postal Code and element . Element E658 has been added to capture the Residential Address country code. These addresses has have been now mapped to the Billing Address fields for the student and hence . So it has been removed from the application.
E330 - This field has been mapped to the Full/Part Time field in Paradigm. It used to be a calculated based on the eftsl EFTSL being submitted in the LL file. No action is required to makethis make this work.
E329 - This field used to be located on the course enrolment screen and . It has now been remapped to the scheduled unit screen and as the field Mode of Delivery. This field relies that the code items for this field have the new HEIMS value filled in. Please see video below.
Widget Connector | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
E355 - This field used to be on the unit enrolment and sent to HEIMS depending on the enrolment status of the unit enrolment directly coded in the application. This field has now been mapped to the enrolment status list found in the Status Edit screen and is configurable per software instance by the provider.
Please see this video to map values for the status items.
TCSI Mapped Fields
In the development of TCSI we have mapped some of the internal fields in Paradigm with fields in the TCSI specification. These fields include:
E599 - This field is located on the course enrolment screen and has been mapped to the course enrolment status field. The enrolment status field needs a HEIMS a value mapped to it in the status edit screen. Paradigm will only send values to TSCI TCSI where there a status mapped to the field. This means you can still have your own internal enrolment status values and only when you set a status where the value is ampped mapped with to send a change to TSCITCSI.
Please see the video below to map values for the status items.
Widget Connector | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
E661 - This field has been mapped to the student country code for there their Semester Address. Paradigm now has configured a mapping of internal country code to TCSI country codes and no . No provider intervention is required for this update.
E658 - This field has been mapped to the student country code for there their Billing Address. Paradigm now has configured a mapping of internal country code to TCSI country codes and no . No provider intervention is required for this update.
Additional Provider SetupSet up
In the development of TCSI you need setup set up a primary provider record where the abbrviation abbreviation of the provider record matches the abbreviation of we map in Nexus for your PRODA authentication record. This means that if you are a dual sector provider then you will need 2 two primary provider records: one for Higher Education and one for VET Provider.
The primary provider record for botht both the higher education and primary vet VET provider must have the role: HEIMS Higher Education Provider.
In addition to the the above role being assigned providers are also required to set a new field: Parent Reporting Provider. Eventhough Even though this is the primary record this field must be set to itself. Apart of submitting records to TCSI Paradigm will only submit records where the primary provider is directly or indirectly associated with the primary provider.
Due to the statement above all records associated with the primary provider must also be have a relationship assigned back to the primary provider. If your instiutiion institution has numerous unit and program providers submmiting submitting data on behalf of the primary provider they also must have the Parent Reporting Provider field set. Only records that are associated to the primary provider will be submitted to TCSI. Knowing this additional provider records can be created that do not have a relationship to the primary provider for internal use.
...
The following tables outline the data packets from TCSI and changes made to the to implement the TCSI data packet.
...
Paradigm has implemented the Course of Study Packet and the Courses Group packet on the same screen. This makes the screen a complex to use as data editing must be completed in the correct order.
Screen / UrlURL | Change |
---|---|
Course Edit - /program_edit.php | Added TCSI section |
Course Edit - /program_edit.php | Removed HEIMS fields |
Course Edit - /program_edit.php | Screen broken up into new subsections |
Course Edit - /program_edit.php | Added Fetch All TCSI Program Records |
Course Edit - /program_edit.php | Added Field Dest Uid 3 |
...
Paradigm has implemented the Course of Study Packet and the Courses Group packet on the same screen. This makes the screen a complex to use as data editing must be completed in the correct order. You must ensure the fields to get a Dest UID 3 are filled in before you can get a Dest UID5. This means you are required to complete the fields of the Course of Study Packet first. It is important to note without a UID for this record you cannot submit a course enrolment.
Screen / UrlURL | Change |
---|---|
Course Edit - /program_edit.php | Added TCSI section |
Course Edit - /program_edit.php | Removed HEIMS fields |
Course Edit - /program_edit.php | Screen broken up into new subsections |
Course Edit - /program_edit.php | Added TCSI sub data packet FIELD OF EDUCATION section |
Course Edit - /program_edit.php | Added TCSI sub data packet SPECIAL COURSE TYPE section |
Course Edit - /program_edit.php | Added Field Dest Uid 5 |
Course Edit - /program_edit.php | Added Fetch All TCSI Program Records |
...
Screen / Url | Change |
---|---|
Provider Edit - /program_edit.php | Added Field Effective Date From |
Provider Edit - /program_edit.php | Added Field Effective Date To |
Validation Status | Added Field |
Last Validated | Added Field |
Abbrev | Matches Proda PRODA Account Id in Nexus |
Provider TCSI UID | Added Field |
Parent Reporting Provider | Required to link this reocrd record to the PRODA provider |
Courses On Campus Record
...
It is important in Paradigm that data packets are now completed in the correct in order for the system to push data packets to TCSI. This is important because we will not attempt to push packets where a required id is not completed. This means if a depenedent dependent UID is later required all the depenedent dependent records will need to saved independently so they get pushed to the TCSI system.eg
If you do not have a UID5 on the Courses Group packet then no course enrolments will be submitted to TCSI and therefore no uniy unit enrolments. So this means all these records will need to be save individually this also means that if these packets have sub packets they will also need to saved to they are pushed as well. Therefore it is vitally important for saving time that data packets are entered in the correct order.
One of the advanages advantages of TCSI reporting over HEPCAT is you only report sub packets if you have data for that sub packet. eg If your student does not have a disability you do not enter that sub packet.
There are some new sub records which can have one or more records, be time depenedent dependent and both have one or values and be time depenedentdependent.
The table below outline those dependencies
Packet | Depenedent Dependent Record | Notes |
---|---|---|
Courses of Study Packet | Provider | Needs to have the provider field competed to determine primary provder provider as required for PRODA. |
Courses Packet | Courses of study Packet | UID3 |
Course Field of education | Courses of study Packet | Reuired Required to have a least one record to get a valid with UID3 |
Campuses Packet | Provider Record | Needed to determine primary provderneed provider need to ensure the Parent Reporting Provider is entered. |
Courses On Campus Packet | Campus Packet Courses of Study Packet | This is required for course admissions packet |
Students Packet | Tax File Number or Course Admission Packet | Only push enrolled course enrolments or students who a tax file number. Needs to have the provider field competed to determine primary provder provider as required for PRODA. |
Course Admission Packet | Students Group with UID 8 and Courses Packet with UID 5 | Similtaneously Simultaneously will send Students Group packet and Course Admissions Group if the course enrolment is enrolled. Needs to have the provider field competed to determine primary provder provider as required for PRODA. |
Unit Enrolments Packet | Course Addmission Packey Admission Packet with UID15 | Must have a course enrolment with a UID 15 set. |
...
Course Of Study Packet
The table below outines outlines the editing rules you need to follow when using the screens to get a TCSI data packet to completed successfully.
Screen / Url | Editing Rule |
---|---|
Course Edit - /program_edit.php | More required field see TCSI Push Rules |
Course Edit - /program_edit.php | Need to ensure the provider is set this is used to get the Primry Privder Primary Provider setup previously which is mapped to your PRODA record which ensures the data is sent to the correct URL in the TCSI system either the HED area or the VET area. |
Course Edit - /program_edit.php | Existing Records require a Dest UID3. Otherwise when they are saved they could create a new in the TCSI system. These are records that have been previously reported in HEPCAT |
Course Edit - /program_edit.php | This data packet does not have any sub packets that required to be filled out before it will submit. |
Common Data Errors
The Paradigm implementation of the TCSI web interfaces
Some HEIMS TCSI response as examples listed below:
Data Packet | Paradigm Internal Survey Id |
---|
TCSI Status |
---|
TCSI Message | Notes | |||
---|---|---|---|---|
Program | TCSI_2020_COS_POST | Error | The Course of Study Load (E350) is not within the accepted range of values. | This is a standard type error returned by TCSI |
. These messages |
quite often have a button to get further details. | ||||
Program | TCSI_2020_CAMPUS_POST | Error | Record too old for TCSI POST | This is |
---|
an error generated by Paradigm |
. It happens because the effective from date is |
too old. If the record already has an existing TCSI UID |
, the system |
assumes the record is |
too old to push to TCSI. If the record does not have a UID, set the Accreditation From date to on or after the start of the current calendar year (i.e. 01/01/2021). |
Workflow
Where to get more details about element numbers
...
Related Pages
...
...
...
On the side menu under 'Resources' click on the Data Element Dictionary. This loads a data element dictionary screen where you can find the specifications and operational definitions for all the elements for which date are to be reported in the Higher Education and VET data collections
...
...
Click on the Elements by number under the label 2019 higher Education Student data collection
...
Click on the Number to be viewed.