Data Reference Standard on Person(s): name architecture

1. Preamble

  • 1.1 This data reference standard is intended to ensure that departments and agencies of the Government of Canada use consistent fields for capturing the diverse set of names of persons.
  • 1.2 This data reference standard is intended to ensure that person names are described, collected and stored consistently in datasets to enable data interoperability and improve data quality.
    • 1.2.1 The appendix outlines the required person name fields to capture primary, secondary and alternate names, as well as names that consist of only one word (that is, mononyms) or which cannot be divided into two parts.
  • 1.3 This data reference standard will be reviewed as required by the data reference standard steward in consultation with the data reference standard custodian.
    • 1.3.1 Data reference standard steward: Immigration, Refugees and Citizenship Canada
    • 1.3.2 Data reference standard custodian: Treasury Board of Canada Secretariat
  • 1.4 The elements of personal information contained in this standard should be collected, used, retained, disclosed and disposed of in accordance with the requirements of the Privacy Act and its underlying policy suite.

2. Effective date

  • 2.1 This data reference standard takes effect on September 27, 2024.

3. Requirements

  • 3.1 This data reference standard provides details on the requirements set out in subsection 4.3.1 of the Directive on Service and Digital.
  • 3.2 Service owners and data practitioners must:
    • 3.2.1 Apply the mandatory data fields (outlined in the appendix) to record a person name or names within the Government of Canada according to the data attributes required for your program.

4. Application

  • 4.1 This data reference standard applies to organizations listed in section 6 of the Directive on Service and Digital.
  • 4.2 This data reference standard applies to all datasets developed after the effective date of this standard.

5. References

6. Enquiries

Appendix: data architecture tables

Person name fields may be repeated to accommodate more than one value. If possible, the source of the name must be accounted for, either once for the entire table or as a field within the table. If a legal name is collected, it must be captured according to Table 1, and the collection of an alternate name must also be offered.

Table 1: required primary and secondary person name fields
Field name Description
Primary name May be the surname, family name, last name, maiden name or married name, main name, mononym (that is, a name consisting of only one word) and in some cases, the entire name where the holder’s name cannot be divided into two parts.
Secondary name The portion of a person’s name that is not the primary name. All remaining portions of the name would be entered into this field.
Name type A metadata field to describe a person name for classifying it for legal, administrative or other purposes (for example, legal name, mononym).
Name source Where the name comes from (for example, an evidence of identity (EOI) document, a court-issued document or an attestation by the person). Primary and secondary names should come from the same source.
Source date The date of issuance of an EOI document or other name source.
Name collection date The date the person name is captured in the dataset.
Last modified date The most recent date any person name field was updated or changed.
Table 2: alternate person name fields (required if applicable)
Field name Description
Alternate primary name An alternate surname, chosen name, preferred name or alias name of a client.
Alternate secondary name Alternate given name or names of a client that can be used to identify which names in the secondary name field should be used for correspondence (for example, a chosen or preferred name or alias).
Alternate name type A metadata field to describe an alternate name for classifying it for legal, administrative or other purposes (for example, a chosen or preferred name, alias or mononym).
Alternate name source Where the name comes from (for example, an EOI document, a court-issued document or an attestation by the person). For each alternate name, the alternate primary and alternate secondary names should come from the same source.
Alternate source date The date of issuance of a document or other name source.
Alternate name collection date The date the name is captured in the dataset.

Page details

Date modified: