Canadian Learner Residency Data Standard

Intended Audience and Contact Information

Contact	Chief Data Officer, Office of the CIO
Intended audience	Internal UBC
UDM Domain	Person Domain
Data Standard ID	DG0061

Purpose

This standard aims to achieve consistency around the collection of Canadian Learner Residency data, and the format in which it is collected and stored. Residency is used to determine assessment of tuition and fees, funding and reporting.

This standard is derived by UBC and applies to all applications collecting residency status and residency reason data. Exceptions are listed in the Dispensation section.

Standard

The following are the data elements and accepted values associated with learner residency:

Canadian Learner Residency Attributes

The following are the data elements and accepted values associated with learner residency:

Attribute	Definition	Format
Student Name	The full Preferred Name of the student that the residency status is associated with.	Auto-populate
Institution	Defaults to "University of British Columbia"	Text
Residency Status*	The status of a learner for the purpose of assessing tuition and fees, funding, and reporting.	Reference List: Refer to the *Residency Status* section for more details on accepted values.
Residency Status Reason	The reason for treating a person as a resident for the purpose of assessing tuition and fees, funding, and reporting.	Reference List: Refer to the *Residency Status Reason* section for more details on accepted values.
Effective Date*	The start date of a residency status.	Date

Note: Residency Status data is always associated with a Student, and is therefore linked to the Student ID (unique identifier).

*Required fields in Workday

Residency Status Standard

The following are accepted values for Learner Residency Status:

Accepted Value	Definition
Resident	A Domestic Learner or one treated as such, as per the relevant BC Ministry guidelines and at the discretion of the university, for purposes of funding and reporting. Examples include: A Domestic Learner An individual who is in Canada to carry out duties as a diplomat or official, and their legal dependent(s), as long as the visa is valid under the diplomatic or official status. An individual with an affiliation to an Indigenous nation of Canada An individual of an Indigenous nation that extends across the Canada-US border A Convention Refugee*. By special class application to the institution, an individual may be considered domestic under the Ministry of Advanced Education Guidelines Respecting International Students at British Columbia Public Post-Secondary Institutions.
Non-resident	A person who is not a Resident.
Undetermined	A temporary value to be used when a learner’s Canadian residency is unknown. Rule: Treated as a non-resident.

*A person has been granted Protected Person Status as a Convention Refugee in Canada.

Residency Status Reason Standard

The following are accepted values for Learner Residency Status Reasons:

Accepted Value	Definition
Verified Canadian Resident	An individual who has been verified by an administrator to be a Canadian Citizen, Canadian Permanent Resident, Convention Refugee, or on a Diplomatic Visa.
Cross Border Indigenous Nation Member	An individual of an Indigenous nation that extends across the Canada-US border.
Indigenous Nation of Canada	An individual who does not have Canadian Citizenship but has an affiliation to an Indigenous nation of Canada.
Work Permit Holder	An individual who has a Work Permit (LMIA) or Work Permit (LMIA-exempt) immigration document that is valid for more than a year and covers the start of the assessed academic period. This status may also apply to their spouse or dependents.

Compliance

The above standard must be complied with at every stage of the data lifecycle except for any dispensations (see Dispensation section).

All applications must collect data as recommended in this standard.
Enterprise Data Integration must adopt this standard.

Reference Data Compliance for Data Integration

The use of accepted reference data values in this standard for data integration among applications must comply with the enterprise integration pattern of leveraging the reference data common service API (Application Programming Interface) published in UBC MuleSoft Exchange.

Any application that intends to access real-time, case-level reference data should have the application owner or manager complete and submit a Request API Access form.

For any compliance questions or requests for a dispensation temporarily, please contact the Enterprise Data Governance Team.

Dispensation

Legacy systems are exempt from this data standard. As systems are replaced, adoption of this standard is required. Examples of legacy systems are:

Student Information System (SIS)

As existing systems change to adopt this standard, the Enterprise Data Governance team needs to be informed.