Intended Audience and Contact Information
| Contact | Chief Data Officer, Office of the CIO |
|---|---|
| UDM Domain | Person |
| Intended Audience | Internal UBC |
Purpose
This standard aims to achieve consistency around the data collected for Identity Verification and the format in which it is collected and stored.
This standard is based on Government of British Columbia’s Guidelines for the Acceptable Use of Names, Date of Birth and Sex (Gender) and Insurance Corporation of British Columbia’s Accepted ID Guidelines. This standard applies to all UBC applications collecting Identity Verification information. Exceptions are listed in the Dispensation section.
Standard
Identity Verification Standard
A person’s identity may be verified using one or combination of the primary identification documents1 listed on Collibra. A primary identification document is required for identity verification. A number of secondary identification documents, as listed on Collibra, may be used as supporting documents. None of the primary identification documents or secondary identification documents2 must have expired at the time of presentation.
All of the following attributes must be verified for the purpose of Identity Verification.
| Attribute | Requirement | Definition |
|---|---|---|
| Legal Name | Required | Legal name is the name that identifies a person for legal, administrative and other official purposes. A person’s legal name may be confirmed with official documents |
| Date of Birth | Required | Date a person was born. |
| Person Photo | Required | Photograph of a person. |
Identity Verification information of a person must only be collected "when it relates directly to and is necessary for a program or activity of UBC, and only from the individual, rather than from a third party"3.
Compliance
Compliance to this standard is required at every stage of the data lifecycle with the exception of dispensations listed on the Dispensation section.
- Applications where Identity Verification is collected, must collect this information as recommended in this standard.
- Enterprise Data Integration must adopt this standard.
Dispensation
Legacy systems are exempt from this data standard. Examples of legacy systems are:
- Student Information System (SIS)
- Human Resource Management System (HRMS)
- Finance Management System (FMS)
As systems are replaced, adoption of this standard is required.
As existing systems change to adopt this standard, the Enterprise Data Governance team needs to be informed.
Related Documents
- Guidelines for the Acceptable Use of Names, Date of Birth and Sex (Gender) (link broken)
- ICBC Accepted IDs
1Guidelines for the Acceptable Use of Names, Date of Birth and Sex (Gender)