Intended Audience and Contact Information
| Contact | Chief Data Officer, Office of the CIO |
|---|---|
| Intended Audience | Internal UBC |
| UDM Domain | Location |
| Data Standard ID | DS0099 |
Definition
Location Group is the highest level of Location Hierarchy.
Location Hierarchy is the ordered geographic structure of Location types.
Location Type is a categorization of Locations based on common characteristics or functions.
Purpose
This standard aims to achieve consistency around the data collected for Location Group, and the format in which it is collected and stored across the University.
This standard applies to all applications collecting Location Group data. Exceptions are listed in the Dispensation section.
Standard
A Location Group Type can represent a Campus, a collection of Hospitals, or groupings of off-campus sites. The following are the accepted values for Location Group Type:
| Accepted Data Value | Definition |
| Campus | The physical grounds and buildings of the University. |
| Off-Campus | A grouping of locations outside of the Campuses, that are owned or leased by UBC, or where UBC staff or faculty work, or where UBC owns assets. |
| Hospital | A grouping of Faculty of Medicine locations outside of the Campuses by Health Authority or health care system. |
The following are the accepted values for Campus Location Group Type:
| Accepted Data Value | Accepted Code | Definition |
|---|---|---|
|
UBC Vancouver Campus |
UBCV | A grouping of UBC locations in the Vancouver Campus. |
|
UBC Okanagan Campus |
UBCO | A grouping of UBC locations in the Okanagan Campus. |
The following are the accepted values for Off-Campus Location Group Type:
| Accepted Data Value | Accepted Code | Definition |
|---|---|---|
|
Lower Mainland Off-Campus |
LOFF | A grouping of UBC locations in the Lower Mainland, including Robson Square. |
|
Okanagan Off-Campus |
OOFF | A grouping of UBC locations in the City of Kelowna. |
|
Other British Columbia Off-Campus |
BOFF | A grouping of UBC locations in BC, outside the lower mainland and the city of Kelowna. |
|
Other Canadian Off-Campus |
COFF | A grouping of UBC locations in other Canadian regions outside of the Lower Mainland and the Okanagan. |
|
International Off-Campus |
IOFF | A grouping of international UBC locations. |
The following are the accepted values for Hospital Location Group Type:
| Data Value | Code | Definition |
|---|---|---|
|
Fraser Health |
FH | Health Authority responsible for the delivery of public hospital and community-based health services in the south-west region of British Columbia. |
|
Interior Health |
IH | Health Authority responsible for the delivery of public hospital and community-based health services in the south-west region of British Columbia. |
|
Island Health |
VIH | Health Authority responsible for the delivery of public hospital and community-based health services in Vancouver Island, the islands in the Salish Sea and the Johnstone Strait, and mainland communities north of Powell River. |
|
Northern Health |
NH | Health Authority responsible for the delivery of public hospital and community-based health services in Northern British Columbia. |
|
Vancouver Coastal Health |
VCH | Health Authority responsible for the delivery of public hospital and community-based health services across Coastal, Richmond and Vancouver areas of British Columbia. |
|
Provincial Health Services |
PHSA | Health Authority responsible for the province-wide delivery of specialized public health services and programs. |
| Providence Health Care | PHC | Catholic health care provider in the Vancouver Coastal region, with special services across British Columbia. |
Compliance
The above standard must be complied with at every stage of the data lifecycle with the exception of 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.
Mapping of Invalid Values from System(s) of Record (SoR) to Common Services
A common service can only accommodate standard reference data enumerations that are available in the SoR as approved by the Data Governance Steering Committee or Data Trustee.
A reference data value that does not match any of the standard reference data value enumerations is considered 'invalid'. Any records from a SoR containing an invalid reference data value for a given data element or attribute must be mapped as an 'empty' value in common service(s). Where a reference data value may potentially have the same meaning as a standard enumeration but named differently in the system of record can be corrected to match the appropriate standard enumeration. Please consult with the EDG team in such cases.
Additional reference data values in a SoR that are not part of the standard reference data enumerations are to be omitted in the common service.
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)
For any compliance questions or requests for a temporary dispensation, please contact the Enterprise Data Governance Team.