Financial and Charitable Donors

Income Statistics Division

User's Guide

Table of contents

Skip to text

RRSP Contributors (product #17C0006)
RRSP Contribution Limits (ROOM) (product # 17C0011)
Canadian Savers (product #17C0009)
Canadian Investors (product #17C0007)
Canadian Investment Income (product #17C0008)
Canadian Capital Gains (product #17C0012)
Canadian Taxfilers (product #17C0010)
Charitable Donations (product #13C0014)
Data Source
Data Frequency
Data Quality
Confidentiality and Rounding
Glossary of Terms
Statistical Tables - Footnotes and Historical Availability
Geography

Geographic Levels – Postal Geography

Geographic Levels – Census Geography
Geographic Levels – Special Geography
We Invite Your Comments
List of Data Products Available

Statistics Canada
Income Statistics Division
income@statcan.gc.ca
February 2013

Text begins

RRSP Contributors (product #17C0006)

This databank provides information on taxfilers who contributed to a Registered Retirement Savings Plan (RRSP) during the tax year under review.

The content of the databank is as follows:

Table 1:  Summary
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk (no longer available)
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Number of RRSP contributors
Column 8 – Average age of RRSP contributors
Column 9 – Median employment income of RRSP contributors
Column 10 – 75th percentile of employment income of RRSP contributors
Column 11 – Amount of RRSP dollars reported (in thousands of dollars)
Column 12 – Median RRSP contribution

Table 2:  Age groups
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk (no longer available)
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Total number of RRSP contributors
Column 8 – Percent of contributors 0 to 24 years of age
Column 9 – Percent of contributors 25 to 34 years of age
Column 10 – Percent of contributors 35 to 44 years of age
Column 11 – Percent of contributors 45 to 54 years of age
Column 12 – Percent of contributors 55 to 64 years of age
Column 13 – Percent of contributors 65+ years of age
Column 14 – Total amount of RRSP dollars reported (in thousands of dollars)
Column 15 – Percent of contributions reported by age group 0 to 24
Column 16 – Percent of contributions reported by age group 25 to 34
Column 17 – Percent of contributions reported by age group 35 to 44
Column 18 – Percent of contributions reported by age group 45 to 54
Column 19 – Percent of contributions reported by age group 55 to 64
Column 20 – Percent of contributions reported by age group 65+

Table 3:  Sex
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk (no longer available)
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Percent of taxfilers who are male
Column 8 – Percent of taxfilers who are female
Column 9 – Total number of RRSP Contributors
Column 10 – Percent of contributors who are male
Column 11 – Percent of contributors who are female
Column 12 – Total amount of RRSP dollars reported (in thousands of dollars)
Column 13 – Percent of contributions reported by males
Column 14 – Percent of contributions reported by females
Column 15 – Median RRSP contribution of all contributors
Column 16 – Median RRSP contribution of males
Column 17 – Median RRSP contribution of females

Table 4:  Income groups
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk (no longer available)
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Total number of RRSP contributors
Column 8 – Percent of RRSP contributors with total income less than $20,000
Column 9 – Percent of RRSP contributors with total income between $20,000 and $39,999
Column 10 – Percent of RRSP contributors with total income between $40,000 and $59,999
Column 11 – Percent of RRSP contributors with total income between $60,000 and $79,999
Column 12 – Percent of RRSP contributors with total income $80,000+
Column 13 – Total amount of RRSP dollars reported (in thousands of dollars)
Column 14 – Percent of total RRSP amount reported by contributors with total income less than $20,000
Column 15 – Percent of total RRSP amount reported by contributors with total income between $20,000 and $39,999
Column 16 – Percent of total RRSP amount reported by contributors with total income between $40,000 and $59,999
Column 17 – Percent of total RRSP amount reported by contributors with total income between $60,000 and $79,999
Column 18 – Percent of total RRSP amount reported by contributors with total income $80,000+

RRSP Contribution Limits (ROOM) (product # 17C0011)

The Registered Retirement Savings Plan (RRSP) Room databank was created to provide information on the RRSP contribution limit (RRSP Room) available. This product can be used in conjunction with the RRSP databank which concentrates on the RRSP contributors.

In 1989, the legislation dictated that contribution limits for persons not contributing to a registered pension plan (RPP) or a Deferred Profit Sharing Plan (DPSP) was 20% of earned income to a maximum of $7,500. The limit for RPP and DPSP members was 20% of earned income to a maximum of $3,500 less the amount contributed by the employee to the RPP or DPSP.

Further amendments to the Income Tax Act relative to RRSPs, taking effect January 1, 1991, were intended to make RRSP contribution limits more equitable. The RRSP contribution limit was set at 18% of earned income for the previous tax year, to a set maximum minus the Pension Adjustment (PA). The PA represents the calculated value of the pension accrued through an RPP or a DPSP in the previous tax year.

Total RRSP Room represents the deduction limit that Canadians can claim with respect to contributions made to RRSPs. It does not include income eligible for transfers, such as retiring allowances and severance pay that may be rolled over into RRSPs. The sum of the deduction limit and rollovers represents the maximum amount that can be claimed as a deduction on line 208 of the income tax return.

Figure 1 – New room- Calculations of RRSP contributions limits

Earned income in tax year New room Unused room Total room (for tax year+1)
1991 For 1992 pre1991 = 0 New room only
1992 For 1993 1991 to 1992 Unused room + new room
1993 For 1994 1991 to 1993 Unused room + new room
1994 For 1995 1991 to 1994 Unused room + new room
1995 For 1996 1991 to 1995 Unused room + new room
1996 For 1997 1991 to 1996 Unused room + new room
1997 For 1998 1991 to 1997 Unused room + new room
1998 For 1999 1991 to 1998 Unused room + new room
1999 For 2000 1991 to 1999 Unused room + new room
2000 For 2001 1991 to 2000 Unused room + new room
2001 For 2002 1991 to 2001 Unused room + new room
2002 For 2003 1991 to 2002 Unused room + new room
2003 For 2004 1991 to 2003 Unused room + new room
2004 For 2005 1991 to 2004 Unused room + new room
2005 For 2006 1991 to 2005 Unused room + new room
2006 For 2007 1991 to 2006 Unused room + new room
2007 For 2008 1991 to 2007 Unused room + new room
2008 For 2009 1991 to 2008 Unused room + new room
2009 For 2010 1991 to 2009 Unused room + new room
2010 For 2011 1991 to 2010 Unused room + new room
2011 For 2012 1991 to 2011 Unused room + new room

 

Calculation of contribution limits

For 1990, maximum contributions are:

  • for non-participants in RPPs and DPSPs, the lesser of 20% of earned income and $7,500
  • for participants in RPPs and DPSPs, 20% of earned income to a maximum of $3,500; the maximum is reduced according to employee contributions to RPPs/DPSPs.

For 1991 to 2011:

New room = 18% of earned income - PA - PSPA

Percentage of earned income to a maximum of

  • $11,500 for 1991
  • $12,500 for 1992 and 1993
  • $13,500 for 1994
  • $14,500 for 1995
  • $13,500 for 1996
  • $13,500 for 1997
  • $13,500 for 1998
  • $13,500 for 1999
  • $13,500 for 2000
  • $13,500 for 2001
  • $13,500 for 2002
  • $14,500 for 2003
  • $15,500 for 2004
  • $16,500 for 2005
  • $18,000 for 2006
  • $19,000 for 2007
  • $20,000 for 2008
  • $21,000 for 2009
  • $22,000 for 2010
  • $22,450 for 2011

Where PA = Pension Adjustment, and PSPA = Past Service Pension Adjustment

Prior to tax year 2000 (Room 2001):

Total Room (for tax year+1) = Unused Room (from 1991 forward) + New Room

For tax years 2000 to 2011 (Room 2001 to Room 2012):

Total Room (for tax year+1) = Unused Room accumulated since 1991 + (18% of earned income – Pension adjustment) – Current tax year contributions excluding rollovers

Data source

Prior to the release of data for tax year 2000, the RRSP ROOM data were derived from a file received annually from the Canada Revenue Agency (CRA, formerly Canada Customs and Revenue Agency). CRA generated the data from an administrative system designed in response to changes to the Income Tax Act with respect to Registered Retirement Savings Plans, changes that took effect January 1, 1991.

The system records information for each taxfiler with "earned income" (income used to determine the RRSP deduction limit). The information includes each year's earned income, new room amounts and unused room amounts carried forward.

Starting with the 2001 ROOM (2000 tax data), the amount of RRSP Room is calculated from other variables on the preliminary file, variables which were previously unavailable.

This year's release of the RRSP Room data is based on 2011 income tax returns. Contributions towards these limits can be made up to February 2013, to be reported on the 2012 tax returns. The mailing address at the time of filing is the basis for the geographic information in the tables.

Data quality

The calculated Room amount is equal to the amount on the Canada Revenue Agency (CRA) RRSP Room file.

The content of the databank is as follows:

Table 1: Persons with room
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk number (no longer available)
Column 4 – Level of geography (see Geography section)
Column 5 – Place name
Column 6 – Amount of Room dollars reported (in thousands of $)
Column 7 – Amount of Unused Room dollars reported (in thousands of $)
Column 8 – Amount of New Room dollars reported (in thousands of $)
Column 9 – Number of taxfilers with Room
Column 10 – Number of taxfilers with Unused Room
Column 11 – Number of taxfilers with New Room

Table 2: Characteristics of persons with new room
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk number (no longer available)
Column 4 – Level of geography (see Geography section)
Column 5 – Place name
Column 6 – Number of taxfilers with New Room
Column 7 – Average Age of taxfilers with New Room
Column 8 – Percentage Female taxfilers with New Room
Column 9 – Median Earned Income of taxfilers with New Room
Column 10 – Average New Room
Column 11 – Percentage of taxfilers with New Room between $500 and $2,399
Column 12 – Percentage of taxfilers with New Room between $2,400 and $4,699
Column 13 – Percentage of taxfilers with New Room between $4,700 and $7,799
Column 14 – Percentage of taxfilers with New Room between $7,800 and $12,999
Column 15 – Percentage of taxfilers with New Room greater than $13,000

Additional notes for Table 2:

Column 11: The first value represents the 25th percentile and is recalculated periodically.
Column 12: The first value represents the 50th percentile and is recalculated periodically.
Column 13: The first value represents the 75th percentile and is recalculated periodically.
Column 14: The first value represents the 90th percentile and is recalculated periodically.
Column 15: The value represents the 97th percentile and is recalculated periodically.

Canadian Savers (product #17C0009)

Line 120 – Taxable amount of dividends from taxable Canadian corporations
Line 121 – Interest and other investment income

This databank provides information on taxfilers who have been classified as savers.

Savers are defined as taxfilers who reported interest and investment income on line 121, but no dividend income on line 120 of the personal income tax return.

Interest and investment income sources would include interest from Canada Savings bonds, bank accounts, treasury bills, investment certificates, term deposits, earnings on life insurance policies as well as foreign interest and dividend income.

Dividend income would include dividends from taxable Canadian corporations (as stocks or mutual funds), but not dividends from foreign investments.

Taxfilers reporting Canadian dividend income would not be counted as savers, but would be classified as investors.

The content of the databank is as follows:

Table 1: Summary
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk (no longer available)
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Number of savers
Column 8 – Average age of savers
Column 9 – Median total income of savers
Column 10 – Total amount of interest dollars reported (in thousands of dollars)
Column 11 – Median of interest dollars

Table 2: Age groups
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk (no longer available)
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Total number of savers
Column 8 – Percent of savers 0-24 years of age
Column 9 – Percent of savers 25-34 years of age
Column 10 – Percent of savers 35-44 years of age
Column 11 – Percent of savers 45-54 years of age
Column 12 – Percent of savers 55-64 years of age
Column 13 – Percent of savers 65+ years of age
Column 14 – Total amount of interest income dollars reported (in thousands of dollars)
Column 15 – Percent of interest income reported by age group 0-24
Column 16 – Percent of interest income reported by age group 25-34
Column 17 – Percent of interest income reported by age group 35-44
Column 18 – Percent of interest income reported by age group 45-54
Column 19 – Percent of interest income reported by age group 55-64
Column 20 – Percent of interest income reported by age group 65+

Table 3: Sex
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk (no longer available)
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Percent of taxfilers who are male
Column 8 – Percent of taxfilers who are female
Column 9 – Total number of savers
Column 10 – Percent of savers who are male
Column 11 – Percent of savers who are female
Column 12 – Total amount of interest income reported (in thousands of dollars)
Column 13 – Percent of interest income reported by males
Column 14 – Percent of interest income reported by females
Column 15 – Median interest income of all savers
Column 16 – Median interest income of all male savers
Column 17 – Median interest income of all female savers

Table 4: Income groups
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk (no longer available)
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Total number of savers
Column 8 – Percent of savers with total income less than $20,000
Column 9 – Percent of savers with total income between $20,000 and $39,999
Column 10 – Percent of savers with total income between $40,000 and $59,999
Column 11 – Percent of savers with total income between $60,000 and $79,999
Column 12 – Percent of savers with total income $80,000+
Column 13 – Total amount of interest income reported (in thousands of dollars)
Column 14 – Percent of interest income reported by savers with total income less than $20,000
Column 15 – Percent of interest income reported by savers with total income between $20,000 and $39,999
Column 16 – Percent of interest income reported by savers with total income between $40,000 and $59,999
Column 17 – Percent of interest income reported by savers with total income between $60,000 and $79,999
Column 18 – Percent of interest income reported by savers with total income $80,000+

Canadian Investors (product #17C0007)

Line 120 – Taxable amount of dividends from taxable Canadian corporations
Line 121 – Interest and other investment income

This databank provides information on taxfilers classified as investors.

Investors include taxfilers who reported dividend income on line 120 of their personal tax return. They may or may not have also reported interest and other investment income on line 121. When income is also reported on line 121, that amount is added to the amount of dividend income received, and the sum becomes the investment income of the investor.

The content of the databank is as follows:

Table 1: Summary
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk (no longer available)
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Number of investors
Column 8 – Average age of investors
Column 9 – Median total income of investors
Column 10 – Amount of investment dollars (in thousands of dollars)
Column 11 – Percentage of the investment income derived from dividends
Column 12 – Median investment income

Table 2: Age groups
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk (no longer available)
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Total number of investors
Column 8 – Percent of investors 0-24 years of age
Column 9 – Percent of investors 25-34 years of age
Column 10 – Percent of investors 35-44 years of age
Column 11 – Percent of investors 45-54 years of age
Column 12 – Percent of investors 55-64 years of age
Column 13 – Percent of investors 65+ years of age
Column 14 – Total amount of investment income dollars reported (in thousands of dollars)
Column 15 – Percent of investment income reported by age group 0-24
Column 16 – Percent of investment income reported by age group 25-34
Column 17 – Percent of investment income reported by age group 35-44
Column 18 – Percent of investment income reported by age group 45-54
Column 19 – Percent of investment income reported by age group 55-64
Column 20 – Percent of investment income reported by age group 65+

Table 3: Sex
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk (no longer available)
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Percent of taxfilers who are male
Column 8 – Percent of taxfilers who are female
Column 9 – Total number of investors
Column 10 – Percent of investors who are male
Column 11 – Percent of investors who are female
Column 12 – Total amount of investment income reported (in thousands of dollars)
Column 13 – Percent of investment income reported by males
Column 14 – Percent of investment income reported by females
Column 15 – Median investment income of all investors
Column 16 – Median investment income of all male investors
Column 17 – Median investment income of all female investors

Table 4: Income groups
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk (no longer available)
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Total number of investors
Column 8 – Percent of investors with total income less than $20,000
Column 9 – Percent of investors with total income between $20,000 and $39,999
Column 10 – Percent of investors with total income between $40,000 and $59,999
Column 11 – Percent of investors with total income between $60,000 and $79,999
Column 12 – Percent of investors with total income $80,000+
Column 13 – Total amount of investment income reported (in thousands of dollars)
Column 14 – Percent of investment income reported by investors with total income less than $20,000
Column 15 – Percent of investment income reported by investors with total income between $20,000 and $39,999
Column 16 – Percent of investment income reported by investors with total income between $40,000 and $59,999
Column 17 – Percent of investment income reported by investors with total income
between $60,000 and $79,999
Column 18 – Percent of investment income reported by investors with total income
$80,000+

Canadian Investment Income (product #17C0008)

Line 120 – Taxable amount of dividends from taxable Canadian corporations
Line 121 – Interest and other investment income

This databank provides information on taxfilers who reported dividend income on line 120 of the tax return, or interest and other investment income on line 121, or both. These taxfilers include those designated as savers and those designated as investors in two other databanks available: Canadian Savers and Canadian Investors. In this databank, investment income includes both interest and dividends.

Dividend income includes dividends from taxable Canadian corporations (as stocks or mutual funds).

Interest and other investment income sources include interest from Canada Savings bonds, bank accounts, treasury bills, investment certificates, term deposits, earnings on life insurance policies as well as foreign interest and dividend income.

The content of the databank is as follows:

Table 1: Summary
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk (no longer available)
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Number of taxfilers with investment income
Column 8 – Average age of taxfilers with investment income
Column 9 – Median total income of taxfilers with investment income
Column 10 – Reported investment income dollars for all taxfilers with investment income (in thousands of dollars)
Column 11 – Median investment income for all taxfilers with investment income

Table 2: Age groups
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk (no longer available)
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Total number of receivers of investment income
Column 8 – Percent of receivers of investment income 0-24 years of age
Column 9 – Percent of receivers of investment income 25-34 years of age
Column 10 – Percent of receivers of investment income 35-44 years of age
Column 11 – Percent of receivers of investment income 45-54 years of age
Column 12 – Percent of receivers of investment income 55-64 years of age
Column 13 – Percent of receivers of investment income 65+ years of age
Column 14 - Total amount of investment income dollars reported (in thousands of dollars)
Column 15 – Percent of investment income reported by age group 0-24
Column 16 – Percent of investment income reported by age group 25-34
Column 17 – Percent of investment income reported by age group 35-44
Column 18 – Percent of investment income reported by age group 45-54
Column 19 – Percent of investment income reported by age group 55-64
Column 20 – Percent of investment income reported by age group 65+

Table 3: Sex
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk (no longer available)
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Percent of taxfilers who are male
Column 8 – Percent of taxfilers who are female
Column 9 – Total number of receivers of investment income
Column 10 – Percent of receivers of investment income who are male
Column 11 – Percent of receivers of investment income who are female
Column 12 – Total amount of investment income reported (in thousands of dollars)
Column 13 – Percent of investment income reported by males
Column 14 – Percent of investment income reported by females
Column 15 – Median investment income of all receivers of investment income
Column 16 – Median investment income of all male receivers of investment income
Column 17 – Median investment income of all female receivers of investment income

Table 4: Income groups
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk (no longer available)
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Total number of receivers of investment income
Column 8 – Percent of receivers of investment income with total income less than $20,000
Column 9 – Percent of receivers of investment income with total income between $20,000 and $39,999
Column 10 – Percent of receivers of investment income with total income between $40,000 and $59,999
Column 11 – Percent of receivers of investment income with total income between $60,000 and $79,999
Column 12 – Percent of receivers of investment income with total income $80,000+
Column 13 – Total amount of investment income reported (in thousands of dollars)
Column 14 – Percent of investment income reported by receivers of investment income with total income less than $20,000
Column 15 – Percent of investment income reported by receivers of investment income with total income between $20,000 and $39,999
Column 16 – Percent of investment income reported by receivers of investment income with total income between $40,000 and $59,999
Column 17 – Percent of investment income reported by receivers of investment income with total income between $60,000 and $79,999
Column 18 – Percent of investment income reported by receivers of investment income with total income $80,000+

Canadian Capital Gains (product #17C0012)

Line 127 – Taxable amount of capital gains

This databank provides information on taxfilers who reported capital gains during the tax year under review.

Line 127 of the T1 income tax return contains the amount of taxable capital gains reported by Canadians; this value is half the actual capital gains received. The information in this databank reflects the total capital gains received; amounts reported have been grossed up to reflect this total.

The content of the databank is as follows:

Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk (no longer available)
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Number of taxfilers reporting capital gains
Column 8 – Percent of taxfilers reporting capital gains who had a total income under $20,000
Column 9 – Percent of taxfilers reporting capital gains who had a total income between $20,000 and $39,999
Column 10 – Percent of taxfilers reporting capital gains who had a total income between $40,000 and $59,999
Column 11 – Percent of taxfilers reporting capital gains who had a total income between $60,000 and $79,999
Column 12 – Percent of taxfilers reporting capital gains who had a total income of $80,000+
Column 13 – Total value of capital gains (in thousands of dollars)
Column 14 – Percent of capital gains reported by taxfilers with a total income under $20,000
Column 15 – Percent of capital gains reported by taxfilers with a total income between $20,000 and $39,999
Column 16 – Percent of capital gains reported by taxfilers with a total income between $40,000 and $59,999
Column 17 – Percent of capital gains reported by taxfilers with a total income between $60,000 and $79,999
Column 18 – Percent of capital gains reported by taxfilers with a total income of $80,000+

Canadian Taxfilers (product #17C0010)

This databank provides a demographic and income profile of all Canadians who filed a personal tax return in the reference year.

The content of the databank is as follows:

Table 1: Summary
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk (no longer available)
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Number of taxfilers
Column 7 – Percent of taxfilers 0-24 years of age
Column 8 – Percent of taxfilers 25-34 years of age
Column 9 – Percent of taxfilers 35-44 years of age
Column 10 – Percent of taxfilers 45-54 years of age
Column 11 – Percent of taxfilers 55-64 years of age
Column 12 – Percent of taxfilers 65+ years of age
Column 13 – Average age of taxfilers
Column 14 – Median total income of taxfilers
Column 15 – 75th percentile of total income of taxfilers
Column 16 – 85th percentile of total income of taxfilers
Column 17 – 95th percentile of total income of taxfilers
Column 18 – Median employment income of taxfilers
Column 19 – 75th percentile of employment income of taxfilers

Table 2: Income Groups
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk (no longer available)
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Number of taxfilers
Column 7 – Percent of taxfilers with total income less than $20,000
Column 8 – Percent of taxfilers with total income between $20,000 and $39,999
Column 9 – Percent of taxfilers with total income between $40,000 and $59,999
Column 10 – Percent of taxfilers with total income between $60,000 and $79,999
Column 11 – Percent of taxfilers with total income $80,000+
Column 12 – Value of total income (in thousands of dollars)
Column 13 – Percent of total income reported by taxfilers with total income less than $20,000
Column 14 – Percent of total income reported by taxfilers with total income between $20,000 and $39,999
Column 15 – Percent of total income reported by taxfilers with total income between $40,000 and $59,999
Column 16 – Percent of total income reported by taxfilers with total income between $60,000 and $79,999
Column 17 – Percent of total income reported by taxfilers with total income $80,000+

Charitable Donations (product #13C0014)

Line 340 – Allowable charitable donations and government gifts

This databank provides information on taxfilers classified as charitable donors. Charitable donors are defined as taxfilers reporting donations on line 340 of the tax return.

Canadians contribute in many ways to charitable organizations. The databank on charitable donors provides information on taxfilers who claimed a tax credit for charitable donations on their income tax return in the reference year. These data may include donations that might be denied by the Canada Revenue Agency (CRA) after an audit. To find out more about why donations might be denied (i.e. tax shelter gifting arrangements, false receipting) please go to the Canada Revenue Agency website: www.cra-arc.gc.ca

Persons making charitable donations, but not reporting them on their personal tax return are not included in this databank. These include donations for which no receipt was provided and donations for which the receipt was lost. No estimate of such donations is included in these data.

Only donations made to approved organizations are allowable as deductions in the tax system. Donations are eligible if made to Canadian registered charities and Canadian amateur athletic associations. They are also eligible if made to: prescribed universities outside Canada; certain tax exempt housing organizations in Canada; Canadian municipalities; the United Nations; and certain charities outside Canada to which the Government of Canada has made a gift.

It is possible to carry donations forward for up to five years after the year in which they were made. In the reference year, it is possible to claim donations made in any of the previous five years, as long as they were not already claimed in a prior year. The donations made in the reference year could be claimed the same year, or could be carried forward to any of the next five years. According to tax laws, taxfilers are permitted to claim both their donations and those made by their spouses to get better tax benefits. Consequently, the number of persons who made charitable donations may be higher than the number who claimed tax credits.

A change in tax regulations was introduced in 2007. Taxfilers contributing to a recognized charity (as outlined above) were eligible to claim a tax credit of 15% of their donations on the first $200, and 29% on the rest. In 2006, the tax credit was 15.25% on the first $200 and 29% on the rest. In 2005, the tax credit was 15% on the first $200 and 29% on the rest. From 2001 to 2004, the tax credit was 16% on the first $200 and 29% on the rest. From 1992 to 2000, the tax credit was 17% on the first $200 and 29% on the rest. Previously, taxfilers had to give $250 to charity before the 29% credit was available.

The content of the databank is as follows:

Table 1: Summary
Column 1 - City identification number
Column 2 - Postal area
Column 3 - Postal walk (no longer available)
Column 4 - Level of geography (see Geography section)
Column 5 - Place name
Column 6 - Total Number of taxfilers
Column 7 - Number of charitable donors
Column 8 - Average age of donors
Column 9 - Average donation for age group 0-24
Column 10 - Average donation for age group 25-34
Column 11 - Average donation for age group 35-44
Column 12 - Average donation for age group 45-54
Column 13 - Average donation for age group 55-64
Column 14 - Average donation for age group 65+
Column 15 - Total amount of charitable donations (thousands of $)
Column 16 - Median donation
Column 17 - Median total income of donors
Column 18 - 75th percentile of donors' total income

Table 2: Age and Sex (new beginning with 1995)
Column 1 - City identification number
Column 2 - Postal area
Column 3 - Postal walk (no longer available)
Column 4 - Level of geography (see Geography section)
Column 5 - Place name
Column 6 - Total Number of taxfilers
Column 7 - Percent of taxfilers who are male
Column 8 - Percent of taxfilers who are female
Column 9 - Number of charitable donors
Column 10 - Percent of charitable donors who are male
Column 11 - Percent of charitable donors who are female
Column 12 - Percent of donors 0 - 24 years of age
Column 13 - Percent of donors 25 - 34 years of age
Column 14 - Percent of donors 35 - 44 years of age
Column 15 - Percent of donors 45 - 54 years of age
Column 16 - Percent of donors 55 - 64 years of age
Column 17 - Percent of donors 65+ years of age
Column 18 - Total median donation
Column 19 - Median donation of males
Column 20 - Median donation of females
Column 21 - Total amount of charitable donations (thousands of $)
Column 22 - Total amount of charitable donations for males (thousands of $)
Column 23 - Total amount of charitable donations for females (thousands of $)

Table 3: Income Groups (new beginning with 1997)
Column 1 - City identification number
Column 2 - Postal area
Column 3 - Postal walk (no longer available)
Column 4 - Level of geography (see Geography section)
Column 5 - Place name
Column 6 - Total number of taxfilers
Column 7 - Total number of charitable donors
Column 8 - Percent of charitable donors with total income less than $20,000
Column 9 - Percent of charitable donors with total income between $20,000 and $39,999
Column 10 - Percent of charitable donors with total income between $40,000 and $59,999
Column 11 - Percent of charitable donors with total income between $60,000 and $79,999
Column 12 - Percent of charitable donors with total income $80,000+
Column 13 - Total value of charitable donations (in thousands of dollars)
Column 14 - Percent of donations reported by donors with total income under $20,000
Column 15 - Percent of donations reported by donors with total income between $20,000 and $39,999
Column 16 - Percent of donations reported by donors with total income between $40,000 and $59,999
Column 17 - Percent of donations reported by donors with total income between $60,000 and $79,999
Column 18 - Percent of donations reported by donors with total income $80,000+

Data Source

The financial databanks are derived from income tax returns. For the most part, tax returns were filed in the spring of the year following the reference year. For example, for the 2011 tax year, income tax returns were filed by April 30, 2012.

The mailing address at the time of filing is the basis for the geographic information in the tables.

Demographic characteristics such as age are given as of December 31 of the tax year. Income information is for the calendar year under review.

Data Frequency

Data are updated on an annual basis.

Data Quality

i) Number of Canadian taxfilers

The data used are direct counts from tax files.  For the 2011 tax year, 25.4 million Canadians or 73.0% filed tax returns.

Figure 2 – Number of Canadian Taxfilers

Tax year Number of taxfilers ('000) Date of population estimate Population ('000) Coverage (%)
1991 18,786 April 1, 1992 28,270 66.5
1992 19,267 April 1, 1993 28,601 67.4
1993 19,882 April 1, 1994 28,907 68.8
1994 20,184 April 1, 1995 29,212 69.1
1995 20,536 April 1, 1996 29,514 69.6
1996 20,772 April 1, 1997 29,818 69.7
1997 21,113 April 1, 1998 30,080 70.2
1998 21,431 April 1, 1999 30,315 70.7
1999 21,893 April 1, 2000 30,594 71.6
2000 22,249 April 1, 2001 30,911 72.0
2001 22,804 April 1, 2002 31,252 73.0
2002 22,968 April 1, 2003 31,548 72.8
2003 23,268 April 1, 2004 31,846 73.1
2004 23,625 April 1, 2005 32,143 73.5
2005 23,952 April 1, 2006 32,471 73.8
2006 24,258 April 1, 2007 32,818 73.9
2007 24,624 April 1, 2008 33,191 74.2
2008 24,987 April 1, 2009 33,604 74.4
2009* 24,321 April 1, 2010 34,002 71.5
2010* 24,495 April 1, 2011 34,368 71.3
2011* 24,842 April 1, 2012 34,754 71.5

Percent coverage is based on a comparison of the number of taxfilers in the Income Statistics Division's taxfilers databank and the population estimates from the Statistics Canada CANSIM table 051-0005, now available on the Statistics Canada web site.

* Since 2009, the count of tax filers is based on the T1 preliminary tax file from the Canada Revenue Agency.

ii) Elderly population

Some elderly Canadians receiving only Old Age Security and Guaranteed Income Supplement do not file because they have low or no taxable income. However, with the introduction of the Federal Sales Tax (FST) Credit in 1986 and the Goods and Services Tax (GST) Credit in 1990, the percentage of the elderly population filing tax returns has increased.

iii) Low Income

Persons with low income have no tax liability and are not required to file tax returns. However, with the introduction of the Child Tax Credit in 1978, the Federal Sales Tax (FST) Credit in 1986, the Goods and Services Tax (GST) Credit in 1990, and the Child Tax Benefits in 1993, persons with low income are likely to file tax returns to apply for these credits.

Confidentialityand Rounding

Over the years since its creation, the T1 Family File (T1FF) has become known as a reliable, annual source for income and demographic estimates. To protect the confidentiality of Canadians, all data are subject to the confidentiality procedures of rounding and suppression.

Developmental work and testing resulted in different confidentiality procedures that were applied to the Financial and Charitable Donors databank for the reference year 2007; it consisted of introducing a certain distortion in the data instead of using the suppression method. However, when the new methodology was applied to the data of the other standard products of Income Statistics Division, the distortion component was no more an option due to the complexity of all the other databanks. Therefore, in an effort to harmonize the confidentiality rules across all the standard products of Income Statistics division, it has been decided to revert back to the suppression rules.

These measures maintain the confidentiality of the data. All counts are rounded. Rounding may increase, decrease, or cause no change to counts. Rounding can affect the results obtained from calculations. For example, when calculating percentages from rounded data, results may be distorted as both the numerator and denominator have been rounded. The distortion can be greatest with small numbers.

All reported amounts are rounded to the nearest $5,000 dollars.

Since 1990, data cells represent counts of 15 or greater, and are rounded to a base of 10. For example, a cell count of 15 would be rounded to 20 and a cell count of 24 would be rounded to 20.

Note: Counts represent the number of persons.
Reported amounts are aggregate dollar amounts reported.

In the data tables:

Medians, Percentiles and Average amount are rounded to the nearest ten dollars.

Percentages are published with no decimal and calculated on rounded data; therefore, the sum of percentages might not equal 100% in the case of small counts.

Suppressed Data

To maintain confidentiality, data cells have been suppressed whenever:

  • areas comprise less than 100 taxfilers;
  • cells represent less than 15 taxfilers;
  • cells were dominated by a single filer;

Suppressed data may occur:

i) Within one area:

  • when one of the income categories is suppressed, a second category must also be suppressed to avoid disclosure of confidential data by subtraction (called residual disclosure);
  • when one of the gender categories is suppressed, the other gender category must also be suppressed to avoid residual disclosure;
  • when one age group category is suppressed, another age group must also be suppressed to avoid residual disclosure.

ii) Between areas:

  • when a variable amount in one area is suppressed, that variable amount is also suppressed in another area to prevent disclosure by subtraction.

Glossary of Terms

75th percentile

Total income values are ranked from highest to lowest and the value reported as being the 75th percentile indicates that 25% of the taxfilers report an income equal or above that amount and 75% fall below. Percentiles are calculated for each geographical level.

For example, if the 75th percentile of total income is shown as $60,000 this means that 25% of the population under review has a total income greater than or equal to $60,000 and 75% of the population has a total income less than or equal to $60,000.

85th percentile

Starting with the 2007 data, the dollar value of the 85th percentile appears in the tables instead of the percentage above the 85th percentile like it was in previous years. Total income values are ranked from highest to lowest and the value reported as being the 85th percentile indicates that 15% of the taxfilers report an income equal or above that amount and 85% fall below. Percentiles are calculated for each geographical level.

For example, if the 85th percentile of total income is shown as $65,000 this means that 15% of the taxfilers has a total income greater than or equal to $65,000

95th percentile

Starting with the 2007 data, the dollar value of the 95th percentile appears in the tables instead of the percentage above the 95th percentile like it was in previous years. Total income values are ranked from highest to lowest and the value reported as being the 95th percentile indicates that 5% of the taxfilers report an income equal or above that amount and 95% fall below. Percentiles are calculated for each geographical level.

For example, if the 95th percentile of total income is shown as $90,000 this means that 5% of the population under review has a total income greater than or equal to $90,000

Age

Calculated as of December 31 of the reference year (i.e., tax year minus year of birth).

Capital Gains

Line 127 of the T1 income tax return shows "taxable capital gains" or half of the capital gains actually received.  The information in this databank has been grossed up to represent the total capital gains received.

Charitable donation

Is the allowable portion of total donations, as reported on the income tax return.

Charitable donor

Is defined as a taxfiler reporting a charitable donation amount on line 340 of the personal income tax form.

CityID

Since municipality names can be, in some cases, quite long and cumbersome for handling in electronic files, municipalities are given a "city identification number". Starting in 2007, the CityID is a five digits alpha-numeric component. It is created with the first letter of Postal CodeOM followed by "9" and a four digits number. Each first letter of Postal Code is allocated a range of number from 1 to 9999 (more explanation in geography section).

Deferred profit sharing plan (DPSP)

An employer-sponsored savings plan registered by the Canada Revenue Agency. Contributions to these plans by the employer (employees cannot contribute) are based on profits. The amount accumulated in these plans can be paid out as a lump sum at retirement or termination of employment, transferred to an RRSP, received in instalments over a period not to exceed ten years, or used to purchase an annuity.

Dividend income

Includes taxable amount of dividends (eligible and other than eligible) received from taxable Canadian corporations (as stocks or mutual funds) as reported on line 120 of the personal income tax return, and then grossed down to the actual amounts received; dividend income does not include dividends received from foreign investments (which are included in interest income and reported on line 121).

Earned income

The income used to determine the RRSP deduction limit. It includes such items as employment income (less union dues and expenses), net business and rental income, disability payments and alimony received. Alimony payments, current year business and rental losses are deducted from this amount. Most investment income (other than rents) is not considered earned income. In calculating the RRSP deduction limit, earned income from the previous year is used.

Employment income

The total reported employment income. Employment income includes wages and salaries, commissions from employment, training allowances, tips and gratuities, and self-employment income (net income from business, profession, farming, fishing and commissions) and Indian Employment Income (new in 1999).

Interest income

Amounts Canadians claimed on line 121 of the personal income tax return. This amount includes interest generated from bank deposits, Canada Savings Bonds, corporate bonds, treasury bills, investment certificates, term deposits, annuities, mutual funds, earnings on life insurance policies and all foreign interest and foreign dividend incomes.

Investment income

Includes both interest income and dividend income.

Investors

Taxfilers who reported dividend income on line 120 of their personal tax return. They may or may not have also reported interest and other investment income on line 121. When such income is reported on line 121, this amount is added to the amount of dividend income received, and the sum becomes the investment income of the investor.

Level of geography

A code designating the type of geographic area to which the information in the table applies. See the section on Geography for further information.

Median

The middle number in a group of numbers. Where a median income, for example, is given as $26,000, it means that exactly half of the incomes reported are greater than or equal to $26,000, and that the other half is less than or equal to the median amount. With the exception of "Total Income", zero values are not included in the calculation of medians for individuals.

New room

For 2011 this amount is calculated as 18% of 2010 earned income (from definition above) to a maximum of 22,450 minus pension adjustment (PA) minus past service pension adjustment (PSPA). Since the focus of these data is for net new room for potential RRSP contributions, PA and/or PSPA details will be omitted.

Past service pension adjustment (PSPA)

Applies only to members of defined benefit RPPs. A PSPA occurs when the pension benefit is upgraded, or additional credits purchased, for service in past years. In the first case, it is called an exempt (from certification) PSPA; in the second case, a certifiable PSPA. Only service after 1989 is considered.

Pension adjustment (PA)

Calculated value of the pension accrued in the year in an RPP or a DPSP. The PA decreases the RRSP deduction limit. To calculate this limit, the PA from the previous year is used.

Registered disability savings plan income (RDSP)

It consists of an individual disability savings plan governed by RRSP investment rules. Private contributions that can be made by anyone are subject to a lifetime limit of $200,000. They will be matched in some degree by government contributions; the lifetime limit is $90,000. Contributions are not deductible and income earned in the plan will not be taxed while in the plan.

Registered pension plan ( RPP )

An employer-sponsored plan registered with the Canada Revenue Agency and most commonly also with one of the pension regulatory authorities. The purpose of such plans is to provide employees with a regular income at retirement. The two main types of RPPs are called defined benefit (where the benefit formula is specified) and defined contribution (where only the contribution formula is defined).

Registered retirement savings plan (RRSP)

An individual retirement savings plan that is registered by the Canada Revenue Agency. It permits limited contributions, and income earned in the RRSP is exempt from tax until payments are received from the plan.

Savers

Taxfilers who reported interest and investment income on line 121 of the personal income tax return, but no dividend income on line 120.

Taxfiler

Individual who filed a personal income tax return for the reference year.

Total income

The reported amounts of income by taxfilers from any of the following sources:

  • Labour force income;
    • Employment income;
      • Wages, salaries and commissions;
      • Other employment income as reported on line 104 of the tax form (tips, gratuities, royalties, etc.);
      • Net self-employment income;
      • Status Indian exempt self-employment income (beginning 2010);
      • Indian Employment Income (beginning in 1999);
    • Employment Insurance (EI) benefits;
  • Pension income;
    • Old Age Security/Net Federal Supplements (the latter including guaranteed income supplements and spouses' allowances since 1994);
    • Canada/Quebec Pension Plans;
    • Superannuation and other (private) pensions;
  • Family Allowance benefits (up to and including 1992);
  • Interest and other investment income;
  • Dividend income;
  • RRSP income (since 1999, for taxfilers 65+ only);
  • Net limited partnership income;
  • Alimony;
  • Net rental income;
  • Other income (e.g. incomes reported on line 130, such as fellowships, bursaries, grants, etc.);
  • Federal Sales Tax (FST) credit (for 1989-1990 inclusive);
  • Goods and Services Tax (GST) credit (beginning in 1990);
  • Harmonized Sales Tax (HST) credit (beginning in 1997);
  • Child tax credit (up to and including 1992);
  • Canada child tax benefit (starting with 1993);
  • Provincial refundable tax credits (beginning in 1994);
  • Other non-taxable income (beginning in 1993);
    • Workers' compensation payments;
    • Social assistance payments;
    • Guaranteed income supplements;
    • Spouses' allowances;
  • Universal child care benefit (both claimed by filer and designated to child) (beginning in 2006);
  • Registered disability savings plan income (beginning in 2008)
  • Working income tax benefit (starting with 2010)

Total room (in thousands of dollars)

The sum of "new room" and "unused room" as defined here.

Total room (number of persons)

The number of taxfilers who have either unused room from previous years, new room based on their earned income, or both. The number of persons with total room does not correspond to the sum of persons with new room and unused room, as an individual can be included in both categories.

Universal Child Care Benefit

Beginning in July 2006, the Universal Child Care Benefit (UCCB) is a taxable amount of $100 paid monthly for each child under 6 years of age. Included in CanadaChild Tax Benefits in the statistical tables.

Unused RRSP contribution room (unused room)

The amount of the RRSP deduction limit that is not claimed by the taxfiler, or the amount remaining after subtracting actual contributions claimed on the tax return from that year's contribution room. Unused room can be carried forward indefinitely. The first year of unused room is from 1991 (see table).

Statistical Tables - Footnotes and Historical Availability

RRSP Contributors

  1. Table 1 is available in its current format starting with the 1990 data, according to the postal geography. Census metropolitan areas (CMAs) are available starting with the 1993 data, census divisions (CDs) with the 1994 data and federal electoral districts (FEDs) with the 1997 data.
  2. Table 2 (age groups) and table 3 (sex) are available in their current formats starting with the 1994 data, for postal areas, CMAs, CDs and FEDs (since 1997). Some changes were made to the age groupings over the years.
  3. Table 4 (income groups) is available in its current format starting with the 2007 data, for postal areas, CMAs, CDs and FEDs. From 1997 to 2006, the income groups were cumulative.

RRSP Contribution Limits (Room)

  1. Both tables are available in their current format starting with the 1993 data.
  2. Data are available for all levels of the postal geography starting with the 1993 tax year.
  3. Data for census metropolitan areas (CMAs) are available starting with the 1993 tax year (1994 room), census divisions (CDs) with the 1994 tax year (1995 room) and federal electoral districts (FEDs) with the 1997 tax year (1998 room).
  4. The figures in Table 2 ($500, $2,400, $4,700, $7,800 and $13,000) represent the 25th, 50th, 75th, 90th and 97th percentiles of new room and are recalculated periodically.

Canadian Savers

  1. Table 1 is available in its current format starting with the 1990 data, according to the postal geography. Census metropolitan areas (CMAs) are available starting with the 1993 data, census divisions (CDs) with the 1995 data and federal electoral districts (FEDs) with the 1997 data.
  2. Table 2 (age groups) and table 3 (sex) are available in their current formats starting with the 1995 data, for postal areas, CMAs, CDs and FEDs (since 1997). Some changes were made to the age groupings over the years.
  3. Table 4 (income groups) is available in its current format starting with the 2007 data, for postal areas, CMAs, CDs and FEDs. From 1997 to 2006, the income groups were cumulative.

Canadian Investors

  1. Table 1 is available in its current format starting with the 1990 data, according to the postal geography. Census metropolitan areas (CMAs) are available starting with the 1993 data, census divisions (CDs) with the 1995 data and federal electoral districts (FEDs) with the 1997 data.
  2. The proportion of investment income from dividends is available starting with the 1996 data (Table 1).
  3. Table 2 (age groups) and table 3 (sex) are available in their current formats starting with the 1995 data, for postal areas, CMAs, CDs and FEDs (since 1997). Some changes were made to the age groupings over the years.
  4. Table 4 (income groups) is available in its current format starting with the 2007 data, for postal areas, CMAs, CDs and FEDs. From 1997 to 2006, the income groups were cumulative.

Canadian Investment Income

  1. Table 1 is available in its current format starting with the 1990 data, according to the postal geography. Census metropolitan areas (CMAs) are available starting with the 1993 data, census divisions (CDs) with the 1995 data and federal electoral districts (FEDs) with the 1997 data.
  2. Table 2 (age groups) and table 3 (sex) are available in their current formats starting with the 1995 data, for postal areas, CMAs, CDs and FEDs (since 1997). Some changes were made to the age groupings over the years.
  3. Table 4 (income groups) is available in its current format starting with the 2007 data, for postal areas, CMAs, CDs and FEDs. From 1997 to 2006, the income groups were cumulative.

Canadian Capital Gains

  1. The standard table on capital gains by income group is available in its current format starting with the 2007 data. From 1998 data up to 2006, the income groups were cumulative.
  2. All levels of geography are available since the 1998 data, including census divisions, census metropolitan areas, federal electoral districts and all levels of the postal geography.

Canadian Taxfilers

  1. Table 1 is available in its current format starting with the 1990 data, according to the postal geography. Census metropolitan areas (CMAs) are available starting with the 1993 data, census divisions (CDs) with the 1995 data and federal electoral districts (FEDs) with the 1997 data.
  2. Starting with the 2007 data, the column on the "% reporting in French" in table 1 has been suppressed.
  3. Table 2 (income groups) is available in its current format starting with the 2007 data, for postal areas, CMAs, CDs and FEDs. From 1997 to 2006, the income groups were cumulative.

Charitable Donations

  1. Table 1 (summary) is available starting with the 1990 data, according to the postal geography. Census metropolitan areas (CMAs) are available starting with the 1993 data, census divisions (CDs) with the 1995 data and federal electoral districts (FEDs) with the 1997 data.
  2. Changes were made to the age groups in table 1 in 1991 and in 1997.
  3. Table 2 (age groups) is available starting with the 1995 data, for the postal geography and for CMAs. CDs are available starting with the 1995 data and FEDs with the 1997 data.
  4. Changes were made to the age groups in table 2 in 1997.
  5. Table 3 (Income groups) is available in its current format starting with the 2007 data, for the postal geography, for CMAs, CDs and FEDs. From 1997 to 2006, the income groups were cumulative.

Geography

The data are available for the following geographic areas. See "Statistical Tables - Footnotes and Historical Availability" for further details. The mailing address at the time of filing is the basis for the geographic information in the tables.

Postal Geography

  • Canada
  • Provinces and territories
  • Cities
  • Urban Forward Sortation Areas (excludes rural routes and suburban services areas within cities)
  • Rural Postal Code

Some postal geography levels such as Postal Walks are no longer available for this data.

Census Geography

  • Economic Regions
  • Census Divisions
  • Census Metropolitan Areas
  • Census Agglomerations
  • Census Tracts
  • Federal Electoral Districts

User-defined areas:

Users may select a specific area of interest that is not a standard area for which data can be made available in standard format. To obtain data, provide us with a list of the Postal Codes for which data are required and we will provide the aggregated data. Of course, the area must satisfy our confidentiality requirements, or no data can be produced. See the "Special Geography" section for further information.

Geographic Levels – Postal Geography

The various data compiled from the taxfile are available for different levels of the postal geography, and for some levels of the Census geography. Coded geographic indicators appearing on the data tables are shown below with a brief description.

Level of Geography (L.O.G.) Postal Area Description
12 Canada This level of data is an aggregation of the provincial/territorial totals (code 11). The national total is identified by the region code Z99099.
11 Province or Territory Total

This level of data is an aggregation of the following geographies within a province:

City Totals (Code 08)
Rural Communities(Code 09)
Other Provincial Totals (Code 10)

These totals are identified by a provincial/territorial postal letter, then a "990" followed by the province/territory code, as follows:

Newfoundland and Labrador (A99010)
Nova Scotia (B99012)
Prince Edward Island (C99011)
New Brunswick (E99013)
Quebec (J99024)
Ontario (P99035)
Manitoba (R99046)
Saskatchewan (S99047)
Alberta (T99048)
British Columbia (V99059)
Northwest Territories (X99061)
Nunavut (X99062)
Yukon Territory (Y99060)

10 Other Provincial Total ("P" Pot)

This level of data is an aggregation of small communities in the province that had less than 100 taxfilers, where these communities are combined into a "pot". Before 1992, it was identified by the same codes as the provincial/territorial totals, and only the "Delivery Mode" codes 2 and 3 distinguished between the two. To avoid this problem, starting with the 1992 data, an "8" appears after the provincial/territorial letter instead of a "9". The "9" will be reserved for the provincial/territorial total, as explained in 11 above. These "pot" codes are as follows:

Newfoundland and Labrador (A89010)
Nova Scotia (B89012)
Prince Edward Island (C89011)
New Brunswick (E89013)
Quebec (J89024)
Ontario (P89035)
Manitoba (R89046)
Saskatchewan (S89047)
Alberta (T89048)
British Columbia (V89059)
Northwest Territories (X89061)
Nunavut (X89062)
Yukon Territory (Y89060)

09 Rural Communities
(Not in City )

For data obtained prior to reference year 2011, this level of geography was called "Rural Postal Codes (Not in a City)".

This level of geography pertains to rural communities that have one and only one rural Postal Code. Rural Postal Code can be identified by a "zero" in the second position of the Postal Code. For this level of geography, only the name of the community appears with the disseminated data. The actual rural Postal Code is not displayed with the disseminated data.

The 2011 databanks contain 3,982 areas coded as level of geography 09.

08 City Total

This level of data is an aggregation of the following geographies for unique place names within a province/territory:

Urban FSA (Residential) (Code 03)
Rural Route (Code 04)
Suburban Services (Code 05)
Rural Postal Code Areas (within city) (Code 06)
Other Urban Area (Code 07)

As of 2011, data for L.O.G. 04 and 05 are suppressed but included in the city totals.

They have the following format: e.g., Edmonton = T95479; Regina = S94876. The pattern is the postal letter of the city plus "9" in the second position (indicating a total), followed by a 4 digit numeric code for the community (often called "CityID").

In general, postal cities do not coincide with census subdivisions.

The 2011 databanks contain 1,640 areas coded as level of geography 08.

07 Other Urban Area (Non-residential within city - "E" Pot)

This aggregation of data (or "pot") covers non-residential addresses within an urban centre and all other data not otherwise displayed. Commercial addresses, post office boxes and general delivery are included, as are residential addresses with too few taxfilers to report separately. They can be recognized by codes that are similar to the city totals, with a distinguishing difference: an "8" will follow the city postal letter rather than the "9" of the city total (e.g., Edmonton = T85479; Regina = S84876).

The 2011 databanks contain 454 areas coded as level of geography 07.

06 Rural Postal Code Areas (Within City)

For data obtained prior to reference year 2011, this level of geography was called "Rural Postal Codes (Within a City)".

These data pertain to rural Postal Codes that belong to communities with more than one rural Postal Code . These occur in areas that were formerly serviced by rural delivery service and changed by Canada Post to urban delivery service or in communities served by more than one rural Postal Code. Rural Postal Codes can be identified by a "zero" in the second position of the Postal Code. Although data is disseminated individually for each rural Postal Codes associated with a community, only the community name appears with the disseminated data. The actual rural Postal Codes are not displayed with the disseminated data. Therefore, for this level of geography, community names will appear more than once.

The 2011 databanks contain 559 areas coded as level of geography 06.

05 Suburban Service

No longer available.

Sparsely populated fringe areas of urban centres may receive their postal service from an urban post office by delivery designated as "suburban service". Their region code retains all six characters of the Postal Code. Suburban Services are usually near or on the perimeters of urban areas, and mail is delivered by a contractor to group mail boxes, community mail boxes and/or external delivery sites (e.g., kiosks, miniparks).

04 Rural Route

No longer available.

Reasonably well-settled rural areas may receive their postal service from an urban post office by delivery designated as "rural route". Mail is delivered by a contractor to customers living along or near well-defined roads. Their region code retains all six characters of the Postal Code.

03 Urban FSA (Residential Area)

The urban Forward Sortation Area (FSA, identified by the first three characters of the Postal Code) includes all residential addresses covered by the first three characters of a Postal Code in a particular urban area (not including levels 04 and 05). Only residential FSAs are considered for these databanks.

An Urban FSA of this type can be identified by the FSA followed by three blanks. One FSA can be split in different parts if it is associated with more than one city.

The 2011 databanks contain 2,428 areas coded as level of geography 03.

02 Other Postal Walk

No longer available.

This level of data is an aggregation of urban residential Postal Codes unallocated to a letter carrier route and postal walks with less than 100 taxfilers. A postal walk record of this type can be identified by the FSA followed by three blanks, and the postal walk number "XXXX".

01 Postal Walk

No longer available.

This is the finest level of data and is an aggregation of urban residential Postal Codes allocated to a letter carrier route. A postal walk of this type can be identified by a region code which is the FSA followed by three blanks, and the postal walk number. An average FSA contains 11 walks.

 

Adding Postal Areas Without Duplication

Data files according to the postal geography will often contain subtotals and totals. Many data users need to add certain geographies in order to come up with a total for their particular area of interest. However, including subtotals during this process results in double-counting some populations, and this leads to an erroneous total. The following is a summary of which postal areas are aggregations in the standard postal geography.

Postal walks (Level of Geography, or LOG 1) and walk pots (LOG 2) add up to urban Forward Sortation Areas (FSAs, LOG 3).

Urban FSAs (LOG 3), rural routes (LOG 4), suburban services (LOG 5), rural Postal Code areas within a city (LOG 6) and other urban areas (LOG 7) add up to city totals (LOG 8).

City totals (LOG 8), rural communities not in a city (LOG 9) and other areas in a province (LOG 10) add up to provincial/territorial totals (LOG 11).

Provincial/territorial totals (LOG 11) add up to the Canada total (LOG 12).

Thus, using the Level of geography codes:
1 + 2 = 3
3 + 4 + 5 + 6 + 7 = 8
8 + 9 + 10 = 11

Geography for small area and administrative data

Description: Geography for small area and administrative data

City identification number (CityID)

As of 2007, CityID has been modified.

Previous to 2007:

  1. CityID was a 4 digits number
  2. Each municipality had a unique number between 1 and 9999
  3. Almost every number was allocated to a municipality. Few numbers remained available for future new municipalities.

Starting with 2007data:
To create more possibilities without changing the CityID length in our systems:

  1. CityID number is now combined with 1st letter of Postal Code
  2. Each 1st letter of Postal Code has a possibility of numbers, ranged from 1 to 9999 (Table 2)
  3. Old numbers have been kept for existing municipality and 1st letters of Postal Code have been added to them (Table 1)
  4. New municipalities have been assigned a new CityID number in new format (Table 1)
Table 1
Postal Code Municipality name 2006 and Prior 2007 and Follow
K1A 1K6 Ottawa 2434 K2434
G3C 0A1 Stoneham-et-Tewkesbury n/a G2

 

Table 2
Province Letter file Range of number
Newfoundland & Labrador A 1 – 9999
Prince Edward Island C 1 – 9999
Nova Scotia B 1 – 9999
New Brunswick E 1 – 9999
Quebec G 1 – 9999
Quebec H 1 – 9999
Quebec J 1 – 9999
Ontario K 1 – 9999
Ontario L 1 – 9999
Ontario M 1 – 9999
Ontario N 1 – 9999
Ontario P 1 – 9999
Manitoba R 1 – 9999
Saskatchewan S 1 – 9999
Alberta T 1 – 9999
British Columbia V 1 – 9999
Yukon Y 1 – 9999
Northwest Territories X 1 – 9999
Nunavut X 1 – 9999

Therefore, it is now essential to identify a municipality by adding the Postal Code 1st letter to the number in order to get the proper municipality in the proper province (Table 3):

Table 3
Letter Number Municipality name Province
A 2 Avondale NL
B 2 Bible Hill NS
T 2 Rocky View AB
G 2 Stoneham-et-Tewkesbury QC

Geographic Levels – Census Geography

Data are also available for the following levels of the Census geography; the following table shows the coded designators for these geographies, as well as a brief description of each.

Level of Geography (L.O.G.) Name Description
61 Census Tract

Census tracts (CTs) are small geographic units representing urban or rural neighbourhood-like communities in census metropolitan areas (see definition below) or census agglomerations with an urban core population of 50,000 or more at time of 1996 Census. CTs are delineated by a committee of local specialists (such as planners, health and social workers and educators) in conjunction with Statistics Canada.

The 2011 databanks contain 4,992 areas coded as level of geography 61, based on 2006 Census.

51 Economic Region

An economic region is a grouping of complete census divisions (see definition below) with one exception in Ontario. Economic regions (ERs) are used to analyse regional economic activity. Within the province of Quebec, ERs are designated by law. In all other provinces, they are created by agreement between Statistics Canada and the provinces concerned. Prince Edward Island and the territories each consist of one economic region.

The 2011 databanks contain 76 areas coded as level of geography 51, based on 2006 Census.

42 Census Agglomeration

The general concept of a census agglomeration (CA) is one of a very large urban area, together with adjacent urban and rural areas that have a high degree of economic and social integration with that urban area. CAs have an urban core population of at least 10,000, based on the previous census.

The 2011 databanks contain 117 areas coded as level of geography 42, based on 2006 Census.

41 Census Metropolitan Area

The general concept of a census metropolitan area (CMA) is one of a very large urban area, together with adjacent urban and rural areas that have a high degree of economic and social integration with that urban area. CMAs have an urban core population of at least 100,000, based on the previous census.

There are 35 CMAs in the 2011 databanks (2006 Census):

001, St. John's, Newfoundland
205, Halifax, Nova Scotia
305, Moncton, New Brunswick
310, Saint John, New Brunswick
408, Saguenay, Québec
421, Québec, Québec
433, Sherbrooke, Québec
442, Trois-Rivières, Québec
462, Montréal, Québec
505, Ottawa-Gatineau (Québec part)
505, Ottawa-Gatineau (Ontario part)
505, Ottawa-Gatineau (Combined)
521, Kingston, Ontario
529, Peterborough, Ontario
532, Oshawa, Ontario
535, Toronto, Ontario
537, Hamilton, Ontario
539, St-Catharines-Niagara, Ontario
541, Kitchener, Ontario
543, Brantford, Ontario
550, Guelph, Ontario
555, London, Ontario
559, Windsor, Ontario
568, Barrie, Ontario
580, Greater Sudbury, Ontario
595, Thunder Bay, Ontario
602, Winnipeg, Manitoba
705, Regina, Saskatchewan
725, Saskatoon, Saskatchewan
825, Calgary, Alberta
835, Edmonton, Alberta
915, Kelowna, British Columbia
932, Abbotsford-Mission, British Columbia
933, Vancouver, British Columbia
935, Victoria, British Columbia

31 Federal Electoral District

A federal electoral district (FED) refers to any place or territorial area represented by a member of Parliament elected to the House of Commons. There are 308 FEDs in Canada according to the 2003 Representation Order. The Representation Order is prepared by the Chief Electoral Officer describing, naming and specifying the population of each electoral district established by the Electoral Boundaries Commission and sent to the Governor in Council.

The 2011 databanks contain 308 areas coded as level of geography 31, based on the 2006 Census.

21 Census Division

A census division (CD) is a group of neighbouring municipalities joined together for the purposes of regional planning and managing common services (such as police or ambulance services). A CD might correspond to a county, a regional municipality or a regional district.

CDs are established under laws in effect in certain provinces and territories of Canada. In other provinces and territories where laws do not provide for such areas (Newfoundland, Manitoba, Saskatchewan and Alberta), Statistics Canada defines equivalent areas for statistical reporting purposes in cooperation with these provinces and territories.

The 2011 databanks contain 288 areas coded as level of geography 21, based on the 2006 Census.

Starting in 2008, Census divisions are identified in the tables by an eight digits code:
2 first digits = Province
2 next digits = Economic Region
2 last digits = Census Division

Geographic Levels – Special Geography

Clients may select geographical areas of their own definition; areas that are not part of the standard areas listed here (for example, bank service areas, retail store catchment areas). For this, clients must submit a list of the Postal Codes that make up their special area, and we will aggregate the micro data to correspond to that area of interest. Information ordered for special, or "user-defined" areas will be coded according to the following:

Level of Geography Name Description
93 Total for all user-defined areas This level represents the sum total of all user-defined areas, and is the total of levels 91 and 92 described below.
92 Other user-defined areas This level of geography represents all user-defined areas that were too small, in terms of population; to have information compiled on those areas individually (i.e. fewer than 100 taxfilers). Such areas are grouped into this "other" category.
91 Special user-defined area Any area showing a code "91" is an area defined by a specific user according to that user's needs (for example, school catchment areas, health districts, etc.)

Conversion files

When a client is interested in purchasing data for areas that are considered non-standard geography by Income Statistics Division, a conversion file is usually necessary. A combination of Postal Codes making up one or more special area(s) is commonly referred to as a conversion file – an electronic file used by our staff to aggregate the different Postal Codes that make up the user-defined area. Simply provide us with the Postal Codes related to the area and we will compile the data (subject to our confidentiality restrictions).

This would apply only to an area that is not a standard area. It could include any one or a combination of areas whose boundaries are a combination of standard areas or a combination of Postal Codes. User-defined areas may be branch service or school catchment areas, neighbourhoods or almost any other region.

Each Postal Code on a conversion file is linked to a corresponding area code. The Postal Code is used as the basis for the tabulation of economic and demographic data for each area.

We Invite Your Comments

We are always working on ways to improve our products. The comments we receive concerning quality and presentation are essential to meet this objective. If you have any suggestions in this regard, we encourage you, the user, to provide us with your comments.

Data in many forms

Statistics Canada disseminates data in a variety of forms. In addition to publications, both standard and special tabulations are offered. Direct online access to aggregated information is possible through CANSIM, Statistics Canada's machine-readable database and retrieval system.

How to obtain more information

Inquiries about these data and related statistics or services should be directed to:

Client Services
Income Statistics Division
Statistics Canada
5th Floor, Jean Talon Building
Ottawa, Ontario K1A 0T6

Telephone: (613) 951-7355
Toll-Free (888) 267-7355
Fax: (613) 951-3012
Toll-Free (888) 267-7355
income@statcan.gc.ca

National enquiries line 1-800-263-1136
National telecommunications device for the hearing impaired 1-800-363-7629
Order-only line (Canada and the United States) 1-800-267-6677
National Toll-free Fax line 1-877-287-4369

You can also visit us on the web: http://www.statcan.gc.ca.

Standards of service to the public

Statistics Canada is committed to serving its clients in a prompt, reliable and courteous manner and in the official language of their choice.  To this end, the agency has developed standards of service which its employees observe in serving its clients.  To obtain a copy of these service standards, please contact your nearest Statistics Canada Regional Reference Centre.

Copyright

Published by authority of the Minister responsible for Statistics Canada.

© Minister of Industry, 2012

All rights reserved. Use of this publication is governed by the Statistics Canada Open Licence Agreement.

© This data includes information copied with permission from Canada Post Corporation

List ofData Products Available

The Income Statistics Division of Statistics Canada tabulates statistical data derived from administrative records - most notably, the taxfile.  The resulting demographic and socio-economic databanks available are listed in the table below, along with their identifying product number and the usual release dates.

Product name Product number Release date
RRSP Contributors 17C0006 Fall
RRSP Contribution Limits (Room) 17C0011 Fall
Canadian Savers 17C0009 Fall
Canadian Investors 17C0007 Fall
Canadian Investment Income 17C0008 Fall
Canadian Taxfilers 17C0010 Fall
Canadian Capital Gains 17C0012 Fall
Charitable Donors 13C0014 Fall
Neighbourhood Income and Demographics 13C0015 Spring
Economic Dependency Profiles 13C0017 Spring
Labour Income Profiles 71C0018 Spring
Families 13C0016 Spring
Seniors 89C0022 Spring
Migration Estimates 91C0025 Fall
 
 

Survey of Staffing - Candidates, Cycle 4

Questions and Answers

  1. What is the Survey of Staffing - Candidates?
    The Survey of Staffing - Candidates is an employee survey that provides the opportunity for employees to give feedback on their experiences with staffing processes within the federal public service.
  2. What are the main objectives of the survey?
    The information gathered by the survey will contribute to a government-wide perspective on the staffing process and will help to identify areas where improvement is needed to the staffing system. It will also be useful in providing information to identify if any changes to the Public Service Employment Act (PSEA), and/or related policies are needed when the legislation is revisited in 2011.
  3. Who will conduct the survey?
    Statistics Canada will contact employees in collaboration with the Public Service Commission. Because the survey is conducted under the authority of the Statistics Act, the confidentiality provisions apply to all information provided by survey respondents.
  4. What kind of questions will I be asked?
    The survey collects data on the appointment process, staffing strategies, the area of competition and the experiences of public servants who have participated in a staffing process. The survey will also collect information on political activities.
  5. Why are you asking me questions about political activities - this is a staffing survey?
    Part of the Public Service Employment Act (PSEA) mandates the Public Service Commission to oversee the political impartiality of the Public Service (see questionnaire cover letter).

    You may not have participated in a staffing process but we are taking this opportunity to ask you a few questions concerning political activities. They provide an indication of the participation in political activities by public servants, the information sources that are typically consulted regarding political activities, and the knowledge of their rights and responsibilities.

    The major objective of the survey is to collect data on staffing experiences. Due to the questionnaire flow, if you did not participate in a staffing process that concluded from July 1st, 2010 to June 30th, 2011, you will be skipped to the portion of the questionnaire where the questions on your general experiences in staffing processes are found.

    We want to reinforce that all information provided to Statistics Canada through this survey is protected by law under the Statistics Act.

    For more information about the mandate of the Public Service Commission regarding political activities, please visit the Internet site at Political Activities.
  6. Who is surveyed?
    The survey targets public service employees working in federal departments and agencies that fall under the Public Service Employment Act (PSEA) with at least 350 employees. A similar survey is being sent out in November by the Public Service Commission to a sample of managers involved in staffing processes during the same time period to explore their views and practices with staffing.
  7. How was I selected to participate in the survey?
    For departments or agencies with 3,000 and more employees, you were randomly selected from a list of employees provided by your organizations. The employees working for a department or agency with between 350 and 3000 employees will all receive a survey questionnaire.
  8. When will the survey take place?
    The collection of the survey will take place from October 24th- November 18th. Completed questionnaires must be sent to Statistics Canada by November 18th, 2011.
  9. Am I required to participate in the survey?
    Your participation in this survey is voluntary. However, the more employees that participate, the more accurate and representative the results will be across the public service.
  10. Is the information I provide confidential?
    Yes, Statistics Canada guarantees the confidentiality of the survey under the Statistics Act. To protect confidentiality, the following precautions will be followed:
    • Names of respondents will not be included on the analysis file that will be created and made available to the Public Service Commission.
    • Data will be produced in tabular and graphical form at aggregate levels only (e.g., department or program levels).
    • All outputs will be screened to ensure that they do not reveal the identity of individual respondents.
  11. The survey asks a question about sharing my information with the Public Service Commission. What does this mean?
    There will be an agreement in place between Statistics Canada and the Public Service Commission that will limit the use of your information for statistical purposes only and will prohibit the disclosure of survey information that could identify you. The protected information will be used for statistical purposes only and analyses at the departmental or agency and public-service-wide levels only. Your information will not be shared if you do not give permission to do so.
  12. I am on an assignment in another department. Should I go back to my department to fill out the survey?
    For the purpose of the survey, you are included in the department in which you are presently working.
  13. How will the confidentiality of my answers be protected for the electronic questionnaire?
    Your responses are anonymous, provided directly to Statistics Canada, and they are protected under the Statistics Act.

    The Statistics Canada Electronic Collection Portal at Privacy notice provides detailed information about the security features in place to maintain confidentiality, as required by the Statistics Act.
  14. When will the survey results be available?
    The public service-wide results of Cycle 3 (2009-2010) survey will be reported in the 2010-2011 Annual Report of the Public Service Commission and the departmental data will be released in the fall 2011. More details and updates of the survey can be found by visiting Annual Reports.
  15. What if an employee does not want to complete the Internet-based survey and requests a paper questionnaire?
    Due to the very low request rate from the previous cycles of this survey, there will not be a paper version of the questionnaire available to complete.
  16. What if a respondent encounters technical difficulties with the Internet-based survey?
    If a respondent has any technical questions or requires assistance, they should access the on-line help pages or contact Statistics Canada at the following email address sos@statcan.gc.ca or call the assistance line at 1-877-949-9492.
  17. Where can I find more information about the survey?
    You could find more information about the survey at webpage Survey of Staffing - Candidates

Canadian Health Measures Survey (CHMS) Cycle 01 Derived Variable (DV) Specifications

Table of contents

mCAFT (9 DVs)

  1. AFCDELG - Eligibility for the modified Canadian Aerobic Fitness Test (mCAFT)
  2. AFTD01 - Starting stage of the modified Canadian Aerobic Fitness Test (mCAFT)
  3. AFTD02 - Ceiling heart rate for the modified Canadian Aerobic Fitness Test (mCAFT)
  4. AFTD21 - Final Stepping Stage of the modified Canadian Aerobic Fitness Test (mCAFT)
  5. AFTD22 - Immediate Post-exercise Heart Rate
  6. AFTD71 - Oxygen cost of the modified Canadian Aerobic Fitness Test (mCAFT)
  7. AFTD72 - Aerobic fitness score based on the modified Canadian Aerobic Fitness Test (mCAFT)
  8. AFTD73 - Aerobic fitness norms for respondents aged 15 - 69
  9. AFTD74 - Aerobic fitness norms for respondents aged less than 15

Alcohol use (3 DVs)

  1. ALCDDLY - Average Daily Alcohol Consumption
  2. ALCDTYP - Type of Drinker
  3. ALCDWKY - Weekly Consumption

Anthropometric (23 DVs)

  1. ANCDELG - Eligibility for the Anthropometric component
  2. HWMD11IN - Standing height (inches) – measured
  3. HWMD12IN - Sitting height (inches) - measured
  4. HWMD13LB - Weight (pounds) – measured
  5. HWMD14IN - Waist circumference (inches) – measured
  6. HWMD15IN - Hip circumference (inches) – measured
  7. HWMDBMI - Body Mass Index (BMI) – measured
  8. HWMDBMIA - BMI classification for adults aged 18 and over (measured) - international standard
  9. HWMDBMIK - BMI Classification for Children Aged 6 to 17 (measured) - CDC BMI-for-age
  10. HWMDCOL - BMI Classification for Children Aged 6 to 17 (Measured) - Cole Classification System
  11. HWMDHTM – Standing height (metres) – measured
  12. HWMDLLN - Leg Length
  13. HWMDMAT - Maturity Offset
  14. HWMDWSTA - Waist Circumference Norms
  15. HWMDWTH - Waist to hip ratio
  16. SFMDBCA - Body Composition Norms
  17. SFMDBSA - Biceps Skinfold Average
  18. SFMDICA - Iliac Crest Skinfold Average
  19. SFMDMCA - Medial Calf Skinfolds Average
  20. SFMDS5 - Sum of 5 Skinfold Measurements
  21. SFMDS5A - Sum of 5 Skinfolds Measurements - Norms (ages 15-69)
  22. SFMDSSA - Subscapular Skinfolds Average
  23. SFMDTSA - Triceps Skinfolds Average

Blood Pressure (20 DVs)

  1. BPMD160 - Type of problem - first set
  2. BPMD161 - Average systolic blood pressure - first set
  3. BPMD162 - Average diastolic blood pressure - first set
  4. BPMD163 - Average resting heart rate - first set
  5. BPMD260 - Type of problem - second set
  6. BPMD261 - Average systolic blood pressure - second set
  7. BPMD262 - Average diastolic blood pressure - second set
  8. BPMD263 - Average resting heart rate - second set
  9. BPMD360 - Type of problem - third set
  10. BPMD361 - Average systolic blood pressure - third set
  11. BPMD362 - Average diastolic blood pressure - third set
  12. BPMD363 - Average resting heart rate - third set
  13. BPMDBPA - Blood pressure norms for respondents 18 or older (Prevalence)
  14. BPMDBPK - Blood pressure norms for respondents less than 18 (Prevalence)
  15. BPMDPBPD - Final average diastolic blood pressure (Prevalence)
  16. BPMDPBPS - Final average systolic blood pressure (Prevalence)
  17. BPMDPHR - Final average resting heart rate (Prevalence)
  18. BPMDSBPD - Final average diastolic blood pressure (Screening)
  19. BPMDSBPS - Final average systolic blood pressure (Screening)
  20. BPMDSHR - Final average resting heart rate (Screening)

Breastfeeding information (1 DV)

  1. BRIFEB6 - Exclusively breastfed for at least 3 months

Chronic conditions (1 DV)

  1. CCCF1 - Has a Chronic Condition

Children’s physical activity (2 DVs)

  1. CPADSAC - Total number of hours per day spent in sedentary activities
  2. CPADTOT - Total number of hours per week participated in physical activities

Dietary fat consumption (2 DVs)

  1. DFCD11Y - Eats regular-fat salad dressing - times per year
  2. DFCD12Y - Eats regular-fat potato chips, tortilla chips or corn chips - times per year

Demographic and household variables (9 DVs)

  1. DHHD611 - Number of Persons in Household 6 to 11 Years of Age
  2. DHHDDWE - Dwelling Type
  3. DHHDECF - Economic Family Status (Household Type)
  4. DHHDHSZ - Household Size
  5. DHHDL12 - Number of Persons in Household Less Than 12 Years of Age
  6. DHHDLE5 - Number of Persons in Household Less Than 6 Years of Age
  7. DHHDLVG - Living/ Family Arrangement of Selected Respondent
  8. DHHDOKD - Number of Persons in Household 16 or 17 Years of Age
  9. DHHDYKD - Number of Persons in Household Less Than 16 Years of Age

Education (4 DVs)

  1. EDUDH04 - Highest Level of Education - Household, 4 Levels
  2. EDUDH10 - Highest Level of Education - Household, 10 Levels
  3. EDUDR04 - Highest Level of Education - Household, 4 Levels
  4. EDUDR10 - Highest Level of Education - Household, 10 Levels

General health (2 DVs)

  1. GENDHDI - Self-Rated Health (Formerly Health Description Index)
  2. GENDMHI - Self-Rated Mental Health

Grains, fruits and vegetables consumption (13 DVs)

  1. GFVD11Y - Eats hot or cold cereal - times per year
  2. GFVD12Y - Eats brown bread, including bagels, rolls, pita bread or tortillas - times per year
  3. GFVD13Y - Eats white bread, including bagels, rolls, pita bread or tortillas - times per year
  4. GFVD14Y - Eats any kind of pasta - times per year
  5. GFVD15Y - Eats any kind of rice - times per year
  6. GFVD16Y - Eats instant, seasoned or wild rice - times per year
  7. GFVD17Y - Eats fruit - times per year
  8. GFVD18Y - Eats tomatoes or tomato sauce - times per year
  9. GFVD19Y - Eats lettuce or green leafy salad - times per year
  10. GFVD20Y - Eats spinach, mustard greens or collards - times per year
  11. GFVD21Y - Eats french fries, home fries or hash brown potatoes - times per year
  12. GFVD22Y - Eats other potatoes - times per year
  13. GFVD23Y - Eats all other types of vegetables - times per year

Grooming product use (7 DVs)

  1. GPUD12Y - Uses fragrance - times per year
  2. GPUD13Y - Uses eye make-up - times per year
  3. GPUD14Y - Uses lipstick - times per year
  4. GPUD15Y - Uses hair dye - times per year
  5. GPUD16Y - Uses hair style products - times per year
  6. GPUD17Y - Uses manicure preparations - times per year
  7. GPUD18Y - Uses scented body products - times per year

Grip Strength (4 DVs)

  1. GSCDELG - Eligibility - Grip Strength component
  2. GSMD51 - Total hand grip strength
  3. GSMD52 - Grip strength norms for respondents 15 – 69
  4. GSMD53 - Grip strength norms for respondents less than 15

Hobbies (10 DVs)

  1. HOBD12Y - Arts - times per year
  2. HOBD13Y - Pottery - times per year
  3. HOBD14Y - Model making - times per year
  4. HOBD15Y - Making fishing sinkers - times per year
  5. HOBD16Y - Welding - times per year
  6. HOBD17Y - Auto repairs - times per year
  7. HOBD18Y - Electronics - times per year
  8. HOBD19Y - Plumbing - times per year
  9. HOBD20Y - Refinishing furniture - times per year
  10. HOBD21Y - Woodworking - times per year

Health utility index (HUI) (10 DVs)

  1. HUIDCOG - Cognition (Function Code)
  2. HUIDDEX - Dexterity Trouble (Function Code)
  3. HUIDEMO - Emotional Problems (Function Code)
  4. HUIDHER - Hearing Problems (Function Code)
  5. HUIDHSC - Health Utility Index - categorical variable
  6. HUIDHSI - Health Utility Index
  7. HUIDMOB - Mobility Trouble (Function Code)
  8. HUIDPAD - Activities Prevented / Pain (Function Code)
  9. HUIDSPE - Speech Trouble (Function Code)
  10. HUIDVIS - Vision Trouble (Function Code)

Height and weight (9 DVs)

  1. HWTDBMI - Body Mass Index (self-reported)
  2. HWTDBMIA - BMI Classification for Adults Aged 18 and Over (self-reported) - International Standard
  3. HWTDBMIK - BMI Classification for Children Less Than 18 Years of Age (self-reported) - CDC BMI-for-age
  4. HWTDCM - Height (centimetres) - self-reported
  5. HWTDCOL - BMI classification for children aged 6 to 17 (self-reported) - Cole classification system
  6. HWTDHTM - Height (metres) - self-reported
  7. HWTDIN - Height (inches) - self-reported
  8. HWTDKG - Weight (kilograms) - self-reported
  9. HWTDLB - Weight (pounds) - self-reported

Income (5 DVs)

  1. INCDDIA2 - Total household income - 2 categories
  2. INCDDIA4 - Total household income - 4 categories
  3. INCDDIA5 - Total household income - 5 categories
  4. INCDHH - Total Household Income - All Sources
  5. INCDPER - Personal Income - All Sources

Labour force (8 DVs)

  1. LBFDHPW - Total usual hours worked per week
  2. LBFDJST - Job status over past year
  3. LBFDMJS - Multiple job status
  4. LBFDPFT - Full-time/ part-time working status (for total usual hours)
  5. LBFDRNW - Main reason for not working last week
  6. LBFDSTU - Student working status
  7. LBFDWSL - Working status last week
  8. LBFDWSS - Working status last week

Milk and dairy product consumption (4 DVs)

  1. MDCD11Y - Drinks milk - times per year
  2. MDCD13Y - Eats cottage cheese - times per year
  3. MDCD14Y - Eats yogurt - times per year
  4. MDCD15Y - Eats ice cream or frozen yogurt - times per year

Meat and fish consumption (11 DVs)

  1. MFCD11Y - Eats red meat - times per year
  2. MFCD12Y - Eats liver - times per year
  3. MFCD13Y - Eats other organ meats - times per year
  4. MFCD14Y - Eats beef or pork hot dogs - times per year
  5. MFCD15Y - Eats sausage or bacon- times per year
  6. MFCD16Y - Eats salt water fish - times per year
  7. MFCD17Y - Eats fresh water fish - times per year
  8. MFCD18Y - Eats shellfish - times per year
  9. MFCD19Y - Eats eggs and egg dishes - times per year
  10. MFCD20Y - Eats cooked dried beans - times per year
  11. MFCD21Y - Eats peanuts, walnuts, seeds or other nuts - times per year

Oral Health (77 DVs)

  1. OHCDELG - Eligibility - Oral Health component
  2. OHEDAC01 - Total number of adult crowns - code 1
  3. OHEDAC02 - Total number of adult crowns - code 2
  4. OHEDAC03 - Total number of adult crowns - code 3
  5. OHEDAC04 - Total number of adult crowns - code 4
  6. OHEDAC05 - Total number of adult crowns - code 5
  7. OHEDAC06 - Total number of adult crowns - code 6
  8. OHEDAC07 - Total number of adult crowns - code 7
  9. OHEDAC08 - Total number of adult crowns - code 8
  10. OHEDAC09 - Total number of adult crowns - code 9
  11. OHEDAC10 - Total number of adult crowns - code 10
  12. OHEDAC12 - Total number of adult crowns - code 12
  13. OHEDAC13 - Total number of adult crowns - code 13
  14. OHEDAC14 - Total number of adult crowns - code 14
  15. OHEDAC15 - Total number of adult crowns - code 15
  16. OHEDAC16 - Total number of adult crowns - code 16
  17. OHEDAC17 - Total number of adult crowns - code 17
  18. OHEDAC18 - Total number of adult crowns - code 18
  19. OHEDAC19 - Total number of adult crowns - code 19
  20. OHEDAC20 - Total number of adult crowns - code 20
  21. OHEDAC21 - Total number of adult crowns - code 21
  22. OHEDAR01 - Total number of adult roots - code 1
  23. OHEDAR03 - Total number of adult roots - code 3
  24. OHEDAR04 - Total number of adult roots - code 4
  25. OHEDAR05 - Total number of adult roots - code 5
  26. OHEDAR06 - Total number of adult roots - code 6
  27. OHEDAR07 - Total number of adult roots - code 7
  28. OHEDAR11 - Total number of adult roots - code 11
  29. OHEDAR12 - Total number of adult roots - code 12
  30. OHEDAR13 - Total number of adult roots - code 13
  31. OHEDAR14 - Total number of adult roots - code 14
  32. OHEDAR15 - Total number of adult roots - code 15
  33. OHEDAR16 - Total number of adult roots - code 16
  34. OHEDAR17 - Total number of adult roots - code 17
  35. OHEDAR19 - Total number of adult roots - code 19
  36. OHEDAR20 - Total number of adult roots - code 20
  37. OHEDAR21 - Total number of adult roots - code 21
  38. OHEDCS01 - Calculus score recode - teeth 17 and 16
  39. OHEDCS02 - Calculus score recode - tooth 11
  40. OHEDCS03 - Calculus score recode - teeth 26 and 27
  41. OHEDCS04 - Calculus score recode - teeth 37 and 36
  42. OHEDCS05 - Calculus score recode - tooth 31
  43. OHEDCS06 - Calculus score recode - teeth 46 and 47
  44. OHEDDS01 - Debris score recode - teeth 17 and 16
  45. OHEDDS02 - Debris score recode - tooth 11
  46. OHEDDS03 - Debris score recode - teeth 26 and 27
  47. OHEDDS04 - Debris score recode - teeth 37 and 36
  48. OHEDDS05 - Debris score recode - tooth 31
  49. OHEDDS06 - Debris score recode - teeth 46 and 47
  50. OHEDDT01 - Total number of deciduous teeth - code 1
  51. OHEDDT02 - Total number of deciduous teeth - code 2
  52. OHEDDT03 - Total number of deciduous teeth - code 3
  53. OHEDDT04 - Total number of deciduous teeth - code 4
  54. OHEDDT05 - Total number of deciduous teeth - code 5
  55. OHEDDT06 - Total number of deciduous teeth - code 6
  56. OHEDDT07 - Total number of deciduous teeth - code 7
  57. OHEDDT08 - Total number of deciduous teeth - code 8
  58. OHEDDT09 - Total number of deciduous teeth - code 9
  59. OHEDDT10 - Total number of deciduous teeth - code 10
  60. OHEDDT12 - Total number of deciduous teeth - code 12
  61. OHEDDT13 - Total number of deciduous teeth - code 13
  62. OHEDDT14 - Total number of deciduous teeth - code 14
  63. OHEDDT15 - Total number of deciduous teeth - code 15
  64. OHEDDT16 - Total number of deciduous teeth - code 16
  65. OHEDDT17 - Total number of deciduous teeth - code 17
  66. OHEDDT20 - Total number of deciduous teeth - code 20
  67. OHEDDT21 - Total number of deciduous teeth - code 21
  68. OHEDFLUO - Fluorosis score recode
  69. OHEDGS12 - Gingivitis score recode - tooth 12
  70. OHEDGS16 - Gingivitis score recode - tooth 16
  71. OHEDGS24 - Gingivitis score recode - tooth 24
  72. OHEDGS32 - Gingivitis score recode - tooth 32
  73. OHEDGS36 - Gingivitis score recode - tooth 36
  74. OHEDGS44 - Gingivitis score recode - tooth 44
  75. OHRD25 - Test exclusion – probing
  76. OHMD31Y - Brushing teeth - number times per year
  77. OHMD32Y - Flossing teeth - number times per year

Physical activities (6 DVs)

  1. PACDEE - Daily Energy Expenditure
  2. PACDFM - Average Monthly Frequency of Physical Activity Lasting Over 15 Minutes
  3. PACDFR - Frequency of All Physical Activity Lasting Over 15 Minutes
  4. PACDPAI - Physical Activity Index
  5. PACFD - Participant In Daily Physical Activity Lasting Over 15 Minutes
  6. PACFLEI - Participant In Leisure Physical Activity

Partial Curl-Ups (2 DVs)

  1. PCCDELG - Eligibility - Partial Curl-up component
  2. PCMD11 - Partial curl-up norms for respondents 15 - 69

Phlebotomy (2 DVs)

  1. BDCD13 - Blood donation status
  2. PHBDELG - Eligibility - Phlebotomy component

Report of Measurements (2 DVs)

  1. RMCDBCK - Back fitness norms for respondents 15 – 69
  2. RMCDMSK - Musculo-skeletal fitness norms for respondents 15 – 69

Sedentary activities (1 DV)

  1. SACDTOT - Total Number of Hours Per Week Spent In Sedentary Activities

Screening (1 DV)

  1. ATGD12 - Fasting status

Socio-demographic characteristics (8 DVs)

  1. SDCDAIM - Age at time of immigration
  2. SDCDCGT - Culture / Race Flag
  3. SDCDFL1 - First official language learned and still understood
  4. SDCDLNG - Language(s) in which respondent can converse
  5. SDCDRES - Length of time in Canada since immigration
  6. SDCFABT - Aboriginal flag
  7. SDCFIMM - Immigration flag
  8. SDCGCB - Country of birth – grouped

Strengths and difficulties (12 DVs)

  1. SDQDCON - Conduct Problems
  2. SDQDEMO - Emotional Symptoms
  3. SDQDHYP - Hyperactivity/Inattention
  4. SDQDPRO - Prosocial Behaviour
  5. SDQDPRP - Peer Relationship Problems
  6. SDQDTOT - Total Difficulties Score
  7. SDQGCON - Conduct Problems Score – Grouped
  8. SDQGEMO - Emotional Symptoms Score – Grouped
  9. SDQGHYP - Hyperactivity Score – Grouped
  10. SDQGPRO - Prosocial Behaviour Score – Grouped
  11. SDQGPRP - Peer Relationship Problems Score – Grouped
  12. SDQGTOT - Total Difficulties Score – Grouped

Smoking (3 DVs)

  1. SMKDSTP - Number of Years Since Stopping Smoking Completely
  2. SMKDSTY - Type of Smoker
  3. SMKDYFS - Number of Years Smoked Daily (Former Daily Smokers Only)

Spirometry (4 DVs)

  1. SPCDELG - Eligibility - Spirometry component
  2. SPMDB1FP - Percent predicted FEV1/FVC
  3. SPMDB1P - Percent predicted Forced Expiratory Volume (FEV1)
  4. SPMDBFVP - Percent predicted Forced Vital Capacity (FVC)

Sit and Reach (4 DVs)

  1. SRCDELG - Eligibility - Sit and Reach component
  2. SRMD11 - Sit and reach measure
  3. SRMD12 - Sit and reach norms - respondents 15 – 69
  4. SRMD13 - Sit and reach norms - respondents less than 15

Urine Collection (1 DV)

  1. URCDELG - Eligibility - Urine Collection component

Water and soft drink consumption (7 DVs)

  1. WSDD11Y - Drinks regular soft drinks - times per year
  2. WSDD12Y - Drinks diet soft drinks - times per year
  3. WSDD13Y - Drinks sport drinks - times per year
  4. WSDD14Y - Drinks fruit juices - times per year
  5. WSDD15Y - Drinks fruit flavoured drinks - times per year
  6. WSDD16Y - Drinks vegetable juices - times per year
  7. WSDD21Y - Drinks water - times per year

Weight change (10 DVs)

  1. WTCD11KG - Weight one year ago (kilograms) - self-reported
  2. WTCD11LB - Weight one year ago (pounds) - self-reported
  3. WTCD21KG - Weight ten years ago (kilograms) - self-reported
  4. WTCD21LB - Weight ten years ago (pounds) - self-reported
  5. WTCD22KG - Weight at age 25 (kilograms) - self-reported
  6. WTCD22LB - Weight at age 25 (pounds) - self-reported
  7. WTCD23KG - Most ever weighed (kilograms) - self-reported
  8. WTCD23LB - Most ever weighed (pounds) - self-reported
  9. WTCD25KG - Least ever weighed (kilograms) - self-reported
  10. WTCD25LB - Least ever weighed (pounds) - self-reported

mCAFT (9 DVs)

1. AFCDELG - Eligibility for themodified Canadian Aerobic Fitness Test (mCAFT)

Variable name:
AFCDELG

Based on:
CLC_AGE, V2_TYPE, ATG_13, ATG_33B, PHC_12, PHC_36, PHC_37, PHC_42G,MHR_611B, PAR_11, PAR_21, PAR_31, PAR_43, PAR_44E, PAR_44H,PAR_44I, PAR_45, PAR_5A3A, PAR_5B3A, PAR_5C3A, PAR_5D3A, PAR_5E3A,PAR_5F3A, PAR_5G3A, PAR_5H3A, PAR_5I3A, PAR_5J3A, PAR_5K3A, PAR_61,PAR_72A, ORS_3, BPMDBPS, BPMDBPD, BPMDHR, BDCD13

Description:
This variable indicates whether the respondent was eligible for the modified Canadian Aerobic Fitness Test (mCAFT).  As there are multiple reasons to be screened out of this measure, the prevalence of screen outs by reason should not be based on frequency counts for this variable.  This test was performed by respondents 6 to 69 years of age.

Note:
Created in the Clinic Post-Verify process.

Table 1
AFCDELG Specifications
Value Condition(s) Description Notes
2 V2_TYPE = 2 Not eligible - home visit  
3 CLC_AGE > 69 Not eligible – age  
4 ATG_13 = 1 Not eligible - ate too close to visit time  
5 ATG_33B = 1 Not eligible - drank alcohol too close to visit time  
6 (12 < PHC_12 < NA) Not eligible - more than 12 weeks pregnant  
8 PHC_36 = 1 and
PHC_37 = 2
Not eligible - did not bring breathing medication  
9 PHC_42G = 1 Not eligible - acute or chronic condition  
12 MHR_611B = 1 Not eligible - medication use  
13 (PAR_N11 = 1 or
PAR_21 = 1 or
PAR_31 = 1 or
(PAR_43 = 1 and
PAR_44E = 1) or
(PAR_43 = 1 and
PAR_44H = 1) or
(PAR_43 = 1 and
PAR_44I = 1 and
PAR_45 = 1) or
PAR_5A3A = 1 or
PAR_5B3A = 1 or
PAR_5C3A = 1 or
PAR_5D3A = 1 or
PAR_5E3A = 1 or
PAR_5F3A = 1 or
PAR_5G3A = 1 or
PAR_5H3A = 1 or
PAR_5I3A = 1 or
PAR_5J3A = 1 or
PAR_5K3A = 1 or
PAR_61 = 1 or
PAR_72A = 1)
Not eligible - PAR-Q answer  
14 ORS_3 = 1 Not eligible - other reason  
15 (CLC_AGE > 14 and
(144 < BPMDBPS < NA)) or
(CLC_AGE > 14 and
(144 < BPMDBPD < NA))
Not eligible - high blood pressure  
16 CLC_AGE > 14 and
(99 < BPMDHR < NA)
Not eligible - high heart rate  
17 BDCD13 = 1 Not eligible - donated blood day before clinic visit  
1 Else Eligible  

2. AFTD01 - Starting stage of the modified Canadian Aerobic Fitness Test (mCAFT)

Variable name:
AFTD01

Based on:
CLC_AGE, CLC_SEX, AFCDELG

Description:
This variable indicates the starting stage for the modified Canadian Aerobic Fitness Test (mCAFT).

Note:
Created in the Clinic data collection application.  This test was performed by respondents 6 to 69 years of age.

Source:
The Canadian Physical Activity, Fitness and Lifestyle Approach (3rd Edition, 2004) by the Canadian Society for Exercise Physiology (CSEP)

Table 2
AFTD01 Specifications
Value Condition(s) Description Notes
9 (CLC_AGE = DK, RF, NS) or
(CLC_SEX = DK, RF, NS)
At least one required question was not answered (don’t know, refusal, not stated) NS
6 (1 < AFCDELG < NA) Population exclusions NA
1 (CLC_SEX = 1 and
(59 < CLC_AGE < 70)) or
(CLC_SEX = 2 and
(49 < CLC_AGE < 70))
Set mCAFT starting stage to Stage 1  
2 (CLC_SEX = 1 and
(49 < CLC_AGE < 60)) or
(CLC_SEX = 2 and
(39 < CLC_AGE < 50))
Set mCAFT starting stage to Stage 2  
3 (CLC_SEX = 1 and
(29 < CLC_AGE < 50)) or
(CLC_SEX = 2 and
(14 < CLC_AGE < 40))
Set mCAFT starting stage to Stage 3  
4 CLC_SEX = 1 and
(14 < CLC_AGE < 30)
Set mCAFT starting stage to Stage 4  
5 CLC_AGE < 15 Set mCAFT starting stage to Stage 5  

3. AFTD02 - Ceiling heart rate for the modified Canadian Aerobic Fitness Test (mCAFT)

Variable name:
AFTD02

Based on:
CLC_AGE, AFCDELG, AFTD01

Description:
This variable indicates the ceiling or maximum heart rate that the respondent may reach when completing the modified Canadian Aerobic Fitness Test (mCAFT). It is the heart rate (in beats per minute) at which the test is stopped. The mCAFT consists of  a maximum of eight 3-minute stepping tests. The test is discontinued when the respondent's heart rate reaches the ceiling indicated.  The ceiling rates are based on the age of the respondent.

Note:
Created in the Clinic data collection application.  This test was performed by respondents 6 to 69 years of age.

Source:
The Canadian Physical Activity, Fitness and Lifestyle Approach (3rd Edition, 2004) by the Canadian Society for Exercise Physiology (CSEP)

Table 3
AFTD02 Specifications
Value Condition(s) Description Notes
999 (CLC_AGE = DK, RF, NS) or
(AFTD01 = DK, RF, NS)
At least one required question was not answered (don’t know, refusal, not stated) NS
996 (1 < AFCDELG < NA) Population exclusions NA
182 CLC_AGE = 6 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 6 (in beats per minute)  
181 CLC_AGE = 7 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 7 (in beats per minute)  
180 CLC_AGE = 8 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 8 (in beats per minute)  
179 CLC_AGE = 9 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 9 (in beats per minute)  
178 CLC_AGE = 10 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 10 (in beats per minute)  
177 (CLC_AGE = 11, 12) and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 11 to 12 (in beats per minute)  
176 CLC_AGE = 13 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 13 (in beats per minute)  
175 CLC_AGE = 14 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 14 (in beats per minute)  
174 CLC_AGE = 15 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 15 (in beats per minute)  
173 (CLC_AGE = 16, 17) and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 16 to 17 (in beats per minute)  
172 CLC_AGE = 18 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 18 (in beats per minute)  
171 CLC_AGE = 19 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 19 (in beats per minute)  
170 CLC_AGE = 20 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 20 (in beats per minute)  
169 CLC_AGE = 21 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 21 (in beats per minute)  
168 CLC_AGE = 22 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 22 (in beats per minute)  
167 (CLC_AGE = 23, 24) and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 23 to 24 (in beats per minute)  
166 CLC_AGE = 25 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 25 (in beats per minute)  
165 CLC_AGE = 26 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 26 (in beats per minute)  
164 CLC_AGE = 27 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 27 (in beats per minute)  
163 CLC_AGE = 28 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 28 (in beats per minute)  
162 (CLC_AGE = 29, 30) and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 29 to 30 (in beats per minute)  
161 CLC_AGE = 31 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 31 (in beats per minute)  
160 CLC_AGE = 32 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 32 (in beats per minute)  
159 CLC_AGE = 33 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 33 (in beats per minute)  
158 CLC_AGE = 34 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 34 (in beats per minute)  
157 CLC_AGE = 35 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 35 (in beats per minute)  
156 (CLC_AGE = 36, 37) and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 36 to 37 (in beats per minute)  
155 CLC_AGE = 38 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 38 (in beats per minute)  
154 CLC_AGE = 39 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 39 (in beats per minute)  
153 CLC_AGE = 40 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 40 (in beats per minute)  
152 CLC_AGE = 41 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 41 (in beats per minute)  
151 CLC_AGE = 42 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 42 (in beats per minute)  
150 (CLC_AGE = 43, 44) and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 43 to 44 (in beatsper minute)  
149 CLC_AGE = 45 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 45 (in beats perminute)  
148 CLC_AGE = 46 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 46 (in beats perminute)  
147 CLC_AGE = 47 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 47 (in beats perminute)  
146 CLC_AGE = 48 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 48 (in beats perminute)  
145 (CLC_AGE = 49, 50) and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 49 to 50 (in beatsper minute)  
144 CLC_AGE = 51 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 51 (in beats perminute)  
143 CLC_AGE = 52 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 52 (in beats perminute)  
142 CLC_AGE = 53 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 53 (in beats perminute)  
141 CLC_AGE = 54 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 54 (in beats perminute)  
140 CLC_AGE = 55 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 55 (in beats perminute)  
139 (CLC_AGE = 56, 57) and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 56 to 57 (in beatsper minute)  
138 CLC_AGE = 58 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 58 (in beats perminute)  
137 CLC_AGE = 59 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 59 (in beats perminute)  
136 CLC_AGE = 60 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 60 (in beats perminute)  
135 CLC_AGE = 61 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 61 (in beats perminute)  
134 CLC_AGE = 62 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 62 (in beats perminute)  
133 (CLC_AGE = 63, 64) and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 63 to 64 (in beatsper minute)  
132 CLC_AGE = 65 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 65 (in beats perminute)  
131 CLC_AGE = 66 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 66 (in beats perminute)  
130 CLC_AGE = 67 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 67 (in beats perminute)  
129 CLC_AGE = 68 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 68 (in beats perminute)  
128 CLC_AGE = 69 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 69 (in beats perminute)  

4. AFTD21 - Final Stepping Stage of the modified Canadian Aerobic Fitness Test (mCAFT)

Variable name:
AFTD21

Based on:
AFCDELG, AFT_11, AFT_12, AFT_13, AFT_14, AFT_15, AFT_16, AFT_17, AFT_18

Description:
This variable indicates the final stepping stage for respondents that completed the modified Canadian Aerobic Fitness Test (mCAFT).

Note:
Created in the Clinic data collection application.  This test was performed by respondents 6 to 69 years of age.

Source:
The Canadian Physical Activity, Fitness and Lifestyle Approach (3rd Edition, 2004) by the Canadian Society for Exercise Physiology (CSEP)

Table 4
AFTD21 Specifications
Value Condition(s) Description Notes
96 (1 < AFCDELG < NA) Population exclusions NA
8 (0 < AFT_18 < NA) Final stepping stage set to stage 8  
7 (0 < AFT_17 < NA) Final stepping stage set to stage 7  
6 (0 < AFT_16 < NA) Final stepping stage set to stage 6  
5 (0 < AFT_15 < NA) Final stepping stage set to stage 5  
4 (0 < AFT_14 < NA) Final stepping stage set to stage 4  
3 (0 < AFT_13 < NA) Final stepping stage set to stage 3  
2 (0 < AFT_12 < NA) Final stepping stage set to stage 2  
1 (0 < AFT_11 < NA) Final stepping stage set to stage 1  
99 Else   NS

5. AFTD22 - Immediate Post-exercise HeartRate

Variable name:
AFTD22

Based on:
AFCDELG, AFT_11, AFT_12, AFT_13, AFT_14, AFT_15, AFT_16, AFT_17,AFT_18

Description:
This variable indicates theimmediate post-exercise heart rate for respondents who completedthe modified Canadian Aerobic Fitness Test (mCAFT).

Note:
Created in the Clinic data collection application.  This testwas performed by respondents 6 to 69 years of age.

Source:
The Canadian Physical Activity,Fitness and Lifestyle Approach (3rd Edition, 2004) by the CanadianSociety for Exercise Physiology (CSEP)

Table 5
AFTD22 Specifications
Value Condition(s)  Description Notes
96 (1 < AFCDELG < NA) Population exclusions NA
AFTD22 =
AFT_18
(0 < AFT_18 < NA) The Immediate Post-exercise Heart Rate equals the heart rate atthe end of Stage 8  
AFTD22 =
AFT_17
(0 < AFT_17 < NA) The Immediate Post-exercise Heart Rate equals the heart rate atthe end of Stage 7  
AFTD22 =
AFT_16
(0 < AFT_16 < NA) The Immediate Post-exercise Heart Rate equals the heart rate atthe end of Stage 6  
AFTD22 =
AFT_15
(0 < AFT_15 < NA) The Immediate Post-exercise Heart Rate equals the heart rate atthe end of Stage 5  
AFTD22 =
AFT_14
(0 < AFT_14 < NA) The Immediate Post-exercise Heart Rate equals the heart rate atthe end of Stage 4  
AFTD22 =
AFT_13
(0 < AFT_13 < NA) The Immediate Post-exercise Heart Rate equals the heart rate atthe end of Stage 3  
AFTD22 =
AFT_12
(0 < AFT_12 < NA) The Immediate Post-exercise Heart Rate equals the heart rate atthe end of Stage 2  
AFTD22 =
AFT_11
(0 < AFT_11 < NA) The Immediate Post-exercise Heart Rate equals the heart rate atthe end of Stage 1  
99 Else   NS

6. AFTD71 - Oxygen cost of the modifiedCanadian Aerobic Fitness Test (mCAFT)

Variable name:
AFTD71

Based on:
CLC_SEX, AFCDELG, AFTD21

Description:
This variable indicates the Oxygen cost for respondents whocompleted the modified Canadian Aerobic Fitness Test (mCAFT).Oxygen cost is measured in millilitres / kilograms / minute.

Note:
Created in the Clinic data collection application.  This testwas performed by respondents 6 to 69 years of age.

Source:
The Canadian Physical Activity, Fitness and Lifestyle Approach (3rdEdition, 2004) by the Canadian Society for Exercise Physiology(CSEP)

Table 6
AFTD71 Specifications
Value Condition(s) Description Notes
99.9 (AFTD21 = DK, RF, NS) At least one required question was not answered (don’tknow, refusal, not stated) NS
99.6 (1 < AFCDELG < NA) Population exclusions NA
15.9 AFTD21 = 1 Oxygen cost for respondents with a final stepping stage ofstage 1  
18.0 AFTD21 = 2 Oxygen cost for respondents with a final stepping stage ofstage 2  
22.0 AFTD21 = 3 Oxygen cost for respondents with a final stepping stage ofstage 3  
24.5 AFTD21 = 4 Oxygen cost for respondents with a final stepping stage ofstage 4  
26.3 CLC_SEX = 2 and AFTD21 = 5 Oxygen cost for female respondents with a final stepping stageof stage 5  
29.5 (CLC_SEX = 1 and
AFTD21 = 5) or
(CLC_SEX = 2 and
AFTD21 = 6)
Oxygen cost for male respondents with a final stepping stage ofstage 5 and females with a final stepping stage of stage 6  
33.6 (CLC_SEX = 1 and
AFTD21 = 6) or
(CLC_SEX = 2 and
AFTD21 = 7)
Oxygen cost for male respondents with a final stepping stage ofstage 6 and females with a final stepping stage of stage 7  
36.2 (CLC_SEX = 1 and
AFTD21 = 7) or
(CLC_SEX = 2 and
AFTD21 = 8)
Oxygen cost for male respondents with a final stepping stage ofstage 7 and females with a final stepping stage of stage 8  
40.1 CLC_SEX = 1 and AFTD21 = 8 Oxygen cost for male respondents with a final stepping stage ofstage 8  

7. AFTD72 - Aerobic fitness score based onthe modified Canadian Aerobic Fitness Test (mCAFT)

Variable name:
AFTD72

Based on:
HWM_13KG, AFCDELG, AFTD71

Description:
This variable indicates the aerobic fitness score based on themodified Canadian Aerobic Fitness Test (mCAFT).

Note:
Created in the Clinic data collection application.  This testwas performed by respondents 6 to 69 years of age.

Source:
The Canadian Physical Activity, Fitness and Lifestyle Approach (3rdEdition, 2004) by the Canadian Society for Exercise Physiology(CSEP)

Table 7
AFTD72 Specifications
Value Condition(s)  Description Notes
999 (AFTD71 = DK, RF, NS) At least one required question was not answered (don’tknow, refusal, not stated) NS
996 (1 < AFCDELG < NA) Population exclusions NA
Round((10 * (17.2 +
(1.29 * AFTD71)–
(0.09 * HWM_13KG)–
(0.18 * CLC_AGE))), 1)
(0 < HWM_13KG < NA) Aerobic fitness score Rounded to integer
999 Else   NA

8. AFTD73 - Aerobic fitness norms forrespondents aged 15 – 69

Variable name:
AFTD73

Based on:
CLC_AGE, CLC_SEX, AFCDELG, AFTD72

Description:
This variable indicates the aerobic fitness norms for respondents15 - 69  based on the modified Canadian Aerobic Fitness Test(mCAFT).

Note:
Created in the Clinic data collection application.  This testwas performed by respondents 15 to 69 years of age.
The Canadian Physical Activity, Fitness and Lifestyle Approach (3rdEdition, 2004) provides the following description of the AerobicFitness Norms:
Excellent - aerobic fitness falls within a range that is generallyassociated with optimal health benefits
Very Good- aerobic fitness falls within a range that is generallyassociated with considerable health benefits
Good - aerobic fitness falls within a range that is generallyassociated with many health benefits
Fair - aerobic fitness falls within a range that is generallyassociated with some health benefits but also some health risks
Needs Improvement - aerobic fitness falls within a range that isgenerally associated with considerable health risks

Source:
The Canadian Physical Activity,Fitness and Lifestyle Approach (3rd Edition, 2004) by the CanadianSociety for Exercise Physiology (CSEP)

Table 8
AFTD73 Specifications
Value Condition(s) Description Notes
9 (AFTD72 = DK, RF, NS) At least one required question was not answered (don’tknow, refusal, not stated) NS
6 CLC_AGE < 15 or
(1 < AFCDELG < NA)
Population exclusions NA
0 (CLC_SEX = 1 and
((14 < CLC_AGE < 20) and
(0 < AFTD72 < 436)) or
((19 < CLC_AGE < 30) and
(0 < AFTD72 < 416)) or
((29 < CLC_AGE < 40) and
(0 < AFTD72 < 337)) or
((39 < CLC_AGE < 50) and
(0 < AFTD72 < 319)) or
((49 < CLC_AGE < 60) and
(0 < AFTD72 < 260)) or
((59 < CLC_AGE < 70) and
(0 < AFTD72 < 235))) or
(CLC_SEX = 2 and
((14 < CLC_AGE < 20) and
(0 < AFTD72 < 368)) or
((19 < CLC_AGE < 30) and
(0 < AFTD72 < 350)) or
((29 < CLC_AGE < 40) and
(0 < AFTD72 < 330)) or
((39 < CLC_AGE < 50) and
(0 < AFTD72 < 271)) or
((49 < CLC_AGE < 60) and
(0 < AFTD72 < 246)) or
((59 < CLC_AGE < 70) and
(0 < AFTD72 < 235)))
Needs improvement  
1 (CLC_SEX = 1 and
((14 < CLC_AGE < 20) and
(435 < AFTD72 < 488)) or
((19 < CLC_AGE < 30) and
(415 < AFTD72 < 472)) or
((29 < CLC_AGE < 40) and
(336 < AFTD72 < 401)) or
((39 < CLC_AGE < 50) and
(318 < AFTD72 < 355)) or
((49 < CLC_AGE < 60) and
(259 < AFTD72 < 301)) or
((59 < CLC_AGE < 70) and
(234 < AFTD72 < 287))) or
(CLC_SEX = 2 and
((14 < CLC_AGE < 20) and
(367 < AFTD72 < 395)) or
((19 < CLC_AGE < 30) and
(349 < AFTD72 < 378)) or
((29 < CLC_AGE < 40) and
(329 < AFTD72 < 360)) or
((39 < CLC_AGE < 50) and
(270 < AFTD72 < 319)) or
((49 < CLC_AGE < 60) and
(245 < AFTD72 < 310)) or
((59 < CLC_AGE < 70) and
(234 < AFTD72 < 296)))
Fair  
2 (CLC_SEX = 1 and
((14 < CLC_AGE < 20) and
(487 < AFTD72 < 524)) or
((19 < CLC_AGE < 30) and
(471 < AFTD72 < 506)) or
((29 < CLC_AGE < 40) and
(400 < AFTD72 < 454)) or
((39 < CLC_AGE < 50) and
(354 < AFTD72 < 427)) or
((49 < CLC_AGE < 60) and
(300 < AFTD72 < 365)) or
((59 < CLC_AGE < 70) and
(286 < AFTD72 < 328))) or
(CLC_SEX = 2 and
((14 < CLC_AGE < 20) and
(394 < AFTD72 < 437)) or
((19 < CLC_AGE < 30) and
(377 < AFTD72 < 420)) or
((29 < CLC_AGE < 40) and
(359 < AFTD72 < 401)) or
((39 < CLC_AGE < 50) and
(318 < AFTD72 < 351)) or
((49 < CLC_AGE < 60) and
(309 < AFTD72 < 340)) or
((59 < CLC_AGE < 70) and
(295 < AFTD72 < 328)))
Good  
3 (CLC_SEX = 1 and
((14 < CLC_AGE < 20) and
(523 < AFTD72 < 574)) or
((19 < CLC_AGE < 30) and
(505 < AFTD72 < 556)) or
((29 < CLC_AGE < 40) and
(453 < AFTD72 < 488)) or
((39 < CLC_AGE < 50) and
(426 < AFTD72 < 470)) or
((49 < CLC_AGE < 60) and
(364 < AFTD72 < 418)) or
((59 < CLC_AGE < 70) and
(327 < AFTD72 < 384))) or
(CLC_SEX = 2 and
((14 < CLC_AGE < 20) and
(436 < AFTD72 < 490)) or
((19 < CLC_AGE < 30) and
(419 < AFTD72 < 472)) or
((29 < CLC_AGE < 40) and
(400 < AFTD72 < 454)) or
((39 < CLC_AGE < 50) and
(350 < AFTD72 < 400)) or
((49 < CLC_AGE < 60) and
(339 < AFTD72 < 366)) or
((59 < CLC_AGE < 70) and
(327 < AFTD72 < 358)))
Very good  
4 (CLC_SEX = 1 and
((14 < CLC_AGE < 20) and
(573 < AFTD72 < NA)) or
((19 < CLC_AGE < 30) and
(555 < AFTD72 < NA)) or
((29 < CLC_AGE < 40) and
(487 < AFTD72 < NA)) or
((39 < CLC_AGE < 50) and
(469 < AFTD72 < NA)) or
((49 < CLC_AGE < 60) and
(417 < AFTD72 < NA)) or
((59 < CLC_AGE < 70) and
(383 < AFTD72 < NA))) or
(CLC_SEX = 2 and
((14 < CLC_AGE < 20) and
(489 < AFTD72 < NA)) or
((19 < CLC_AGE < 30) and
(471 < AFTD72 < NA)) or
((29 < CLC_AGE < 40) and
(453 < AFTD72 < NA)) or
((39 < CLC_AGE < 50) and
(399 < AFTD72 < NA)) or
((49 < CLC_AGE < 60) and
(365 < AFTD72 < NA)) or
((59 < CLC_AGE < 70) and
(357 < AFTD72 < NA)))
Excellent  
9 Else   NS

9. AFTD74 - Aerobic fitness norms forrespondents aged less than 15

Variable name:
AFTD74

Based on:
CLC_AGE, AFCDELG, AFTD21, AFTD72

Description:
This variable indicates the aerobic fitness norms for respondents less than 15 based on their aerobic fitness test result.

Note:
Created in the Clinic data collection application.  This testwas performed by respondents 6 to 14 years of age.
The aerobic fitness norms for respondents less than 15 are described as follows:
Excellent - aerobic fitness falls within a range that is generally associated with optimal health benefits
Very good - aerobic fitness falls within a range that is generally associated with considerable health benefits
Good - aerobic fitness falls within a range that is generally associated with many health benefits
Average - aerobic fitness falls within a range that is generally associated with some health benefits but also some health risks
Low - aerobic fitness falls within a range that may accelerate certain health risks

Source:
'Assessing Physical Fitness and Physical Activity in Population-Based Surveys' by the Canadian Fitness and Lifestyle Research Institute, Ottawa: ON.

Table 9
AFTD74 Specifications
Value Condition(s) Description Notes
9 (AFTD72 = DK, RF, NS) At least one required question was not answered (don’tknow, refusal, not stated) NS
6 CLC_AGE > 14 or (1 < AFCDELG < NA) Population exclusions NA
5 CLC_AGE = 6 No standards  
0 AFTD21 = 5 Needs improvement  
1 AFTD21 = 6 Low  
2 AFTD21 = 7 and (167 < AFTD22 < NA) Average  
3 AFTD21 = 7 and (130 < AFTD22 < 168) Very good  
4 AFTD21 = 7 and (0 < AFTD22 < 131) Excellent  
9 Else   NS

Alcohol use (3 DVs)

1. ALCDDLY - Average Daily AlcoholConsumption

Variable name:
ALCDDLY

Based on:
ALCDWKY

Description:
This variable indicates the average number of drinks the respondentconsumed per day in the week prior to the interview.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents less than 12 years of age and those who did not have atleast one drink in the last 12 months were excluded from thepopulation.

Table 1
ALCDDLY Specifications
Value Condition(s) Description Notes
996 ALCDWKY = NA Population exclusions NA
999 ALCDWKY = NS At least one required question was not answered (don’tknow, refusal, not stated) NS
round((ALCDWKY / 7),1) ALCDWKY < 694 Average daily alcohol consumption Rounded to integer (min: 0; max: 99)

2. ALCDTYP - Type of Drinker

Variable name:
ALCDTYP

Based on:
DHH_AGE, ALC_12, ALC_17

Description:
This variable indicates the type of drinker the respondent is basedon his/her drinking habits.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents less than 12 years of age were excluded from thepopulation.

Table 2
ALCDTYP Specifications
Value Condition(s) Description Notes
6 DHH_AGE < 12 Population exclusion NA
9 (ALC_12 = DK, RF, NS) or (ALC_17 = DK, RF, NS) At least one required question was not answered (don’tknow, refusal, not stated) NS
1 (2 <= ALC_12 < NA) Regular drinker  
2 ALC_12 = 1 Occasional drinker  
3 ALC_17 = 1 Former Drinker  
4 ALC_17 = 2 Never Drank  

3. ALCDWKY - Weekly Consumption

Variable name:
ALCDWKY

Based on:
DHH_AGE, ALC_11, ALC_15A, ALC_15B, ALC_15C, ALC_15D, ALC_15E,ALC_15F, ALC_15G

Description:
This variable indicates the total number of drinks consumed in theweek prior to the interview.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents less than 12 years of age and those who did not have atleast one drink in the past 12 months were excluded from thepopulation.

Table 3
ALCDWKY Specifications
Value Condition(s) Description Notes
996 ALC_11 = 2 or
DHH_AGE < 12
Population exclusions NA
999 (ALC_15A = DK, RF, NS) or
(ALC_15B = DK, RF, NS) or
(ALC_15C = DK, RF, NS) or
(ALC_15D = DK, RF, NS) or
(ALC_15E = DK, RF, NS) or
(ALC_15F = DK, RF, NS) or
(ALC_15G = DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NS
0 ALC_14 = 2 Hasn’t had a drink in last week  
ALC_15A +
ALC_15B +
ALC_15C +
ALC_15D +
ALC_15E +
ALC_15F +
ALC_15G
(0 <= ALC_15A < NA) and
(0 <= ALC_15B < NA) and
(0 <= ALC_15C < NA) and
(0 <= ALC_15D < NA) and
(0 <= ALC_15E < NA) and
(0 <= ALC_15F < NA) and
(0 <= ALC_15G < NA)
Number of drinks consumed in past week (min: 0; max: 693)

Anthropometric (23 DVs)

1. ANCDELG - Eligibility for theAnthropometric component

Variable name:
ANCDELG

Based on:
PHC_42C, PHC_42D

Description:
This variable indicates whether the respondent was eligible for theAnthropometric component. As there are multiple reasons to bescreened out of this measure, the prevalence of screen outs byreason should not be based on frequency counts for thisvariable.

Note:
Created in the Clinic Post-Verify process.

Table 1
ANCDELG Specifications
Value Condition(s) Description Notes
9 PHC_42C = 1 and PHC_42D = 1 Not eligible - acute or chronic condition  
1 Else Eligible  

2. HWMD11IN - Standing height (inches)– measured

Variable name:
HWMD11IN

Based on:
PHC_42C, ANCDELG, HWM_11CM

Description:
This variable contains the measured standing height in inches.

Introduced in:
CCHS - Cycle 1.1

Note:
Created in the Clinic data collection application.

Table 2
HWMD11IN Specifications
Value Condition(s) Description Notes
99.6 PHC_42C = 1 or
(ANCDELG > 1 and
ANCDELG < NA)
Population exclusions NA
Round((HWM_11CM * 0.3937), .1) HWM_11CM > 0 and
HWM_11CM < NA
Measured standing height in inches Rounded to one decimal place
99.9 Else   NS

3. HWMD12IN - Sitting height (inches) -measured

Variable name:
HWMD12IN

Based on:
PHC_42C, ANCDELG, HWM_12CM

Description:
This variable contains the measured sitting height in inches.

Note:
Created in the Clinic data collection application.

Table 3
HWMD12IN Specifications
Value Condition(s) Description Notes
99.6 PHC_42C = 1 or
(ANCDELG > 1 and
ANCDELG < NA)
Population exclusions NA
Round((HWM_12CM * 0.3937), .1) HWM_12CM > 0 and
HWM_12CM < NA
Measured sitting height in inches Rounded to one decimal place
99.9 Else   NS

4. HWMD13LB - Weight (pounds) –measured

Variable name:
HWMD13LB

Based on:
PHC_11, PHC_42C, ANCDELG, HWM_13KG

Description:
This variable contains the measured weight in pounds.

Introduced in:
CCHS - Cycle 1.1

Note:
Created in the Clinic data collection application.

Table 4
HWMD13LB Specifications
Value Condition(s) Description Notes
999.6 PHC_11 = 1 or
PHC_42C = 1 or
(ANCDELG > 1 and
ANCDELG < NA)
Population exclusions NA
Round((HWM_13KG * 2.205), .1) HWM_13KG > 0 and
HWM_13KG < NA
Measured weight in pounds Rounded to one decimal place
999.9 Else   NS

5. HWMD14IN - Waist circumference(inches) – measured

Variable name:
HWMD14IN

Based on:
PHC_11, PHC_42C, ANCDELG, HWM_14CM

Description:
This variable contains the waist circumference in inches.

Note:
Created in the Clinic data collection application.
Waist circumference was not measured for pregnant women.

Table 5
HWMD14IN Specifications
Value Condition(s) Description Notes
99.6 PHC_11 = 1 or
PHC_42C = 1 or
(ANCDELG > 1 and
ANCDELG < NA)
Population exclusions NA
Round((HWM_14CM * 0.3937), .1) HWM_14CM > 0 and
HWM_14CM < NA
Waist circumference in inches Rounded to one decimal place
99.9 Else   NS

          

6. HWMD15IN - Hip circumference (inches)– measured

Variable name:
HWMD15IN

Based on:
PHC_11, PHC_42C, ANCDELG, HWM_15CM

Description:
This variable contains the hip circumference in inches.

Note:
Created in the Clinic data collection application.
Hip circumference was not measured for pregnant women

Table 6
HWMD15IN Specifications
Value Condition(s) Description Notes
99.6 PHC_11 = 1 or
PHC_42C = 1 or
(ANCDELG > 1 and
ANCDELG < NA) or
HWMD15CM = NA
Population exclusions NA
Round((HWM_15CM * 0.3937), .1) HWM_15CM > 0 and
HWM_15CM < NA
Hip circumference in inches Rounded to one decimal place
99.9 Else   NS

7. HWMDBMI - Body Mass Index (BMI)– measured

Variable name:
HWMDBMI

Based on:
PHC_11, PHC_42C, ANCDELG, HWM_13KG, HWMDHTM

Description:
Body Mass Index (BMI) is a comparison of "weight" relative to the"height" of respondents.  BMI is calculated by dividing weightin kilograms by height in metres squared.
(BMI = WEIGHT (kilograms) / HEIGHT (metres) SQUARED)

Introduced in:
CCHS - Cycle 1.1

Note:
Created in the Clinic data collection application.
BMI was not calculated for pregnant women.
This BMI classification was created using "measured height" and"measured weight" variables.

Table 7
HWMDBMI Specifications
Value Condition(s) Description Notes
999.99 CLC_SEX = 2 and
(PHC_11 = DK, RF, NS)
Females who did not answer the pregnancy question (don't know,refusal, not stated) NS
999.99 HWM_13KG > NA or
HWMDHTM = NS
Respondents for whom a valid measured height and weight werenot obtained NS
999.96 PHC_11 = 1 or
PHC_42C = 1 or
(1 < ANCDELG < NA)
Population exclusions NA
Round(HWM_13KG /
(HWMDHTM x HWMDHTM), .2)
HWM_13KG < NA and
HWMDHTM < NA
BMI calculated from both measured height and measured weightvalues Rounded to two decimal places

            

8. HWMDBMIA - BMI classification foradults aged 18 and over (measured) - internationalstandard

Variable name:
HWMDBMIA

Based on:
CLC_AGE, PHC_11, PHC_42C, ANCDELG, HWMDBMI

Description:
This variable assigns adult respondents aged 18 and over (exceptpregnant women) to one of the following categories, according totheir Body Mass Index (BMI): underweight; acceptable weight;overweight; obese class I; obese class II; and, obese class III.Here, the BMI categories are adopted from a body weightclassification system recommended by Health Canada and the WorldHealth Organization (WHO) which has been widely usedinternationally.

Introduced in:
CCHS - Cycle 3.1

Note:
Created in the Clinic data collection application.
According to Health Canada, this BMI classification system can beused as a screening tool to identify weight-related health risks atthe population and individual levels. The following health risksare associated with each of the BMI categories for adults aged 18and over:
normal weight = least health risk;
underweight and overweight = increased health risk;
obese class I = high health risk;
obese class II = very high health risk;
obese class III = extremely high health risk;
At the population level, the BMI classification system can be usedto compare body weight patterns and related health risks within andbetween populations and to establish population trends in bodyweight patterns. The classification should be used with caution atthe individual level because the health risk associated with eachBMI category varies considerably between individuals. Particularcaution should be used when classifying: adults who are naturallyvery lean, very muscular adults, some ethnic and racial groups, andseniors.
This variable excludes female respondents aged 18 and over who werepregnant.

Internet site:
http://www.hc-sc.gc.ca/hpfb-dgpsa/onpp-bppn/weight

Table 8
HWMDBMIA Specifications
Value Condition(s) Description Notes
99 HWMDBMI = NS At least one required question was not answered (don’tknow, refusal, not stated) NS
96 CLC_AGE < 18 or
PHC_11 = 1 or
PHC_42C = 1 or
(ANCDELG > 1 and
ANCDELG < NA)
Population exclusions NA
1 HWMDBMI < 18.50 Underweight  
2 (18.50 <= HWMDBMI <= 24.99) Normal weight  
3 (25.00 <= HWMDBMI <= 29.99) Overweight  
4 (30.00 <= HWMDBMI <= 34.99) Obese - Class I  
5 (35.00 <= HWMDBMI <= 39.99) Obese - Class II  
6 HWMDBMI >= 40.00 Obese - Class III  

Reference: For more detailed information see Canadian Guidelinesfor Body Weight Classification in Adults, Health Canada,2003.  These norms are used along with skinfold norms(SFMDS5A) and Waist Circumference norms (HWMDWSTA) to create thebody composition score (SFMDBCA).

9. HWMDBMIK - BMI Classification forChildren Aged 6 to 17 (measured) - CDC BMI-for-age

Variable name:
HWMDBMIK

Based on:
CLC_AGE, PHC_11, PHC_42C, ANCDELG, HWMDBMI

Description:
Body Mass Index (BMI) growth charts can be used beginning at 2years of age.  BMI is calculated from weight and heightmeasurements and is used to determine whether an individual'sweight is appropriate for their height. The growth charts consistof a series of percentile curves illustrating the distribution ofmeasurements in U.S. children.  Most of the data used toconstruct the charts comes from the National Health and NutritionExamination Survey (NHANES), which has periodically collectedheight and weight data (and other health information) on theAmerican population since the early 1960's.

Note:
Created in the Clinic data collection application.
The following percentiles were selected as cutoff points:
5th percentile and below = underweight;
From the 5th percentile up to and including the 85th percentile =normal;
From the 85th percentile up to and including the 95th percentile =overweight;
Above the 95th percentile = obese.

Table 9
HWMDBMIK Specifications
Value Condition(s) Description Notes
99 HWTDBMI = NS At least one required question was not answered (don’tknow, refusal, not stated) NS
96 CLC_AGE >17 or
PHC_11 = 1 or
PHC_42C = 1 or
(1 < ANCDELG < NA)
Population exclusions NA
1 At or below the 5th percentile for the child's age in days, andsex Underweight  
2 Between the 5th and up to and including the 85th percentile forthe child's age in days, and sex Normal weight  
3 Between the 86th and up to and including the 95th percentilefor the child's age in days, and sex Overweight  
4 Above the 95th percentile for the child's age in days, andsex Obese  

Reference: For more information, please see www.cdc.gov/growthcharts

10. HWMDCOL - BMI Classification forChildren Aged 6 to 17 (Measured) - Cole ClassificationSystem

Variable name:
HWMDCOL

Based on:
CLC_AGE, CLC_SEX, CLC_YOB, CLC_MOB, CLC_DOB, V2_YEAR, V2_MONTH,V2_DAY, PHC_42C, ANCDELG, HWMDBMI

Description:
This variable classifies children aged 6 to 17 as "obese" or"overweight" according to the age-and-sex-specific BMI cut-offpoints as defined by Cole et al. The Cole cut-off points are basedon pooled international data (Brazil, Great Britain, Hong Kong,Netherlands, Singapore, and United States) for BMI and linked tothe internationally accepted adult BMI cut-off points of 25(overweight) and 30 kg/m2 (obese).

Introduced in:
CCHS - Cycle 3.1

Note:
Respondents who do not fall within the categories of "Obese" or"Overweight" (as defined by Cole et al.) have been classified byCCHS as "neither obese nor overweight".
This variable excludes female respondents who were pregnant andrespondents who were 216 months in age, i.e. 18 years old orolder.

Table 10.1
HWMDCOL Temporary Reformat
Value Condition(s) Description Notes
AGET1
  CLC_AGM / 12
CLC_AGM < NA Convert respondent’s "age in months" to "age inyears" Rounded to nearest 0.5
CLC_AGM
  Age in months
Interview date converted in months (V2_YEAR, V2_MTH and V2_DAY)- Date of birth converted in months (CLC_YOB, CLC_MOB andCLC_DOB) Create respondent’s age in months at time of theinterview (Min: 72; Max: 203)
9999 (CLC_DOB = DK, RF, NS) or
(CLC_MOB = DK, RF, NS) or
(CLC_YOB = DK, RF, NS)
A valid day of birth or month of birth or year of birth is notavailable for the respondent NS

 

Table 10.2
HWMDCOL Specifications
Value Condition(s) Description Notes
9 HWMDBMI = NS At least one required question was not answered (don’tknow, refusal, not stated) NS
6 CLC_AGE >17 or
PHC_11 = 1 or
PHC_42C = 1 or
(1 < ANCDELG < NA)
Population exclusions NA
2 (AGET1 = 6 and
CLC_SEX = 1 and
(HWMDBMI >=  17.55 and
HWMDBMI < 19.78)) or
(AGET1 = 6 and
CLC_SEX = 2 and
(HWMDBMI >=  17.34 and
HWMDBMI < 19.65)) or
(AGET1 = 6.5 and
CLC_SEX = 1 and
(HWMDBMI >=  17.71 and
HWMDBMI < 20.23)) or
(AGET1 = 6.5 and
CLC_SEX = 2 and
(HWMDBMI >=  17.53 and
HWMDBMI < 20.08)) or
(AGET1 = 7 and
CLC_SEX = 1 and
(HWMDBMI >=  17.92 and
HWMDBMI < 20.63)) or
(AGET1 = 7 and
CLC_SEX = 2 and
(HWMDBMI >=  17.75 and
HWMDBMI < 20.51)) or
(AGET1 = 7.5 and
CLC_SEX = 1 and
(HWMDBMI >=  18.16 and
HWMDBMI < 21.09)) or
(AGET1 = 7.5 and
CLC_SEX = 2 and
(HWMDBMI >=  18.03 and
HWMDBMI < 21.01)) or
(AGET1 = 8 and
CLC_SEX = 1 and
(HWMDBMI >=  18.44 and
HWMDBMI < 21.60)) or
(AGET1 = 8 and
CLC_SEX = 2 and
(HWMDBMI >=  18.35 and
HWMDBMI < 21.57)) or
(AGET1 = 8.5 and
CLC_SEX = 1 and
(HWMDBMI >=  18.76 and
HWMDBMI < 22.17)) or
(AGET1 = 8.5 and
CLC_SEX = 2 and
(HWMDBMI >=  18.69 and
HWMDBMI < 22.18)) or
(AGET1 = 9 and
CLC_SEX = 1 and
(HWMDBMI >=  19.10 and
HWMDBMI < 22.77)) or
(AGET1 = 9 and
CLC_SEX = 2 and
(HWMDBMI >=  19.07 and
HWMDBMI < 22.81)) or
(AGET1 = 9.5 and
CLC_SEX = 1 and
(HWMDBMI >=  19.46 and
HWMDBMI < 23.39)) or
(AGET1 = 9.5 and
CLC_SEX = 2 and
(HWMDBMI >=  19.45 and
HWMDBMI < 23.46)) or
(AGET1 = 10 and
CLC_SEX = 1 and
(HWMDBMI >=  19.84 and
HWMDBMI < 24.00)) or
(AGET1 = 10 and
CLC_SEX = 2 and
(HWMDBMI >=  19.86 and
HWMDBMI < 24.11)) or
(AGET1 = 10.5 and
CLC_SEX = 1 and
(HWMDBMI >=  20.20 and
HWMDBMI < 24.57)) or
(AGET1 = 10.5 and
CLC_SEX = 2 and
(HWMDBMI >=  20.29 and
HWMDBMI < 24.77)) or
(AGET1 = 11 and
CLC_SEX = 1 and
(HWMDBMI >=  20.55 and
HWMDBMI < 25.10)) or
(AGET1 = 11 and
CLC_SEX = 2 and
(HWMDBMI >=  20.74 and
HWMDBMI < 25.42)) or
(AGET1 = 11.5 and
CLC_SEX = 1 and
(HWMDBMI >=  20.89 and
HWMDBMI < 25.58)) or
(AGET1 = 11.5 and
CLC_SEX = 2 and
(HWMDBMI >=  21.20 and
HWMDBMI < 26.05)) or
(AGET1 = 12 and
CLC_SEX = 1 and
(HWMDBMI >=  21.22 and
HWMDBMI < 26.02)) or
(AGET1 = 12 and
CLC_SEX = 2 and
(HWMDBMI >=  21.68 and
HWMDBMI < 26.67)) or
(AGET1 = 12.5 and
CLC_SEX = 1 and
(HWMDBMI >=  21.56 and
HWMDBMI < 26.43)) or
(AGET1 = 12.5 and
CLC_SEX = 2 and
(HWMDBMI >=  22.14 and
HWMDBMI < 27.24)) or
(AGET1 = 13 and
CLC_SEX = 1 and
(HWMDBMI >=  21.91 and
HWMDBMI < 26.84)) or
(AGET1 = 13 and
CLC_SEX = 2 and
(HWMDBMI >=  22.58 and
HWMDBMI < 27.76)) or
(AGET1 = 13.5 and
CLC_SEX = 1 and
(HWMDBMI >=  22.27 and
HWMDBMI < 27.25)) or
(AGET1 = 13.5 and
CLC_SEX = 2 and
(HWMDBMI >=  22.98 and
HWMDBMI < 28.20)) or
(AGET1 = 14 and
CLC_SEX = 1 and
(HWMDBMI >=  22.62 and
HWMDBMI < 27.63)) or
(AGET1 = 14 and
CLC_SEX = 2 and
(HWMDBMI >=  23.34 and
HWMDBMI < 28.57)) or
(AGET1 = 14.5 and
CLC_SEX = 1 and
(HWMDBMI >=  22.96 and
HWMDBMI < 27.98)) or
(AGET1 = 14.5 and
CLC_SEX = 2 and
(HWMDBMI >=  23.66 and
HWMDBMI < 28.87)) or
(AGET1 = 15 and
CLC_SEX = 1 and
(HWMDBMI >=  23.29 and
HWMDBMI < 28.30)) or
(AGET1 = 15 and
CLC_SEX = 2 and
(HWMDBMI >=  23.94 and
HWMDBMI < 29.11)) or
(AGET1 = 15.5 and
CLC_SEX = 1 and
(HWMDBMI >=  23.60 and
HWMDBMI < 28.60)) or
(AGET1 = 15.5 and
CLC_SEX = 2 and
(HWMDBMI >=  24.17 and
HWMDBMI < 29.29)) or
(AGET1 = 16 and
CLC_SEX = 1 and
(HWMDBMI >=  23.90 and
HWMDBMI < 28.88)) or
(AGET1 = 16 and
CLC_SEX = 2 and
(HWMDBMI >=  24.37 and
HWMDBMI < 29.43)) or
(AGET1 = 16.5 and
CLC_SEX = 1 and
(HWMDBMI >=  24.19 and
HWMDBMI < 29.14)) or
(AGET1 = 16.5 and
CLC_SEX = 2 and
(HWMDBMI >=  24.54 and
HWMDBMI < 29.56)) or
(AGET1 = 17 and
CLC_SEX = 1 and
(HWMDBMI >=  24.46 and
HWMDBMI < 29.41)) or
(AGET1 = 17 and
CLC_SEX = 2 and
(HWMDBMI >=  24.70 and
HWMDBMI < 29.69)) or
(AGET1 = 17.5 and
CLC_SEX = 1 and
(HWMDBMI >=  24.73 and
HWMDBMI < 29.70)) or
(AGET1 = 17.5 and
CLC_SEX = 2 and
(HWMDBMI >=  24.85 and
HWMDBMI < 29.84)) or
(AGET1 = 18 and
CLC_SEX = 1 and
(HWMDBMI >=  25.00 and
HWMDBMI < 30.00))or
(AGET1 = 18 and
CLC_SEX = 2 and
(HWMDBMI >=  25.00 and
HWMDBMI < 30.00))
Overweight  
3 (AGET1 = 6 and
CLC_SEX = 1 and
HWMDBMI >=  19.78) or
(AGET1 = 6 and
CLC_SEX = 2 and
HWMDBMI >=  19.65) or
(AGET1 = 6.5 and
CLC_SEX = 1 and
HWMDBMI >=  20.23) or
(AGET1 = 6.5 and
CLC_SEX = 2 and
HWMDBMI >=  20.08) or
(AGET1 = 7 and
CLC_SEX = 1 and
HWMDBMI >=  20.63) or
(AGET1 = 7 and
CLC_SEX = 2 and
HWMDBMI >=  20.51) or
(AGET1 = 7.5 and
CLC_SEX = 1 and
HWMDBMI >=  21.09) or
(AGET1 = 7.5 and
CLC_SEX = 2 and
HWMDBMI >=  21.01) or
(AGET1 = 8 and
CLC_SEX = 1 and
HWMDBMI >=  21.60) or
(AGET1 = 8 and
CLC_SEX = 2 and
HWMDBMI >=  21.57) or
(AGET1 = 8.5 and
CLC_SEX = 1 and
HWMDBMI >=  22.17) or
(AGET1 = 8.5 and
CLC_SEX = 2 and
HWMDBMI >=  22.18) or
(AGET1 = 9 and
CLC_SEX = 1 and
HWMDBMI >=  22.77) or
(AGET1 = 9 and
CLC_SEX = 2 and
HWMDBMI >=  22.81) or
(AGET1 = 9.5 and
CLC_SEX = 1 and
HWMDBMI >=  23.39) or
(AGET1 = 9.5 and
CLC_SEX = 2 and
HWMDBMI >=  23.46) or
(AGET1 = 10 and
CLC_SEX = 1 and
HWMDBMI >=  24.00) or
(AGET1 = 10 and
CLC_SEX = 2 and
HWMDBMI >=  24.41) or
(AGET1 = 10.5 and
CLC_SEX = 1 and
HWMDBMI >=  24.57) or
(AGET1 = 10.5 and
CLC_SEX = 2 and
HWMDBMI >=  24.77) or
(AGET1 = 11 and
CLC_SEX = 1 and
HWMDBMI >=  25.10) or
(AGET1 = 11 and
CLC_SEX = 2 and
HWMDBMI >=  24.42) or
(AGET1 = 11.5 and
CLC_SEX = 1 and
HWMDBMI >=  25.58) or
(AGET1 = 11.5 and
CLC_SEX = 2 and
HWMDBMI >=  26.05) or
(AGET1 = 12 and
CLC_SEX = 1 and
HWMDBMI >=  26.02) or
(AGET1 = 12 and
CLC_SEX = 2 and
HWMDBMI >=  26.67) or
(AGET1 = 12.5 and
CLC_SEX = 1 and
HWMDBMI >=  26.43) or
(AGET1 = 12.5 and
CLC_SEX = 2 and
HWMDBMI >=  27.24) or
(AGET1 = 13 and
CLC_SEX = 1 and
HWMDBMI >=  26.84) or
(AGET1 = 13 and
CLC_SEX = 2 and
HWMDBMI >=  27.76) or
(AGET1 = 13.5 and
CLC_SEX = 1 and
HWMDBMI >=  27.25) or
(AGET1 = 13.5 and
CLC_SEX = 2 and
HWMDBMI >=  28.20) or
(AGET1 = 14 and
CLC_SEX = 1 and
HWMDBMI >=  27.63) or
(AGET1 = 14 and
CLC_SEX = 2 and
HWMDBMI >=  28.57) or
(AGET1 = 14.5 and
CLC_SEX = 1 and
HWMDBMI >=  27.98) or
(AGET1 = 14.5 and
CLC_SEX = 2 and
HWMDBMI >=  28.87) or
(AGET1 = 15 and
CLC_SEX = 1 and
HWMDBMI >=  28.30) or
(AGET1 = 15 and
CLC_SEX = 2 and
HWMDBMI >=  29.11) or
(AGET1 = 15.5 and
CLC_SEX = 1 and
HWMDBMI >=  28.60) or
(AGET1 = 15.5 and
CLC_SEX = 2 and
HWMDBMI >=  29.29) or
(AGET1 = 16 and
CLC_SEX = 1 and
HWMDBMI >=  28.88) or
(AGET1 = 16 and
CLC_SEX = 2 and
HWMDBMI >=  29.43) or
(AGET1 = 16.5 and
CLC_SEX = 1 and
HWMDBMI >=  29.14) or
(AGET1 = 16.5 and
CLC_SEX = 2 and
HWMDBMI >=  29.56) or
(AGET1 = 17 and
CLC_SEX = 1 and
HWMDBMI >=  29.41) or
(AGET1 = 17 and
CLC_SEX = 2 and
HWMDBMI >=  29.69) or
(AGET1 = 17.5 and
CLC_SEX = 1 and
HWMDBMI >=  29.70) or
(AGET1 = 17.5 and
CLC_SEX = 2 and
HWMDBMI >=  29.84) or
(AGET1 = 18 and
CLC_SEX = 1 and
HWMDBMI >=  30.00) or
(AGET1 = 18 and
CLC_SEX = 2 and
HWMDBMI >=  30.00)
Obese  
1 Else Neither overweight nor obese  

 

Reference: For more information about the Cole BMIclassification system, see Establishing a Standard Definition forChild Overweight and Obesity Worldwide - International survey, byTim J. Cole, Mary C. Bellizzi, Katherine M. Flegal, William H.Dietz, published in British Medical Journal, Volume: 320, May2000.

11. HWMDHTM – Standing height(metres) – measured

Variable name:
HWMDHTM

Based on:
PHC_42C, ANCDELG, HWM_11CM

Description:
This variable indicates the respondent's standing height inmetres.

Introduced in:
CCHS - Cycle 3.1

Table 11
HWMDHTM Specifications
Value Condition(s) Description Notes
9.999 (HWM_11CM = DK, RF, NS) At least one required question was not answered (don’tknow, refusal, not stated) NS
9.996 PHC_42C = 1 or
(1 < ANCDELG < NA)
Population exclusions NA
HWM_11CM / 100 Else Height in metres  

12. HWMDLLN - Leg Length

Variable name:
HWMDLLN

Based on:
PHC_42C, ANCDELG, HWM_11CM, HWM_12CM

Description:
This variable calculates the leg length in centimetres of arespondent as sitting height subtracted from standing height.

Table 12
HWMDLLN Specifications
Value Condition(s) Description Notes
999 (HWM_11CM = DK, RF, NS) or
(HWM_12CM = DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NS
996 PHC_42C = 1 or
(1 < ANCDELG < NA)
Population exclusions NA
HWM_11CM –
HWM_12CM
Else Leg Length  

13. HWMDMAT - Maturity Offset

Variable name:
HWMDMAT

Based on:
ANCDELG, CLC_AGE, CLC_MOB, CLC_SEX, CLC_YOB, PHC_42C, HWM_11CM,HWM_12CM, HWM_13KG, HWMDLLN

Description:
Age at peak height velocity (APHV) is a common bench mark inchildren used to estimate biological age.  How far anindividual is from PHV (Maturity Offset) can be predicted using aregression equation including measures of sex, age, height, sittingheight and weight.

Note:
Maturity Offset is calculated for ages 8 to 16 in girls and ages 9to 18 in boys.

Table 13.1
HWMDMAT Temporary Reformat
Value Condition(s) Description Notes
HWMTWHR
100 * (HWM_13KG /  HWM_11CM)
(HWM_11CM <> DK, RF, NS) and
(HWM_13KG <> DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NS
AGET3
Round(((mdy(v2_mth, v2_day, v2_year)
- mdy(clc_mob, clc_dob, clc_yob))/365.25), 0.5)
  Calculate respondent's age Rounded to nearest 0.5

 

Table 13.2
HWMDMAT Specifications
Value Condition(s) Description Notes
99.99 (HWM_11CM = DK, RF, NS) or
(HWM_13KG = DK, RF, NS) or
HWMDLLN = NS or
(CLC_YOB = DK, RF, NS) or
(CLC_MOB = DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NS
99.96 (CLC_SEX = 1 and
(CLC_AGE < 9 or
CLC_AGE > 18)) or
(CLC_SEX = 2 and
(CLC_AGE < 8 or
CLC_AGE > 16)) or
PHC_42C = 1 or
(1 < ANCDELG < NA) or
HWM_11CM = NA or
HWM_12CM = NA or
HWM_13KG = NA
Population exclusions NA
round((-9.236 +
(0.0002708 *
HWMDLLN *
HWM_12CM) +
(-0.001663 *
AGET3 *
HWMDLLN) +
(0.007216 *
AGET3 *
HWM_12CM) +
(0.02292 *
HWMTWHR)),
0.01)
CLC_SEX = 1 and
(CLC_AGE > 8 and
CLC_AGE < 19)
Maturity offset for males  
round((-9.376+
(0.0001882 *
HWMDLLN *
HWM_12CM)) +
(0.0022*
AGET3 *
HWMDLLN) +
(0.005841 *
AGET3 *
HWM_12CM) -
 (0.002658 *
AGET3 *
HWM_13KG) +
 (0.07693 *
HWMTWHR)),
0.01)
CLC_SEX = 2 and
(CLC_AGE > 7 and
CLC_AGE < 17)
Maturity offset for females  

 

Reference: For more information on Maturity Offset please see"An assessment of maturity from anthropometric measurements" byMirwald et al. 2001 in the Official Journal of the American Collegeof Sports Medicine.

14. HWMDWSTA - Waist CircumferenceNorms

Variable name:
HWMDWSTA

Based on:
CLC_SEX, PHC_42C, ANCDELG, HWM_14CM, HWMDBMI

Description:
Waist circumference (WC) is an important indicator of health riskassociated with abdominal obesity.  Sex-specific cut-offpoints have been established to identify risks associated withexcess abdominal fat.  A WC above these points is associatedwith an increased health risk.  The measurement should be usedamong those with Body Mass Indexes (BMIs) between 18.5 and 34.9, toidentify additional risk.  For BMIs > 35.0, the WCmeasurement does not provide additional information on healthrisk.

Note:
Created in the Clinic data collection application.  Thesenorms are for respondents 15 to 69 years of age.
These norms are used along with skinfold norms (SFMDS5A) and BMI(HWMDBMI) to create the body composition score (SFMDBCA).

Table 14
HWMDWSTA Specifications
Value Condition(s) Description Notes
9 (HWM_14CM = DK, RF, NS) or
HWMDBMI = NS
At least one required question was not answered (don’tknow, refusal, not stated) NS
6 CLC_AGE < 15 or
CLC_AGE > 69 or
PHC_42C = 1 or
(1 < ANCDELG < NA) or
HWM_14CM = NA
Population exclusions NA
0 (29.99 < HWMDBMI < NA) and
((CLC_SEX = 1 and
(101.0 < HWM_14CM < NA)) or
(CLC_SEX = 2 and
(87.0 < HWM_14CM < NA)))
Score of 0 Needs improvement
1 (18.49 < HWMDBMI < 30.0) and
((CLC_SEX = 1 and
(101.0 < HWM_14CM < NA)) or
(CLC_SEX = 2 and
(79.9 < HWM_14CM < 87.1)))
Score of 1 Fair
2 (29.99 < HWMDBMI < NA) and
((CLC_SEX = 1 and
(93.9 < HWM_14CM < 101.1)) or
((CLC_SEX = 2 and
(79.9 < HWM_14CM < 87.1)))
Score of 2 Good
3 (CLC_SEX = 1 and
((0 < HWMDBMI < 18.50) or
((18.49 < HWMDBMI < 30.00) and
(93.9 < HWM_14CM < 101.1)))) or
(CLC_SEX = 2 and
((0 < HWMDBMI < 18.50) or
((18.49 < HWMDBMI < 30.00) and
(79.9 < HWM_14CM < 87.1))))
Score of 3 Very good
4 (CLC_SEX = 1 and
(0 < HWM_14CM < 94.0)) or
(CLC_SEX = 2 and
(0 < HWM_14CM < 80.0))
Score of 4 Excellent

           

Reference: For more information, please see Canadian Guidelinesfor Body Weight Classification, Health Canada, 2003, and TheCanadian Physical Activity, Fitness and Lifestyle Approach (3rdEdition, 2004) by the Canadian Society for Exercise Physiology(CSEP).

15. HWMDWTH - Waist to hipratio

Variable name:
HWMDWTH

Based on:
PHC_11, PHC_42C, ANCDELG, HWM_14CM, HWM_15CM

Description:
This variable calculates thewaist-to-hip ratio of the respondent.

Note:
Created in the Clinic data collection application.

Table 15
HWMDWTH Specifications
Value Condition(s) Description Notes
99.99 HWM_14CM = DK, RF, NS or
HWM_15CM = DK, RF, NS
At least one required question was not answered
(don’t know, refusal, not stated)
NS
99.96 PHC_11 = 1 or
(PHC_12 > 12 and
PHC_12 < NA) or
PHC_42C = 1 or
(ANCDELG > 1 and
ANCDELG < NA)
Population exclusions NA
Round((HWM_14CM /
HWM_15CM), .01)
Else Waist to hip ratio  

16. SFMDBCA - Body CompositionNorms

Variable name:
SFMDBCA

Based on:
CLC_AGE, CLC_SEX, HWM_14CM, HWMDBMI, HWMDWSTA, SFMDS5A

Description:
For respondents aged 15-69, the body composition score isinterpreted based on ratings from the Canadian Physical Activity,Fitness and Lifestyle Approach (CPAFLA). There are currently nostandards from which to interpret the score for respondents aged6-14 and 70-79.

Note:
Created in the Clinic data collection application. This variableapplies to respondents 15 to 69 years of age.

Table 16.1
SFMDBCA Temporary Reformat
Value
PTS1
Condition(s) Description Notes

Round((
HWMDWSTA * 1.5 +
SFMDS5A) / 2.5, .1)

(0 < HWMDBMI < NA) and
(SFMDS5A = 0, 1, 2, 3, 4) and
(HWMDWSTA = 0, 1, 2, 3, 4)

Calculation for body composition score given all
three measures, i.e., Body Mass Index, Waist
Circumference, and Sum of Five Skinfolds

Rounded to 1
decimal place

SFMDBCA

(0 < HWMDBMI < NA) and
(SFMDS5A = 0, 1, 2, 3, 4) and
(HWMDWSTA = DK, RF, NS)

Value for body composition score given Body
Mass Index and Sum of Five Skinfolds only (no
Waist Circumference)

 

HWMDWSTA

(0 < HWMDBMI < NA) and
(HWMDWSTA = 0, 1, 2, 3, 4) and
(SFMDS5A = DK, RF, NS)

Value for body composition score given Body
Mass Index and Waist Circumference only (no
Sum of Five Skinfolds)

 

1

((32.49 < HWMDBMI < 35.00) and
(SFMDS5A = DK, RF, NS) and
(HWMDWSTA = DK, RF, NS)) or
(CLC_SEX = 1 and
(HWMDBMI = DK, RF, NS) and
(SFMDS5A = DK, RF, NS) and
(101.0 < HWM_14CM < NA)) or
(CLC_SEX = 2 and
(HWMDBMI = DK, RF, NS) and
(SFMDS5A = DK, RF, NS) and
(87.0 < HWM_14CM < NA))

Value for body composition score given Body
Mass Index (between 32.49 and 35.00) only (no
Waist Circumference or Sum of Five Skinfolds)
and for males given Waist Circumference greater
than 101.0 cm only (no BMI, no Sum of Five
Skinfolds) and for females given Waist
Circumference greater than 87.0 cm only (no
BMI, no Sum of Five Skinfolds)

 

2

(29.99 < HWMDBMI < 32.50) and
(SFMDS5A = DK, RF, NS) and
(HWMDWSTA = DK, RF, NS)

Value for body composition score given Body
Mass Index (between 29.99 and 32.50) only (no
Waist Circumference or Sum of Five Skinfolds)

 

3

((0 < HWMDBMI < 18.50) or
(24.99 < HWMDBMI < 30.00)) and
(SFMDS5A = DK, RF, NS) and
(HWMDWSTA = DK, RF, NS) or
(CLC_SEX = 1 and
(HWMDBMI = DK, RF, NS) and
(SFMDS5A = DK, RF, NS) and
(93.9 < HWM_14CM < 101.1)) or
(CLC_SEX = 2 and
(HWMDBMI = DK, RF, NS) and
(SFMDS5A = (DK, RF, NS) and
(79.9 < HWM_14CM < 87.1))

Value for body composition score given Body
Mass Index (between 0 and 18.50 and between
24.99 and 30.00) only (no Waist Circumference
or Sum of Five Skinfolds) and for males given
Waist Circumference between 93.9 and 101.1
cm only (no BMI, no Sum of Five Skinfolds) and
for females given Waist Circumference between
79.9 and 87.1 cm only (no BMI, no Sum of Five Skinfolds)

 

4

((18.49 < HWMDBMI < 25.00) and
(SFMDS5A = DK, RF, NS) and
(HWMDWSTA = (DK, RF, NS)) or
(CLC_SEX = 1 and
(HWMDBMI = DK, RF, NS) and
(SFMDS5A = DK, RF, NS) and
(0 < HWM_14CM < 94.0)) or
(CLC_SEX = 2 and
(HWMDBMI = DK, RF, NS) and
(SFMDS5A = DK, RF, NS) and
(0 < HWM_14CM < 80.0))

Value for body composition score given Body Mass Index (between18.49 and 25.00) only (no Waist Circumference or Sum of FiveSkinfolds) and for males given Waist Circumference less than 94.0cm only (no BMI, no Sum of Five Skinfolds) and for females givenWaist Circumference less than 80.0 cm only (no BMI, no Sum of FiveSkinfolds)

 

5

Else

 

 

 

Table 16.2
HWMDWTH Specifications
Value Condition(s) Description Notes
6 (CLC_AGE < 15 or
CLC_AGE > 69) or
(HWM_14CM = NA and
HWMDBMI = NA and
HWMDWSTA = NA and
SFMDS5A = NA)
Population exclusions NA
9 HWM_14CM > NA and
HWMDBMI = NS and
HWMDWSTA = NS and
SFMDS5A = NS
At least one required question was not answered (don’tknow, refusal, not stated) NS
0 (0 <= PTS1 < 0.5) Needs Improvement. Respondent's Body Composition Score fallswithin a range that is generally associated with considerablehealth risk  
1 (0.4 < PTS1 < 1.5) Fair. Respondent's Body Composition Score falls within a rangethat is generally associated with some health risk  
2 (1.4 < PTS1 < 2.5) Good. Respondent's Body Composition Score falls within a rangethat is generally associated with many health benefits  
3 (2.4 < PTS1 < 3.5) Very Good. Respondent's Body Composition Score falls within arange that is generally associated with considerable healthbenefits  
4 (3.4 < PTS1 < 5.0) Excellent. Respondent's Body Composition Score falls within arange that is generally associated with optimal healthbenefits  
5 PTS1 > 4.9 There are currently no standards with which to interpret theBody Composition Score  

 

Reference: This variable uses the sum of five skinfolds norm(SFMDS5A), the waist circumference norms (HWMDWSTA) and the BMInorms (HWMDBMIA) to create a body composition score.  Thescore is calculated based on an equation if all three norms areavailable.  If not, a score is assigned based on the availablemeasures, and according to the CPAFLA approach.

17. SFMDBSA - Biceps SkinfoldAverage

Variable name:
SFMDBSA

Based on:
PHC_11, PHC_12, PHC_42D, ANCDELG, HWMDBMI, SFM_12, SFM_22,SFM_32

Description:
This variable indicates the average of the biceps skinfoldmeasurements in millimetres.

Note:
Created in the Clinic data collection application.

This derived variable is created based on skinfold measurementsfrom appropriately selected respondents who had at least onemeasurement taken.  Two sets of measurements are preferred;however, if only one measurement was taken then the derivedvariable will equal the actual measurement.  If twomeasurements were taken and the difference between the twomeasurements was less than .5 mm then the derived variable will bethe average of the two measurements.  If the differencebetween the above-mentioned two measurements was greater than .4 mmthen a third measurement was taken.  If two of the threemeasurements  were within .4 mm then those two measurementswill be used to create the derived variable.  If all threemeasurements differ by more than .4 mm then the derived variablewill be the average of the three measurements.

Table 17
SFMDBSA Specifications
Value Condition(s) Description Notes
99.6

PHC_11 = 1 or
(12 < PHC_12 < NA) or
PHC_42D = 1 or
(1 < ANCDELG < NA) or
(29.99 < HWMDBMI < NA)

Population exclusions NS
99.9 (SFM_12 = DK, RF, NS) and
(SFM_22 = DK, RF, NS) and
(SFM_32 = DK, RF, NS)
At least one required question was not
answered (don’t know, refusal, not stated)
NA
  Calculate an average using the two
skinfold measurements that are different by 0.4 mm or less
   

18. SFMDICA - Iliac Crest SkinfoldAverage

Variable name:
SFMDICA

Based on:
PHC_11, PHC_12, PHC_42D, ANCDELG, HWMDBMI, SFM_14, SFM_24,SFM_34

Description:
This variable indicates the average of the iliac crest skinfoldmeasurements in millimetres.

Note:
Created in the Clinic data collection application.

This derived variable is created based on skinfold measurementsfrom appropriately selected respondents who had at least onemeasurement taken.  Two sets of measurements are preferred;however, if only one measurement is taken then the derived variablewill equal the actual measurement.  If two measurements aretaken and the difference between the two measurements is less than.5 mm then the derived variable will be the average of the twomeasurements.  If the difference between the above-mentionedtwo measurements is greater than .4 mm then a third measurement istaken.  If two of the three measurements are within .4 mm thenthose two measurements will be used to create the derivedvariable.  If all three measurements differ by more than .4 mmthen the derived variable will be the average of the threemeasurements.

Table 18
SFMDICA Specifications
Value Condition(s) Description Notes
99.6

PHC_11 = 1 or
(12 < PHC_12 < NA) or
PHC_42D = 1 or
(1 < ANCDELG < NA) or
(29.99 < HWMDBMI < NA)

Population exclusions NS
99.9 (SFM_14 = DK, RF, NS) and
(SFM_24 = DK, RF, NS) and
(SFM_34 = DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NA
  Calculate an average using the two
skinfold measurements that are different by 0.4 mm or less
   

19. SFMDMCA - Medial Calf SkinfoldsAverage

Variable name:
SFMDMCA

Based on:
PHC_11, PHC_12, PHC_42D, ANCDELG, HWMDBMI, SFM_15, SFM_25,SFM_35

Description:
This variable indicates the average of the medial calf skinfoldmeasurements in millimetres.

Note:
Created in the Clinic data collection application.

This derived variable is created based on skinfold measurementsfrom appropriately selected respondents who had at least onemeasurement taken.  Two sets of measurements are preferred;however, if only one measurement was taken then the derivedvariable will equal the actual measurement.  If twomeasurements were taken and the difference between the twomeasurements was less than .5 mm then the derived variable will bethe average of the two measurements.  If the differencebetween the above-mentioned two measurements was greater than .4 mmthen a third measurement was taken.  If two of the threemeasurements were within .4 mm then those two measurements will beused to create the derived variable.  If all threemeasurements differ by more than .4 mm then the derived variablewill be the average of the three measurements.

Table 19
SFMDMCA Specifications
Value Condition(s) Description Notes
99.6

PHC_11 = 1 or
(12 < PHC_12 < NA) or
PHC_42D = 1 or
(1 < ANCDELG < NA) or
(29.99 < HWMDBMI < NA)

Population exclusions NS
99.9 (SFM_15 = DK, RF, NS) and
(SFM_25 = DK, RF, NS) and
(SFM_35 = DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NA
  Calculate an average using the two skinfold measurements thatare different by 0.4 mm or less    

20. SFMDS5 - Sum of 5 SkinfoldMeasurements

Variable name:
SFMDS5

Based on:
PHC_11, PHC_12, PHC_42D, ANCDELG, HWMDBMI, SFMDBSA, SFMDICA,SFMDMCA, SFMDSSA, SFMDTSA

Description:
This variable indicates the sum of 5 average skinfoldsmeasurements:
Triceps
Biceps
Subscapular
Iliac Crest
Medial Calf

Note:
Created in the Clinic data collection application.

Skinfold measurements are used to estimate general fatness andthe distribution of subcutaneous adipose tissue. The principlebehind this technique is that the amount of subcutaneous fat (fatthat lies directly beneath the skin) is proportional to the totalamount of body fat.  Both too much fat and too little fat isassociated with increased health risk.

Table 20
SFMDS5 Specifications
Value Condition(s) Description Notes
999.6

PHC_11 = 1 or
(12 < PHC_12 < NA) or
PHC_42D = 1 or
(1 < ANCDELG < NA) or
(29.99 < HWMDBMI < NA)

Population exclusions NS
999.9 SFMDBSA = NS or
SFMDICA = NS or
SFMDMCA = NS or
SFMDSSA = NS or
SFMDTSA = NS
At least one required question was not answered (don’tknow, refusal, not stated) NA
SFMDBSA +
SFMDICA +
SFMDMCA +
SFMDSSA +
SFMDTSA
Else Sum of five average skinfold measurements  

21. SFMDS5A - Sum of 5 SkinfoldsMeasurements - Norms (ages 15-69)

Variable name:
SFMDS5A

Based on:
CLC_AGE, CLC_SEX, HWMDBMI, SFMDS5

Description:
These norms are intended to be used to calculate a Body CompositionScore which uses a combination of Body Mass Index, WaistCircumference, and Sum of Five Skinfolds as published by theCanadian Physical Activity, Fitness and Lifestyle Approach 3rdEdition.  This derived variable calculates the points assignedfor the Sum of Five Skinfolds which will contribute to the BodyComposition Score.

Note:
Created in the Clinic data collection application. This variableapplies to respondents 15 to 69 years of age.

Table 21
SFMDS5A Specifications
Value Condition(s) Description Notes
6 CLC_AGE < 15 or
CLC_AGE > 69 or
HWMDBMI = NA or
SFMDS5 = NA
Population exclusions NA
9 HWMDBMI = NS or
SFMDS5 = NS
At least one required question was not answered (don’tknow, refusal, not stated) NS
0 (CLC_SEX = 1 and
HWMDBMI > 34.99 and
SFMDS5 > 77.0) or
(CLC_SEX = 2 and
HWMDBMI > 34.99 and
SFMDS5 > 113.0)
Score of 0 Needs improvement
1 (CLC_SEX = 1 and
(32.49 < HWMDBMI < 35.00) and
(77.0 < SFMDS5 < NA)) or
(CLC_SEX = 2 and
(32.49 < HWMDBMI < 35.00) and
(113.0 < SFMDS5 < NA))
Score of 1 Fair
2 (CLC_SEX = 1 and
((0 < HWMDBMI < 32.50) and
(77.0 < SFMDS5 < NA)) or
((32.49 < HWMDBMI < 35.00) and
(53.9 < SFMDS5 < 77.1))) or
(CLC_SEX = 2 and
((0 < HWMDBMI < 32.50) and
(113.0 < SFMDS5 < NA)) or
((32.49 < HWMDBMI < 35.00) and
(82.9 < SFMDS5 < 113.1)))
Score of 2 Good
3 (CLC_SEX = 1 and
(0 < HWMDBMI < 18.50) and
((0 < SFMDS5 < 25.0) or
(55.0 < SFMDS5 < 77.1)) or
((18.49 < HWMDBMI < 32.50) and
(53.9 < SFMDS5 < 77.1))) or
(CLC_SEX = 2 and
(0 < HWMDBMI < 18.50) and
((0 < SFMDS5 < 46.0) or
(84.0 < SFMDS5 < 113.1)) or
((18.49 < HWMDBMI < 32.50) and
(82.9 < SFMDS5 < 113.1)))
Score of 3 Very good
4 (CLC_SEX  = 1 and
((0 < HWMDBMI < 18.50) and
(24.9 < SFMDS5 < 55.1)) or
((18.49 < HWMDBMI < NA) and
(0 < SFMDS5 < 54.0))) or
 (CLC_SEX  = 2 and
((0 < HWMDBMI < 18.50) and
(45.9 < SFMDS5 < 84.1)) or
((18.49 < HWMDBMI < NA) and
(0 < SFMDS5 < 83.0)))
Score of 4 Excellent

Reference: These norms are used along with BMI norms (HWMDBMI)and Waist Circumference norms (HWMDWSTA) to create the bodycomposition score (SFMDBCA).

22. SFMDSSA - Subscapular SkinfoldsAverage

Variable name:
SFMDSSA

Based on:
PHC_11, PHC_12, PHC_42D, ANCDELG, HWMDBMI, SFM_13, SFM_23,SFM_33

Description:
This variable indicates the average of the subscapular skinfoldmeasurements in millimetres.

Note:
Created in the Clinic data collection application.

This derived variable is created based on skinfold measurementsfrom appropriately selected respondents who had at least onemeasurement taken.  Two sets of measurements are preferred;however, if only one measurement was taken then the derivedvariable will equal the actual measurement.  If twomeasurements were taken and the difference between the twomeasurements was less than .5 mm then the derived variable will bethe average of the two measurements.  If the differencebetween the above-mentioned two measurements was greater than .4 mmthen a third measurement was taken.  If two of the threemeasurements were within .4 mm then those two measurements will beused to create the derived variable.  If all threemeasurements differ by more than .4 mm then the derived variablewill be the average of the three measurements.

Table 22
SFMDSSA Specifications
Value Condition(s) Description Notes
99.6 PHC_11 = 1 or
(12 < PHC_12 < NA) or
PHC_42D = 1 or
(1 < ANCDELG < NA) or
(29.99 < HWMDBMI < NA)
Population exclusions NA
99.9 (SFM_13 = DK, RF, NS) and
(SFM_23 = DK, RF, NS) and
(SFM_33 = DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NS
  Calculate an average using the two
skinfold measurements that are different by 0.4 mm or less
   

23. SFMDTSA - Triceps SkinfoldsAverage

Variable name:
SFMDTSA

Based on:
PHC_11, PHC_12, PHC_42D, ANCDELG, HWMDBMI, SFM_11, SFM_21,SFM_31

Description:
This variable indicates the average of the triceps skinfoldmeasurements in millimetres.

Note:
Created in the Clinic data collection application.

This derived variable is created based on skinfold measurementsfrom appropriately selected respondents who had at least onemeasurement taken.  Two sets of measurements are preferred;however, if only one measurement was taken then the derivedvariable will equal the actual measurement.  If twomeasurements were taken and the difference between the twomeasurements was less than .5 mm then the derived variable will bethe average of the two measurements.  If the differencebetween the above-mentioned two measurements was greater than .4 mmthen a third measurement was taken.  If two of the threemeasurements were within .4 mm then those two measurements will beused to create the derived variable.  If all threemeasurements differ by more than .4 mm then the derived variablewill be the average of the three measurements.

Table 23
SFMDTSA Specifications
Value Condition(s) Description Notes
99.6 PHC_11 = 1 or
(12 < PHC_12 < NA) or
PHC_42D = 1 or
(1 < ANCDELG < NA) or
(29.99 < HWMDBMI < NA)
Population exclusions NA
99.9 (SFM_11 = DK, RF, NS) and
(SFM_21 = DK, RF, NS) and
(SFM_31 = DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NS
  Calculate an average using the two
skinfold measurements that are different by 0.4 mm or less
   

Blood Pressure (20 DVs)

1. BPMD160 - Type of problem - firstset

Variable name:
BPMD160

Based on:
BPM_110, BPM_101A, BPM_111A,BPM_111B, BPM_112A, BPM_113A, BPM_113B, BPM_113C, BPM_113D,BPM_113E, BPM_121A, BPM_121B, BPM_122A, BPM_123A, BPM_123B,BPM_123C, BPM_123D, BPM_123E, BPM_131A, BPM_131B, BPM_132A,BPM_133A, BPM_133B, BPM_133C, BPM_133D, BPM_133E, BPM_141A,BPM_141B, BPM_142A, BPM_143A, BPM_143B, BPM_143C, BPM_143D,BPM_143E, BPM_151A, BPM_151B, BPM_152A, BPM_153A, BPM_153B,BPM_153C, BPM_153D, BPM_153E

Description:
This variable indicates the type of error that occurred for thefirst set of resting blood pressure and heart rate

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available onrequest.
The first measures of the set are dropped prior to deriving thisvariable.
The following is a description of the possible error types:

  1. Three or more measurement errors
  2. The range of systolic blood pressure measurements exceeds 30millimetres of Mercury (mmHg)
  3. The range of diastolic blood pressure measurements exceeds 20millimetres of Mercury (mmHg)
  4. The range of heart rate measurements exceeds 30 beats perminute (bpm)

2. BPMD161 - Average systolic bloodpressure - first set

Variable name:
BPMD161

Based on:
BPM_111A, BPM_111B, BPM_121A,BPM_121B, BPM_131A, BPM_131B, BPM_141A, BPM_141B, BPM_151A,BPM_151B, BPM_160

Description:
This variable indicates the average resting systolic blood pressurefor the first set of blood pressure measurements.
Blood pressure is measured in millimetres of Mercury (mmHg).

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available uponrequest.
The first measure of the set is dropped prior to deriving thisvariable.

3. BPMD162 - Average diastolic bloodpressure - first set

Variable name:
BPMD162

Based on:
BPM_111A, BPM_111B, BPM_121A, BPM_121B, BPM_131A, BPM_131B,BPM_141A, BPM_141B, BPM_151A, BPM_151B, BPM_160

Description:
This variable indicates the average resting diastolic bloodpressure for the first set of blood pressure measurements.
Blood pressure is measured in millimetres of Mercury (mmHg).

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available uponrequest.

The first measure of the set is dropped prior to deriving thisvariable.

4. BPMD163 - Average resting heart rate- first set

Variable name:
BPMD163

Based on:
BPM_112, BPM_122, BPM_132,BPM_142, BPM_152, BPM_160

Description:
This variable indicates the average resting heart rate for thefirst set of heart rate measurements. Heart rate is measured inbeats per minute (bpm).

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available uponrequest.
The first measure of the set is dropped prior to deriving thisvariable.

5. BPMD260 - Type of problem - secondset

Variable name:
BPMD260

Based on:
BPM_110, BPM_210, BPM_101A,BPM_111A, BPM_201A, BPM_211A, BPM_211B, BPM_212, BPM_213A,BPM_213B, BPM_213C, BPM_213D, BPM_213E, BPM_221A, BPM_221B,BPM_222, BPM_223A, BPM_223B, BPM_223C, BPM_223D, BPM_223E,BPM_231A, BPM_231B, BPM_232, BPM_233A, BPM_233B, BPM_233C,BPM_233D, BPM_233E, BPM_241A, BPM_241B, BPM_242, BPM_243A,BPM_243B, BPM_243C, BPM_243D, BPM_243E, BPM_251A, BPM_251B,BPM_252, BPM_253A, BPM_253B, BPM_253C, BPM_253D, BPM_253E

Description:
This variable indicates the type of error that occurred for thesecond set of resting blood pressure and heart rate
measurements.

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available uponrequest.
The first measures of the set are dropped prior to deriving thisvariable.
The following is a description of the possible error types:

  1. Three or more measurement errors
  2. The range of systolic blood pressure measurements exceeds 30millimetres of Mercury (mmHg)
  3. The range of diastolic blood pressure measurements exceeds 20millimetres of Mercury (mmHg)
  4. The range of heart rate measurements exceeds 30 beats perminute (bpm)

6. BPMD261 - Average systolic bloodpressure - second set

Variable name:
BPMD261

Based on:
BPM_211A, BPM_211B, BPM_221A,BPM_221B, BPM_231A, BPM_231B, BPM_241A, BPM_241B, BPM_251A,BPM_251B, BPM_260

Description:
This variable indicates the average resting systolic blood pressurefor the second set of blood pressure measurements. Blood pressureis measured in millimetres of Mercury (mmHg).

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available uponrequest.
The first measure of the set is dropped prior to deriving thisvariable.

7. BPMD262 - Average diastolic bloodpressure - second set

Variable name:
BPMD262

Based on:
BPM_211A, BPM_211B, BPM_221A,BPM_221B, BPM_231A, BPM_231B, BPM_241A, BPM_241B, BPM_251A,BPM_251B,BPM_260

Description:
This variable indicates the average resting diastolic bloodpressure for the second set of blood pressure measurements. Bloodpressure is measured in millimetres of Mercury (mmHg).

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available uponrequest.
 The first measure of the set is dropped prior to derivingthis variable.

8. BPMD263 - Average resting heart rate- second set

Variable name:
BPMD263

Based on:
BPM_212, BPM_222, BPM_232,BPM_242, BPM_252, BPM_260

Description:
This variable indicates the average resting heart rate for thesecond set of heart rate measurements. Heart rate is measured inbeats per minute (bpm).

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available uponrequest.
The first measure of the set is dropped prior to deriving thisvariable.

9. BPMD360 - Type of problem - thirdset

Variable name:
BPMD360

Based on:
BPM_110, BPM_210, BPM_310,BPM_101A, BPM_111A, BPM_201A, BPM_301A, BPM_311A, BPM_311B,BPM_312, BPM_313A, BPM_313B, BPM_313C, BPM_313D, BPM_313E, BPM_321A, BPM_321B,  BPM_322,  BPM_323A, BPM_323B,BPM_323C, BPM_323D, BPM_323E, BPM_331A, BPM_331B, BPM_332,BPM_333A, BPM_333B, BPM_333C, BPM_333D, BPM_333E, BPM_341A,BPM_341B, BPM_342, BPM_343A, BPM_343B, BPM_343C, BPM_343D,BPM_343E, BPM_351A, BPM_351B, BPM_352, BPM_353A, BPM_353B,BPM_353C, BPM_353D, BPM_353E, BPM_360

Description:
This variable indicates the type of error that occurred for thethird set of resting blood pressure and heart rate

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available uponrequest.
The first measures of the set are dropped prior to deriving thisvariable.
The following is a description of the possible error types:

  1. Three or more measurement errors
  2. The range of systolic blood pressure measurements exceeds 30millimetres of Mercury (mmHg)
  3. The range of diastolic blood pressure measurements exceeds 20millimetres of Mercury (mmHg)
  4. The range of heart rate measurements exceeds 30 beats perminute (bpm)

10. BPMD361 - Average systolic bloodpressure - third set

Variable name:
BPMD361

Based on:
BPM_311A, BPM_311B, BPM_321A,BPM_321B, BPM_331A, BPM_331B, BPM_341A, BPM_341B, BPM_351A,BPM_351B

Description:
This variable indicates the average resting systolic blood pressurefor the third set of blood pressure measurements.
Blood pressure is measured in millimetres of Mercury (mmHg).

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available uponrequest.

11. BPMD362 - Average diastolic bloodpressure - third set

Variable name:
BPMD362

Based on:
BPM_311A, BPM_311B, BPM_321A,BPM_321B, BPM_331A, BPM_331B, BPM_341A, BPM_341B, BPM_351A,BPM_351B

Description:
This variable indicates the average resting diastolic bloodpressure for the third set of blood pressure measurements. Blood pressure is measured in millimetres of Mercury (mmHg).

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available uponrequest.
The first measure of the set is dropped prior to deriving thisvariable.

12. BPMD363 - Average resting heart rate- third set

Variable name:
BPMD363

Based on:
BPM_312, BPM_322, BPM_332,BPM_342, BPM_352

Description:
This variable indicates the average resting heart rate for thethird set of heart rate measurements. Heart rate is measured inbeats per minute (bpm).

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available uponrequest.
 The first measure of the set is dropped prior to derivingthis variable.

13. BPMDBPA - Blood pressure norms forrespondents 18 or older (Prevalence)

Variable name:
BPMDBPA

Based on:
CLC_AGE, BPM_314, BPM_315

Description:
This variable indicates the blood pressure norm for respondentsmore than 17 years of age based on the average prevalence bloodpressure measurement.

Note:
Created during processing.
The SAS code used to derive this variable is available uponrequest.
The Canadian Coalition for High Blood Pressure Prevention andControl, 1994 provides the following description of
blood pressure norms:
Category 1 - Within the acceptable range
Category 2 - Acceptable, but at the high end of the acceptablerange
Category 3 - Above the acceptable range
Category 4 - Moderately high
Category 5 - High
Category 6 - Very high

14. BPMDBPK - Blood pressure norms forrespondents less than 18 (Prevalence)

Variable name:
BPMDBPK

Based on:
BPM_314, BPM_315, CLC_SEX,CLC_AGE, HWM_11

Description:
This variable indicates the blood pressure norms for respondentsless than 18 years of age based on the average prevalence bloodpressure measurement.

Note:
Created during processing.
The SAS code used to derive this variable is available uponrequest.
The Fourth Report on the Diagnosis, Evaluation, and Treatment ofHigh Blood Pressure in Children and Adolescents, 2004 provides thefollowing description of blood pressure norms:
Category 1 - Normal
Category 2 - Normal but at the high end of the normal range
Category 3 - High
Category 4 - Very high

15. BPMDPBPD - Final average diastolicblood pressure (Prevalence)

Variable name:
BPMDPBPD

Based on:
BPM_111A, BPM_111B, BPM_112,BPM_121A, BPM_121B, BPM_122, BPM_131A, BPM_131B, BPM_132, BPM_141A,BPM_141B, BPM_142, BPM_151A, BPM_151B, BPM_152, BPM_160, BPM_161,BPM_162, BPM_163, BPM_211A, BPM_211B, BPM_212, BPM_221A, BPM_221B,BPM_222, BPM_231A, BPM_231B, BPM_232, BPM_241A, BPM_241B, BPM_242,BPM_251A, BPM_251B, BPM_252, BPM_260, BPM_261 BPM_262 BPM_263,BPM_311A, BPM_311B, BPM_312, BPM_321A, BPM_321B, BPM_322, BPM_331A,BPM_331B, BPM_332, BPM_341A, BPM_341B, BPM_342, BPM_351A, BPM_351B,BPM_352, BPM_360, BPM_361 BPM_362, BPM_363

Description:
This variable indicates the average resting diastolic bloodpressure for the prevalence blood pressure measurement.
Blood pressure is measured in millimetres of Mercury (mmHg).

Note:
Created during processing.
The SAS code used to derive this variable is available uponrequest.
The first measure from each set is dropped prior to deriving thisvariable.

16. BPMDPBPS - Final average systolicblood pressure (Prevalence)

Variable name:
BPMDPBPS

Based on:
BPM_111A, BPM_111B, BPM_112,BPM_121A, BPM_121B, BPM_122, BPM_131A, BPM_131B, BPM_132, BPM_141A,BPM_141B, BPM_142, BPM_151A, BPM_151B, BPM_152, BPM_160, BPM_161,BPM_162, BPM_163, BPM_211A, BPM_211B, BPM_212, BPM_221A, BPM_221B,BPM_222, BPM_231A, BPM_231B, BPM_232, BPM_241A, BPM_241B, BPM_242,BPM_251A, BPM_251B, BPM_252, BPM_260, BPM_261 BPM_262 BPM_263,BPM_311A, BPM_311B, BPM_312, BPM_321A, BPM_321B, BPM_322, BPM_331A,BPM_331B, BPM_332, BPM_341A, BPM_341B, BPM_342, BPM_351A, BPM_351B,BPM_352, BPM_360, BPM_361 BPM_362, BPM_363

Description:
This variable indicates the average resting systolic blood pressurefor the prevalence blood pressure measurement.  Blood pressureis measured in millimetres of Mercury (mmHg).

Note:
Created during processing.
The SAS code used to derive this variable is available uponrequest.
The first measure from each set is dropped prior to deriving thisvariable.

17. BPMDPHR - Final average restingheart rate (Prevalence)

Variable name:
BPMDPHR

Based on:
BPM_111A, BPM_111B, BPM_112,BPM_121A, BPM_121B, BPM_122, BPM_131A, BPM_131B, BPM_132, BPM_141A,BPM_141B, BPM_142, BPM_151A, BPM_151B, BPM_152, BPM_160, BPM_161,BPM_162, BPM_163, BPM_211A, BPM_211B, BPM_212, BPM_221A, BPM_221B,BPM_222, BPM_231A, BPM_231B, BPM_232, BPM_241A, BPM_241B, BPM_242,BPM_251A, BPM_251B, BPM_252, BPM_260, BPM_261 BPM_262 BPM_263,BPM_311A, BPM_311B, BPM_312, BPM_321A, BPM_321B, BPM_322, BPM_331A,BPM_331B, BPM_332, BPM_341A, BPM_341B, BPM_342, BPM_351A, BPM_351B,BPM_352, BPM_360, BPM_361 BPM_362, BPM_363

Description:
This variable indicates the average resting heart rate for theprevalence heart rate measurement. Heart rate is measured in beatsper minute (bpm).

Note:
Created during processing.
The SAS code used to derive this variable is available uponrequest.
The first measure from each set is dropped prior to deriving thisvariable.

18. BPMDSBPD - Final average diastolicblood pressure (Screening)

Variable name:
BPMDSBPD

Based on:
BPM_160, BPM_161, BPM_162,BPM_163, BPM_260, BPM_261, BPM_262, BPM_263, BPM_311, BPM_312,BPM_313, BPM_360, BPM_361, BPM_D362, BPM_363

Description:
This variable indicates the average resting diastolic bloodpressure for the screening blood pressure measurement.  Bloodpressure is measured in millimetres of Mercury (mmHg).

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available uponrequest.
The first measure from each set is dropped prior to deriving thisvariable.

19. BPMDSBPS - Final average systolicblood pressure (Screening)

Variable name:
BPMDSBPS

Based on:
BPM_160, BPM_161, BPM_162,BPM_163, BPM_260, BPM_261, BPM_262, BPM_263, BPM_311, BPM_312,BPM_313, BPM_360, BPM_361, BPM_D362, BPM_363

Description:
This variable indicates the average resting systolic blood pressurefor the screening blood pressure measurement.   Bloodpressure is measured in millimetres of Mercury (mmHg).

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available uponrequest.
The first measure from each set is dropped prior to deriving thisvariable.

20. BPMDSHR - Final average restingheart rate (Screening)

Variable name:
BPMDSHR

Based on:
BPM_160, BPM_161, BPM_162,BPM_163, BPM_260, BPM_261, BPM_262, BPM_263, BPM_311, BPM_312,BPM_313, BPM_360, BPM_361, BPM_D362, BPM_363

Description:
This variable indicates the average resting heart rate for thescreening heart rate measurement. Heart rate is measured in beatsper minute (bpm).

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available uponrequest.
The first measure from each set is dropped prior to deriving thisvariable.

Breastfeeding information (1DV)

1. BRIFEB6 - Exclusively breastfed forat least 3 months

Variable name:
BRIFEB6

Based on:
DHH_AGE, BRI_11, BRI_12, BRI_13

Description:
This variable indicates whether the respondent was exclusivelybreastfed for at least 3 months.  Respondents greater than 11years of age were excluded from the population.

Table 1
BRIFEB6 Specifications
Value Condition(s) Description Notes
9 (BRI_11 = DK, RF, NS) or
(BRI_12 = DK, RF, NS) or
(BRI_13 = DK, RF, NS)
At least one required question was not answered (don’t know, refusal, not stated) NS
6 DHH_AGE > 11 Population exclusions NA
1 (BRI_13 = 6, 7) Respondent was exclusively breastfed for at least 3 months  
2 BRI_11 = 2 or
BRI_13 < 6
Respondent not exclusively breastfed for at least 3 months  

Chronic conditions (1 DV)

1) CCCF1 - Has a ChronicCondition

Variable name:
CCCF1

Based on:
CCC_11, CCC_21, CCC_22, CCC_24, CCC_31, CCC_34, CCC_41, CCC_43,CCC_45, CCC_51, CCC_61, CCC_71, CCC_81, CCC_82, CCC_83, CCC_84,CCC_91, CCC_92, CCC_93, CCC_95, CCC_101

Description:
This variable indicates whether the respondent has at least onechronic health condition which was diagnosed by a healthprofessional.

Introduced in:
CCHS - Cycle 1.1

Table 1
CCCF1 Specifications
Value Condition(s) Description Notes
9 (CCC_11 = DK, RF, NS) or
(CCC_21 = DK, RF, NS) or
(CCC_22 = DK, RF, NS) or
(CCC_24 = DK, RF, NS) or
(CCC_31 = DK, RF, NS) or
(CCC_34 = DK, RF, NS) or
(CCC_41 = DK, RF, NS) or
(CCC_43 = DK, RF, NS) or
(CCC_45 = DK, RF, NS) or
(CCC_51 = DK, RF, NS) or
(CCC_61 = DK, RF, NS) or
(CCC_71 = DK, RF, NS) or
(CCC_81 = DK, RF, NS) or
(CCC_82 = DK, RF, NS) or
(CCC_83 = DK, RF, NS) or
(CCC_84 = DK, RF, NS) or
(CCC_91 = DK, RF, NS) or
(CCC_92 = DK, RF, NS) or
(CCC_93 = DK, RF, NS) or
(CCC_95 = DK, RF, NS) or
(CCC_101 = DK, RF, NS)
At least one required question
was not answered
(don’t know, refusal, not stated)
NS
1 CCC_11 = 1 or
CCC_21 = 1 or
CCC_22 = 1 or
CCC_24 = 1 or
CCC_31 = 1 or
CCC_34 = 1 or
CCC_41 = 1 or
CCC_43 = 1 or
CCC_45 = 1 or
CCC_51 = 1 or
CCC_61 = 1 or
CCC_71 = 1 or
CCC_81 = 1 or
CCC_82 = 1 or
CCC_83 = 1 or
CCC_84 = 1 or
CCC_91 = 1 or
CCC_92 = 1 or
CCC_93 = 1 or
CCC_95 = 1 or
CCC_101 = 1
Has at least one chronic condition  
2 CCC_11 = 2 and
(CCC_21 = 2,NA) and
(CCC_22 = 2,NA) and
(CCC_24 = 2,NA) and
(CCC_31 = 2,NA) and
(CCC_34 = 2,NA) and
CCC_41 = 2 and
(CCC_43 = 2,NA) and
(CCC_45 = 2,NA) and
CCC_51 = 2 and
CCC_61 = 2 and
CCC_71 = 2 and
(CCC_81 = 2,NA) and
(CCC_82 = 2,NA) and
CCC_83 = 2 and
CCC_84 = 2 and
CCC_91 = 2 and
(CCC_92 = 2,NA) and
(CCC_93 = 2,NA) and
(CCC_95 = 2,NA) and
CCC_101 = 2
Has no chronic conditions  

Children's physical activity (2DVs)

Table
Children's physical activity Temporary Reformat

CPAT13
Value Condition(s) Description Notes
0 CPA_13 = 1 Recode to midpoint of response ranges  
1 CPA_13 = 2 Recode to midpoint of response ranges  
2.5 CPA_13 = 3 Recode to midpoint of response ranges  
5 CPA_13 = 4 Recode to midpoint of response ranges  
7 CPA_13 = 5 Recode to midpoint of response ranges  

 

CPAT14
Value Condition(s) Description Notes
0 CPA_14 = 1 Recode to midpoint of response ranges  
1 CPA_14 = 2 Recode to midpoint of response ranges  
2.5 CPA_14 = 3 Recode to midpoint of response ranges  
5 CPA_14 = 4 Recode to midpoint of response ranges  
7 CPA_14 = 5 Recode to midpoint of response ranges  

 

 

CPAT15
Value Condition(s) Description Notes
0 CPA_15 = 1 Recode to midpoint of response ranges  
1 CPA_15 = 2 Recode to midpoint of response ranges  
2.5 CPA_15 = 3 Recode to midpoint of response ranges  
5 CPA_15 = 4 Recode to midpoint of response ranges  
7 CPA_15 = 5 Recode to midpoint of response ranges  

 

 

CPAT16
Value Condition(s) Description Notes
0 CPA_16 = 1 Recode to midpoint of response ranges  
1 CPA_16 = 2 Recode to midpoint of response ranges  
2.5 CPA_16 = 3 Recode to midpoint of response ranges  
5 CPA_16 = 4 Recode to midpoint of response ranges  
7 CPA_16 = 5 Recode to midpoint of response ranges  

 

 

CPAT17
Value Condition(s) Description Notes
0 CPA_17 = 1 Recode to midpoint of response ranges  
0.5 CPA_17 = 2 Recode to midpoint of response ranges  
1.5 CPA_17 = 3 Recode to midpoint of response ranges  
3.5 CPA_17 = 4 Recode to midpoint of response ranges  
5.5 CPA_17 = 5 Recode to midpoint of response ranges  
7 CPA_17 = 6 Recode to midpoint of response ranges  

 

 

CPAT18
Value Condition(s) Description Notes
0 CPA_18 = 1 Recode to midpoint of response ranges  
0.5 CPA_18 = 2 Recode to midpoint of response ranges  
1.5 CPA_18 = 3 Recode to midpoint of response ranges  
3.5 CPA_18 = 4 Recode to midpoint of response ranges  
5.5 CPA_18 = 5 Recode to midpoint of response ranges  
7 CPA_18 = 6 Recode to midpoint of response ranges  

 

1. CPADSAC - Total number of hours perday spent in sedentary activities

Variable name:
CPADSAC

Based on:
CPA_17, CPA_18

Description:
This variable estimates the total number of hours per day the childparticipates in sedentary activities including watching TV orvideos, playing video games, and spending time on a computer playinggames, e-mailing, chatting and surfing the Internet.

Note:
This variable applies to children aged 6 to 11.

Table 1
CPADSAC Specifications
Value Condition(s) Description Notes
96 CPA_11 = NA Population exclusions NA
99 (CPA_17 = DK, RF, NS) or
(CPA_18 = DK, RF, NS)
At least one required question was
not answered (don’t know, refusal, not stated)
NS
CPAT17 +
CPAT18
(Round to nearest 0.5)
(0 <= CPAT17 <= 7) and
(0 <= CPAT18 <= 7)
Total number of hours per day
participated in sedentary activities
(e.g. watching TV, spending time on a computer)
(min: 0.0; max: 14.0)

2. CPADTOT - Total number of hours perweek participated in physical activities

Variable name:
CPADTOT

Based on:
CPA_13, CPA_14, CPA_15, CPA_16

Description:
This variable estimates the total number of hours per week thechild usually takes part in physical activities at school oroutside of school.

Note:
This variable applies to children aged 6 to 11.

Table 2
CPADTOT Specifications
Value Condition(s) Description Notes
96 CPA_11 = NA Population exclusions NA
99 (CPA_13 = DK, RF, NS) or
(CPA_14 = DK, RF, NS) or
(CPA_15 = DK, RF, NS) or
(CPA_16 = DK, RF, NS)
At least one required question was
not answered (don’t know, refusal, not stated)
NS
CPAT13 +
CPAT14 +
CPAT15 +
CPAT16
(Round to nearest
whole number)
(0 <= CPAT13 <= 7) and
(0 <= CPAT14 <= 7) and
(0 <= CPAT15 <= 7) and
(0 <= CPAT16 <= 7)
Total number of hours per week
participated in physical activities
(min: 0; max: 28)

Dietary fat consumption (2 DVs)

1. DFCD11Y - Eats regular-fat saladdressing - times per year

Variable name:
DFCD11Y

Based on:
DFC_11, DFC_11N

Description:
The number of times per year the respondent eats regular-fat saladdressing or mayonnaise.

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 1
DFCD11Y Specifications
Value Condition(s) Description Notes
0 DFC_11 = 0 Never  
DFC_11 * 365 DFC_11N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
DFC_11 * 52 DFC_11N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
DFC_11 * 12 DFC_11N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
DFC_11 DFC_11N = 4 Reported number of times consumed per year  
9996 DFC_11N = NA Population exclusions NA
9999 Else   NS

2. DFCD12Y - Eats regular-fat potatochips, tortilla chips or corn chips - times per year

Variable name:
DFCD12Y

Based on:
DFC_12, DFC_12N

Description:
The number of times per year the respondent eats regular-fat potatochips, tortilla chips or corn chips (excluding low fat chips andpretzels).

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 2
DFCD12Y Specifications
Value Condition(s) Description Notes
0 DFC_12 = 0 Never  
DFC_12 * 365 DFC_12N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
DFC_12 * 52 DFC_12N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
DFC_12 * 12 DFC_12N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
DFC_12 DFC_12N = 4 Reported number of times consumed per year  
9996 DFC_12N = NA Population exclusions NA
9999 Else   NS

Demographic and household variables (9DVs)

1. DHHD611 - Number of Persons inHousehold 6 to 11 Years of Age

Variable name:
DHHD611

Based on:
SAMPLEID, PERSONID, DHH_AGE

Description:
This variable indicates the number of people between 6 and 11 yearsold living within a household.

Introduced in:
CCHS - Cycle 1.1

Note:
This variable is derived by sorting the household roster dataset bySAMPLEID and PERSONID and by counting the number ofPERSONID’s that have a DHH_AGE value from 6 to 11 within eachSAMPLEID.

Table 1
DHHD611 Specifications
Value Condition(s) Description Notes
Total number of
PERSONID’s for
each SAMPLEID
(6 <= DHH_AGE <= 11)
(from Member file)
Number of persons 6 to 11 in a household  

2. DHHDDWE - Dwelling Type

Variable name:
DHHDDWE

Based on:
DHH_DW1, DHH_DW2

Description:
This variable indicates the type of dwelling the respondent livesin, according to the answer either given on the phone (DHH_DW1) orentered by observation (DHH_DW2).

Introduced in:
CCHS - Cycle 1.1

Table 2
DHHDDWE Specifications
Value Condition(s) Description Notes
99 (DHH_DW1 = DK, RF, NS) or
(DHH_DW2 = DK, RF, NS)
At least one required question was not
answered (don’t know, refusal, not stated)
NS
1 DHH_DW1 = 1 or
DHH_DW2 = 1
Single detached  
2 DHH_DW1 = 2 or
DHH_DW2 = 2
Double  
3 DHH_DW1 = 3 or
DHH_DW2 = 3
Row or terrace  
4 DHH_DW1 = 4 or
DHH_DW2 = 4
Duplex  
5 DHH_DW1 = 5 or
DHH_DW2 = 5
Low-rise apartment (< 5 stories) or flat  
6 DHH_DW1 = 6 or
DHH_DW2 = 6
High-rise apartment (5 stories or more)  
7 DHH_DW1 = 7 or
DHH_DW2 = 7
Institution  
8 DHH_DW1 = 8 or
DHH_DW2 = 8
Hotel/rooming house/camp  
9 DHH_DW1 = 9 or
DHH_DW2 = 9
Mobile home  
10 DHH_DW1 = 10 or
DHH_DW2 = 10
Other  

3. DHHDECF - Economic Family Status(Household Type)

Variable name:
DHHDECF

Based on:
DHH_REL for all PERSONID in SAMPLEID, DHH_AGE, DHH_SEX, DHHDHSZ

Description:
This variable identifies the family relationships within thehousehold.

Introduced in:
CCHS - Cycle 1.1

Note:
The necessary data is collected using a set of relationship codesthat define a link between each person in a household.  Allrelationships within each household (relationship of each person ina household to each other person within that household) are used increating this variable. The variable is based on the ages andreported relationships of each person to all others in thehousehold.

Table 3
DHHDECF Temporary Reformat

DHH_REL
Value Condition(s) Description Notes
X 10, 20 Temporary recodes to collapse relationships -Spouse (10 =Husband/Wife, 20 = Common Law Partner) Relationship Codes DVECF94
A 40, 41, 42, 43 Temporary recodes to collapse relationships - Parental Relationship Codes DVECF94
M 50, 51, 52, 53 (sorted by age) Temporary recodes to collapse relationships - Child (50 =Son/Daughter, 51 = Birth Child, 52 = Step Child, 53 = AdoptedChild) Relationship Codes DVECF94
L 60, 61, 62, 63, 64, 65*, 70*, 80*, 90, 100, 110, 111, 112, 113,114, 120, 121, 122, 123, 124, 260 Temporary recodes to collapse relationships -Other (60 =Brother/Sister, 61 = Full Sister/Brother, 62 = Half Sister/Brother,63 = Step Sister/Brother, 64 = Adopted Sister/Brother, 65 = FosterSister/Brother, 70 = Foster Parent, 80 = Foster Child, 90 =Grandparent, 100 = Grandchild, 110 = In-Law, 111 =Father/Mother-in-law, 112 = Son/Daughter-in-law, 113 =Brother/Sister-in-law, 114 = Other in-law, 120 = Other Related, 121= Uncle/Aunt, 122 = Cousin, 123 = Nephew/Niece, 124 = OtherRelative, 260 = Unrelated) Relationship Codes DVECF94 *All Foster relationships (fostersister/brother, parent, or child) have been recoded into the Otherrelationship category due to the temporary nature of therelationships
Y DHHDHSZ = 1 Temporary recodes to collapse relationships - Single Relationship Codes DVECF94
Z Else Temporary recodes to collapse relationships - Not stated Relationship Codes DVECF94

 

Table 3
DHHDECF Specifications
Value Condition(s) Description Notes
99 Any DHH_REL = Z Not Stated NS
1 DHHDHSZ = 1 Unattached individual living alone
Household size=1
 
2 All DHH_REL for all PERSONID in SAMPLEID in (L,Y) Unattached individuals living together
There cannot be a marital/common-law or parental relationship butother relationships such as siblings are allowed
 
3 DHHDHSZ = 2 and
DHH_REL for both PERSONID in SAMPLEID = X
Couple (married or common-law) with no dependent children
No other relationships are permitted
Household size=2
 
4 DHHDHSZ > 2 and
At least 2 PERSONID in SAMPLEID must have an
DHH_REL = X  and
DHH_REL for all PERSONID in SAMPLEID <> A and M
Couple (married or common-law) with no dependent children
There can be no parent/child relationships
Other relationships are permitted
 
5 DHHDHSZ > 2 and
At least 2 PERSONID in SAMPLEID must have an
DHH_REL = X and
At least one of which must have an DHH_REL = A.
All others PERSONID in SAMPLEID must have
DHH_REL = M and of these at least one is DHH_AGE < 25
Married or common-law couple with at least one partner beingthe parent of a dependent child (age < 25)
No other relationships are allowed
 
6 At least 2 PERSONID in SAMPLEID must have an
DHH_REL = X and
At least one of which must have an DHH_REL = A.
At least one other PERSONID in SAMPLEID must have DHH_REL = M withthe above PERSONID and of these at least one is DHH_AGE <25
Couple With Children < 25, Others
At least one partner must be the parent of one child < 25 yearsold in the household
Other relationships are allowed
 
7 DHHDHSZ > 2 and
At least 2 PERSONID in SAMPLEID must have an
DHH_REL = X and
At least one of which must have an DHH_REL = A.
All others PERSONID in SAMPLEID must have
DHH_REL = M and of these DHH_AGE >= 25
Married or common-law couple with all children >= 25 yearsold
No other relationships are permitted
 
8 DHHDHSZ > 2 and
At least 2 PERSONID in SAMPLEID must have an
DHH_REL = X and
At least one of which must have an DHH_REL = A.
At least one other PERSONID in SAMPLEID must have DHH_REL = M withthe above PERSONID and of these DHH_AGE >= 25
Married or common-law couple with all children >= 25 yearsold, Others
Any other relationships are allowed
 
9 DHHDHSZ > 1 and
One PERSONID in SAMPLEID must have DHH_REL = A and DHH_SEX = 2. Allothers PERSONID in SAMPLEID must have
DHH_REL = M and of these at least one DHH_AGE < 25
Female lone parent with children < 25
One child must be < 25 years old
No other relationships are permitted.
 
10 DHHDHSZ > 1 and
One PERSONID in SAMPLEID must have DHH_REL = A and DHHn_SEX =2.
At least one other PERSONID in SAMPLEID must have DHH_REL = M withthe above PERSONID and of these at least one DHH_AGE < 25
Female lone parent with children < 25, Others
One child must be < 25 years old
Other relationships are allowed
 
11 DHHDHSZ > 1 and
One PERSONID in SAMPLEID must have DHH_REL = A and DHHn_SEX =2.
All others PERSONID in SAMPLEID must have
DHH_REL = M and of these DHH_AGE >= 25
Female Lone Parent With All Children >= 25
All children must be >= 25 years old
No other relationships are permitted
 
12 DHHDHSZ > 1 and
One PERSONID in SAMPLEID must have DHH_REL = A and DHH_SEX = 2.
At least one other PERSONID in SAMPLEID must have DHH_REL = M withthe above PERSONID and of these DHH_AGE >= 25
Female Lone Parent With All Children >= 25, Others
All children must be >= 25 years old
Other relationships are allowed
 
13 DHHDHSZ > 1 and
One PERSONID in SAMPLEID must have DHH_REL = A and DHH_SEX = 1.
All others PERSONID in SAMPLEID must have
DHH_REL = M and of these at least one DHH_AGE < 25
Male Lone Parent With Children < 25
One child must be < 25 years old
No other relationships are permitted
 
14 DHHDHSZ > 1 and
One PERSONID in SAMPLEID must have DHH_REL = A and DHH_SEX = 1.
At least one other PERSONID in SAMPLEID must have DHH_REL = M withthe above PERSONID and of these at least one DHH_AGE < 25
Male Lone Parent With Children < 25, Others
One child must be < 25 years old
Other relationships are allowed
 
15 DHHDHSZ > 1 and
One PERSONID in SAMPLEID must have DHH_REL = A and DHH_SEX = 1.
All others PERSONID in SAMPLEID must have
DHH_REL = M and of these DHH_AGE >= 25
Male Lone Parent With All Children >= 25
All children must be >= 25 years old
No other relationships are permitted
 
16 DHHDHSZ > 1 and
One PERSONID in SAMPLEID must have DHH_REL = A and DHH_SEX = 1.
At least one other PERSONID in SAMPLEID must have DHH_REL = M withthe above PERSONID and of these DHH_AGE >= 25
Male Lone Parent With All Children >= 25, Others
All children must be >= 25 years old
Other relationships are allowed
 
17 Else Other Family Type
All other household types
 

4. DHHDHSZ - Household Size

Variable name:
DHHDHSZ

Based on:
Based on household roster, SAMPLEID, PERSONID

Description:
This variable indicates the number of people living within ahousehold.

Introduced in:
CCHS - Cycle 1.1

Note:
This variable is derived by sorting the household roster dataset bySAMPLEID and PERSONID and by counting the number ofPERSONID’s within each SAMPLEID.

Table 4
DHHDHSZ Specifications
Value Condition(s) Description Notes
Total number of
PERSONID’s for
each SAMPLEID
Sort the file (Member file)
by SAMPLEID and PERSONID
Number of persons in a household  

5. DHHDL12 - Number of Persons inHousehold Less Than 12 Years of Age

Variable name:
DHHDL12

Based on:
SAMPLEID, PERSONID, DHH_AGE

 Description:
This variable indicates the number of people less than 12 years oldliving within a household.

Introduced in:
CCHS - Cycle 1.1

Note:
This variable is derived by sorting the household roster dataset bySAMPLEID and PERSONID and by counting the number ofPERSONID’s that have a DHH_AGE value less than 12 within eachSAMPLEID.

Table 5
DHHDL12 Specifications
Value Condition(s) Description Notes
Total number of
PERSONID’s for
each SAMPLEID
DHH_AGE < 12
(from Member file)
Number of persons under 12 in a household  

6. DHHDLE5 - Number of Persons inHousehold Less Than 6 Years of Age

Variable name:
DHHDLE5

Based on:
SAMPLEID, PERSONID, DHH_AGE

Description:
This variable indicates the number of people living within ahousehold whose age is less than 6 years old.

Introduced in:
CCHS - Cycle 1.1

Note:
This variable is derived by sorting the household roster dataset bySAMPLEID and PERSONID and by counting the number ofPERSONID’s that have a DHH_AGE value less than 6 within eachSAMPLEID.

Table 6
DHHDLE5 Specifications
Value Condition(s) Description Notes
Total number of
PERSONID’s for
each SAMPLEID
DHH_AGE <= 5
(from Member file)
Number of persons under 6 in a household  

7. DHHDLVG - Living/ Family Arrangementof Selected Respondent

Variable name:
DHHDLVG

Based on:
DHH_REL of selected respondent, DHHDHSZ, DHH_AGE

Description:
This variable identifies the family relationships between theselected respondent and the rest of the household.

Introduced in:
CCHS - Cycle 1.1

Note:
The necessary data is collected using a set of relationship codesthat define a link between each person in a household.  Allrelationships with the selected respondent within each sample(relationship of selected respondent to each other person withinthe household) are used in creating this variable.

Table 7
DHHDLVG
Temporary Reformat

DHH_REL
Value Condition(s) Description Notes
Z1 NS Temporary recodes to collapse relationships - Not stated Relationship Codes
A1 40, 41, 42, 43 Temporary recodes to collapse relationships –Parental Relationship Codes
B1 50, 51, 52, 53 Temporary recodes to collapse relationships – Child Relationship Codes
C1 60, 61, 62, 63, 64 Temporary recodes to collapse relationships –Sibling Relationship Codes
K1 90, 100, 110, 111,
112, 113, 114, 120,
121, 122, 123, 124
Temporary recodes to collapse relationships - Otherrelative Relationship Codes
L1 65*, 70*, 80*, 260,
261, 262, 263
Temporary recodes to collapse relationships - Non-relative Relationship Codes *All
Foster relationships
(foster sister/brother, parent, or child)
have been recoded into the Other
relationship category due to the
temporary nature of the relationships.
X1 10, 20 Temporary recodes to collapse relationships -Spouse/Partner Relationship Codes

 

Table 7
DHHDLVG Specifications
Value Condition(s) Description Notes
99 Any DHH_REL = Z1 Not Stated NS
1 DHHDHSZ = 1 Unattached individual living alone
Household size=1
 
2 All DHH_REL <> X1 and A1 Unattached individual living with others
S/he cannot have a marital/common-law
or parental relationship but other relationships
such as siblings are allowed
 
3 DHHDHSZ = 2 and
DHH_REL = X1
Spouse/partner living with spouse/partner
Household size=2
 
4 DHHDHSZ > 2 and
One DHH_REL = X1 and
all other DHH_REL = A1
Parent living with spouse/partner and children  
5 All DHH_REL = A1 Single parent living with children
No other relationships are permitted
 
6 DHHDHSZ = 2 and
DHH_REL = B1
Child living with single parent
Household size=2
 
7 DHHDHSZ > 2 and
One DHH_REL = B1 and
all other DHH_ REL = C1
Child living with single parent and siblings  
8 DHHDHSZ = 3 and
All DHH_REL = B1
Child living with two parents
Household size=3
 
9 DHHDHSZ > 3 and
Two DHH_REL = B1 and all other DHH_REL = C1
Child living with two parents and siblings  
10 Else Other
Lives in a household composition not classified above
 
Total number
of PERSONID’s
with each SAMPLEID
DHH_AGE = 16, 17 (Member file) and
RELATIONSHIP = 51, 52, 53, 80, 100, 112, 123 (Relation files)
Number of persons aged 16 or 17 in a household
whose relationship with at least one adult of the
household is child, grandchild, child-in-law or, niece ornephew
(min: 0; max: 40)

 

8. DHHDOKD - Number of Persons inHousehold 16 or 17 Years of Age

Variable name:
DHHDOKD

Based on:
PERSONID, DHH_AGE, RELATIONSHIP

Description:
This variable indicates the number of people living within ahousehold whose age is 16 or 17 years old and whose relationship toat least one adult living within the household is child,grandchild, child-in-law, niece or nephew.

Introduced in:
CCHS - Cycle 3.1

Note:
This variable is derived by sorting the household roster dataset bySAMPLEID and PERSONID and by counting the number ofPERSONID’s that have a DHH_AGE value of 16 or 17 and whoseRELATIONSHIP value of (51, 52, 53, 80, 100, 112 or 123) within eachSAMPLEID.

Table 8
DHHDOKD Specifications
Value Condition(s) Description Notes
Total number
of
PERSONID’s
with each
SAMPLEID
DHH_AGE = 16, 17 (Member file) and
RELATIONSHIP = 51, 52, 53, 80, 100,
112, 123 (Relation files)
Number of persons aged 16 or 17
in a household whose relationship
with at least one adult of the household
is child, grandchild, child-in-law, or niece or nephew
(min: 0; max: 40)

9. DHHDYKD - Number of Persons inHousehold Less Than 16 Years of Age

Variable name:
DHHDYKD

Based on:
SAMPLEID, PERSONID, DHH_AGE

Description:
This variable indicates the number of people living within ahousehold whose age is less than 16 years old.

Introduced in:
CCHS - Cycle 3.1

Note:
This variable is derived by sorting the household roster dataset bySAMPLEID and PERSONID and by counting the number ofPERSONID’s that have a DHH_AGE value of less than 16 withineach SAMPLEID.

Table 9
DHHDYKD Specifications
Value Condition(s) Description Notes
Total number
of
PERSONID’s
for each
SAMPLEID
DHH_AGE <= 15 (from Member file) Number of persons under 16 in a household  

Education (4 DVs)

1. EDUDH04 - Highest Level ofEducation - Household, 4 Levels

Variable name:
EDUDH04

Based on:
EDUDR04 for each member of the household

Description:
This variable indicates the highest level of education acquired byany member of the household.

Introduced in:
CCHS - Cycle 1.1

Note:
This variable is derived by temporarily creating EDUDR04 for allmembers of the household (all PERSONIDs within SAMPLEID), then bycomparing the values of EDUDR04 within the household and returningthe highest value.  If EDUDR04 for any household member is NS(not stated), then NS is returned.  If EDUDR04 for allhousehold members is NA (not applicable), then NA is returned.

2. EDUDH10 - Highest Level of Education- Household, 10 Levels

Variable name:
EDUDH10

Based on:
EDUDR10 for each member of the household

Description:
This variable indicates the highest level of education acquired byany member of the household.

Introduced in:
CCHS - Cycle 1.1

Note:
This variable is derived by temporarily creating EDUDR10 for allmembers of the household (all PERSONIDs within SAMPLEID), then bycomparing the values of EDUDR10 within the household and returningthe highest value.  If EDUDR10 for any household member is NS(not stated), then NS is returned.  If EDUDR10 for allhousehold members is NA (not applicable), then NA is returned.

3. EDUDR04 - Highest Level of Education- Household, 4 Levels

Variable name:
EDUDR04

Based on:
DHH_ED1, DHH_ED2, DHH_ED3, DHH_ED4

Description:
This variable indicates the highest level of education acquired byeach member of the household.

Introduced in:
CCHS - Cycle 1.1

Table 3
EDUDR04 Specifications
Value Condition(s) Description Notes
9 (DHH_ED2 = DK, RF, NS) or
(DHH_ED3 = DK, RF, NS) or
(DHH_ED4 = DK, RF, NS)
At least one required question
was not answered (don’t know, refusal, not stated)
NS
1 ((DHH_ED1 = 1, 2) or
DHH_ED2 = 2) and
DHH_ED3 = 2
Less than secondary school graduation  
2 DHH_ED2 = 1 and
DHH_ED3 = 2
Secondary school graduation,
no post-secondary education
 
3 DHH_ED4 = 1 Some post-secondary education  
4 (2 <= DHH_ED4 <= 6) Post-secondary degree/diploma  

4. EDUDR10 - Highest Level of Education- Household, 10 Levels

Variable name:
EDUDR10

Based on:
DHH_ED1, DHH_ED2, DHH_ED3, DHH_ED4

Description:
This variable indicates the highest level of education acquired byeach member of the household.

Introduced in:
CCHS - Cycle 1.1

Table 4
EDUDR10 Specifications
Value Condition(s) Description Notes
99 ((DHH_ED1 = DK, RF, NS)
and DHH_ED2 = 2) or
(DHH_ED2 = DK, RF, NS)
or (DHH_ED3 = DK, RF, NS)
or (DHH_ED4 = DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NS
1 DHH_ED1 = 1 and
DHH_ED3 = 2
Grade 8 or lower (Québec: Secondary II or lower)  
2 DHH_ED1 = 2 and
DHH_ED3 = 2
Grade 9-10 (Québec: Secondary III or IV; Newfoundland& Labrador: 1st year of secondary)  
3 DHH_ED1 = 3 and
DHH_ED2 = 2 and
DHH_ED3 = 2
Grade 11-13 (Québec: Secondary V; Newfoundland &Labrador: 2nd to 4th year of secondary)  
4 DHH_ED2 = 1 and
DHH_ED3 = 2
Secondary school graduate, no post-secondary education  
5 DHH_ED4 = 1 Some post secondary education  
6 DHH_ED4 = 2 Trade certificate or diploma from a vocational school orapprenticeship training  
7 DHH_ED4 = 3 Non-university certificate or diploma from a community college,CEGEP, school of nursing, etc.  
8 DHH_ED4 = 4 University certificate below bachelor’s level  
9 DHH_ED4 = 5 Bachelor’s degree  
10 DHH_ED4 = 6 University degree or certificate above bachelor’sdegree  

General health (2 DVs)

1. GENDHDI - Self-Rated Health(Formerly Health Description Index)

Variable name:
GENDHDI

Based on:
GEN_11

Description:
This variable indicates the respondent’s health status basedon his/her own judgement.

Introduced in:
NPHS - Cycle 1

Note:
Higher values indicate positive self-reported health status.

Table 1
GENDHDI Specifications
Value Condition(s) Description Notes
9 (GEN_11 = DK, RF, NS) At least one required question was not answered (don’tknow, refusal, not stated) NS
0 GEN_11 = 5 Poor  
1 GEN_11 = 4 Fair  
2 GEN_11 = 3 Good  
3 GEN_11 = 2 Very good  
4 GEN_11 = 1 Excellent  

2. GENDMHI - Self-Rated MentalHealth

Variable name:
GENDMHI

Based on:
GEN_14

Description:
This variable indicates the respondent’s mental health statusbased on his/her own judgement.

Introduced in:
CCHS - Cycle 1.2

Note:
Higher values indicate positive self-reported mental health status.

Table 2
GENDMHI Specifications
Value Condition(s) Description Notes
9 (GEN_14 = DK, RF, NS) At least one required question was not answered (don’tknow, refusal, not stated) NS
0 GEN_14 = 5 Poor  
1 GEN_14 = 4 Fair  
2 GEN_14 = 3 Good  
3 GEN_14 = 2 Very good  
4 GEN_14 = 1 Excellent  

Grains, fruits and vegetablesconsumption (13 DVs)

1. GFVD11Y - Eats hot or cold cereal -times per year

Variable name:
GFVD11Y

Based on:
GFV_11, GFV_11N

Description:
The number of times per year the respondent eats hot or coldcereal.

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 1
GFVD11Y Specifications
Value Condition(s) Description Notes
0 GFV_11 = 0 Never  
GFV_11 * 365 GFV_11N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
GFV_11 * 52 GFV_11N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
GFV_11 * 12 GFV_11N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
GFV_11 GFV_11N = 4 Reported number of times consumed per year  
9996 GFV_11N = NA Population exclusions NA
9999 Else   NS

2. GFVD12Y - Eats brown bread, includingbagels, rolls, pita bread or tortillas - times per year

Variable name:
GFVD12Y

Based on:
GFV_12, GFV_12N

Description:
The number of times per year the respondent eats brown bread(including bagels, rolls, pita bread or tortillas).

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 2
GFVD12Y Specifications
Value Condition(s) Description Notes
0 GFV_12 = 0 Never  
GFV_12 * 365 GFV_12N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
GFV_12 * 52 GFV_12N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
GFV_12 * 12 GFV_12N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
GFV_12 GFV_12N = 4 Reported number of times consumed per year  
9996 GFV_12N = NA Population exclusions NA
9999 Else   NS

3. GFVD13Y - Eats white bread, includingbagels, rolls, pita bread or tortillas - times per year

Variable name:
GFVD13Y

Based on:
GFV_13, GFV_13N

Description:
The number of times per year the respondent eats white bread(including bagels, rolls, pita bread or tortillas).

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 3
GFVD13Y Specifications
Value Condition(s) Description Notes
0 GFV_13 = 0 Never  
GFV_13 * 365 GFV_13N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
GFV_13 * 52 GFV_13N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
GFV_13 * 12 GFV_13N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
GFV_13 GFV_13N = 4 Reported number of times consumed per year  
9996 GFV_13N = NA Population exclusions NA
9999 Else   NS

4. GFVD14Y - Eats any kind of pasta -times per year

Variable name:
GFVD14Y

Based on:
GFV_14, GFV_14N

Description:
The number of times per year the respondent eats any kind of pasta(including spaghetti, noodles, macaroni and cheese or pastasalad).

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 4
GFVD14Y Specifications
Value Condition(s) Description Notes
0 GFV_14 = 0 Never  
GFV_14 * 365 GFV_14N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
GFV_14 * 52 GFV_14N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
GFV_14 * 12 GFV_14N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
GFV_14 GFV_14N = 4 Reported number of times consumed per year  
9996 GFV_14N = NA Population exclusions NA
9999 Else   NS

5. GFVD15Y - Eats any kind of rice -times per year

Variable name:
GFVD15Y

Based on:
GFV_15, GFV_15N

Description:
The number of times per year the respondent eats any kind ofrice.

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 5
GFVD15Y Specifications
Value Condition(s) Description Notes
0 GFV_15 = 0 Never  
GFV_15 * 365 GFV_15N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
GFV_15 * 52 GFV_15N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
GFV_15 * 12 GFV_15N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
GFV_15 GFV_15N = 4 Reported number of times consumed per year  
9996 GFV_15N = NA Population exclusions NA
9999 Else   NS

6. GFVD16Y - Eats instant, seasoned orwild rice - times per year

Variable name:
GFVD16Y

Based on:
GFV_16, GFV_16N

Description:
The number of times per year the respondent who eats rice eatsinstant, seasoned or wild rice (including Minute Rice®,Dainty®, Rice-a-Roni®).

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 6
GFVD16Y Specifications
Value Condition(s) Description Notes
0 GFV_16 = 0 Never  
GFV_16 * 365 GFV_16N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
GFV_16 * 52 GFV_16N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
GFV_16 * 12 GFV_16N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
GFV_16 GFV_16N = 4 Reported number of times consumed per year  
9996 GFV_16N = NA Population exclusions NA
9999 Else   NS

7. GFVD17Y - Eats fruit - times peryear

Variable name:
GFVD17Y

Based on:
GFV_17, GFV_17N

Description:
The number of times per year the respondent eats fruit (fresh,frozen, canned).

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 7
GFVD17Y Specifications
Value Condition(s) Description Notes
0 GFV_17 = 0 Never  
GFV_17 * 365 GFV_17N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
GFV_17 * 52 GFV_17N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
GFV_17 * 12 GFV_17N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
GFV_17 GFV_17N = 4 Reported number of times consumed per year  
9996 GFV_17N = NA Population exclusions NA
9999 Else   NS

8. GFVD18Y - Eats tomatoes or tomatosauce - times per year

Variable name:
GFVD18Y

Based on:
GFV_18, GFV_18N

Description:
The number of times per year the respondent eats tomatoes or tomatosauce (including salsa, tomato soup and spaghetti sauce butexcluding tomato paste, ketchup or pizza sauce).

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 8
GFVD18Y Specifications
Value Condition(s) Description Notes
0 GFV_18 = 0 Never  
GFV_18 * 365 GFV_18N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
GFV_18 * 52 GFV_18N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
GFV_18 * 12 GFV_18N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
GFV_18 GFV_18N = 4 Reported number of times consumed per year  
9996 GFV_18N = NA Population exclusions NA
9999 Else   NS

9. GFVD19Y - Eats lettuce or green leafysalad - times per year

Variable name:
GFVD19Y

Based on:
GFV_19, GFV_19N

Description:
The number of times per year the respondent eats lettuce or greenleafy salad with or without other vegetables.

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 9
GFVD19Y Specifications
Value Condition(s) Description Notes
0 GFV_19 = 0 Never  
GFV_19 * 365 GFV_19N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
GFV_19 * 52 GFV_19N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
GFV_19 * 12 GFV_19N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
GFV_19 GFV_19N = 4 Reported number of times consumed per year  
9996 GFV_19N = NA Population exclusions NA
9999 Else   NS

10. GFVD20Y - Eats spinach, mustardgreens or collards - times per year

Variable name:
GFVD20Y

Based on:
GFV_20, GFV_20N

Description:
The number of times per year the respondent eats spinach, mustardgreens or collards excluding kale.

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 10
GFVD20Y Specifications
Value Condition(s) Description Notes
0 GFV_20 = 0 Never  
GFV_20 * 365 GFV_20N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
GFV_20 * 52 GFV_20N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
GFV_20 * 12 GFV_20N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
GFV_20 GFV_20N = 4 Reported number of times consumed per year  
9996 GFV_20N = NA Population exclusions NA
9999 Else   NS

11. GFVD21Y - Eats french fries, homefries or hash brown potatoes - times per year

Variable name:
GFVD21Y

Based on:
GFV_21, GFV_21N

Description:
The number of times per year the respondent eats french fries, homefries or hash brown potatoes.

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 11
GFVD21Y Specifications
Value Condition(s) Description Notes
0 GFV_21 = 0 Never  
GFV_21 * 365 GFV_21N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
GFV_21 * 52 GFV_21N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
GFV_21 * 12 GFV_21N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
GFV_21 GFV_21N = 4 Reported number of times consumed per year  
9996 GFV_21N = NA Population exclusions NA
9999 Else   NS

12. GFVD22Y - Eats other potatoes -times per year

Variable name:
GFVD22Y

 Based on:
GFV_22, GFV_22N

Description:
The number of times per year the respondent eats other potatoes(including baked, boiled, mashed or in potato salad, but excludingsweet potatoes).

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 12
GFVD22Y Specifications
Value Condition(s) Description Notes
0 GFV_22 = 0 Never  
GFV_22 * 365 GFV_22N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
GFV_22 * 52 GFV_22N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
GFV_22 * 12 GFV_22N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
GFV_22 GFV_22N = 4 Reported number of times consumed per year  
9996 GFV_22N = NA Population exclusions NA
9999 Else   NS

13. GFVD23Y - Eats all other types ofvegetables - times per year

Variable name:
GFVD23Y

Based on:
GFV_23, GFV_23N

Description:
The number of times per year the respondent eats all other types ofvegetables.

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 13
GFVD23Y Specifications
Value Condition(s) Description Notes
0 GFV_23 = 0 Never  
GFV_23 * 365 GFV_23N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
GFV_23 * 52 GFV_23N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
GFV_23 * 12 GFV_23N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
GFV_23 GFV_23N = 4 Reported number of times consumed per year  
9996 GFV_23N = NA Population exclusions NA
9999 Else   NS

Grooming product use (7 DVs)

1. GPUD12Y - Uses fragrance - timesper year

Variable name:
GPUD12Y

Based on:
GPU_12, GPU_12N

Description:
The number of times per year the respondent uses fragrance(including perfumes, cologne and aftershave).

Note:
Created in the Household Post-Verify process.

Table 1
GPUD12Y Specifications
Value Condition(s) Description Notes
0 GPU_12 = 0 Never  
GPU_12 * 365 GPU_12N = 1 Reported number of times used per day converted to derivednumber of times used per year  
GPU_12 * 52 GPU_12N = 2 Reported number of times used per week converted to derivednumber of times used per year  
GPU_12 * 12 GPU_12N = 3 Reported number of times used per month converted to derivednumber of times used per year  
GPU_12 GPU_12N = 4 Reported number of times used per year  
9996 GPU_12N = NA Population exclusions NA
9999 Else   NS

2. GPUD13Y - Uses eye make-up - timesper year

Variable name:
GPUD13Y

Based on:
GPU_13, GPU_13N

Description:
The number of times per year the respondent uses eye make-up.

Note:
Created in the Household Post-Verify process.

Table 2
GPUD13Y Specifications
Value Condition(s) Description Notes
0 GPU_13 = 0 Never  
GPU_13 * 365 GPU_13N = 1 Reported number of times used per day converted to derivednumber of times used per year  
GPU_13 * 52 GPU_13N = 2 Reported number of times used per week converted to derivednumber of times used per year  
GPU_13 * 12 GPU_13N = 3 Reported number of times used per month converted to derivednumber of times used per year  
GPU_13 GPU_13N = 4 Reported number of times used per year  
9996 GPU_13N = NA Population exclusions NA
9999 Else   NS

3. GPUD14Y - Uses lipstick - times peryear

Variable name:
GPUD14Y

Based on:
GPU_14, GPU_14N

Description:
The number of times per year the respondent uses lipstick(including lip gloss).

Note:
Created in the Household Post-Verify process.

Table 3
GPUD14Y Specifications
Value Condition(s) Description Notes
0 GPU_14 = 0 Never  
GPU_14 * 365 GPU_14N = 1 Reported number of times used per day converted to derivednumber of times used per year  
GPU_14 * 52 GPU_14N = 2 Reported number of times used per week converted to derivednumber of times used per year  
GPU_14 * 12 GPU_14N = 3 Reported number of times used per month converted to derivednumber of times used per year  
GPU_14 GPU_14N = 4 Reported number of times used per year  
9996 GPU_14N = NA Population exclusions NA
9999 Else   NS

4. GPUD15Y - Uses hair dye - times peryear

Variable name:
GPUD15Y

Based on:
GPU_15, GPU_15N

Description:
The number of times per year the respondent uses hair dye.

Note:
Created in the Household Post-Verify process.

Table 4
GPUD15Y Specifications
Value Condition(s) Description Notes
0 GPU_15 = 0 Never  
GPU_15 * 365 GPU_15N = 1 Reported number of times used per day converted to derivednumber of times used per year  
GPU_15 * 52 GPU_15N = 2 Reported number of times used per week converted to derivednumber of times used per year  
GPU_15 * 12 GPU_15N = 3 Reported number of times used per month converted to derivednumber of times used per year  
GPU_15 GPU_15N = 4 Reported number of times used per year  
9996 GPU_15N = NA Population exclusions NA
9999 Else   NS

5. GPUD16Y - Uses hair style products -times per year

Variable name:
GPUD16Y

Based on:
GPU_16, GPU_16N

Description:
The number of times per year the respondent uses hair styleproducts.

Note:
Created in the Household Post-Verify process.

Table 5
GPUD16Y Specifications
Value Condition(s) Description Notes
0 GPU_16 = 0 Never  
GPU_16 * 365 GPU_16N = 1 Reported number of times used per day converted to derivednumber of times used per year  
GPU_16 * 52 GPU_16N = 2 Reported number of times used per week converted to derivednumber of times used per year  
GPU_16 * 12 GPU_16N = 3 Reported number of times used per month converted to derivednumber of times used per year  
GPU_16 GPU_16N = 4 Reported number of times used per year  
9996 GPU_16N = NA Population exclusions NA
9999 Else   NS

6. GPUD17Y - Uses manicure preparations- times per year

Variable name:
GPUD17Y

Based on:
GPU_17, GPU_17N

Description:
The number of times per year the respondent uses manicurepreparations.

Note:
Created in the Household Post-Verify process.

Table 6
GPUD17Y Specifications
Value Condition(s) Description Notes
0 GPU_17 = 0 Never  
GPU_17 * 365 GPU_17N = 1 Reported number of times used per day converted to derivednumber of times used per year  
GPU_17 * 52 GPU_17N = 2 Reported number of times used per week converted to derivednumber of times used per year  
GPU_17 * 12 GPU_17N = 3 Reported number of times used per month converted to derivednumber of times used per year  
GPU_17 GPU_17N = 4 Reported number of times used per year  
9996 GPU_17N = NA Population exclusions NA
9999 Else   NS

7. GPUD18Y - Uses scented body products- times per year

Variable name:
GPUD18Y

Based on:
GPU_18, GPU_18N

Description:
The number of times per year the respondent uses scented bodyproducts (including lotion, cream and body wash).

Note:
Created in the Household Post-Verify process.

Table 7
GPUD18Y Specifications
Value Condition(s) Description Notes
0 GPU_18 = 0 Never  
GPU_18 * 365 GPU_18N = 1 Reported number of times used per day converted to derivednumber of times used per year  
GPU_18 * 52 GPU_18N = 2 Reported number of times used per week converted to derivednumber of times used per year  
GPU_18 * 12 GPU_18N = 3 Reported number of times used per month converted to derivednumber of times used per year  
GPU_18 GPU_18N = 4 Reported number of times used per year  
9996 GPU_18N = NA Population exclusions NA
9999 Else   NS

Grip Strength (4 DVs)

1. GSCDELG - Eligibility - GripStrength component

Variable name:
GSCDELG

Based on:
ATG_33A, PHC_42H, MHR_611C, PAR_5A3B, PAR_5B3B, PAR_5C3B, PAR_5D3B,PAR_5E3B, PAR_5F3B, PAR_5G3B, PAR_5H3B, PAR_5I3B, PAR_5J3B,PAR_5K3B, PAR_62E, PAR_72B, ORS_1

Description:
This variable indicates whether the respondent was eligible for theGrip Strength Component. As there are multiple reasons to bescreened out of this measure, the prevalence of screen outs byreason should not be based on frequency counts for thisvariable.

Note:
Created in the Clinic Post-Verify process.

Table 1
GSCDELG Specifications
Value Condition(s) Description Notes
5 ATG_33A = 1 Not eligible - drank alcohol too close to visit time  
9 PHC_42H = 1 Not eligible - acute or chronic condition  
12 MHR_611C = 1 Not eligible - medication use  
13 PAR_5A3B = 1 or
PAR_5B3B = 1 or
PAR_5C3B = 1 or
PAR_5D3B = 1 or
PAR_5E3B = 1 or
PAR_5F3B = 1 or
PAR_5G3B = 1 or
PAR_5H3B = 1 or
PAR_5I3B = 1 or
PAR_5J3B = 1 or
PAR_5K3B = 1 or
PAR_62E = 1 or
PAR_72B = 1
Not eligible - PAR-Q answer  
14 ORS_1 = 1 Not eligible - other reason  
1 Else Eligible  

2. GSMD51 - Total hand gripstrength

Variable name:
GSMD51

Based on:
GSCDELG, GSM_11, GSM_12, GSM_21, GSM_22

Description:
This variable indicates the respondent’s total hand gripstrength.

Note:
Created in the Clinic data collection application

Table 2
GSMD51 Specifications
Value Condition(s) Description Notes
999 (GSM_11 > NA and
GSM_21 > NA) or
(GSM_12 > NA and
GSM_22 > NA)
At least one required question was not answered (don’tknow, refusal, not stated) NS
996 (1 < GSCDELG < NA) Population exclusions NA
GSM_21 +
GSM_22
((0 < GSM_11 < NA) and
(0 < GSM_21 < NA) and
(0 < GSM_12 < NA) and
(0 < GSM_22 < NA) and
(GSM_11 < GSM_21) and
(GSM_12 < GSM_22)) or
((0 < GSM_11 < NA) and
(0 < GSM_21 < NA) and
(GSM_12 >= NA) and
(0 < GSM_22 < NA) and
(GSM_11 < GSM_21)) or
((GSM_11 >= NA) and
(0 < GSM_21 < NA) and
(0 < GSM_12 < NA) and
(0 < GSM_22 < NA) and
(GSM_12 < GSM_22)) or
((GSM_11 >= NA) and
(0 < GSM_21 < NA) and
(GSM_12 >= NA) and
(0 < GSM_22 < NA))
Second grip strength measurement for the right hand and theleft hand  
GSM_21 +
GSM_12
((0 < GSM_11 < NA) and
(0 < GSM_21 < NA) and
(0 < GSM_12 < NA) and
(0 < GSM_22 < NA) and
(GSM_11 < GSM_21) and
(GSM_12 >= GSM_22)) or
((0 < GSM_11 < NA) and
(0 < GSM_21 < NA) and
(0 < GSM_12 < NA) and
(GSM_22 >= NA) and
(GSM_11 < GSM_21)) or
((GSM_11 >= NA) and
(0 < GSM_21 < NA) and
(0 < GSM_12 < NA) and
(0 < GSM_22 < NA) and
(GSM_12 >= GSM_22)) or
((GSM_11 >= 996) and
(0 < GSM_21 < 996) and
(0 < GSM_12 < 996) and
(GSM_22 >= 996))
Second grip strength measurement for the right hand and firstgrip strength measurement for the left hand  
GSM_11 +
GSM_22
((0 < GSM_11 < NA) and
(0 < GSM_21 < NA) and
(0 < GSM_12 < NA) and
(0 < GSM_22 < NA) and
(GSM_11 >= GSM_21) and
(GSM_12 < GSM_22)) or
((0 < GSM_11 < NA) and
(0 < GSM_21 < NA) and
(GSM_12 >= NA) and
(0 < GSM_22 < NA) and
(GSM_11 >= GSM_21)) or
((0 < GSM_11 < NA) and
(GSM_21 >= NA) and
(0 < GSM_12 < NA) and
(0 < GSM_22 < NA) and
(GSM_12 < GSM_22)) or
((0 < GSM_11 < NA) and
(GSM_21 >= NA) and
(GSM_12 >= NA) and
(0 < GSM_22 < NA))
First grip strength measurement for the right hand and secondgrip strength measurement for the left hand  
GSM_11 +
GSM_12
((0 < GSM_11 < NA) and
(0 < GSM_21 < NA) and
(0 < GSM_12 < NA) and
(0 < GSM_22 < NA) and
(GSM_11 >= GSM_21) and
(GSM_12 >= GSM_22)) or
((0 < GSM_11 < NA) and
(0 < GSM_21 < NA) and
(0 < GSM_12 < NA) and
(GSM_22 >= NA) and
(GSM_11 >= GSM_21)) or
((0 < GSM_11 < NA) and
(GSM_21 >= NA) and
(0 < GSM_12 < NA) and
(0 < GSM_22 < NA) and
(GSM_12 >= GSM_22)) or
((0 < GSM_11 < NA) and
(GSM_21 >= NA) and
(0 < GSM_12 < NA) and
(GSM_22 >= NA))
First grip strength measurement for the right hand and the lefthand  

3. GSMD52 - Grip strength norms forrespondents 15 – 69

Variable name:
GSMD52

Based on:
CLC_AGE, CLC_SEX, GSMD51

Description:
This variable indicates the grip strength norms for respondents 15to 69 years of age.

Note:
Created in the Clinic data collection application

Source:
The Canadian Physical Activity, Fitness and Lifestyle Approach: 3rdEdition, 2003 by the Canadian Society for Exercise Physiology(CSEP)

Table 3
GSMD52 Specifications
Value Condition(s) Description Notes
6 CLC_AGE < 15 or
CLC_AGE > 69 or
GSMD51 = NA
Population exclusions NA
9 GSMD51 = NS At least one required question was not answered (don’tknow, refusal, not stated) NS
0 (CLC_SEX = 1 and
((CLC_AGE < 20 and
(0 < GSMD51 < 79)) or
((19 < CLC_AGE < 30) and
(0 < GSMD51 < 84)) or
((29 < CLC_AGE < 40) and
(0 < GSMD51 < 84)) or
((39 < CLC_AGE < 50) and
(0 < GSMD51 < 80)) or
((49 < CLC_AGE < 60) and
(0 < GSMD51 < 76)) or
((59 < CLC_AGE < 70) and
(0 < GSMD51 < 73)))) or
(CLC_SEX = 2 and
((CLC_AGE < 20 and
(0 < GSMD51 < 48)) or
((19 < CLC_AGE < 30) and
(0 < GSMD51 < 52)) or
((29 < CLC_AGE < 40) and
(0 < GSMD51 < 51)) or
((39 < CLC_AGE < 50) and
(0 < GSMD51 < 49)) or
((49 < CLC_AGE < 60) and
(0 < GSMD51 < 45)) or
((59 < CLC_AGE < 70) and
(0 < GSMD51 < 41))))
Needs improvement  
1 (CLC_SEX = 1 and
((CLC_AGE < 20 and
(78 < GSMD51 < 90)) or
((19 < CLC_AGE < 30) and
(83 < GSMD51 < 95)) or
((29 < CLC_AGE < 40) and
(83 < GSMD51 < 95)) or
((39 < CLC_AGE < 50) and
(79 < GSMD51 < 88)) or
((49 < CLC_AGE < 60) and
(75 < GSMD51 < 84)) or
((59 < CLC_AGE < 70) and
(72 < GSMD51 < 84)))) or
(CLC_SEX = 2 and
((CLC_AGE < 20 and
(47 < GSMD51 < 53)) or
((19 < CLC_AGE < 30) and
(51 < GSMD51 < 58)) or
((29 < CLC_AGE < 40) and
(50 < GSMD51 < 58)) or
((39 < CLC_AGE < 50) and
(48 < GSMD51 < 54)) or
((49 < CLC_AGE < 60) and
(44 < GSMD51 < 49)) or
((59 < CLC_AGE < 70) and
(40 < GSMD51 < 45))))
Fair  
2 (CLC_SEX = 1 and
((CLC_AGE < 20 and
(89 < GSMD51 < 98)) or
((19 < CLC_AGE < 30) and
(94 < GSMD51 < 104)) or
((29 < CLC_AGE < 40) and
(94 < GSMD51 < 104)) or
((39 < CLC_AGE < 50) and
(87 < GSMD51 < 97)) or
((49 < CLC_AGE < 60) and
(83 < GSMD51 < 92)) or
((59 < CLC_AGE < 70) and
(83 < GSMD51 < 91)))) or
(CLC_SEX = 2 and
((CLC_AGE < 20 and
(52 < GSMD51 < 60)) or
((19 < CLC_AGE < 30) and
(57 < GSMD51 < 63)) or
((29 < CLC_AGE < 40) and
(57 < GSMD51 < 63)) or
((39 < CLC_AGE < 50) and
(53 < GSMD51 < 61)) or
((49 < CLC_AGE < 60) and
(48 < GSMD51 < 54)) or
((59 < CLC_AGE < 70) and
(44 < GSMD51 < 48))))
Good  
3 (CLC_SEX = 1 and
((CLC_AGE < 20 and
(97 < GSMD51 < 108)) or
((19 < CLC_AGE < 30) and
(103 < GSMD51 < 115)) or
((29 < CLC_AGE < 40) and
(103 < GSMD51 < 115)) or
((39 < CLC_AGE < 50) and
(96 < GSMD51 < 108)) or
((49 < CLC_AGE < 60) and
(91 < GSMD51 < 101)) or
((59 < CLC_AGE < 70) and
(90 < GSMD51 < 100)))) or
(CLC_SEX = 2 and
((CLC_AGE < 20 and
(59 < GSMD51 < 68)) or
((19 < CLC_AGE < 30) and
(62 < GSMD51 < 70)) or
((29 < CLC_AGE < 40) and
(62 < GSMD51 < 71)) or
((39 < CLC_AGE < 50) and
(60 < GSMD51 < 69)) or
((49 < CLC_AGE < 60) and
(53 < GSMD51 < 61)) or
((59 < CLC_AGE < 70) and
(47 < GSMD51 < 54))))
Very good  
4 (CLC_SEX = 1 and
((CLC_AGE < 20) and
(107 < GSMD51 < NA)) or
((19 < CLC_AGE < 30) and
(114 < GSMD51 < NA)) or
((29 < CLC_AGE < 40) and
(114 < GSMD51 < NA)) or
((39 < CLC_AGE < 50) and
(107 < GSMD51 < NA)) or
((49 < CLC_AGE < 60) and
(100 < GSMD51 < NA)) or
((59 < CLC_AGE < 70) and
(99 < GSMD51 < NA)))) or
(CLC_SEX = 2 and
((CLC_AGE < 20 and
(67 < GSMD51 < NA)) or
((19 < CLC_AGE < 30) and
(69 < GSMD51 < NA)) or
((29 < CLC_AGE < 40) and
(70 < GSMD51 < NA)) or
((39 < CLC_AGE < 50) and
(68 < GSMD51 < NA)) or
((49 < CLC_AGE < 60) and
(60 < GSMD51 < NA)) or
((59 < CLC_AGE < 70) and
(53 < GSMD51 < NA))))
Excellent  

4. GSMD53 - Grip strength norms forrespondents less than 15

Variable name:
GSMD53

Based on:
CLC_AGE, CLC_SEX, GSMD51

Description:
This variable indicates the grip strength norms for respondentsless than 15 years of age.

Note:
Created in the Clinic data collection application

Source:
Stephens, T. & C.L. Craig. 1985. Fitness and activitymeasurement in the 1981 Canada Fitness Survey. In: Drury, T. (ed.).1989. Assessing physical fitness and activity patterns in generalpopulation surveys. Department of Health and Human Services, PublicHealth Service, Center for Disease Control, National Center forHealth Statistics. Hyattsville, MD. pub. No. (PHS) 89-1253.

Table 4
GSMD53 Specifications
Value Condition(s) Description Notes
6 CLC_AGE > 14 or
GSMD51 = NA
Population exclusions NA
9 GSMD51 = NS At least one required question was not answered (don’tknow, refusal, not stated) NS
1 (CLC_SEX = 1 and
(((6 < CLC_AGE < 10) and
(0 < GSMD51 < 28)) or
((9 < CLC_AGE < 13) and
(0 < GSMD51 < 43)) or
((12 < CLC_AGE < 15) and
(0 < GSMD51 < 61)))) or
(CLC_SEX = 2 and
(((6 < CLC_AGE < 10) and
(0 < GSMD51 < 26)) or
((9 < CLC_AGE < 13) and
(0 < GSMD51 < 36)) or
((12 < CLC_AGE < 15) and
(0 < GSMD51 < 52))))
Below average  
2 (CLC_SEX = 1 and
(((6 < CLC_AGE < 10) and
(27 < GSMD51 < 33)) or
((9 < CLC_AGE < 13) and
(42 < GSMD51 < 48)) or
((12 < CLC_AGE < 15) and
(60 < GSMD51 < 70)))) or
(CLC_SEX = 2 and
(((6 < CLC_AGE < 10) and
(25 < GSMD51 < 29)) or
((9 < CLC_AGE < 13) and
(35 < GSMD51 < 41)) or
((12 < CLC_AGE < 15) and
(51 < GSMD51 < 57))))
Average  
3 (CLC_SEX = 1 and
(((6 < CLC_AGE < 10) and
(32 < GSMD51 < NA)) or
((9 < CLC_AGE < 13) and
(47 < GSMD51 < NA)) or
((12 < CLC_AGE < 15) and
(69 < GSMD51 < NA)))) or
(CLC_SEX = 2 and
(((6 < CLC_AGE < 10) and
(28 < GSMD51 < NA)) or
((9 < CLC_AGE < 13) and
(40 < GSMD51 < NA)) or
((12 < CLC_AGE < 15) and
(56 < GSMD51 < NA))))
Above average  
5 CLC_AGE = 6 No norms for this age group  

Hobbies (10 DVs)

1. HOBD12Y - Arts - times peryear

Variable name:
HOBD12Y

Based on:
HOB_12, HOB_12N

Description:
The number of times per yearthe respondent did arts activities, including arts using paints,glazes, finger paints, water colours or crayons in his/her leisuretime or at school.

Note:
Created in the Household Post-Verify process.

Table 1
HOBD12Y Specifications
Value Condition(s) Description Notes
0 HOB_12 = 0 Never  
HOB_12 * 365 HOB_12N = 1 Reported number of times per day converted to derived number oftimes per year  
HOB_12 * 52 HOB_12N = 2 Reported number of times per week converted to derived numberof times per year  
HOB_12 * 12 HOB_12N = 3 Reported number of times per month converted to derived numberof times per year  
HOB_12 HOB_12N = 4 Reported number of times per year  
9996 HOB_12N = NA Population exclusions NA
9999 Else   NS

2. HOBD13Y - Pottery - times peryear

Variable name:
HOBD13Y

Based on:
HOB_13, HOB_13N

Description:
The number of times per year the respondent made pottery orceramics in his/her leisure time or at school.

Note:
Created in the Household Post-Verify process.

Table 2
HOBD13Y Specifications
Value Condition(s) Description Notes
0 HOB_13 = 0 Never  
HOB_13 * 365 HOB_13N = 1 Reported number of times per day converted to derived number oftimes per year  
HOB_13 * 52 HOB_13N = 2 Reported number of times per week converted to derived numberof times per year  
HOB_13 * 12 HOB_13N = 3 Reported number of times per month converted to derived numberof times per year  
HOB_13 HOB_13N = 4 Reported number of times per year  
9996 HOB_13N = NA Population exclusions NA
9999 Else   NS

3. HOBD14Y - Model making - times peryear

Variable name:
HOBD14Y

Based on:
HOB_14, HOB_14N

Description:
The number of times per year the respondent made models usingglues, solders, paints or metals in his/her leisure time or atschool.

Note:
Created in the Household Post-Verify process.

Table 3
HOBD14Y Specifications
Value Condition(s) Description Notes
0 HOB_14 = 0 Never  
HOB_14 * 365 HOB_14N = 1 Reported number of times per day converted to derived number oftimes per year  
HOB_14 * 52 HOB_14N = 2 Reported number of times per week converted to derived numberof times per year  
HOB_14 * 12 HOB_14N = 3 Reported number of times per month converted to derived numberof times per year  
HOB_14 HOB_14N = 4 Reported number of times per year  
9996 HOB_14N = NA Population exclusions NA
9999 Else   NS

4. HOBD15Y - Making fishing sinkers -times per year

Variable name:
HOBD15Y

Based on:
HOB_15, HOB_15N

Description:
The number of times per year the respondent made fishing sinkers orweights in his/her leisure time or at school.

Note:
Created in the Household Post-Verify process.

Table 4
HOBD15Y Specifications
Value Condition(s) Description Notes
0 HOB_15 = 0 Never  
HOB_15 * 365 HOB_15N = 1 Reported number of times per day converted to derived number oftimes per year  
HOB_15 * 52 HOB_15N = 2 Reported number of times per week converted to derived numberof times per year  
HOB_15 * 12 HOB_15N = 3 Reported number of times per month converted to derived numberof times per year  
HOB_15 HOB_15N = 4 Reported number of times per year  
9996 HOB_15N = NA Population exclusions NA
9999 Else   NS

5. HOBD16Y - Welding - times peryear

Variable name:
HOBD16Y

Based on:
HOB_16, HOB_16N

Description:
The number of times per year the respondent did welding orsoldering in his/her leisure time or at school.

Note:
Created in the Household Post-Verify process.

Table 5
HOBD16Y Specifications
Value Condition(s) Description Notes
0 HOB_16 = 0 Never  
HOB_16 * 365 HOB_16N = 1 Reported number of times per day converted to derived number oftimes per year  
HOB_16 * 52 HOB_16N = 2 Reported number of times per week converted to derived numberof times per year  
HOB_16 * 12 HOB_16N = 3 Reported number of times per month converted to derived numberof times per year  
HOB_16 HOB_16N = 4 Reported number of times per year  
9996 HOB_16N = NA Population exclusions NA
9999 Else   NS

6. HOBD17Y - Auto repairs - times peryear

Variable name:
HOBD17Y

Based on:
HOB_17, HOB_17N

Description:
The number of times per year the respondent did auto repairs inhis/her leisure time or at school.

Note:
Created in the Household Post-Verify process.

Table 6
HOBD17Y Specifications
Value Condition(s) Description Notes
0 HOB_17 = 0 Never  
HOB_17 * 365 HOB_17N = 1 Reported number of times per day converted to derived number oftimes per year  
HOB_17 * 52 HOB_17N = 2 Reported number of times per week converted to derived numberof times per year  
HOB_17 * 12 HOB_17N = 3 Reported number of times per month converted to derived numberof times per year  
HOB_17 HOB_17N = 4 Reported number of times per year  
9996 HOB_17N = NA Population exclusions NA
9999 Else   NS

7. HOBD18Y - Electronics - times peryear

Variable name:
HOBD18Y

Based on:
HOB_18, HOB_18N

Description:
The number of times per year the respondent did electronicsassembly or repairs of components in his/her leisure time or atschool.

Note:
Created in the Household Post-Verify process.

Table 7
HOBD18Y Specifications
Value Condition(s) Description Notes
0 HOB_18 = 0 Never  
HOB_18 * 365 HOB_18N = 1 Reported number of times per day converted to derived number oftimes per year  
HOB_18 * 52 HOB_18N = 2 Reported number of times per week converted to derived numberof times per year  
HOB_18 * 12 HOB_18N = 3 Reported number of times per month converted to derived numberof times per year  
HOB_18 HOB_18N = 4 Reported number of times per year  
9996 HOB_18N = NA Population exclusions NA
9999 Else   NS

8. HOBD19Y - Plumbing - times peryear

Variable name:
HOBD19Y

Based on:
HOB_19, HOB_19N

Description:
The number of times per year the respondent did plumbing in his/herleisure time or at school.

Note:
Created in the Household Post-Verify process.

Table 8
HOBD19Y Specifications
Value Condition(s) Description Notes
0 HOB_19 = 0 Never  
HOB_19 * 365 HOB_19N = 1 Reported number of times per day converted to derived number oftimes per year  
HOB_19 * 52 HOB_19N = 2 Reported number of times per week converted to derived numberof times per year  
HOB_19 * 12 HOB_19N = 3 Reported number of times per month converted to derived numberof times per year  
HOB_19 HOB_19N = 4 Reported number of times per year  
9996 HOB_19N = NA Population exclusions NA
9999 Else   NS

9. HOBD20Y - Refinishing furniture -times per year

Variable name:
HOBD20Y

Based on:
HOB_20, HOB_20N

Description:
The number of times per year the respondent refinished furniture inhis/her leisure time or at school.

Note:
Created in the Household Post-Verify process.

Table 9
HOBD20Y Specifications
Value Condition(s) Description Notes
0 HOB_20 = 0 Never  
HOB_20 * 365 HOB_20N = 1 Reported number of times per day converted to derived number oftimes per year  
HOB_20 * 52 HOB_20N = 2 Reported number of times per week converted to derived numberof times per year  
HOB_20 * 12 HOB_20N = 3 Reported number of times per month converted to derived numberof times per year  
HOB_20 HOB_20N = 4 Reported number of times per year  
9996 HOB_20N = NA Population exclusions NA
9999 Else   NS

10. HOBD21Y - Woodworking - times peryear

Variable name:
HOBD21Y

Based on:
HOB_21, HOB_21N

Description:
The number of times per year the respondent did woodworking inhis/her leisure time or at school.

Note:
Created in the Household Post-Verify process.

Table 10
HOBD21Y Specifications
Value Condition(s) Description Notes
0 HOB_21 = 0 Never  
HOB_21 * 365 HOB_21N = 1 Reported number of times per day converted to derived number oftimes per year  
HOB_21 * 52 HOB_21N = 2 Reported number of times per week converted to derived numberof times per year  
HOB_21 * 12 HOB_21N = 3 Reported number of times per month converted to derived numberof times per year  
HOB_21 HOB_21N = 4 Reported number of times per year  
9996 HOB_21N = NA Population exclusions NA
9999 Else   NS

Health utility index (HUI) (10DVs)

1. HUIDCOG - Cognition (FunctionCode)

Variable name:
HUIDCOG

Based on:
HUI_26, HUI_27

Description:
This variable classifies respondents based on their level ofcognitive problems.

Introduced in:
CCHS - Cycle 1.1

Table 1
HUIDCOG Specifications
Value Condition(s) Description Notes
99 (HUI_26 = DK, RF, NS) or
(HUI_27 = DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NS
1 HUI_26 = 1 and
HUI_27 = 1
No cognitive problems  
2 (HUI_26 = 1 and
HUI_27 = 2) or
(HUI_26 = 1 and
HUI_27 = 3)
A little difficulty thinking  
3 HUI_26 = 2 and
HUI_27 = 1
Somewhat forgetful  
4 (HUI_26 = 2 and
HUI_27 = 2) or
(HUI_26 = 2 and
HUI_27 = 3)
Somewhat forgetful / a little difficulty thinking  
5 (HUI_26 = 1 and
HUI_27 = 4) or
(HUI_26 = 2 and
HUI_27 = 4) or
(HUI_26 = 3 and
HUI_27 = 1) or
(HUI_26 = 3 and
HUI_27 = 2) or
(HUI_26 = 3 and
HUI_27 = 3) or
(HUI_26 = 3 and
HUI_27 = 4)
Very forgetful / great deal of difficulty thinking  
6 (HUI_26 = 1 and
HUI_27 = 5) or
(HUI_26 = 2 and
HUI_27 = 5) or
(HUI_26 = 3 and
HUI_27 = 5) or
(HUI_26 = 4 and
HUI_27 = 1) or
(HUI_26 = 4 and
HUI_27 = 2) or
(HUI_26 = 4 and
HUI_27 = 3) or
(HUI_26 = 4 and
HUI_27 = 4) or
(HUI_26 = 4 and
HUI_27 = 5)
Unable to remember and / or to think  

2. HUIDDEX - Dexterity Trouble(Function Code)

Variable name:
HUIDDEX

Based on:
HUI_21, HUI_22, HUI_23, HUI_24

Description:
This variable classifies the respondents based on their state ofdexterity trouble.

Introduced in:
CCHS - Cycle 1.1

Table 2
HUIDDEX Specifications
Value Condition(s) Description Notes
99 (HUI_21 = DK, RF, NS) or
(HUI_22 = DK, RF, NS) or
(HUI_23 = DK, RF, NS) or
(HUI_24 = DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NS
1 HUI_21 = 1 and
HUI_22 = 6 and
HUI_23 = 6 and
HUI_24 = 6
No dexterity problems  
2 HUI_21 = 2 and
HUI_22 = 2 and
HUI_23 = 6 and
HUI_24 = 2
Dexterity problem - no help required  
3 HUI_21 = 2 and
HUI_22 = 2 and
HUI_23 = 6 and
HUI_24 = 1
Dexterity problem - requires special equipment  
4 (HUI_21 = 2 and
HUI_22 = 1 and
HUI_23 = 1 and
HUI_24 = 1) or
(HUI_21 = 2 and
HUI_22 = 1 and
HUI_23 = 1 and
HUI_24 = 2)
Dexterity problem - requires help with some tasks  
5 (HUI_21 = 2 and
HUI_22 = 1 and
HUI_23 = 2 and
HUI_24 = 1) or
(HUI_21 = 2 and
HUI_22 = 1 and
HUI_23 = 2 and
HUI_24 = 2) or
(HUI_21 = 2 and
HUI_22 = 1 and
HUI_23 = 3 and
HUI_24 =1) or
(HUI_21 = 2 and
HUI_22 = 1 and
HUI_23 = 3 and
HUI_24 = 2)
Dexterity problem - requires help with most tasks  
6 (HUI_21 = 2 and
HUI_22 = 1 and
HUI_23 = 4 and
HUI_24 = 1) or
(HUI_21 = 2 and
HUI_22 = 1 and
HUI_23 = 4 and
HUI_24 = 2)
Dexterity problem - requires help with all tasks  

3. HUIDEMO - Emotional Problems(Function Code)

Variable name:
HUIDEMO

Based on:
HUI_25

Description:
This variable classifies the respondents based on their level ofemotional problems.

Introduced in:
CCHS - Cycle 1.1

Table 3
HUIDEMO Specifications
Value Condition(s) Description Notes
9 (HUI_25 = DK, RF, NS) At least one required question was not answered (don’tknow, refusal, not stated) NS
1 HUI_25 = 1 Happy and interested in life  
2 HUI_25 = 2 Somewhat happy  
3 HUI_25 = 3 Somewhat unhappy  
4 HUI_25 = 4 Very unhappy  
5 HUI_25 = 5 So unhappy that life is not worthwhile  

4. HUIDHER - Hearing Problems(Function Code)

Variable name:
HUIDHER

Based on:
HUI_06, HUI_07, HUI_07A, HUI_08, HUI_09

Description:
This variable classifies the respondents based on their hearingstate.

Introduced in:
CCHS - Cycle 1.1

Table 4
HUIDHER Specifications
Value Condition(s) Description Notes
99 (HUI_06 = DK, RF, NS) or
(HUI_07 = DK, RF, NS) or
(HUI_07A = DK, RF, NS) or
(HUI_08 = DK, RF, NS) or
(HUI_09 = DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NS
1 HUI_06 = 1 and
HUI_07 = 6 and
HUI_07A = 6 and
HUI_08 = 6 and
HUI_09 = 6
No hearing problems  
2 HUI_06 = 2 and
HUI_07 = 1 and
HUI_07A = 6 and
HUI_08 = 1 and
HUI_09 = 6
Problem hearing in group - corrected  
3 (HUI_06 = 2 and
HUI_07 = 1 and
HUI_07A = 6 and
HUI_08 = 2 and
HUI_09 = 1) or
(HUI_06 = 2 and
HUI_07 = 1 and
HUI_07A = 6 and
HUI_08 = 2 and
HUI_09 = 2)
Problem hearing in group and individual - corrected  
4 HUI_06 = 2 and
HUI_07 = 2 and
HUI_07A = 1 and
HUI_08 = 1 and
HUI_09 = 6
Problem hearing in group - not corrected  
5 HUI_06 = 2 and
HUI_07 = 2 and
HUI_07A = 1 and
HUI_08 = 2 and
HUI_09 = 1
Problem hearing in group and individual - individualcorrected  
6 (HUI_06 = 2 and
HUI_07 = 2 and
HUI_07A = 1 and
HUI_08 = 2 and
HUI_09 = 2) or
(HUI_06 = 2 and
HUI_07 = 2 and
HUI_07A = 2 and
HUI_08 = 6 and
HUI_09 = 6)
Cannot hear  

5. HUIDHSC - Health Utility Index -categorical variable

Variable name:
HUIDHSC

Based on:
HUIDHSI

Description:
This variable categorizes the respondent's HUI score into one offour categories: no disability, mild disability, moderatedisability or severe disability.

Table 5
HUIDHSC Specifications
Value Condition(s) Description Notes
9 HUIDHSI = NS At least one required question was not answered (don’tknow, refusal, not stated) NS
1 HUIDHSI = 1 No disability  
2 HUIDHSI >= 0.89 and
HUIDHSI < 1
Mild disability  
3 HUIDHSI >= 0.7 and
HUIDHSI < 0.89
Moderate disability  
4 HUIDHSI < 0.7 Severe disability  

6. HUIDHSI - Health UtilityIndex

Variable name:
HUIDHSI

Based on:
HUIDVIS, HUIDHER, HUIDSPE, HUIDMOB, HUIDDEX, HUIDEMO, HUIDCOG,HUIDPAD

Description:
The Health Status Index or Health Utility INDEX (HUI) is a generichealth status index that is able to synthesize both quantitativeand qualitative aspects of health. The index, developed at McMasterUniversity’s Centre for Health Economics and Policy Analysis,is based on the Comprehensive Health Status Measurement System(CHSMS). It provides a description of an individual’s overallfunctional health, based on eight attributes: vision, hearing,speech, mobility (ability to get around), dexterity (use of handsand fingers), cognition (memory and thinking), emotion (feelings),and pain and discomfort.

Introduced in:
CCHS - Cycle 1.1

Note:
In addition to describing functional health status levels, theCHSMS is the basis for HUI3. The HUI3 is a single numerical valuefor any possible combination of levels of these eight self-reportedhealth attributes. The HUI3 maps any one of the vectors of eighthealth attribute levels into a summary health value between -0.360and 1. For instance, an individual who is near-sighted, yet fullyhealthy on the other seven attributes, receives a score of 0.973.On that scale, the most preferred health level (perfect health) israted 1.000 and death is rated 0.000, while negative scores reflecthealth states considered worse than death.

The scores of the HUI embody the views of society concerninghealth status. These views are termed societal preferences, sincepreferences about various health states are elicited from arepresentative sample of individuals.

The HUI3 (Mark 3) was developed by McMaster University’sCentre for Health Economics and Policy Analysis, and is derivedusing societal preferences from a random sample of 500 peoplewithin the boundaries of the City of Hamilton-Wentworth, Ontario,Canada.

The algorithm mapping the questions to the CHSMS itself is theproperty of Health Utilities Inc. and is protected by copyright.Statistics Canada is authorized, when requested, to share thisalgorithm with users who wish to replicate results or analysesconducted by Statistics Canada. The use of the algorithm for otherpurposes, or the sharing of it with others, is prohibited.

Higher scale indicates better health index
Range: -0.360 to 1 in increments of 0.001
Reference: For a detailed explanation of the calculation of theHUI3, refer to:
-Furlong WJ, Feeny DH, Torrance GW. "Health Utilities Index (HUI):Algorithm for determining HUI Mark 2 (HUI2)/ Mark 3 (HUI3) healthstatus classification levels, health states, health-related qualityof life utility scores and single-attribute utility score from40-item interviewer-administered health status questionnaires."Dundas, Canada: Health Utilities Inc. February 1999.

-Furlong WJ, Feeny DH, Torrance GW, et al. "Multiplicativemulti-attribute utility function for the Health Utilities IndexMark 3 (HUI3) system: a technical report" Hamilton, Canada:McMaster University Centre for Health Economics and Policy AnalysisWorking Paper #98-11, December 1998.

7. HUIDMOB - Mobility Trouble(Function Code)

Variable name:
HUIDMOB

Based on:
HUI_14, HUI_15, HUI_16, HUI_17, HUI_18

Description:
This variable classifies the respondents based on their state ofmobility trouble.

Introduced in:
CCHS - Cycle 1.1

Table 7
HUIDMOB Specifications
Value Condition(s) Description Notes
99 (HUI_14 = DK, RF, NS) or
(HUI_15 = DK, RF, NS) or
(HUI_16 = DK, RF, NS) or
(HUI_17 = DK, RF, NS) or
(HUI_18 = DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NS
1 HUI_14 = 1 and
HUI_15 = 6 and
HUI_16 = 6 and
HUI_17 = 6 and
HUI_18 = 6
No mobility problems  
2 HUI_14 = 2 and
HUI_15 = 1 and
HUI_16 = 2 and
HUI_17 = 2 and
HUI_18 = 2
Problem - no aid required  
3 HUI_14 = 2 and
HUI_15 = 1 and
HUI_16 = 1 and
HUI_17 = 2 and
HUI_18 = 2
Problem - requires mechanical support  
4 (HUI_14 = 2 and
HUI_15 = 1 and
HUI_16 = 1 and
HUI_17 = 2 and
HUI_18 = 1) or
(HUI_14 = 2 and
HUI_15 = 1 and
HUI_16 = 2 and
HUI_17 = 2 and
HUI_18 = 1)
Problem - requires wheelchair  
5 (HUI_14 = 2 and
HUI_15 = 1 and
HUI_16 = 1 and
HUI_17 = 1 and
HUI_18 = 1) or
(HUI_14 = 2 and
HUI_15 = 1 and
HUI_16 = 1 and
HUI_17 = 1 and
HUI_18 = 2) or
(HUI_14 = 2 and
HUI_15 = 1 and
HUI_16 = 2 and
HUI_17 = 1 and
HUI_18 = 1) or
(HUI_14 = 2 and
HUI_15 = 1 and
HUI_16 = 2 and
HUI_17 = 1 and
HUI_18 = 2)
Problem - requires help from people  
6 (HUI_14 = 2 and
HUI_15 = 2 and
HUI_16 = 6 and
HUI_17 = 6 and
HUI_18 = 1) or
(HUI_14 = 2 and
HUI_15 = 2 and
HUI_16 = 6 and
HUI_17 = 6 and
HUI_18 = 2)
Cannot walk  

8. HUIDPAD - Activities Prevented /Pain (Function Code)

Variable name:
HUIDPAD

Based on:
HUI_28, HUI_30

Description:
This variable classifies the respondents based on their activitylimitation due to pain or discomfort.

Introduced in:
CCHS - Cycle 1.1

Table 8
HUIDPAD Specifications
Value Condition(s) Description Notes
9 (HUI_28 = DK, RF, NS) or
(HUI_30 = DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NS
1 HUI_28 = 1 and
HUI_30 = 6
No pain or discomfort  
2 HUI_28 = 2 and
HUI_30 = 1
Pain - does not prevent activity  
3 HUI_28 = 2 and
HUI_30 = 2
Pain prevents a few activities  
4 HUI_28 = 2 and
HUI_30 = 3
Pain prevents some activities  
5 HUI_28 = 2 and
HUI_30 = 4
Pain prevents most activities  

9. HUIDSPE - Speech Trouble (FunctionCode)

Variable name:
HUIDSPE

Based on:
HUI_10, HUI_11, HUI_12, HUI_13

Description:
This variable classifies the respondents based on their state ofspeech trouble.

Introduced in:
CCHS - Cycle 1.1

Table 9
HUIDSPE Specifications
Value Condition(s) Description Notes
9 (HUI_10 = DK, RF, NS) or
(HUI_11 = DK, RF, NS) or
(HUI_12 = DK, RF, NS) or
(HUI_13 = DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NS
1 HUI_10 = 1 and
HUI_11 = 6 and
HUI_12 = 6 and
HUI_13 = 6
No speech problems  
2 HUI_10 = 2 and
HUI_11 = 1 and
HUI_12 = 1 and
HUI_13 = 6
Partially understood by strangers  
3 HUI_10 = 2 and
HUI_11 = 1 and
HUI_12 = 2 and
HUI_13 = 1
Partially understood by friends  
4 (HUI_10 = 2 and
HUI_11 = 2 and
HUI_12 = 1 and
HUI_13 = 6) or
(HUI_10 = 2 and
HUI_11 = 2 and
HUI_12 = 2 and
HUI_13 = 1)
Not understood by strangers  
5 (HUI_10 = 2 and
HUI_11 = 1 and
HUI_12 = 2 and
HUI_13 = 2) or
(HUI_10 = 2 and
HUI_11 = 2 and
HUI_12 = 2 and
HUI_13 = 2)
Not understood by friends  

10. HUIDVIS - Vision Trouble (FunctionCode)

Variable name:
HUIDVIS

Based on:
HUI_01, HUI_02, HUI_03, HUI_04, HUI_05

Description:
This variable classifies the respondents based on their visionstate.

Introduced in:
CCHS - Cycle 1.1

Table 10
HUIDVIS Specifications
Value Condition(s) Description Notes
99 (HUI_01 = DK, RF, NS) or
(HUI_02 = DK, RF, NS) or
(HUI_03 = DK, RF, NS) or
(HUI_04 = DK, RF, NS) or
(HUI_05 = DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NS
1 HUI_01 = 1 and
HUI_02 = 6 and
HUI_03 = 6 and
HUI_04 = 1 and
HUI_05 = 6
No visual problems  
2 (HUI_01 = 1 and
HUI_02 = 6 and
HUI_03 = 6 and
HUI_04 = 2 and
HUI_05 = 1) or
(HUI_01 = 2 and
HUI_02 = 1 and
HUI_03 = 6 and
HUI_04 = 1 and
HUI_05 = 6) or
(HUI_01 = 2 and
HUI_02 = 1 and
HUI_03 = 6 and
HUI_04 = 2 and
HUI_05 = 1)
Problems corrected by lenses (distance, close, or both)  
3 (HUI_01 = 1 and
HUI_02 = 6 and
HUI_03 = 6 and
HUI_04 = 2 and
HUI_05 = 2) or
(HUI_01 = 2 and
HUI_02 = 1 and
HUI_03 = 6 and
HUI_04 = 2 and
HUI_05 = 2)
Problems seeing distance - not corrected  
4 (HUI_01 = 2 and
HUI_02 = 2 and
HUI_03 = 1 and
HUI_04 = 1 and
HUI_05 = 6) or
(HUI_01 = 2 and
HUI_02 = 2 and
HUI_03 = 1 and
HUI_04 = 2 and
HUI_05 = 1)
Problems seeing close - not corrected  
5 HUI_01 = 2 and
HUI_02 = 2 and
HUI_03 = 1 and
HUI_04 = 2 and
HUI_05 = 2
Problem seeing close and distance - not corrected  
6 HUI_01 = 2 and
HUI_02 = 2 and
HUI_03 = 2 and
HUI_04 = 6 and
HUI_05 = 6
No sight at all  

Height and weight (9 DVs)

1. HWTDBMI - Body Mass Index(self-reported)

Variable name:
HWTDBMI

Based on:
HWTDHTM, HWTDKG

Description:
Body Mass Index (BMI) is a comparison of "weight" relative to the"height" of respondents.  BMI is calculated by dividing weightin kilograms by height in metres squared.
(BMI = WEIGHT (kilograms) / HEIGHT (metres) SQUARED)

Introduced in:
CCHS - Cycle 1.1

Note:
BMI is not calculated for pregnant women.
This BMI classification is created using "self-reported height" and"self-reported weight" variables.

Table 1
HWTDBMI Specifications
Value Condition(s) Description Notes
999.96 PRS_11 = 1 Population exclusion - Pregnant NA
999.99 HWTDHTM = NS or
HWTDKG = NS
Respondents for whom a valid self-reported height and weightwas not obtained NS
999.99 DHH_SEX = 2 and
(PRS_11 = DK, RF, NS)
Females who did not answer the pregnancy question (don’tknow, refusal, not stated) NS
Round(HWTDKG /
(HWTDHTM * HWTDHTM), .2)
HWTDHTM < NA  and
HWTDKG < NA
BMI calculated from both self-reported height and self-reportedweight values Rounded to two decimal places

2. HWTDBMIA - BMI Classification forAdults Aged 18 and Over (self-reported) - InternationalStandard

Variable name:
HWTDBMIA

Based on:
HWMDBMI, CLC_AGE

Description:
This variable assigns adult respondents aged 18 and over (exceptpregnant women) to one of the following categories, according totheir Body Mass Index (BMI): underweight; normal weight;overweight; obese class I; obese class II; and, obese class III.Here, the BMI categories are adopted from a body weightclassification system recommended by Health Canada and the WorldHealth Organization (WHO) which has been widely usedinternationally.

Introduced in:
CCHS - Cycle 3.1

Note:
According to Health Canada, this BMI classification system can beused as a screening tool to identify weight-related risks at thepopulation and individual levels.  The following health risksare associated with each of the BMI categories for adults aged 18and over:
normal weight = least health risk;
underweight and overweight = increased health risk;
obese class I = high health risk;
obese class II = very high health risk;
obese class III = extremely high health risk
At the population level, the BMI classification system can be usedto compare body weight patterns and related health risks within andbetween populations and to establish population trends in bodyweight patterns.  The classification should be used withcaution at the individual level because the health risk associatedwith each BMI category varies considerably betweenindividuals.  Particular caution should be used whenclassifying: adults who are naturally very lean, very muscularadults, some ethnic and racial groups, and seniors.
This variable excludes female respondents aged 18 and over who werepregnant.

Internet site:
http://www.hc-sc.gc.ca/hpfb-dgpsa/onpp-bppn/weight

Table 2
HWTDBMIA Specifications
Value Condition(s) Description Notes
99 HWTDBMI = NS or
(PRS_11 = DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NS
96 DHH_AGE < 18 or
PRS_11 = 1
Population exclusions NA
1 HWTDBMI < 18.50 Underweight  
2 (18.50 <= HWTDBMI <= 24.99) Normal weight  
3 (25.00 <= HWTDBMI <= 29.99) Overweight  
4 (30.00 <= HWTDBMI <= 34.99) Obese - Class I  
5 (35.00 <= HWTDBMI <= 39.99) Obese - Class II  
6 HWTDBMI >= 40.00 Obese - Class III  

Reference:
For more detailed information, see Canadian Guidelines for BodyWeight Classification in Adults, Health Canada, 2003.

3. HWTDBMIK - BMI Classification forChildren Less Than 18 Years of Age (self-reported) - CDCBMI-for-age

Variable name:
HWTDBMIK

Based on:
DHH_AGE, PRS_11, HWTDBMI

Description:
BMI growth charts can be used beginning at 2 years of age. BMI is calculated from weight and height measurements and is usedto determine whether an individual's weight is appropriate fortheir height. The growth charts consist of a series of percentilecurves illustrating the distribution of measurements in U.S.children.  Most of the data used to construct the charts comesfrom the National Health and Nutrition Examination Survey (NHANES),which has periodically collected height and weight data (and otherhealth information) on the American population since the early1960's.

Note:
This variable excludes femalerespondents who were pregnant and respondents who were 18 years ofage or older.
In these charts, the following percentiles were selected as cutoffpoints:
5th percentile and below = underweight;
From the 6th percentile up to and including the 85th percentile =normal;
From the 86th percentile up to and including the 95th percentile =overweight;
Above the 95th percentile = obese.

Source:
http://www.cdc.gov/growthcharts

Table 3
HWTDBMIK Specifications
Value Condition(s) Description Notes
6 DHH_AGE >17 or
PRS_11 = 1
Population exclusions NA
9 HWTDBMI = NS or
(PRS_11 = DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NS
1 At and below the 5th percentile for the child's age in days,and sex Underweight  
2 Between the 6th and up to and including the 85th percentile forthe child's age in days, and sex Normal weight  
3 Between the 86th and up to and including the 95th percentilefor the child's age in days, and sex Overweight  
4 Above the 95th percentile for the child's age in days, andsex Obese  

4. HWTDCM - Height (centimetres) -self-reported

Variable name:
HWTDCM

Based on:
HWT_2, HWT_2A, HWT_2B, HWT_2C, HWT_2D, HWT_2E, HWT_2F, HWT_2G,HWTDIN

Description:
This variable contains the self-reported standing height incentimetres.

Note:
Created in the Household Post-Verify process.

Table 4
HWTDCM Specifications
Value Condition(s) Description Notes
0 HWT_2 = 0    
Round(HWTDIN * 2.54) HWT_2A < 12 or 
HWT_2B < 12 or
HWT_2C < 12 or
HWT_2D < 12 or
HWT_2E < 12 or
HWT_2F < 12 or
HWT_2G < 12
Self-reported standing height in centimetres  
999 Else   NS

5. HWTDCOL - BMI classification forchildren aged 6 to 17 (self-reported) - Cole classificationsystem

Variable name:
HWTDCOL

Based on:
HWTDBMI, CLC_SEX, CLC_AGE, age in months, age in days

Description:
This variable classifies children aged 6 to 17 (except femalerespondents aged 14 to 17 who were pregnant or did not answer thepregnancy question) as "obese", "overweight" or "neither obese oroverweight" according to the age-and-sex-specific BMI cut-offpoints as defined by Cole et al. The Cole cut-off points are basedon pooled international data (Brazil, Great Britain, Hong Kong,Netherlands, Singapore, and United States) for BMI and linked tothe widely internationally accepted adult BMI cut-off points of 25(overweight) and 30  (obese).

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents who do not fall within the categories of "Obese" or"Overweight" (as defined by Cole et al.) have been classified byCCHS and CHMS as "neither obese nor overweight".  Thisvariable excludes respondents who are 18 years of age or over.

Table 5
HWTDCOL Temporary Reformat

 

AGET1

 

Value Condition(s) Description Notes
round(((mdy(C2_MONTH, C2_DAY, C2_YEAR) -mdy(DHH_MOB, DHH_DOB, DHH_YOB))/365.25), 0.5) Interview date converted to months (C2_MONTH, C2_DAY andC2_YEAR) - Date of birth converted in months (DHH_MOB, DHH_DOB andDHH_YOB) Create respondent’s age in months at time of theinterview  

 

Table
HWTDCOL Specifications
Value Condition(s) Description Notes
9 HWTDBMI = NS or
(PRS_11 = DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NS
6 DHH_AGE > 17 or
PRS_11 = 1
Population exclusions NA
3 (AGET1 = 6 and
CLC_SEX = 1 and
HWMDBMI >=  19.78) or
(AGET1 = 6 and
CLC_SEX = 2 and
HWMDBMI >=  19.65) or
(AGET1 = 6.5 and
CLC_SEX = 1 and
HWMDBMI >=  20.23) or
(AGET1 = 6.5 and
CLC_SEX = 2 and
HWMDBMI >=  20.08) or
(AGET1 = 7 and
CLC_SEX = 1 and
HWMDBMI >=  20.63) or
(AGET1 = 7 and
CLC_SEX = 2 and
HWMDBMI >=  20.51) or
(AGET1 = 7.5 and
CLC_SEX = 1 and
HWMDBMI >=  21.09) or
(AGET1 = 7.5 and
CLC_SEX = 2 and
HWMDBMI >=  21.01) or
(AGET1 = 8 and
CLC_SEX = 1 and
HWMDBMI >=  21.60) or
(AGET1 = 8 and
CLC_SEX = 2 and
HWMDBMI >=  21.57) or
(AGET1 = 8.5 and
CLC_SEX = 1 and
HWMDBMI >=  22.17) or
(AGET1 = 8.5 and
CLC_SEX = 2 and
HWMDBMI >=  22.18) or
(AGET1 = 9 and
CLC_SEX = 1 and
HWMDBMI >=  22.77) or
(AGET1 = 9 and
CLC_SEX = 2 and
HWMDBMI >=  22.81) or
(AGET1 = 9.5 and
CLC_SEX = 1 and
HWMDBMI >=  23.39) or
(AGET1 = 9.5 and
CLC_SEX = 2 and
HWMDBMI >=  23.46) or
(AGET1 = 10 and
CLC_SEX = 1 and
HWMDBMI >=  24.00) or
(AGET1 = 10 and
CLC_SEX = 2 and
HWMDBMI >=  24.41) or
(AGET1 = 10.5 and
CLC_SEX = 1 and
HWMDBMI >=  24.57) or
(AGET1 = 10.5 and
CLC_SEX = 2 and
HWMDBMI >=  24.77) or
(AGET1 = 11 and
CLC_SEX = 1 and
HWMDBMI >=  25.10) or
(AGET1 = 11 and
CLC_SEX = 2 and
HWMDBMI >=  24.42) or
(AGET1 = 11.5 and
CLC_SEX = 1 and
HWMDBMI >=  25.58) or
(AGET1 = 11.5 and
CLC_SEX = 2 and
HWMDBMI >=  26.05) or
(AGET1 = 12 and
CLC_SEX = 1 and
HWMDBMI >=  26.02) or
(AGET1 = 12 and
CLC_SEX = 2 and
HWMDBMI >=  26.67) or
(AGET1 = 12.5 and
CLC_SEX = 1 and
HWMDBMI >=  26.43) or
(AGET1 = 12.5 and
CLC_SEX = 2 and
HWMDBMI >=  27.24) or
(AGET1 = 13 and
CLC_SEX = 1 and
HWMDBMI >=  26.84) or
(AGET1 = 13 and
CLC_SEX = 2 and
HWMDBMI >=  27.76) or
(AGET1 = 13.5 and
CLC_SEX = 1 and
HWMDBMI >=  27.25) or
(AGET1 = 13.5 and
CLC_SEX = 2 and
HWMDBMI >=  28.20) or
(AGET1 = 14 and
CLC_SEX = 1 and
HWMDBMI >=  27.63) or
(AGET1 = 14 and
CLC_SEX = 2 and
HWMDBMI >=  28.57) or
(AGET1 = 14.5 and
CLC_SEX = 1 and
HWMDBMI >=  27.98) or
(AGET1 = 14.5 and
CLC_SEX = 2 and
HWMDBMI >=  28.87) or
(AGET1 = 15 and
CLC_SEX = 1 and
HWMDBMI >=  28.30) or
(AGET1 = 15 and
CLC_SEX = 2 and
HWMDBMI >=  29.11) or
(AGET1 = 15.5 and
CLC_SEX = 1 and
HWMDBMI >=  28.60) or
(AGET1 = 15.5 and
CLC_SEX = 2 and
HWMDBMI >=  29.29) or
(AGET1 = 16 and
CLC_SEX = 1 and
HWMDBMI >=  28.88) or
(AGET1 = 16 and
CLC_SEX = 2 and
HWMDBMI >=  29.43) or
(AGET1 = 16.5 and
CLC_SEX = 1 and
HWMDBMI >=  29.14) or
(AGET1 = 16.5 and
CLC_SEX = 2 and
HWMDBMI >=  29.56) or
(AGET1 = 17 and
CLC_SEX = 1 and
HWMDBMI >=  29.41) or
(AGET1 = 17 and
CLC_SEX = 2 and
HWMDBMI >=  29.69) or
(AGET1 = 17.5 and
CLC_SEX = 1 and
HWMDBMI >=  29.70) or
(AGET1 = 17.5 and
CLC_SEX = 2 and
HWMDBMI >=  29.84) or
(AGET1 = 18 and
CLC_SEX = 1 and
HWMDBMI >=  30.00) or
(AGET1 = 18 and
CLC_SEX = 2 and
HWMDBMI >=  30.00)
Obese  
2 (AGET1 = 6 and
CLC_SEX = 1 and
(HWMDBMI >=  17.55 and
HWMDBMI < 19.78)) or
(AGET1 = 6 and
CLC_SEX = 2 and
(HWMDBMI >=  17.34 and
HWMDBMI < 19.65)) or
(AGET1 = 6.5 and
CLC_SEX = 1 and
(HWMDBMI >=  17.71 and
HWMDBMI < 20.23)) or
(AGET1 = 6.5 and
CLC_SEX = 2 and
(HWMDBMI >=  17.53 and
HWMDBMI < 20.08)) or
(AGET1 = 7 and
CLC_SEX = 1 and
(HWMDBMI >=  17.92 and
HWMDBMI < 20.63)) or
(AGET1 = 7 and
CLC_SEX = 2 and
(HWMDBMI >=  17.75 and
HWMDBMI < 20.51)) or
(AGET1 = 7.5 and
CLC_SEX = 1 and
(HWMDBMI >=  18.16 and
HWMDBMI < 21.09)) or
(AGET1 = 7.5 and
CLC_SEX = 2 and
(HWMDBMI >=  18.03 and
HWMDBMI < 21.01)) or
(AGET1 = 8 and
CLC_SEX = 1 and
(HWMDBMI >=  18.44 and
HWMDBMI < 21.60)) or
(AGET1 = 8 and
CLC_SEX = 2 and
(HWMDBMI >=  18.35 and
HWMDBMI < 21.57)) or
(AGET1 = 8.5 and
CLC_SEX = 1 and
(HWMDBMI >=  18.76 and
HWMDBMI < 22.17)) or
(AGET1 = 8.5 and
CLC_SEX = 2 and
(HWMDBMI >=  18.69 and
HWMDBMI < 22.18)) or
(AGET1 = 9 and
CLC_SEX = 1 and
(HWMDBMI >=  19.10 and
HWMDBMI < 22.77)) or
(AGET1 = 9 and
CLC_SEX = 2 and
(HWMDBMI >=  19.07 and
HWMDBMI < 22.81)) or
(AGET1 = 9.5 and
CLC_SEX = 1 and
(HWMDBMI >=  19.46 and
HWMDBMI < 23.39)) or
(AGET1 = 9.5 and
CLC_SEX = 2 and
(HWMDBMI >=  19.45 and
HWMDBMI < 23.46)) or
(AGET1 = 10 and
CLC_SEX = 1 and
(HWMDBMI >=  19.84 and
HWMDBMI < 24.00)) or
(AGET1 = 10 and
CLC_SEX = 2 and
(HWMDBMI >=  19.86 and
HWMDBMI < 24.11)) or
(AGET1 = 10.5 and
CLC_SEX = 1 and
(HWMDBMI >=  20.20 and
HWMDBMI < 24.57)) or
(AGET1 = 10.5 and
CLC_SEX = 2 and
(HWMDBMI >=  20.29 and
HWMDBMI < 24.77)) or
(AGET1 = 11 and
CLC_SEX = 1 and
(HWMDBMI >=  20.55 and
HWMDBMI < 25.10)) or
(AGET1 = 11 and
CLC_SEX = 2 and
(HWMDBMI >=  20.74 and
HWMDBMI < 25.42)) or
(AGET1 = 11.5 and
CLC_SEX = 1 and
(HWMDBMI >=  20.89 and
HWMDBMI < 25.58)) or
(AGET1 = 11.5 and
CLC_SEX = 2 and
(HWMDBMI >=  21.20 and
HWMDBMI < 26.05)) or
(AGET1 = 12 and
CLC_SEX = 1 and
(HWMDBMI >=  21.22 and
HWMDBMI < 26.02)) or
(AGET1 = 12 and
CLC_SEX = 2 and
(HWMDBMI >=  21.68 and
HWMDBMI < 26.67)) or
(AGET1 = 12.5 and
CLC_SEX = 1 and
(HWMDBMI >=  21.56 and
HWMDBMI < 26.43)) or
(AGET1 = 12.5 and
CLC_SEX = 2 and
(HWMDBMI >=  22.14 and
HWMDBMI < 27.24)) or
(AGET1 = 13 and
CLC_SEX = 1 and
(HWMDBMI >=  21.91 and
HWMDBMI < 26.84)) or
(AGET1 = 13 and
CLC_SEX = 2 and
(HWMDBMI >=  22.58 and
HWMDBMI < 27.76)) or
(AGET1 = 13.5 and
CLC_SEX = 1 and
(HWMDBMI >=  22.27 and
HWMDBMI < 27.25)) or
(AGET1 = 13.5 and
CLC_SEX = 2 and
(HWMDBMI >=  22.98 and
HWMDBMI < 28.20)) or
(AGET1 = 14 and
CLC_SEX = 1 and
(HWMDBMI >=  22.62 and
HWMDBMI < 27.63)) or
(AGET1 = 14 and
CLC_SEX = 2 and
(HWMDBMI >=  23.34 and
HWMDBMI < 28.57)) or
(AGET1 = 14.5 and
CLC_SEX = 1 and
(HWMDBMI >=  22.96 and
HWMDBMI < 27.98)) or
(AGET1 = 14.5 and
CLC_SEX = 2 and
(HWMDBMI >=  23.66 and
HWMDBMI < 28.87)) or
(AGET1 = 15 and
CLC_SEX = 1 and
(HWMDBMI >=  23.29 and
HWMDBMI < 28.30)) or
(AGET1 = 15 and
CLC_SEX = 2 and
(HWMDBMI >=  23.94 and
HWMDBMI < 29.11)) or
(AGET1 = 15.5 and
CLC_SEX = 1 and
(HWMDBMI >=  23.60 and
HWMDBMI < 28.60)) or
(AGET1 = 15.5 and
CLC_SEX = 2 and
(HWMDBMI >=  24.17 and
HWMDBMI < 29.29)) or
(AGET1 = 16 and
CLC_SEX = 1 and
(HWMDBMI >=  23.90 and
HWMDBMI < 28.88)) or
(AGET1 = 16 and
CLC_SEX = 2 and
(HWMDBMI >=  24.37 and
HWMDBMI < 29.43)) or
(AGET1 = 16.5 and
CLC_SEX = 1 and
(HWMDBMI >=  24.19 and
HWMDBMI < 29.14)) or
(AGET1 = 16.5 and
CLC_SEX = 2 and
(HWMDBMI >=  24.54 and
HWMDBMI < 29.56)) or
(AGET1 = 17 and
CLC_SEX = 1 and
(HWMDBMI >=  24.46 and
HWMDBMI < 29.41)) or
(AGET1 = 17 and
CLC_SEX = 2 and
(HWMDBMI >=  24.70 and
HWMDBMI < 29.69)) or
(AGET1 = 17.5 and
CLC_SEX = 1 and
(HWMDBMI >=  24.73 and
HWMDBMI < 29.70)) or
(AGET1 = 17.5 and
CLC_SEX = 2 and
(HWMDBMI >=  24.85 and
HWMDBMI < 29.84)) or
(AGET1 = 18 and
CLC_SEX = 1 and
(HWMDBMI >=  25.00 and
HWMDBMI < 30.00)) or
(AGET1 = 18 and
CLC_SEX = 2 and
(HWMDBMI >=  25.00 and
HWMDBMI < 30.00))
Overweight  
1 Else Neither overweight nor obese  

Reference:
For more information about the Cole BMI classification system, seeEstablishing a Standard Definition for Child Overweight and ObesityWorldwide - International survey, by Tim J Cole, Mary C Bellizzi,Katherine M. Flegal, William H Dietz, published in British MedicalJournal, Volume: 320, May 2000.

 

6. HWTDHTM - Height (metres) -self-reported

Variable name:
HWTDHTM

Based on:
HWTDCM

Description:
This variable indicates the respondent’s self-reported heightin metres.

Introduced in:
CCHS - Cycle 1.1

Table 6
HWTDHTM Specifications
Value Condition(s) Description Notes
9.99 HWTDCM = NS At least one required question was not answered (don’t know, refusal, not stated) NS
HWTDCM/100 Else Self-reported height in metres  

7. HWTDIN - Height (inches) -self-reported

Variable name:
HWTDIN

Based on:
HWT_2, HWT_2A, HWT_2B, HWT_2C, HWT_2D, HWT_2E, HWT_2F, HWT_2G

Description:
This variable contains the self-reported standing height ininches.

Note:
Created in the Household Post-Verify process

Table 7
HWTDIN Specifications
Value Condition(s) Description Notes
0 HWT_2 = 0 Less than 12”  
HWT_2A + 12 HWT_2A < 12 Between 12” and 23”  
HWT_2B + 24 HWT_2B < 12 Between 24” and 35”  
HWT_2C + 36 HWT_2C < 12 Between 36” and 47”  
HWT_2D + 48 HWT_2D < 12 Between 48” and 59”  
HWT_2E + 60 HWT_2E < 12 Between 60” and 71”  
HWT_2F + 72 HWT_2F < 12 Between 72” and 83”  
HWT_2G + 84 HWT_2G < 12 Between 84” and 95”  
99 Else   NS

8. HWTDKG - Weight (kilograms) -self-reported

Variable name:
HWTDKG

Based on:
HWT_3, HWT_3N, PRS_11

Description:
This variable contains the self-reported weight in kilograms.

Introduced in:
CCHS - Cycle 1.1

Note:
Created in the Household Post-Verify process.  This variableexcludes female respondents who were pregnant.

Table 8
HWTDKG Specifications
Value Condition(s) Description Notes
996 PRS_11 = 1 Population exclusions NA
Round(HWT_3 * 0.4536) HWT_3N = 1 Self-reported weight in pounds converted to kilograms  
HWT_3 HWT_3N = 2 Self-reported weight in kilograms  
999 Else   NS

9. HWTDLB - Weight (pounds) -self-reported

Variable name:
HWTDLB

Based on:
HWT_3, HWT_3N, PRS_11

Description:
This variable contains the self-reported weight in pounds.

Note:
Created in the Household Post-Verify process.  This variableexcludes female respondents who were pregnant.

Table 9
HWTDLB Specifications
Value Condition(s) Description Notes
996 PRS_11 = 1 Population exclusions NA
HWT_3 HWT_3N = 1 Self-reported weight in pounds  
Round(HWT_3 * 2.205) HWT_3N = 2 Self-reported weight in kilograms converted to pounds  
999 Else   NS

Income (5 DVs)

1. INCDDIA2 - Total household income- 2 categories

Variable name:
INCDDIA2

Based on:
DHHDHSZ, INCDHH

Description:
This variable classifies the total household income into twocategories based on total household income and the number of peopleliving in the household.

Introduced in:
NPHS - Cycle 1

Table 1
INCDDIA2 Specifications
Value Condition(s) Description Notes
1 (DHHDHSZ in (1,2) and
INCDHH in (1,2,3,4)) or
(DHHDHSZ in (3,4) and
INCDHH in (1,2,3,4,5)) or
(DHHDHSZ > 4 and
INCDHH in (1,2,3,4,5,6))
Low income  
2 (DHHDHSZ in (1,2) and
INCDHH in (5,6,7,8,9,10,11,12)) or
(DHHDHSZ in (3,4) and
INCDHH in (6,7,8,9,10,11,12)) or
(DHHDHSZ > 4 and
INCDHH in (7,8,9,10,11,12))
Middle or high income  
9 Else Not enough information for the classification NS

2. INCDDIA4 - Total household income -4 categories

Variable name:
INCDDIA4

Based on:
DHHDHSZ, INCDHH

Description:
This variable classifies the total household income into fourcategories based on total household income and the number of peopleliving in the household.

Introduced in:
NPHS - Cycle 1

Table 2
INCDDIA4 Specifications
Value Condition(s) Description Notes
1 (DHHDHSZ in (1,2) and
INCDHH in (1,2,3,4)) or
(DHHDHSZ in (3,4) and
INCDHH in (1,2,3,4,5)) or
(DHHDHSZ > 4 and
INCDHH in (1,2,3,4,5,6))
Lowest income grouping  
2 (DHHDHSZ in (1,2) and
INCDHH in (5,6)) or
(DHHDHSZ in (3,4) and
INCDHH in (6,7)) or
(DHHDHSZ > 4 and
INCDHH in (7,8,9))
Lower middle income grouping  
3 (DHHDHSZ in (1,2) and
INCDHH in (7,8,9)) or
(DHHDHSZ in (3,4) and
INCDHH in (8,9,10)) or
(DHHDHSZ > 4 and
INCDHH in (10))
Upper middle income grouping  
4 (DHHDHSZ in (1,2) and
INCDHH in (10,11,12)) or
(DHHDHSZ > 2 and
INCDHH in (11,12))
Highest income grouping  
9 Else Not enough information for the classification NS

3. INCDDIA5 - Total household income -5 categories

Variable name:
INCDDIA5

Based on:
DHHDHSZ, INCDHH

Description:
This variable classifies the total household income into fivecategories based on total household income and the number of peopleliving in the household.

Introduced in:
NPHS - Cycle 1

Table 3
INCDDIA5 Specifications
Value Condition(s) Description Notes
1 (DHHDHSZ in (1,2,3,4) and
INCDHH in (1,2,3)) or
(DHHDHSZ > 4 and
INCDHH in (1,2,3,4))
Lowest income grouping  
2 (DHHDHSZ in (1,2) and
INCDHH in (4)) or
(DHHDHSZ in (3,4) and
INCDHH in (4,5)) or
(DHHDHSZ > 4 and
INCDHH in (5,6))
Lower middle income grouping  
3 (DHHDHSZ in (1,2) and
INCDHH in (5,6)) or
(DHHDHSZ in (3,4) and
INCDHH in (6,7)) or
(DHHDHSZ > 4 and
INCDHH in (7,8,9))
Middle income grouping  
4 (DHHDHSZ in (1,2) and
INCDHH in (7,8,9)) or
(DHHDHSZ in (3,4) and
INCDHH in (8,9,10)) or
(DHHDHSZ > 4 and
INCDHH in (10))
Upper middle income grouping  
5 (DHHDHSZ in (1,2) and
INCDHH in (10,11,12)) or
(DHHDHSZ > 2 and
INCDHH in (11,12))
Highest income grouping  
9 Else Not enough information for the classification NS

4. INCDHH - Total Household Income -All Sources

Variable name:
INCDHH

Based on:
INC_22, INC_23, INC_24, INC_25, INC_26, INC_27, INC_28

Description:
This variable groups the total household income from all sources. Arange value was assigned by the application to respondents whoprovided an exact amount in question INC_21.

Introduced in:
CCHS - Cycle 1.1

Table 4
INCDHH Specifications
Value Condition(s) Description Notes
99 (INC_22 = DK, RF, NS) None of the income questions were answered (don’t know,refusal, not stated) NS
1 INC_22 = 3 No income  
2 INC_24 = 1 Less than $5,000  
3 INC_24 = 2 $5,000 to $9,999  
4 INC_25 = 1 $10,000 to $14,999  
5 INC_25 = 2 $15,000 to $19,999  
6 INC_27 = 1 $20,000 to $29,999  
7 INC_27 = 2 $30,000 to $39,999  
8 INC_28 = 1 $40,000 to $49,999  
9 INC_28 = 2 $50,000 to $59,999  
10 INC_28 = 3 $60,000 to $79,999  
11 INC_28 = 4 $80,000 to $99,999  
12 INC_28 = 5 $100,000 +  
99 Else Not enough information for the classification NS

5. INCDPER - Personal Income - AllSources

Variable name:
INCDPER

Based on:
INC_32, INC_34, INC_35, INC_37, INC_38

Description:
This variable indicates the respondent’s personal income fromall sources. A range value was assigned by the application torespondents who provided an exact amount in question INC_31.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents less than 15 years old were excluded from thepopulation.

Table 5
INCDPER Specifications
Value Condition(s) Description Notes
96 DHH_AGE < 15 Population exclusions NA
99 (INC_32 = DK, RF, NS) None of the income questions were answered (don’t know,refusal, not stated) NS
1 (INC_32 = 3, NA) No income  
2 INC_34 = 1 Less than $5,000  
3 INC_34 = 2 $5,000 to $9,999  
4 INC_35 = 1 $10,000 to $14,999  
5 INC_35 = 2 $15,000 to $19,999  
6 INC_37 = 1 $20,000 to $29,999  
7 INC_37 = 2 $30,000 to $39,999  
8 INC_38 = 1 $40,000 to $49,999  
9 INC_38 = 2 $50,000 to $59,999  
10 INC_38 = 3 $60,000 to $79,999  
11 INC_38 = 4 $80,000 to $99,999  
12 INC_38 = 5 $100,000 +  
99 Else Not enough information for the classification NS

Labour force (8 DVs)

1. LBFDHPW - Total usual hoursworked per week

Variable name:
LBFDHPW

Based on:
DHH_AGE, LBF_42, LBF_53

Description:
This variable indicates the total number of hours the respondentworked per week.

Introduced in:
CCHS - Cycle 3.1

Note:
Respondents aged less than 15 or more than 75 years old or who didnot answer whether they had worked in the year preceding theinterview have been excluded from the population.

Table 1
LBFDHPW Specifications
Value Condition(s) Description Notes
996 DHH_AGE < 15 or
DHH_AGE > 75 or
LBF_42 = NA
Population exclusion NA
999 (LBF_42 = DK, RF, NS) or
(LBF_53 = DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NS
LBF_42 LBF_42 < NA and
LBF_53 = NA
Number of hours usually worked for respondents with onejob  
LBF_42 +
LBF_53
LBF_42 < NA and
LBF_53 < NA
Number of hours usually worked for respondents with more thanone job  

2. LBFDJST - Job status over pastyear

Variable name:
LBFDJST

Based on:
DHH_AGE, LBF_01, LBF_11, LBF_22, LBF_61, LBF_71

Description:
This variable indicates the respondent’s job status over thepast year.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents aged less than 15 or more than 75 years old or who didnot work in the week preceding the interview were excluded from thepopulation.

Table 2
LBFDJST Specifications
Value Condition(s) Description Notes
96 LBF_01 = NA or
DHH_AGE < 15 or
DHH_AGE > 75
Population exclusion NA
99 (LBF_22 = DK, RF, NS) or
(LBF_61 = DK, RF, NS) or
(LBF_71 = DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NS
1 LBF_61 = 52 Has had a job throughout the past year  
2 LBF_71 = 52 Was without a job and looking for work throughout the pastyear  
3 LBF_22 = 2 Was without a job and not looking for work throughout pastyear  
4 (LBF_61 + LBF_71) = 52 and
(0 < LBF_71 < 52) and
LBF_61 < 52
Has had a job part of the year - was without a job and lookingfor other part of the year  
5 LBF_61 < 52 and
LBF_71 = 0
Has had a job part of the year - was without a job and notlooking for other part of the year  
6 LBF_71 < 52 and
LBF_21 = 2 and
(LBF_11 = 1 or
LBF_22 = 1)
Was without a job and looking for part of the year - waswithout a job and not looking for other part of the year  
7 (LBF_61 + LBF_71) < 52 and
(0 < LBF_71 < 52) and
LBF_61 < 52
Has had a job part of the year - was without a job and lookingfor part of the year - was without a job and not looking for otherpart of year  

3. LBFDMJS - Multiple jobstatus

Variable name:
LBFDMJS

Based on:
DHH_AGE, LBF_03, LBF_21, LBF_23, LBF_51

Description:
This variable classifies respondents based on whether or not theyhad multiple jobs in the past year and if they still do.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents aged less than 15 or more than 75 years old have beenexcluded from the population.

Table 3
LBFDMJS Specifications
Value Condition(s) Description Notes
6 DHH_AGE < 15 or
DHH_AGE > 75
Population exclusion NA
9 (LBF_03 = DK, RF, NS) or
(LBF_21 = DK, RF, NS) or
(LBF_23 = DK, RF, NS) or
(LBF_51 = DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NS
1 LBF_51 = 52 Currently has multiple jobs - had them all past year  
2 LBF_03 = 1 and
LBF_51 < 52
Currently has multiple jobs - did not have them all pastyear  
3 LBF_03 = 2 Currently has only one job  
4 LBF_23 = 1 Currently does not have a job - held multiple jobs over pastyear  
5 LBF_23 = 2 or
LBF_21 = 2
Currently does not have a job - did not hold multiple jobs overthe year  

4. LBFDPFT - Full-time/ part-timeworking status (for total usual hours)

Variable name:
LBFDPFT

Based on:
LBFDHPW

Description:
This variable indicates if the respondent works full-time orpart-time.

Introduced in:
CCHS - Cycle 3.1

Note:
Respondents aged less than 15 or more than 75 years old or who didnot work in the year preceding the interview have been excludedfrom the population.

Table 4
LBFDPFT Specifications
Value Condition(s) Description Notes
6 LBFDHPW = NA Population exclusion NA
9 LBFDHPW = NS At least one required question was not answered (don’tknow, refusal, not stated) NS
1 LBFDHPW >= 30 Full-time  
2 LBFDHPW < 30 Part-time  

5. LBFDRNW - Main reason for notworking last week

Variable name:
LBFDRNW

Based on:
DHH_AGE, LBF_01, LBF_11, LBF_13, LBF_41

Description:
This variable indicates the main reason why the respondent did notwork in the week prior to the interview.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents aged less than 15 or more than 75 years old or who didnot work in the week preceding the interview have been excludedfrom the population.

Table 5
LBFDRNW Specifications
Value Condition(s) Description Notes
96 DHH_AGE < 15 or
DHH_AGE > 75  or
LBF_01 =  1
Population exclusion NA
99 (LBF_11 = DK, RF, NS) or
(LBF_13 = DK, RF, NS) or
(LBF_41 = DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NS
1 LBF_01 = 3 Permanently unable to work  
2 LBF_13 = 1 or
LBF_41 = 1
Own illness or disability  
3 LBF_13 = 2 or
LBF_41 = 2
Caring for - own children  
4 LBF_13 = 3 or
LBF_41 = 3
Caring for - elder relative  
5 LBF_13 = 4 or
LBF_41 = 4
Pregnancy/ maternity leave  
6 LBF_13 = 5 or
LBF_41 = 5
Other personal or family responsibilities  
7 LBF_13 = 6 or
LBF_41 = 6
Vacation  
8 LBF_13 = 7 or
LBF_41 = 14
School or educational leave  
9 LBF_13 = 8 Retired  
10 LBF_13 = 9 Believes no work is available (in area or suited toskills)  
11 LBF_41 = 7 Labour dispute  
12 LBF_41 = 8 Temporary layoff due to business conditions  
13 LBF_41 = 9 Seasonal layoff  
14 LBF_41 = 10 Casual job, no work available  
15 LBF_41 = 12 Self-employed, no work available  
16 LBF_41 = 13 Seasonal business  
17 LBF_11 = 1 Looking for work  
18 LBF_41 = 11 Work schedule  
19 LBF_13 = 10 or
LBF_41 = 15
Other reason  

6. LBFDSTU - Student workingstatus

Variable name:
LBFDSTU

Based on:
DHH_AGE, EDU_01, EDU_02, LBF_01, LBF_02, LBF_21

Description:
This variable indicates the respondent’s working status ifhe/she was a student.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents aged less than 15 years or more than 75 years old orwho were not studying at the time of the interview have beenexcluded from the population.

Table 6
LBFDSTU Specifications
Value Condition(s) Description Notes
6 DHH_AGE < 15 or
DHH_AGE > 75 or
EDU_01 = 2
Population exclusion NA
9 (LBF_21 = DK, RF, NS) or
(EDU_02 = DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NS
1 (LBF_01 = 1 or
LBF_02 = 1 or
LBF_21 = 1) and
EDU_02 = 1
Worked during last 12 months and currently attending schoolfull-time  
2 (LBF_01 = 1 or
LBF_02 = 1 or
LBF_21 = 1) and
EDU_02 = 2
Worked during last 12 months and currently attending schoolpart-time  
3 LBF_21 = 2 and
EDU_02 = 1
Did not work during last 12 months and currently attendingschool full-time  
4 LBF_21 = 2 and
EDU_02 = 2
Did not work during last 12 months and currently attendingschool part-time  

7. LBFDWSL - Working status lastweek

Variable name:
LBFDWSL

Based on:
DHH_AGE, LBF_01, LBF_11, LBF_41

Description:
This variable classifies the respondent based on his/her workingstatus in the week prior to the interview and also includesgrouping for reasons of not working.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents aged less than 15 or more than 75 years old have beenexcluded from the population.

Table 7
LBFDWSL Specifications
Value Condition(s) Description Notes
96 DHH_AGE < 15 or
DHH_AGE > 75
Population exclusion NA
99 (LBF_11 = DK, RF, NS) or
(LBF_41 = DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NS
1 LBF_01 = 1 Worked at a job or business  
2 (LBF_41 = 8, 9, 10, 12, 13) Had a job - on temporary or seasonal layoff  
3 (0 < LBF_41 < 8) or
LBF_41 = 11 or
(13 < LBF_41 < NA)
Had a job - absent for some other reason  
4 LBF_11 = 1 Did not have a job - looked for work over past 4 weeks  
5 LBF_11 = 2 Did not have a job - did not look for work over past 4weeks  
6 LBF_01 = 3 Permanently unable to work  

8. LBFDWSS - Working status lastweek

Variable name:
LBFDWSS

Based on:
DHH_AGE, LBF_01, LBF_02

Description:
This variable classifies the respondent based on his/her workingstatus in the week prior to the interview.

Introduced in:
CCHS - Cycle 3.1

Note:
Respondents aged less than 15 or more than 75 years old have beenexcluded from the population.

Table 8
LBFDWSS Specifications
Value Condition(s) Description Notes
6 DHH_AGE < 15 or
DHH_AGE > 75
Population exclusions NA
1 LBF_01 = 1 Worked at a job or business  
2 LBF_02 = 1 Had a job but did not work (absent)  
3 LBF_02 = 2 Did not have a job  
4 LBF_02 = 3 Permanently unable to work  
9 (LBF_02 = DK, R, NS) or
(LBF_01 = DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NS

Milk and dairy product consumption (4DVs)

1. MDCD11Y - Drinks milk - times peryear

Variable name:
MDCD11Y

Based on:
MDC_11, MDC_11N

Description:
The number of times per year the respondent drinks milk or enrichedmilk substitutes or uses them on cereal.

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 1
MDCD11Y Specifications
Value Condition(s) Description Notes
0 MDC_11 = 0 Never  
MDC_11 * 365 MDC_11N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MDC_11 * 52 MDC_11N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MDC_11 * 12 MDC_11N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MDC_11 MDC_11N = 4 Reported number of times consumed per year  
9996 MDC_11N = NA Population exclusions NA
9999 Else   NS

2. MDCD13Y - Eats cottage cheese -times per year

Variable name:
MDCD13Y

Based on:
MDC_13, MDC_13N

Description:
The number of times per year the respondent eats cottagecheese.

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 2
MDCD13Y Specifications
Value Condition(s) Description Notes
0 MDC_13 = 0 Never  
MDC_13 * 365 MDC_13N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MDC_13 * 52 MDC_13N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MDC_13 * 12 MDC_13N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MDC_13 MDC_13N = 4 Reported number of times consumed per year  
9996 MDC_13N = NA Population exclusions NA
9999 Else   NS

3. MDCD14Y - Eats yogurt - times peryear

Variable name:
MDCD14Y

Based on:
MDC_14, MDC_14N

Description:
The number of times per year the respondent eats yogurt, excludingfrozen yogurt.

Note:
Created in the Household Post-Verify process.   Based onCCHS 2.2 but no direct variables.

Table 3
MDCD14Y Specifications
Value Condition(s) Description Notes
0 MDC_14 = 0 Never  
MDC_14 * 365 MDC_14N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MDC_14 * 52 MDC_14N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MDC_14 * 12 MDC_14N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MDC_14 MDC_14N = 4 Reported number of times consumed per year  
9996 MDC_14N = NA Population exclusions NA
9999 Else   NS

4. MDCD15Y - Eats ice cream or frozenyogurt - times per year

Variable name:
MDCD15Y

Based on:
MDC_15, MDC_15N

Description:
The number of times per year the respondent eats ice cream orfrozen yogurt.

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 4
MDCD15Y Specifications
Value Condition(s) Description Notes
0 MDC_15 = 0 Never  
MDC_15 * 365 MDC_15N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MDC_15 * 52 MDC_15N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MDC_15 * 12 MDC_15N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MDC_15 MDC_15N = 4 Reported number of times consumed per year  
9996 MDC_15N = NA Population exclusions NA
9999 Else   NS

Meat and fish consumption (11DVs)

1. MFCD11Y - Eats red meat - timesper year

Variable name:
MFCD11Y

Based on:
MFC_11, MFC_11N

Description:
The number of times per year the respondent eats red meat(including beef, hamburger, pork or lamb).

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 1
MFCD11Y Specifications
Value Condition(s) Description Notes
0 MFC_11 = 0 Never  
MFC_11 * 365 MFC_11N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MFC_11 * 52 MFC_11N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MFC_11 * 12 MFC_11N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MFC_11 MFC_11N = 4 Reported number of times consumed per year  
9996 MFC_11N = NA Population exclusions NA
9999 Else   NS

2. MFCD12Y - Eats liver - times peryear

Variable name:
MFCD12Y

Based on:
MFC_12, MFC_12N

Description:
The number of times per year the respondent eats liver (includingall types of liver such as beef, veal, pork or chicken butexcluding liverwurst and liver pâté).

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 2
MFCD12Y Specifications
Value Condition(s) Description Notes
0 MFC_12 = 0 Never  
MFC_12 * 365 MFC_12N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MFC_12 * 52 MFC_12N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MFC_12 * 12 MFC_12N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MFC_12 MFC_12N = 4 Reported number of times consumed per year  
9996 MFC_12N = NA Population exclusions NA
9999 Else   NS

3. MFCD13Y - Eats other organ meats -times per year

Variable name:
MFCD13Y

Based on:
MFC_13, MFC_13N

Description:
The number of times per year the respondent eats other organ meats(including kidneys, heart or giblets).

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 3
MFCD13Y Specifications
Value Condition(s) Description Notes
0 MFC_13 = 0 Never  
MFC_13 * 365 MFC_13N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MFC_13 * 52 MFC_13N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MFC_13 * 12 MFC_13N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MFC_13 MFC_13N = 4 Reported number of times consumed per year  
9996 MFC_13N = NA Population exclusions NA
9999 Else   NS

4. MFCD14Y - Eats beef or pork hotdogs - times per year

Variable name:
MFCD14Y

Based on:
MFC_14, MFC_14N

Description:
The number of times per year the respondent eats beef or porkhotdogs.

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 4
MFCD14Y Specifications
Value Condition(s) Description Notes
0 MFC_14 = 0 Never  
MFC_14 * 365 MFC_14N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MFC_14 * 52 MFC_14N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MFC_14 * 12 MFC_14N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MFC_14 MFC_14N = 4 Reported number of times consumed per year  
9996 MFC_14N = NA Population exclusions NA
9999 Else   NS

5. MFCD15Y - Eats sausage or bacon-times per year

Variable name:
MFCD15Y

Based on:
MFC_15, MFC_15N

Description:
The number of times per year the respondent eats sausages or bacon(including all types of sausages such as breakfast, pepperoni andKielbassa but excluding low-fat, light or turkey varieties).

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 5
MFCD15Y Specifications
Value Condition(s) Description Notes
0 MFC_15 = 0 Never  
MFC_15 * 365 MFC_15N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MFC_15 * 52 MFC_15N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MFC_15 * 12 MFC_15N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MFC_15 MFC_15N = 4 Reported number of times consumed per year  
9996 MFC_15N = NA Population exclusions NA
9999 Else   NS

6. MFCD16Y - Eats salt water fish -times per year

Variable name:
MFCD16Y

Based on:
MFC_16, MFC_16N

Description:
The number of times per year the respondent eats salt water fish(including salmon, tuna or fish sticks).

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables. 

Table 6
MFCD16Y Specifications
Value Condition(s) Description Notes
0 MFC_16 = 0 Never  
MFC_16 * 365 MFC_16N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MFC_16 * 52 MFC_16N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MFC_16 * 12 MFC_16N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MFC_16 MFC_16N = 4 Reported number of times consumed per year  
9996 MFC_16N = NA Population exclusions NA
9999 Else   NS

7. MFCD17Y - Eats fresh water fish -times per year

Variable name:
MFCD17Y

Based on:
MFC_17, MFC_17N

Description:
The number of times per year the respondent eats fresh water fish(including trout, walleye or pickerel).

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 7
MFCD17Y Specifications
Value Condition(s) Description Notes
0 MFC_17 = 0 Never  
MFC_17 * 365 MFC_17N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MFC_17 * 52 MFC_17N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MFC_17 * 12 MFC_17N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MFC_17 MFC_17N = 4 Reported number of times consumed per year  
9996 MFC_17N = NA Population exclusions NA
9999 Else   NS

8. MFCD18Y - Eats shellfish - timesper year

Variable name:
MFCD18Y

Based on:
MFC_18, MFC_18N

Description:
The number of times per year the respondent eats shellfish(including shrimp, mussels, scallops, lobster, clams, oysters orcrab).

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 8
MFCD18Y Specifications
Value Condition(s) Description Notes
0 MFC_18 = 0 Never  
MFC_18 * 365 MFC_18N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MFC_18 * 52 MFC_181N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MFC_18 * 12 MFC_18N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MFC_18 MFC_18N = 4 Reported number of times consumed per year  
9996 MFC_18N = NA Population exclusions NA
9999 Else   NS

9. MFCD19Y - Eats eggs and egg dishes- times per year

Variable name:
MFCD19Y

Based on:
MFC_19, MFC_19N

Description:
The number of times per year the respondent eats eggs and eggdishes including the yolk such as omelettes, frittata or quiche(excluding all egg dishes made with only egg whites).

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 9
MFCD19Y Specifications
Value Condition(s) Description Notes
0 MFC_19 = 0 Never  
MFC_19 * 365 MFC_19N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MFC_19 * 52 MFC_19N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MFC_19 * 12 MFC_19N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MFC_19 MFC_19N = 4 Reported number of times consumed per year  
9996 MFC_19N = NA Population exclusions NA
9999 Else   NS

10. MFCD20Y - Eats cooked dried beans- times per year

Variable name:
MFCD20Y

Based on:
MFC_20, MFC_20N

Description:
The number of times per year the respondent eats cooked dried beans(including refried beans, baked beans, pea soup or kidney beans,excluding green and yellow beans).

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 10
MFCD20Y Specifications
Value Condition(s) Description Notes
0 MFC_20 = 0 Never  
MFC_20 * 365 MFC_20N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MFC_20 * 52 MFC_20N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MFC_20 * 12 MFC_20N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MFC_20 MFC_20N = 4 Reported number of times consumed per year  
9996 MFC_20N = NA Population exclusions NA
9999 Else   NS

11. MFCD21Y - Eats peanuts, walnuts,seeds or other nuts - times per year

Variable name:
MFCD21Y

Based on:
MFC_21, MFC_21N

Description:
The number of times per year the respondent eats peanuts, walnuts,seeds, or other nuts (excluding nut butters such as peanutbutter).

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 11
MFCD21Y Specifications
Value Condition(s) Description Notes
0 MFC_21 = 0 Never  
MFC_21 * 365 MFC_21N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MFC_21 * 52 MFC_21N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MFC_21 * 12 MFC_21N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MFC_21 MFC_21N = 4 Reported number of times consumed per year  
9996 MFC_21N = NA Population exclusions NA
9999 Else   NS

Oral Health (77 DVs)

1. OHCDELG - Eligibility - OralHealth

Variable name:
OHCDELG

Based on:
PHC_42K

Description:
This variable indicates whether the respondent was eligible for theOral Health component. As there are multiple reasons to be screenedout of this measure, the prevalence of screen outs by reason shouldnot be based on frequency counts for this variable.

Note:
Created in the Clinic Post-Verify process

Table 1
OHCDELG Specifications
Value Condition(s) Description Notes
9 PHC_42K = 1 Not eligible - acute or chronic condition  
1 Else Eligible  

2. OHEDAC01 - Total number of adultcrowns - code 1

Variable name:
OHEDAC01

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 1 (Sound - never decayed or restored) during the clinic dentalexaminations.  The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 2
OHEDAC01 Temporary Reformat
Value Condition(s) Description Notes
DVC01_11   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 11  
DVC01_12   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 12  
DVC01_13   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 13  
DVC01_14   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 14  
DVC01_15   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 15  
DVC01_16   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 16  
DVC01_17   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 17  
DVC01_21   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 21  
DVC01_22   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 22  
DVC01_23   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 23  
DVC01_24   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 24  
DVC01_25   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 25  
DVC01_26   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 26  
DVC01_27   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 27  
DVC01_31   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 31  
DVC01_32   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 32  
DVC01_33   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 33  
DVC01_34   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 34  
DVC01_35   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 35  
DVC01_36   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 36  
DVC01_37   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 37  
DVC01_41   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 41  
DVC01_42   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 42  
DVC01_43   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 43  
DVC01_44   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 44  
DVC01_45   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 45  
DVC01_46   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 46  
DVC01_47   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 47  

 

Table 2
OHEDAC01 Specifications
Value Condition(s) Description Notes
sum (of
DVC01_11-
DVC01_17
DVC01_21-
DVC01_27
DVC01_31-
DVC01_37
DVC01_41-
DVC01_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 1  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

3. OHEDAC02 - Total number of adultcrowns - code 2

Variable name:
OHEDAC02

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 2 (Sound - crown sealed, never decayed or otherwise restored)during the clinic dental examinations.  The probing portion ofthe oral health exam was completed by all respondents except thosemeeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant. 

Table 3
OHEDAC02 Temporary Reformat
Value Condition(s) Description Notes
DVC02_11   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 11  
DVC02_12   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 12  
DVC02_13   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 13  
DVC02_14   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 14  
DVC02_15   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 15  
DVC02_16   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 16  
DVC02_17   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 17  
DVC02_21   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 21  
DVC02_22   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 22  
DVC02_23   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 23  
DVC02_24   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 24  
DVC02_25   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 25  
DVC02_26   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 26  
DVC02_27   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 27  
DVC02_31   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 31  
DVC02_32   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 32  
DVC02_33   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 33  
DVC02_34   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 34  
DVC02_35   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 35  
DVC02_36   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 36  
DVC02_37   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 37  
DVC02_41   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 41  
DVC02_42   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 42  
DVC02_43   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 43  
DVC02_44   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 44  
DVC02_45   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 45  
DVC02_46   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 46  
DVC02_47   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 47  

 

Table 3
OHEDAC02 Specifications
Value Condition(s)  Description Notes
sum (of
DVC02_11-
DVC02_17
DVC02_21-
DVC02_27
DVC02_31-
DVC02_37
DVC02_41-
DVC02_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 2  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

4. OHEDAC03 - Total number of adultcrowns - code 3

Variable name:
OHEDAC03

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 3 (Missing - due to orthodontic treatment) during the clinicdental examinations.  The probing portion of the oral healthexam was completed by all respondents except those meeting theexclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 4
OHEDAC03 Temporary Reformat
Value Condition(s) Description Notes
DVC03_11   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 11  
DVC03_12   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 12  
DVC03_13   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 13  
DVC03_14   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 14  
DVC03_15   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 15  
DVC03_16   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 16  
DVC03_17   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 17  
DVC03_21   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 21  
DVC03_22   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 22  
DVC03_23   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 23  
DVC03_24   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 24  
DVC03_25   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 25  
DVC03_26   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 26  
DVC03_27   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 27  
DVC03_31   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 31  
DVC03_32   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 32  
DVC03_33   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 33  
DVC03_34   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 34  
DVC03_35   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 35  
DVC03_36   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 36  
DVC03_37   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 37  
DVC03_41   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 41  
DVC03_42   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 42  
DVC03_43   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 43  
DVC03_44   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 44  
DVC03_45   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 45  
DVC03_46   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 46  
DVC03_47   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 47  

 

Table 4
OHEDAC03 Specifications
Value Condition(s) Description Notes
sum (of
DVC03_11-
DVC03_17
DVC03_21-
DVC03_27
DVC03_31-
DVC03_37
DVC03_41-
DVC03_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 3  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

5. OHEDAC04 - Total number of adultcrowns - code 4

Variable name:
OHEDAC04

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 4 (Missing - due to trauma) during the clinic dentalexaminations.  The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant. 

Table 5
OHEDAC04 Temporary Reformat
Value Condition(s) Description Notes
DVC04_11   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 11  
DVC04_12   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 12  
DVC04_13   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 13  
DVC04_14   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 14  
DVC04_15   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 15  
DVC04_16   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 16  
DVC04_17   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 17  
DVC04_21   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 21  
DVC04_22   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 22  
DVC04_23   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 23  
DVC04_24   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 24  
DVC04_25   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 25  
DVC04_26   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 26  
DVC04_27   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 27  
DVC04_31   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 31  
DVC04_32   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 32  
DVC04_33   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 33  
DVC04_34   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 34  
DVC04_35   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 35  
DVC04_36   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 36  
DVC04_37   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 37  
DVC04_41   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 41  
DVC04_42   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 42  
DVC04_43   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 43  
DVC04_44   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 44  
DVC04_45   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 45  
DVC04_46   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 46  
DVC04_47   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 47  

 

Table 5
OHEDAC04 Specifications
Value Condition(s) Description Notes
sum (of
DVC04_11-
DVC04_17
DVC04_21-
DVC04_27
DVC04_31-
DVC04_37
DVC04_41-
DVC04_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 4  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

6. OHEDAC05 - Total number of adultcrowns - code 5

Variable name:
OHEDAC05

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 5 (Missing - due to caries or periodontal disease) during theclinic dental examinations.  The probing portion of the oralhealth exam was completed by all respondents except those meetingthe exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant. 

Table 6
OHEDAC05 Temporary Reformat
Value Condition(s) Description Notes
DVC05_11   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 11  
DVC05_12   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 12  
DVC05_13   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 13  
DVC05_14   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 14  
DVC05_15   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 15  
DVC05_16   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 16  
DVC05_17   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 17  
DVC05_21   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 21  
DVC05_22   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 22  
DVC05_23   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 23  
DVC05_24   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 24  
DVC05_25   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 25  
DVC05_26   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 26  
DVC05_27   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 27  
DVC05_31   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 31  
DVC05_32   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 32  
DVC05_33   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 33  
DVC05_34   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 34  
DVC05_35   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 35  
DVC05_36   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 36  
DVC05_37   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 37  
DVC05_41   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 41  
DVC05_42   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 42  
DVC05_43   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 43  
DVC05_44   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 44  
DVC05_45   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 45  
DVC05_46   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 46  
DVC05_47   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 47  

 

Table 6
OHEDAC05 Specifications
Value Condition(s) Description Notes
sum (of
DVC05_11-
DVC05_17
DVC05_21-
DVC05_27
DVC05_31-
DVC05_37
DVC05_41-
DVC05_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 5  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

7. OHEDAC06 - Total number of adultcrowns - code 6

Variable name:
OHEDAC06

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 6 (Unerupted tooth, congenitally missing or unexposed root)during the clinic dental examinations.  The probing portion ofthe oral health exam was completed by all respondents except thosemeeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 7
OHEDAC06 Temporary Reformat
Value Condition(s) Description Notes
DVC06_11   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 11  
DVC06_12   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 12  
DVC06_13   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 13  
DVC06_14   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 14  
DVC06_15   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 15  
DVC06_16   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 16  
DVC06_17   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 17  
DVC06_21   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 21  
DVC06_22   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 22  
DVC06_23   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 23  
DVC06_24   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 24  
DVC06_25   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 25  
DVC06_26   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 26  
DVC06_27   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 27  
DVC06_31   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 31  
DVC06_32   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 32  
DVC06_33   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 33  
DVC06_34   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 34  
DVC06_35   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 35  
DVC06_36   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 36  
DVC06_37   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 37  
DVC06_41   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 41  
DVC06_42   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 42  
DVC06_43   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 43  
DVC06_44   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 44  
DVC06_45   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 45  
DVC06_46   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 46  
DVC06_47   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 47  

 

Table 7
OHEDAC06 Specifications
Value Condition(s) Description Notes
sum (of
DVC06_11-
DVC06_17
DVC06_21-
DVC06_27
DVC06_31-
DVC06_37
DVC06_41-
DVC06_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 6  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

8. OHEDAC07 - Total number of adultcrowns - code 7

Variable name:
OHEDAC07

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 7 (Decayed severely) during the clinic dentalexaminations.  The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 8
OHEDAC07 Temporary Reformat
Value Condition(s) Description Notes
DVC07_11   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 11  
DVC07_12   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 12  
DVC07_13   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 13  
DVC07_14   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 14  
DVC07_15   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 15  
DVC07_16   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 16  
DVC07_17   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 17  
DVC07_21   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 21  
DVC07_22   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 22  
DVC07_23   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 23  
DVC07_24   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 24  
DVC07_25   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 25  
DVC07_26   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 26  
DVC07_27   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 27  
DVC07_31   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 31  
DVC07_32   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 32  
DVC07_33   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 33  
DVC07_34   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 34  
DVC07_35   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 35  
DVC07_36   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 36  
DVC07_37   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 37  
DVC07_41   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 41  
DVC07_42   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 42  
DVC07_43   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 43  
DVC07_44   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 44  
DVC07_45   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 45  
DVC07_46   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 46  
DVC07_47   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 47  

 

Table 8
OHEDAC07 Specifications
Value Condition(s) Description Notes
sum (of
DVC07_11-
DVC07_17
DVC07_21-
DVC07_27
DVC07_31-
DVC07_37
DVC07_41-
DVC07_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 7  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

9. OHEDAC08 - Total number of adultcrowns - code 8

Variable name:
OHEDAC08

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 8 (Decayed - pit and fissure caries) during the clinic dentalexaminations.  The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 9
OHEDAC08 Temporary Reformat
Value Condition(s) Description Notes
DVC08_11   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 11  
DVC08_12   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 12  
DVC08_13   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 13  
DVC08_14   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 14  
DVC08_15   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 15  
DVC08_16   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 16  
DVC08_17   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 17  
DVC08_21   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 21  
DVC08_22   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 22  
DVC08_23   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 23  
DVC08_24   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 24  
DVC08_25   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 25  
DVC08_26   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 26  
DVC08_27   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 27  
DVC08_31   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 31  
DVC08_32   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 32  
DVC08_33   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 33  
DVC08_34   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 34  
DVC08_35   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 35  
DVC08_36   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 36  
DVC08_37   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 37  
DVC08_41   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 41  
DVC08_42   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 42  
DVC08_43   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 43  
DVC08_44   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 44  
DVC08_45   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 45  
DVC08_46   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 46  
DVC08_47   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 47  

 

Table 9
OHEDAC08 Specifications
Value Condition(s) Description Notes
sum (of
DVC08_11-
DVC08_17
DVC08_21-
DVC08_27
DVC08_31-
DVC08_37
DVC08_41-
DVC08_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 8  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

10. OHEDAC09 - Total number of adultcrowns - code 9

Variable name:
OHEDAC09

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 9 (Decayed - smooth surface caries) during the clinic dentalexaminations.  The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant. 

Table 10
OHEDAC09 Temporary Reformat
Value Condition(s) Description Notes
DVC09_11   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 11  
DVC09_12   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 12  
DVC09_13   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 13  
DVC09_14   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 14  
DVC09_15   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 15  
DVC09_16   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 16  
DVC09_17   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 17  
DVC09_21   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 21  
DVC09_22   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 22  
DVC09_23   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 23  
DVC09_24   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 24  
DVC09_25   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 25  
DVC09_26   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 26  
DVC09_27   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 27  
DVC09_31   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 31  
DVC09_32   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 32  
DVC09_33   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 33  
DVC09_34   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 34  
DVC09_35   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 35  
DVC09_36   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 36  
DVC09_37   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 37  
DVC09_41   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 41  
DVC09_42   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 42  
DVC09_43   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 43  
DVC09_44   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 44  
DVC09_45   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 45  
DVC09_46   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 46  
DVC09_47   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 47  

 

Table 10
OHEDAC09 Specifications
Value Condition(s) Description Notes
sum (of
DVC09_11-
DVC09_17
DVC09_21-
DVC09_27
DVC09_31-
DVC09_37
DVC09_41-
DVC09_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 9  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

11. OHEDAC10 - Total number of adultcrowns - code 10

Variable name:
OHEDAC10

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 10 (Decayed - both smooth surface and pit and fissure caries)during the clinic dental examinations.  The probing portion ofthe oral health exam was completed by all respondents except thosemeeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant. 

Table 11
OHEDAC10 Temporary Reformat
Value Condition(s) Description Notes
DVC10_11   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 11  
DVC10_12   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 12  
DVC10_13   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 13  
DVC10_14   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 14  
DVC10_15   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 15  
DVC10_16   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 16  
DVC10_17   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 17  
DVC10_21   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 21  
DVC10_22   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 22  
DVC10_23   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 23  
DVC10_24   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 24  
DVC10_25   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 25  
DVC10_26   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 26  
DVC10_27   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 27  
DVC10_31   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 31  
DVC10_32   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 32  
DVC10_33   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 33  
DVC10_34   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 34  
DVC10_35   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 35  
DVC10_36   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 36  
DVC10_37   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 37  
DVC10_41   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 41  
DVC10_42   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 42  
DVC10_43   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 43  
DVC10_44   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 44  
DVC10_45   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 45  
DVC10_46   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 46  
DVC10_47   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 47  

 

Table 11
OHEDAC10 Specifications
Value Condition(s) Description Notes
sum (of
DVC10_11-
DVC10_17
DVC10_21-
DVC10_27
DVC10_31-
DVC10_37
DVC10_41-
DVC10_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 10  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

12. OHEDAC12 - Total number of adultcrowns - code 12

Variable name:
OHEDAC12

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 12 (Filled with amalgam, no other decay) during the clinicdental examinations.  The probing portion of the oral healthexam was completed by all respondents except those meeting theexclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 12
OHEDAC12 Temporary Reformat
Value Condition(s) Description Notes
DVC12_11   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 11  
DVC12_12   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 12  
DVC12_13   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 13  
DVC12_14   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 14  
DVC12_15   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 15  
DVC12_16   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 16  
DVC12_17   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 17  
DVC12_21   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 21  
DVC12_22   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 22  
DVC12_23   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 23  
DVC12_24   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 24  
DVC12_25   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 25  
DVC12_26   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 26  
DVC12_27   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 27  
DVC12_31   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 31  
DVC12_32   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 32  
DVC12_33   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 33  
DVC12_34   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 34  
DVC12_35   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 35  
DVC12_36   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 36  
DVC12_37   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 37  
DVC12_41   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 41  
DVC12_42   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 42  
DVC12_43   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 43  
DVC12_44   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 44  
DVC12_45   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 45  
DVC12_46   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 46  
DVC12_47   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 47  

 

Table 12
OHEDAC12 Specifications
Value Condition(s) Description Notes
sum (of
DVC12_11-
DVC12_17
DVC12_21-
DVC12_27
DVC12_31-
DVC12_37
DVC12_41-
DVC12_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 12  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

13. OHEDAC13 - Total number of adultcrowns - code 13

Variable name:
OHEDAC13

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 13 (Filled with other material (resin, GIC, inlay, crown), noother decay) during the clinic dental examinations.  Theprobing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 13
OHEDAC13 Temporary Reformat
Value Condition(s) Description Notes
DVC13_11   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 11  
DVC13_12   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 12  
DVC13_13   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 13  
DVC13_14   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 14  
DVC13_15   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 15  
DVC13_16   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 16  
DVC13_17   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 17  
DVC13_21   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 21  
DVC13_22   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 22  
DVC13_23   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 23  
DVC13_24   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 24  
DVC13_25   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 25  
DVC13_26   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 26  
DVC13_27   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 27  
DVC13_31   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 31  
DVC13_32   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 32  
DVC13_33   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 33  
DVC13_34   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 34  
DVC13_35   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 35  
DVC13_36   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 36  
DVC13_37   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 37  
DVC13_41   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 41  
DVC13_42   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 42  
DVC13_43   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 43  
DVC13_44   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 44  
DVC13_45   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 45  
DVC13_46   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 46  
DVC13_47   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 47  

 

Table 13
OHEDAC13 Specifications
Value Condition(s) Description Notes
sum (of
DVC13_11-
DVC13_17
DVC13_21-
DVC13_27
DVC13_31-
DVC13_37
DVC13_41-
DVC13_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 13  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

14. OHEDAC14 - Total number of adultcrowns - code 14

Variable name:
OHEDAC14

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 14 (Filled with amalgam and other material (resin, GIC, inlay,crown), no other decay) during the clinic dentalexaminations.  The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 14
OHEDAC14 Temporary Reformat
Value Condition(s) Description Notes
DVC14_11   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 11  
DVC14_12   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 12  
DVC14_13   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 13  
DVC14_14   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 14  
DVC14_15   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 15  
DVC14_16   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 16  
DVC14_17   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 17  
DVC14_21   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 21  
DVC14_22   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 22  
DVC14_23   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 23  
DVC14_24   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 24  
DVC14_25   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 25  
DVC14_26   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 26  
DVC14_27   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 27  
DVC14_31   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 31  
DVC14_32   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 32  
DVC14_33   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 33  
DVC14_34   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 34  
DVC14_35   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 35  
DVC14_36   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 36  
DVC14_37   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 37  
DVC14_41   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 41  
DVC14_42   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 42  
DVC14_43   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 43  
DVC14_44   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 44  
DVC14_45   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 45  
DVC14_46   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 46  
DVC14_47   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 47  

 

Table 14
OHEDAC14 Specifications
Value Condition(s) Description Notes

sum (of
DVC14_11-
DVC14_17
DVC14_21-
DVC14_27
DVC14_31-
DVC14_37
DVC14_41-
DVC14_47)

OHE_11 in (1 2 3)

Sum of all permanent (adult) crowns coded as 14

 

6

OHE_11 in (4 5)

Population exclusions

NA

9

OHE_11 > NA

At least one required question was not answered (don’tknow, refusal, not stated)

NS

9

Else

 

NS

 

15. OHEDAC15 - Total number of adultcrowns - code 15

Variable name:
OHEDAC15

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 15 (Filled with amalgam, no other decay, but filling isdefective and needs replacement) during the clinic dentalexaminations.  The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 15
OHEDAC15 Temporary Reformat
Value Condition(s) Description Notes
DVC15_11   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 11  
DVC15_12   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 12  
DVC15_13   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 13  
DVC15_14   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 14  
DVC15_15   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 15  
DVC15_16   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 16  
DVC15_17   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 17  
DVC15_21   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 21  
DVC15_22   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 22  
DVC15_23   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 23  
DVC15_24   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 24  
DVC15_25   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 25  
DVC15_26   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 26  
DVC15_27   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 27  
DVC15_31   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 31  
DVC15_32   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 32  
DVC15_33   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 33  
DVC15_34   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 34  
DVC15_35   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 35  
DVC15_36   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 36  
DVC15_37   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 37  
DVC15_41   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 41  
DVC15_42   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 42  
DVC15_43   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 43  
DVC15_44   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 44  
DVC15_45   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 45  
DVC15_46   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 46  
DVC15_47   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 47  

 

Table 15
OHEDAC15 Specifications
Value Condition(s) Description Notes
sum (of
DVC15_11-
DVC15_17
DVC15_21-
DVC15_27
DVC15_31-
DVC15_37
DVC15_41-
DVC15_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 15  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

16. OHEDAC16 - Total number of adultcrowns - code 16

Variable name:
OHEDAC16

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 16 (Filled with other material (resin, GIC, inlay, crown) butfilling is defective and needs replacement) during the clinicdental examinations.  The probing portion of the oral healthexam was completed by all respondents except those meeting theexclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant. 

Table 16
OHEDAC16 Temporary Reformat
Value Condition(s) Description Notes
DVC16_11   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 11  
DVC16_12   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 12  
DVC16_13   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 13  
DVC16_14   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 14  
DVC16_15   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 15  
DVC16_16   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 16  
DVC16_17   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 17  
DVC16_21   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 21  
DVC16_22   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 22  
DVC16_23   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 23  
DVC16_24   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 24  
DVC16_25   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 25  
DVC16_26   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 26  
DVC16_27   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 27  
DVC16_31   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 31  
DVC16_32   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 32  
DVC16_33   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 33  
DVC16_34   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 34  
DVC16_35   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 35  
DVC16_36   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 36  
DVC16_37   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 37  
DVC16_41   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 41  
DVC16_42   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 42  
DVC16_43   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 43  
DVC16_44   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 44  
DVC16_45   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 45  
DVC16_46   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 46  
DVC16_47   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 47  

 

Table 16
OHEDAC16 Specifications
Value Condition(s) Description Notes
sum (of
DVC16_11-
DVC16_17
DVC16_21-
DVC16_27
DVC16_31-
DVC16_37
DVC16_41-
DVC16_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 16  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else At least one required question was not answered (don’tknow, refusal, not stated) NS

 

17. OHEDAC17 - Total number of adultcrowns - code 17

Variable name:
OHEDAC17

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 17 (Filled with amalgam and other material (resin, GIC, inlay,crown) but filling is defective and needs replacement) during theclinic dental examinations.  The probing portion of the oralhealth exam was completed by all respondents except those meetingthe exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 17
OHEDAC17 Temporary Reformat
Value Condition(s) Description Notes
DVC17_11   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 11  
DVC17_12   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 12  
DVC17_13   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 13  
DVC17_14   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 14  
DVC17_15   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 15  
DVC17_16   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 16  
DVC17_17   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 17  
DVC17_21   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 21  
DVC17_22   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 22  
DVC17_23   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 23  
DVC17_24   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 24  
DVC17_25   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 25  
DVC17_26   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 26  
DVC17_27   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 27  
DVC17_31   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 31  
DVC17_32   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 32  
DVC17_33   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 33  
DVC17_34   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 34  
DVC17_35   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 35  
DVC17_36   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 36  
DVC17_37   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 37  
DVC17_41   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 41  
DVC17_42   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 42  
DVC17_43   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 43  
DVC17_44   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 44  
DVC17_45   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 45  
DVC17_46   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 46  
DVC17_47   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 47  

 

Table 17
OHEDAC17 Specifications
Value Condition(s) Description Notes
sum (of
DVC17_11-
DVC17_17
DVC17_21-
DVC17_27
DVC17_31-
DVC17_37
DVC17_41-
DVC17_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 17  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

18. OHEDAC18 - Total number of adultcrowns - code 18

Variable name:
OHEDAC18

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 18 (Bridge abutment, special crown or veneer) during the clinicdental examinations.  The probing portion of the oral healthexam was completed by all respondents except those meeting theexclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant. 

Table 18
OHEDAC18 Temporary Reformat
Value Condition(s) Description Notes
DVC18_11   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 11  
DVC18_12   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 12  
DVC18_13   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 13  
DVC18_14   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 14  
DVC18_15   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 15  
DVC18_16   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 16  
DVC18_17   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 17  
DVC18_21   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 21  
DVC18_22   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 22  
DVC18_23   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 23  
DVC18_24   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 24  
DVC18_25   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 25  
DVC18_26   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 26  
DVC18_27   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 27  
DVC18_31   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 31  
DVC18_32   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 32  
DVC18_33   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 33  
DVC18_34   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 34  
DVC18_35   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 35  
DVC18_36   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 36  
DVC18_37   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 37  
DVC18_41   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 41  
DVC18_42   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 42  
DVC18_43   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 43  
DVC18_44   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 44  
DVC18_45   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 45  
DVC18_46   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 46  
DVC18_47   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 47  

 

Table 18
OHEDAC18 Specifications
Value Condition(s) Description Notes
sum (of
DVC18_11-
DVC18_17
DVC18_21-
DVC18_27
DVC18_31-
DVC18_37
DVC18_41-
DVC18_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 18  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

19. OHEDAC19 - Total number of adultcrowns - code 19

Variable name:
OHEDAC19

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 19 (Implant) during the clinic dental examinations.  Theprobing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 19
OHEDAC19 Temporary Reformat
Value Condition(s) Description Notes
DVC19_11   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 11  
DVC19_12   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 12  
DVC19_13   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 13  
DVC19_14   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 14  
DVC19_15   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 15  
DVC19_16   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 16  
DVC19_17   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 17  
DVC19_21   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 21  
DVC19_22   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 22  
DVC19_23   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 23  
DVC19_24   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 24  
DVC19_25   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 25  
DVC19_26   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 26  
DVC19_27   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 27  
DVC19_31   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 31  
DVC19_32   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 32  
DVC19_33   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 33  
DVC19_34   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 34  
DVC19_35   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 35  
DVC19_36   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 36  
DVC19_37   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 37  
DVC19_41   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 41  
DVC19_42   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 42  
DVC19_43   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 43  
DVC19_44   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 44  
DVC19_45   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 45  
DVC19_46   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 46  
DVC19_47   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 47  

 

Table 19
OHEDAC19 Specifications
Value Condition(s) Description Notes
sum (of
DVC19_11-
DVC19_17
DVC19_21-
DVC19_27
DVC19_31-
DVC19_37
DVC19_41-
DVC19_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 19  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

20. OHEDAC20 - Total number of adultcrowns - code 20

Variable name:
OHEDAC20

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 20 (Fractured due to trauma) during the clinic dentalexaminations.  The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 20
OHEDAC20 Temporary Reformat
Value Condition(s) Description Notes
DVC20_11   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 11  
DVC20_12   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 12  
DVC20_13   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 13  
DVC20_14   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 14  
DVC20_15   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 15  
DVC20_16   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 16  
DVC20_17   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 17  
DVC20_21   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 21  
DVC20_22   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 22  
DVC20_23   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 23  
DVC20_24   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 24  
DVC20_25   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 25  
DVC20_26   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 26  
DVC20_27   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 27  
DVC20_31   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 31  
DVC20_32   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 32  
DVC20_33   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 33  
DVC20_34   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 34  
DVC20_35   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 35  
DVC20_36   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 36  
DVC20_37   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 37  
DVC20_41   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 41  
DVC20_42   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 42  
DVC20_43   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 43  
DVC20_44   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 44  
DVC20_45   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 45  
DVC20_46   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 46  
DVC20_47   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 47  

 

Table 20
OHEDAC20 Specifications
Value Condition(s) Description Notes
sum (of
DVC20_11-
DVC20_17
DVC20_21-
DVC20_27
DVC20_31-
DVC20_37
DVC20_41-
DVC20_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 20  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

21. OHEDAC21 - Total number of adultcrowns - code 21

Variable name:
OHEDAC21

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 21 (Other) during the clinic dental examinations.  Theprobing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 21
OHEDAC21 Temporary Reformat
Value Condition(s) Description Notes
DVC21_11   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 11  
DVC21_12   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 12  
DVC21_13   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 13  
DVC21_14   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 14  
DVC21_15   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 15  
DVC21_16   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 16  
DVC21_17   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 17  
DVC21_21   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 21  
DVC21_22   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 22  
DVC21_23   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 23  
DVC21_24   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 24  
DVC21_25   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 25  
DVC21_26   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 26  
DVC21_27   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 27  
DVC21_31   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 31  
DVC21_32   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 32  
DVC21_33   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 33  
DVC21_34   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 34  
DVC21_35   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 35  
DVC21_36   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 36  
DVC21_37   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 37  
DVC21_41   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 41  
DVC21_42   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 42  
DVC21_43   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 43  
DVC21_44   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 44  
DVC21_45   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 45  
DVC21_46   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 46  
DVC21_47   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 47  

 

Table 21
OHEDAC21 Specifications
Value Condition(s) Description Notes
sum (of
DVC21_11-
DVC21_17
DVC21_21-
DVC21_27
DVC21_31-
DVC21_37
DVC21_41-
DVC21_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 21  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

22. OHEDAR01 - Total number of adultroots - code 1

Variable name:
OHEDAR01

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as1 (Sound - never decayed or restored) during the clinic dentalexaminations.  The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant. 

Table 22
OHEDAR01 Temporary Reformat
Value Condition(s) Description Notes
DVR01_11   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 11  
DVR01_12   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 12  
DVR01_13   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 13  
DVR01_14   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 14  
DVR01_15   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 15  
DVR01_16   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 16  
DVR01_17   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 17  
DVR01_21   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 21  
DVR01_22   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 22  
DVR01_23   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 23  
DVR01_24   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 24  
DVR01_25   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 25  
DVR01_26   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 26  
DVR01_27   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 27  
DVR01_31   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 31  
DVR01_32   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 32  
DVR01_33   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 33  
DVR01_34   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 34  
DVR01_35   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 35  
DVR01_36   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 36  
DVR01_37   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 37  
DVR01_41   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 41  
DVR01_42   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 42  
DVR01_43   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 43  
DVR01_44   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 44  
DVR01_45   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 45  
DVR01_46   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 46  
DVR01_47   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 47  

 

Table 22
OHEDAR01 Specifications
Value Condition(s) Description Notes
sum (of
DVR01_11-
DVR01_17
DVR01_21-
DVR01_27
DVR01_31-
DVR01_37
DVR01_41-
DVR01_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 1  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

23. OHEDAR03 - Total number of adultroots - code 3

Variable name:
OHEDAR03

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as3 (Missing - due to orthodontic treatment) during the clinic dentalexaminations.  The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant. 

Table 23
OHEDAR03 Temporary Reformat
Value Condition(s) Description Notes
DVR03_11   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 11  
DVR03_12   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 12  
DVR03_13   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 13  
DVR03_14   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 14  
DVR03_15   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 15  
DVR03_16   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 16  
DVR03_17   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 17  
DVR03_21   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 21  
DVR03_22   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 22  
DVR03_23   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 23  
DVR03_24   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 24  
DVR03_25   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 25  
DVR03_26   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 26  
DVR03_27   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 27  
DVR03_31   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 31  
DVR03_32   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 32  
DVR03_33   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 33  
DVR03_34   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 34  
DVR03_35   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 35  
DVR03_36   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 36  
DVR03_37   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 37  
DVR03_41   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 41  
DVR03_42   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 42  
DVR03_43   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 43  
DVR03_44   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 44  
DVR03_45   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 45  
DVR03_46   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 46  
DVR03_47   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 47  

 

Table 23
OHEDAR03 Specifications
Value Condition(s) Description Notes
sum (of
DVR03_11-
DVR03_17
DVR03_21-
DVR03_27
DVR03_31-
DVR03_37
DVR03_41-
DVR03_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 3  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

24. OHEDAR04 - Total number of adultroots - code 4

Variable name:
OHEDAR04

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as4 (Missing - due to trauma) during the clinic dentalexaminations.  The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 24
OHEDAR04 Temporary Reformat
Value Condition(s) Description Notes
DVR04_11   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 11  
DVR04_12   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 12  
DVR04_13   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 13  
DVR04_14   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 14  
DVR04_15   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 15  
DVR04_16   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 16  
DVR04_17   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 17  
DVR04_21   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 21  
DVR04_22   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 22  
DVR04_23   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 23  
DVR04_24   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 24  
DVR04_25   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 25  
DVR04_26   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 26  
DVR04_27   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 27  
DVR04_31   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 31  
DVR04_32   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 32  
DVR04_33   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 33  
DVR04_34   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 34  
DVR04_35   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 35  
DVR04_36   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 36  
DVR04_37   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 37  
DVR04_41   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 41  
DVR04_42   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 42  
DVR04_43   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 43  
DVR04_44   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 44  
DVR04_45   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 45  
DVR04_46   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 46  
DVR04_47   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 47  

 

Table 24
OHEDAR04 Specifications
Value Condition(s) Description Notes
sum (of
DVR04_11-
DVR04_17
DVR04_21-
DVR04_27
DVR04_31-
DVR04_37
DVR04_41-
DVR04_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 4  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

25. OHEDAR05 - Total number of adultroots - code 5

Variable name:
OHEDAR05

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as5 (Missing - due to caries or periodontal disease) during theclinic dental examinations.  The probing portion of the oralhealth exam was completed by all respondents except those meetingthe exclusion criteria:

  1.   Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated bycreating arrays for each of 4 quadrants and also creating arraysfor the temporary variables used to maintain a total count for eachquadrant.

Table 25
OHEDAR05 Temporary Reformat
Value Condition(s) Description Notes
DVR05_11   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 11  
DVR05_12   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 12  
DVR05_13   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 13  
DVR05_14   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 14  
DVR05_15   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 15  
DVR05_16   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 16  
DVR05_17   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 17  
DVR05_21   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 21  
DVR05_22   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 22  
DVR05_23   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 23  
DVR05_24   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 24  
DVR05_25   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 25  
DVR05_26   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 26  
DVR05_27   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 27  
DVR05_31   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 31  
DVR05_32   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 32  
DVR05_33   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 33  
DVR05_34   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 34  
DVR05_35   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 35  
DVR05_36   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 36  
DVR05_37   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 37  
DVR05_41   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 41  
DVR05_42   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 42  
DVR05_43   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 43  
DVR05_44   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 44  
DVR05_45   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 45  
DVR05_46   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 46  
DVR05_47   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 47  

 

Table 25
OHEDAR05 Specifications
Value Condition(s) Description Notes
sum (of
DVR05_11-
DVR05_17
DVR05_21-
DVR05_27
DVR05_31-
DVR05_37
DVR05_41-
DVR05_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 5  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

26. OHEDAR06 - Total number of adultroots - code 6

Variable name:
OHEDAR06

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as6 (Unerupted tooth, congenitally missing or unexposed root) duringthe clinic dental examinations.  The probing portion of theoral health exam was completed by all respondents except thosemeeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 26
OHEDAR06 Temporary Reformat
Value Condition(s) Description Notes
DVR06_11   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 11  
DVR06_12   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 12  
DVR06_13   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 13  
DVR06_14   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 14  
DVR06_15   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 15  
DVR06_16   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 16  
DVR06_17   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 17  
DVR06_21   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 21  
DVR06_22   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 22  
DVR06_23   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 23  
DVR06_24   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 24  
DVR06_25   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 25  
DVR06_26   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 26  
DVR06_27   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 27  
DVR06_31   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 31  
DVR06_32   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 32  
DVR06_33   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 33  
DVR06_34   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 34  
DVR06_35   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 35  
DVR06_36   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 36  
DVR06_37   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 37  
DVR06_41   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 41  
DVR06_42   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 42  
DVR06_43   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 43  
DVR06_44   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 44  
DVR06_45   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 45  
DVR06_46   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 46  
DVR06_47   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 47  

 

Table 26
OHEDAR06 Specifications
Value Condition(s) Description Notes
sum (of
DVR06_11-
DVR06_17
DVR06_21-
DVR06_27
DVR06_31-
DVR06_37
DVR06_41-
DVR06_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 6  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

27. OHEDAR07 - Total number of adultroots - code 7

Variable name:
OHEDAR07

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47 

Description:
This variable is a count of all permanent (adult) roots recorded as7 (Decayed severely) during the clinic dental examinations. The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 27
OHEDAR07 Temporary Reformat
Value Condition(s) Description Notes
DVR07_11   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 11  
DVR07_12   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 12  
DVR07_13   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 13  
DVR07_14   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 14  
DVR07_15   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 15  
DVR07_16   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 16  
DVR07_17   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 17  
DVR07_21   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 21  
DVR07_22   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 22  
DVR07_23   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 23  
DVR07_24   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 24  
DVR07_25   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 25  
DVR07_26   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 26  
DVR07_27   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 27  
DVR07_31   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 31  
DVR07_32   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 32  
DVR07_33   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 33  
DVR07_34   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 34  
DVR07_35   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 35  
DVR07_36   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 36  
DVR07_37   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 37  
DVR07_41   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 41  
DVR07_42   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 42  
DVR07_43   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 43  
DVR07_44   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 44  
DVR07_45   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 45  
DVR07_46   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 46  
DVR07_47   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 47  

 

Table 27
OHEDAR07 Specifications
Value Condition(s) Description Notes
sum (of
DVR07_11-
DVR07_17
DVR07_21-
DVR07_27
DVR07_31-
DVR07_37
DVR07_41-
DVR07_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 7  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

28. OHEDAR11 - Total number of adultroots - code 11

Variable name:
OHEDAR11

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as11 (Decayed - smooth surface caries) during the clinic dentalexaminations.  The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 28
OHEDAR11 Temporary Reformat
Value Condition(s) Description Notes
DVR11_11   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 11  
DVR11_12   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 12  
DVR11_13   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 13  
DVR11_14   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 14  
DVR11_15   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 15  
DVR11_16   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 16  
DVR11_17   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 17  
DVR11_21   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 21  
DVR11_22   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 22  
DVR11_23   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 23  
DVR11_24   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 24  
DVR11_25   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 25  
DVR11_26   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 26  
DVR11_27   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 27  
DVR11_31   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 31  
DVR11_32   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 32  
DVR11_33   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 33  
DVR11_34   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 34  
DVR11_35   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 35  
DVR11_36   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 36  
DVR11_37   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 37  
DVR11_41   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 41  
DVR11_42   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 42  
DVR11_43   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 43  
DVR11_44   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 44  
DVR11_45   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 45  
DVR11_46   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 46  
DVR11_47   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 47  

 

Table 28
OHEDAR11 Specifications
Value Condition(s) Description Notes
sum (of
DVR11_11-
DVR11_17
DVR11_21-
DVR11_27
DVR11_31-
DVR11_37
DVR11_41-
DVR11_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 11  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

29. OHEDAR12 - Total number of adultroots - code 12

Variable name:
OHEDAR12

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as12 (Filled with amalgam, no other decay) during the clinic dentalexaminations.  The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 29
OHEDAR12 Temporary Reformat
Value Condition(s) Description Notes
DVR12_11   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 11  
DVR12_12   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 12  
DVR12_13   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 13  
DVR12_14   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 14  
DVR12_15   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 15  
DVR12_16   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 16  
DVR12_17   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 17  
DVR12_21   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 21  
DVR12_22   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 22  
DVR12_23   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 23  
DVR12_24   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 24  
DVR12_25   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 25  
DVR12_26   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 26  
DVR12_27   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 27  
DVR12_31   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 31  
DVR12_32   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 32  
DVR12_33   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 33  
DVR12_34   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 34  
DVR12_35   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 35  
DVR12_36   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 36  
DVR12_37   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 37  
DVR12_41   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 41  
DVR12_42   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 42  
DVR12_43   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 43  
DVR12_44   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 44  
DVR12_45   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 45  
DVR12_46   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 46  
DVR12_47   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 47  

 

Table 29
OHEDAR12 Specifications
Value Condition(s) Description Notes
sum (of
DVR12_11-
DVR12_17
DVR12_21-
DVR12_27
DVR12_31-
DVR12_37
DVR12_41-
DVR12_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 12  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

30. OHEDAR13 - Total number of adultroots - code 13

Variable name:
OHEDAR13

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as13 (Filled with other material, (resin, GIC, inlay, crown), noother decay) during the clinic dental examinations.  Theprobing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 30
OHEDAR13 Temporary Reformat
Value Condition(s) Description Notes
DVR13_11   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 11  
DVR13_12   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 12  
DVR13_13   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 13  
DVR13_14   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 14  
DVR13_15   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 15  
DVR13_16   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 16  
DVR13_17   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 17  
DVR13_21   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 21  
DVR13_22   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 22  
DVR13_23   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 23  
DVR13_24   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 24  
DVR13_25   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 25  
DVR13_26   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 26  
DVR13_27   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 27  
DVR13_31   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 31  
DVR13_32   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 32  
DVR13_33   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 33  
DVR13_34   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 34  
DVR13_35   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 35  
DVR13_36   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 36  
DVR13_37   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 37  
DVR13_41   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 41  
DVR13_42   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 42  
DVR13_43   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 43  
DVR13_44   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 44  
DVR13_45   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 45  
DVR13_46   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 46  
DVR13_47   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 47  

 

Table 30
OHEDAR13 Specifications
Value Condition(s) Description Notes
sum (of
DVR13_11-
DVR13_17
DVR13_21-
DVR13_27
DVR13_31-
DVR13_37
DVR13_41-
DVR13_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 13  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

31. OHEDAR14 - Total number of adultroots - code 14

Variable name:
OHEDAR14

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as14 (Filled with amalgam and other material, (resin, GIC, inlay,crown), no other decay) during the clinic dentalexaminations.  The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 31
OHEDAR14 Temporary Reformat
Value Condition(s) Description Notes
DVR14_11   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 11  
DVR14_12   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 12  
DVR14_13   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 13  
DVR14_14   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 14  
DVR14_15   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 15  
DVR14_16   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 16  
DVR14_17   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 17  
DVR14_21   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 21  
DVR14_22   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 22  
DVR14_23   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 23  
DVR14_24   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 24  
DVR14_25   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 25  
DVR14_26   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 26  
DVR14_27   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 27  
DVR14_31   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 31  
DVR14_32   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 32  
DVR14_33   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 33  
DVR14_34   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 34  
DVR14_35   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 35  
DVR14_36   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 36  
DVR14_37   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 37  
DVR14_41   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 41  
DVR14_42   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 42  
DVR14_43   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 43  
DVR14_44   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 44  
DVR14_45   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 45  
DVR14_46   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 46  
DVR14_47   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 47  

 

Table 31
OHEDAR14 Specifications
Value Condition(s) Description Notes
sum (of
DVR14_11-
DVR14_17
DVR14_21-
DVR14_27
DVR14_31-
DVR14_37
DVR14_41-
DVR14_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 14  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

32. OHEDAR15 - Total number of adultroots - code 15

Variable name:
OHEDAR15

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as15 (Filled with amalgam, no other decay, but filling is defectiveand needs replacement) during the clinic dental examinations. The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 32
OHEDAR15 Temporary Reformat
Value Condition(s) Description Notes
DVR15_11   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 11  
DVR15_12   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 12  
DVR15_13   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 13  
DVR15_14   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 14  
DVR15_15   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 15  
DVR15_16   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 16  
DVR15_17   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 17  
DVR15_21   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 21  
DVR15_22   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 22  
DVR15_23   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 23  
DVR15_24   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 24  
DVR15_25   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 25  
DVR15_26   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 26  
DVR15_27   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 27  
DVR15_31   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 31  
DVR15_32   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 32  
DVR15_33   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 33  
DVR15_34   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 34  
DVR15_35   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 35  
DVR15_36   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 36  
DVR15_37   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 37  
DVR15_41   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 41  
DVR15_42   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 42  
DVR15_43   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 43  
DVR15_44   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 44  
DVR15_45   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 45  
DVR15_46   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 46  
DVR15_47   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 47  

 

Table 32
OHEDAR15 Specifications
Value Condition(s) Description Notes
sum (of
DVR15_11-
DVR15_17
DVR15_21-
DVR15_27
DVR15_31-
DVR15_37
DVR15_41-
DVR15_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 15  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

33. OHEDAR16 - Total number of adultroots - code 16

Variable name:
OHEDAR16

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as16 (Filled with other material (resin, GIC, inlay, crown) butfilling is defective and needs replacement) during the clinicdental examinations.  The probing portion of the oral healthexam was completed by all respondents except those meeting theexclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 33
OHEDAR16 Temporary Reformat
Value Condition(s) Description Notes
DVR16_11   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 11  
DVR16_12   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 12  
DVR16_13   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 13  
DVR16_14   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 14  
DVR16_15   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 15  
DVR16_16   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 16  
DVR16_17   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 17  
DVR16_21   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 21  
DVR16_22   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 22  
DVR16_23   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 23  
DVR16_24   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 24  
DVR16_25   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 25  
DVR16_26   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 26  
DVR16_27   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 27  
DVR16_31   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 31  
DVR16_32   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 32  
DVR16_33   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 33  
DVR16_34   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 34  
DVR16_35   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 35  
DVR16_36   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 36  
DVR16_37   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 37  
DVR16_41   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 41  
DVR16_42   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 42  
DVR16_43   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 43  
DVR16_44   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 44  
DVR16_45   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 45  
DVR16_46   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 46  
DVR16_47   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 47  

 

Table 33
OHEDAR16 Specifications
Value Condition(s) Description Notes
sum (of
DVR16_11-
DVR16_17
DVR16_21-
DVR16_27
DVR16_31-
DVR16_37
DVR16_41-
DVR16_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 16  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

34. OHEDAR17 - Total number of adultroots - code 17

Variable name:
OHEDAR17

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as17 (Filled with amalgam and other material (resin, GIC, inlay,crown) but filling is defective and needs replacement) during theclinic dental examinations.  The probing portion of the oralhealth exam was completed by all respondents except those meetingthe exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 34
OHEDAR17 Temporary Reformat
Value Condition(s) Description Notes
DVR17_11   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 11  
DVR17_12   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 12  
DVR17_13   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 13  
DVR17_14   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 14  
DVR17_15   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 15  
DVR17_16   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 16  
DVR17_17   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 17  
DVR17_21   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 21  
DVR17_22   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 22  
DVR17_23   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 23  
DVR17_24   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 24  
DVR17_25   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 25  
DVR17_26   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 26  
DVR17_27   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 27  
DVR17_31   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 31  
DVR17_32   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 32  
DVR17_33   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 33  
DVR17_34   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 34  
DVR17_35   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 35  
DVR17_36   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 36  
DVR17_37   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 37  
DVR17_41   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 41  
DVR17_42   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 42  
DVR17_43   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 43  
DVR17_44   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 44  
DVR17_45   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 45  
DVR17_46   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 46  
DVR17_47   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 47  

 

Table 34
OHEDAR17 Specifications
Value Condition(s) Description Notes
sum (of
DVR17_11-
DVR17_17
DVR17_21-
DVR17_27
DVR17_31-
DVR17_37
DVR17_41-
DVR17_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 17  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

35. OHEDAR19 - Total number of adultroots - code 19

Variable name:
OHEDAR19

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as19 (Implant) during the clinic dental examinations.  Theprobing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:This variable is calculated by creatingarrays for each of 4 quadrants and also creating arrays for thetemporary variables used to maintain a total count for eachquadrant.

Table 35
OHEDAR19 Temporary Reformat
Value Condition(s) Description Notes
DVR19_11   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 11  
DVR19_12   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 12  
DVR19_13   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 13  
DVR19_14   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 14  
DVR19_15   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 15  
DVR19_16   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 16  
DVR19_17   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 17  
DVR19_21   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 21  
DVR19_22   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 22  
DVR19_23   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 23  
DVR19_24   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 24  
DVR19_25   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 25  
DVR19_26   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 26  
DVR19_27   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 27  
DVR19_31   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 31  
DVR19_32   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 32  
DVR19_33   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 33  
DVR19_34   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 34  
DVR19_35   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 35  
DVR19_36   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 36  
DVR19_37   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 37  
DVR19_41   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 41  
DVR19_42   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 42  
DVR19_43   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 43  
DVR19_44   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 44  
DVR19_45   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 45  
DVR19_46   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 46  
DVR19_47   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 47  

 

Table 35
OHEDAR19 Specifications
Value Condition(s) Description Notes
sum (of
DVR19_11-
DVR19_17
DVR19_21-
DVR19_27
DVR19_31-
DVR19_37
DVR19_41-
DVR19_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 19  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

36. OHEDAR20 - Total number of adultroots - code 20

Variable name:
OHEDAR20

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as20 (Fractured due to trauma) during the clinic dentalexaminations.  The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 36
OHEDAR20 Temporary Reformat
Value Condition(s) Description Notes
DVR20_11   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 11  
DVR20_12   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 12  
DVR20_13   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 13  
DVR20_14   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 14  
DVR20_15   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 15  
DVR20_16   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 16  
DVR20_17   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 17  
DVR20_21   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 21  
DVR20_22   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 22  
DVR20_23   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 23  
DVR20_24   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 24  
DVR20_25   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 25  
DVR20_26   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 26  
DVR20_27   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 27  
DVR20_31   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 31  
DVR20_32   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 32  
DVR20_33   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 33  
DVR20_34   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 34  
DVR20_35   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 35  
DVR20_36   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 36  
DVR20_37   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 37  
DVR20_41   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 41  
DVR20_42   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 42  
DVR20_43   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 43  
DVR20_44   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 44  
DVR20_45   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 45  
DVR20_46   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 46  
DVR20_47   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 47  

 

Table 36
OHEDAR20 Specifications
Value Condition(s) Description Notes
sum (of
DVR20_11-
DVR20_17
DVR20_21-
DVR20_27
DVR20_31-
DVR20_37
DVR20_41-
DVR20_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 20  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

37. OHEDAR21 - Total number of adultroots - code 21

Variable name:
OHEDAR21

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as21 (Other) during the clinic dental examinations.  The probingportion of the oral health exam was completed by all respondentsexcept those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 37
OHEDAR21 Temporary Reformat
Value Condition(s) Description Notes
DVR21_11   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 11  
DVR21_12   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 12  
DVR21_13   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 13  
DVR21_14   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 14  
DVR21_15   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 15  
DVR21_16   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 16  
DVR21_17   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 17  
DVR21_21   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 21  
DVR21_22   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 22  
DVR21_23   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 23  
DVR21_24   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 24  
DVR21_25   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 25  
DVR21_26   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 26  
DVR21_27   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 27  
DVR21_31   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 31  
DVR21_32   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 32  
DVR21_33   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 33  
DVR21_34   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 34  
DVR21_35   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 35  
DVR21_36   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 36  
DVR21_37   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 37  
DVR21_41   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 41  
DVR21_42   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 42  
DVR21_43   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 43  
DVR21_44   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 44  
DVR21_45   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 45  
DVR21_46   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 46  
DVR21_47   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 47  

 

Table 37
OHEDAR21 Specifications
Value Condition(s) Description Notes
sum (of
DVR21_11-
DVR21_17
DVR21_21-
DVR21_27
DVR21_31-
DVR21_37
DVR21_41-
DVR21_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 21  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
9 Else   NS

 

38. OHEDCS01 - Calculus score recode -teeth 17 and 16

Variable name:
OHEDCS01

Based on:
OHE_32C1

Description:
This variable takes the original calculus score for teeth 17 and 16which was recorded using a scale from 1 to 4 during the clinicdental examinations and recodes the score as a scale from 0 to3. 

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 38
OHEDCS01 Specifications
Value Condition(s) Description Notes
6 OHE_32C1 = NA Population exclusions NA
9 (OHE_32C1 = DK, RF, NS) At least one required question was not answered (don’tknow, refusal, not stated) NS
0 OHE_32C1 = 1 No calculus  
1 OHE_32C1 = 2 Less than 1/3 of surface covered  
2 OHE_32C1 = 3 1/3 to 2/3 of surface covered  
3 OHE_32C1 = 4 More than 2/3 of surface covered  

39. OHEDCS02 - Calculus score recode -tooth 11

Variable name:
OHEDCS02

Based on:
OHE_32C2

Description:
This variable takes the original calculus score for tooth 11 whichwas recorded using a scale from 1 to 4 during the clinic dentalexaminations and recodes the score as a scale from 0 to 3.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 39
OHEDCS02 Specifications
Value Condition(s) Description Notes
6 OHE_32C2 = NA Population exclusions NA
9 (OHE_32C2 = DK, RF, NS) At least one required question was not answered (don’tknow, refusal, not stated) NS
0 OHE_32C2 = 1 No calculus  
1 OHE_32C2 = 2 Less than 1/3 of surface covered  
2 OHE_32C2 = 3 1/3 to 2/3 of surface covered  
3 OHE_32C2 = 4 More than 2/3 of surface covered  

40. OHEDCS03 - Calculus score recode -teeth 26 and 27

Variable name:
OHEDCS03

Based on:
OHE_32C3

Description:
This variable takes the original calculus score for teeth 26 and 27which was recorded using a scale from 1 to 4 during the clinicdental examinations and recodes the score as a scale from 0 to3.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 40
OHEDCS03 Specifications
Value Condition(s) Description Notes
6 OHE_32C3 = NA Population exclusions NA
9 (OHE_32C3 = DK, RF, NS) At least one required question was not answered (don’tknow, refusal, not stated) NS
0 OHE_32C3 = 1 No calculus  
1 OHE_32C3 = 2 Less than 1/3 of surface covered  
2 OHE_32C3 = 3 1/3 to 2/3 of surface covered  
3 OHE_32C3 = 4 More than 2/3 of surface covered  

41. OHEDCS04 - Calculus score recode -teeth 37 and 36

Variable name:
OHEDCS04

Based on:
OHE_32C4

Description:
This variable takes the original calculus score for teeth 37 and 36which was recorded using a scale from 1 to 4 during the clinicdental examinations and recodes the score as a scale from 0 to3.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 41
OHEDCS04 Specifications
Value Condition(s) Description Notes
6 OHE_32C4 = NA Population exclusions NA
9 (OHE_32C4 = DK, RF, NS) At least one required question was not answered (don’tknow, refusal, not stated) NS
0 OHE_32C4 = 1 No calculus  
1 OHE_32C4 = 2 Less than 1/3 of surface covered  
2 OHE_32C4 = 3 1/3 to 2/3 of surface covered  
3 OHE_32C4 = 4 More than 2/3 of surface covered  

42. OHEDCS05 - Calculus score recode -tooth 31

Variable name:
OHEDCS05

Based on:
OHE_32C5

Description:
This variable takes the original calculus score for tooth 31 whichwas recorded using a scale from 1 to 4 during the clinic dentalexaminations and recodes the score as a scale from 0 to 3.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 42
OHEDCS05 Specifications
Value Condition(s) Description Notes
6 OHE_32C5 = NA Population exclusions NA
9 (OHE_32C5 = DK, RF, NS) At least one required question was not answered (don’tknow, refusal, not stated) NS
0 OHE_32C5 = 1 No calculus  
1 OHE_32C5 = 2 Less than 1/3 of surface covered  
2 OHE_32C5 = 3 1/3 to 2/3 of surface covered  
3 OHE_32C5 = 4 More than 2/3 of surface covered  

43. OHEDCS06 - Calculus score recode -teeth 46 and 47

Variable name:
OHEDCS06

Based on:
OHE_32C6

Description:
This variable takes the original calculus score for teeth 46 and 47which was recorded using a scale from 1 to 4 during the clinicdental examinations and recodes the score as a scale from 0 to3.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 43
OHEDCS06 Specifications
Value Condition(s) Description Notes
6 OHE_32C6 = NA Population exclusions NA
9 (OHE_32C6 = DK, RF, NS) At least one required question was not answered (don’tknow, refusal, not stated) NS
0 OHE_32C6 = 1 No calculus  
1 OHE_32C6 = 2 Less than 1/3 of surface covered  
2 OHE_32C6 = 3 1/3 to 2/3 of surface covered  
3 OHE_32C6 = 4 More than 2/3 of surface covered  

44. OHEDDS01 - Debris score recode -teeth 17 and 16

Variable name:
OHEDDS01

Based on:
OHE_32D1

Description:
This variable takes the original debris score for teeth 17 and 16which was recorded using a scale from 1 to 5 during the clinicdental examinations and recodes the score as a scale from 0 to4.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 44
OHEDDS01 Specifications
Value Condition(s) Description Notes
6 OHE_32D1 = NA Population exclusions NA
9 (OHE_32D1 = DK, RF, NS) At least one required question was not answered (don’tknow, refusal, not stated) NS
0 OHE_32D1 = 1 No soft debris or stain  
1 OHE_32D1 = 2 Less than 1/3 of surface covered  
2 OHE_32D1 = 3 1/3 to 2/3 of surface covered  
3 OHE_32D1 = 4 More than 2/3 of surface covered  
4 OHE_32D1 = 5 Teeth missing  

45. OHEDDS02 - Debris score recode -tooth 11

Variable name:
OHEDDS02

Based on:
OHE_32D2

Description:
This variable takes the original debris score for tooth 11 whichwas recorded using a scale from 1 to 5 during the clinic dentalexaminations and recodes the score as a scale from 0 to 4.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 45
OHEDDS02 Specifications
Value Condition(s) Description Notes
6 OHE_32D2 = NA Population exclusions NA
9 (OHE_32D2 = DK, RF, NS) At least one required question was not answered (don’tknow, refusal, not stated) NS
0 OHE_32D2 = 1 No soft debris or stain  
1 OHE_32D2 = 2 Less than 1/3 of surface covered  
2 OHE_32D2 = 3 1/3 to 2/3 of surface covered  
3 OHE_32D2 = 4 More than 2/3 of surface covered  
4 OHE_32D2 = 5 Teeth missing  

46. OHEDDS03 - Debris score recode -teeth 26 and 27

Variable name:
OHEDDS03

Based on:
OHE_32D3

Description:
This variable takes the original debris score for teeth 26 and 27which was recorded using a scale from 1 to 5 during the clinicdental examinations and recodes the score as a scale from 0 to4.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 46
OHEDDS03 Specifications
Value Condition(s) Description Notes
6 OHE_32D3 = NA Population exclusions NA
9 (OHE_32D3 = DK, RF, NS) At least one required question was not answered (don’tknow, refusal, not stated) NS
0 OHE_32D3 = 1 No soft debris or stain  
1 OHE_32D3 = 2 Less than 1/3 of surface covered  
2 OHE_32D3 = 3 1/3 to 2/3 of surface covered  
3 OHE_32D3 = 4 More than 2/3 of surface covered  
4 OHE_32D3 = 5 Teeth missing  

47. OHEDDS04 - Debris score recode -teeth 37 and 36

Variable name:
OHEDDS04

Based on:
OHE_32D4

Description:
This variable takes the original debris score for teeth 37 and 36which was recorded using a scale from 1 to 5 during the clinicdental examinations and recodes the score as a scale from 0 to4.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 47
OHEDDS04 Specifications
Value Condition(s) Description Notes
6 OHE_32D4 = NA Population exclusions NA
9 (OHE_32D4 = DK, RF, NS) At least one required question was not answered (don’tknow, refusal, not stated) NS
0 OHE_32D4 = 1 No soft debris or stain  
1 OHE_32D4 = 2 Less than 1/3 of surface covered  
2 OHE_32D4 = 3 1/3 to 2/3 of surface covered  
3 OHE_32D4 = 4 More than 2/3 of surface covered  
4 OHE_32D4 = 5 Teeth missing  

48. OHEDDS05 - Debris score recode -tooth 31

Variable name:
OHEDDS05

Based on:
OHE_32D5

Description:
This variable takes the original debris score for tooth 31 whichwas recorded using a scale from 1 to 5 during the clinic dentalexaminations and recodes the score as a scale from 0 to 4.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 48
OHEDDS05 Specifications
Value Condition(s) Description Notes
6 OHE_32D5 = NA Population exclusions NA
9 (OHE_32D5 = DK, RF, NS) At least one required question was not answered (don’tknow, refusal, not stated) NS
0 OHE_32D5 = 1 No soft debris or stain  
1 OHE_32D5 = 2 Less than 1/3 of surface covered  
2 OHE_32D5 = 3 1/3 to 2/3 of surface covered  
3 OHE_32D5 = 4 More than 2/3 of surface covered  
4 OHE_32D5 = 5 Teeth missing  

49. OHEDDS06 - Debris score recode -teeth 46 and 47

Variable name:
OHEDDS06

Based on:
OHE_32D6

Description:
This variable takes the original debris score for teeth 46 and 47which was recorded using a scale from 1 to 5 during the clinicdental examinations and recodes the score as a scale from 0 to4.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 49
OHEDDS06 Specifications
Value Condition(s) Description Notes
6 OHE_32D6 = NA Population exclusions NA
9 (OHE_32D6 = DK, RF, NS) At least one required question was not answered (don’tknow, refusal, not stated) NS
0 OHE_32D6 = 1 No soft debris or stain  
1 OHE_32D6 = 2 Less than 1/3 of surface covered  
2 OHE_32D6 = 3 1/3 to 2/3 of surface covered  
3 OHE_32D6 = 4 More than 2/3 of surface covered  
4 OHE_32D6 = 5 Teeth missing  

50. OHEDDT01 - Total number ofdeciduous teeth - code 1

Variable name:
OHEDDT01

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75,  OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 1 (Sound - never decayed or restored) during the clinic dental examinations.

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 50
OHEDDT01 Temporary Reformat
Value Condition(s) Description Notes
DVT01_51   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 51  
DVT01_52   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 52  
DVT01_53   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 53  
DVT01_54   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 54  
DVT01_55   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 55  
DVT01_61   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 61  
DVT01_62   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 62  
DVT01_63   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 63  
DVT01_64   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 64  
DVT01_65   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 65  
DVT01_71   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 71  
DVT01_72   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 72  
DVT01_73   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 73  
DVT01_74   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 74  
DVT01_75   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 75  
DVT01_81   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 81  
DVT01_82   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 82  
DVT01_83   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 83  
DVT01_84   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 84  
DVT01_85   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 85  

 

Table 50
OHEDDT01 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
sum (of
DVT01_51-
DVT01_55 DVT01_61-
DVT01_65 DVT01_71-
DVT01_75 DVT01_81-DVT01_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 1  
9 Else   NS

 

51. OHEDDT02 - Total number ofdeciduous teeth - code 2

Variable name:
OHEDDT02

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 2 (Sound - crown sealed, never decayed or otherwise restored) during the clinic dental examinations.

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 51
OHEDDT02 Temporary Reformat
Value Condition(s) Description Notes
DVT02_51   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 51  
DVT02_52   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 52  
DVT02_53   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 53  
DVT02_54   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 54  
DVT02_55   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 55  
DVT02_61   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 61  
DVT02_62   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 62  
DVT02_63   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 63  
DVT02_64   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 64  
DVT02_65   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 65  
DVT02_71   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 71  
DVT02_72   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 72  
DVT02_73   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 73  
DVT02_74   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 74  
DVT02_75   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 75  
DVT02_81   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 81  
DVT02_82   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 82  
DVT02_83   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 83  
DVT02_84   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 84  
DVT02_85   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 85  

 

Table 51
OHEDDT02 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
sum (of
DVT02_51-
DVT02_55 DVT02_61-
DVT02_65 DVT02_71-
DVT02_75 DVT02_81-DVT02_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 2  
9 Else   NS

 

52. OHEDDT03 - Total number ofdeciduous teeth - code 3

Variable name:
OHEDDT03

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75,  OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 3 (Missing - due to orthodontic treatment) during the clinic dental examinations. 

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant. 

Table 52
OHEDDT03 Temporary Reformat
Value Condition(s) Description Notes
DVT03_51   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 51  
DVT03_52   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 52  
DVT03_53   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 53  
DVT03_54   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 54  
DVT03_55   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 55  
DVT03_61   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 61  
DVT03_62   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 62  
DVT03_63   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 63  
DVT03_64   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 64  
DVT03_65   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 65  
DVT03_71   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 71  
DVT03_72   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 72  
DVT03_73   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 73  
DVT03_74   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 74  
DVT03_75   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 75  
DVT03_81   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 81  
DVT03_82   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 82  
DVT03_83   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 83  
DVT03_84   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 84  
DVT03_85   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 85  

 

Table 52
OHEDDT03 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
sum (of
DVT03_51-
DVT03_55 DVT03_61-
DVT03_65 DVT03_71-
DVT03_75 DVT03_81-DVT03_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 3  
9 Else   NS

 

53. OHEDDT04 - Total number ofdeciduous teeth - code 4

Variable name:
OHEDDT04

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 4 (Missing - due to trauma) during the clinic dental examinations. 

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 53
OHEDDT04 Temporary Reformat
Value Condition(s) Description Notes
DVT04_51   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 51  
DVT04_52   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 52  
DVT04_53   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 53  
DVT04_54   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 54  
DVT04_55   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 55  
DVT04_61   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 61  
DVT04_62   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 62  
DVT04_63   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 63  
DVT04_64   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 64  
DVT04_65   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 65  
DVT04_71   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 71  
DVT04_72   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 72  
DVT04_73   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 73  
DVT04_74   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 74  
DVT04_75   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 75  
DVT04_81   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 81  
DVT04_82   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 82  
DVT04_83   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 83  
DVT04_84   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 84  
DVT04_85   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 85  

 

Table 53
OHEDDT04 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
sum (of
DVT04_51-
DVT04_55 DVT04_61-
DVT04_65 DVT04_71-
DVT04_75 DVT04_81-DVT04_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 4  
9 Else   NS

 

54. OHEDDT05 - Total number ofdeciduous teeth - code 5

Variable name:
OHEDDT05

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75,  OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 5 (Missing - due to caries or periodontal disease) during the clinic dental examinations. 

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 54
OHEDDT05 Temporary Reformat
Value Condition(s) Description Notes
DVT05_51   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 51  
DVT05_52   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 52  
DVT05_53   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 53  
DVT05_54   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 54  
DVT05_55   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 55  
DVT05_61   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 61  
DVT05_62   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 62  
DVT05_63   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 63  
DVT05_64   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 64  
DVT05_65   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 65  
DVT05_71   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 71  
DVT05_72   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 72  
DVT05_73   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 73  
DVT05_74   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 74  
DVT05_75   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 75  
DVT05_81   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 81  
DVT05_82   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 82  
DVT05_83   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 83  
DVT05_84   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 84  
DVT05_85   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 85  

 

Table 54
OHEDDT05 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
sum (of
DVT05_51-
DVT05_55 DVT05_61-
DVT05_65 DVT05_71-
DVT05_75 DVT05_81-DVT05_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 5  
9 Else   NS

 

55. OHEDDT06 - Total number ofdeciduous teeth - code 6

Variable name:
OHEDDT06

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75,  OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 6 (Unerupted tooth, congenitally missing or unexposed root) during the clinic dental examinations.

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 55
OHEDDT06 Temporary Reformat
Value Condition(s) Description Notes
DVT06_51   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 51  
DVT06_52   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 52  
DVT06_53   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 53  
DVT06_54   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 54  
DVT06_55   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 55  
DVT06_61   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 61  
DVT06_62   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 62  
DVT06_63   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 63  
DVT06_64   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 64  
DVT06_65   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 65  
DVT06_71   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 71  
DVT06_72   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 72  
DVT06_73   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 73  
DVT06_74   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 74  
DVT06_75   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 75  
DVT06_81   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 81  
DVT06_82   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 82  
DVT06_83   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 83  
DVT06_84   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 84  
DVT06_85   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 85  

 

Table 55
OHEDDT06 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
sum (of
DVT06_51-
DVT06_55 DVT06_61-
DVT06_65 DVT06_71-
DVT06_75 DVT06_81-DVT06_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 6  
9 Else   NS

 

56. OHEDDT07 - Total number ofdeciduous teeth - code 7

Variable name:
OHEDDT07

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 7 (Decayed severely) during the clinic dental examinations. 

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 56
OHEDDT07 Temporary Reformat
Value Condition(s) Description Notes
DVT07_51   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 51  
DVT07_52   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 52  
DVT07_53   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 53  
DVT07_54   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 54  
DVT07_55   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 55  
DVT07_61   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 61  
DVT07_62   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 62  
DVT07_63   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 63  
DVT07_64   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 64  
DVT07_65   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 65  
DVT07_71   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 71  
DVT07_72   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 72  
DVT07_73   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 73  
DVT07_74   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 74  
DVT07_75   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 75  
DVT07_81   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 81  
DVT07_82   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 82  
DVT07_83   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 83  
DVT07_84   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 84  
DVT07_85   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 85  

 

Table 56
OHEDDT07 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
sum (of
DVT07_51-
DVT07_55 DVT07_61-
DVT07_65 DVT07_71-
DVT07_75 DVT07_81-DVT07_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 7  
9 Else   NS

 

57. OHEDDT08 - Total number ofdeciduous teeth - code 8

Variable name:
OHEDDT08

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 8 (Decayed - pit and fissure caries) during the clinic dental examinations. 

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 57
OHEDDT08 Temporary Reformat
Value Condition(s) Description Notes
DVT08_51   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 51  
DVT08_52   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 52  
DVT08_53   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 53  
DVT08_54   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 54  
DVT08_55   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 55  
DVT08_61   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 61  
DVT08_62   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 62  
DVT08_63   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 63  
DVT08_64   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 64  
DVT08_65   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 65  
DVT08_71   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 71  
DVT08_72   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 72  
DVT08_73   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 73  
DVT08_74   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 74  
DVT08_75   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 75  
DVT08_81   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 81  
DVT08_82   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 82  
DVT08_83   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 83  
DVT08_84   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 84  
DVT08_85   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 85  

 

Table 57
OHEDDT08 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
sum (of
DVT08_51-
DVT08_55 DVT08_61-
DVT08_65 DVT08_71-
DVT08_75 DVT08_81-DVT08_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 8  
9 Else   NS

 

58. OHEDDT09 - Total number ofdeciduous teeth - code 9

Variable name:
OHEDDT09

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 9 (Decayed - smooth surface caries) during the clinic dental examinations. 

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 58
OHEDDT09 Temporary Reformat
Value Condition(s) Description Notes
DVT09_51   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 51  
DVT09_52   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 52  
DVT09_53   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 53  
DVT09_54   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 54  
DVT09_55   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 55  
DVT09_61   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 61  
DVT09_62   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 62  
DVT09_63   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 63  
DVT09_64   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 64  
DVT09_65   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 65  
DVT09_71   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 71  
DVT09_72   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 72  
DVT09_73   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 73  
DVT09_74   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 74  
DVT09_75   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 75  
DVT09_81   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 81  
DVT09_82   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 82  
DVT09_83   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 83  
DVT09_84   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 84  
DVT09_85   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 85  

 

Table 58
OHEDDT09 Specifications
Value Condition(s)  Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
sum (of
DVT09_51-
DVT09_55 DVT09_61-
DVT09_65 DVT09_71-
DVT09_75 DVT09_81-DVT09_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 9  
9 Else   NS

 

59. OHEDDT10 - Total number ofdeciduous teeth - code 10

Variable name:
OHEDDT10

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 10 (Decayed - both smooth surface and pit and fissure caries) during the clinic dental examinations. 

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 59
OHEDDT10 Temporary Reformat
Value Condition(s) Description Notes
DVT10_51   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 51  
DVT10_52   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 52  
DVT10_53   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 53  
DVT10_54   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 54  
DVT10_55   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 55  
DVT10_61   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 61  
DVT10_62   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 62  
DVT10_63   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 63  
DVT10_64   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 64  
DVT10_65   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 65  
DVT10_71   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 71  
DVT10_72   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 72  
DVT10_73   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 73  
DVT10_74   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 74  
DVT10_75   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 75  
DVT10_81   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 81  
DVT10_82   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 82  
DVT10_83   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 83  
DVT10_84   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 84  
DVT10_85   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 85  

 

Table 59
OHEDDT10 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
sum (of
DVT10_51-
DVT10_55 DVT10_61-
DVT10_65 DVT10_71-
DVT10_75 DVT10_81-DVT10_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 10  
9 Else   NS

 

60. OHEDDT12 - Total number ofdeciduous teeth - code 12

Variable name:
OHEDDT12

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 12 (Filled with amalgam, no other decay) during the clinic dental examinations. 

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 60
OHEDDT12 Temporary Reformat
Value Condition(s) Description Notes
DVT12_51   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 51  
DVT12_52   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 52  
DVT12_53   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 53  
DVT12_54   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 54  
DVT12_55   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 55  
DVT12_61   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 61  
DVT12_62   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 62  
DVT12_63   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 63  
DVT12_64   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 64  
DVT12_65   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 65  
DVT12_71   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 71  
DVT12_72   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 72  
DVT12_73   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 73  
DVT12_74   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 74  
DVT12_75   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 75  
DVT12_81   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 81  
DVT12_82   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 82  
DVT12_83   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 83  
DVT12_84   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 84  
DVT12_85   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 85  

 

Table 60
OHEDDT12 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
sum (of
DVT12_51-
DVT12_55 DVT12_61-
DVT12_65 DVT12_71-
DVT12_75 DVT12_81-DVT12_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 12  
9 Else   NS

 

61. OHEDDT13 - Total number ofdeciduous teeth - code 13

Variable name:
OHEDDT13

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 13 (Filled with other material (resin, GIC, inlay, crown), no other decay) during the clinic dental examinations. 

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 61
OHEDDT13 Temporary Reformat
Value Condition(s) Description Notes
DVT13_51   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 51  
DVT13_52   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 52  
DVT13_53   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 53  
DVT13_54   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 54  
DVT13_55   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 55  
DVT13_61   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 61  
DVT13_62   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 62  
DVT13_63   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 63  
DVT13_64   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 64  
DVT13_65   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 65  
DVT13_71   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 71  
DVT13_72   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 72  
DVT13_73   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 73  
DVT13_74   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 74  
DVT13_75   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 75  
DVT13_81   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 81  
DVT13_82   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 82  
DVT13_83   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 83  
DVT13_84   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 84  
DVT13_85   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 85  

 

Table 61
OHEDDT13 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
sum (of
DVT13_51-
DVT13_55 DVT13_61-
DVT13_65 DVT13_71-
DVT13_75 DVT13_81-DVT13_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 13  
9 Else   NS

 

62. OHEDDT14 - Total number ofdeciduous teeth - code 14

Variable name:
OHEDDT14

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 14 (Filled with amalgam and other material (resin, GIC, inlay, crown), no other decay) during the clinic dental examinations. 

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 62
OHEDDT14 Temporary Reformat
Value Condition(s) Description Notes
DVT14_51   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 51  
DVT14_52   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 52  
DVT14_53   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 53  
DVT14_54   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 54  
DVT14_55   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 55  
DVT14_61   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 61  
DVT14_62   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 62  
DVT14_63   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 63  
DVT14_64   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 64  
DVT14_65   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 65  
DVT14_71   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 71  
DVT14_72   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 72  
DVT14_73   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 73  
DVT14_74   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 74  
DVT14_75   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 75  
DVT14_81   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 81  
DVT14_82   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 82  
DVT14_83   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 83  
DVT14_84   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 84  
DVT14_85   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 85  

 

Table 62
OHEDDT14 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
sum (of
DVT14_51-
DVT14_55 DVT14_61-
DVT14_65 DVT14_71-
DVT14_75 DVT14_81-DVT14_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 14  
9 Else   NS

 

63. OHEDDT15 - Total number ofdeciduous teeth - code 15

Variable name:
OHEDDT15

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 15 (Filled with amalgam, no other decay, but filling is defective and needs replacement) during the clinic dental examinations

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 63
OHEDDT15 Temporary Reformat
Value Condition(s) Description Notes
DVT15_51   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 51  
DVT15_52   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 52  
DVT15_53   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 53  
DVT15_54   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 54  
DVT15_55   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 55  
DVT15_61   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 61  
DVT15_62   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 62  
DVT15_63   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 63  
DVT15_64   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 64  
DVT15_65   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 65  
DVT15_71   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 71  
DVT15_72   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 72  
DVT15_73   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 73  
DVT15_74   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 74  
DVT15_75   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 75  
DVT15_81   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 81  
DVT15_82   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 82  
DVT15_83   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 83  
DVT15_84   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 84  
DVT15_85   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 85  

 

Table 63
OHEDDT15 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
sum (of
DVT15_51-
DVT15_55 DVT15_61-
DVT15_65 DVT15_71-
DVT15_75 DVT15_81-DVT15_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 15  
9 Else   NS

 

64. OHEDDT16 - Total number ofdeciduous teeth - code 16

Variable name:
OHEDDT16

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 16 (Filled with other material (resin, GIC, inlay, crown) but filling is defective and needs replacement) during the clinic dental examinations. 

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 64
OHEDDT16 Temporary Reformat
Value Condition(s) Description Notes
DVT16_51   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 51  
DVT16_52   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 52  
DVT16_53   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 53  
DVT16_54   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 54  
DVT16_55   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 55  
DVT16_61   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 61  
DVT16_62   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 62  
DVT16_63   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 63  
DVT16_64   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 64  
DVT16_65   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 65  
DVT16_71   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 71  
DVT16_72   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 72  
DVT16_73   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 73  
DVT16_74   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 74  
DVT16_75   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 75  
DVT16_81   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 81  
DVT16_82   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 82  
DVT16_83   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 83  
DVT16_84   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 84  
DVT16_85   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 85  

 

Table 64
OHEDDT16 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
sum (of
DVT16_51-
DVT16_55 DVT16_61-
DVT16_65 DVT16_71-
DVT16_75 DVT16_81-DVT16_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 16  
9 Else   NS

 

65. OHEDDT17 - Total number ofdeciduous teeth - code 17

Variable name:
OHEDDT17

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 17 (Filled with amalgam and other material (resin, GIC, inlay, crown) but filling is defective and needs replacement) during the clinic dental examinations. 

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 65
OHEDDT17 Temporary Reformat
Value Condition(s) Description Notes
DVT17_51   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 51  
DVT17_52   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 52  
DVT17_53   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 53  
DVT17_54   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 54  
DVT17_55   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 55  
DVT17_61   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 61  
DVT17_62   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 62  
DVT17_63   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 63  
DVT17_64   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 64  
DVT17_65   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 65  
DVT17_71   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 71  
DVT17_72   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 72  
DVT17_73   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 73  
DVT17_74   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 74  
DVT17_75   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 75  
DVT17_81   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 81  
DVT17_82   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 82  
DVT17_83   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 83  
DVT17_84   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 84  
DVT17_85   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 85  

 

Table 65
OHEDDT17 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
sum (of
DVT17_51-
DVT17_55 DVT17_61-
DVT17_65 DVT17_71-
DVT17_75 DVT17_81-DVT17_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 17  
9 Else   NS

 

66. OHEDDT20 - Total number ofdeciduous teeth - code 20

Variable name:
OHEDDT20

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 20 (Fractured due to trauma) during the clinic dental examinations. 

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 66
OHEDDT20 Temporary Reformat
Value Condition(s) Description Notes
DVT20_51   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 51  
DVT20_52   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 52  
DVT20_53   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 53  
DVT20_54   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 54  
DVT20_55   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 55  
DVT20_61   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 61  
DVT20_62   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 62  
DVT20_63   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 63  
DVT20_64   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 64  
DVT20_65   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 65  
DVT20_71   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 71  
DVT20_72   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 72  
DVT20_73   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 73  
DVT20_74   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 74  
DVT20_75   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 75  
DVT20_81   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 81  
DVT20_82   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 82  
DVT20_83   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 83  
DVT20_84   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 84  
DVT20_85   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 85  

 

Table 66
OHEDDT20 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
sum (of
DVT20_51-
DVT20_55 DVT20_61-
DVT20_65 DVT20_71-
DVT20_75 DVT20_81-DVT20_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 20  
9 Else   NS

 

67. OHEDDT21 - Total number ofdeciduous teeth - code 21

Variable name:
OHEDDT21

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 21 (Other) during the clinic dental examinations. 

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 67
OHEDDT21 Temporary Reformat
Value Condition(s) Description Notes
DVT21_51   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 51  
DVT21_52   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 52  
DVT21_53   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 53  
DVT21_54   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 54  
DVT21_55   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 55  
DVT21_61   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 61  
DVT21_62   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 62  
DVT21_63   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 63  
DVT21_64   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 64  
DVT21_65   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 65  
DVT21_71   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 71  
DVT21_72   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 72  
DVT21_73   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 73  
DVT21_74   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 74  
DVT21_75   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 75  
DVT21_81   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 81  
DVT21_82   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 82  
DVT21_83   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 83  
DVT21_84   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 84  
DVT21_85   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 85  

 

Table 67
OHEDDT21 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
sum (of
DVT21_51-
DVT21_55 DVT21_61-
DVT21_65 DVT21_71-
DVT21_75 DVT21_81-DVT21_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 21  
9 Else   NS

 

68. OHEDFLUO - Fluorosis scorerecode

Variable name:
OHEDFLUO

Based on:
OHE_20

Description:
During the clinic dental examinations the fluorosis score wasrecorded using a scale of 1 to 7 for the most affected pair ofteeth for teeth 11, 12, 21 or 22.  If the two teeth were notequally affected, the score for the less affected of the two wasrecorded.  This variable recodes the fluorosis score into ascale of 0 to 6.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 68
OHEDFLUO Specifications
Value Condition(s) Description Notes
99 (OHE_N20 = DK, RF, NS) At least one required question was not answered (don’tknow, refusal, not stated) NS
96 OHE_20 = NA Population exclusions NA
0 OHE_20 = 1 Normal  
1 OHE_20 = 2 Questionable  
2 OHE_20 = 3 Very mild  
3 OHE_20 = 4 Mild  
4 OHE_20 = 5 Moderate  
5 OHE_20 = 6 Severe  
6 OHE_20 = 7 All 4 anterior teeth absent  

69. OHEDGS12 - Gingivitis score recode- tooth 12

Variable name:
OHEDGS12

Based on:
OHE_31G2

Description:
This variable takes theoriginal gingivitis score for tooth 12 which was recorded using ascale from 1 to 5 during the clinic dental examinations and recodesthe score as a scale from 0 to 4.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 69
OHEDGS12 Specifications
Value Condition(s) Description Notes
6 OHE_31G2 = NA Population exclusions NA
9 (OHE_31G2 = DK, RF, NS) At least one required question was not answered (don’tknow, refusal, not stated) NS
0 OHE_31G2 = 1 No inflammation  
1 OHE_31G2 = 2 Mild inflammation  
2 OHE_31G2 = 3 Moderate inflammation  
3 OHE_31G2 = 4 Severe inflammation  
4 OHE_31G2 = 5 Tooth missing  

70. OHEDGS16 - Gingivitis score recode- tooth 16

Variable name:
OHEDGS16

Based on:
OHE_31G1

Description:
This variable takes the original gingivitis score for tooth 16which was recorded using a scale from 1 to 5 during the clinicdental examinations and recodes the score as a scale from 0 to4.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 70
OHEDGS16 Specifications
Value Condition(s) Description Notes
6 OHE_31G1 = NA Population exclusions NA
9 (OHE_31G1 = DK, RF, NS) At least one required question was not answered (don’tknow, refusal, not stated) NS
0 OHE_31G1 = 1 No inflammation  
1 OHE_31G1 = 2 Mild inflammation  
2 OHE_31G1 = 3 Moderate inflammation  
3 OHE_31G1 = 4 Severe inflammation  
4 OHE_31G1 = 5 Tooth missing  

71. OHEDGS24 - Gingivitis score recode- tooth 24

Variable name:
OHEDGS24

Based on:
OHE_31G3

Description:
This variable takes the original gingivitis score for tooth 24which was recorded using a scale from 1 to 5 during the clinicdental examinations and recodes the score as a scale from 0 to4.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 71
OHEDGS24 Specifications
Value Condition(s) Description Notes
6 OHE_31G3 = NA Population exclusions NA
9 (OHE_31G3 = DK, RF, NS) At least one required question was not answered (don’tknow, refusal, not stated) NS
0 OHE_31G3 = 1 No inflammation  
1 OHE_31G3 = 2 Mild inflammation  
2 OHE_31G3 = 3 Moderate inflammation  
3 OHE_31G3 = 4 Severe inflammation  
4 OHE_31G3 = 5 Tooth missing  

72. OHEDGS32 - Gingivitis score recode- tooth 32

Variable name:
OHEDGS32

Based on:
OHE_31G5

Description:
This variable takes the original gingivitis score for tooth 32which was recorded using a scale from 1 to 5 during the clinicdental examinations and recodes the score as a scale from 0 to4.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria: 

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 72
OHEDGS32 Specifications
Value Condition(s) Description Notes
6 OHE_31G5 = NA Population exclusions NA
9 (OHE_31G5 = DK, RF, NS) At least one required question was not answered (don’tknow, refusal, not stated) NS
0 OHE_31G5 = 1 No inflammation  
1 OHE_31G5 = 2 Mild inflammation  
2 OHE_31G5 = 3 Moderate inflammation  
3 OHE_31G5 = 4 Severe inflammation  
4 OHE_31G5 = 5 Tooth missing  

73. OHEDGS36 - Gingivitis score recode- tooth 36

Variable name:
OHEDGS36

Based on:
OHE_31G4

Description:
This variable takes the original gingivitis score for tooth 36which was recorded using a scale from 1 to 5 during the clinicdental examinations and recodes the score as a scale from 0 to4.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 73
OHEDGS36 Specifications
Value Condition(s) Description Notes
6 OHE_31G4 = NA Population exclusions NA
9 (OHE_31G4 = DK, RF, NS) At least one required question was not answered (don’tknow, refusal, not stated) NS
0 OHE_31G4 = 1 No inflammation  
1 OHE_31G4 = 2 Mild inflammation  
2 OHE_31G4 = 3 Moderate inflammation  
3 OHE_31G4 = 4 Severe inflammation  
4 OHE_31G4 = 5 Tooth missing  

74. OHEDGS44 - Gingivitis score recode- tooth 44

Variable name:
OHEDGS44

Based on:
OHE_31G6

Description:
This variable takes the original gingivitis score for tooth 44which was recorded using a scale from 1 to 5 during the clinicdental examinations and recodes the score as a scale from 0 to4.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 74
OHEDGS44 Specifications
Value Condition(s) Description Notes
6 OHE_31G6 = NA Population exclusions NA
9 (OHE_31G6 = DK, RF, NS) At least one required question was not answered (don’tknow, refusal, not stated) NS
0 OHE_31G6 = 1 No inflammation  
1 OHE_31G6 = 2 Mild inflammation  
2 OHE_31G6 = 3 Moderate inflammation  
3 OHE_31G6 = 4 Severe inflammation  
4 OHE_31G6 = 5 Tooth missing  

75. OHRD25 - Test exclusion –probing

Variable name:
OHRD25

Based on:
OHR_11, OHR_12, OHR_13, OHR_14,OHR_15, OHR_16, OHR_17, OHR_19, OHR_20, OHR_21, OHR_22, OHR_23,OHR_24

Description:
If the respondent answered yesto any of the Oral Health Restriction questions, probing was notperformed.

Note:
Created in the Clinic data collection application

Table 75
OHRD25 Specifications
Value Condition(s) Description Notes
9 OHR_11 > NA or
OHR_12 > NA or
OHR_13 > NA or
OHR_14 > NA or
OHR_15 > NA or
OHR_16 > NA or
OHR_17 > NA or
OHR_19 > NA or
OHR_20 > NA or
OHR_21 > NA or
OHR_22 > NA or
OHR_23 > NA or
OHR_24 > NA
At least one required question was not answered (don’tknow, refusal, not stated) NS
6 OHR_11 = NA and
OHR_12 = NA and
OHR_13 = NA and
OHR_14 = NA and
OHR_15 = NA and
OHR_16 = NA and
OHR_17 = NA and
OHR_19 = NA and
OHR_20 = NA and
OHR_21 = NA and
OHR_22 = NA and
OHR_23 = NA and
OHR_24 = NA
Population exclusions NA
1 OHR_11 = 1 or
OHR_12 = 1 or
OHR_13 = 1 or
OHR_14 = 1 or
OHR_15 = 1 or
OHR_16 = 1 or
OHR_17 = 1 or
OHR_19 = 1 or
OHR_20 = 1 or
OHR_21 = 1 or
OHR_22 = 1 or
OHR_23 = 1 or
OHR_24 = 1
The respondent answered yes to one of the Oral HealthRestriction questions  
2 Else    

76. OHMD31Y - Brushing teeth - numbertimes per year

Variable name:
OHMD31Y

Based on:
OHM_31, OHM_31N

Description:
The number of times per year the respondent brushes his/her teethand/or dentures.

Note:
Created in the Household Post-Verify process.

Table 76
OHMD31Y Specifications
Value Condition(s) Description Notes
9996 OHM_31N = NA Population exclusions NA
0 OHM_31 = 0 Never  
OHM_31 * 365 OHM_31N = 1 Reported number of times per day converted to derived number oftimes per year  
OHM_31 * 52 OHM_31N = 2 Reported number of times per week converted to derived numberof times per year  
OHM_31 * 12 OHM_31N = 3 Reported number of times per month converted to derived numberof times per year  
OHM_31 OHM_31N = 4 Reported number of times per year  
9999 Else At least one required question was not answered (don’tknow, refusal, not stated) NS

77. OHMD32Y - Flossing teeth - numbertimes per year

Variable name:
OHMD32Y

Based on:
OHM_32, OHM_32N

Description:
The number of times per year the respondent flosses his/herteeth.

Note:
Created in the Household Post-Verify process.

Table 77
OHMD32Y Specifications
Value Condition(s) Description Notes
9996 OHM_32N = NA Population exclusions NA
0 OHM_32 = 0 Never  
OHM_32 * 365 OHM_32N = 1 Reported number of times per day converted to derived number oftimes per year  
OHM_32 * 52 OHM_32N = 2 Reported number of times per week converted to derived numberof times per year  
OHM_32 * 12 OHM_32N = 3 Reported number of times per month converted to derived numberof times per year  
OHM_32 OHM_32N = 4 Reported number of times per year  
9999 Else At least one required question was not answered (don’tknow, refusal, not stated) NS

Physical activities (6 DVs)

1. PACDEE - Daily EnergyExpenditure

Variable name:
PACDEE

Based on:
PAC_11W, PAC_12A, PAC_12B, PAC_12C, PAC_12D, PAC_12E, PAC_12F,PAC_12G, PAC_12H, PAC_12I, PAC_12J, PAC_12K, PAC_12L, PAC_12M,PAC_12N, PAC_12O, PAC_12P, PAC_12Q, PAC_12R, PAC_12S, PAC_12T,PAC_12U, PAC_12V, PAC_12X, PAC_12Y, PAC_13A, PAC_13B, PAC_13C,PAC_13D, PAC_13E, PAC_13F, PAC_13G, PAC_13H, PAC_13I, PAC_13J,PAC_13K, PAC_13L, PAC_13M, PAC_13N, PAC_13O, PAC_13P, PAC_13Q,PAC_13R, PAC_13S, PAC_13T,  PAC_13U, PAC_13V, PAC_13X,PAC_13Y, DHH_AGE

Description:
This variable is a measure of the average daily energy expendedduring leisure time activities by the respondent in the past threemonths.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents less than 12 years of age were excluded from thepopulation.
Energy Expenditure is calculated using the frequency and durationper session of the physical activity as well as the MET value ofthe activity. The MET is a value of metabolic energy cost expressedas a multiple of the resting metabolic rate.  For example, anactivity of 4 METS requires four times the amount of energy ascompared to when the body is at rest.
EE (Energy Expenditure for each activity) = (N X D X METvalue) /365
Where:
N = the number of times a respondent engaged in an activity over a12 month period
D = the average duration in hours of the activity
MET value = the energy cost of the activity expressed askilocalories expended per kilogram of body weight per hour ofactivity (kcal/kg per hour)/365 (to convert yearly data into dailydata)

MET values tend to be expressed in three intensity levels (i.e.low, medium, high).  The CCHS questions did not ask therespondent to specify the intensity level of their activities.Therefore the MET values adopted correspond to the low intensityvalue of each activity. This approach is adopted from the CanadianFitness and Lifestyle Research Institute because individuals tendto overestimate the intensity, frequency and duration of theiractivities.

* Times were assigned an average duration value for thecalculation, as with NPHS:
(13 minutes or .2167 hour, 23 minutes or .3833 hour, 45 minutes or.75 hour, 60 minutes or 1 hour)

Internet site:
Canadian Fitness and Lifestyle Research Institute: www.cflri.ca

Table 1
PACDEE Temporary Reformat

 

PACDEEA

 

Value Condition(s) Description Notes
0 PAC_13A = NA Did not participate in activity Walking for exercise
0 (PAC_13A = DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) Walking for exercise
(PAC_12A × 4 ×
.2167 × 3) / 365
PAC_13A = 1 Calculate EE for < 15 min* Walking for exercise
(PAC_12A × 4 ×
.3833 × 3) / 365
PAC_13A = 2 Calculate EE for 16 to 30 min* Walking for exercise
(PAC_12A × 4 ×
.75 × 3) / 365
PAC_13A = 3 Calculate EE for 31 to 60 min* Walking for exercise
(PAC_12A × 4 × 1
× 3) / 365
PAC_13A = 4 Calculate EE for > 60 min* Walking for exercise


PACDEEB

 

Value Condition(s) Description Notes
0 PAC_13B = NA Did not participate in activity Gardening or yard work
0 (PAC_13B = DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) Gardening or yard work
(PAC_12B × 4 ×
.2167 × 3) / 365
PAC_13B = 1 Calculate EE for < 15 min* Gardening or yard work
(PAC_12B × 4 ×
.3833 × 3) / 365
PAC_13B = 2 Calculate EE for 16 to 30 min* Gardening or yard work
(PAC_12B × 4 ×
.75 × 3) / 365
PAC_13B = 3 Calculate EE for 31 to 60 min* Gardening or yard work
(PAC_12B × 4 × 1
× 3) / 365
PAC_13B = 4 Calculate EE for > 60 min* Gardening or yard work


PACDEEC

 

 

Value Condition(s) Description Notes
0 PAC_13C = NA Did not participate in activity Swimming
0 (PAC_13C = DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) Swimming
(PAC_12C × 4 ×
.2167 × 3) / 365
PAC_13C = 1 Calculate EE for < 15 min* Swimming
(PAC_12C × 4 ×
.3833 × 3) / 365
PAC_13C = 2 Calculate EE for 16 to 30 min* Swimming
(PAC_12C × 4 ×
.75 × 3) / 365
PAC_13C = 3 Calculate EE for 31 to 60 min* Swimming
(PAC_12C × 4 × 1
× 3) / 365
PAC_13C = 4 Calculate EE for > 60 min* Swimming


PACDEED

 

 

Value Condition(s) Description Notes
0 PAC_13D = NA Did not participate in activity Bicycling
0 (PAC_13D = DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) Bicycling
(PAC_12D × 4 ×
.2167 × 4) / 365
PAC_13D = 1 Calculate EE for < 15 min* Bicycling
(PAC_12D × 4 ×
.3833 × 4) / 365
PAC_13D = 2 Calculate EE for 16 to 30 min* Bicycling
(PAC_12D × 4 ×
.75 × 4) / 365
PAC_13D = 3 Calculate EE for 31 to 60 min* Bicycling
(PAC_12D × 4 × 1
× 4) / 365
PAC_13D = 4 Calculate EE for > 60 min* Bicycling


PACDEEE

 

 

Value Condition(s) Description Notes
0 PAC_13E = NA Did not participate in activity Popular or social dance
0 (PAC_13E = DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) Popular or social dance
(PAC_12E × 4 ×
.2167 × 3) / 365
PAC_13E = 1 Calculate EE for < 15 min* Popular or social dance
(PAC_12E × 4 ×
.3833 × 3) / 365
PAC_13E = 2 Calculate EE for 16 to 30 min* Popular or social dance
(PAC_12E × 4 ×
.75 × 3) / 365
PAC_13E = 3 Calculate EE for 31 to 60 min* Popular or social dance
(PAC_12E × 4 × 1
× 3) / 365
PAC_13E = 4 Calculate EE for > 60 min* Popular or social dance


PACDEEF

 

 

Value Condition(s) Description Notes
0 PAC_13F = NA Did not participate in activity Home exercises
0 (PAC_13F = DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) Home exercises
(PAC_12F × 4 ×
.2167 × 3) / 365
PAC_13F = 1 Calculate EE for < 15 min* Home exercises
(PAC_12F × 4 ×
.3833 × 3) / 365
PAC_13F = 2 Calculate EE for 16 to 30 min* Home exercises
(PAC_12F × 4 ×
.75 × 3) / 365
PAC_13F = 3 Calculate EE for 31 to 60 min* Home exercises
(PAC_12F × 4 × 1
× 3) / 365
PAC_13F = 4 Calculate EE for > 60 min* Home exercises


PACDEEG

 

 

Value Condition(s) Description Notes
0 PAC_13G = NA Did not participate in activity Ice hockey
0 (PAC_13G = DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) Ice hockey
(PAC_12G × 4 ×
.2167 × 6) / 365
PAC_13G = 1 Calculate EE for < 15 min* Ice hockey
(PAC_12G × 4 ×
.3833 × 6) / 365
PAC_13G = 2 Calculate EE for 16 to 30 min* Ice hockey
(PAC_12G × 4 ×
.75 × 6) / 365
PAC_13G = 3 Calculate EE for 31 to 60 min* Ice hockey
(PAC_12G × 4 × 1
× 6) / 365
PAC_13G = 4 Calculate EE for > 60 min* Ice hockey


PACDEEH

 

 

Value Condition(s) Description Notes
0 PAC_13H = NA Did not participate in activity Ice skating
0 (PAC_13H = DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) Ice skating
(PAC_12H × 4 ×
.2167 × 4) / 365
PAC_13H = 1 Calculate EE for < 15 min* Ice skating
(PAC_12H × 4 ×
.3833 × 4) / 365
PAC_13H = 2 Calculate EE for 16 to 30 min* Ice skating
(PAC_12H × 4 ×
.75 × 4) / 365
PAC_13H = 3 Calculate EE for 31 to 60 min* Ice skating
(PAC_12H × 4 × 1
× 4) / 365
PAC_13H = 4 Calculate EE for > 60 min* Ice skating


PACDEEI

 

 

Value Condition(s) Description Notes
0 PAC_13I = NA Did not participate in activity In-line skating OR ROLLERBLADING
0 (PAC_13I = DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) In-line skating OR ROLLERBLADING
(PAC_12I × 4 ×
.2167 × 5) / 365
PAC_13I = 1 Calculate EE for < 15 min* In-line skating OR ROLLERBLADING
(PAC_12I × 4 ×
.3833 × 5) / 365
PAC_13I = 2 Calculate EE for 16 to 30 min* In-line skating OR ROLLERBLADING
(PAC_12I × 4 ×
.75 × 5) / 365
PAC_13I = 3 Calculate EE for 31 to 60 min* In-line skating OR ROLLERBLADING
(PAC_12I × 4 × 1× 5) / 365 PAC_13I = 4 Calculate EE for > 60 min* In-line skating OR ROLLERBLADING


PACDEEJ

 

 

Value Condition(s) Description Notes
0 PAC_13J = NA Did not participate in activity Jogging or running
0 (PAC_13J = DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) Jogging or running
(PAC_12J × 4 ×
.2167 × 9.5) / 365
PAC_13J = 1 Calculate EE for < 15 min* Jogging or running
(PAC_12J × 4 ×
.3833 × 9.5) / 365
PAC_13J = 2 Calculate EE for 16 to 30 min* Jogging or running
(PAC_12J × 4 ×
.75 × 9.5) / 365
PAC_13J = 3 Calculate EE for 31 to 60 min* Jogging or running
(PAC_12J × 4 × 1
× 9.5) / 365
PAC_13J = 4 Calculate EE for > 60 min* Jogging or running


PACDEEK

 

 

Value Condition(s) Description Notes
0 PAC_13K = NA Did not participate in activity Golfing
0 (PAC_13K = DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) Golfing
(PAC_12K × 4 ×
.2167 × 4) / 365
PAC_13K = 1 Calculate EE for < 15 min* Golfing
(PAC_12K × 4 ×
.3833 × 4) / 365
PAC_13K = 2 Calculate EE for 16 to 30 min* Golfing
(PAC_12K × 4 ×
.75 × 4) / 365
PAC_13K = 3 Calculate EE for 31 to 60 min* Golfing
(PAC_12K × 4 × 1
× 4) / 365
PAC_13K = 4 Calculate EE for > 60 min* Golfing


PACDEEL

 

 

Value Condition(s) Description Notes
0 PAC_13L = NA Did not participate in activity Exercise class or aerobics
0 (PAC_13L = DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) Exercise class or aerobics
(PAC_12L × 4 ×
.2167 × 4) / 365
PAC_13L = 1 Calculate EE for < 15 min* Exercise class or aerobics
(PAC_12L × 4 ×
.3833 × 4) / 365
PAC_13L = 2 Calculate EE for 16 to 30 min* Exercise class or aerobics
(PAC_12L × 4 ×
.75 × 4) / 365
PAC_13L = 3 Calculate EE for 31 to 60 min* Exercise class or aerobics
(PAC_12L × 4 × 1× 4) / 365 PAC_13L = 4 Calculate EE for > 60 min* Exercise class or aerobics


PACDEEM

 

 

Value Condition(s) Description Notes
0 PAC_13M = NA Did not participate in activity Downhill skiing or snowboarding
0 (PAC_13M = DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) Downhill skiing or snowboarding
(PAC_12M × 4 ×
.2167 × 4) / 365
PAC_13M = 1 Calculate EE for < 15 min* Downhill skiing or snowboarding
(PAC_12M × 4 ×
.3833 × 4) / 365
PAC_13M = 2 Calculate EE for 16 to 30 min* Downhill skiing or snowboarding
(PAC_12M × 4 ×
.75 × 4) / 365
PAC_13M = 3 Calculate EE for 31 to 60 min* Downhill skiing or snowboarding
(PAC_12M × 4 × 1× 4) / 365 PAC_13M = 4 Calculate EE for > 60 min* Downhill skiing or snowboarding


PACDEEN

 

 

Value Condition(s) Description Notes
0 PAC_13N = NA Did not participate in activity Bowling
0 (PAC_13N = DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) Bowling
(PAC_12N × 4 ×
.2167 × 2) / 365
PAC_13N = 1 Calculate EE for < 15 min* Bowling
(PAC_12N × 4 ×
.3833 × 2) / 365
PAC_13N = 2 Calculate EE for 16 to 30 min* Bowling
(PAC_12N × 4 ×
.75 × 2) / 365
PAC_13N = 3 Calculate EE for 31 to 60 min* Bowling
(PAC_12N × 4 × 1
× 2) / 365
PAC_13N = 4 Calculate EE for > 60 min* Bowling


PACDEEO

 

 

Value Condition(s) Description Notes
0 PAC_13O = NA Did not participate in activity Baseball or softball
0 (PAC_13O = DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) Baseball or softball
(PAC_12O × 4 ×
.2167 × 3) / 365
PAC_13O = 1 Calculate EE for < 15 min* Baseball or softball
(PAC_12O × 4 ×
.3833 × 3) / 365
PAC_13O = 2 Calculate EE for 16 to 30 min* Baseball or softball
(PAC_12O × 4 ×
.75 × 3) / 365
PAC_13O = 3 Calculate EE for 31 to 60 min* Baseball or softball
(PAC_12O × 4 × 1
× 3) / 365
PAC_13O = 4 Calculate EE for > 60 min* Baseball or softball


PACDEEP

 

 

Value Condition(s) Description Notes
0 PAC_13P = NA Did not participate in activity Tennis
0 (PAC_13P = DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) Tennis
(PAC_12P × 4 ×
.2167 × 4) / 365
PAC_13P = 1 Calculate EE for < 15 min* Tennis
(PAC_12P × 4 ×
.3833 × 4) / 365
PAC_13P = 2 Calculate EE for 16 to 30 min* Tennis
(PAC_12P × 4 ×
.75 × 4) / 365
PAC_13P = 3 Calculate EE for 31 to 60 min* Tennis
(PAC_12P × 4 × 1
× 4) / 365
PAC_13P = 4 Calculate EE for > 60 min* Tennis


PACDEEQ

 

 

Value Condition(s) Description Notes
0 PAC_13Q = NA Did not participate in activity Weight-training
0 (PAC_13Q = DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) Weight-training
(PAC_12Q × 4 ×
.2167 × 3) / 365
PAC_13Q = 1 Calculate EE for < 15 min* Weight-training
(PAC_12Q × 4 ×
.3833 × 3) / 365
PAC_13Q = 2 Calculate EE for 16 to 30 min* Weight-training
(PAC_12Q × 4 ×
.75 × 3) / 365
PAC_13Q = 3 Calculate EE for 31 to 60 min* Weight-training
(PAC_12Q × 4 × 1
× 3) / 365
PAC_13Q = 4 Calculate EE for > 60 min* Weight-training


PACDEER

 

 

Value Condition(s) Description Notes
0 PAC_13R = NA Did not participate in activity Fishing
0 (PAC_13R = DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) Fishing
(PAC_12R × 4 ×
.2167 × 3) / 365
PAC_13R = 1 Calculate EE for < 15 min* Fishing
(PAC_12R × 4 ×
.3833 × 3) / 365
PAC_13R = 2 Calculate EE for 16 to 30 min* Fishing
(PAC_12R × 4 ×
.75 × 3) / 365
PAC_13R = 3 Calculate EE for 31 to 60 min* Fishing
(PAC_12R × 4 × 1
× 3) / 365
PAC_13R = 4 Calculate EE for > 60 min* Fishing


PACDEES

 

 

Value Condition(s) Description Notes
0 PAC_13S = NA Did not participate in activity Volleyball
0 (PAC_13S = DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) Volleyball
(PAC_12S × 4 ×
.2167 × 5) / 365
PAC_13S = 1 Calculate EE for < 15 min* Volleyball
(PAC_12S × 4 ×
.3833 × 5) / 365
PAC_13S = 2 Calculate EE for 16 to 30 min* Volleyball
(PAC_12S × 4 ×
.75 × 5) / 365
PAC_13S = 3 Calculate EE for 31 to 60 min* Volleyball
(PAC_12S × 4 × 1
× 5) / 365
PAC_13S = 4 Calculate EE for > 60 min* Volleyball


PACDEET

 

 

Value Condition(s) Description Notes
0 PAC_13T = NA Did not participate in activity Basketball
0 (PAC_13T = DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) Basketball
(PAC_12T × 4 ×
.2167 × 6) / 365
PAC_13T = 1 Calculate EE for < 15 min* Basketball
(PAC_12T × 4 ×
.3833 × 6) / 365
PAC_13T = 2 Calculate EE for 16 to 30 min* Basketball
(PAC_12T × 4 ×
.75 × 6) / 365
PAC_13T = 3 Calculate EE for 31 to 60 min* Basketball
(PAC_12T × 4 × 1
× 6) / 365
PAC_13T = 4 Calculate EE for > 60 min* Basketball


PACDEEU

 

 

Value Condition(s) Description Notes
0 PAC_13U = NA Did not participate in activity Soccer (U)
0 (PAC_13U = DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) Soccer (U)
(PAC_12U × 4 ×
.2167 × 5) / 365
PAC_13U = 1 Calculate EE for < 15 min* Soccer (U)
(PAC_12U × 4 ×
.3833 × 5) / 365
PAC_13U = 2 Calculate EE for 16 to 30 min* Soccer (U)
(PAC_12U × 4 ×
.75 × 5) / 365
PAC_13U = 3 Calculate EE for 31 to 60 min* Soccer (U)
(PAC_12U × 4 × 1
× 5) / 365
PAC_13U = 4 Calculate EE for > 60 min* Soccer (U)


PACDEEV

 

 

Value Condition(s) Description Notes
0 PAC_13V = NA Did not participate in activity Other (V)
0 (PAC_13V = DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) Other (V)
(PAC_12V × 4 ×
.2167 × 4) / 365
PAC_13V = 1 Calculate EE for < 15 min* Other (V)
(PAC_12V × 4 ×
.3833 × 4) / 365
PAC_13V = 2 Calculate EE for 16 to 30 min* Other (V)
(PAC_12V × 4 ×
.75 × 4) / 365
PAC_13V = 3 Calculate EE for 31 to 60 min* Other (V)
(PAC_12V × 4 × 1
× 4) / 365
PAC_13V = 4 Calculate EE for > 60 min* Other (V)


PACDEEX

 

 

Value Condition(s) Description Notes
0 PAC_13X = NA Did not participate in activity Other (X)
0 (PAC_13X = DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) Other (X)
(PAC_12X × 4 ×
.2167 × 4) / 365
PAC_13X = 1 Calculate EE for < 15 min* Other (X)
(PAC_12X × 4 ×
.3833 × 4) / 365
PAC_13X = 2 Calculate EE for 16 to 30 min* Other (X)
(PAC_12X × 4 ×
.75 × 4) / 365
PAC_13X = 3 Calculate EE for 31 to 60 min* Other (X)
(PAC_12X × 4 × 1
× 4) / 365
PAC_13X = 4 Calculate EE for > 60 min* Other (X)


PACDEEY

 

 

Value Condition(s) Description Notes
0 PAC_13Y = NA Did not participate in activity Other (Y)
0 (PAC_13Y = DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) Other (Y)
(PAC_12Y × 4 ×
.2167 × 4) / 365
PAC_13Y = 1 Calculate EE for < 15 min* Other (Y)
(PAC_12Y × 4 ×
.3833 × 4) / 365
PAC_13Y = 2 Calculate EE for 16 to 30 min* Other (Y)
(PAC_12Y × 4 ×
.75 × 4) / 365
PAC_13Y = 3 Calculate EE for 31 to 60 min* Other (Y)
(PAC_12Y × 4 × 1
× 4) / 365
PAC_13Y = 4 Calculate EE for > 60 min* Other (Y)

 

 

Table 1
PACDEE Specifications
Value Condition(s) Description Notes
99.6 DHH_AGE < 12 or
PAC_11W = NA
Population exclusions NA
99.9 (PAC_11W = DK, RF, NS) Required question was
not answered (don’t know, refusal, not stated)
NS
0 PAC_11W = 1 No physical activity  
PACDEEA +
PACDEEB +
PACDEEC +
PACDEED +
PACDEEE +
PACDEEF +
PACDEEG +
PACDEEH +
PACDEEI +
PACDEEJ +
PACDEEK +
PACDEEL +
PACDEEM +
PACDEEN +
PACDEEO +
PACDEEP +
PACDEEQ +
PACDEER +
PACDEES +
PACDEET +
PACDEEU +
PACDEEV +
PACDEEX +
PACDEEY
(0 <= PACDEEA <  NA) and
(0 <= PACDEEB <  NA) and
(0 <= PACDEEC <  NA) and
(0 <= PACDEED < NA) and
(0 <= PACDEEE < NA) and
(0 <= PACDEEF < NA) and
(0 <= PACDEEG < NA) and
(0 <= PACDEEH < NA) and
(0 <= PACDEEI < NA) and
(0 <= PACDEEJ < NA) and
(0 <= PACDEEK < NA) and
(0 <= PACDEEL < NA) and
(0 <= PACDEEM < NA) and
(0 <= PACDEEN < NA) and
(0 <= PACDEEO < NA) and
(0 <= PACDEEP < NA) and
(0 <= PACDEEQ < NA) and
(0 <= PACDEER < NA) and
(0 <= PACDEES < NA) and
(0 <= PACDEET < NA) and
(0 <= PACDEEU < NA) and
(0 <= PACDEEV < NA) and
(0 <= PACDEEX < NA) and
(0 <= PACDEEY < NA)
Total daily energy expenditure (kcal/kg/day) Rounded to one decimal place (min: 0.0; max: 99.5)

 

2. PACDFM - Average Monthly Frequencyof Physical Activity Lasting Over 15 Minutes

Variable name:
PACDFM

Based on:
PAC_11W, PAC_12A, PAC_12B, PAC_12C, PAC_12D, PAC_12E, PAC_12F,PAC_12G, PAC_12H, PAC_12I, PAC_12J, PAC_12K, PAC_12L, PAC_12M,PAC_12N, PAC_12O, PAC_12P, PAC_12Q, PAC_12R, PAC_12S,PAC_12T,PAC_12U, PAC_12V, PAC_12X, PAC_12Y, PAC_13A, PAC_13B, PAC_13C,PAC_13D, PAC_13E, PAC_13F, PAC_13G, PAC_13H, PAC_13I, PAC_13J,PAC_13K, PAC_13L, PAC_13M, PAC_13N, PAC_13O, PAC_13P, PAC_13Q,PAC_13R, PAC_13S, PAC_13T, PAC_31U, PAC_13V, PAC_13X, PAC_13Y,DHH_AGE

Description:
This variable measures the total number of times per month thatrespondents took part in a physical activity(ies) lasting more than15 minutes.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents less than 12 years of age were excluded from thepopulation.
The survey questions refer to "the past three months". Thisvariable calculates a one-month average by dividing the totalreported frequency by three.

Source:
Ontario Health Survey

Internet site:
www.chass.utoronto.ca/datalib/codebooks/utm/ohs/ohs90.htm

Table 2
PACDFM Temporary Reformat

PACT2A

Value Condition(s) Description Notes
0 (PAC_13A = 1, NA, DK, RF, NS) Set all values for PAC_12A (number of times/3months respondentsdid physical activity) to 0 if PAC_13A is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)  
PAC_12A Else Set PACT2A = PAC_12A  

PACT2B

Value Condition(s) Description Notes
0

(PAC_13B = 1, NA, DK, RF, NS)

Set all values for PAC_12B (number of times/3months respondentsdid physical activity) to 0 if PAC_13B is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 

PAC_12B Else Set PACT2B = PAC_12B  

PACT2C

Value Condition(s) Description Notes
0

(PAC_13C = 1, NA, DK, RF, NS)

Set all values for PAC_12C (number of times/3months respondentsdid physical activity) to 0 if PAC_13C is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 

PAC_12C Else Set PACT2C = PAC_12C  

PACT2D

Value Condition(s) Description Notes
0

(PAC_13D = 1, NA, DK, RF, NS)

Set all values for PAC_12D (number of times/3months respondentsdid physical activity) to 0 if PAC_13D is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 

PAC_12D Else Set PACT2D = PAC_12D  

PACT2E

Value Condition(s) Description Notes
0

(PAC_13E = 1, NA, DK, RF, NS)

Set all values for PAC_12E (number of times/3months respondentsdid physical activity) to 0 if PAC_13E is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 

PAC_13E Else Set PACT2E = PAC_12E  

PACT2F

Value Condition(s) Description Notes
0

(PAC_13F = 1, NA, DK, RF, NS)

Set all values for PAC_12F (number of times/3months respondentsdid physical activity) to 0 if PAC_13F is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 

PAC_12F Else Set PACT2F = PAC_12F  

PACT2G

Value Condition(s) Description Notes
0

(PAC_13G = 1, NA, DK, RF, NS)

Set all values for PAC_12G (number of times/3months respondentsdid physical activity) to 0 if PAC_13G is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 

PAC_12G Else Set PACT2G = PAC_12G  

PACT2H

Value Condition(s) Description Notes
0

(PAC_13H = 1, NA, DK, RF, NS)

Set all values for PAC_12H (number of times/3months respondentsdid physical activity) to 0 if PAC_13H is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 

PAC_12H Else Set PACT2H = PAC_12H  

PACT2I

Value Condition(s) Description Notes
0

(PAC_13I = 1, NA, DK, RF, NS)

Set all values for PAC_12I (number of times/3months respondentsdid physical activity) to 0 if PAC_13I is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 

PAC_12I Else Set PACT2I = PAC_12I  

PACT2J

Value Condition(s) Description Notes
0

(PAC_13J = 1, NA, DK, RF, NS)

Set all values for PAC_12J (number of times/3months respondentsdid physical activity) to 0 if PAC_13J is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 

PAC_12J Else Set PACT2J = PAC_12J  

PACT2K

Value Condition(s) Description Notes
0

(PAC_13K = 1, NA, DK, RF, NS)

Set all values for PAC_12K (number of times/3months respondentsdid physical activity) to 0 if PAC_13K is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 

PAC_12K Else Set PACT2K = PAC_12K  

PACT2L

Value Condition(s) Description Notes
0

(PAC_13L = 1, NA, DK, RF, NS)

Set all values for PAC_12L (number of times/3months respondentsdid physical activity) to 0 if PAC_13L is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 

PAC_12L Else Set PACT2L = PAC_12L  

PACT2M

Value Condition(s) Description Notes
0

(PAC_13M = 1, NA, DK, RF, NS)

Set all values for PAC_12M (number of times/3months respondentsdid physical activity) to 0 if PAC_13M is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 

PAC_12M Else Set PACT2M = PAC_12M  

PACT2N

Value Condition(s) Description Notes
0

(PAC_13N = 1, NA, DK, RF, NS)

Set all values for PAC_12N (number of times/3months respondentsdid physical activity) to 0 if PAC_13N is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 

PAC_12N Else Set PACT2N = PAC_12N  

PACT2O

Value Condition(s) Description Notes
0

(PAC_13O = 1, NA, DK, RF, NS)

Set all values for PAC_12O (number of times/3months respondentsdid physical activity) to 0 if PAC_13O is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 

PAC_12O Else Set PACT2O = PAC_12O  

PACT2P

Value Condition(s) Description Notes
0

(PAC_13P = 1, NA, DK, RF, NS)

Set all values for PAC_12P (number of times/3months respondentsdid physical activity) to 0 if PAC_13P is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 

PAC_12P Else Set PACT2P = PAC_12P  

PACT2Q

Value Condition(s) Description Notes
0

(PAC_13Q = 1, NA, DK, RF, NS)

Set all values for PAC_12Q (number of times/3months respondentsdid physical activity) to 0 if PAC_13Q is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 

PAC_12Q Else Set PACT2Q = PAC_12Q  

PACT2R

Value Condition(s) Description Notes
0

(PAC_13R = 1, NA, DK, RF, NS)

Set all values for PAC_12R (number of times/3months respondentsdid physical activity) to 0 if PAC_13R is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 

PAC_12R Else Set PACT2R = PAC_12R  

PACT2S

Value Condition(s) Description Notes
0

(PAC_13S = 1, NA, DK, RF, NS)

Set all values for PAC_12S (number of times/3months respondentsdid physical activity) to 0 if PAC_13S is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 

PAC_12S Else Set PACT2S = PAC_12S  

PACT2T

Value Condition(s) Description Notes
0

(PAC_13T = 1, NA, DK, RF, NS)

Set all values for PAC_12T (number of times/3months respondentsdid physical activity) to 0 if PAC_13T is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 

PAC_12T Else Set PACT2T = PAC_12T  

PACT2U

Value Condition(s) Description Notes
0

(PAC_13U = 1, NA, DK, RF, NS)

Set all values for PAC_12U (number of times/3months respondentsdid physical activity) to 0 if PAC_13U is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 

PAC_12U Else Set PACT2U = PAC_12U  

PACT2V

Value Condition(s) Description Notes
0

(PAC_13V = 1, NA, DK, RF, NS)

Set all values for PAC_12V (number of times/3months respondentsdid physical activity) to 0 if PAC_13V is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 

PAC_12V Else Set PACT2V = PAC_12V  

PACT2X

Value Condition(s) Description Notes
0

(PAC_13X = 1, NA, DK, RF, NS)

Set all values for PAC_12X (number of times/3months respondentsdid physical activity) to 0 if PAC_13X is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 

PAC_12X Else Set PACT2X = PAC_12X  

PACT2Y

Value Condition(s) Description Notes
0

(PAC_13Y = 1, NA, DK, RF, NS)

Set all values for PAC_12Y (number of times/3months respondentsdid physical activity) to 0 if PAC_13Y is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 

PAC_12Y Else Set PACT2Y = PAC_12Y  

 

Table 2
PACDFM Specifications
Value Condition(s) Description Notes
996 DHH_AGE < 12 or
PAC_11W = NA
Population exclusions NA
999 (PAC_11W = DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) NS
0 PAC_11W=1 No physical activity  
(PACT2A +
PACT2B +
PACT2C +
PACT2D +
PACT2E +
PACT2F +
PACT2G +
PACT2H +
PACT2I +
PACT2J +
PACT2K +
PACT2L +
PACT2M +
PACT2N +
PACT2O +
PACT2P +
PACT2Q +
PACT2R +
PACT2S +
PACT2T +
PACT2U +
PACT2V +
PACT2X +
PACT2Y) / 3
(0 <= PACT2A < NA) and
(0 <= PACT2B < NA) and
(0 <= PACT2C < NA) and
(0 <= PACT2D < NA) and
(0 <= PACT2E < NA) and
(0 <= PACT2F < NA) and
(0 <= PACT2G < NA) and
(0 <= PACT2H < NA) and
(0 <= PACT2I < NA) and
(0 <= PACT2J < NA) and
(0 <= PACT2K < NA) and
(0 <= PACT2L < NA) and
(0 <= PACT2M < NA) and
(0 <= PACT2N < NA) and
(0 <= PACT2O < NA) and
(0 <= PACT2P < NA) and
(0 <= PACT2Q < NA) and
(0 <= PACT2R <NA) and
(0 <= PACT2S < NA) and
(0 <= PACT2T < NA) and
(0 <= PACT2U < NA) and
(0 <= PACT2V < NA) and
(0 <= PACT2X < NA) and
(0 <= PACT2Y < NA)
Monthly frequency of all physical activity lasting over 15minutes Rounded to nearest integer (min: 0;  max: 995)

 

3. PACDFR - Frequency of All PhysicalActivity Lasting Over 15 Minutes

Variable name:
PACDFR

Based on:
DHH_AGE, PACDFM

Description:
This variable classifies respondents according to their pattern, orregularity of physical activity lasting more than 15 minutes.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents less than 12 years of age were excluded from thepopulation.
This variable uses values for the derived variable MonthlyFrequency of Physical Activity (PACDFM). The values for PACDFMreflect a one-month average based on data reported for athree-month period.

Table 3
PACDFR Specifications
Value Condition(s) Description Notes
6 DHH_AGE < 12 or
PACDFM = NA
Population exclusion NA
9 PACDFM = NS Required question was not answered (don’t know, refusal,not stated) NS
1 (12 <= PACDFM < NA) Regular practice of activities  
2 (4 <= PACDFM < 12) Occasional practice of activities  
3 PACDFM < 4 Infrequent practice of activities  

4. PACDPAI - Physical ActivityIndex

Variable name:
PACDPAI

Based on:
DHH_AGE, PACDEE

Description:
This variable categorizes respondents as being "active","moderate", or "inactive" based on the total daily EnergyExpenditure values (kcal/kg/day) calculated for PACDEE.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents less than 12 years of age were excluded from thepopulation.
The Physical Activity Index follows the same criteria used tocategorize individuals in the Ontario Health Survey (OHS) and inthe Campbell’s Survey on Well Being.

Internet site:
Campbell Survey on Well-Being in Canada: www.cflri.ca/cflri/pa/surveys/88survey.html

Table 4
PACDPAI Specifications
Value Condition(s) Description Notes
6 DHH_AGE < 12 or
PACDEE = NA
Population exclusions NA
9 PACDEE = NS Required question was not answered (don’t know, refusal,not stated) NS
1 (3 <= PACDEE < NA) Active  
2 (1.5 <= PACDEE < 3.0) Moderate  
3 (0 <= PACDEE < 1.5) Inactive  

5. PACFD - Participant In DailyPhysical Activity Lasting Over 15 Minutes

Variable name:
PACFD

Based on:
DHH_AGE, PACDFM

Description:
This variable indicates whether the respondent participated dailyin physical activity lasting over 15 minutes.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents less than 12 years of age were excluded from thepopulation.
This variable is based on values for Monthly Frequency of PhysicalActivity (PACDFM).  Values for PACDFM reflect a one-monthaverage based on data reported for a three-month period.

Table 5
PACFD Specifications
Value Condition(s) Description Notes
6 DHH_AGE < 12 or
PACDFM = NA
Population exclusions NA
9 PACDFM = NS Required question was not answered (don’t know, refusal,not stated) NS
1 (30 <= PACDFM < NA) Participates in daily physical activity  
2 PACDFM < 30 Does not participate in daily physical activity  

6. PACFLEI - Participant In LeisurePhysical Activity

Variable name:
PACFLEI

Based on:
DHH_AGE, PAC_11W

Description:
This variable indicates whether the respondent participated in anyleisure physical activities in the three months prior to theinterview.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents less than 12 years of agewere excluded from the population.

Source:
Ontario Health Survey

Internet site:
www.chass.utoronto.ca/datalib/codebooks/utm/ohs/ohs90.htm

Table 6
PACFLEI Specifications
Value Condition(s) Description Notes
6 DHH_AGE < 12 or
PAC_11W = NA
Population exclusions NA
9 (PAC_11W = DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) NS
1 PAC_11W = 2 Participates in leisure physical activity  
2 PAC_11W = 1 Does not participate in leisure physical activity  

Partial Curl-Ups (2 DVs)

1. PCCDELG - Eligibility - PartialCurl-up component

Variable name:
PCCDELG

Based on:
CLC_AGE, V2_TYPE, ATG_13, ATG_33B, PHC_11, PHC_12, PHC_36, PHC_37,PHC_42G, MHR_611B, PAR_11, PAR_21, PAR_31,PAR_5A3A, PAR_5B3A, PAR_5B3A, PAR_5D3A, PAR_5E3A, PAR_5F3A,PAR_5G3A, PAR_5H3A, PAR_5I3A, PAR_5J3A, PAR_5K3A, PAR_62E, PAR_72D,ORS_3, BPMDBPS, BPMDBPD, BPMDHR

Description:
This variable indicates whether the respondent was eligible for thePartial Curl-up component. As there are multiple reasons to bescreened out of this measure, the prevalence of screen outs byreason should not be based on frequency counts for thisvariable.

Note:
Created in the Clinic Post-Verify process.

Table 1
PCCDELG Specifications
Value Condition(s) Description Notes
2 V2_TYPE = 2 Not eligible - home visit  
3 CLC_AGE > 69 Not eligible - age  
5 ATG_33D = 1 Not eligible - drank alcohol too close to visit time  
6 PHC_11 = 1 and
(12 < PHC_12 < NA)
Not eligible - more than 12 weeks pregnant  
9 PHC_42J = 1 Not eligible - acute or chronic condition  
12 MHR_611E = 1 Not eligible - medication use  
13 PAR_N11 = 1 or
PAR_21 = 1 or
PAR_31 = 1 or
PAR_5A3A = 1 or
PAR_5B3A = 1 or
PAR_5C3A = 1 or
PAR_5D3A = 1 or
PAR_5E3A = 1 or
PAR_5F3A = 1 or
PAR_5G3A = 1 or
PAR_5H3A = 1 or
PAR_5I3A = 1 or
PAR_5J3A = 1 or
PAR_5K3A = 1 or
PAR_62E = 1 or
PAR_72D = 1
Not eligible - PAR-Q answer  
14 ORS_5 = 1 Not eligible - other reason  
15 (CLC_AGE > 14 and
(144 < BPMDBPS < NA)) or
(CLC_AGE > 14 and
(144 < BPMDBPD < NA))
Not eligible - high blood pressure  
16 CLC_AGE > 14 and
(99 < BPMDHR < NA)
Not eligible - high heart rate  
1 Else Eligible  

2. PCMD11 - Partial curl-up norms forrespondents 15 - 69

Variable name:
PCMD11

Based on:
CLC_AGE, CLC_SEX, PCM_01

De2. scription:
This variable indicates the partial curl-up norms for respondents15 - 69.

Note:
Created in the Clinic data collection application. 
This variable applies to respondents aged 15-69 years old. Thecategories are:
Needs improvement
Fair
Good
Very good
Excellent

Source:
The Canadian Physical Activity, Fitness and Lifestyle Approach (3rdEdition, 2004) by the Canadian Society for Exercise Physiology(CSEP)

Table 2
PCMD11 Specifications
Value Condition(s) Description Notes
6 CLC_AGE < 15 or
CLC_AGE > 69 or
PCM_01 = NA
Population exclusions NA
9 PCM_01 > NA At least one required question was not answered (don’tknow, refusal, not stated) NS
0 (CLC_SEX = 1 and
((CLC_AGE < 20 and
PCM_01 < 16) or
((19 < CLC_AGE < 30) and
PCM_01 < 11) or
((29 < CLC_AGE < 40) and
PCM_01 < 11) or
((39 < CLC_AGE < 50) and
PCM_01 < 6) or
((49 < CLC_AGE < 60) and
PCM_01 < 8) or
(CLC_AGE > 59 and
PCM_01 < 6)) or
(CLC_SEX = 2 and
((CLC_AGE < 20 and
PCM_01 < 12) or
((19 < CLC_AGE < 30) and
PCM_01 < 5) or
((29 < CLC_AGE < 40) and
PCM_01 < 6) or
((39 < CLC_AGE < 50) and
PCM_01 < 4) or
((49 < CLC_AGE < 60) and
PCM_01 < 6) or
(CLC_AGE > 59 and
PCM_01 < 3))
Needs improvement  
1 (CLC_SEX = 1 and
(((19 < CLC_AGE < 30) and
(10 < PCM_01 < 16)) or
((29 < CLC_AGE < 40) and
(10 < PCM_01 < 15)) or
((39 < CLC_AGE < 50) and
(5 < PCM_01 < 13)) or
((49 < CLC_AGE < 60) and
(7 < PCM_01 < 11)) or
(CLC_AGE > 59 and
(5 < PCM_01 < 11))) or
(CLC_SEX = 2 and
((CLC_AGE < 20 and
(11 < PCM_01 < 17)) or
((19 < CLC_AGE < 30) and
(4 < PCM_01 < 14)) or
((29 < CLC_AGE < 40) and
(5 < PCM_01 < 10)) or
((39 < CLC_AGE < 50) and
(3 < PCM_01 < 11)) or
((49 < CLC_AGE < 60) and
(5 < PCM_01 < 10)) or
(CLC_AGE > 59 and
(2 < PCM_01 < 8)))
Fair  
2 (CLC_SEX = 1 and
((CLC_AGE < 20 and
(20 < PCM_01 < 23)) or
((19 < CLC_AGE < 30) and
(15 < PCM_01 < 21)) or
((29 < CLC_AGE < 40) and
(14 < PCM_01 < 18)) or
((39 < CLC_AGE < 50) and
(12 < PCM_01 < 18)) or
((49 < CLC_AGE < 60) and
(10 < PCM_01 < 17)) or
(CLC_AGE > 59 and
(10 < PCM_01 < 16))) or
(CLC_SEX = 2 and
((CLC_AGE < 20 and
(16 < PCM_01 < 22)) or
((19 < CLC_AGE < 30) and
(13 < PCM_01 < 18)) or
((29 < CLC_AGE < 40) and
(9 < PCM_01 < 19)) or
((39 < CLC_AGE < 50) and
(10 < PCM_01 < 19)) or
((49 < CLC_AGE < 60) and
(9 < PCM_01 < 19)) or
(CLC_AGE > 59 and
(7 < PCM_01 < 17)))
Good  
3 (CLC_SEX = 1 and
((CLC_AGE < 20 and
(22 < PCM_01 < 25)) or
((19 < CLC_AGE < 30) and
(20 < PCM_01 < 25)) or
((29 < CLC_AGE < 40) and
(17 < PCM_01 < 25)) or
((39 < CLC_AGE < 50) and
(17 < PCM_01 < 25)) or
((49 < CLC_AGE < 60) and
(16 < PCM_01 < 25)) or
(CLC_AGE > 59 and
(15 < PCM_01 < 25))) or
(CLC_SEX = 2 and
((CLC_AGE < 20 and
(21 < PCM_01 < 25)) or
((19 < CLC_AGE < 30) and
(17 < PCM_01 < 25)) or
((29 < CLC_AGE < 40) and
(18 < PCM_01 < 25)) or
((39 < CLC_AGE < 50) and
(18 < PCM_01 < 25)) or
((49 < CLC_AGE < 60) and
(18 < PCM_01 < 25)) or
(CLC_AGE > 59 and
(16 < PCM_01 < 25)))
Very good  
4 Else Excellent  

Phlebotomy (2 DVs)

1. BDCD13 - Blood donationstatus

Variable name:
BDCD13

Based on:
BDC_12, BDC_13D, BDC_13M, BDC_13Y, V2_DAY, V2_MONTH, V2_YEAR

Description:
This variable indicates whether the respondent gave blood the daybefore the clinic visit.

Note:
Created in the Clinic data collection application.

Table 1
BDCD13 Temporary Reformat

V2_YDAY

 

Value Condition(s) Description Notes
V2_DAY - 1

All records

 

 


V2_YMTH

 

 

Value Condition(s) Description Notes
V2_MTH - 1

V2_DAY = 1

 

 

V2_MTH

Else

 

 


V2_YYEAR

 

 

Value Condition(s) Description Notes
V2_YEAR - 1

V2_DAY = 1 and
V2_MTH = 1

 

 

V2_YEAR

Else

 

 

 

 

Table 1
BDCD13 Specifications
Value Condition(s) Description Notes
9 (BDC_12 = DK, RF, NS) At least one required question was not answered (don’tknow, refusal, not stated) NS
6 (1 < PHBDELG < NA) Population exclusions NA
1 BDC_13Y = V2_YYEAR and
BDC_13M = V2_YMTH and
BDC_13D = V2_YDAY
Donated blood the day before the clinic visit  
2 Else Did not donate blood the day before the clinic  

 

2. PHBDELG - Eligibility - Phlebotomycomponent

Variable name:
PHBDELG

Based on:
PHC_42A, PHC_51, PHC_52

Description:
This variable indicates whether the respondent was eligible for thePhlebotomy component. As there are multiple reasons to be screenedout of this measure, the prevalence of screen outs by reason shouldnot be based on frequency counts for this variable.

Note:
Created in the Clinic Post-Verify process.

Table 2
PHBDELG Specifications
Value Condition(s) Description Notes
9 PHC_42A = 1 Not eligible - acute or chronic condition  
10 PHC_51 = 1 Not eligible - hemophilia  
11 PHC_52 = 1 Not eligible - received chemoptherapy in past four weeks  
1 Else Eligible  

Report of Measurements (2DVs)

1. RMCDBCK - Back fitness norms forrespondents 15 – 69

Variable name:
RMCDBCK

Based on:
CLC_AGE, CLC_SEX, HWMDWSTA, SRMD12, PCMD11

Description:
This variable indicates the back fitness norms for respondents aged 15 to 69,  based on the norms for Partial Curl-Ups, Waist Circumference and Sit and Reach.

Note:
Created in the Clinic Post-Verify process.
This variable applies to respondents aged 15-69 years old. Thecategories are:
Considerable health risk
Some health risk
Many health benefits
Considerable health benefits
Optimal health benefits

Table 1
RMCDBCK Temporary Reformat

PTS3

Value Condition(s) Description Notes
Round(((HWMDWSTA + SRMD12 + PCMD11) / 3), .1) CLC_SEX = 1 and
HWMDWSTA in (0,1,2,3,4) and
SRMD12 in (0,1,2,3,4) and
PCMD11 in (0,1,2,3,4)
Calculation for male back fitness given all three norms, i.e.,Waist Circumference, Sit and Reach, and Partial Curl-Up. Rounded to one decimal place
0 CLC_SEX = 1 and
HWMDWSTA in (0,1,2,3,4) and
SRMD12 in (0,1,2,3,4) and
(PCMD11 = DK, RF, NS) and
(HWMDWSTA + SRMD12 = 1)
Value for male back fitness given Waist Circumference and Sitand Reach norms only (no Partial Curl-Up norms), where the sum ofthe available norms is 1  
1 CLC_SEX = 1 and
HWMDWSTA in (0,1,2,3,4) and
SRMD12 in (0,1,2,3,4) and
(PCMD11 = DK, RF, NS) and
(HWMDWSTA + SRMD12 = 3)
Value for male back fitness given Waist Circumference and Sitand Reach norms only (no Partial Curl-Up norms), where the sum ofthe available norms is 3.  
Round(((HWMDWSTA + SRMD12) / 2), .1) CLC_SEX = 1 and
HWMDWSTA in (0,1,2,3,4) and
SRMD12 in (0,1,2,3,4) and
(PCMD11 = DK, RF, NS) and
((HWMDWSTA + SRMD12) not in (1, 3))
Calculation for male back fitness given Waist Circumference andSit and Reach norms only (no Partial Curl-Up norms), where the sumof the available norms is not 1 or 3. Rounded to one decimal place
0 CLC_SEX = 1 and
HWMDWSTA in (0,1,2,3,4) and
(SRMD12 = DK, RF, NS) and
PCMD11 in (0,1,2,3,4) and
(HWMDWSTA + PCMD11 = 1)
Value for male back fitness given Waist Circumference andPartial Curl-Up norms only (no Sit and Reach norms), where the sumof the available norms is 1  
1 CLC_SEX = 1 and
HWMDWSTA in (0,1,2,3,4) and
(SRMD12 = DK, RF, NS) and
PCMD11 in (0,1,2,3,4) and
(HWMDWSTA + PCMD11 = 3)
Value for male back fitness given Waist Circumference andPartial Curl-Up norms only (no Sit and Reach norms), where the sumof the available norms is 3.  
Round(((HWMDWSTA + PCMD11) / 2), .1) CLC_SEX = 1 and
HWMDWSTA in (0,1,2,3,4) and
(SRMD12 = DK, RF, NS) and
PCMD11 in (0,1,2,3,4) and
((HWMDWSTA + PCMD11) not in (1, 3))
Calculation for male back fitness given Waist Circumference andPartial Curl-Up norms only (no Sit and Reach norms), where the sumof the available norms is not 1 or 3 Rounded to one decimal place
0 CLC_SEX = 2 and
HWMDWSTA in (0,1,2,3,4) and
SRMD12 in (0,1,2,3,4) and
PCMD11 in (0,1,2,3,4) and
(HWMDWSTA * 2 + SRMD12 + PCMD11 = 2)
Value for female back fitness given all three norms (i.e.,Waist Circumference, Sit and Reach, and Partial Curl-Up), whereHWMDWSTA * 2 + SRMD12 + PCMD11 = 2  
1 CLC_SEX = 2 and
HWMDWSTA in (0,1,2,3,4) and
SRMD12 in (0,1,2,3,4) and
PCMD11 in (0,1,2,3,4) and
(HWMDWSTA * 2 + SRMD12 + PCMD11 = 6)
Value for female back fitness given all three norms (i.e.,Waist Circumference, Sit and Reach, and Partial Curl-Up), whereHWMDWSTA * 2 + SRMD12 + PCMD11 = 6  
Round(((HWMDWSTA * 2 + SRMD12 + PCMD11) / 4), .1) CLC_SEX = 2 and
HWMDWSTA in (0,1,2,3,4) and
SRMD12 in (0,1,2,3,4) and
PCMD11 in (0,1,2,3,4) and
((HWMDWSTA * 2 + SRMD12 + PCMD11) not in (2, 6))
Calculation for female back fitness given all three norms(i.e., Waist Circumference, Sit and Reach, and Partial Curl-Up),where (HWMDWSTA * 2 + SRMD12 + PCMD11) not in (2, 6) Rounded to one decimal place
Round(((HWMDWSTA * 2 + SRMD12) / 3), .1) CLC_SEX = 2 and
HWMDWSTA in (0,1,2,3,4) and
SRMD12 in (0,1,2,3,4) and
(PCMD11 = DK, RF, NS)
Calculation for female back fitness given Waist Circumferenceand Sit and Reach norms only (no Partial Curl-Up norms) Rounded to one decimal place
Round(((HWMDWSTA * 2 + PCMD11) / 3), .1) CLC_SEX = 2 and
HWMDWSTA in (0,1,2,3,4) and
(SRMD12 = DK, RF, NS) and
PCMD11 in (0,1,2,3,4)
Calculation for female back fitness given Waist Circumferenceand Partial Curl-Up norms only (no Sit and Reach norms) Rounded to one decimal place
0 (HWMDWSTA = DK, RF, NS) and
SRMD12 in (0,1,2,3,4) and
PCMD11 in (0,1,2,3,4) and
(SRMD12 + PCMD11 = 1)
Value for back fitness given Sit and Reach and Partial Curl-Upnorms only (no Waist Circumference norms), where the sum of theavailable norms is 1  
1 (HWMDWSTA = DK, RF, NS) and
SRMD12 in (0,1,2,3,4) and
PCMD11 in (0,1,2,3,4) and
(SRMD12 + PCMD11 = 3)
Value for back fitness given Sit and Reach and Partial Curl-Upnorms only (no Waist Circumference norms), where the sum of theavailable norms is 3  
Round(((SRMD12 + PCMD11) / 2), .1) (HWMDWSTA = DK, RF, NS) and
SRMD12 in (0,1,2,3,4) and
PCMD11 in (0,1,2,3,4) and
((SRMD12 + PCMD11) not in (1, 3))
Calculation for back fitness given Sit and Reach and PartialCurl-Up norms only (no Waist Circumference norms), where the sum ofthe available norms is not 1 or 3 Rounded to one decimal place
HWMDWSTA HWMDWSTA in (0,1,2,3,4) and
(SRMD12 = DK, RF, NS) and
(PCMD11 = DK, RF, NS)
Calculation for back fitness given Waist Circumference normsonly (no Sit and Reach or Partial Curl-Up norms)  
SRMD12 (HWMDWSTA = DK, RF, NS) and
SRMD12 in (0,1,2,3,4) and
(PCMD11 = DK, RF, NS)
Calculation for back fitness given Sit and Reach norms only (noWaist Circumference or Partial Curl-Up norms)  
PCMD11 (HWMDWSTA = DK, RF, NS) and
(SRMD12 = DK, RF, NS) and
PCMD11 in (0,1,2,3,4)
Calculation for back fitness given Partial Curl-Up norms only(no Waist Circumference or Sit and Reach norms)  

 

Table 1
RMCDBCK Specifications
Value Condition(s) Description Notes
6 CLC_AGE < 15 or
CLC_AGE > 69
Population exclusions NA
9 HWMD24 > NA and
SRMD12 > NA and
PCMD11 > NA
At least one required question was not answered (don’tknow, refusal, not stated) NS
6 HWMD24 = NA and
SRMD12 = NA and
PCMD11 = NA
Population exclusions NA
0 PTS3 = 0 or
(0.0 < PTS3 < 0.5)
Needs Improvement. Respondent's back fitness falls within arange that is generally associated with considerable healthrisk.  
1 (0.4 < PTS3 < 1.5) Fair. Respondent's back fitness falls within a range that isgenerally associated with some health risk.  
2 (1.4 < PTS3 < 2.5) Good. Respondent's back fitness falls within a range that isgenerally associated with many health benefits.  
3 (2.4 < PTS3 < 3.5) Very Good. Respondent's back fitness falls within a range thatis generally associated with considerable health benefits.  
4 (3.4 < PTS3 < 5.0) Excellent. Respondent's back fitness falls within a range thatis generally associated with optimal health benefits.  

 

2. RMCDMSK - Musculo-skeletal fitnessnorms for respondents 15 – 69

Variable name:
RMCDMSK

Based on:
CLC_AGE, CLC_SEX, GSMD52, SRMD12, PCMD11

Description:
This variable indicates the musculo-skeletal fitness norms for respondents aged 15 to 69,  based on the norms for Sit and Reach, Grip Strength and Partial Curl-Ups.

Note:
Created in the Clinic Post-Verify process.
This variable applies to respondents aged 15-69 years old. Thecategories are:
Considerable health risk
Some health risk
Many health benefits
Considerable health benefits
Optimal health benefits

Table 2
RMCDMSK Temporary Reformat

PTS2

Value Condition(s) Description Notes
Round(((GSMD52 * 2 + SRMD12 + PCMD11) / 4), .1) CLC_SEX = 1 and
GSMD52 in (0,1,2,3,4) and
SRMD12 in (0,1,2,3,4) and
PCMD11 in (0,1,2,3,4)
Calculation for male musculo-skeletal fitness given all threenorms, i.e., Grip Strength, Sit and Reach, and PartialCurl-Up. Rounded to one decimal place
Round(((GSMD52 * 2 + SRMD12) / 3), .1) CLC_SEX = 1 and
GSMD52 in (0,1,2,3,4) and
SRMD12 in (0,1,2,3,4) and
(PCMD11 = DK, RF, NS)
Calculation for male musculo-skeletal fitness given GripStrength and Sit and Reach norms only (no Partial Curl-Upnorms). Rounded to one decimal place
Round(((GSMD52 * 2 + PCMD11) / 3), .1) CLC_SEX = 1 and
GSMD52 in (0,1,2,3,4) and
(SRMD12 = DK, RF, NS) and
PCMD11 in (0,1,2,3,4)
Calculation for male musculo-skeletal fitness given GripStrength and Partial Curl-Up norms only (no Sit and Reachnorms). Rounded to one decimal place
0 CLC_SEX = 1 and
(GSMD52 = DK, RF, NS) and
SRMD12 in (0,1,2,3,4) and
PCMD11 in (0,1,2,3,4) and
(SRMD12 + PCMD11 = 1)
Value for male musculo-skeletal fitness given Sit and Reach andPartial Curl-Up norms only (no Grip Strength norms), where the sumof the available norms is 1.  
1 CLC_SEX = 1 and
(GSMD52 = DK, RF, NS) and
SRMD12 in (0,1,2,3,4) and
PCMD11 in (0,1,2,3,4) and
(SRMD12 + PCMD11 = 3)
Value for male musculo-skeletal fitness given Sit and Reach andPartial Curl-Up norms only (no Grip Strength norms), where the sumof the available norms is 3.  
Round(((SRMD12 + PCMD11) / 2), .1) CLC_SEX = 1 and
(GSMD52 = DK, RF, NS) and
SRMD12 in (0,1,2,3,4) and
PCMD11 in (0,1,2,3,4) and
((SRMD12 + PCMD11) not in (1, 3))
Calculation for male musculo-skeletal fitness given Sit andReach and Partial Curl-Up norms only (no Grip Strength norms),where the sum of the available norms is not 1 or 3. Rounded to one decimal place
Round(((GSMD52 * 2 + SRMD12 * 2 + PCMD11) / 5), .1) CLC_SEX = 2 and
GSMD52 in (0,1,2,3,4) and
SRMD12 in (0,1,2,3,4) and
PCMD11 in (0,1,2,3,4)
Calculation for female musculo-skeletal fitness given all threenorms, i.e., Grip Strength, Sit and Reach, and PartialCurl-Up. Rounded to one decimal place
0 CLC_SEX = 2 and
GSMD52 in (0,1,2,3,4) and
SRMD12 in (0,1,2,3,4) and
(PCMD11 = DK, RF, NS) and
((GSM_D52 * 2 + SRM_D12 * 2) = 2)
Value for female musculo-skeletal fitness given Grip Strengthand Sit and Reach norms only (no Partial Curl-Up norms), where thesum of double the available norms is 2.  
1 CLC_SEX = 2 and
GSMD52 in (0,1,2,3,4) and
SRMD12 in (0,1,2,3,4) and
(PCMD11 = DK, RF, NS) and
((GSM_D52 * 2 + SRM_D12 * 2) = 6)
Value for female musculo-skeletal fitness given Grip Strengthand Sit and Reach norms only (no Partial Curl-Up norms), where thesum of double the available norms is 6.  
Round(((GSMD52 * 2 + SRMD12 * 2) / 4), .1) CLC_SEX = 2 and
GSMD52 in (0,1,2,3,4) and
SRMD12 in (0,1,2,3,4) and
(PCMD11 = DK, RF, NS) and
((GSM_D52 * 2 + SRM_D12 * 2) not in (2, 6))
Calculation for female musculo-skeletal fitness given GripStrength and Sit and Reach norms only (no Partial Curl-Up norms),where the sum of double the available norms is not 2 or 6. Rounded to one decimal place
Round(((GSMD52 * 2 + PCMD11) / 3), .1) CLC_SEX = 2 and
GSMD52 in (0,1,2,3,4) and
(SRMD12 = DK, RF, NS) and
PCMD11 in (0,1,2,3,4)
Calculation for female musculo-skeletal fitness given GripStrength and Partial Curl-Up norms only (no Sit and Reachnorms). Rounded to one decimal place
Round(((SRMD12 * 2 + PCMD11) / 3), .1) CLC_SEX = 2 and
(GSMD52 = DK, RF, NS) and
SRMD12 in (0,1,2,3,4) and
PCMD11 in (0,1,2,3,4)
Calculation for female musculo-skeletal fitness given Sit andReach and Partial Curl-Up norms only (no Grip Strength norms). Rounded to one decimal place
GSMD52 GSMD52 in (0,1,2,3,4) and
(SRMD12 = DK, RF, NS) and
(PCMD11 = DK, RF, NS)
Calculation for musculo-skeletal fitness given Grip Strengthnorms only (no Sit and Reach or Partial Curl-Up norms).  
SRMD12 (GSMD52 = DK, RF, NS) and
SRMD12 in (0,1,2,3,4) and
(PCMD11 = DK, RF, NS)
Calculation for musculo-skeletal fitness given Sit and Reachnorms only (no Grip Strength or Partial Curl-Up norms).  
PCMD11 (GSMD52 = DK, RF, NS) and
(SRMD12 = DK, RF, NS) and
PCMD11 in (0,1,2,3,4)
Calculation for musculo-skeletal fitness given Partial Curl-Upnorms only (no Grip Strength or Sit and Reach norms).  

 

Table 2
RMCDMSK Specifications
Value Condition(s) Description Notes
6 CLC_AGE < 15 or
CLC_AGE > 69
Population exclusions NA
9 GSMD52 > NA and
SRMD12 > NA and
PCMD11 > NA
At least one required question was not answered (don’tknow, refusal, not stated) NS
6 GSMD52 = NA and
SRMD12 = NA and
PCMD11 = NA
Population exclusions NA
0 PTS2 = 0 or
(0.0 < PTS2 < 0.5)
Needs Improvement. Respondent's musculo-skeletal fitness fallswithin a range that is generally associated with considerablehealth risk.  
1 (0.4 < PTS2 < 1.5) Fair. Respondent's musculo-skeletal fitness falls within arange that is generally associated with some health risk.  
2 (1.4 < PTS2 < 2.5) Good. Respondent's musculo-skeletal fitness falls within arange that is generally associated with many health benefits.  
3 (2.4 < PTS2 < 3.5) Very Good. Respondent's musculo-skeletal fitness falls within arange that is generally associated with considerable healthbenefits.  
4 (3.4 < PTS2 < 5.0) Excellent. Respondent's musculo-skeletal fitness falls within arange that is generally associated with optimal healthbenefits.  

 

Sedentary activities (1 DV)

Table
Sedentary activities Temporary Reformat

SAC_T11

Value Condition(s) Description Notes
0 SAC_11 = 1 Recode to midpoint of response ranges  
0.5 SAC_11 = 2 Recode to midpoint of response ranges  
1.5 SAC_11 = 3 Recode to midpoint of response ranges  
4 SAC_11 = 4 Recode to midpoint of response ranges  
8 SAC_11 = 5 Recode to midpoint of response ranges  
12.5 SAC_11 = 6 Recode to midpoint of response ranges  
17.5 SAC_11 = 7 Recode to midpoint of response ranges  
20 SAC_11 = 8 Recode to midpoint of response ranges  

SAC_T12

Value Condition(s) Description Notes
0 SAC_12 = 1 Recode to midpoint of response ranges  
0.5 SAC_12 = 2 Recode to midpoint of response ranges  
1.5 SAC_12 = 3 Recode to midpoint of response ranges  
4 SAC_12 = 4 Recode to midpoint of response ranges  
8 SAC_12 = 5 Recode to midpoint of response ranges  
12.5 SAC_12 = 6 Recode to midpoint of response ranges  
17.5 SAC_12 = 7 Recode to midpoint of response ranges  
20 SAC_12 = 8 Recode to midpoint of response ranges  

SAC_T13

Value Condition(s) Description Notes
0 SAC_13 = 1 Recode to midpoint of response ranges  
0.5 SAC_13 = 2 Recode to midpoint of response ranges  
1.5 SAC_13 = 3 Recode to midpoint of response ranges  
4 SAC_13 = 4 Recode to midpoint of response ranges  
8 SAC_13 = 5 Recode to midpoint of response ranges  
12.5 SAC_13 = 6 Recode to midpoint of response ranges  
17.5 SAC_13 = 7 Recode to midpoint of response ranges  
20 SAC_13 = 8 Recode to midpoint of response ranges  

SAC_T14

Value Condition(s) Description Notes
0 SAC_14 = 1 Recode to midpoint of response ranges  
0.5 SAC_14 = 2 Recode to midpoint of response ranges  
1.5 SAC_14 = 3 Recode to midpoint of response ranges  
4 SAC_14 = 4 Recode to midpoint of response ranges  
8 SAC_14 = 5 Recode to midpoint of response ranges  
12.5 SAC_14 = 6 Recode to midpoint of response ranges  
17.5 SAC_14 = 7 Recode to midpoint of response ranges  
20 SAC_14 = 8 Recode to midpoint of response ranges  

1. SACDTOT - Total Number of Hours PerWeek Spent In Sedentary Activities

Variable name:
SACDTOT

Based on:
DHH_AGE, SAC_11, SAC_12, SAC_13, SAC_14

Description:
This variable estimates the total number of hours the respondentspent in a typical week in past 3 months doing the followingsedentary activities: computer, computer games and Internet, videogames, television or videos and reading. For all activities, timespent at school or work is excluded.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents less than 12 years of age were excluded from thepopulation.

Table 1
SACDTOT Temporary Reformat

SAC

Value Condition(s) Description Notes
96 DHH_AGE < 12 Module not asked - respondent aged < 12 NA
99 (SAC_T11 = DK, RF, NS) or
(SAC_T12 = DK, RF, NS) or
(SAC_T13 = DK, RF, NS) or
(SAC_T14 = DK, RF, NS)
At least one required question was not answered (don't know,refusal, not stated) NS
SAC_T11 +
SAC_T12 +
SAC_T13 +
SAC_T14
(0 <= SAC_T11 <= 20) and
(0 <= SAC_T12 <= 20) and
(0 <= SAC_T13 <= 20) and
(0 <= SAC_T14 <= 20)
Total number of hours spent in sedentary activities.  

 

Table 1
SACDTOT Specifications
Value Condition(s) Description Notes
99 SAC = NS At least one required question was not answered (don't know,refusal, not stated) NS
96 SAC = NA Population exclusions NA
1 (0 <= SAC < 5) Less than 5 hours  
2 (5 <= SAC < 10) From 5 to less than 10 hours  
3 (10 <= SAC < 15) From 10 to less than 15  
4 (15 <= SAC < 20) From 15 to less than 20  
5 (20 <= SAC < 25) From 20 to less than 25 hours  
6 (25 <= SAC < 30) From 25 to less than 30 hours  
7 (30 <= SAC < 35) From 30 to less than 35 hours  
8 (35 <= SAC < 40) From 35 to less than 40 hours  
9 (40 <= SAC < 45) From 40 to less than 45 hours  
10 45 <= SAC More than 45 hours  

 

Screening (1 DV)

1. ATGD12 - Fasting status

Variable name:
ATGD12

Based on:
V2_HOUR, ATG_11H, ATG_12

Description:
This variable indicates whether the respondent had fasted for atleast 10 hours at the time of the clinic visit.

Note:
Created in the Clinic data collection application.

Table 1
ATGD12 Specifications
Value Condition(s) Description Notes
9 ATG_11H > NA At least one required question was not answered (don't know,refusal, not stated) NS
1 ATG_11H < V2_HOUR and
(V2_HOUR - ATG_11H) > 9
Respondent fasted 10 hours or more  
1 ATG_11H > V2_HOUR and
(24 + V2_HOUR - ATG_11H) > 9
Respondent fasted 10 hours or more  
1 ATG_12 = 1 Respondent met the fasting criteria  
2 ATG_12 = 2 Respondent was not fasted  

Socio-demographic characteristics (8DVs)

1. SDCDAIM - Age at time ofimmigration

Variable name:
SDCDAIM

Based on:
SDC_13, DHH_YOB

Description:
This variable indicates the age of the respondent at the time ofimmigration.

Introduced in:
CCHS - Cycle 1.1

Note:
Non-immigrants were excluded from the population.

Table 1
SDCDAIM Specifications
Value Condition(s) Description Notes
996 SDC_13 = NA Population exclusion NA
999 (SDC_13 = DK, RF, NS) At least one required question was not answered (don't know,refusal, not stated) NS
SDC_13 -
DHH_YOB
SDC_13 < NA Age at time of immigration [min: 0; max: 130 (current age)]

2. SDCDCGT - Culture / RaceFlag

Variable name:
SDCDCGT

Based on:
SDC_24A, SDC_24B, SDC_24C, SDC_24D, SDC_24E, SDC_24F, SDC_24G,SDC_24H, SDC_24I, SDC_24J, SDC_24K, SDC_24L, SDC_24M

Description:
This variable indicates the cultural or racial background of therespondent. It excludes all respondents who identify asaboriginal.

Introduced in:
CCHS - Cycle 3.1

Table 2
SDCDCGT Specifications
Value Condition(s) Description Notes
96 SDC_22 = 1 Aboriginal origin NA
99 (SDC_24A = DK, RF, NS) Required question was not answered (don't know, refusal, notstated) NS
1 SDC_24A = 1 and
SDC_24B > 1 and
SDC_24C > 1 and
SDC_24D > 1 and
SDC_24E > 1 and
SDC_24F > 1 and
SDC_24G > 1 and
SDC_24H > 1 and
SDC_24I > 1 and
SDC_24J > 1 and
SDC_24K > 1 and
SDC_24M > 1
White only  
2 SDC_24A > 1 and
SDC_24B > 1 and
SDC_24C > 1 and
SDC_24D = 1 and
SDC_24E > 1 and
SDC_24F > 1 and
SDC_24G > 1 and
SDC_24H > 1 and
SDC_24I > 1 and
SDC_24J > 1 and
SDC_24K > 1 and
SDC_24M > 1
Black only  
3 SDC_24A > 1 and
SDC_24B > 1 and
SDC_24C > 1 and
SDC_24D > 1 and
SDC_24E > 1 and
SDC_24F > 1 and
SDC_24G > 1 and
SDC_24H > 1 and
SDC_24I > 1 and
SDC_24J > 1 and
SDC_24K = 1 and
SDC_24M > 1
Korean only  
4 SDC_24A > 1 and
SDC_24B > 1 and
SDC_24C > 1 and
SDC_24D > 1 and
SDC_24E = 1 and
SDC_24F > 1 and
SDC_24G > 1 and
SDC_24H > 1 and
SDC_24I > 1 and
SDC_24J > 1 and
SDC_24K > 1 and
SDC_24M > 1
Filipino only  
5 SDC_24A > 1 and
SDC_24B > 1 and
SDC_24C > 1 and
SDC_24D > 1 and
SDC_24E > 1 and
SDC_24F > 1 and
SDC_24G > 1 and
SDC_24H > 1 and
SDC_24I > 1 and
SDC_24J = 1 and
SDC_24K > 1 and
SDC_24M > 1
Japanese only  
6 SDC_24A > 1 and
SDC_24B = 1 and
SDC_24C > 1 and
SDC_24D > 1 and
SDC_24E > 1 and
SDC_24F > 1 and
SDC_24G > 1 and
SDC_24H > 1 and
SDC_24I > 1 and
SDC_24J > 1 and
SDC_24K > 1 and
SDC_24M > 1
Chinese only  
7 SDC_24A > 1 and
SDC_24B > 1 and
SDC_24C = 1 and
SDC_24D > 1 and
SDC_24E > 1 and
SDC_24F > 1 and
SDC_24G > 1 and
SDC_24H > 1 and
SDC_24I > 1 and
SDC_24J > 1 and
SDC_24K > 1 and
SDC_24M > 1
South Asian only  
8 SDC_24A > 1 and
SDC_24B > 1 and
SDC_24C > 1 and
SDC_24D > 1 and
SDC_24E > 1 and
SDC_24F > 1 and
SDC_24G = 1 and
SDC_24H > 1 and
SDC_24I > 1 and
SDC_24J > 1 and
SDC_24K > 1 and
SDC_24M > 1
Southeast Asian only  
9 SDC_24A = 1 and
SDC_24B > 1 and
SDC_24C > 1 and
SDC_24D > 1 and
SDC_24E > 1 and
SDC_24F > 1 and
SDC_24G > 1 and
SDC_24H = 1 and
SDC_24I > 1 and
SDC_24J > 1 and
SDC_24K > 1 and
SDC_24M > 1
Arab only  
10 SDC_24A > 1 and
SDC_24B > 1 and
SDC_24C > 1 and
SDC_24D > 1 and
SDC_24E > 1 and
SDC_24F > 1 and
SDC_24G > 1 and
SDC_24H > 1 and
SDC_24I = 1 and
SDC_24J > 1 and
SDC_24K > 1 and
SDC_24M > 1
West Asian only  
11 SDC_24A > 1 and
SDC_24B > 1 and
SDC_24C > 1 and
SDC_24D > 1 and
SDC_24E > 1 and
SDC_24F = 1 and
SDC_24G > 1 and
SDC_24H > 1 and
SDC_24I > 1 and
SDC_24J > 1 and
SDC_24K > 1 and
SDC_24M > 1
Latin American only  
12 SDC_24A > 1 and
SDC_24B > 1 and
SDC_24C > 1 and
SDC_24D > 1 and
SDC_24E > 1 and
SDC_24F > 1 and
SDC_24G > 1 and
SDC_24H > 1 and
SDC_24I > 1 and
SDC_24J > 1 and
SDC_24K > 1 and
SDC_24M = 1
Other racial or cultural origin (only)  
13 SDC_22 > 1 and
More than one category answered
from SDC_24A to SDC_24M
Multiple racial or cultural origin  

3. SDCDFL1 - First official languagelearned and still understood

Variable name:
SDCDFL1

Based on:
SDC_33A, SDC_33B, SDC_33C, SDC_33D, SDC_33E, SDC_33F, SDC_33G,SDC_33H, SDC_33I, SDC_33J, SDC_33K, SDC_33L, SDC_33M, SDC_33N,SDC_33O, SDC_33P, SDC_33Q, SDC_33R, SDC_33S, SDC_33T, SDC_33U,SDC_33V, SDC_33W

Description:
This variable indicates the first official language spoken andstill understood by the respondent.

Introduced in:
CCHS - Cycle 2.1

Table 3
SDCDFL1 Specifications
Value Condition(s) Description Notes
99 (SDC_33A = DK, RF, NS) Required question was not answered (don't know, refusal, notstated) NS
1 SDC_33A = 1 and
SDC_33B > 1 and
SDC_33C > 1 and
SDC_33D > 1 and
SDC_33E > 1 and
SDC_33F > 1 and
SDC_33G > 1 and
SDC_33H > 1 and
SDC_33I > 1 and
SDC_33J > 1 and
SDC_33K > 1 and
SDC_33L > 1 and
SDC_33M > 1 and
SDC_33N > 1 and
SDC_33O > 1 and
SDC_33P > 1 and
SDC_33Q > 1 and
SDC_33R > 1 and
SDC_33S > 1 and
SDC_33T > 1 and
SDC_33U > 1 and
SDC_33V > 1 and
SDC_33W > 1
English only  
2 SDC_33A > 1 and
SDC_33B = 1 and
SDC_33C > 1 and
SDC_33D > 1 and
SDC_33E > 1 and
SDC_33F > 1 and
SDC_33G > 1 and
SDC_33H > 1 and
SDC_33I > 1 and
SDC_33J > 1 and
SDC_33K > 1 and
SDC_33L > 1 and
SDC_33M > 1 and
SDC_33N > 1 and
SDC_33O > 1 and
SDC_33P > 1 and
SDC_33Q > 1 and
SDC_33R > 1 and
SDC_33S > 1 and
SDC_33T > 1 and
SDC_33U > 1 and
SDC_33V > 1 and
SDC_33W > 1
French only  
3 (SDC_33A = 1 and
SDC_33B = 1) and
SDC_33C > 1 and
SDC_33D > 1 and
SDC_33E > 1 and
SDC_33F > 1 and
SDC_33G > 1 and
SDC_33H > 1 and
SDC_33I > 1 and
SDC_33J > 1 and
SDC_33K > 1 and
SDC_33L > 1 and
SDC_33M > 1 and
SDC_33N > 1 and
SDC_33O > 1 and
SDC_33P > 1 and
SDC_33Q > 1 and
SDC_33R > 1 and
SDC_33S > 1 and
SDC_33T > 1 and
SDC_33U > 1 and
SDC_33V > 1 and
SDC_33W > 1
English and French only  
4 (SDC_33A = 1 and
SDC_33B = 1) and
(SDC_33C = 1 or
SDC_33D = 1 or
SDC_33E = 1 or
SDC_33F = 1 or
SDC_33G = 1 or
SDC_33H = 1 or
SDC_33I = 1 or
SDC_33J = 1 or
SDC_33K = 1 or
SDC_33L = 1 or
SDC_33M = 1 or
SDC_33N = 1 or
SDC_33O = 1 or
SDC_33P = 1 or
SDC_33Q = 1 or
SDC_33R = 1 or
SDC_33S = 1 or
SDC_33T = 1 or
SDC_33U = 1 or
SDC_33V = 1 or
SDC_33W = 1)
English, French and Other  
5 (SDC_33A = 1 and
SDC_33B > 1) and
(SDC_33C = 1 or
SDC_33D = 1 or
SDC_33E = 1 or
SDC_33F = 1 or
SDC_33G = 1 or
SDC_33H = 1 or
SDC_33I = 1 or
SDC_33J = 1 or
SDC_33K = 1 or
SDC_33L = 1 or
SDC_33M = 1 or
SDC_33N = 1 or
SDC_33O = 1 or
SDC_33P = 1 or
SDC_33Q = 1 or
SDC_33R = 1 or
SDC_33S = 1 or
SDC_33T = 1 or
SDC_33U = 1 or
SDC_33V = 1 or
SDC_33W = 1)
English and Other (not French)  
6 (SDC_33A > 1 and
SDC_33B = 1) and
(SDC_33C = 1 or
SDC_33D = 1 or
SDC_33E = 1 or
SDC_33F = 1 or
SDC_33G = 1 or
SDC_33H = 1 or
SDC_33I = 1 or
SDC_33J = 1 or
SDC_33K = 1 or
SDC_33L = 1 or
SDC_33M = 1 or
SDC_33N = 1 or
SDC_33O = 1 or
SDC_33P = 1 or
SDC_33Q = 1 or
SDC_33R = 1 or
SDC_33S = 1 or
SDC_33T = 1 or
SDC_33U = 1 or
SDC_33V = 1 or
SDC_33W = 1)
French and Other (not English)  
7 (SDC_33A > 1 and
SDC_33B > 1) and
(SDC_33C = 1 or
SDC_33D = 1 or
SDC_33E = 1 or
SDC_33F = 1 or
SDC_33G = 1 or
SDC_33H = 1 or
SDC_33I = 1 or
SDC_33J = 1 or
SDC_33K = 1 or
SDC_33L = 1 or
SDC_33M = 1 or
SDC_33N = 1 or
SDC_33O = 1 or
SDC_33P = 1 or
SDC_33Q = 1 or
SDC_33R = 1 or
SDC_33S = 1 or
SDC_33T = 1 or
SDC_33U = 1 or
SDC_33V = 1 or
SDC_33W = 1)
Other (neither English nor French)  

4. SDCDLNG - Language(s) in whichrespondent can converse

Variable name:
SDCDLNG

Based on:
SDC_31A, SDC_31B, SDC_31C, SDC_31D, SDC_31E, SDC_31F, SDC_31G,SDC_31H, SDC_31I, SDC_31J, SDC_31K, SDC_31L, SDC_31M, SDC_31N,SDC_31O, SDC_31P, SDC_31Q, SDC_31R, SDC_31S, SDC_31T, SDC_31U,SDC_31V, SDC_31W

Description:
This variable indicates the language(s) in which the respondent canconverse.

Introduced in:
CCHS - Cycle 1.1

Table 4
SDCDLNG Specifications
Value Condition(s) Description Notes
99 (SDC_31A = DK, RF, NS) Required question was not answered (don't know, refusal, notstated) NS
1 SDC_31A = 1 and
SDC_31B > 1 and
SDC_31C > 1 and
SDC_31D >1 and
SDC_31E > 1 and
SDC_31F > 1 and
SDC_31G > 1 and
SDC_31H > 1 and
SDC_31I > 1 and
SDC_31J > 1 and
SDC_31K > 1 and
SDC_31L > 1 and
SDC_31M > 1 and
SDC_31N > 1 and
SDC_31O > 1 and
SDC_31P > 1 and
SDC_31Q > 1 and
SDC_31R > 1 and
SDC_31S > 1 and
SDC_31T > 1 and
SDC_31U > 1 and
SDC_31V > 1 and
SDC_31W > 1
English only  
2 SDC_31A > 1 and
SDC_31B = 1 and
SDC_31C > 1 and
SDC_31D > 1 and
SDC_31E > 1 and
SDC_31F > 1 and
SDC_31G > 1 and
SDC_31H > 1 and
SDC_31I > 1 and
SDC_31J > 1 and
SDC_31K > 1 and
SDC_31L > 1 and
SDC_31M > 1 and
SDC_31N > 1 and
SDC_31O > 1 and
SDC_31P > 1 and
SDC_31Q > 1 and
SDC_31R > 1 and
SDC_31S > 1 and
SDC_31T > 1 and
SDC_31U > 1 and
SDC_31V > 1 and
SDC_31W > 1
French only  
3 SDC_31A = 1 and
SDC_31B = 1  and
SDC_31C > 1 and
SDC_31D > 1 and
SDC_31E > 1 and
SDC_31F > 1 and
SDC_31G > 1 and
SDC_31H > 1 and
SDC_31I > 1 and
SDC_31J > 1 and
SDC_31K > 1 and
SDC_31L > 1 and
SDC_31M > 1 and
SDC_31N > 1 and
SDC_31O > 1 and
SDC_31P > 1 and
SDC_31Q > 1 and
SDC_31R > 1 and
SDC_31S > 1 and
SDC_31T > 1 and
SDC_31U > 1 and
SDC_31V > 1 and
SDC_31W > 1
English and French only  
4 (SDC_31A = 1 and
SDC_31B = 1) and
(SDC_31C = 1 or
SDC_31D = 1 or
SDC_31E = 1 or
SDC_31F = 1 or
SDC_31G = 1 or
SDC_31H = 1 or
SDC_31I = 1 or
SDC_31J = 1 or
SDC_31K = 1 or
SDC_31L = 1 or
SDC_31M = 1 or
SDC_31N = 1 or
SDC_31O = 1 or
SDC_31P = 1 or
SDC_31Q = 1 or
SDC_31R = 1 or
SDC_31S = 1 or
SDC_31T = 1 or
SDC_31U = 1 or
SDC_31V = 1 or
SDC_31W = 1)
English, French and Other  
5 (SDC_31A = 1 and
SDC_31B > 1) and
(SDC_31C = 1 or
SDC_31D = 1 or
SDC_31E = 1 or
SDC_31F = 1 or
SDC_31G = 1 or
SDC_31H = 1 or
SDC_31I = 1 or
SDC_31J = 1 or
SDC_31K = 1 or
SDC_31L = 1 or
SDC_31M = 1 or
SDC_31N = 1 or
SDC_31O = 1 or
SDC_31P = 1 or
SDC_31Q = 1 or
SDC_31R = 1 or
SDC_31S = 1 or
SDC_31T = 1 or
SDC_31U = 1 or
SDC_31V = 1 or
SDC_31W = 1)
English and Other (not French)  
6 (SDC_31A > 1 and
SDC_31B = 1) and
(SDC_31C = 1 or
SDC_31D = 1 or
SDC_31E = 1 or
SDC_31F = 1 or
SDC_31G = 1 or
SDC_31H = 1 or
SDC_31I = 1 or
SDC_31J = 1 or
SDC_31K = 1 or
SDC_31L = 1 or
SDC_31M = 1 or
SDC_31N = 1 or
SDC_31O = 1 or
SDC_31P = 1 or
SDC_31Q = 1 or
SDC_31R = 1 or
SDC_31S = 1 or
SDC_31T = 1 or
SDC_31U = 1 or
SDC_31V = 1 or
SDC_31W = 1)
French and Other (not English)  
7 (SDC_31A > 1 and
SDC_31B > 1) and
(SDC_31C = 1 or
SDC_31D = 1 or
SDC_31E = 1 or
SDC_31F = 1 or
SDC_31G = 1 or
SDC_31H = 1 or
SDC_31I = 1 or
SDC_31J = 1 or
SDC_31K = 1 or
SDC_31L = 1 or
SDC_31M = 1 or
SDC_31N = 1 or
SDC_31O = 1 or
SDC_31P = 1 or
SDC_31Q = 1 or
SDC_31R = 1 or
SDC_31S = 1 or
SDC_31T = 1 or
SDC_31U = 1 or
SDC_31V = 1 or
SDC_31W = 1)
Other (neither English nor French)  

5. SDCDRES - Length of time inCanada since immigration

Variable name:
SDCDRES

Based on:
SDC_13, C2_YEAR

Description:
This variable indicates the length of time the respondent has beenin Canada since his/her immigration.

Introduced in:
CCHS - Cycle 1.1

Note:
Non-immigrants were excluded from the population.

Table 5
SDCDRES Specifications
Value Condition(s) Description Notes
996 SDC_13 = NA Population exclusion NA
999 (SDC_13 = DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) NS
C2_YEAR -
SDC_13
SDC_13 < NA Length of time in Canada since immigration [min: 0; max: 130 (current age)]

6. SDCFABT - Aboriginal flag

Variable name:
SDCFABT

Based on:
SDC_22

Description:
This variable indicates whether the respondent reported being anaboriginal person.

Introduced in:
CCHS - Cycle 4.1

Table 6
SDCFABT Specifications
Value Condition(s) Description Notes
9 (SDC_22 = DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) NS
1 SDC_22 = 1 Aboriginal (North American Indian, Métis, Inuit)  
2 SDC_22 = 2 Not Aboriginal  

7. SDCFIMM - Immigration flag

Variable name:
SDCFIMM

Based on:
SDC_13

Description:
This variable indicates if the respondent is an immigrant.

Introduced in:
CCHS - Cycle 1.1

Table 7
SDCFIMM Specifications
Value Condition(s) Description Notes
9 (SDC_13 = DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) NS
1 SDC_13 < NA Immigrant  
2 SDC_13 = NA Not an immigrant  

8. SDCGCB - Country of birth –grouped

Variable name:
SDCGCB

Based on:
SDCCCB

Description:
This variable classifies the respondent based on his/her codedcountry of birth.

Introduced in:
CCHS - Cycle 1.1

Table 8
SDCGCB Specifications
Value Condition(s) Description Notes
99 (SDCCCB = 000, 995, DK, RF, NS) Required question was not answered (don’t know, refusal,not stated) NS
1 (0 < SDCCCB  < 14) Canada  
2 (100 <= SDCCCB < 200) or
SDCCCB = 206
Other North America  
3 (200 < SDCCCB < 206) or
(206 < SDCCCB < 500)
South, Central America and Caribbean  
4 (500 <= SDCCCB < 600) Europe  
5 (600 <= SDCCCB < 700) Africa  
6 (700 <= SDCCCB < 800) Asia  
7 (800 <= SDCCCB < 900) Oceania  

Strengths and difficulties (12DVs)

The SDQ is a brief behavioural screening questionnaire,developed for 3-16 year olds.  It consists of 25 items dividedamong 5 categories:

  1. Emotional Symptoms
  2. Conduct Problems
  3. Hyperactivity/Inattention
  4. Peer relationship problems
  5. Prosocial Behaviour

The scores can be used as continuous variables or classified asnormal, borderline or abnormal.

Table
Strengths and difficulties Temporary Reformat

SDQT11

Value Condition(s) Description Notes
0 (SDQ_11 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_11 = 2 Recode to SDQ scoring  
2 SDQ_11 = 3 Recode to SDQ scoring  

SDQT12

Value Condition(s) Description Notes
0 (SDQ_12 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_12 = 2 Recode to SDQ scoring  
2 SDQ_12 = 3 Recode to SDQ scoring  

SDQT13

Value Condition(s) Description Notes
0 (SDQ_13 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_13 = 2 Recode to SDQ scoring  
2 SDQ_13 = 3 Recode to SDQ scoring  

SDQT14

Value Condition(s) Description Notes
0 (SDQ_14 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_14 = 2 Recode to SDQ scoring  
2 SDQ_14 = 3 Recode to SDQ scoring  

SDQT15

Value Condition(s) Description Notes
0 (SDQ_15 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_15 = 2 Recode to SDQ scoring  
2 SDQ_15 = 3 Recode to SDQ scoring  

SDQT16

Value Condition(s) Description Notes
0 (SDQ_16 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_16 = 2 Recode to SDQ scoring  
2 SDQ_16 = 3 Recode to SDQ scoring  

SDQT17

Value Condition(s) Description Notes
0 (SDQ_17 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_17 = 2 Recode to SDQ scoring  
2 SDQ_17 = 3 Recode to SDQ scoring  

SDQT18

Value Condition(s) Description Notes
0 (SDQ_18 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_18 = 2 Recode to SDQ scoring  
2 SDQ_18 = 3 Recode to SDQ scoring  

SDQT19

Value Condition(s) Description Notes
0 (SDQ_19 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_19 = 2 Recode to SDQ scoring  
2 SDQ_19 = 3 Recode to SDQ scoring  

SDQT20

Value Condition(s) Description Notes
0 (SDQ_20 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_20 = 2 Recode to SDQ scoring  
2 SDQ_20 = 3 Recode to SDQ scoring  

SDQT21

Value Condition(s) Description Notes
0 (SDQ_21 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_21 = 2 Recode to SDQ scoring  
2 SDQ_21 = 3 Recode to SDQ scoring  

SDQT22

Value Condition(s) Description Notes
0 (SDQ_22 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_22 = 2 Recode to SDQ scoring  
2 SDQ_22 = 3 Recode to SDQ scoring  

SDQT23

Value Condition(s) Description Notes
0 (SDQ_23 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_23 = 2 Recode to SDQ scoring  
2 SDQ_23 = 3 Recode to SDQ scoring  

SDQT24

Value Condition(s) Description Notes
0 (SDQ_24 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_24 = 2 Recode to SDQ scoring  
2 SDQ_24 = 3 Recode to SDQ scoring  

SDQT25

Value Condition(s) Description Notes
0 (SDQ_25 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_25 = 2 Recode to SDQ scoring  
2 SDQ_25 = 3 Recode to SDQ scoring  

SDQT26

Value Condition(s) Description Notes
0 (SDQ_26 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_26 = 2 Recode to SDQ scoring  
2 SDQ_26 = 3 Recode to SDQ scoring  

SDQT27

Value Condition(s) Description Notes
0 (SDQ_27 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_27 = 2 Recode to SDQ scoring  
2 SDQ_27 = 3 Recode to SDQ scoring  

SDQT28

Value Condition(s) Description Notes
0 (SDQ_28 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_28 = 2 Recode to SDQ scoring  
2 SDQ_28 = 3 Recode to SDQ scoring  

SDQT29

Value Condition(s) Description Notes
0 (SDQ_29 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_29 = 2 Recode to SDQ scoring  
2 SDQ_29 = 3 Recode to SDQ scoring  

SDQT30

Value Condition(s) Description Notes
0 (SDQ_30 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_30 = 2 Recode to SDQ scoring  
2 SDQ_30 = 3 Recode to SDQ scoring  

SDQT31

Value Condition(s) Description Notes
0 (SDQ_31 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_31 = 2 Recode to SDQ scoring  
2 SDQ_31 = 3 Recode to SDQ scoring  

SDQT32

Value Condition(s) Description Notes
0 (SDQ_32 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_32 = 2 Recode to SDQ scoring  
2 SDQ_32 = 3 Recode to SDQ scoring  

SDQT33

Value Condition(s) Description Notes
0 (SDQ_33 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_33 = 2 Recode to SDQ scoring  
2 SDQ_33 = 3 Recode to SDQ scoring  

SDQT34

Value Condition(s) Description Notes
0 (SDQ_34 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_34 = 2 Recode to SDQ scoring  
2 SDQ_34 = 3 Recode to SDQ scoring  

SDQT35

Value Condition(s) Description Notes
0 (SDQ_35 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_35 = 2 Recode to SDQ scoring  
2 SDQ_35 = 3 Recode to SDQ scoring  

1. SDQDCON - Conduct Problems

Variable name:
SDQDCON

Based on:
DHH_AGE, SDQ_15, SDQ_17, SDQ_22, SDQ_28, SDQ_32

Description:
The Conduct Problems Scale forms part of the Strengths andDifficulties Questionnaire (SDQ), a brief behavioural screeningquestionnaire developed by Robert Goodman.  There are 5 itemswhich comprise the Conduct Problems portion of thequestionnaire.

Note:
The scale can be prorated if at least 3 items were completed. Thescore can be used as a continuous variable, or else classified asnormal, borderline, or abnormal (see SDQGCON).  Respondentsgreater than 17 years of age were excluded from the population.

Internet site:
www.sdqinfo.com

Table 1
SDQDCON Temporary Reformat

SDQT15C

Value Condition(s) Description Notes
1 SDQ_15 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT17C

Value Condition(s) Description Notes
1 SDQ_17 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT22C

Value Condition(s) Description Notes
1 SDQ_22 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT28C

Value Condition(s) Description Notes
1 SDQ_28 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT32C

Value Condition(s) Description Notes
1 SDQ_32 <> (DK, RF, NS) Counts the response Else set value to zero

TOCNTCON

Value Condition(s) Description Notes
SDQT15C +
SDQT17C +
SDQT22C +
SDQT28C +
SDQT32C
(SDQT15C +
SDQT17C +
SDQT22C +
SDQT28C +
SDQT32C) > = 3
Sums the total number of responses Else value = x

TOSUMCON

Value Condition(s) Description Notes
SDQT15 +
SDQT17 +
SDQT22 +
SDQT28 +
SDQT32
  Generates the total raw score (not pro-rated) on the ConductProblems Scale  

 

Table 1
SDQDCON Specifications
Value Condition(s) Description Notes
96 DHH_AGE > 17 Population exclusions NA
99 TOCNTCON = x At least one required question was not answered (don’tknow, refusal, not stated) NS
5 * TOSUMCON /
TOCNTCON
TOCNTCON <> x Conduct Problems Score  

 

2. SDQDEMO - EmotionalSymptoms

Variable name:
SDQDEMO

Based on:
DHH_AGE, SDQ_13, SDQ_18, SDQ_23, SDQ_26, SDQ_34

Description:
The Emotional Symptoms Scale forms part of the Strengths andDifficulties Questionnaire (SDQ), a brief behavioural screeningquestionnaire developed by Robert Goodman.  There are 5 itemswhich comprise the Emotional Symptoms portion of thequestionnaire.

Note:
The scale can be prorated if at least 3 items were completed. Thescore can be used as a continuous variable, or else classified asnormal, borderline, or abnormal (see SDQGEMO).  Respondentsgreater than 17 years of age were excluded from the population.

Internet site:
www.sdqinfo.com

Table 2
SDQDEMO Temporary Reformat

SDQT13C

Value Condition(s) Description Notes
1 SDQ_13 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT18C

Value Condition(s) Description Notes
1 SDQ_18 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT23C

Value Condition(s) Description Notes
1 SDQ_23 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT26C

Value Condition(s) Description Notes
1 SDQ_26 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT34C

Value Condition(s) Description Notes
1 SDQ_34 <> (DK, RF, NS) Counts the response Else set value to zero

TOCNTEMO

Value Condition(s) Description Notes
SDQT13C +
SDQT18C +
SDQT23C +
SDQT26C +
SDQT34C
(SDQT13C +
SDQT18C +
SDQT23C +
SDQT26C +
SDQT34C) > = 3
Sums the total number of responses Else value = x

TOSUMEMO

Value Condition(s) Description Notes
SDQT13 +
SDQT18 +
SDQT23 +
SDQT26 +
SDQT34
  Generates the total raw score (not pro-rated) on the EmotionalSymptoms Scale  

 

Table 2
SDQDEMO Specifications
Value Condition(s) Description Notes
96 DHH_AGE > 17 Population exclusions NA
99 TOCNTEMO = x At least one required question was not answered (don’tknow, refusal, not stated) NS
5 * TOSUMEMO /
TOCNTEMO
TOCNTEMO <> x Emotional Symptoms Score  

 

3. SDQDHYP -Hyperactivity/Inattention

Variable name:
SDQDHYP

Based on:
DHH_AGE, SDQ_12, SDQ_20, SDQ_25, SDQ_31, SDQ_35

Description:
The Hyperactivity/InattentionScale forms part of the Strengths and Difficulties Questionnaire(SDQ), a brief behavioural screening questionnaire developed byRobert Goodman.  There are 5 items which comprise theHyperactivity/Inattention portion of the questionnaire.

Note:
The scale can be prorated if at least 3 items were completed. Thescore can be used as a continuous variable, or else classified asnormal, borderline, or abnormal (see SDQGHYP).  Respondentsgreater than 17 years of age were excluded from the population.

Internet site:
www.sdqinfo.com

Table 3
SDQDHYPTemporary Reformat

SDQT12C

Value Condition(s) Description Notes
1 SDQ_12 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT20C

Value Condition(s) Description Notes
1 SDQ_20 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT25C

Value Condition(s) Description Notes
1 SDQ_25 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT31C

Value Condition(s) Description Notes
1 SDQ_31 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT35C

Value Condition(s) Description Notes
1 SDQ_35 <> (DK, RF, NS) Counts the response Else set value to zero

TOCNTHYP

Value Condition(s) Description Notes
SDQT12C +
SDQT20C +
SDQT25C +
SDQT31C +
SDQT35C
(SDQT12C +
SDQT20C +
SDQT25C +
SDQT31C +
SDQT35C) >= 3
Sums the total number of responses Else value = x

TOSUMHYP

Value Condition(s) Description Notes
SDQT12 +
SDQT20 +
SDQT25 +
SDQT31 +
SDQT35
  Generates the total raw score (not pro-rated) on theHyperactivity/Inattention Scale  

 

Table 3
SDQDHYP Specifications
Value Condition(s) Description Notes
96 DHH_AGE > 17 Population exclusions NA
99 TOCNTHYP = x At least one required question was not answered (don’tknow, refusal, not stated) NS
5 * TOSUMHYP /
TOCNTHYP
TOCNTHYP <> x Hyperactivity/Inattention Score  

 

4. SDQDPRO - ProsocialBehaviour

Variable name:
SDQDPRO

Based on:
DHH_AGE, SDQ_11, SDQ_14, SDQ_19, SDQ_27, SDQ_30

Description:
The Prosocial Behaviour Scale forms part of the Strengths andDifficulties Questionnaire (SDQ), a brief behavioural screeningquestionnaire developed by Robert Goodman.  There are 5 itemswhich comprise the Prosocial Behaviour portion of thequestionnaire.  The prosocial behaviour score is the onlyscore which does not comprise part of the Total DifficultiesScore.

Note:
The scale can be prorated if at least 3 items were completed. Thescore can be used as a continuous variable, or else classified asnormal, borderline, or abnormal (see SDQGPRO).  Respondentsgreater than 17 years of age were excluded from the population.

Table 4
SDQDPRO Temporary Reformat

SDQT11C

Value Condition(s) Description Notes
1 SDQ_11 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT14C

Value Condition(s) Description Notes
1 SDQ_14 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT19C

Value Condition(s) Description Notes
1 SDQ_19 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT27C

Value Condition(s) Description Notes
1 SDQ_27 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT30C

Value Condition(s) Description Notes
1 SDQ_30 <> (DK, RF, NS) Counts the response Else set value to zero

TOCNTPRO

Value Condition(s) Description Notes
SDQT11C +
SDQT14C +
SDQT19C +
SDQT27C +
SDQT30C
(SDQT11C +
SDQT14C +
SDQT19C +
SDQT27C +
(SDQT30C) >= 3
Sums the total number of responses Else value = x

TOSUMPRO

Value Condition(s) Description Notes
SDQT11 +
SDQT14 +
SDQT19 +
SDQT27 +
SDQT30
  Generates the total raw score (not pro-rated) on the ProsocialBehaviour Scale  

 

Table 4
SDQDPRO Specifications
Value Condition(s) Description Notes
96 DHH_AGE > 17 Population exclusions NA
99 TOCNTPRO = x At least one required question was not answered (don’tknow, refusal, not stated) NS
5 * TOSUMPRO /
TOCNTPRO
TOCNTPRO <> x Prosocial Behaviour Score  

 

5. SDQDPRP - Peer RelationshipProblems

Variable name:
SDQDPRP

Based on:
DHH_AGE, SDQ_16, SDQ_21, SDQ_24, SDQ_29, SDQ_33

Description:
The Peer Relationship Problems Scale forms part of the Strengthsand Difficulties Questionnaire (SDQ), a brief behavioural screeningquestionnaire developed by Robert Goodman.  There are 5 itemswhich comprise the Peer Relationship Problems portion of thequestionnaire.

Note:
The scale can be prorated if at least 3 items were completed. Thescore can be used as a continuous variable, or else classified asnormal, borderline, or abnormal (see SDQGPRP).  Respondentsgreater than 17 years of age were excluded from the population.

Table 5
SDQDPRP Temporary Reformat

SDQT16C

Value Condition(s) Description Notes
1 SDQ_16 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT21C

Value Condition(s) Description Notes
1 SDQ_21 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT24C

Value Condition(s) Description Notes
1 SDQ_24 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT29C

Value Condition(s) Description Notes
1 SDQ_29 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT33C

Value Condition(s) Description Notes
1 SDQ_33 <> (DK, RF, NS) Counts the response Else set value to zero

TOCNTPRP

Value Condition(s) Description Notes
SDQT16C +
SDQT21C +
SDQT24C +
SDQT29C +
SDQT33C
(SDQT16C +
SDQT21C +
SDQT24C +
SDQT29C +
(SDQT33C) >= 3
Sums the total number of responses Else value = x

TOSUMPRP

Value Condition(s) Description Notes
SDQT16 +
SDQT21 +
SDQT24 +
SDQT29 +
SDQT33
  Generates the total raw score (not pro-rated) on the PeerRelationship Problems Scale  

 

Table 5
SDQDPRP Specifications
Value Condition(s) Description Notes
96 DHH_AGE > 17 Population exclusions NA
99 TOCNTPRP = x At least one required question was not answered (don’tknow, refusal, not stated) NS
5 * TOSUMPRP /
TOCNTPRP
TOCNTPRP <> x Peer Relationship Problems Score  

 

6. SDQDTOT - Total DifficultiesScore

Variable name:
SDQDTOT

Based on:
DHH_AGE, SDQDEMO, SDQDCON, SDQDHYP, SDQDPRP

Description:
The Total Difficulties Score is generated by summing the scoresfrom all the scales except the Prosocial Behaviour Scale.  Theresultant score can range from 0 to 40 (and is counted as missingif one of the component scores is missing).

Note:
The score can be used as a continuous variable, or else classifiedas normal, borderline, or abnormal (see SDQGTOT).  Respondentsgreater than 17 years of age were excluded from the population.

Table 6
SDQDTOT Specifications
Value Condition(s) Description Notes
96 DHH_AGE > 17 Population exclusions NA
99 SDQDEMO = 99 or
SDQDCON = 99 or
SDQDHYP = 99 or
SDQDPRP = 99
At least one required question was not answered (don’tknow, refusal, not stated) NS
SDQDEMO +
SDQDCON +
SDQDHYP +
SDQDPRP
Else Total Difficulties Score min: 0; max: 40

7. SDQGCON - Conduct Problems Score– Grouped

Variable name:
SDQGCON

Based on:
DHH_AGE, SDQDCON

Description:
Although SDQ scores can be used as continuous variables (seeSDQDCON), they are also sometimes classified as "normal","borderline", and "abnormal". 

Note:
Respondents greater than 17 years of age were excluded from thepopulation.

Internet site:
www.sdqinfo.com

Table 7
SDQGCON Specifications
Value Condition(s) Description Notes
6 DHH_AGE > 17 Population exclusions NA
9 SDQDCON = 99 At least one required question was not answered (don’tknow, refusal, not stated) NS
1 0 < = SDQDCON < 3 Normal  
2 SDQDCON = 3 Borderline  
3 3 < SDQDCON < 11 Abnormal  

8. SDQGEMO - Emotional Symptoms Score– Grouped

Variable name:
SDQGEMO

Based on:
DHH_AGE, SDQDEMO

Description:
Although SDQ scores can be used as continuous variables (seeSDQDEMO), they are also sometimes classified as "normal","borderline", and "abnormal".

Note:
Respondents greater than 17 years of age were excluded from thepopulation.

Internet site:
www.sdqinfo.com

Table 8
SDQGEMO Specifications
Value Condition(s) Description Notes
6 DHH_AGE > 17 Population exclusions NA
9 SDQDEMO = 99 At least one required question was not answered (don’tknow, refusal, not stated) NS
1 0 < = SDQDEMO < 4 Normal  
2 SDQDEMO = 4 Borderline  
3 4 < SDQDEMO < 11 Abnormal  

9. SDQGHYP - Hyperactivity Score– Grouped

Variable name:
SDQGHYP

Based on:
DHH_AGE, SDQDHYP

Description:
Although SDQ scores can be used as continuous variables (seeSDQDHYP), they are also sometimes classified as "normal","borderline", and "abnormal".

Note:
Respondents greater than 17 years of age were excluded from thepopulation.

Internet site:
www.sdqinfo.com

Table 9
SDQGHYP Specifications
Value Condition(s) Description Notes
6 DHH_AGE > 17 Population exclusions NA
9 SDQDHYP = 99 At least one required question was not answered (don’tknow, refusal, not stated) NS
1 0 < = SDQDHYP < 6 Normal  
2 SDQDHYP = 6 Borderline  
3 6 < SDQDHYP < 11 Abnormal  

10. SDQGPRO - Prosocial BehaviourScore – Grouped

Variable name:
SDQGPRO

Based on:
DHH_AGE, SDQDPRO

Description:
Although SDQ scores can be used as continuous variables (seeSDQDPRO), they are also sometimes classified as "normal","borderline", and "abnormal".

Note:
Respondents greater than 17 years of age were excluded from thepopulation.

Internet site:
www.sdqinfo.com

Table 10
SDQGPRO Specifications
Value Condition(s) Description Notes
6 DHH_AGE > 17 Population exclusions NA
9 SDQDPRO =99 At least one required question was not answered (don’tknow, refusal, not stated) NS
1 5 < SDQDPRO < 11 Normal  
2 SDQDPRO = 5 Borderline  
3 0 <= SDQDPRO < 5 Abnormal  

11. SDQGPRP - Peer RelationshipProblems Score – Grouped

Variable name:
SDQGPRP

Based on:
DHH_AGE, SDQDPRP

Description:
Although SDQ scores can be used as continuous variables (seeSDQDPRP), they are also sometimes classified as "normal","borderline", and "abnormal".

Note:
Respondents greater than 17 years of age were excluded from thepopulation.

Internet site:
www.sdqinfo.com

Table 11
SDQGPRP Specifications
Value Condition(s) Description Notes
6 DHH_AGE > 17 Population exclusions NA
9 SDQDPRP = 99 At least one required question was not answered (don’tknow, refusal, not stated) NS
1 0 < = SDQDPRP < 3 Normal  
2 SDQDPRP = 3 Borderline  
3 3 > SDQDPRP > 11 Abnormal  

12. SDQGTOT - Total Difficulties Score– Grouped

Variable name:
SDQGTOT

Based on:
DHH_AGE, SDQTOT

Description:
Although SDQ scores can be used as continuous variables (seeSDQDTOT), they are also sometimes classified as "normal","borderline", and "abnormal".

Note:
Respondents greater than 17 years of age were excluded from thepopulation.

Internet site:
www.sdqinfo.com

Table 12
SDQGTOT Specifications
Value Condition(s) Description Notes
6 DHH_AGE > 17 Population exclusions NA
9 SDQDTOT = 99 At least one required question was not answered (don’tknow, refusal, not stated) NS
1 0 < = SDQDTOT < 14 Normal  
2 13 < SDQDTOT < 17 Borderline  
3 16 < SDQDTOT <= 40 Abnormal  

Smoking (3 DVs)

1. SMKDSTP - Number of Years SinceStopping Smoking Completely

Variable name:
SMKDSTP

Based on:
DHH_AGE, SMK_11, SMK_12, SMK_22, SMK_51, SMK_54, SMKDSTY

Description:
This variable indicates the approximate number of years sinceformer daily smokers completely quit smoking.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents less than 12 years of age,current smokers and respondents who did not smoke a total of 100cigarettes or more in their lifetime were excluded from thepopulation.

Table 1
SMKDSTP Specifications
Value Condition(s) Description Notes
996 DHH_AGE < 12 or
(SMKDSTY = 1, 2, 3, 6) or
(SMK_12 = 3 and
SMK_11 = 2) or
SMK_22 = 0 or
SMK_51 = 2
Population exclusions NA
999 SMKDSTY = NS or
(SMK_22 = DK, RF, NS) or
(SMK_51 = DK, RF, NS) or
(SMK_54 = DK, RF, NS) or
(DHH_AGE = DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NS
DHH_AGE –
SMK_54
SMK_11 = 1 and
SMK_12 = 3 and
SMK_51 = 1
Number of years since completely quit smoking  

2. SMKDSTY - Type of Smoker

Variable name:
SMKDSTY

Based on:
DHH_AGE, SMK_11, SMK_12, SMK_22, SMK_51

Description:
This variable indicates the type of smoker the respondent is, basedon his/her smoking habits.

Note:
Respondents less than 12 years of age were excluded from thepopulation.

Introduced in:
CCHS - Cycle 1.1

Table 2
SMKDSTY Specifications
Value Condition(s) Description Notes
96 DHH_AGE < 12 Population exclusions NA
99 (SMK_11 = DK, RF, NS) or
(SMK_12 = DK, RF, NS) or
(SMK_22 = DK, RF, NS) or
(SMK_51 = DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NS
1 SMK_12 = 1 Current Daily smoker  
2 SMK_12 = 2 and
SMK_51 = 1
Occasional smoker (former daily smoker)  
3 SMK_12 = 2 and
(SMK_51 = 2, NA)
Occasional smoker (never a daily smoker or has smoked less than100 cigarettes lifetime)  
4 SMK_12 = 3 and
SMK_51 = 1
Non-smoker (former daily smoker)  
5 SMK_12 = 3 and
(SMK_51 = 2 or
SMK_22 = 0) and
SMK_11 = 1
Non-smoker (former occasional smoker, at least 100 cigarettesin lifetime)  
6 SMK_12 = 3 and
SMK_11 = 2
Never smoked (at least 100 cigarettes)  

3. SMKDYFS - Number of Years SmokedDaily (Former Daily Smokers Only)

Variable name:
SMKDYFS

Based on:
DHH_AGE, SMK_52, SMK_54

Description:
This variable indicates the number of years the respondent smokeddaily.

Note:
Respondents less than 12 years of age, respondents who are dailysmokers, respondents who have never been daily smokers or who neversmoked at least 1 cigarette per month or respondents who have notsmoked a total of 100 cigarettes in their lifetime have beenexcluded from the population.

Table 3
SMKDYFS Specifications
Value Condition(s) Description Notes
996 DHH_AGE < 12 or
SMK_12 =1 or
(SMK_51 = 2 or
SMK_22 = 0) or 
SMK_11=2
Population exclusion NA
999 (SMK_12 = DK, RF, NS) or
(SMK_52 = DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NS
SMK_54 –
SMK_52
(SMK_12 = 2,3) and
SMK_51 = 1)
Number of years smoking daily (min: 0;  max: 125)

Spirometry (4 DVs)

1. SPCDELG - Eligibility -Spirometry component

Variable name:
SPCDELG

Based on:
PHC_12, PHC_42F, MHR_611A, ORS_2

Description:
This variable indicates whether the respondent was eligible for theSpirometry component. As there are multiple reasons to be screenedout of this measure, the prevalence of screen outs by reason shouldnot be based on frequency counts for this variable.

Note:
Created in the Clinic Post-Verify process.

Table 1
SPCDELG Specifications
Value Condition(s) Description Notes
7 (27 < PHC_12 < NA) Not eligible - more than 27 weeks pregnant  
9 PHC_42F = 1 Not eligible - acute or chronic condition  
12 MHR_611A = 1 Not eligible - medication use  
14 ORS_2 = 1 Not eligible - other reason  
1 Else Eligible  

2. SPMDB1FP - Percent predictedFEV1/FVC

Variable name:
SPMDB1FP

Based on:
SPM_B1F, SPM_PV1F

Description:
This variable indicates the forced expiratory volume in one second(FEV1.0)  as a fraction of the forced vital capacity (FVC)expressed as a percentage of the predicted value. The predictedvalue is a reference value (in litres) obtained from a well-definedpopulation of subjects with traits similar to the person beingtested.

Note:
Created in the Clinic data collection application.
The predicted reference value for respondents aged 6-7 years wasCorey 1976. An ethnic correction of 10% was applied for the blackand Asian ethnic groups.
The predicted reference value for respondents aged 8 - 79 years wasHankinson (NHANES III). An ethnic correction of 10% was applied forthe Asian ethnic group.
Hankinson, J.L., Odencrantz, J.R. and Fedan, K.B. 1999. SpirometricReference Values from a Sample of the General U.S.Population.  American Journal of Respiratory and Critical CareMedicine. 159:179-187
Corey M.L., Levison H., Crozier D. 1976. Five- to seven-year courseof pulmonary function in cystic fibrosis.  American Review ofRespiratory Disease. 111; 1085-1092.Created in the ClinicPost-Verify process.

Table 2
SPMDB1FP Specifications
Value Condition(s) Description Notes

999.6

SPM_B1F = NA or SPM_PV1F = NA

Population exclusions

NA
999.9 SPM_B1F > NA or SPM_PV1F > NA At least one required question was not answered (don't know, refusal, not stated) NS
Round((SPM_B1F/SPM_PV1F * 100), .1) Else Percent predicted FEV1/FVC  

3. SPMDB1P - Percent predicted ForcedExpiratory Volume (FEV1)

Variable name:
SPMDB1P

Based on:
SPM_B1, SPM_PV1

Description:
This variable indicates the total volume of air that can beforcibly blown out in the first second of a forced vital capacitymanoeuvre (forced expiratory volume in one second), measured inlitres and expressed as a percentage of the predicted value. Thepredicted value is a reference value (in litres) obtained from awell-defined population of subjects with traits similar to theperson being tested.

Note:
Created in the Clinic data collection application.
The predicted reference value for respondents aged 6-7 years wasCorey 1976. An ethnic correction of 10% was applied for the blackand Asian ethnic groups.
The predicted reference value for respondents aged 8 - 79 years wasHankinson (NHANES III). An ethnic correction of 10% was applied forthe Asian ethnic group.
Hankinson, J.L., Odencrantz, J.R. and Fedan, K.B. 1999. SpirometricReference Values from a Sample of the General U.S.Population.  American Journal of Respiratory and Critical CareMedicine. 159:179-187
Corey M.L., Levison H., Crozier D. 1976. Five- to seven-year courseof pulmonary function in cystic fibrosis.  American Review ofRespiratory Disease. 111; 1085-1092.Created in the ClinicPost-Verify process.

Table 3
SPMDB1P Specifications
Value Condition(s) Description Notes
999.6 SPM_B1 = NA or
SPM_PV1 = NA
Popuolation exclusions NA
999.9 SPM_B1 > NA or SPM_PV1 > NA At least one required question was not answered (don't know, refusal, not stated) NS
Round((SPM_104 / SPM_052 * 100), .1) Else Percent predicted FEV1  

4. SPMDBFVP - Percent predicted ForcedVital Capacity (FVC)

Variable name:
SPMDBFVP

Based on:
SPM_BFVC, SPM_PFVC

Description:
This variable indicates the total volume of air that can beforcibly blown out after full inspiration (forced vital capacity),measured in litres and expressed as a percentage of the predictedvalue. The predicted value is a reference value (in litres)obtained from a well-defined population of subjects with traitssimilar to the person being tested.

Note:
Created in the Clinic data collection application.
The predicted reference value for respondents aged 6-7 years wasCorey 1976. An ethnic correction of 10% was applied for the blackand Asian ethnic groups.
The predicted reference value for respondents aged 8 - 79 years wasHankinson (NHANES III). An ethnic correction of 10% was applied forthe Asian ethnic group.
Hankinson, J.L., Odencrantz, J.R. and Fedan, K.B. 1999. SpirometricReference Values from a Sample of the General U.S.Population.  American Journal of Respiratory and Critical CareMedicine. 159:179-187
Corey M.L., Levison H., Crozier D. 1976. Five- to seven-year courseof pulmonary function in cystic fibrosis.  American Review ofRespiratory Disease. 111; 1085-1092

Table 4
SPMDBFVP Specifications
Value Condition(s) Description Notes
999.6 SPM_BFVC = NA or SPM_PFVC = NA Population exclusions NA
999.9 SPM_BFVC = NA or SPM_PFVC = NA At least one required question was not answered (don't know, refusal, not stated) NS
Round((SPM_BFVC / SPM_PFVC * 100), .1) Else Percent predicted FVC  

Sit and Reach (4 DVs)

1. SRCDELG - Eligibility - Sit andReach component

Variable name:
SRCDELG

Based on:
CLC_AGE, V2_TYPE, ATG_33C, PHC_12, PHC_42I, MHR_611D, PAR_5A3C,PAR_5B3C, PAR_5C3C, PAR_5D3C, PAR_5E3C, PAR_5F3C, PAR_5G3C,PAR_5H3C, PAR_5I3C, PAR_5J3C, PAR_5K3C, PAR_72C, ORS_4

Description:
This variable indicates whether the respondent was eligible for theSit and Reach component. As there are multiple reasons to bescreened out of this measure, the prevalence of screen outs byreason should not be based on frequency counts for thisvariable.

Note:
Created in the Clinic Post-Verify process.

Table 1
SRCDELG Specifications
Value Condition(s) Description Notes
2 V2_TYPE = 2 Not eligible - home visit  
3 CLC_AGE > 69 Not eligible - age  
5 ATG_33C = 1 Not eligible - drank alcohol too close to visit time  
6 (12 < PHC_12 < NA) Not eligible - more than 12 weeks pregnant  
9 PHC_42I = 1 Not eligible - acute or chronic condition  
12 MHR_611D = 1 Not eligible - medication use  
13 PAR_5A3C = 1 or
PAR_5B3C = 1 or
PAR_5C3C = 1 or
PAR_5D3C = 1 or
PAR_5E3C = 1 or
PAR_5F3C = 1 or
PAR_5G3C = 1 or
PAR_5H3C = 1 or
PAR_5I3C = 1 or
PAR_5J3C = 1 or
PAR_5K3C = 1 or
PAR_72C = 1
Not eligible - PAR-Q answer  
14 ORS_4 = 1 Not eligible - other reason  
1 Else Eligible  

2. SRMD11 - Sit and reachmeasure

Variable name:
SRMD11

Based on:
SRM_01, SRM_02

Description:
This variable indicates which of the two Sit and Reach Measurementswill be used in subsequent Derived Variables.

Note:
Created in the Clinic data collection application. 

Table 2
SRMD11 Specifications
Value Condition(s) Description Notes
99.9 (SRM_01 = DK, RF, NS) and
(SRM_02 = DK, RF, NS)
At least one required question was not answered (don’tknow, refusal, not stated) NS
99.6 (1 < SRCDELG < NA) Population exclusions NA
SRMD11 = SRM_01 ((0 =< SRM_01 < 99.6) and
(0 =< SRM_02 < 99.6) and
(SRM_01 > SRM_02)) or
((0 =< SRM_01 < 99.6) and
(SRM_02 => 99.6))
SRMD11 is equal to the first Sit and Reach measurement.  
SRMD11 = SRM_02 ((0 =< SRM_01 < 99.6) and
(0 =< SRM_02 < 99.6) and
(SRM_01 <= SRM_02)) or
((SRM_01 => 99.6) and
(0 < SRM_02 < 99.6))
SRMD11 is equal to the second Sit and Reach measurement.  

3. SRMD12 - Sit and reach norms -respondents 15 – 69

Variable name:
SRMD12

Based on:
CLC_AGE, CLC_SEX, SRMD11

Description:
This variable indicates the flexibility norms for respondents aged15 to 69.

Note:
Created in the Clinic data collection application.  Thisvariable categorizes the respondent's sit and reach score into oneof five categories: needs improvement, fair, good, very good orexcellent.

Source:
The Canadian Physical Activity, Fitness and Lifestyle Approach: 3rdEdition, 2003 by the Canadian Society for Exercise Physiology(CSEP)

Table 3
SRMD12 Specifications
Value Condition(s) Description Notes
6 CLC_AGE < 15 or
CLC_AGE > 69 or
SRMD11 = NA
Population exclusions NA
9 SRMD11 = NS At least one required question was not answered (don’tknow, refusal, not stated) NS
0 (CLC_SEX = 1 and
(((14 < CLC_AGE < 20) and
(0 < SRMD11 < 23.5)) or
((19 < CLC_AGE < 30) and
(0 < SRMD11 < 24.5)) or
((29 < CLC_AGE < 40) and
(0 < SRMD11 < 22.5)) or
((39 < CLC_AGE < 50) and
(0 < SRMD11 < 17.5)) or
((49 < CLC_AGE < 60) and
(0 < SRMD11 < 15.5)) or
((59 < CLC_AGE < 70) and
(0 < SRMD11 < 14.5)))) or
(CLC_SEX = 2 and 
(((14 < CLC_AGE < 20) and
(0 < SRMD11 < 28.5)) or
((19 < CLC_AGE < 30) and
(0 < SRMD11 < 27.5)) or
((29 < CLC_AGE < 40) and
(0 < SRMD11 < 26.5)) or
((39 < CLC_AGE < 50) and
(0 < SRMD11 < 24.5)) or
((49 < CLC_AGE < 60) and
(0 < SRMD11 < 24.5)) or
((59 < CLC_AGE < 70) and
(0 < SRMD11 < 22.5))))
Needs Improvement  
1 (CLC_SEX = 1 and
(((14 < CLC_AGE < 20) and
(23.4 < SRMD11 < 28.5)) or
((19 < CLC_AGE < 30) and
(24.4 < SRMD11 < 29.5)) or
((29 < CLC_AGE < 40) and
(22.4 < SRMD11 < 27.5)) or
((39 < CLC_AGE < 50) and
(17.4 < SRMD11 < 23.5)) or
((49 < CLC_AGE < 60) and
(15.4 < SRMD11 < 23.5)) or
((59 < CLC_AGE < 70) and
(14.4 < SRMD11 < 19.5)))) or
(CLC_SEX = 2 and
(((14 < CLC_AGE < 20) and
(28.4 < SRMD11 < 33.5)) or
((19 < CLC_AGE < 30) and
(27.4 < SRMD11 < 32.5)) or
((29 < CLC_AGE < 40) and
(26.4 < SRMD11 < 31.5)) or
((39 < CLC_AGE < 50) and
(24.4 < SRMD11 < 29.5)) or
((49 < CLC_AGE < 60) and
(24.4 < SRMD11 < 29.5)) or
((59 < CLC_AGE < 70) and
(22.4 < SRMD11 < 26.5))))
Fair  
2 (CLC_SEX = 1 and
(((14 < CLC_AGE < 20) and
(28.4 < SRMD11 < 33.5)) or
((19 < CLC_AGE < 30) and
(29.4 < SRMD11 < 33.5)) or
((29 < CLC_AGE < 40) and
(27.4 < SRMD11 < 32.5)) or
((39 < CLC_AGE < 50) and
(23.4 < SRMD11 < 28.5)) or
((49 < CLC_AGE < 60) and
(23.4 < SRMD11 < 27.5)) or
((59 < CLC_AGE < 70) and
(19.4 < SRMD11 < 24.5)))) or
(CLC_SEX = 2 and
(((14 < CLC_AGE < 20) and
(33.4 < SRMD11 < 37.5)) or
((19 < CLC_AGE < 30) and
(32.4 < SRMD11 < 36.5)) or
((29 < CLC_AGE < 40) and
(31.4 < SRMD11 < 35.5)) or
((39 < CLC_AGE < 50) and
(29.4 < SRMD11 < 33.5)) or
((49 < CLC_AGE < 60) and
(29.4 < SRMD11 < 32.5)) or
((59 < CLC_AGE < 70) and
(26.4 < SRMD11 < 30.5))))
Good  
3 (CLC_SEX = 1 and
(((14 < CLC_AGE < 20) and
(33.4 < SRMD11 < 38.5)) or
((19 < CLC_AGE < 30) and
(33.4 < SRMD11 < 39.5)) or
((29 < CLC_AGE < 40) and
(32.4 < SRMD11 < 37.5)) or
((39 < CLC_AGE < 50) and
(28.4 < SRMD11 < 34.5)) or
((49 < CLC_AGE < 60) and
(27.4 < SRMD11 < 34.5)) or
((59 < CLC_AGE < 70) and
(24.4 < SRMD11 < 32.5)))) or
(CLC_SEX = 2 and
(((14 < CLC_AGE < 20) and
(37.4 < SRMD11 < 42.5)) or
((19 < CLC_AGE < 30) and
(36.4 < SRMD11 < 40.5)) or
((29 < CLC_AGE < 40) and
(35.4 < SRMD11 < 40.5)) or
((39 < CLC_AGE < 50) and
(33.4 < SRMD11 < 37.5)) or
((49 < CLC_AGE < 60) and
(32.4 < SRMD11 < 38.5)) or
(59 < CLC_AGE < 70) and
(30.4 < SRMD11 < 34.5))))
Very good  
4 (CLC_SEX = 1 and
(((14 < CLC_AGE < 20) and
(38.4 < SRMD11 < 99.6)) or
((19 < CLC_AGE < 30) and
(39.4 < SRMD11 < 99.6)) or
((29 < CLC_AGE < 40) and
(37.4 < SRMD11 < 99.6)) or
((39 < CLC_AGE < 50) and
(34.4 < SRMD11 < 99.6)) or
((49 < CLC_AGE < 60) and
(34.4 < SRMD11 < 99.6)) or
((59 < CLC_AGE < 70) and
(32.4 < SRMD11 < 99.6)))) or
(CLC_SEX = 2 and
(((14 < CLC_AGE < 20) and
(42.4 < SRMD11 < 99.6)) or
((19 < CLC_AGE < 30) and
(40.4 < SRMD11 < 99.6)) or
((29 < CLC_AGE < 40) and
(40.4 < SRMD11 < 99.6)) or
((39 < CLC_AGE < 50) and
(37.4 < SRMD11 < 99.6)) or
((49 < CLC_AGE < 60) and
(38.4 < SRMD11 < 99.6)) or
((59 < CLC_AGE < 70) and
(34.4 < SRMD11 < 99.6))))
Excellent  

4. SRMD13 - Sit and reach norms -respondents less than 15

Variable name:
SRMD13

Based on:
CLC_AGE, CLC_SEX, SRMD11

Description:
This variable indicates the flexibility norms for respondents aged7 to 14.

Note:
Created in the Clinic data collection application.  Thisvariable categorizes the respondent's sit and reach score into oneof three categories: below average, average or above average.

Source:
Stephens, T. & C.L. Craig. 1985. Fitness and activitymeasurement in the 1981 Canada Fitness Survey. In: Drury, T. (ed.).1989. Assessing physical fitness and activity patterns in generalpopulation surveys. Department of Health and Human Services, PublicHealth Service, Center for Disease Control, National Center forHealth Statistics. Hyattsville, MD. pub. No. (PHS) 89-1253.

Table 4
SRMD13 Specifications
Value Condition(s) Description Notes
6 CLC_AGE > 14 or
SRMD11 = NA
Population exclusions NA
9 SRMD11 = NS At least one required question was not answered (don’tknow, refusal, not stated) NS
1 (CLC_SEX = 1 and
(((6 < CLC_AGE < 10) and
(0 < = SRMD11 < 25.5)) or
((9 < CLC_AGE < 13) and
(0 < = SRMD11 < 25.5)) or
((12 < CLC_AGE < 15) and
(0 < = SRMD11 < 24.5)))) or
(CLC_SEX = 2 and
(((6 < CLC_AGE < 10) and
(0 < = SRMD11 < 30.5)) or
((9 < CLC_AGE < 13) and
(0 < = SRMD11 < 29.5)) or
((12 < CLC_AGE < 15) and
(0 < = SRMD11 < 31.5))))
Below average  
2 (CLC_SEX = 1 and
(((6 < CLC_AGE < 10) and
(25.4 < SRMD11 < 30.5)) or
((9 < CLC_AGE < 13) and
(25.4 < SRMD11 < 29.5)) or
((12 < CLC_AGE < 15) and
(24.4 < SRMD11 < 29.5)))) or
(CLC_SEX = 2 and
(((6 < CLC_AGE < 10) and
(30.4 < SRMD11 < 34.5)) or
((9 < CLC_AGE < 13) and
(29.4 < SRMD11 < 34.5)) or
((12 < CLC_AGE < 15) and
(31.4 < SRMD11 < 35.5))))
Average  
3 (CLC_SEX = 1 and
(((6 < CLC_AGE < 10) and
(30.4 < SRMD11 < 99.6)) or
((9 < CLC_AGE < 13) and
(29.4 < SRMD11 < 99.6)) or
((12 < CLC_AGE < 15) and
(29.4 < SRMD11 < 99.6)))) or
(CLC_SEX = 2 and
((6 < CLC_AGE < 10) and
(34.4 < SRMD11 < 99.6)) or
((9 < CLC_AGE < 13) and
(34.4 < SRMD11 < 99.6)) or
((12 < CLC_AGE < 15) and
(35.4 < SRMD11 < 99.6))))
Above average  
4 CLC_AGE = 6 No norm available  

Urine Collection (1 DV)

Variable name:
1. URCDELG - Eligibility - UrineCollection component

Based on:
PHC_42B

Description:
This variable indicates whether the respondent was eligible for theUrine Collection component. As there are multiple reasons to bescreened out of this measure, the prevalence of screen outs byreason should not be based on frequency counts for thisvariable.

Note:
Created in the Clinic Post-Verify process.

Table 1
URCDELG Specifications
Value Condition(s) Description Notes
9 PHC_42B = 1 Not eligible - acute or chronic condition  
1 Else Eligible  

Water and soft drink consumption (7DVs)

1. WSDD11Y - Drinks regular softdrinks - times per year

Variable name:
WSDD11Y

Based on:
WSD_11, WSD_11N

Description:
The number of times per year the respondent drinks regular softdrinks.

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 1
WSDD11Y Specifications
Value Condition(s) Description Notes
0 WSD_11 = 0 Never  
WSD_11 * 365 WSD_11N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
WSD_11 * 52 WSD_11N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
WSD_11 * 12 WSD_11N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
WSD_11 WSD_11N = 4 Reported number of times consumed per year  
9996 WSD_11N = NA Population exclusions NA
9999 Else   NS

2. WSDD12Y - Drinks diet soft drinks -times per year

Variable name:
WSDD12Y

Based on:
WSD_12, WSD_12N

Description:
The number of times per year the respondent drinks diet softdrinks.

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 2
WSDD12Y Specifications
Value Condition(s) Description Notes
0 WSD_12 = 0 Never  
WSD_12 * 365 WSD_12N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
WSD_12 * 52 WSD_12N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
WSD_12 * 12 WSD_12N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
WSD_12 WSD_12N = 4 Reported number of times consumed per year  
9996 WSD_12N = NA Population exclusions NA
9999 Else   NS

3. WSDD13Y - Drinks sport drinks -times per year

Variable name:
WSDD13Y

Based on:
WSD_13, WSD_13N

Description:
The number of times per year the respondent drinks sport drinks(including Gatorade® or Powerade®).

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 3
WSDD13Y Specifications
Value Condition(s) Description Notes
0 WSD_13 = 0 Never  
WSD_13 * 365 WSD_13N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
WSD_13 * 52 WSD_13N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
WSD_13 * 12 WSD_13N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
WSD_13 WSD_13N = 4 Reported number of times consumed per year  
9996 WSD_13N = NA Population exclusions NA
9999 Else   NS

4. WSDD14Y - Drinks fruit juices -times per year

Variable name:
WSDD14Y

Based on:
WSD_14, WSD_14N

Description:
The number of times per year the respondent drinks fruitjuices.

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 4
WSDD14Y Specifications
Value Condition(s) Description Notes
0 WSD_14 = 0 Never  
WSD_14 * 365 WSD_14N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
WSD_14 * 52 WSD_14N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
WSD_14 * 12 WSD_14N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
WSD_14 WSD_14N = 4 Reported number of times consumed per year  
9996 WSD_14N = NA Population exclusions NA
9999 Else   NS

5. WSDD15Y - Drinks fruit flavoureddrinks - times per year

Variable name:
WSDD15Y

Based on:
WSD_15, WSD_15N

Description:
The number of times per year the respondent drinks fruit flavoureddrinks.

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 5
WSDD15Y Specifications
Value Condition(s) Description Notes
0 WSD_15 = 0 Never  
WSD_15 * 365 WSD_15N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
WSD_15 * 52 WSD_15N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
WSD_15 * 12 WSD_15N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
WSD_15 WSD_15N = 4 Reported number of times consumed per year  
9996 WSD_15N = NA Population exclusions NA
9999 Else   NS

6. WSDD16Y - Drinks vegetable juices -times per year

Variable name:
WSDD16Y

Based on:
WSD_16, WSD_16N

Description:
The number of times per year the respondent drinks vegetablejuices.

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 6
WSDD16Y Specifications
Value Condition(s) Description Notes
0 WSD_16 = 0 Never  
WSD_16 * 365 WSD_16N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
WSD_16 * 52 WSD_16N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
WSD_16 * 12 WSD_16N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
WSD_16 WSD_16N = 4 Reported number of times consumed per year  
9996 WSD_16N = NA Population exclusions NA
9999 Else   NS

7. WSDD21Y - Drinks water - times peryear

Variable name:
WSDD21Y

Based on:
WSD_21, WSD_21N

Description:
The number of times per year the respondent drinks water.

Note:
Created in the Household Post-Verify process.  Based on CCHS2.2 but no direct variables.

Table 7
WSDD21Y Specifications
Value Condition(s) Description Notes
0 WSD_21 = 0 Never  
WSD_21 * 365 WSD_21N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
WSD_21 * 52 WSD_21N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
WSD_21 * 12 WSD_21N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
WSD_21 WSD_21N = 4 Reported number of times consumed per year  
9996 WSD_21N = NA Population exclusions NA
9999 Else   NS

Weight change (10 DVs)

1. WTCD11KG - Weight one year ago(kilograms) - self-reported

Variable name:
WTCD11KG

Based on:
DHH_AGE, WTC_11, WTC_11N

Description:
This variable contains the self-reported weight one year ago inkilograms.

Note:
Created in the Household Post-Verify process.  Respondentsless than 18 years of age were excluded from the population.

Table 1
WTCD11KG Specifications
Value Condition(s) Description Notes
996 DHH_AGE < 18 Population exclusions NA
Round(WTC_11 * 0.4536) WTC_11N = 1 Weight in pounds converted to kilograms  
WTC_11 WTC_11N = 2 Weight in kilograms  
999 Else   NS

2. WTCD11LB - Weight one year ago(pounds) - self-reported

Variable name:
WTCD11LB

Based on:
DHH_AGE, WTC_11, WTC_11N

Description:
This variable contains the self-reported weight one year ago inpounds.

Note:
Created in the Household Post-Verify process.  Respondentsless than 18 years of age were excluded from the population.

Table 2
WTCD11LB Specifications
Value Condition(s) Description Notes
996 DHH_AGE < 18 Population exclusions NA
WTC_11 WTC_11N = 1 Weight in pounds  
Round(WTC_11 * 2.205) WTC_11N = 2 Weight in kilograms converted to pounds  
999 Else   NS

3. WTCD21KG - Weight ten years ago(kilograms) - self-reported

Variable name:
WTCD21KG

Based on:
DHH_AGE, WTC_21, WTC_21N

Description:
This variable contains the self-reported weight ten years ago inkilograms.

Note:
Created in the Household Post-Verify process.  Respondentsless than 28 years of age were excluded from the population.

Table 3
WTCD21KG Specifications
Value Condition(s) Description Notes
996 DHH_AGE < 28 Population exclusions NA
Round(WTC_21 * 0.4536) WTC_21N = 1 Weight in pounds converted to kilograms  
WTC_21 WTC_21N = 2 Weight in kilograms  
999 Else   NS

4. WTCD21LB - Weight ten years ago(pounds) - self-reported

Variable name:
WTCD21LB

Based on
DHH_AGE, WTC_21, WTC_21N

Description:
This variable contains the self-reported weight ten years ago inpounds.  Respondents less than 28 years of age were excludedfrom the population.

Note:
Created in the Household Post-Verify process.

Table 4
WTCD21LB Specifications
Value Condition(s) Description Notes
996 DHH_AGE < 28 Population exclusions NA
WTC_21 WTC_21N = 1 Weight in pounds  
Round(WTC_21 * 2.205) WTC_21N = 2 Weight in kilograms converted to pounds  
999 Else   NS

5. WTCD22KG - Weight at age 25(kilograms) - self-reported

Variable name:
WTCD22KG

Based on:
DHH_AGE, WTC_22, WTC_22N

Description:
This variable contains the self-reported weight at age 25 inkilograms.  Respondents less than 27 years of age or who were35 years of age were excluded from the population.

Note:
Created in the Household Post-Verify process.

Table 5
WTCD22KG Specifications
Value Condition(s) Description Notes
996 DHH_AGE < 27 or
DHH_AGE = 35
Population exclusions NA
Round(WTC_22 * 0.4536) WTC_22N = 1 Weight in pounds converted to kilograms  
WTC_22 WTC_22N = 2 Weight in kilograms  
999 Else   NS

6. WTCD22LB - Weight at age 25(pounds) - self-reported

Variable name:
WTCD22LB

Based on:
DHH_AGE, WTC_22, WTC_22N

Description:
This variable contains the self-reported weight at age 25 inpounds.  Respondents less than 27 years of age or who were 35years of age were excluded from the population.

Note: 
Created in the Household Post-Verify process.

Table 6
WTCD22LB Specifications
Value Condition(s) Description Notes
996 DHH_AGE < 27 or
DHH_AGE = 35
Population exclusions NA
WTC_22 WTC_22N = 1 Weight in pounds  
Round(WTC_22 * 2.205) WTC_22N = 2 Weight in kilograms converted to pounds  
999 Else   NS

7. WTCD23KG - Most ever weighed(kilograms) - self-reported

Variable name:
WTCD23KG

Based on:
DHH_AGE, WTC_23, WTC_23N

Description:
This variable contains the self-reported highest weight inkilograms.  Respondents less than 18 years of age wereexcluded from the population.

Note:
Created in the Household Post-Verify process.

Table 7
WTCD23KG Specifications
Value Condition(s) Description Notes
996 DHH_AGE < 18 Population exclusions NA
Round(WTC_23 * 0.4536) WTC_23N = 1 Weight in pounds converted to kilograms  
WTC_23 WTC_23N = 2 Weight in kilograms  
999 Else   NS

8. WTCD23LB - Most ever weighed(pounds) - self-reported

Variable name:
WTCD23LB

Based on:
DHH_AGE, WTC_23, WTC_23N

Description:
This variable contains the self-reported highest weight inpounds.  Respondents less than 18 years of age were excludedfrom the population.

Note:
Created in the Household Post-Verify process.

Table 8
WTCD23LB Specifications
Value Condition(s) Description Notes
996 DHH_AGE < 18 Population exclusions NA
WTC_23 WTC_23N = 1 Weight in pounds  
Round(WTC_23 * 2.205) WTC_23N = 2 Weight in kilograms converted to pounds  
999 Else   NS

9. WTCD25KG - Least ever weighed(kilograms) - self-reported

Variable name:
WTCD25KG

Based on:
DHH_AGE, WTC_25, WTC_25N

Description:
This variable contains the self-reported lowest weight inkilograms.  Respondents less than 19 years of age wereexcluded from the population.

Note:
Created in the Household Post-Verify process.

Table 9
WTCD25KG Specifications
Value Condition(s) Description Notes
996 DHH_AGE < 19 Population exclusions NA
Round(WTC_25 * 0.4536) WTC_25N = 1 Weight in pounds converted to kilograms  
WTC_25 WTC_25N = 2 Weight in kilograms  
999 Else   NS

10. WTCD25LB - Least ever weighed(pounds) - self-reported

Variable name:
WTCD25LB

Based on:
DHH_AGE, WTC_25, WTC_25N

Description:
This variable contains the self-reported lowest weight inpounds.  Respondents less than 19 years of age were excludedfrom the population.

Note:
Created in the Household Post-Verify process.

Table 10
WTCD25LB Specifications
Value Condition(s) Description Notes
996 DHH_AGE < 19 Population exclusions NA
WTC_25 WTC_25N = 1 Weight in pounds  
Round(WTC_25 * 2.205) WTC_25N = 2 Weight in kilograms converted to pounds  
999 Else   NS

Canadian Health Measures Survey (CHMS) Cycle 01 Derived Variable (DV) Specifications

Table of contents

mCAFT (9 DVs)

  1. AFCDELG - Eligibility for the modified Canadian Aerobic Fitness Test (mCAFT)
  2. AFTD01 - Starting stage of the modified Canadian Aerobic Fitness Test (mCAFT)
  3. AFTD02 - Ceiling heart rate for the modified Canadian Aerobic Fitness Test (mCAFT)
  4. AFTD21 - Final Stepping Stage of the modified Canadian Aerobic Fitness Test (mCAFT)
  5. AFTD22 - Immediate Post-exercise Heart Rate
  6. AFTD71 - Oxygen cost of the modified Canadian Aerobic Fitness Test (mCAFT)
  7. AFTD72 - Aerobic fitness score based on the modified Canadian Aerobic Fitness Test (mCAFT)
  8. AFTD73 - Aerobic fitness norms for respondents aged 15 - 69
  9. AFTD74 - Aerobic fitness norms for respondents aged less than 15

Alcohol use (3 DVs)

  1. ALCDDLY - Average Daily Alcohol Consumption
  2. ALCDTYP - Type of Drinker
  3. ALCDWKY - Weekly Consumption

Anthropometric (23 DVs)

  1. ANCDELG - Eligibility for the Anthropometric component
  2. HWMD11IN - Standing height (inches) – measured
  3. HWMD12IN - Sitting height (inches) - measured
  4. HWMD13LB - Weight (pounds) – measured
  5. HWMD14IN - Waist circumference (inches) – measured
  6. HWMD15IN - Hip circumference (inches) – measured
  7. HWMDBMI - Body Mass Index (BMI) – measured
  8. HWMDBMIA - BMI classification for adults aged 18 and over (measured) - international standard
  9. HWMDBMIK - BMI Classification for Children Aged 6 to 17 (measured) - CDC BMI-for-age
  10. HWMDCOL - BMI Classification for Children Aged 6 to 17 (Measured) - Cole Classification System
  11. HWMDHTM – Standing height (metres) – measured
  12. HWMDLLN - Leg Length
  13. HWMDMAT - Maturity Offset
  14. HWMDWSTA - Waist Circumference Norms
  15. HWMDWTH - Waist to hip ratio
  16. SFMDBCA - Body Composition Norms
  17. SFMDBSA - Biceps Skinfold Average
  18. SFMDICA - Iliac Crest Skinfold Average
  19. SFMDMCA - Medial Calf Skinfolds Average
  20. SFMDS5 - Sum of 5 Skinfold Measurements
  21. SFMDS5A - Sum of 5 Skinfolds Measurements - Norms (ages 15-69)
  22. SFMDSSA - Subscapular Skinfolds Average
  23. SFMDTSA - Triceps Skinfolds Average

Blood Pressure (20 DVs)

  1. BPMD160 - Type of problem - first set
  2. BPMD161 - Average systolic blood pressure - first set
  3. BPMD162 - Average diastolic blood pressure - first set
  4. BPMD163 - Average resting heart rate - first set
  5. BPMD260 - Type of problem - second set
  6. BPMD261 - Average systolic blood pressure - second set
  7. BPMD262 - Average diastolic blood pressure - second set
  8. BPMD263 - Average resting heart rate - second set
  9. BPMD360 - Type of problem - third set
  10. BPMD361 - Average systolic blood pressure - third set
  11. BPMD362 - Average diastolic blood pressure - third set
  12. BPMD363 - Average resting heart rate - third set
  13. BPMDBPA - Blood pressure norms for respondents 18 or older (Prevalence)
  14. BPMDBPK - Blood pressure norms for respondents less than 18 (Prevalence)
  15. BPMDPBPD - Final average diastolic blood pressure (Prevalence)
  16. BPMDPBPS - Final average systolic blood pressure (Prevalence)
  17. BPMDPHR - Final average resting heart rate (Prevalence)
  18. BPMDSBPD - Final average diastolic blood pressure (Screening)
  19. BPMDSBPS - Final average systolic blood pressure (Screening)
  20. BPMDSHR - Final average resting heart rate (Screening)

Breastfeeding information (1 DV)

  1. BRIFEB6 - Exclusively breastfed for at least 3 months

Chronic conditions (1 DV)

  1. CCCF1 - Has a Chronic Condition

Children's physical activity (2 DVs)

  1. CPADSAC - Total number of hours per day spent in sedentary activities
  2. CPADTOT - Total number of hours per week participated in physical activities

Dietary fat consumption (2 DVs)

  1. DFCD11Y - Eats regular-fat salad dressing - times per year
  2. DFCD12Y - Eats regular-fat potato chips, tortilla chips or corn chips - times per year

Demographic and household variables (9 DVs)

  1. DHHD611 - Number of Persons in Household 6 to 11 Years of Age
  2. DHHDDWE - Dwelling Type
  3. DHHDECF - Economic Family Status (Household Type)
  4. DHHDHSZ - Household Size
  5. DHHDL12 - Number of Persons in Household Less Than 12 Years of Age
  6. DHHDLE5 - Number of Persons in Household Less Than 6 Years of Age
  7. DHHDLVG - Living/ Family Arrangement of Selected Respondent
  8. DHHDOKD - Number of Persons in Household 16 or 17 Years of Age
  9. DHHDYKD - Number of Persons in Household Less Than 16 Years of Age

Education (4 DVs)

  1. EDUDH04 - Highest Level of Education - Household, 4 Levels
  2. EDUDH10 - Highest Level of Education - Household, 10 Levels
  3. EDUDR04 - Highest Level of Education - Household, 4 Levels
  4. EDUDR10 - Highest Level of Education - Household, 10 Levels

General health (2 DVs)

  1. GENDHDI - Self-Rated Health (Formerly Health Description Index)
  2. GENDMHI - Self-Rated Mental Health

Grains, fruits and vegetables consumption (13 DVs)

  1. GFVD11Y - Eats hot or cold cereal - times per year
  2. GFVD12Y - Eats brown bread, including bagels, rolls, pita bread or tortillas - times per year
  3. GFVD13Y - Eats white bread, including bagels, rolls, pita bread or tortillas - times per year
  4. GFVD14Y - Eats any kind of pasta - times per year
  5. GFVD15Y - Eats any kind of rice - times per year
  6. GFVD16Y - Eats instant, seasoned or wild rice - times per year
  7. GFVD17Y - Eats fruit - times per year
  8. GFVD18Y - Eats tomatoes or tomato sauce - times per year
  9. GFVD19Y - Eats lettuce or green leafy salad - times per year
  10. GFVD20Y - Eats spinach, mustard greens or collards - times per year
  11. GFVD21Y - Eats french fries, home fries or hash brown potatoes - times per year
  12. GFVD22Y - Eats other potatoes - times per year
  13. GFVD23Y - Eats all other types of vegetables - times per year

Grooming product use (7 DVs)

  1. GPUD12Y - Uses fragrance - times per year
  2. GPUD13Y - Uses eye make-up - times per year
  3. GPUD14Y - Uses lipstick - times per year
  4. GPUD15Y - Uses hair dye - times per year
  5. GPUD16Y - Uses hair style products - times per year
  6. GPUD17Y - Uses manicure preparations - times per year
  7. GPUD18Y - Uses scented body products - times per year

Grip Strength (4 DVs)

  1. GSCDELG - Eligibility - Grip Strength component
  2. GSMD51 - Total hand grip strength
  3. GSMD52 - Grip strength norms for respondents 15 – 69
  4. GSMD53 - Grip strength norms for respondents less than 15

Hobbies (10 DVs)

  1. HOBD12Y - Arts - times per year
  2. HOBD13Y - Pottery - times per year
  3. HOBD14Y - Model making - times per year
  4. HOBD15Y - Making fishing sinkers - times per year
  5. HOBD16Y - Welding - times per year
  6. HOBD17Y - Auto repairs - times per year
  7. HOBD18Y - Electronics - times per year
  8. HOBD19Y - Plumbing - times per year
  9. HOBD20Y - Refinishing furniture - times per year
  10. HOBD21Y - Woodworking - times per year

Health utility index (HUI) (10 DVs)

  1. HUIDCOG - Cognition (Function Code)
  2. HUIDDEX - Dexterity Trouble (Function Code)
  3. HUIDEMO - Emotional Problems (Function Code)
  4. HUIDHER - Hearing Problems (Function Code)
  5. HUIDHSC - Health Utility Index - categorical variable
  6. HUIDHSI - Health Utility Index
  7. HUIDMOB - Mobility Trouble (Function Code)
  8. HUIDPAD - Activities Prevented / Pain (Function Code)
  9. HUIDSPE - Speech Trouble (Function Code)
  10. HUIDVIS - Vision Trouble (Function Code)

Height and weight (9 DVs)

  1. HWTDBMI - Body Mass Index (self-reported)
  2. HWTDBMIA - BMI Classification for Adults Aged 18 and Over (self-reported) - International Standard
  3. HWTDBMIK - BMI Classification for Children Less Than 18 Years of Age (self-reported) - CDC BMI-for-age
  4. HWTDCM - Height (centimetres) - self-reported
  5. HWTDCOL - BMI classification for children aged 6 to 17 (self-reported) - Cole classification system
  6. HWTDHTM - Height (metres) - self-reported
  7. HWTDIN - Height (inches) - self-reported
  8. HWTDKG - Weight (kilograms) - self-reported
  9. HWTDLB - Weight (pounds) - self-reported

Income (5 DVs)

  1. INCDDIA2 - Total household income - 2 categories
  2. INCDDIA4 - Total household income - 4 categories
  3. INCDDIA5 - Total household income - 5 categories
  4. INCDHH - Total Household Income - All Sources
  5. INCDPER - Personal Income - All Sources

Labour force (8 DVs)

  1. LBFDHPW - Total usual hours worked per week
  2. LBFDJST - Job status over past year
  3. LBFDMJS - Multiple job status
  4. LBFDPFT - Full-time/ part-time working status (for total usual hours)
  5. LBFDRNW - Main reason for not working last week
  6. LBFDSTU - Student working status
  7. LBFDWSL - Working status last week
  8. LBFDWSS - Working status last week

Milk and dairy product consumption (4 DVs)

  1. MDCD11Y - Drinks milk - times per year
  2. MDCD13Y - Eats cottage cheese - times per year
  3. MDCD14Y - Eats yogurt - times per year
  4. MDCD15Y - Eats ice cream or frozen yogurt - times per year

Meat and fish consumption (11 DVs)

  1. MFCD11Y - Eats red meat - times per year
  2. MFCD12Y - Eats liver - times per year
  3. MFCD13Y - Eats other organ meats - times per year
  4. MFCD14Y - Eats beef or pork hot dogs - times per year
  5. MFCD15Y - Eats sausage or bacon- times per year
  6. MFCD16Y - Eats salt water fish - times per year
  7. MFCD17Y - Eats fresh water fish - times per year
  8. MFCD18Y - Eats shellfish - times per year
  9. MFCD19Y - Eats eggs and egg dishes - times per year
  10. MFCD20Y - Eats cooked dried beans - times per year
  11. MFCD21Y - Eats peanuts, walnuts, seeds or other nuts - times per year

Oral Health (77 DVs)

  1. OHCDELG - Eligibility - Oral Health component
  2. OHEDAC01 - Total number of adult crowns - code 1
  3. OHEDAC02 - Total number of adult crowns - code 2
  4. OHEDAC03 - Total number of adult crowns - code 3
  5. OHEDAC04 - Total number of adult crowns - code 4
  6. OHEDAC05 - Total number of adult crowns - code 5
  7. OHEDAC06 - Total number of adult crowns - code 6
  8. OHEDAC07 - Total number of adult crowns - code 7
  9. OHEDAC08 - Total number of adult crowns - code 8
  10. OHEDAC09 - Total number of adult crowns - code 9
  11. OHEDAC10 - Total number of adult crowns - code 10
  12. OHEDAC12 - Total number of adult crowns - code 12
  13. OHEDAC13 - Total number of adult crowns - code 13
  14. OHEDAC14 - Total number of adult crowns - code 14
  15. OHEDAC15 - Total number of adult crowns - code 15
  16. OHEDAC16 - Total number of adult crowns - code 16
  17. OHEDAC17 - Total number of adult crowns - code 17
  18. OHEDAC18 - Total number of adult crowns - code 18
  19. OHEDAC19 - Total number of adult crowns - code 19
  20. OHEDAC20 - Total number of adult crowns - code 20
  21. OHEDAC21 - Total number of adult crowns - code 21
  22. OHEDAR01 - Total number of adult roots - code 1
  23. OHEDAR03 - Total number of adult roots - code 3
  24. OHEDAR04 - Total number of adult roots - code 4
  25. OHEDAR05 - Total number of adult roots - code 5
  26. OHEDAR06 - Total number of adult roots - code 6
  27. OHEDAR07 - Total number of adult roots - code 7
  28. OHEDAR11 - Total number of adult roots - code 11
  29. OHEDAR12 - Total number of adult roots - code 12
  30. OHEDAR13 - Total number of adult roots - code 13
  31. OHEDAR14 - Total number of adult roots - code 14
  32. OHEDAR15 - Total number of adult roots - code 15
  33. OHEDAR16 - Total number of adult roots - code 16
  34. OHEDAR17 - Total number of adult roots - code 17
  35. OHEDAR19 - Total number of adult roots - code 19
  36. OHEDAR20 - Total number of adult roots - code 20
  37. OHEDAR21 - Total number of adult roots - code 21
  38. OHEDCS01 - Calculus score recode - teeth 17 and 16
  39. OHEDCS02 - Calculus score recode - tooth 11
  40. OHEDCS03 - Calculus score recode - teeth 26 and 27
  41. OHEDCS04 - Calculus score recode - teeth 37 and 36
  42. OHEDCS05 - Calculus score recode - tooth 31
  43. OHEDCS06 - Calculus score recode - teeth 46 and 47
  44. OHEDDS01 - Debris score recode - teeth 17 and 16
  45. OHEDDS02 - Debris score recode - tooth 11
  46. OHEDDS03 - Debris score recode - teeth 26 and 27
  47. OHEDDS04 - Debris score recode - teeth 37 and 36
  48. OHEDDS05 - Debris score recode - tooth 31
  49. OHEDDS06 - Debris score recode - teeth 46 and 47
  50. OHEDDT01 - Total number of deciduous teeth - code 1
  51. OHEDDT02 - Total number of deciduous teeth - code 2
  52. OHEDDT03 - Total number of deciduous teeth - code 3
  53. OHEDDT04 - Total number of deciduous teeth - code 4
  54. OHEDDT05 - Total number of deciduous teeth - code 5
  55. OHEDDT06 - Total number of deciduous teeth - code 6
  56. OHEDDT07 - Total number of deciduous teeth - code 7
  57. OHEDDT08 - Total number of deciduous teeth - code 8
  58. OHEDDT09 - Total number of deciduous teeth - code 9
  59. OHEDDT10 - Total number of deciduous teeth - code 10
  60. OHEDDT12 - Total number of deciduous teeth - code 12
  61. OHEDDT13 - Total number of deciduous teeth - code 13
  62. OHEDDT14 - Total number of deciduous teeth - code 14
  63. OHEDDT15 - Total number of deciduous teeth - code 15
  64. OHEDDT16 - Total number of deciduous teeth - code 16
  65. OHEDDT17 - Total number of deciduous teeth - code 17
  66. OHEDDT20 - Total number of deciduous teeth - code 20
  67. OHEDDT21 - Total number of deciduous teeth - code 21
  68. OHEDFLUO - Fluorosis score recode
  69. OHEDGS12 - Gingivitis score recode - tooth 12
  70. OHEDGS16 - Gingivitis score recode - tooth 16
  71. OHEDGS24 - Gingivitis score recode - tooth 24
  72. OHEDGS32 - Gingivitis score recode - tooth 32
  73. OHEDGS36 - Gingivitis score recode - tooth 36
  74. OHEDGS44 - Gingivitis score recode - tooth 44
  75. OHRD25 - Test exclusion – probing
  76. OHMD31Y - Brushing teeth - number times per year
  77. OHMD32Y - Flossing teeth - number times per year

Physical activities (6 DVs)

  1. PACDEE - Daily Energy Expenditure
  2. PACDFM - Average Monthly Frequency of Physical Activity Lasting Over 15 Minutes
  3. PACDFR - Frequency of All Physical Activity Lasting Over 15 Minutes
  4. PACDPAI - Physical Activity Index
  5. PACFD - Participant In Daily Physical Activity Lasting Over 15 Minutes
  6. PACFLEI - Participant In Leisure Physical Activity

Partial Curl-Ups (2 DVs)

  1. PCCDELG - Eligibility - Partial Curl-up component
  2. PCMD11 - Partial curl-up norms for respondents 15 - 69

Phlebotomy (2 DVs)

  1. BDCD13 - Blood donation status
  2. PHBDELG - Eligibility - Phlebotomy component

Report of Measurements (2 DVs)

  1. RMCDBCK - Back fitness norms for respondents 15 – 69
  2. RMCDMSK - Musculo-skeletal fitness norms for respondents 15 – 69

Sedentary activities (1 DV)

  1. SACDTOT - Total Number of Hours Per Week Spent In Sedentary Activities

Screening (1 DV)

  1. ATGD12 - Fasting status

Socio-demographic characteristics (8 DVs)

  1. SDCDAIM - Age at time of immigration
  2. SDCDCGT - Culture / Race Flag
  3. SDCDFL1 - First official language learned and still understood
  4. SDCDLNG - Language(s) in which respondent can converse
  5. SDCDRES - Length of time in Canada since immigration
  6. SDCFABT - Aboriginal flag
  7. SDCFIMM - Immigration flag
  8. SDCGCB - Country of birth – grouped

Strengths and difficulties (12 DVs)

  1. SDQDCON - Conduct Problems
  2. SDQDEMO - Emotional Symptoms
  3. SDQDHYP - Hyperactivity/Inattention
  4. SDQDPRO - Prosocial Behaviour
  5. SDQDPRP - Peer Relationship Problems
  6. SDQDTOT - Total Difficulties Score
  7. SDQGCON - Conduct Problems Score – Grouped
  8. SDQGEMO - Emotional Symptoms Score – Grouped
  9. SDQGHYP - Hyperactivity Score – Grouped
  10. SDQGPRO - Prosocial Behaviour Score – Grouped
  11. SDQGPRP - Peer Relationship Problems Score – Grouped
  12. SDQGTOT - Total Difficulties Score – Grouped

Smoking (3 DVs)

  1. SMKDSTP - Number of Years Since Stopping Smoking Completely
  2. SMKDSTY - Type of Smoker
  3. SMKDYFS - Number of Years Smoked Daily (Former Daily Smokers Only)

Spirometry (4 DVs)

  1. SPCDELG - Eligibility - Spirometry component
  2. SPMDB1FP - Percent predicted FEV1/FVC
  3. SPMDB1P - Percent predicted Forced Expiratory Volume (FEV1)
  4. SPMDBFVP - Percent predicted Forced Vital Capacity (FVC)

Sit and Reach (4 DVs)

  1. SRCDELG - Eligibility - Sit and Reach component
  2. SRMD11 - Sit and reach measure
  3. SRMD12 - Sit and reach norms - respondents 15 – 69
  4. SRMD13 - Sit and reach norms - respondents less than 15

Urine Collection (1 DV)

  1. URCDELG - Eligibility - Urine Collection component

Water and soft drink consumption (7 DVs)

  1. WSDD11Y - Drinks regular soft drinks - times per year
  2. WSDD12Y - Drinks diet soft drinks - times per year
  3. WSDD13Y - Drinks sport drinks - times per year
  4. WSDD14Y - Drinks fruit juices - times per year
  5. WSDD15Y - Drinks fruit flavoured drinks - times per year
  6. WSDD16Y - Drinks vegetable juices - times per year
  7. WSDD21Y - Drinks water - times per year

Weight change (10 DVs)

  1. WTCD11KG - Weight one year ago (kilograms) - self-reported
  2. WTCD11LB - Weight one year ago (pounds) - self-reported
  3. WTCD21KG - Weight ten years ago (kilograms) - self-reported
  4. WTCD21LB - Weight ten years ago (pounds) - self-reported
  5. WTCD22KG - Weight at age 25 (kilograms) - self-reported
  6. WTCD22LB - Weight at age 25 (pounds) - self-reported
  7. WTCD23KG - Most ever weighed (kilograms) - self-reported
  8. WTCD23LB - Most ever weighed (pounds) - self-reported
  9. WTCD25KG - Least ever weighed (kilograms) - self-reported
  10. WTCD25LB - Least ever weighed (pounds) - self-reported

mCAFT (9 DVs)

1. AFCDELG - Eligibility for themodified Canadian Aerobic Fitness Test (mCAFT)

Variable name:
AFCDELG

Based on:
CLC_AGE, V2_TYPE, ATG_13, ATG_33B, PHC_12, PHC_36, PHC_37, PHC_42G,MHR_611B, PAR_11, PAR_21, PAR_31, PAR_43, PAR_44E, PAR_44H,PAR_44I, PAR_45, PAR_5A3A, PAR_5B3A, PAR_5C3A, PAR_5D3A, PAR_5E3A,PAR_5F3A, PAR_5G3A, PAR_5H3A, PAR_5I3A, PAR_5J3A, PAR_5K3A, PAR_61,PAR_72A, ORS_3, BPMDBPS, BPMDBPD, BPMDHR, BDCD13

Description:
This variable indicates whether the respondent was eligible for the modified Canadian Aerobic Fitness Test (mCAFT). As there are multiple reasons to be screened out of this measure, the prevalence of screen outs by reason should not be based on frequency counts for this variable. This test was performed by respondents 6 to 69 years of age.

Note:
Created in the Clinic Post-Verify process.

Table 1
AFCDELG Specifications
Value Condition(s) Description Notes
2 V2_TYPE = 2 Not eligible - home visit  
3 CLC_AGE > 69 Not eligible – age  
4 ATG_13 = 1 Not eligible - ate too close to visit time  
5 ATG_33B = 1 Not eligible - drank alcohol too close to visit time  
6 (12 < PHC_12 < NA) Not eligible - more than 12 weeks pregnant  
8 PHC_36 = 1 and
PHC_37 = 2
Not eligible - did not bring breathing medication  
9 PHC_42G = 1 Not eligible - acute or chronic condition  
12 MHR_611B = 1 Not eligible - medication use  
13 (PAR_N11 = 1 or
PAR_21 = 1 or
PAR_31 = 1 or
(PAR_43 = 1 and
PAR_44E = 1) or
(PAR_43 = 1 and
PAR_44H = 1) or
(PAR_43 = 1 and
PAR_44I = 1 and
PAR_45 = 1) or
PAR_5A3A = 1 or
PAR_5B3A = 1 or
PAR_5C3A = 1 or
PAR_5D3A = 1 or
PAR_5E3A = 1 or
PAR_5F3A = 1 or
PAR_5G3A = 1 or
PAR_5H3A = 1 or
PAR_5I3A = 1 or
PAR_5J3A = 1 or
PAR_5K3A = 1 or
PAR_61 = 1 or
PAR_72A = 1)
Not eligible - PAR-Q answer  
14 ORS_3 = 1 Not eligible - other reason  
15 (CLC_AGE > 14 and
(144 < BPMDBPS < NA)) or
(CLC_AGE > 14 and
(144 < BPMDBPD < NA))
Not eligible - high blood pressure  
16 CLC_AGE > 14 and
(99 < BPMDHR < NA)
Not eligible - high heart rate  
17 BDCD13 = 1 Not eligible - donated blood day before clinic visit  
1 Else Eligible  

2. AFTD01 - Starting stage of the modified Canadian Aerobic Fitness Test (mCAFT)

Variable name:
AFTD01

Based on:
CLC_AGE, CLC_SEX, AFCDELG

Description:
This variable indicates the starting stage for the modified Canadian Aerobic Fitness Test (mCAFT).

Note:
Created in the Clinic data collection application. This test was performed by respondents 6 to 69 years of age.

Source:
The Canadian Physical Activity, Fitness and Lifestyle Approach (3rd Edition, 2004) by the Canadian Society for Exercise Physiology (CSEP)

Table 2
AFTD01 Specifications
Value Condition(s) Description Notes
9 (CLC_AGE = DK, RF, NS) or
(CLC_SEX = DK, RF, NS)
At least one required question was not answered (don't know, refusal, not stated) NS
6 (1 < AFCDELG < NA) Population exclusions NA
1 (CLC_SEX = 1 and
(59 < CLC_AGE < 70)) or
(CLC_SEX = 2 and
(49 < CLC_AGE < 70))
Set mCAFT starting stage to Stage 1  
2 (CLC_SEX = 1 and
(49 < CLC_AGE < 60)) or
(CLC_SEX = 2 and
(39 < CLC_AGE < 50))
Set mCAFT starting stage to Stage 2  
3 (CLC_SEX = 1 and
(29 < CLC_AGE < 50)) or
(CLC_SEX = 2 and
(14 < CLC_AGE < 40))
Set mCAFT starting stage to Stage 3  
4 CLC_SEX = 1 and
(14 < CLC_AGE < 30)
Set mCAFT starting stage to Stage 4  
5 CLC_AGE < 15 Set mCAFT starting stage to Stage 5  

3. AFTD02 - Ceiling heart rate for the modified Canadian Aerobic Fitness Test (mCAFT)

Variable name:
AFTD02

Based on:
CLC_AGE, AFCDELG, AFTD01

Description:
This variable indicates the ceiling or maximum heart rate that the respondent may reach when completing the modified Canadian Aerobic Fitness Test (mCAFT). It is the heart rate (in beats per minute) at which the test is stopped. The mCAFT consists of a maximum of eight 3-minute stepping tests. The test is discontinued when the respondent's heart rate reaches the ceiling indicated. The ceiling rates are based on the age of the respondent.

Note:
Created in the Clinic data collection application. This test was performed by respondents 6 to 69 years of age.

Source:
The Canadian Physical Activity, Fitness and Lifestyle Approach (3rd Edition, 2004) by the Canadian Society for Exercise Physiology (CSEP)

Table 3
AFTD02 Specifications
Value Condition(s) Description Notes
999 (CLC_AGE = DK, RF, NS) or
(AFTD01 = DK, RF, NS)
At least one required question was not answered (don't know, refusal, not stated) NS
996 (1 < AFCDELG < NA) Population exclusions NA
182 CLC_AGE = 6 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 6 (in beats per minute)  
181 CLC_AGE = 7 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 7 (in beats per minute)  
180 CLC_AGE = 8 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 8 (in beats per minute)  
179 CLC_AGE = 9 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 9 (in beats per minute)  
178 CLC_AGE = 10 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 10 (in beats per minute)  
177 (CLC_AGE = 11, 12) and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 11 to 12 (in beats per minute)  
176 CLC_AGE = 13 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 13 (in beats per minute)  
175 CLC_AGE = 14 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 14 (in beats per minute)  
174 CLC_AGE = 15 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 15 (in beats per minute)  
173 (CLC_AGE = 16, 17) and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 16 to 17 (in beats per minute)  
172 CLC_AGE = 18 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 18 (in beats per minute)  
171 CLC_AGE = 19 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 19 (in beats per minute)  
170 CLC_AGE = 20 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 20 (in beats per minute)  
169 CLC_AGE = 21 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 21 (in beats per minute)  
168 CLC_AGE = 22 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 22 (in beats per minute)  
167 (CLC_AGE = 23, 24) and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 23 to 24 (in beats per minute)  
166 CLC_AGE = 25 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 25 (in beats per minute)  
165 CLC_AGE = 26 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 26 (in beats per minute)  
164 CLC_AGE = 27 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 27 (in beats per minute)  
163 CLC_AGE = 28 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 28 (in beats per minute)  
162 (CLC_AGE = 29, 30) and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 29 to 30 (in beats per minute)  
161 CLC_AGE = 31 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 31 (in beats per minute)  
160 CLC_AGE = 32 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 32 (in beats per minute)  
159 CLC_AGE = 33 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 33 (in beats per minute)  
158 CLC_AGE = 34 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 34 (in beats per minute)  
157 CLC_AGE = 35 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 35 (in beats per minute)  
156 (CLC_AGE = 36, 37) and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 36 to 37 (in beats per minute)  
155 CLC_AGE = 38 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 38 (in beats per minute)  
154 CLC_AGE = 39 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 39 (in beats per minute)  
153 CLC_AGE = 40 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 40 (in beats per minute)  
152 CLC_AGE = 41 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 41 (in beats per minute)  
151 CLC_AGE = 42 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 42 (in beats per minute)  
150 (CLC_AGE = 43, 44) and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 43 to 44 (in beatsper minute)  
149 CLC_AGE = 45 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 45 (in beats perminute)  
148 CLC_AGE = 46 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 46 (in beats perminute)  
147 CLC_AGE = 47 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 47 (in beats perminute)  
146 CLC_AGE = 48 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 48 (in beats perminute)  
145 (CLC_AGE = 49, 50) and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 49 to 50 (in beatsper minute)  
144 CLC_AGE = 51 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 51 (in beats perminute)  
143 CLC_AGE = 52 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 52 (in beats perminute)  
142 CLC_AGE = 53 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 53 (in beats perminute)  
141 CLC_AGE = 54 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 54 (in beats perminute)  
140 CLC_AGE = 55 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 55 (in beats perminute)  
139 (CLC_AGE = 56, 57) and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 56 to 57 (in beatsper minute)  
138 CLC_AGE = 58 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 58 (in beats perminute)  
137 CLC_AGE = 59 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 59 (in beats perminute)  
136 CLC_AGE = 60 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 60 (in beats perminute)  
135 CLC_AGE = 61 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 61 (in beats perminute)  
134 CLC_AGE = 62 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 62 (in beats perminute)  
133 (CLC_AGE = 63, 64) and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 63 to 64 (in beatsper minute)  
132 CLC_AGE = 65 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 65 (in beats perminute)  
131 CLC_AGE = 66 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 66 (in beats perminute)  
130 CLC_AGE = 67 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 67 (in beats perminute)  
129 CLC_AGE = 68 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 68 (in beats perminute)  
128 CLC_AGE = 69 and
(0 < AFTD01 < 6)
The ceiling heart rate for respondents aged 69 (in beats perminute)  

4. AFTD21 - Final Stepping Stage of the modified Canadian Aerobic Fitness Test (mCAFT)

Variable name:
AFTD21

Based on:
AFCDELG, AFT_11, AFT_12, AFT_13, AFT_14, AFT_15, AFT_16, AFT_17, AFT_18

Description:
This variable indicates the final stepping stage for respondents that completed the modified Canadian Aerobic Fitness Test (mCAFT).

Note:
Created in the Clinic data collection application. This test was performed by respondents 6 to 69 years of age.

Source:
The Canadian Physical Activity, Fitness and Lifestyle Approach (3rd Edition, 2004) by the Canadian Society for Exercise Physiology (CSEP)

Table 4
AFTD21 Specifications
Value Condition(s) Description Notes
96 (1 < AFCDELG < NA) Population exclusions NA
8 (0 < AFT_18 < NA) Final stepping stage set to stage 8  
7 (0 < AFT_17 < NA) Final stepping stage set to stage 7  
6 (0 < AFT_16 < NA) Final stepping stage set to stage 6  
5 (0 < AFT_15 < NA) Final stepping stage set to stage 5  
4 (0 < AFT_14 < NA) Final stepping stage set to stage 4  
3 (0 < AFT_13 < NA) Final stepping stage set to stage 3  
2 (0 < AFT_12 < NA) Final stepping stage set to stage 2  
1 (0 < AFT_11 < NA) Final stepping stage set to stage 1  
99 Else   NS

5. AFTD22 - Immediate Post-exercise HeartRate

Variable name:
AFTD22

Based on:
AFCDELG, AFT_11, AFT_12, AFT_13, AFT_14, AFT_15, AFT_16, AFT_17,AFT_18

Description:
This variable indicates theimmediate post-exercise heart rate for respondents who completedthe modified Canadian Aerobic Fitness Test (mCAFT).

Note:
Created in the Clinic data collection application. This testwas performed by respondents 6 to 69 years of age.

Source:
The Canadian Physical Activity,Fitness and Lifestyle Approach (3rd Edition, 2004) by the CanadianSociety for Exercise Physiology (CSEP)

Table 5
AFTD22 Specifications
Value Condition(s)  Description Notes
96 (1 < AFCDELG < NA) Population exclusions NA
AFTD22 =
AFT_18
(0 < AFT_18 < NA) The Immediate Post-exercise Heart Rate equals the heart rate atthe end of Stage 8  
AFTD22 =
AFT_17
(0 < AFT_17 < NA) The Immediate Post-exercise Heart Rate equals the heart rate atthe end of Stage 7  
AFTD22 =
AFT_16
(0 < AFT_16 < NA) The Immediate Post-exercise Heart Rate equals the heart rate atthe end of Stage 6  
AFTD22 =
AFT_15
(0 < AFT_15 < NA) The Immediate Post-exercise Heart Rate equals the heart rate atthe end of Stage 5  
AFTD22 =
AFT_14
(0 < AFT_14 < NA) The Immediate Post-exercise Heart Rate equals the heart rate atthe end of Stage 4  
AFTD22 =
AFT_13
(0 < AFT_13 < NA) The Immediate Post-exercise Heart Rate equals the heart rate atthe end of Stage 3  
AFTD22 =
AFT_12
(0 < AFT_12 < NA) The Immediate Post-exercise Heart Rate equals the heart rate atthe end of Stage 2  
AFTD22 =
AFT_11
(0 < AFT_11 < NA) The Immediate Post-exercise Heart Rate equals the heart rate atthe end of Stage 1  
99 Else   NS

6. AFTD71 - Oxygen cost of the modifiedCanadian Aerobic Fitness Test (mCAFT)

Variable name:
AFTD71

Based on:
CLC_SEX, AFCDELG, AFTD21

Description:
This variable indicates the Oxygen cost for respondents whocompleted the modified Canadian Aerobic Fitness Test (mCAFT).Oxygen cost is measured in millilitres / kilograms / minute.

Note:
Created in the Clinic data collection application. This testwas performed by respondents 6 to 69 years of age.

Source:
The Canadian Physical Activity, Fitness and Lifestyle Approach (3rdEdition, 2004) by the Canadian Society for Exercise Physiology(CSEP)

Table 6
AFTD71 Specifications
Value Condition(s) Description Notes
99.9 (AFTD21 = DK, RF, NS) At least one required question was not answered (don'tknow, refusal, not stated) NS
99.6 (1 < AFCDELG < NA) Population exclusions NA
15.9 AFTD21 = 1 Oxygen cost for respondents with a final stepping stage ofstage 1  
18.0 AFTD21 = 2 Oxygen cost for respondents with a final stepping stage ofstage 2  
22.0 AFTD21 = 3 Oxygen cost for respondents with a final stepping stage ofstage 3  
24.5 AFTD21 = 4 Oxygen cost for respondents with a final stepping stage ofstage 4  
26.3 CLC_SEX = 2 and AFTD21 = 5 Oxygen cost for female respondents with a final stepping stageof stage 5  
29.5 (CLC_SEX = 1 and
AFTD21 = 5) or
(CLC_SEX = 2 and
AFTD21 = 6)
Oxygen cost for male respondents with a final stepping stage ofstage 5 and females with a final stepping stage of stage 6  
33.6 (CLC_SEX = 1 and
AFTD21 = 6) or
(CLC_SEX = 2 and
AFTD21 = 7)
Oxygen cost for male respondents with a final stepping stage ofstage 6 and females with a final stepping stage of stage 7  
36.2 (CLC_SEX = 1 and
AFTD21 = 7) or
(CLC_SEX = 2 and
AFTD21 = 8)
Oxygen cost for male respondents with a final stepping stage ofstage 7 and females with a final stepping stage of stage 8  
40.1 CLC_SEX = 1 and AFTD21 = 8 Oxygen cost for male respondents with a final stepping stage ofstage 8  

7. AFTD72 - Aerobic fitness score based onthe modified Canadian Aerobic Fitness Test (mCAFT)

Variable name:
AFTD72

Based on:
HWM_13KG, AFCDELG, AFTD71

Description:
This variable indicates the aerobic fitness score based on themodified Canadian Aerobic Fitness Test (mCAFT).

Note:
Created in the Clinic data collection application. This testwas performed by respondents 6 to 69 years of age.

Source:
The Canadian Physical Activity, Fitness and Lifestyle Approach (3rdEdition, 2004) by the Canadian Society for Exercise Physiology(CSEP)

Table 7
AFTD72 Specifications
Value Condition(s)  Description Notes
999 (AFTD71 = DK, RF, NS) At least one required question was not answered (don'tknow, refusal, not stated) NS
996 (1 < AFCDELG < NA) Population exclusions NA
Round((10 * (17.2 +
(1.29 * AFTD71)–
(0.09 * HWM_13KG)–
(0.18 * CLC_AGE))), 1)
(0 < HWM_13KG < NA) Aerobic fitness score Rounded to integer
999 Else   NA

8. AFTD73 - Aerobic fitness norms forrespondents aged 15 – 69

Variable name:
AFTD73

Based on:
CLC_AGE, CLC_SEX, AFCDELG, AFTD72

Description:
This variable indicates the aerobic fitness norms for respondents15 - 69 based on the modified Canadian Aerobic Fitness Test(mCAFT).

Note:
Created in the Clinic data collection application. This testwas performed by respondents 15 to 69 years of age.
The Canadian Physical Activity, Fitness and Lifestyle Approach (3rdEdition, 2004) provides the following description of the AerobicFitness Norms:
Excellent - aerobic fitness falls within a range that is generallyassociated with optimal health benefits
Very Good- aerobic fitness falls within a range that is generallyassociated with considerable health benefits
Good - aerobic fitness falls within a range that is generallyassociated with many health benefits
Fair - aerobic fitness falls within a range that is generallyassociated with some health benefits but also some health risks
Needs Improvement - aerobic fitness falls within a range that isgenerally associated with considerable health risks

Source:
The Canadian Physical Activity,Fitness and Lifestyle Approach (3rd Edition, 2004) by the CanadianSociety for Exercise Physiology (CSEP)

Table 8
AFTD73 Specifications
Value Condition(s) Description Notes
9 (AFTD72 = DK, RF, NS) At least one required question was not answered (don'tknow, refusal, not stated) NS
6 CLC_AGE < 15 or
(1 < AFCDELG < NA)
Population exclusions NA
0 (CLC_SEX = 1 and
((14 < CLC_AGE < 20) and
(0 < AFTD72 < 436)) or
((19 < CLC_AGE < 30) and
(0 < AFTD72 < 416)) or
((29 < CLC_AGE < 40) and
(0 < AFTD72 < 337)) or
((39 < CLC_AGE < 50) and
(0 < AFTD72 < 319)) or
((49 < CLC_AGE < 60) and
(0 < AFTD72 < 260)) or
((59 < CLC_AGE < 70) and
(0 < AFTD72 < 235))) or
(CLC_SEX = 2 and
((14 < CLC_AGE < 20) and
(0 < AFTD72 < 368)) or
((19 < CLC_AGE < 30) and
(0 < AFTD72 < 350)) or
((29 < CLC_AGE < 40) and
(0 < AFTD72 < 330)) or
((39 < CLC_AGE < 50) and
(0 < AFTD72 < 271)) or
((49 < CLC_AGE < 60) and
(0 < AFTD72 < 246)) or
((59 < CLC_AGE < 70) and
(0 < AFTD72 < 235)))
Needs improvement  
1 (CLC_SEX = 1 and
((14 < CLC_AGE < 20) and
(435 < AFTD72 < 488)) or
((19 < CLC_AGE < 30) and
(415 < AFTD72 < 472)) or
((29 < CLC_AGE < 40) and
(336 < AFTD72 < 401)) or
((39 < CLC_AGE < 50) and
(318 < AFTD72 < 355)) or
((49 < CLC_AGE < 60) and
(259 < AFTD72 < 301)) or
((59 < CLC_AGE < 70) and
(234 < AFTD72 < 287))) or
(CLC_SEX = 2 and
((14 < CLC_AGE < 20) and
(367 < AFTD72 < 395)) or
((19 < CLC_AGE < 30) and
(349 < AFTD72 < 378)) or
((29 < CLC_AGE < 40) and
(329 < AFTD72 < 360)) or
((39 < CLC_AGE < 50) and
(270 < AFTD72 < 319)) or
((49 < CLC_AGE < 60) and
(245 < AFTD72 < 310)) or
((59 < CLC_AGE < 70) and
(234 < AFTD72 < 296)))
Fair  
2 (CLC_SEX = 1 and
((14 < CLC_AGE < 20) and
(487 < AFTD72 < 524)) or
((19 < CLC_AGE < 30) and
(471 < AFTD72 < 506)) or
((29 < CLC_AGE < 40) and
(400 < AFTD72 < 454)) or
((39 < CLC_AGE < 50) and
(354 < AFTD72 < 427)) or
((49 < CLC_AGE < 60) and
(300 < AFTD72 < 365)) or
((59 < CLC_AGE < 70) and
(286 < AFTD72 < 328))) or
(CLC_SEX = 2 and
((14 < CLC_AGE < 20) and
(394 < AFTD72 < 437)) or
((19 < CLC_AGE < 30) and
(377 < AFTD72 < 420)) or
((29 < CLC_AGE < 40) and
(359 < AFTD72 < 401)) or
((39 < CLC_AGE < 50) and
(318 < AFTD72 < 351)) or
((49 < CLC_AGE < 60) and
(309 < AFTD72 < 340)) or
((59 < CLC_AGE < 70) and
(295 < AFTD72 < 328)))
Good  
3 (CLC_SEX = 1 and
((14 < CLC_AGE < 20) and
(523 < AFTD72 < 574)) or
((19 < CLC_AGE < 30) and
(505 < AFTD72 < 556)) or
((29 < CLC_AGE < 40) and
(453 < AFTD72 < 488)) or
((39 < CLC_AGE < 50) and
(426 < AFTD72 < 470)) or
((49 < CLC_AGE < 60) and
(364 < AFTD72 < 418)) or
((59 < CLC_AGE < 70) and
(327 < AFTD72 < 384))) or
(CLC_SEX = 2 and
((14 < CLC_AGE < 20) and
(436 < AFTD72 < 490)) or
((19 < CLC_AGE < 30) and
(419 < AFTD72 < 472)) or
((29 < CLC_AGE < 40) and
(400 < AFTD72 < 454)) or
((39 < CLC_AGE < 50) and
(350 < AFTD72 < 400)) or
((49 < CLC_AGE < 60) and
(339 < AFTD72 < 366)) or
((59 < CLC_AGE < 70) and
(327 < AFTD72 < 358)))
Very good  
4 (CLC_SEX = 1 and
((14 < CLC_AGE < 20) and
(573 < AFTD72 < NA)) or
((19 < CLC_AGE < 30) and
(555 < AFTD72 < NA)) or
((29 < CLC_AGE < 40) and
(487 < AFTD72 < NA)) or
((39 < CLC_AGE < 50) and
(469 < AFTD72 < NA)) or
((49 < CLC_AGE < 60) and
(417 < AFTD72 < NA)) or
((59 < CLC_AGE < 70) and
(383 < AFTD72 < NA))) or
(CLC_SEX = 2 and
((14 < CLC_AGE < 20) and
(489 < AFTD72 < NA)) or
((19 < CLC_AGE < 30) and
(471 < AFTD72 < NA)) or
((29 < CLC_AGE < 40) and
(453 < AFTD72 < NA)) or
((39 < CLC_AGE < 50) and
(399 < AFTD72 < NA)) or
((49 < CLC_AGE < 60) and
(365 < AFTD72 < NA)) or
((59 < CLC_AGE < 70) and
(357 < AFTD72 < NA)))
Excellent  
9 Else   NS

9. AFTD74 - Aerobic fitness norms forrespondents aged less than 15

Variable name:
AFTD74

Based on:
CLC_AGE, AFCDELG, AFTD21, AFTD72

Description:
This variable indicates the aerobic fitness norms for respondentsless than 15 based on the modified Canadian Aerobic Fitness Test(mCAFT).

Note:
Created in the Clinic data collection application. This testwas performed by respondents 6 to 14 years of age.
The Canadian Physical Activity, Fitness and Lifestyle Approach (3rdEdition, 2004) provides the following description of the AerobicFitness Norms:
Excellent - aerobic fitness falls within a range that is generallyassociated with optimal health benefits
Very Good- aerobic fitness falls within a range that is generallyassociated with considerable health benefits
Good - aerobic fitness falls within a range that is generallyassociated with many health benefits
Fair - aerobic fitness falls within a range that is generallyassociated with some health benefits but also some health risks
Needs Improvement - aerobic fitness falls within a range that isgenerally associated with considerable health risks

Source:
The Canadian Physical Activity, Fitness and Lifestyle Approach (3rdEdition, 2004) by the Canadian Society for Exercise Physiology(CSEP)

Table 9
AFTD74 Specifications
Value Condition(s) Description Notes
9 (AFTD72 = DK, RF, NS) At least one required question was not answered (don'tknow, refusal, not stated) NS
6 CLC_AGE > 14 or (1 < AFCDELG < NA) Population exclusions NA
5 CLC_AGE = 6 No standards  
0 AFTD21 = 5 Needs improvement  
1 AFTD21 = 6 Fair  
2 AFTD21 = 7 and (167 < AFTD22 < NA) Good  
3 AFTD21 = 7 and (130 < AFTD22 < 168) Very good  
4 AFTD21 = 7 and (0 < AFTD22 < 131) Excellent  
9 Else   NS

Alcohol use (3 DVs)

1. ALCDDLY - Average Daily AlcoholConsumption

Variable name:
ALCDDLY

Based on:
ALCDWKY

Description:
This variable indicates the average number of drinks the respondentconsumed per day in the week prior to the interview.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents less than 12 years of age and those who did not have atleast one drink in the last 12 months were excluded from thepopulation.

Table 1
ALCDDLY Specifications
Value Condition(s) Description Notes
996 ALCDWKY = NA Population exclusions NA
999 ALCDWKY = NS At least one required question was not answered (don'tknow, refusal, not stated) NS
round((ALCDWKY / 7),1) ALCDWKY < 694 Average daily alcohol consumption Rounded to integer (min: 0; max: 99)

2. ALCDTYP - Type of Drinker

Variable name:
ALCDTYP

Based on:
DHH_AGE, ALC_12, ALC_17

Description:
This variable indicates the type of drinker the respondent is basedon his/her drinking habits.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents less than 12 years of age were excluded from thepopulation.

Table 2
ALCDTYP Specifications
Value Condition(s) Description Notes
6 DHH_AGE < 12 Population exclusion NA
9 (ALC_12 = DK, RF, NS) or (ALC_17 = DK, RF, NS) At least one required question was not answered (don'tknow, refusal, not stated) NS
1 (2 <= ALC_12 < NA) Regular drinker  
2 ALC_12 = 1 Occasional drinker  
3 ALC_17 = 1 Former Drinker  
4 ALC_17 = 2 Never Drank  

3. ALCDWKY - Weekly Consumption

Variable name:
ALCDWKY

Based on:
DHH_AGE, ALC_11, ALC_15A, ALC_15B, ALC_15C, ALC_15D, ALC_15E,ALC_15F, ALC_15G

Description:
This variable indicates the total number of drinks consumed in theweek prior to the interview.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents less than 12 years of age and those who did not have atleast one drink in the past 12 months were excluded from thepopulation.

Table 3
ALCDWKY Specifications
Value Condition(s) Description Notes
996 ALC_11 = 2 or
DHH_AGE < 12
Population exclusions NA
999 (ALC_15A = DK, RF, NS) or
(ALC_15B = DK, RF, NS) or
(ALC_15C = DK, RF, NS) or
(ALC_15D = DK, RF, NS) or
(ALC_15E = DK, RF, NS) or
(ALC_15F = DK, RF, NS) or
(ALC_15G = DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NS
0 ALC_14 = 2 Hasn't had a drink in last week  
ALC_15A +
ALC_15B +
ALC_15C +
ALC_15D +
ALC_15E +
ALC_15F +
ALC_15G
(0 <= ALC_15A < NA) and
(0 <= ALC_15B < NA) and
(0 <= ALC_15C < NA) and
(0 <= ALC_15D < NA) and
(0 <= ALC_15E < NA) and
(0 <= ALC_15F < NA) and
(0 <= ALC_15G < NA)
Number of drinks consumed in past week (min: 0; max: 693)

Anthropometric (23 DVs)

1. ANCDELG - Eligibility for theAnthropometric component

Variable name:
ANCDELG

Based on:
PHC_42C, PHC_42D

Description:
This variable indicates whether the respondent was eligible for theAnthropometric component. As there are multiple reasons to bescreened out of this measure, the prevalence of screen outs byreason should not be based on frequency counts for thisvariable.

Note:
Created in the Clinic Post-Verify process.

Table 1
ANCDELG Specifications
Value Condition(s) Description Notes
9 PHC_42C = 1 and PHC_42D = 1 Not eligible - acute or chronic condition  
1 Else Eligible  

2. HWMD11IN - Standing height (inches)– measured

Variable name:
HWMD11IN

Based on:
PHC_42C, ANCDELG, HWM_11CM

Description:
This variable contains the measured standing height in inches.

Introduced in:
CCHS - Cycle 1.1

Note:
Created in the Clinic data collection application.

Table 2
HWMD11IN Specifications
Value Condition(s) Description Notes
99.6 PHC_42C = 1 or
(ANCDELG > 1 and
ANCDELG < NA)
Population exclusions NA
Round((HWM_11CM * 0.3937), .1) HWM_11CM > 0 and
HWM_11CM < NA
Measured standing height in inches Rounded to one decimal place
99.9 Else   NS

3. HWMD12IN - Sitting height (inches) -measured

Variable name:
HWMD12IN

Based on:
PHC_42C, ANCDELG, HWM_12CM

Description:
This variable contains the measured sitting height in inches.

Note:
Created in the Clinic data collection application.

Table 3
HWMD12IN Specifications
Value Condition(s) Description Notes
99.6 PHC_42C = 1 or
(ANCDELG > 1 and
ANCDELG < NA)
Population exclusions NA
Round((HWM_12CM * 0.3937), .1) HWM_12CM > 0 and
HWM_12CM < NA
Measured sitting height in inches Rounded to one decimal place
99.9 Else   NS

4. HWMD13LB - Weight (pounds) –measured

Variable name:
HWMD13LB

Based on:
PHC_11, PHC_42C, ANCDELG, HWM_13KG

Description:
This variable contains the measured weight in pounds.

Introduced in:
CCHS - Cycle 1.1

Note:
Created in the Clinic data collection application.

Table 4
HWMD13LB Specifications
Value Condition(s) Description Notes
999.6 PHC_11 = 1 or
PHC_42C = 1 or
(ANCDELG > 1 and
ANCDELG < NA)
Population exclusions NA
Round((HWM_13KG * 2.205), .1) HWM_13KG > 0 and
HWM_13KG < NA
Measured weight in pounds Rounded to one decimal place
999.9 Else   NS

5. HWMD14IN - Waist circumference(inches) – measured

Variable name:
HWMD14IN

Based on:
PHC_11, PHC_42C, ANCDELG, HWM_14CM

Description:
This variable contains the waist circumference in inches.

Note:
Created in the Clinic data collection application.
Waist circumference was not measured for pregnant women.

Table 5
HWMD14IN Specifications
Value Condition(s) Description Notes
99.6 PHC_11 = 1 or
PHC_42C = 1 or
(ANCDELG > 1 and
ANCDELG < NA)
Population exclusions NA
Round((HWM_14CM * 0.3937), .1) HWM_14CM > 0 and
HWM_14CM < NA
Waist circumference in inches Rounded to one decimal place
99.9 Else   NS

6. HWMD15IN - Hip circumference (inches)– measured

Variable name:
HWMD15IN

Based on:
PHC_11, PHC_42C, ANCDELG, HWM_15CM

Description:
This variable contains the hip circumference in inches.

Note:
Created in the Clinic data collection application.
Hip circumference was not measured for pregnant women

Table 6
HWMD15IN Specifications
Value Condition(s) Description Notes
99.6 PHC_11 = 1 or
PHC_42C = 1 or
(ANCDELG > 1 and
ANCDELG < NA) or
HWMD15CM = NA
Population exclusions NA
Round((HWM_15CM * 0.3937), .1) HWM_15CM > 0 and
HWM_15CM < NA
Hip circumference in inches Rounded to one decimal place
99.9 Else   NS

7. HWMDBMI - Body Mass Index (BMI)– measured

Variable name:
HWMDBMI

Based on:
PHC_11, PHC_42C, ANCDELG, HWM_13KG, HWMDHTM

Description:
Body Mass Index (BMI) is a comparison of "weight" relative to the"height" of respondents. BMI is calculated by dividing weightin kilograms by height in metres squared.
(BMI = WEIGHT (kilograms) / HEIGHT (metres) SQUARED)

Introduced in:
CCHS - Cycle 1.1

Note:
Created in the Clinic data collection application.
BMI was not calculated for pregnant women.
This BMI classification was created using "measured height" and"measured weight" variables.

Table 7
HWMDBMI Specifications
Value Condition(s) Description Notes
999.99 CLC_SEX = 2 and
(PHC_11 = DK, RF, NS)
Females who did not answer the pregnancy question (don't know,refusal, not stated) NS
999.99 HWM_13KG > NA or
HWMDHTM = NS
Respondents for whom a valid measured height and weight werenot obtained NS
999.96 PHC_11 = 1 or
PHC_42C = 1 or
(1 < ANCDELG < NA)
Population exclusions NA
Round(HWM_13KG /
(HWMDHTM x HWMDHTM), .2)
HWM_13KG < NA and
HWMDHTM < NA
BMI calculated from both measured height and measured weightvalues Rounded to two decimal places

8. HWMDBMIA - BMI classification foradults aged 18 and over (measured) - internationalstandard

Variable name:
HWMDBMIA

Based on:
CLC_AGE, PHC_11, PHC_42C, ANCDELG, HWMDBMI

Description:
This variable assigns adult respondents aged 18 and over (exceptpregnant women) to one of the following categories, according totheir Body Mass Index (BMI): underweight; acceptable weight;overweight; obese class I; obese class II; and, obese class III.Here, the BMI categories are adopted from a body weightclassification system recommended by Health Canada and the WorldHealth Organization (WHO) which has been widely usedinternationally.

Introduced in:
CCHS - Cycle 3.1

Note:
Created in the Clinic data collection application.
According to Health Canada, this BMI classification system can beused as a screening tool to identify weight-related health risks atthe population and individual levels. The following health risksare associated with each of the BMI categories for adults aged 18and over:
normal weight = least health risk;
underweight and overweight = increased health risk;
obese class I = high health risk;
obese class II = very high health risk;
obese class III = extremely high health risk;
At the population level, the BMI classification system can be usedto compare body weight patterns and related health risks within andbetween populations and to establish population trends in bodyweight patterns. The classification should be used with caution atthe individual level because the health risk associated with eachBMI category varies considerably between individuals. Particularcaution should be used when classifying: adults who are naturallyvery lean, very muscular adults, some ethnic and racial groups, andseniors.
This variable excludes female respondents aged 18 and over who werepregnant.

Internet site:
http://www.hc-sc.gc.ca/hpfb-dgpsa/onpp-bppn/weight

Table 8
HWMDBMIA Specifications
Value Condition(s) Description Notes
99 HWMDBMI = NS At least one required question was not answered (don'tknow, refusal, not stated) NS
96 CLC_AGE < 18 or
PHC_11 = 1 or
PHC_42C = 1 or
(ANCDELG > 1 and
ANCDELG < NA)
Population exclusions NA
1 HWMDBMI < 18.50 Underweight  
2 (18.50 <= HWMDBMI <= 24.99) Normal weight  
3 (25.00 <= HWMDBMI <= 29.99) Overweight  
4 (30.00 <= HWMDBMI <= 34.99) Obese - Class I  
5 (35.00 <= HWMDBMI <= 39.99) Obese - Class II  
6 HWMDBMI >= 40.00 Obese - Class III  

Reference: For more detailed information see Canadian Guidelinesfor Body Weight Classification in Adults, Health Canada,2003. These norms are used along with skinfold norms(SFMDS5A) and Waist Circumference norms (HWMDWSTA) to create thebody composition score (SFMDBCA).

9. HWMDBMIK - BMI Classification forChildren Aged 6 to 17 (measured) - CDC BMI-for-age

Variable name:
HWMDBMIK

Based on:
CLC_AGE, PHC_11, PHC_42C, ANCDELG, HWMDBMI

Description:
Body Mass Index (BMI) growth charts can be used beginning at 2years of age. BMI is calculated from weight and heightmeasurements and is used to determine whether an individual'sweight is appropriate for their height. The growth charts consistof a series of percentile curves illustrating the distribution ofmeasurements in U.S. children. Most of the data used toconstruct the charts comes from the National Health and NutritionExamination Survey (NHANES), which has periodically collectedheight and weight data (and other health information) on theAmerican population since the early 1960's.

Note:
Created in the Clinic data collection application.
The following percentiles were selected as cutoff points:
5th percentile and below = underweight;
From the 5th percentile up to and including the 85th percentile =normal;
From the 85th percentile up to and including the 95th percentile =overweight;
Above the 95th percentile = obese.

Table 9
HWMDBMIK Specifications
Value Condition(s) Description Notes
99 HWTDBMI = NS At least one required question was not answered (don'tknow, refusal, not stated) NS
96 CLC_AGE >17 or
PHC_11 = 1 or
PHC_42C = 1 or
(1 < ANCDELG < NA)
Population exclusions NA
1 At or below the 5th percentile for the child's age in days, andsex Underweight  
2 Between the 5th and up to and including the 85th percentile forthe child's age in days, and sex Normal weight  
3 Between the 86th and up to and including the 95th percentilefor the child's age in days, and sex Overweight  
4 Above the 95th percentile for the child's age in days, andsex Obese  

Reference: For more information, please see www.cdc.gov/growthcharts

10. HWMDCOL - BMI Classification forChildren Aged 6 to 17 (Measured) - Cole ClassificationSystem

Variable name:
HWMDCOL

Based on:
CLC_AGE, CLC_SEX, CLC_YOB, CLC_MOB, CLC_DOB, V2_YEAR, V2_MONTH,V2_DAY, PHC_42C, ANCDELG, HWMDBMI

Description:
This variable classifies children aged 6 to 17 as "obese" or"overweight" according to the age-and-sex-specific BMI cut-offpoints as defined by Cole et al. The Cole cut-off points are basedon pooled international data (Brazil, Great Britain, Hong Kong,Netherlands, Singapore, and United States) for BMI and linked tothe internationally accepted adult BMI cut-off points of 25(overweight) and 30 kg/m2 (obese).

Introduced in:
CCHS - Cycle 3.1

Note:
Respondents who do not fall within the categories of "Obese" or"Overweight" (as defined by Cole et al.) have been classified byCCHS as "neither obese nor overweight".
This variable excludes female respondents who were pregnant andrespondents who were 216 months in age, i.e. 18 years old orolder.

Table 10.1
HWMDCOL Temporary Reformat
Value Condition(s) Description Notes
AGET1
 CLC_AGM / 12
CLC_AGM < NA Convert respondent's "age in months" to "age inyears" Rounded to nearest 0.5
CLC_AGM
 Age in months
Interview date converted in months (V2_YEAR, V2_MTH and V2_DAY)- Date of birth converted in months (CLC_YOB, CLC_MOB andCLC_DOB) Create respondent's age in months at time of theinterview (Min: 72; Max: 203)
9999 (CLC_DOB = DK, RF, NS) or
(CLC_MOB = DK, RF, NS) or
(CLC_YOB = DK, RF, NS)
A valid day of birth or month of birth or year of birth is notavailable for the respondent NS
Table 10.2
HWMDCOL Specifications
Value Condition(s) Description Notes
9 HWMDBMI = NS At least one required question was not answered (don'tknow, refusal, not stated) NS
6 CLC_AGE >17 or
PHC_11 = 1 or
PHC_42C = 1 or
(1 < ANCDELG < NA)
Population exclusions NA
2 (AGET1 = 6 and
CLC_SEX = 1 and
(HWMDBMI >= 17.55 and
HWMDBMI < 19.78)) or
(AGET1 = 6 and
CLC_SEX = 2 and
(HWMDBMI >= 17.34 and
HWMDBMI < 19.65)) or
(AGET1 = 6.5 and
CLC_SEX = 1 and
(HWMDBMI >= 17.71 and
HWMDBMI < 20.23)) or
(AGET1 = 6.5 and
CLC_SEX = 2 and
(HWMDBMI >= 17.53 and
HWMDBMI < 20.08)) or
(AGET1 = 7 and
CLC_SEX = 1 and
(HWMDBMI >= 17.92 and
HWMDBMI < 20.63)) or
(AGET1 = 7 and
CLC_SEX = 2 and
(HWMDBMI >= 17.75 and
HWMDBMI < 20.51)) or
(AGET1 = 7.5 and
CLC_SEX = 1 and
(HWMDBMI >= 18.16 and
HWMDBMI < 21.09)) or
(AGET1 = 7.5 and
CLC_SEX = 2 and
(HWMDBMI >= 18.03 and
HWMDBMI < 21.01)) or
(AGET1 = 8 and
CLC_SEX = 1 and
(HWMDBMI >= 18.44 and
HWMDBMI < 21.60)) or
(AGET1 = 8 and
CLC_SEX = 2 and
(HWMDBMI >= 18.35 and
HWMDBMI < 21.57)) or
(AGET1 = 8.5 and
CLC_SEX = 1 and
(HWMDBMI >= 18.76 and
HWMDBMI < 22.17)) or
(AGET1 = 8.5 and
CLC_SEX = 2 and
(HWMDBMI >= 18.69 and
HWMDBMI < 22.18)) or
(AGET1 = 9 and
CLC_SEX = 1 and
(HWMDBMI >= 19.10 and
HWMDBMI < 22.77)) or
(AGET1 = 9 and
CLC_SEX = 2 and
(HWMDBMI >= 19.07 and
HWMDBMI < 22.81)) or
(AGET1 = 9.5 and
CLC_SEX = 1 and
(HWMDBMI >= 19.46 and
HWMDBMI < 23.39)) or
(AGET1 = 9.5 and
CLC_SEX = 2 and
(HWMDBMI >= 19.45 and
HWMDBMI < 23.46)) or
(AGET1 = 10 and
CLC_SEX = 1 and
(HWMDBMI >= 19.84 and
HWMDBMI < 24.00)) or
(AGET1 = 10 and
CLC_SEX = 2 and
(HWMDBMI >= 19.86 and
HWMDBMI < 24.11)) or
(AGET1 = 10.5 and
CLC_SEX = 1 and
(HWMDBMI >= 20.20 and
HWMDBMI < 24.57)) or
(AGET1 = 10.5 and
CLC_SEX = 2 and
(HWMDBMI >= 20.29 and
HWMDBMI < 24.77)) or
(AGET1 = 11 and
CLC_SEX = 1 and
(HWMDBMI >= 20.55 and
HWMDBMI < 25.10)) or
(AGET1 = 11 and
CLC_SEX = 2 and
(HWMDBMI >= 20.74 and
HWMDBMI < 25.42)) or
(AGET1 = 11.5 and
CLC_SEX = 1 and
(HWMDBMI >= 20.89 and
HWMDBMI < 25.58)) or
(AGET1 = 11.5 and
CLC_SEX = 2 and
(HWMDBMI >= 21.20 and
HWMDBMI < 26.05)) or
(AGET1 = 12 and
CLC_SEX = 1 and
(HWMDBMI >= 21.22 and
HWMDBMI < 26.02)) or
(AGET1 = 12 and
CLC_SEX = 2 and
(HWMDBMI >= 21.68 and
HWMDBMI < 26.67)) or
(AGET1 = 12.5 and
CLC_SEX = 1 and
(HWMDBMI >= 21.56 and
HWMDBMI < 26.43)) or
(AGET1 = 12.5 and
CLC_SEX = 2 and
(HWMDBMI >= 22.14 and
HWMDBMI < 27.24)) or
(AGET1 = 13 and
CLC_SEX = 1 and
(HWMDBMI >= 21.91 and
HWMDBMI < 26.84)) or
(AGET1 = 13 and
CLC_SEX = 2 and
(HWMDBMI >= 22.58 and
HWMDBMI < 27.76)) or
(AGET1 = 13.5 and
CLC_SEX = 1 and
(HWMDBMI >= 22.27 and
HWMDBMI < 27.25)) or
(AGET1 = 13.5 and
CLC_SEX = 2 and
(HWMDBMI >= 22.98 and
HWMDBMI < 28.20)) or
(AGET1 = 14 and
CLC_SEX = 1 and
(HWMDBMI >= 22.62 and
HWMDBMI < 27.63)) or
(AGET1 = 14 and
CLC_SEX = 2 and
(HWMDBMI >= 23.34 and
HWMDBMI < 28.57)) or
(AGET1 = 14.5 and
CLC_SEX = 1 and
(HWMDBMI >= 22.96 and
HWMDBMI < 27.98)) or
(AGET1 = 14.5 and
CLC_SEX = 2 and
(HWMDBMI >= 23.66 and
HWMDBMI < 28.87)) or
(AGET1 = 15 and
CLC_SEX = 1 and
(HWMDBMI >= 23.29 and
HWMDBMI < 28.30)) or
(AGET1 = 15 and
CLC_SEX = 2 and
(HWMDBMI >= 23.94 and
HWMDBMI < 29.11)) or
(AGET1 = 15.5 and
CLC_SEX = 1 and
(HWMDBMI >= 23.60 and
HWMDBMI < 28.60)) or
(AGET1 = 15.5 and
CLC_SEX = 2 and
(HWMDBMI >= 24.17 and
HWMDBMI < 29.29)) or
(AGET1 = 16 and
CLC_SEX = 1 and
(HWMDBMI >= 23.90 and
HWMDBMI < 28.88)) or
(AGET1 = 16 and
CLC_SEX = 2 and
(HWMDBMI >= 24.37 and
HWMDBMI < 29.43)) or
(AGET1 = 16.5 and
CLC_SEX = 1 and
(HWMDBMI >= 24.19 and
HWMDBMI < 29.14)) or
(AGET1 = 16.5 and
CLC_SEX = 2 and
(HWMDBMI >= 24.54 and
HWMDBMI < 29.56)) or
(AGET1 = 17 and
CLC_SEX = 1 and
(HWMDBMI >= 24.46 and
HWMDBMI < 29.41)) or
(AGET1 = 17 and
CLC_SEX = 2 and
(HWMDBMI >= 24.70 and
HWMDBMI < 29.69)) or
(AGET1 = 17.5 and
CLC_SEX = 1 and
(HWMDBMI >= 24.73 and
HWMDBMI < 29.70)) or
(AGET1 = 17.5 and
CLC_SEX = 2 and
(HWMDBMI >= 24.85 and
HWMDBMI < 29.84)) or
(AGET1 = 18 and
CLC_SEX = 1 and
(HWMDBMI >= 25.00 and
HWMDBMI < 30.00))or
(AGET1 = 18 and
CLC_SEX = 2 and
(HWMDBMI >= 25.00 and
HWMDBMI < 30.00))
Overweight  
3 (AGET1 = 6 and
CLC_SEX = 1 and
HWMDBMI >= 19.78) or
(AGET1 = 6 and
CLC_SEX = 2 and
HWMDBMI >= 19.65) or
(AGET1 = 6.5 and
CLC_SEX = 1 and
HWMDBMI >= 20.23) or
(AGET1 = 6.5 and
CLC_SEX = 2 and
HWMDBMI >= 20.08) or
(AGET1 = 7 and
CLC_SEX = 1 and
HWMDBMI >= 20.63) or
(AGET1 = 7 and
CLC_SEX = 2 and
HWMDBMI >= 20.51) or
(AGET1 = 7.5 and
CLC_SEX = 1 and
HWMDBMI >= 21.09) or
(AGET1 = 7.5 and
CLC_SEX = 2 and
HWMDBMI >= 21.01) or
(AGET1 = 8 and
CLC_SEX = 1 and
HWMDBMI >= 21.60) or
(AGET1 = 8 and
CLC_SEX = 2 and
HWMDBMI >= 21.57) or
(AGET1 = 8.5 and
CLC_SEX = 1 and
HWMDBMI >= 22.17) or
(AGET1 = 8.5 and
CLC_SEX = 2 and
HWMDBMI >= 22.18) or
(AGET1 = 9 and
CLC_SEX = 1 and
HWMDBMI >= 22.77) or
(AGET1 = 9 and
CLC_SEX = 2 and
HWMDBMI >= 22.81) or
(AGET1 = 9.5 and
CLC_SEX = 1 and
HWMDBMI >= 23.39) or
(AGET1 = 9.5 and
CLC_SEX = 2 and
HWMDBMI >= 23.46) or
(AGET1 = 10 and
CLC_SEX = 1 and
HWMDBMI >= 24.00) or
(AGET1 = 10 and
CLC_SEX = 2 and
HWMDBMI >= 24.41) or
(AGET1 = 10.5 and
CLC_SEX = 1 and
HWMDBMI >= 24.57) or
(AGET1 = 10.5 and
CLC_SEX = 2 and
HWMDBMI >= 24.77) or
(AGET1 = 11 and
CLC_SEX = 1 and
HWMDBMI >= 25.10) or
(AGET1 = 11 and
CLC_SEX = 2 and
HWMDBMI >= 24.42) or
(AGET1 = 11.5 and
CLC_SEX = 1 and
HWMDBMI >= 25.58) or
(AGET1 = 11.5 and
CLC_SEX = 2 and
HWMDBMI >= 26.05) or
(AGET1 = 12 and
CLC_SEX = 1 and
HWMDBMI >= 26.02) or
(AGET1 = 12 and
CLC_SEX = 2 and
HWMDBMI >= 26.67) or
(AGET1 = 12.5 and
CLC_SEX = 1 and
HWMDBMI >= 26.43) or
(AGET1 = 12.5 and
CLC_SEX = 2 and
HWMDBMI >= 27.24) or
(AGET1 = 13 and
CLC_SEX = 1 and
HWMDBMI >= 26.84) or
(AGET1 = 13 and
CLC_SEX = 2 and
HWMDBMI >= 27.76) or
(AGET1 = 13.5 and
CLC_SEX = 1 and
HWMDBMI >= 27.25) or
(AGET1 = 13.5 and
CLC_SEX = 2 and
HWMDBMI >= 28.20) or
(AGET1 = 14 and
CLC_SEX = 1 and
HWMDBMI >= 27.63) or
(AGET1 = 14 and
CLC_SEX = 2 and
HWMDBMI >= 28.57) or
(AGET1 = 14.5 and
CLC_SEX = 1 and
HWMDBMI >= 27.98) or
(AGET1 = 14.5 and
CLC_SEX = 2 and
HWMDBMI >= 28.87) or
(AGET1 = 15 and
CLC_SEX = 1 and
HWMDBMI >= 28.30) or
(AGET1 = 15 and
CLC_SEX = 2 and
HWMDBMI >= 29.11) or
(AGET1 = 15.5 and
CLC_SEX = 1 and
HWMDBMI >= 28.60) or
(AGET1 = 15.5 and
CLC_SEX = 2 and
HWMDBMI >= 29.29) or
(AGET1 = 16 and
CLC_SEX = 1 and
HWMDBMI >= 28.88) or
(AGET1 = 16 and
CLC_SEX = 2 and
HWMDBMI >= 29.43) or
(AGET1 = 16.5 and
CLC_SEX = 1 and
HWMDBMI >= 29.14) or
(AGET1 = 16.5 and
CLC_SEX = 2 and
HWMDBMI >= 29.56) or
(AGET1 = 17 and
CLC_SEX = 1 and
HWMDBMI >= 29.41) or
(AGET1 = 17 and
CLC_SEX = 2 and
HWMDBMI >= 29.69) or
(AGET1 = 17.5 and
CLC_SEX = 1 and
HWMDBMI >= 29.70) or
(AGET1 = 17.5 and
CLC_SEX = 2 and
HWMDBMI >= 29.84) or
(AGET1 = 18 and
CLC_SEX = 1 and
HWMDBMI >= 30.00) or
(AGET1 = 18 and
CLC_SEX = 2 and
HWMDBMI >= 30.00)
Obese  
1 Else Neither overweight nor obese  

Reference: For more information about the Cole BMIclassification system, see Establishing a Standard Definition forChild Overweight and Obesity Worldwide - International survey, byTim J. Cole, Mary C. Bellizzi, Katherine M. Flegal, William H.Dietz, published in British Medical Journal, Volume: 320, May2000.

11. HWMDHTM – Standing height(metres) – measured

Variable name:
HWMDHTM

Based on:
PHC_42C, ANCDELG, HWM_11CM

Description:
This variable indicates the respondent's standing height inmetres.

Introduced in:
CCHS - Cycle 3.1

Table 11
HWMDHTM Specifications
Value Condition(s) Description Notes
9.999 (HWM_11CM = DK, RF, NS) At least one required question was not answered (don'tknow, refusal, not stated) NS
9.996 PHC_42C = 1 or
(1 < ANCDELG < NA)
Population exclusions NA
HWM_11CM / 100 Else Height in metres  

12. HWMDLLN - Leg Length

Variable name:
HWMDLLN

Based on:
PHC_42C, ANCDELG, HWM_11CM, HWM_12CM

Description:
This variable calculates the leg length in centimetres of arespondent as sitting height subtracted from standing height.

Table 12
HWMDLLN Specifications
Value Condition(s) Description Notes
999 (HWM_11CM = DK, RF, NS) or
(HWM_12CM = DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NS
996 PHC_42C = 1 or
(1 < ANCDELG < NA)
Population exclusions NA
HWM_11CM –
HWM_12CM
Else Leg Length  

13. HWMDMAT - Maturity Offset

Variable name:
HWMDMAT

Based on:
ANCDELG, CLC_AGE, CLC_MOB, CLC_SEX, CLC_YOB, PHC_42C, HWM_11CM,HWM_12CM, HWM_13KG, HWMDLLN

Description:
Age at peak height velocity (APHV) is a common bench mark inchildren used to estimate biological age. How far anindividual is from PHV (Maturity Offset) can be predicted using aregression equation including measures of sex, age, height, sittingheight and weight.

Note:
Maturity Offset is calculated for ages 8 to 16 in girls and ages 9to 18 in boys.

Table 13.1
HWMDMAT Temporary Reformat
Value Condition(s) Description Notes
HWMTWHR
100 * (HWM_13KG / HWM_11CM)
(HWM_11CM <> DK, RF, NS) and
(HWM_13KG <> DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NS
AGET3
Round(((mdy(v2_mth, v2_day, v2_year)
- mdy(clc_mob, clc_dob, clc_yob))/365.25), 0.5)
  Calculate respondent's age Rounded to nearest 0.5
Table 13.2
HWMDMAT Specifications
Value Condition(s) Description Notes
99.99 (HWM_11CM = DK, RF, NS) or
(HWM_13KG = DK, RF, NS) or
HWMDLLN = NS or
(CLC_YOB = DK, RF, NS) or
(CLC_MOB = DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NS
99.96 (CLC_SEX = 1 and
(CLC_AGE < 9 or
CLC_AGE > 18)) or
(CLC_SEX = 2 and
(CLC_AGE < 8 or
CLC_AGE > 16)) or
PHC_42C = 1 or
(1 < ANCDELG < NA) or
HWM_11CM = NA or
HWM_12CM = NA or
HWM_13KG = NA
Population exclusions NA
round((-9.236 +
(0.0002708 *
HWMDLLN *
HWM_12CM) +
(-0.001663 *
AGET3 *
HWMDLLN) +
(0.007216 *
AGET3 *
HWM_12CM) +
(0.02292 *
HWMTWHR)),
0.01)
CLC_SEX = 1 and
(CLC_AGE > 8 and
CLC_AGE < 19)
Maturity offset for males  
round((-9.376+
(0.0001882 *
HWMDLLN *
HWM_12CM)) +
(0.0022*
AGET3 *
HWMDLLN) +
(0.005841 *
AGET3 *
HWM_12CM) -
 (0.002658 *
AGET3 *
HWM_13KG) +
 (0.07693 *
HWMTWHR)),
0.01)
CLC_SEX = 2 and
(CLC_AGE > 7 and
CLC_AGE < 17)
Maturity offset for females  

Reference: For more information on Maturity Offset please see"An assessment of maturity from anthropometric measurements" byMirwald et al. 2001 in the Official Journal of the American Collegeof Sports Medicine.

14. HWMDWSTA - Waist CircumferenceNorms

Variable name:
HWMDWSTA

Based on:
CLC_SEX, PHC_42C, ANCDELG, HWM_14CM, HWMDBMI

Description:
Waist circumference (WC) is an important indicator of health riskassociated with abdominal obesity. Sex-specific cut-offpoints have been established to identify risks associated withexcess abdominal fat. A WC above these points is associatedwith an increased health risk. The measurement should be usedamong those with Body Mass Indexes (BMIs) between 18.5 and 34.9, toidentify additional risk. For BMIs > 35.0, the WCmeasurement does not provide additional information on healthrisk.

Note:
Created in the Clinic data collection application. Thesenorms are for respondents 15 to 69 years of age.
These norms are used along with skinfold norms (SFMDS5A) and BMI(HWMDBMI) to create the body composition score (SFMDBCA).

Table 14
HWMDWSTA Specifications
Value Condition(s) Description Notes
9 (HWM_14CM = DK, RF, NS) or
HWMDBMI = NS
At least one required question was not answered (don'tknow, refusal, not stated) NS
6 CLC_AGE < 15 or
CLC_AGE > 69 or
PHC_42C = 1 or
(1 < ANCDELG < NA) or
HWM_14CM = NA
Population exclusions NA
0 (29.99 < HWMDBMI < NA) and
((CLC_SEX = 1 and
(101.0 < HWM_14CM < NA)) or
(CLC_SEX = 2 and
(87.0 < HWM_14CM < NA)))
Score of 0 Needs improvement
1 (18.49 < HWMDBMI < 30.0) and
((CLC_SEX = 1 and
(101.0 < HWM_14CM < NA)) or
(CLC_SEX = 2 and
(79.9 < HWM_14CM < 87.1)))
Score of 1 Fair
2 (29.99 < HWMDBMI < NA) and
((CLC_SEX = 1 and
(93.9 < HWM_14CM < 101.1)) or
((CLC_SEX = 2 and
(79.9 < HWM_14CM < 87.1)))
Score of 2 Good
3 (CLC_SEX = 1 and
((0 < HWMDBMI < 18.50) or
((18.49 < HWMDBMI < 30.00) and
(93.9 < HWM_14CM < 101.1)))) or
(CLC_SEX = 2 and
((0 < HWMDBMI < 18.50) or
((18.49 < HWMDBMI < 30.00) and
(79.9 < HWM_14CM < 87.1))))
Score of 3 Very good
4 (CLC_SEX = 1 and
(0 < HWM_14CM < 94.0)) or
(CLC_SEX = 2 and
(0 < HWM_14CM < 80.0))
Score of 4 Excellent

Reference: For more information, please see Canadian Guidelinesfor Body Weight Classification, Health Canada, 2003, and TheCanadian Physical Activity, Fitness and Lifestyle Approach (3rdEdition, 2004) by the Canadian Society for Exercise Physiology(CSEP).

15. HWMDWTH - Waist to hipratio

Variable name:
HWMDWTH

Based on:
PHC_11, PHC_42C, ANCDELG, HWM_14CM, HWM_15CM

Description:
This variable calculates thewaist-to-hip ratio of the respondent.

Note:
Created in the Clinic data collection application.

Table 15
HWMDWTH Specifications
Value Condition(s) Description Notes
99.99 HWM_14CM = DK, RF, NS or
HWM_15CM = DK, RF, NS
At least one required question was not answered
(don't know, refusal, not stated)
NS
99.96 PHC_11 = 1 or
(PHC_12 > 12 and
PHC_12 < NA) or
PHC_42C = 1 or
(ANCDELG > 1 and
ANCDELG < NA)
Population exclusions NA
Round((HWM_14CM /
HWM_15CM), .01)
Else Waist to hip ratio  

16. SFMDBCA - Body CompositionNorms

Variable name:
SFMDBCA

Based on:
CLC_AGE, CLC_SEX, HWM_14CM, HWMDBMI, HWMDWSTA, SFMDS5A

Description:
For respondents aged 15-69, the body composition score isinterpreted based on ratings from the Canadian Physical Activity,Fitness and Lifestyle Approach (CPAFLA). There are currently nostandards from which to interpret the score for respondents aged6-14 and 70-79.

Note:
Created in the Clinic data collection application. This variableapplies to respondents 15 to 69 years of age.

Table 16.1
SFMDBCA Temporary Reformat
Value
PTS1
Condition(s) Description Notes

Round((
HWMDWSTA * 1.5 +
SFMDS5A) / 2.5, .1)

(0 < HWMDBMI < NA) and
(SFMDS5A = 0, 1, 2, 3, 4) and
(HWMDWSTA = 0, 1, 2, 3, 4)

Calculation for body composition score given all
three measures, i.e., Body Mass Index, Waist
Circumference, and Sum of Five Skinfolds

Rounded to 1
decimal place

SFMDBCA

(0 < HWMDBMI < NA) and
(SFMDS5A = 0, 1, 2, 3, 4) and
(HWMDWSTA = DK, RF, NS)

Value for body composition score given Body
Mass Index and Sum of Five Skinfolds only (no
Waist Circumference)

 

HWMDWSTA

(0 < HWMDBMI < NA) and
(HWMDWSTA = 0, 1, 2, 3, 4) and
(SFMDS5A = DK, RF, NS)

Value for body composition score given Body
Mass Index and Waist Circumference only (no
Sum of Five Skinfolds)

 

1

((32.49 < HWMDBMI < 35.00) and
(SFMDS5A = DK, RF, NS) and
(HWMDWSTA = DK, RF, NS)) or
(CLC_SEX = 1 and
(HWMDBMI = DK, RF, NS) and
(SFMDS5A = DK, RF, NS) and
(101.0 < HWM_14CM < NA)) or
(CLC_SEX = 2 and
(HWMDBMI = DK, RF, NS) and
(SFMDS5A = DK, RF, NS) and
(87.0 < HWM_14CM < NA))

Value for body composition score given Body
Mass Index (between 32.49 and 35.00) only (no
Waist Circumference or Sum of Five Skinfolds)
and for males given Waist Circumference greater
than 101.0 cm only (no BMI, no Sum of Five
Skinfolds) and for females given Waist
Circumference greater than 87.0 cm only (no
BMI, no Sum of Five Skinfolds)

 

2

(29.99 < HWMDBMI < 32.50) and
(SFMDS5A = DK, RF, NS) and
(HWMDWSTA = DK, RF, NS)

Value for body composition score given Body
Mass Index (between 29.99 and 32.50) only (no
Waist Circumference or Sum of Five Skinfolds)

 

3

((0 < HWMDBMI < 18.50) or
(24.99 < HWMDBMI < 30.00)) and
(SFMDS5A = DK, RF, NS) and
(HWMDWSTA = DK, RF, NS) or
(CLC_SEX = 1 and
(HWMDBMI = DK, RF, NS) and
(SFMDS5A = DK, RF, NS) and
(93.9 < HWM_14CM < 101.1)) or
(CLC_SEX = 2 and
(HWMDBMI = DK, RF, NS) and
(SFMDS5A = (DK, RF, NS) and
(79.9 < HWM_14CM < 87.1))

Value for body composition score given Body
Mass Index (between 0 and 18.50 and between
24.99 and 30.00) only (no Waist Circumference
or Sum of Five Skinfolds) and for males given
Waist Circumference between 93.9 and 101.1
cm only (no BMI, no Sum of Five Skinfolds) and
for females given Waist Circumference between
79.9 and 87.1 cm only (no BMI, no Sum of Five Skinfolds)

 

4

((18.49 < HWMDBMI < 25.00) and
(SFMDS5A = DK, RF, NS) and
(HWMDWSTA = (DK, RF, NS)) or
(CLC_SEX = 1 and
(HWMDBMI = DK, RF, NS) and
(SFMDS5A = DK, RF, NS) and
(0 < HWM_14CM < 94.0)) or
(CLC_SEX = 2 and
(HWMDBMI = DK, RF, NS) and
(SFMDS5A = DK, RF, NS) and
(0 < HWM_14CM < 80.0))

Value for body composition score given Body Mass Index (between18.49 and 25.00) only (no Waist Circumference or Sum of FiveSkinfolds) and for males given Waist Circumference less than 94.0cm only (no BMI, no Sum of Five Skinfolds) and for females givenWaist Circumference less than 80.0 cm only (no BMI, no Sum of FiveSkinfolds)

 

5

Else

   
Table 16.2
HWMDWTH Specifications
Value Condition(s) Description Notes
6 (CLC_AGE < 15 or
CLC_AGE > 69) or
(HWM_14CM = NA and
HWMDBMI = NA and
HWMDWSTA = NA and
SFMDS5A = NA)
Population exclusions NA
9 HWM_14CM > NA and
HWMDBMI = NS and
HWMDWSTA = NS and
SFMDS5A = NS
At least one required question was not answered (don'tknow, refusal, not stated) NS
0 (0 <= PTS1 < 0.5) Needs Improvement. Respondent's Body Composition Score fallswithin a range that is generally associated with considerablehealth risk  
1 (0.4 < PTS1 < 1.5) Fair. Respondent's Body Composition Score falls within a rangethat is generally associated with some health risk  
2 (1.4 < PTS1 < 2.5) Good. Respondent's Body Composition Score falls within a rangethat is generally associated with many health benefits  
3 (2.4 < PTS1 < 3.5) Very Good. Respondent's Body Composition Score falls within arange that is generally associated with considerable healthbenefits  
4 (3.4 < PTS1 < 5.0) Excellent. Respondent's Body Composition Score falls within arange that is generally associated with optimal healthbenefits  
5 PTS1 > 4.9 There are currently no standards with which to interpret theBody Composition Score  

Reference: This variable uses the sum of five skinfolds norm(SFMDS5A), the waist circumference norms (HWMDWSTA) and the BMInorms (HWMDBMIA) to create a body composition score. Thescore is calculated based on an equation if all three norms areavailable. If not, a score is assigned based on the availablemeasures, and according to the CPAFLA approach.

17. SFMDBSA - Biceps SkinfoldAverage

Variable name:
SFMDBSA

Based on:
PHC_11, PHC_12, PHC_42D, ANCDELG, HWMDBMI, SFM_12, SFM_22,SFM_32

Description:
This variable indicates the average of the biceps skinfoldmeasurements in millimetres.

Note:
Created in the Clinic data collection application.

This derived variable is created based on skinfold measurementsfrom appropriately selected respondents who had at least onemeasurement taken. Two sets of measurements are preferred;however, if only one measurement was taken then the derivedvariable will equal the actual measurement. If twomeasurements were taken and the difference between the twomeasurements was less than .5 mm then the derived variable will bethe average of the two measurements. If the differencebetween the above-mentioned two measurements was greater than .4 mmthen a third measurement was taken. If two of the threemeasurements  were within .4 mm then those two measurementswill be used to create the derived variable. If all threemeasurements differ by more than .4 mm then the derived variablewill be the average of the three measurements.

Table 17
SFMDBSA Specifications
Value Condition(s) Description Notes
99.6

PHC_11 = 1 or
(12 < PHC_12 < NA) or
PHC_42D = 1 or
(1 < ANCDELG < NA) or
(29.99 < HWMDBMI < NA)

Population exclusions NS
99.9 (SFM_12 = DK, RF, NS) and
(SFM_22 = DK, RF, NS) and
(SFM_32 = DK, RF, NS)
At least one required question was not
answered (don't know, refusal, not stated)
NA
  Calculate an average using the two
skinfold measurements that are different by 0.4 mm or less
   

18. SFMDICA - Iliac Crest SkinfoldAverage

Variable name:
SFMDICA

Based on:
PHC_11, PHC_12, PHC_42D, ANCDELG, HWMDBMI, SFM_14, SFM_24,SFM_34

Description:
This variable indicates the average of the iliac crest skinfoldmeasurements in millimetres.

Note:
Created in the Clinic data collection application.

This derived variable is created based on skinfold measurementsfrom appropriately selected respondents who had at least onemeasurement taken. Two sets of measurements are preferred;however, if only one measurement is taken then the derived variablewill equal the actual measurement. If two measurements aretaken and the difference between the two measurements is less than.5 mm then the derived variable will be the average of the twomeasurements. If the difference between the above-mentionedtwo measurements is greater than .4 mm then a third measurement istaken. If two of the three measurements are within .4 mm thenthose two measurements will be used to create the derivedvariable. If all three measurements differ by more than .4 mmthen the derived variable will be the average of the threemeasurements.

Table 18
SFMDICA Specifications
Value Condition(s) Description Notes
99.6

PHC_11 = 1 or
(12 < PHC_12 < NA) or
PHC_42D = 1 or
(1 < ANCDELG < NA) or
(29.99 < HWMDBMI < NA)

Population exclusions NS
99.9 (SFM_14 = DK, RF, NS) and
(SFM_24 = DK, RF, NS) and
(SFM_34 = DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NA
  Calculate an average using the two
skinfold measurements that are different by 0.4 mm or less
   

19. SFMDMCA - Medial Calf SkinfoldsAverage

Variable name:
SFMDMCA

Based on:
PHC_11, PHC_12, PHC_42D, ANCDELG, HWMDBMI, SFM_15, SFM_25,SFM_35

Description:
This variable indicates the average of the medial calf skinfoldmeasurements in millimetres.

Note:
Created in the Clinic data collection application.

This derived variable is created based on skinfold measurementsfrom appropriately selected respondents who had at least onemeasurement taken. Two sets of measurements are preferred;however, if only one measurement was taken then the derivedvariable will equal the actual measurement. If twomeasurements were taken and the difference between the twomeasurements was less than .5 mm then the derived variable will bethe average of the two measurements. If the differencebetween the above-mentioned two measurements was greater than .4 mmthen a third measurement was taken. If two of the threemeasurements were within .4 mm then those two measurements will beused to create the derived variable. If all threemeasurements differ by more than .4 mm then the derived variablewill be the average of the three measurements.

Table 19
SFMDMCA Specifications
Value Condition(s) Description Notes
99.6

PHC_11 = 1 or
(12 < PHC_12 < NA) or
PHC_42D = 1 or
(1 < ANCDELG < NA) or
(29.99 < HWMDBMI < NA)

Population exclusions NS
99.9 (SFM_15 = DK, RF, NS) and
(SFM_25 = DK, RF, NS) and
(SFM_35 = DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NA
  Calculate an average using the two skinfold measurements thatare different by 0.4 mm or less    

20. SFMDS5 - Sum of 5 SkinfoldMeasurements

Variable name:
SFMDS5

Based on:
PHC_11, PHC_12, PHC_42D, ANCDELG, HWMDBMI, SFMDBSA, SFMDICA,SFMDMCA, SFMDSSA, SFMDTSA

Description:
This variable indicates the sum of 5 average skinfoldsmeasurements:
Triceps
Biceps
Subscapular
Iliac Crest
Medial Calf

Note:
Created in the Clinic data collection application.

Skinfold measurements are used to estimate general fatness andthe distribution of subcutaneous adipose tissue. The principlebehind this technique is that the amount of subcutaneous fat (fatthat lies directly beneath the skin) is proportional to the totalamount of body fat. Both too much fat and too little fat isassociated with increased health risk.

Table 20
SFMDS5 Specifications
Value Condition(s) Description Notes
999.6

PHC_11 = 1 or
(12 < PHC_12 < NA) or
PHC_42D = 1 or
(1 < ANCDELG < NA) or
(29.99 < HWMDBMI < NA)

Population exclusions NS
999.9 SFMDBSA = NS or
SFMDICA = NS or
SFMDMCA = NS or
SFMDSSA = NS or
SFMDTSA = NS
At least one required question was not answered (don'tknow, refusal, not stated) NA
SFMDBSA +
SFMDICA +
SFMDMCA +
SFMDSSA +
SFMDTSA
Else Sum of five average skinfold measurements  

21. SFMDS5A - Sum of 5 SkinfoldsMeasurements - Norms (ages 15-69)

Variable name:
SFMDS5A

Based on:
CLC_AGE, CLC_SEX, HWMDBMI, SFMDS5

Description:
These norms are intended to be used to calculate a Body CompositionScore which uses a combination of Body Mass Index, WaistCircumference, and Sum of Five Skinfolds as published by theCanadian Physical Activity, Fitness and Lifestyle Approach 3rdEdition. This derived variable calculates the points assignedfor the Sum of Five Skinfolds which will contribute to the BodyComposition Score.

Note:
Created in the Clinic data collection application. This variableapplies to respondents 15 to 69 years of age.

Table 21
SFMDS5A Specifications
Value Condition(s) Description Notes
6 CLC_AGE < 15 or
CLC_AGE > 69 or
HWMDBMI = NA or
SFMDS5 = NA
Population exclusions NA
9 HWMDBMI = NS or
SFMDS5 = NS
At least one required question was not answered (don'tknow, refusal, not stated) NS
0 (CLC_SEX = 1 and
HWMDBMI > 34.99 and
SFMDS5 > 77.0) or
(CLC_SEX = 2 and
HWMDBMI > 34.99 and
SFMDS5 > 113.0)
Score of 0 Needs improvement
1 (CLC_SEX = 1 and
(32.49 < HWMDBMI < 35.00) and
(77.0 < SFMDS5 < NA)) or
(CLC_SEX = 2 and
(32.49 < HWMDBMI < 35.00) and
(113.0 < SFMDS5 < NA))
Score of 1 Fair
2 (CLC_SEX = 1 and
((0 < HWMDBMI < 32.50) and
(77.0 < SFMDS5 < NA)) or
((32.49 < HWMDBMI < 35.00) and
(53.9 < SFMDS5 < 77.1))) or
(CLC_SEX = 2 and
((0 < HWMDBMI < 32.50) and
(113.0 < SFMDS5 < NA)) or
((32.49 < HWMDBMI < 35.00) and
(82.9 < SFMDS5 < 113.1)))
Score of 2 Good
3 (CLC_SEX = 1 and
(0 < HWMDBMI < 18.50) and
((0 < SFMDS5 < 25.0) or
(55.0 < SFMDS5 < 77.1)) or
((18.49 < HWMDBMI < 32.50) and
(53.9 < SFMDS5 < 77.1))) or
(CLC_SEX = 2 and
(0 < HWMDBMI < 18.50) and
((0 < SFMDS5 < 46.0) or
(84.0 < SFMDS5 < 113.1)) or
((18.49 < HWMDBMI < 32.50) and
(82.9 < SFMDS5 < 113.1)))
Score of 3 Very good
4 (CLC_SEX = 1 and
((0 < HWMDBMI < 18.50) and
(24.9 < SFMDS5 < 55.1)) or
((18.49 < HWMDBMI < NA) and
(0 < SFMDS5 < 54.0))) or
 (CLC_SEX = 2 and
((0 < HWMDBMI < 18.50) and
(45.9 < SFMDS5 < 84.1)) or
((18.49 < HWMDBMI < NA) and
(0 < SFMDS5 < 83.0)))
Score of 4 Excellent

Reference: These norms are used along with BMI norms (HWMDBMI)and Waist Circumference norms (HWMDWSTA) to create the bodycomposition score (SFMDBCA).

22. SFMDSSA - Subscapular SkinfoldsAverage

Variable name:
SFMDSSA

Based on:
PHC_11, PHC_12, PHC_42D, ANCDELG, HWMDBMI, SFM_13, SFM_23,SFM_33

Description:
This variable indicates the average of the subscapular skinfoldmeasurements in millimetres.

Note:
Created in the Clinic data collection application.

This derived variable is created based on skinfold measurementsfrom appropriately selected respondents who had at least onemeasurement taken. Two sets of measurements are preferred;however, if only one measurement was taken then the derivedvariable will equal the actual measurement. If twomeasurements were taken and the difference between the twomeasurements was less than .5 mm then the derived variable will bethe average of the two measurements. If the differencebetween the above-mentioned two measurements was greater than .4 mmthen a third measurement was taken. If two of the threemeasurements were within .4 mm then those two measurements will beused to create the derived variable. If all threemeasurements differ by more than .4 mm then the derived variablewill be the average of the three measurements.

Table 22
SFMDSSA Specifications
Value Condition(s) Description Notes
99.6 PHC_11 = 1 or
(12 < PHC_12 < NA) or
PHC_42D = 1 or
(1 < ANCDELG < NA) or
(29.99 < HWMDBMI < NA)
Population exclusions NA
99.9 (SFM_13 = DK, RF, NS) and
(SFM_23 = DK, RF, NS) and
(SFM_33 = DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NS
  Calculate an average using the two
skinfold measurements that are different by 0.4 mm or less
   

23. SFMDTSA - Triceps SkinfoldsAverage

Variable name:
SFMDTSA

Based on:
PHC_11, PHC_12, PHC_42D, ANCDELG, HWMDBMI, SFM_11, SFM_21,SFM_31

Description:
This variable indicates the average of the triceps skinfoldmeasurements in millimetres.

Note:
Created in the Clinic data collection application.

This derived variable is created based on skinfold measurementsfrom appropriately selected respondents who had at least onemeasurement taken. Two sets of measurements are preferred;however, if only one measurement was taken then the derivedvariable will equal the actual measurement. If twomeasurements were taken and the difference between the twomeasurements was less than .5 mm then the derived variable will bethe average of the two measurements. If the differencebetween the above-mentioned two measurements was greater than .4 mmthen a third measurement was taken. If two of the threemeasurements were within .4 mm then those two measurements will beused to create the derived variable. If all threemeasurements differ by more than .4 mm then the derived variablewill be the average of the three measurements.

Table 23
SFMDTSA Specifications
Value Condition(s) Description Notes
99.6 PHC_11 = 1 or
(12 < PHC_12 < NA) or
PHC_42D = 1 or
(1 < ANCDELG < NA) or
(29.99 < HWMDBMI < NA)
Population exclusions NA
99.9 (SFM_11 = DK, RF, NS) and
(SFM_21 = DK, RF, NS) and
(SFM_31 = DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NS
  Calculate an average using the two
skinfold measurements that are different by 0.4 mm or less
   

Blood Pressure (20 DVs)

1. BPMD160 - Type of problem - firstset

Variable name:
BPMD160

Based on:
BPM_110, BPM_101A, BPM_111A,BPM_111B, BPM_112A, BPM_113A, BPM_113B, BPM_113C, BPM_113D,BPM_113E, BPM_121A, BPM_121B, BPM_122A, BPM_123A, BPM_123B,BPM_123C, BPM_123D, BPM_123E, BPM_131A, BPM_131B, BPM_132A,BPM_133A, BPM_133B, BPM_133C, BPM_133D, BPM_133E, BPM_141A,BPM_141B, BPM_142A, BPM_143A, BPM_143B, BPM_143C, BPM_143D,BPM_143E, BPM_151A, BPM_151B, BPM_152A, BPM_153A, BPM_153B,BPM_153C, BPM_153D, BPM_153E

Description:
This variable indicates the type of error that occurred for thefirst set of resting blood pressure and heart rate

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available onrequest.
The first measures of the set are dropped prior to deriving thisvariable.
The following is a description of the possible error types:

  1. Three or more measurement errors
  2. The range of systolic blood pressure measurements exceeds 30millimetres of Mercury (mmHg)
  3. The range of diastolic blood pressure measurements exceeds 20millimetres of Mercury (mmHg)
  4. The range of heart rate measurements exceeds 30 beats perminute (bpm)

2. BPMD161 - Average systolic bloodpressure - first set

Variable name:
BPMD161

Based on:
BPM_111A, BPM_111B, BPM_121A,BPM_121B, BPM_131A, BPM_131B, BPM_141A, BPM_141B, BPM_151A,BPM_151B, BPM_160

Description:
This variable indicates the average resting systolic blood pressurefor the first set of blood pressure measurements.
Blood pressure is measured in millimetres of Mercury (mmHg).

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available uponrequest.
The first measure of the set is dropped prior to deriving thisvariable.

3. BPMD162 - Average diastolic bloodpressure - first set

Variable name:
BPMD162

Based on:
BPM_111A, BPM_111B, BPM_121A, BPM_121B, BPM_131A, BPM_131B,BPM_141A, BPM_141B, BPM_151A, BPM_151B, BPM_160

Description:
This variable indicates the average resting diastolic bloodpressure for the first set of blood pressure measurements.
Blood pressure is measured in millimetres of Mercury (mmHg).

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available uponrequest.

The first measure of the set is dropped prior to deriving thisvariable.

4. BPMD163 - Average resting heart rate- first set

Variable name:
BPMD163

Based on:
BPM_112, BPM_122, BPM_132,BPM_142, BPM_152, BPM_160

Description:
This variable indicates the average resting heart rate for thefirst set of heart rate measurements. Heart rate is measured inbeats per minute (bpm).

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available uponrequest.
The first measure of the set is dropped prior to deriving thisvariable.

5. BPMD260 - Type of problem - secondset

Variable name:
BPMD260

Based on:
BPM_110, BPM_210, BPM_101A,BPM_111A, BPM_201A, BPM_211A, BPM_211B, BPM_212, BPM_213A,BPM_213B, BPM_213C, BPM_213D, BPM_213E, BPM_221A, BPM_221B,BPM_222, BPM_223A, BPM_223B, BPM_223C, BPM_223D, BPM_223E,BPM_231A, BPM_231B, BPM_232, BPM_233A, BPM_233B, BPM_233C,BPM_233D, BPM_233E, BPM_241A, BPM_241B, BPM_242, BPM_243A,BPM_243B, BPM_243C, BPM_243D, BPM_243E, BPM_251A, BPM_251B,BPM_252, BPM_253A, BPM_253B, BPM_253C, BPM_253D, BPM_253E

Description:
This variable indicates the type of error that occurred for thesecond set of resting blood pressure and heart rate
measurements.

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available uponrequest.
The first measures of the set are dropped prior to deriving thisvariable.
The following is a description of the possible error types:

  1. Three or more measurement errors
  2. The range of systolic blood pressure measurements exceeds 30millimetres of Mercury (mmHg)
  3. The range of diastolic blood pressure measurements exceeds 20millimetres of Mercury (mmHg)
  4. The range of heart rate measurements exceeds 30 beats perminute (bpm)

6. BPMD261 - Average systolic bloodpressure - second set

Variable name:
BPMD261

Based on:
BPM_211A, BPM_211B, BPM_221A,BPM_221B, BPM_231A, BPM_231B, BPM_241A, BPM_241B, BPM_251A,BPM_251B, BPM_260

Description:
This variable indicates the average resting systolic blood pressurefor the second set of blood pressure measurements. Blood pressureis measured in millimetres of Mercury (mmHg).

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available uponrequest.
The first measure of the set is dropped prior to deriving thisvariable.

7. BPMD262 - Average diastolic bloodpressure - second set

Variable name:
BPMD262

Based on:
BPM_211A, BPM_211B, BPM_221A,BPM_221B, BPM_231A, BPM_231B, BPM_241A, BPM_241B, BPM_251A,BPM_251B,BPM_260

Description:
This variable indicates the average resting diastolic bloodpressure for the second set of blood pressure measurements. Bloodpressure is measured in millimetres of Mercury (mmHg).

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available uponrequest.
 The first measure of the set is dropped prior to derivingthis variable.

8. BPMD263 - Average resting heart rate- second set

Variable name:
BPMD263

Based on:
BPM_212, BPM_222, BPM_232,BPM_242, BPM_252, BPM_260

Description:
This variable indicates the average resting heart rate for thesecond set of heart rate measurements. Heart rate is measured inbeats per minute (bpm).

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available uponrequest.
The first measure of the set is dropped prior to deriving thisvariable.

9. BPMD360 - Type of problem - thirdset

Variable name:
BPMD360

Based on:
BPM_110, BPM_210, BPM_310,BPM_101A, BPM_111A, BPM_201A, BPM_301A, BPM_311A, BPM_311B,BPM_312, BPM_313A, BPM_313B, BPM_313C, BPM_313D, BPM_313E, BPM_321A, BPM_321B, BPM_322, BPM_323A, BPM_323B,BPM_323C, BPM_323D, BPM_323E, BPM_331A, BPM_331B, BPM_332,BPM_333A, BPM_333B, BPM_333C, BPM_333D, BPM_333E, BPM_341A,BPM_341B, BPM_342, BPM_343A, BPM_343B, BPM_343C, BPM_343D,BPM_343E, BPM_351A, BPM_351B, BPM_352, BPM_353A, BPM_353B,BPM_353C, BPM_353D, BPM_353E, BPM_360

Description:
This variable indicates the type of error that occurred for thethird set of resting blood pressure and heart rate

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available uponrequest.
The first measures of the set are dropped prior to deriving thisvariable.
The following is a description of the possible error types:

  1. Three or more measurement errors
  2. The range of systolic blood pressure measurements exceeds 30millimetres of Mercury (mmHg)
  3. The range of diastolic blood pressure measurements exceeds 20millimetres of Mercury (mmHg)
  4. The range of heart rate measurements exceeds 30 beats perminute (bpm)

10. BPMD361 - Average systolic bloodpressure - third set

Variable name:
BPMD361

Based on:
BPM_311A, BPM_311B, BPM_321A,BPM_321B, BPM_331A, BPM_331B, BPM_341A, BPM_341B, BPM_351A,BPM_351B

Description:
This variable indicates the average resting systolic blood pressurefor the third set of blood pressure measurements.
Blood pressure is measured in millimetres of Mercury (mmHg).

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available uponrequest.

11. BPMD362 - Average diastolic bloodpressure - third set

Variable name:
BPMD362

Based on:
BPM_311A, BPM_311B, BPM_321A,BPM_321B, BPM_331A, BPM_331B, BPM_341A, BPM_341B, BPM_351A,BPM_351B

Description:
This variable indicates the average resting diastolic bloodpressure for the third set of blood pressure measurements. Blood pressure is measured in millimetres of Mercury (mmHg).

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available uponrequest.
The first measure of the set is dropped prior to deriving thisvariable.

12. BPMD363 - Average resting heart rate- third set

Variable name:
BPMD363

Based on:
BPM_312, BPM_322, BPM_332,BPM_342, BPM_352

Description:
This variable indicates the average resting heart rate for thethird set of heart rate measurements. Heart rate is measured inbeats per minute (bpm).

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available uponrequest.
 The first measure of the set is dropped prior to derivingthis variable.

13. BPMDBPA - Blood pressure norms forrespondents 18 or older (Prevalence)

Variable name:
BPMDBPA

Based on:
CLC_AGE, BPM_314, BPM_315

Description:
This variable indicates the blood pressure norm for respondentsmore than 17 years of age based on the average prevalence bloodpressure measurement.

Note:
Created during processing.
The SAS code used to derive this variable is available uponrequest.
The Canadian Coalition for High Blood Pressure Prevention andControl, 1994 provides the following description of
blood pressure norms:
Category 1 - Within the acceptable range
Category 2 - Acceptable, but at the high end of the acceptablerange
Category 3 - Above the acceptable range
Category 4 - Moderately high
Category 5 - High
Category 6 - Very high

14. BPMDBPK - Blood pressure norms forrespondents less than 18 (Prevalence)

Variable name:
BPMDBPK

Based on:
BPM_314, BPM_315, CLC_SEX,CLC_AGE, HWM_11

Description:
This variable indicates the blood pressure norms for respondentsless than 18 years of age based on the average prevalence bloodpressure measurement.

Note:
Created during processing.
The SAS code used to derive this variable is available uponrequest.
The Fourth Report on the Diagnosis, Evaluation, and Treatment ofHigh Blood Pressure in Children and Adolescents, 2004 provides thefollowing description of blood pressure norms:
Category 1 - Normal
Category 2 - Normal but at the high end of the normal range
Category 3 - High
Category 4 - Very high

15. BPMDPBPD - Final average diastolicblood pressure (Prevalence)

Variable name:
BPMDPBPD

Based on:
BPM_111A, BPM_111B, BPM_112,BPM_121A, BPM_121B, BPM_122, BPM_131A, BPM_131B, BPM_132, BPM_141A,BPM_141B, BPM_142, BPM_151A, BPM_151B, BPM_152, BPM_160, BPM_161,BPM_162, BPM_163, BPM_211A, BPM_211B, BPM_212, BPM_221A, BPM_221B,BPM_222, BPM_231A, BPM_231B, BPM_232, BPM_241A, BPM_241B, BPM_242,BPM_251A, BPM_251B, BPM_252, BPM_260, BPM_261 BPM_262 BPM_263,BPM_311A, BPM_311B, BPM_312, BPM_321A, BPM_321B, BPM_322, BPM_331A,BPM_331B, BPM_332, BPM_341A, BPM_341B, BPM_342, BPM_351A, BPM_351B,BPM_352, BPM_360, BPM_361 BPM_362, BPM_363

Description:
This variable indicates the average resting diastolic bloodpressure for the prevalence blood pressure measurement.
Blood pressure is measured in millimetres of Mercury (mmHg).

Note:
Created during processing.
The SAS code used to derive this variable is available uponrequest.
The first measure from each set is dropped prior to deriving thisvariable.

16. BPMDPBPS - Final average systolicblood pressure (Prevalence)

Variable name:
BPMDPBPS

Based on:
BPM_111A, BPM_111B, BPM_112,BPM_121A, BPM_121B, BPM_122, BPM_131A, BPM_131B, BPM_132, BPM_141A,BPM_141B, BPM_142, BPM_151A, BPM_151B, BPM_152, BPM_160, BPM_161,BPM_162, BPM_163, BPM_211A, BPM_211B, BPM_212, BPM_221A, BPM_221B,BPM_222, BPM_231A, BPM_231B, BPM_232, BPM_241A, BPM_241B, BPM_242,BPM_251A, BPM_251B, BPM_252, BPM_260, BPM_261 BPM_262 BPM_263,BPM_311A, BPM_311B, BPM_312, BPM_321A, BPM_321B, BPM_322, BPM_331A,BPM_331B, BPM_332, BPM_341A, BPM_341B, BPM_342, BPM_351A, BPM_351B,BPM_352, BPM_360, BPM_361 BPM_362, BPM_363

Description:
This variable indicates the average resting systolic blood pressurefor the prevalence blood pressure measurement. Blood pressureis measured in millimetres of Mercury (mmHg).

Note:
Created during processing.
The SAS code used to derive this variable is available uponrequest.
The first measure from each set is dropped prior to deriving thisvariable.

17. BPMDPHR - Final average restingheart rate (Prevalence)

Variable name:
BPMDPHR

Based on:
BPM_111A, BPM_111B, BPM_112,BPM_121A, BPM_121B, BPM_122, BPM_131A, BPM_131B, BPM_132, BPM_141A,BPM_141B, BPM_142, BPM_151A, BPM_151B, BPM_152, BPM_160, BPM_161,BPM_162, BPM_163, BPM_211A, BPM_211B, BPM_212, BPM_221A, BPM_221B,BPM_222, BPM_231A, BPM_231B, BPM_232, BPM_241A, BPM_241B, BPM_242,BPM_251A, BPM_251B, BPM_252, BPM_260, BPM_261 BPM_262 BPM_263,BPM_311A, BPM_311B, BPM_312, BPM_321A, BPM_321B, BPM_322, BPM_331A,BPM_331B, BPM_332, BPM_341A, BPM_341B, BPM_342, BPM_351A, BPM_351B,BPM_352, BPM_360, BPM_361 BPM_362, BPM_363

Description:
This variable indicates the average resting heart rate for theprevalence heart rate measurement. Heart rate is measured in beatsper minute (bpm).

Note:
Created during processing.
The SAS code used to derive this variable is available uponrequest.
The first measure from each set is dropped prior to deriving thisvariable.

18. BPMDSBPD - Final average diastolicblood pressure (Screening)

Variable name:
BPMDSBPD

Based on:
BPM_160, BPM_161, BPM_162,BPM_163, BPM_260, BPM_261, BPM_262, BPM_263, BPM_311, BPM_312,BPM_313, BPM_360, BPM_361, BPM_D362, BPM_363

Description:
This variable indicates the average resting diastolic bloodpressure for the screening blood pressure measurement. Bloodpressure is measured in millimetres of Mercury (mmHg).

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available uponrequest.
The first measure from each set is dropped prior to deriving thisvariable.

19. BPMDSBPS - Final average systolicblood pressure (Screening)

Variable name:
BPMDSBPS

Based on:
BPM_160, BPM_161, BPM_162,BPM_163, BPM_260, BPM_261, BPM_262, BPM_263, BPM_311, BPM_312,BPM_313, BPM_360, BPM_361, BPM_D362, BPM_363

Description:
This variable indicates the average resting systolic blood pressurefor the screening blood pressure measurement. Bloodpressure is measured in millimetres of Mercury (mmHg).

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available uponrequest.
The first measure from each set is dropped prior to deriving thisvariable.

20. BPMDSHR - Final average restingheart rate (Screening)

Variable name:
BPMDSHR

Based on:
BPM_160, BPM_161, BPM_162,BPM_163, BPM_260, BPM_261, BPM_262, BPM_263, BPM_311, BPM_312,BPM_313, BPM_360, BPM_361, BPM_D362, BPM_363

Description:
This variable indicates the average resting heart rate for thescreening heart rate measurement. Heart rate is measured in beatsper minute (bpm).

Note:
Created in the clinic collection application.
The SAS code used to derive this variable is available uponrequest.
The first measure from each set is dropped prior to deriving thisvariable.

Breastfeeding information (1DV)

1. BRIFEB6 - Exclusively breastfed forat least 3 months

Variable name:
BRIFEB6

Based on:
DHH_AGE, BRI_11, BRI_12, BRI_13

Description:
This variable indicates whether the respondent was exclusivelybreastfed for at least 3 months. Respondents greater than 11years of age were excluded from the population.

Table 1
BRIFEB6 Specifications
Value Condition(s) Description Notes
9 (BRI_11 = DK, RF, NS) or
(BRI_12 = DK, RF, NS) or
(BRI_13 = DK, RF, NS)
At least one required question was not answered (don't know, refusal, not stated) NS
6 DHH_AGE > 11 Population exclusions NA
1 (BRI_13 = 6, 7) Respondent was exclusively breastfed for at least 3 months  
2 BRI_11 = 2 or
BRI_13 < 6
Respondent not exclusively breastfed for at least 3 months  

Chronic conditions (1 DV)

1) CCCF1 - Has a ChronicCondition

Variable name:
CCCF1

Based on:
CCC_11, CCC_21, CCC_22, CCC_24, CCC_31, CCC_34, CCC_41, CCC_43,CCC_45, CCC_51, CCC_61, CCC_71, CCC_81, CCC_82, CCC_83, CCC_84,CCC_91, CCC_92, CCC_93, CCC_95, CCC_101

Description:
This variable indicates whether the respondent has at least onechronic health condition which was diagnosed by a healthprofessional.

Introduced in:
CCHS - Cycle 1.1

Table 1
CCCF1 Specifications
Value Condition(s) Description Notes
9 (CCC_11 = DK, RF, NS) or
(CCC_21 = DK, RF, NS) or
(CCC_22 = DK, RF, NS) or
(CCC_24 = DK, RF, NS) or
(CCC_31 = DK, RF, NS) or
(CCC_34 = DK, RF, NS) or
(CCC_41 = DK, RF, NS) or
(CCC_43 = DK, RF, NS) or
(CCC_45 = DK, RF, NS) or
(CCC_51 = DK, RF, NS) or
(CCC_61 = DK, RF, NS) or
(CCC_71 = DK, RF, NS) or
(CCC_81 = DK, RF, NS) or
(CCC_82 = DK, RF, NS) or
(CCC_83 = DK, RF, NS) or
(CCC_84 = DK, RF, NS) or
(CCC_91 = DK, RF, NS) or
(CCC_92 = DK, RF, NS) or
(CCC_93 = DK, RF, NS) or
(CCC_95 = DK, RF, NS) or
(CCC_101 = DK, RF, NS)
At least one required question
was not answered
(don't know, refusal, not stated)
NS
1 CCC_11 = 1 or
CCC_21 = 1 or
CCC_22 = 1 or
CCC_24 = 1 or
CCC_31 = 1 or
CCC_34 = 1 or
CCC_41 = 1 or
CCC_43 = 1 or
CCC_45 = 1 or
CCC_51 = 1 or
CCC_61 = 1 or
CCC_71 = 1 or
CCC_81 = 1 or
CCC_82 = 1 or
CCC_83 = 1 or
CCC_84 = 1 or
CCC_91 = 1 or
CCC_92 = 1 or
CCC_93 = 1 or
CCC_95 = 1 or
CCC_101 = 1
Has at least one chronic condition  
2 CCC_11 = 2 and
(CCC_21 = 2,NA) and
(CCC_22 = 2,NA) and
(CCC_24 = 2,NA) and
(CCC_31 = 2,NA) and
(CCC_34 = 2,NA) and
CCC_41 = 2 and
(CCC_43 = 2,NA) and
(CCC_45 = 2,NA) and
CCC_51 = 2 and
CCC_61 = 2 and
CCC_71 = 2 and
(CCC_81 = 2,NA) and
(CCC_82 = 2,NA) and
CCC_83 = 2 and
CCC_84 = 2 and
CCC_91 = 2 and
(CCC_92 = 2,NA) and
(CCC_93 = 2,NA) and
(CCC_95 = 2,NA) and
CCC_101 = 2
Has no chronic conditions  

Children's physical activity (2DVs)

Table
Children's physical activity Temporary Reformat

CPAT13
Value Condition(s) Description Notes
0 CPA_13 = 1 Recode to midpoint of response ranges  
1 CPA_13 = 2 Recode to midpoint of response ranges  
2.5 CPA_13 = 3 Recode to midpoint of response ranges  
5 CPA_13 = 4 Recode to midpoint of response ranges  
7 CPA_13 = 5 Recode to midpoint of response ranges  
CPAT14
Value Condition(s) Description Notes
0 CPA_14 = 1 Recode to midpoint of response ranges  
1 CPA_14 = 2 Recode to midpoint of response ranges  
2.5 CPA_14 = 3 Recode to midpoint of response ranges  
5 CPA_14 = 4 Recode to midpoint of response ranges  
7 CPA_14 = 5 Recode to midpoint of response ranges  
CPAT15
Value Condition(s) Description Notes
0 CPA_15 = 1 Recode to midpoint of response ranges  
1 CPA_15 = 2 Recode to midpoint of response ranges  
2.5 CPA_15 = 3 Recode to midpoint of response ranges  
5 CPA_15 = 4 Recode to midpoint of response ranges  
7 CPA_15 = 5 Recode to midpoint of response ranges  
CPAT16
Value Condition(s) Description Notes
0 CPA_16 = 1 Recode to midpoint of response ranges  
1 CPA_16 = 2 Recode to midpoint of response ranges  
2.5 CPA_16 = 3 Recode to midpoint of response ranges  
5 CPA_16 = 4 Recode to midpoint of response ranges  
7 CPA_16 = 5 Recode to midpoint of response ranges  
CPAT17
Value Condition(s) Description Notes
0 CPA_17 = 1 Recode to midpoint of response ranges  
0.5 CPA_17 = 2 Recode to midpoint of response ranges  
1.5 CPA_17 = 3 Recode to midpoint of response ranges  
3.5 CPA_17 = 4 Recode to midpoint of response ranges  
5.5 CPA_17 = 5 Recode to midpoint of response ranges  
7 CPA_17 = 6 Recode to midpoint of response ranges  
CPAT18
Value Condition(s) Description Notes
0 CPA_18 = 1 Recode to midpoint of response ranges  
0.5 CPA_18 = 2 Recode to midpoint of response ranges  
1.5 CPA_18 = 3 Recode to midpoint of response ranges  
3.5 CPA_18 = 4 Recode to midpoint of response ranges  
5.5 CPA_18 = 5 Recode to midpoint of response ranges  
7 CPA_18 = 6 Recode to midpoint of response ranges  

1. CPADSAC - Total number of hours perday spent in sedentary activities

Variable name:
CPADSAC

Based on:
CPA_17, CPA_18

Description:
This variable estimates the total number of hours per day the childparticipates in sedentary activities including watching TV orvideos, playing video games, and spending time on a computer playinggames, e-mailing, chatting and surfing the Internet.

Note:
This variable applies to children aged 6 to 11.

Table 1
CPADSAC Specifications
Value Condition(s) Description Notes
96 CPA_11 = NA Population exclusions NA
99 (CPA_17 = DK, RF, NS) or
(CPA_18 = DK, RF, NS)
At least one required question was
not answered (don't know, refusal, not stated)
NS
CPAT17 +
CPAT18
(Round to nearest 0.5)
(0 <= CPAT17 <= 7) and
(0 <= CPAT18 <= 7)
Total number of hours per day
participated in sedentary activities
(e.g. watching TV, spending time on a computer)
(min: 0.0; max: 14.0)

2. CPADTOT - Total number of hours perweek participated in physical activities

Variable name:
CPADTOT

Based on:
CPA_13, CPA_14, CPA_15, CPA_16

Description:
This variable estimates the total number of hours per week thechild usually takes part in physical activities at school oroutside of school.

Note:
This variable applies to children aged 6 to 11.

Table 2
CPADTOT Specifications
Value Condition(s) Description Notes
96 CPA_11 = NA Population exclusions NA
99 (CPA_13 = DK, RF, NS) or
(CPA_14 = DK, RF, NS) or
(CPA_15 = DK, RF, NS) or
(CPA_16 = DK, RF, NS)
At least one required question was
not answered (don't know, refusal, not stated)
NS
CPAT13 +
CPAT14 +
CPAT15 +
CPAT16
(Round to nearest
whole number)
(0 <= CPAT13 <= 7) and
(0 <= CPAT14 <= 7) and
(0 <= CPAT15 <= 7) and
(0 <= CPAT16 <= 7)
Total number of hours per week
participated in physical activities
(min: 0; max: 28)

Dietary fat consumption (2 DVs)

1. DFCD11Y - Eats regular-fat saladdressing - times per year

Variable name:
DFCD11Y

Based on:
DFC_11, DFC_11N

Description:
The number of times per year the respondent eats regular-fat saladdressing or mayonnaise.

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 1
DFCD11Y Specifications
Value Condition(s) Description Notes
0 DFC_11 = 0 Never  
DFC_11 * 365 DFC_11N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
DFC_11 * 52 DFC_11N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
DFC_11 * 12 DFC_11N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
DFC_11 DFC_11N = 4 Reported number of times consumed per year  
9996 DFC_11N = NA Population exclusions NA
9999 Else   NS

2. DFCD12Y - Eats regular-fat potatochips, tortilla chips or corn chips - times per year

Variable name:
DFCD12Y

Based on:
DFC_12, DFC_12N

Description:
The number of times per year the respondent eats regular-fat potatochips, tortilla chips or corn chips (excluding low fat chips andpretzels).

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 2
DFCD12Y Specifications
Value Condition(s) Description Notes
0 DFC_12 = 0 Never  
DFC_12 * 365 DFC_12N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
DFC_12 * 52 DFC_12N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
DFC_12 * 12 DFC_12N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
DFC_12 DFC_12N = 4 Reported number of times consumed per year  
9996 DFC_12N = NA Population exclusions NA
9999 Else   NS

Demographic and household variables (9DVs)

1. DHHD611 - Number of Persons inHousehold 6 to 11 Years of Age

Variable name:
DHHD611

Based on:
SAMPLEID, PERSONID, DHH_AGE

Description:
This variable indicates the number of people between 6 and 11 yearsold living within a household.

Introduced in:
CCHS - Cycle 1.1

Note:
This variable is derived by sorting the household roster dataset bySAMPLEID and PERSONID and by counting the number ofPERSONID's that have a DHH_AGE value from 6 to 11 within eachSAMPLEID.

Table 1
DHHD611 Specifications
Value Condition(s) Description Notes
Total number of
PERSONID's for
each SAMPLEID
(6 <= DHH_AGE <= 11)
(from Member file)
Number of persons 6 to 11 in a household  

2. DHHDDWE - Dwelling Type

Variable name:
DHHDDWE

Based on:
DHH_DW1, DHH_DW2

Description:
This variable indicates the type of dwelling the respondent livesin, according to the answer either given on the phone (DHH_DW1) orentered by observation (DHH_DW2).

Introduced in:
CCHS - Cycle 1.1

Table 2
DHHDDWE Specifications
Value Condition(s) Description Notes
99 (DHH_DW1 = DK, RF, NS) or
(DHH_DW2 = DK, RF, NS)
At least one required question was not
answered (don't know, refusal, not stated)
NS
1 DHH_DW1 = 1 or
DHH_DW2 = 1
Single detached  
2 DHH_DW1 = 2 or
DHH_DW2 = 2
Double  
3 DHH_DW1 = 3 or
DHH_DW2 = 3
Row or terrace  
4 DHH_DW1 = 4 or
DHH_DW2 = 4
Duplex  
5 DHH_DW1 = 5 or
DHH_DW2 = 5
Low-rise apartment (< 5 stories) or flat  
6 DHH_DW1 = 6 or
DHH_DW2 = 6
High-rise apartment (5 stories or more)  
7 DHH_DW1 = 7 or
DHH_DW2 = 7
Institution  
8 DHH_DW1 = 8 or
DHH_DW2 = 8
Hotel/rooming house/camp  
9 DHH_DW1 = 9 or
DHH_DW2 = 9
Mobile home  
10 DHH_DW1 = 10 or
DHH_DW2 = 10
Other  

3. DHHDECF - Economic Family Status(Household Type)

Variable name:
DHHDECF

Based on:
DHH_REL for all PERSONID in SAMPLEID, DHH_AGE, DHH_SEX, DHHDHSZ

Description:
This variable identifies the family relationships within thehousehold.

Introduced in:
CCHS - Cycle 1.1

Note:
The necessary data is collected using a set of relationship codesthat define a link between each person in a household. Allrelationships within each household (relationship of each person ina household to each other person within that household) are used increating this variable. The variable is based on the ages andreported relationships of each person to all others in thehousehold.

Table 3
DHHDECF Temporary Reformat

DHH_REL
Value Condition(s) Description Notes
X 10, 20 Temporary recodes to collapse relationships -Spouse (10 =Husband/Wife, 20 = Common Law Partner) Relationship Codes DVECF94
A 40, 41, 42, 43 Temporary recodes to collapse relationships - Parental Relationship Codes DVECF94
M 50, 51, 52, 53 (sorted by age) Temporary recodes to collapse relationships - Child (50 =Son/Daughter, 51 = Birth Child, 52 = Step Child, 53 = AdoptedChild) Relationship Codes DVECF94
L 60, 61, 62, 63, 64, 65*, 70*, 80*, 90, 100, 110, 111, 112, 113,114, 120, 121, 122, 123, 124, 260 Temporary recodes to collapse relationships -Other (60 =Brother/Sister, 61 = Full Sister/Brother, 62 = Half Sister/Brother,63 = Step Sister/Brother, 64 = Adopted Sister/Brother, 65 = FosterSister/Brother, 70 = Foster Parent, 80 = Foster Child, 90 =Grandparent, 100 = Grandchild, 110 = In-Law, 111 =Father/Mother-in-law, 112 = Son/Daughter-in-law, 113 =Brother/Sister-in-law, 114 = Other in-law, 120 = Other Related, 121= Uncle/Aunt, 122 = Cousin, 123 = Nephew/Niece, 124 = OtherRelative, 260 = Unrelated) Relationship Codes DVECF94 *All Foster relationships (fostersister/brother, parent, or child) have been recoded into the Otherrelationship category due to the temporary nature of therelationships
Y DHHDHSZ = 1 Temporary recodes to collapse relationships - Single Relationship Codes DVECF94
Z Else Temporary recodes to collapse relationships - Not stated Relationship Codes DVECF94
Table 3
DHHDECF Specifications
Value Condition(s) Description Notes
99 Any DHH_REL = Z Not Stated NS
1 DHHDHSZ = 1 Unattached individual living alone
Household size=1
 
2 All DHH_REL for all PERSONID in SAMPLEID in (L,Y) Unattached individuals living together
There cannot be a marital/common-law or parental relationship butother relationships such as siblings are allowed
 
3 DHHDHSZ = 2 and
DHH_REL for both PERSONID in SAMPLEID = X
Couple (married or common-law) with no dependent children
No other relationships are permitted
Household size=2
 
4 DHHDHSZ > 2 and
At least 2 PERSONID in SAMPLEID must have an
DHH_REL = X and
DHH_REL for all PERSONID in SAMPLEID <> A and M
Couple (married or common-law) with no dependent children
There can be no parent/child relationships
Other relationships are permitted
 
5 DHHDHSZ > 2 and
At least 2 PERSONID in SAMPLEID must have an
DHH_REL = X and
At least one of which must have an DHH_REL = A.
All others PERSONID in SAMPLEID must have
DHH_REL = M and of these at least one is DHH_AGE < 25
Married or common-law couple with at least one partner beingthe parent of a dependent child (age < 25)
No other relationships are allowed
 
6 At least 2 PERSONID in SAMPLEID must have an
DHH_REL = X and
At least one of which must have an DHH_REL = A.
At least one other PERSONID in SAMPLEID must have DHH_REL = M withthe above PERSONID and of these at least one is DHH_AGE <25
Couple With Children < 25, Others
At least one partner must be the parent of one child < 25 yearsold in the household
Other relationships are allowed
 
7 DHHDHSZ > 2 and
At least 2 PERSONID in SAMPLEID must have an
DHH_REL = X and
At least one of which must have an DHH_REL = A.
All others PERSONID in SAMPLEID must have
DHH_REL = M and of these DHH_AGE >= 25
Married or common-law couple with all children >= 25 yearsold
No other relationships are permitted
 
8 DHHDHSZ > 2 and
At least 2 PERSONID in SAMPLEID must have an
DHH_REL = X and
At least one of which must have an DHH_REL = A.
At least one other PERSONID in SAMPLEID must have DHH_REL = M withthe above PERSONID and of these DHH_AGE >= 25
Married or common-law couple with all children >= 25 yearsold, Others
Any other relationships are allowed
 
9 DHHDHSZ > 1 and
One PERSONID in SAMPLEID must have DHH_REL = A and DHH_SEX = 2. Allothers PERSONID in SAMPLEID must have
DHH_REL = M and of these at least one DHH_AGE < 25
Female lone parent with children < 25
One child must be < 25 years old
No other relationships are permitted.
 
10 DHHDHSZ > 1 and
One PERSONID in SAMPLEID must have DHH_REL = A and DHHn_SEX =2.
At least one other PERSONID in SAMPLEID must have DHH_REL = M withthe above PERSONID and of these at least one DHH_AGE < 25
Female lone parent with children < 25, Others
One child must be < 25 years old
Other relationships are allowed
 
11 DHHDHSZ > 1 and
One PERSONID in SAMPLEID must have DHH_REL = A and DHHn_SEX =2.
All others PERSONID in SAMPLEID must have
DHH_REL = M and of these DHH_AGE >= 25
Female Lone Parent With All Children >= 25
All children must be >= 25 years old
No other relationships are permitted
 
12 DHHDHSZ > 1 and
One PERSONID in SAMPLEID must have DHH_REL = A and DHH_SEX = 2.
At least one other PERSONID in SAMPLEID must have DHH_REL = M withthe above PERSONID and of these DHH_AGE >= 25
Female Lone Parent With All Children >= 25, Others
All children must be >= 25 years old
Other relationships are allowed
 
13 DHHDHSZ > 1 and
One PERSONID in SAMPLEID must have DHH_REL = A and DHH_SEX = 1.
All others PERSONID in SAMPLEID must have
DHH_REL = M and of these at least one DHH_AGE < 25
Male Lone Parent With Children < 25
One child must be < 25 years old
No other relationships are permitted
 
14 DHHDHSZ > 1 and
One PERSONID in SAMPLEID must have DHH_REL = A and DHH_SEX = 1.
At least one other PERSONID in SAMPLEID must have DHH_REL = M withthe above PERSONID and of these at least one DHH_AGE < 25
Male Lone Parent With Children < 25, Others
One child must be < 25 years old
Other relationships are allowed
 
15 DHHDHSZ > 1 and
One PERSONID in SAMPLEID must have DHH_REL = A and DHH_SEX = 1.
All others PERSONID in SAMPLEID must have
DHH_REL = M and of these DHH_AGE >= 25
Male Lone Parent With All Children >= 25
All children must be >= 25 years old
No other relationships are permitted
 
16 DHHDHSZ > 1 and
One PERSONID in SAMPLEID must have DHH_REL = A and DHH_SEX = 1.
At least one other PERSONID in SAMPLEID must have DHH_REL = M withthe above PERSONID and of these DHH_AGE >= 25
Male Lone Parent With All Children >= 25, Others
All children must be >= 25 years old
Other relationships are allowed
 
17 Else Other Family Type
All other household types
 

4. DHHDHSZ - Household Size

Variable name:
DHHDHSZ

Based on:
Based on household roster, SAMPLEID, PERSONID

Description:
This variable indicates the number of people living within ahousehold.

Introduced in:
CCHS - Cycle 1.1

Note:
This variable is derived by sorting the household roster dataset bySAMPLEID and PERSONID and by counting the number ofPERSONID's within each SAMPLEID.

Table 4
DHHDHSZ Specifications
Value Condition(s) Description Notes
Total number of
PERSONID's for
each SAMPLEID
Sort the file (Member file)
by SAMPLEID and PERSONID
Number of persons in a household  

5. DHHDL12 - Number of Persons inHousehold Less Than 12 Years of Age

Variable name:
DHHDL12

Based on:
SAMPLEID, PERSONID, DHH_AGE

Description:
This variable indicates the number of people less than 12 years oldliving within a household.

Introduced in:
CCHS - Cycle 1.1

Note:
This variable is derived by sorting the household roster dataset bySAMPLEID and PERSONID and by counting the number ofPERSONID's that have a DHH_AGE value less than 12 within eachSAMPLEID.

Table 5
DHHDL12 Specifications
Value Condition(s) Description Notes
Total number of
PERSONID's for
each SAMPLEID
DHH_AGE < 12
(from Member file)
Number of persons under 12 in a household  

6. DHHDLE5 - Number of Persons inHousehold Less Than 6 Years of Age

Variable name:
DHHDLE5

Based on:
SAMPLEID, PERSONID, DHH_AGE

Description:
This variable indicates the number of people living within ahousehold whose age is less than 6 years old.

Introduced in:
CCHS - Cycle 1.1

Note:
This variable is derived by sorting the household roster dataset bySAMPLEID and PERSONID and by counting the number ofPERSONID's that have a DHH_AGE value less than 6 within eachSAMPLEID.

Table 6
DHHDLE5 Specifications
Value Condition(s) Description Notes
Total number of
PERSONID's for
each SAMPLEID
DHH_AGE <= 5
(from Member file)
Number of persons under 6 in a household  

7. DHHDLVG - Living/ Family Arrangementof Selected Respondent

Variable name:
DHHDLVG

Based on:
DHH_REL of selected respondent, DHHDHSZ, DHH_AGE

Description:
This variable identifies the family relationships between theselected respondent and the rest of the household.

Introduced in:
CCHS - Cycle 1.1

Note:
The necessary data is collected using a set of relationship codesthat define a link between each person in a household. Allrelationships with the selected respondent within each sample(relationship of selected respondent to each other person withinthe household) are used in creating this variable.

Table 7
DHHDLVG
Temporary Reformat

DHH_REL
Value Condition(s) Description Notes
Z1 NS Temporary recodes to collapse relationships - Not stated Relationship Codes
A1 40, 41, 42, 43 Temporary recodes to collapse relationships –Parental Relationship Codes
B1 50, 51, 52, 53 Temporary recodes to collapse relationships – Child Relationship Codes
C1 60, 61, 62, 63, 64 Temporary recodes to collapse relationships –Sibling Relationship Codes
K1 90, 100, 110, 111,
112, 113, 114, 120,
121, 122, 123, 124
Temporary recodes to collapse relationships - Otherrelative Relationship Codes
L1 65*, 70*, 80*, 260,
261, 262, 263
Temporary recodes to collapse relationships - Non-relative Relationship Codes *All
Foster relationships
(foster sister/brother, parent, or child)
have been recoded into the Other
relationship category due to the
temporary nature of the relationships.
X1 10, 20 Temporary recodes to collapse relationships -Spouse/Partner Relationship Codes
Table 7
DHHDLVG Specifications
Value Condition(s) Description Notes
99 Any DHH_REL = Z1 Not Stated NS
1 DHHDHSZ = 1 Unattached individual living alone
Household size=1
 
2 All DHH_REL <> X1 and A1 Unattached individual living with others
S/he cannot have a marital/common-law
or parental relationship but other relationships
such as siblings are allowed
 
3 DHHDHSZ = 2 and
DHH_REL = X1
Spouse/partner living with spouse/partner
Household size=2
 
4 DHHDHSZ > 2 and
One DHH_REL = X1 and
all other DHH_REL = A1
Parent living with spouse/partner and children  
5 All DHH_REL = A1 Single parent living with children
No other relationships are permitted
 
6 DHHDHSZ = 2 and
DHH_REL = B1
Child living with single parent
Household size=2
 
7 DHHDHSZ > 2 and
One DHH_REL = B1 and
all other DHH_ REL = C1
Child living with single parent and siblings  
8 DHHDHSZ = 3 and
All DHH_REL = B1
Child living with two parents
Household size=3
 
9 DHHDHSZ > 3 and
Two DHH_REL = B1 and all other DHH_REL = C1
Child living with two parents and siblings  
10 Else Other
Lives in a household composition not classified above
 
Total number
of PERSONID's
with each SAMPLEID
DHH_AGE = 16, 17 (Member file) and
RELATIONSHIP = 51, 52, 53, 80, 100, 112, 123 (Relation files)
Number of persons aged 16 or 17 in a household
whose relationship with at least one adult of the
household is child, grandchild, child-in-law or, niece ornephew
(min: 0; max: 40)

8. DHHDOKD - Number of Persons inHousehold 16 or 17 Years of Age

Variable name:
DHHDOKD

Based on:
PERSONID, DHH_AGE, RELATIONSHIP

Description:
This variable indicates the number of people living within ahousehold whose age is 16 or 17 years old and whose relationship toat least one adult living within the household is child,grandchild, child-in-law, niece or nephew.

Introduced in:
CCHS - Cycle 3.1

Note:
This variable is derived by sorting the household roster dataset bySAMPLEID and PERSONID and by counting the number ofPERSONID's that have a DHH_AGE value of 16 or 17 and whoseRELATIONSHIP value of (51, 52, 53, 80, 100, 112 or 123) within eachSAMPLEID.

Table 8
DHHDOKD Specifications
Value Condition(s) Description Notes
Total number
of
PERSONID's
with each
SAMPLEID
DHH_AGE = 16, 17 (Member file) and
RELATIONSHIP = 51, 52, 53, 80, 100,
112, 123 (Relation files)
Number of persons aged 16 or 17
in a household whose relationship
with at least one adult of the household
is child, grandchild, child-in-law, or niece or nephew
(min: 0; max: 40)

9. DHHDYKD - Number of Persons inHousehold Less Than 16 Years of Age

Variable name:
DHHDYKD

Based on:
SAMPLEID, PERSONID, DHH_AGE

Description:
This variable indicates the number of people living within ahousehold whose age is less than 16 years old.

Introduced in:
CCHS - Cycle 3.1

Note:
This variable is derived by sorting the household roster dataset bySAMPLEID and PERSONID and by counting the number ofPERSONID's that have a DHH_AGE value of less than 16 withineach SAMPLEID.

Table 9
DHHDYKD Specifications
Value Condition(s) Description Notes
Total number
of
PERSONID's
for each
SAMPLEID
DHH_AGE <= 15 (from Member file) Number of persons under 16 in a household  

Education (4 DVs)

1. EDUDH04 - Highest Level ofEducation - Household, 4 Levels

Variable name:
EDUDH04

Based on:
EDUDR04 for each member of the household

Description:
This variable indicates the highest level of education acquired byany member of the household.

Introduced in:
CCHS - Cycle 1.1

Note:
This variable is derived by temporarily creating EDUDR04 for allmembers of the household (all PERSONIDs within SAMPLEID), then bycomparing the values of EDUDR04 within the household and returningthe highest value. If EDUDR04 for any household member is NS(not stated), then NS is returned. If EDUDR04 for allhousehold members is NA (not applicable), then NA is returned.

2. EDUDH10 - Highest Level of Education- Household, 10 Levels

Variable name:
EDUDH10

Based on:
EDUDR10 for each member of the household

Description:
This variable indicates the highest level of education acquired byany member of the household.

Introduced in:
CCHS - Cycle 1.1

Note:
This variable is derived by temporarily creating EDUDR10 for allmembers of the household (all PERSONIDs within SAMPLEID), then bycomparing the values of EDUDR10 within the household and returningthe highest value. If EDUDR10 for any household member is NS(not stated), then NS is returned. If EDUDR10 for allhousehold members is NA (not applicable), then NA is returned.

3. EDUDR04 - Highest Level of Education- Household, 4 Levels

Variable name:
EDUDR04

Based on:
DHH_ED1, DHH_ED2, DHH_ED3, DHH_ED4

Description:
This variable indicates the highest level of education acquired byeach member of the household.

Introduced in:
CCHS - Cycle 1.1

Table 3
EDUDR04 Specifications
Value Condition(s) Description Notes
9 (DHH_ED2 = DK, RF, NS) or
(DHH_ED3 = DK, RF, NS) or
(DHH_ED4 = DK, RF, NS)
At least one required question
was not answered (don't know, refusal, not stated)
NS
1 ((DHH_ED1 = 1, 2) or
DHH_ED2 = 2) and
DHH_ED3 = 2
Less than secondary school graduation  
2 DHH_ED2 = 1 and
DHH_ED3 = 2
Secondary school graduation,
no post-secondary education
 
3 DHH_ED4 = 1 Some post-secondary education  
4 (2 <= DHH_ED4 <= 6) Post-secondary degree/diploma  

4. EDUDR10 - Highest Level of Education- Household, 10 Levels

Variable name:
EDUDR10

Based on:
DHH_ED1, DHH_ED2, DHH_ED3, DHH_ED4

Description:
This variable indicates the highest level of education acquired byeach member of the household.

Introduced in:
CCHS - Cycle 1.1

Table 4
EDUDR10 Specifications
Value Condition(s) Description Notes
99 ((DHH_ED1 = DK, RF, NS)
and DHH_ED2 = 2) or
(DHH_ED2 = DK, RF, NS)
or (DHH_ED3 = DK, RF, NS)
or (DHH_ED4 = DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NS
1 DHH_ED1 = 1 and
DHH_ED3 = 2
Grade 8 or lower (Québec: Secondary II or lower)  
2 DHH_ED1 = 2 and
DHH_ED3 = 2
Grade 9-10 (Québec: Secondary III or IV; Newfoundland& Labrador: 1st year of secondary)  
3 DHH_ED1 = 3 and
DHH_ED2 = 2 and
DHH_ED3 = 2
Grade 11-13 (Québec: Secondary V; Newfoundland &Labrador: 2nd to 4th year of secondary)  
4 DHH_ED2 = 1 and
DHH_ED3 = 2
Secondary school graduate, no post-secondary education  
5 DHH_ED4 = 1 Some post secondary education  
6 DHH_ED4 = 2 Trade certificate or diploma from a vocational school orapprenticeship training  
7 DHH_ED4 = 3 Non-university certificate or diploma from a community college,CEGEP, school of nursing, etc.  
8 DHH_ED4 = 4 University certificate below bachelor's level  
9 DHH_ED4 = 5 Bachelor's degree  
10 DHH_ED4 = 6 University degree or certificate above bachelor'sdegree  

General health (2 DVs)

1. GENDHDI - Self-Rated Health(Formerly Health Description Index)

Variable name:
GENDHDI

Based on:
GEN_11

Description:
This variable indicates the respondent's health status basedon his/her own judgement.

Introduced in:
NPHS - Cycle 1

Note:
Higher values indicate positive self-reported health status.

Table 1
GENDHDI Specifications
Value Condition(s) Description Notes
9 (GEN_11 = DK, RF, NS) At least one required question was not answered (don'tknow, refusal, not stated) NS
0 GEN_11 = 5 Poor  
1 GEN_11 = 4 Fair  
2 GEN_11 = 3 Good  
3 GEN_11 = 2 Very good  
4 GEN_11 = 1 Excellent  

2. GENDMHI - Self-Rated MentalHealth

Variable name:
GENDMHI

Based on:
GEN_14

Description:
This variable indicates the respondent's mental health statusbased on his/her own judgement.

Introduced in:
CCHS - Cycle 1.2

Note:
Higher values indicate positive self-reported mental health status.

Table 2
GENDMHI Specifications
Value Condition(s) Description Notes
9 (GEN_14 = DK, RF, NS) At least one required question was not answered (don'tknow, refusal, not stated) NS
0 GEN_14 = 5 Poor  
1 GEN_14 = 4 Fair  
2 GEN_14 = 3 Good  
3 GEN_14 = 2 Very good  
4 GEN_14 = 1 Excellent  

Grains, fruits and vegetablesconsumption (13 DVs)

1. GFVD11Y - Eats hot or cold cereal -times per year

Variable name:
GFVD11Y

Based on:
GFV_11, GFV_11N

Description:
The number of times per year the respondent eats hot or coldcereal.

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 1
GFVD11Y Specifications
Value Condition(s) Description Notes
0 GFV_11 = 0 Never  
GFV_11 * 365 GFV_11N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
GFV_11 * 52 GFV_11N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
GFV_11 * 12 GFV_11N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
GFV_11 GFV_11N = 4 Reported number of times consumed per year  
9996 GFV_11N = NA Population exclusions NA
9999 Else   NS

2. GFVD12Y - Eats brown bread, includingbagels, rolls, pita bread or tortillas - times per year

Variable name:
GFVD12Y

Based on:
GFV_12, GFV_12N

Description:
The number of times per year the respondent eats brown bread(including bagels, rolls, pita bread or tortillas).

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 2
GFVD12Y Specifications
Value Condition(s) Description Notes
0 GFV_12 = 0 Never  
GFV_12 * 365 GFV_12N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
GFV_12 * 52 GFV_12N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
GFV_12 * 12 GFV_12N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
GFV_12 GFV_12N = 4 Reported number of times consumed per year  
9996 GFV_12N = NA Population exclusions NA
9999 Else   NS

3. GFVD13Y - Eats white bread, includingbagels, rolls, pita bread or tortillas - times per year

Variable name:
GFVD13Y

Based on:
GFV_13, GFV_13N

Description:
The number of times per year the respondent eats white bread(including bagels, rolls, pita bread or tortillas).

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 3
GFVD13Y Specifications
Value Condition(s) Description Notes
0 GFV_13 = 0 Never  
GFV_13 * 365 GFV_13N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
GFV_13 * 52 GFV_13N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
GFV_13 * 12 GFV_13N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
GFV_13 GFV_13N = 4 Reported number of times consumed per year  
9996 GFV_13N = NA Population exclusions NA
9999 Else   NS

4. GFVD14Y - Eats any kind of pasta -times per year

Variable name:
GFVD14Y

Based on:
GFV_14, GFV_14N

Description:
The number of times per year the respondent eats any kind of pasta(including spaghetti, noodles, macaroni and cheese or pastasalad).

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 4
GFVD14Y Specifications
Value Condition(s) Description Notes
0 GFV_14 = 0 Never  
GFV_14 * 365 GFV_14N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
GFV_14 * 52 GFV_14N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
GFV_14 * 12 GFV_14N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
GFV_14 GFV_14N = 4 Reported number of times consumed per year  
9996 GFV_14N = NA Population exclusions NA
9999 Else   NS

5. GFVD15Y - Eats any kind of rice -times per year

Variable name:
GFVD15Y

Based on:
GFV_15, GFV_15N

Description:
The number of times per year the respondent eats any kind ofrice.

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 5
GFVD15Y Specifications
Value Condition(s) Description Notes
0 GFV_15 = 0 Never  
GFV_15 * 365 GFV_15N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
GFV_15 * 52 GFV_15N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
GFV_15 * 12 GFV_15N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
GFV_15 GFV_15N = 4 Reported number of times consumed per year  
9996 GFV_15N = NA Population exclusions NA
9999 Else   NS

6. GFVD16Y - Eats instant, seasoned orwild rice - times per year

Variable name:
GFVD16Y

Based on:
GFV_16, GFV_16N

Description:
The number of times per year the respondent who eats rice eatsinstant, seasoned or wild rice (including Minute Rice®,Dainty®, Rice-a-Roni®).

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 6
GFVD16Y Specifications
Value Condition(s) Description Notes
0 GFV_16 = 0 Never  
GFV_16 * 365 GFV_16N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
GFV_16 * 52 GFV_16N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
GFV_16 * 12 GFV_16N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
GFV_16 GFV_16N = 4 Reported number of times consumed per year  
9996 GFV_16N = NA Population exclusions NA
9999 Else   NS

7. GFVD17Y - Eats fruit - times peryear

Variable name:
GFVD17Y

Based on:
GFV_17, GFV_17N

Description:
The number of times per year the respondent eats fruit (fresh,frozen, canned).

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 7
GFVD17Y Specifications
Value Condition(s) Description Notes
0 GFV_17 = 0 Never  
GFV_17 * 365 GFV_17N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
GFV_17 * 52 GFV_17N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
GFV_17 * 12 GFV_17N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
GFV_17 GFV_17N = 4 Reported number of times consumed per year  
9996 GFV_17N = NA Population exclusions NA
9999 Else   NS

8. GFVD18Y - Eats tomatoes or tomatosauce - times per year

Variable name:
GFVD18Y

Based on:
GFV_18, GFV_18N

Description:
The number of times per year the respondent eats tomatoes or tomatosauce (including salsa, tomato soup and spaghetti sauce butexcluding tomato paste, ketchup or pizza sauce).

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 8
GFVD18Y Specifications
Value Condition(s) Description Notes
0 GFV_18 = 0 Never  
GFV_18 * 365 GFV_18N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
GFV_18 * 52 GFV_18N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
GFV_18 * 12 GFV_18N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
GFV_18 GFV_18N = 4 Reported number of times consumed per year  
9996 GFV_18N = NA Population exclusions NA
9999 Else   NS

9. GFVD19Y - Eats lettuce or green leafysalad - times per year

Variable name:
GFVD19Y

Based on:
GFV_19, GFV_19N

Description:
The number of times per year the respondent eats lettuce or greenleafy salad with or without other vegetables.

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 9
GFVD19Y Specifications
Value Condition(s) Description Notes
0 GFV_19 = 0 Never  
GFV_19 * 365 GFV_19N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
GFV_19 * 52 GFV_19N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
GFV_19 * 12 GFV_19N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
GFV_19 GFV_19N = 4 Reported number of times consumed per year  
9996 GFV_19N = NA Population exclusions NA
9999 Else   NS

10. GFVD20Y - Eats spinach, mustardgreens or collards - times per year

Variable name:
GFVD20Y

Based on:
GFV_20, GFV_20N

Description:
The number of times per year the respondent eats spinach, mustardgreens or collards excluding kale.

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 10
GFVD20Y Specifications
Value Condition(s) Description Notes
0 GFV_20 = 0 Never  
GFV_20 * 365 GFV_20N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
GFV_20 * 52 GFV_20N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
GFV_20 * 12 GFV_20N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
GFV_20 GFV_20N = 4 Reported number of times consumed per year  
9996 GFV_20N = NA Population exclusions NA
9999 Else   NS

11. GFVD21Y - Eats french fries, homefries or hash brown potatoes - times per year

Variable name:
GFVD21Y

Based on:
GFV_21, GFV_21N

Description:
The number of times per year the respondent eats french fries, homefries or hash brown potatoes.

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 11
GFVD21Y Specifications
Value Condition(s) Description Notes
0 GFV_21 = 0 Never  
GFV_21 * 365 GFV_21N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
GFV_21 * 52 GFV_21N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
GFV_21 * 12 GFV_21N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
GFV_21 GFV_21N = 4 Reported number of times consumed per year  
9996 GFV_21N = NA Population exclusions NA
9999 Else   NS

12. GFVD22Y - Eats other potatoes -times per year

Variable name:
GFVD22Y

Based on:
GFV_22, GFV_22N

Description:
The number of times per year the respondent eats other potatoes(including baked, boiled, mashed or in potato salad, but excludingsweet potatoes).

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 12
GFVD22Y Specifications
Value Condition(s) Description Notes
0 GFV_22 = 0 Never  
GFV_22 * 365 GFV_22N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
GFV_22 * 52 GFV_22N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
GFV_22 * 12 GFV_22N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
GFV_22 GFV_22N = 4 Reported number of times consumed per year  
9996 GFV_22N = NA Population exclusions NA
9999 Else   NS

13. GFVD23Y - Eats all other types ofvegetables - times per year

Variable name:
GFVD23Y

Based on:
GFV_23, GFV_23N

Description:
The number of times per year the respondent eats all other types ofvegetables.

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 13
GFVD23Y Specifications
Value Condition(s) Description Notes
0 GFV_23 = 0 Never  
GFV_23 * 365 GFV_23N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
GFV_23 * 52 GFV_23N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
GFV_23 * 12 GFV_23N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
GFV_23 GFV_23N = 4 Reported number of times consumed per year  
9996 GFV_23N = NA Population exclusions NA
9999 Else   NS

Grooming product use (7 DVs)

1. GPUD12Y - Uses fragrance - timesper year

Variable name:
GPUD12Y

Based on:
GPU_12, GPU_12N

Description:
The number of times per year the respondent uses fragrance(including perfumes, cologne and aftershave).

Note:
Created in the Household Post-Verify process.

Table 1
GPUD12Y Specifications
Value Condition(s) Description Notes
0 GPU_12 = 0 Never  
GPU_12 * 365 GPU_12N = 1 Reported number of times used per day converted to derivednumber of times used per year  
GPU_12 * 52 GPU_12N = 2 Reported number of times used per week converted to derivednumber of times used per year  
GPU_12 * 12 GPU_12N = 3 Reported number of times used per month converted to derivednumber of times used per year  
GPU_12 GPU_12N = 4 Reported number of times used per year  
9996 GPU_12N = NA Population exclusions NA
9999 Else   NS

2. GPUD13Y - Uses eye make-up - timesper year

Variable name:
GPUD13Y

Based on:
GPU_13, GPU_13N

Description:
The number of times per year the respondent uses eye make-up.

Note:
Created in the Household Post-Verify process.

Table 2
GPUD13Y Specifications
Value Condition(s) Description Notes
0 GPU_13 = 0 Never  
GPU_13 * 365 GPU_13N = 1 Reported number of times used per day converted to derivednumber of times used per year  
GPU_13 * 52 GPU_13N = 2 Reported number of times used per week converted to derivednumber of times used per year  
GPU_13 * 12 GPU_13N = 3 Reported number of times used per month converted to derivednumber of times used per year  
GPU_13 GPU_13N = 4 Reported number of times used per year  
9996 GPU_13N = NA Population exclusions NA
9999 Else   NS

3. GPUD14Y - Uses lipstick - times peryear

Variable name:
GPUD14Y

Based on:
GPU_14, GPU_14N

Description:
The number of times per year the respondent uses lipstick(including lip gloss).

Note:
Created in the Household Post-Verify process.

Table 3
GPUD14Y Specifications
Value Condition(s) Description Notes
0 GPU_14 = 0 Never  
GPU_14 * 365 GPU_14N = 1 Reported number of times used per day converted to derivednumber of times used per year  
GPU_14 * 52 GPU_14N = 2 Reported number of times used per week converted to derivednumber of times used per year  
GPU_14 * 12 GPU_14N = 3 Reported number of times used per month converted to derivednumber of times used per year  
GPU_14 GPU_14N = 4 Reported number of times used per year  
9996 GPU_14N = NA Population exclusions NA
9999 Else   NS

4. GPUD15Y - Uses hair dye - times peryear

Variable name:
GPUD15Y

Based on:
GPU_15, GPU_15N

Description:
The number of times per year the respondent uses hair dye.

Note:
Created in the Household Post-Verify process.

Table 4
GPUD15Y Specifications
Value Condition(s) Description Notes
0 GPU_15 = 0 Never  
GPU_15 * 365 GPU_15N = 1 Reported number of times used per day converted to derivednumber of times used per year  
GPU_15 * 52 GPU_15N = 2 Reported number of times used per week converted to derivednumber of times used per year  
GPU_15 * 12 GPU_15N = 3 Reported number of times used per month converted to derivednumber of times used per year  
GPU_15 GPU_15N = 4 Reported number of times used per year  
9996 GPU_15N = NA Population exclusions NA
9999 Else   NS

5. GPUD16Y - Uses hair style products -times per year

Variable name:
GPUD16Y

Based on:
GPU_16, GPU_16N

Description:
The number of times per year the respondent uses hair styleproducts.

Note:
Created in the Household Post-Verify process.

Table 5
GPUD16Y Specifications
Value Condition(s) Description Notes
0 GPU_16 = 0 Never  
GPU_16 * 365 GPU_16N = 1 Reported number of times used per day converted to derivednumber of times used per year  
GPU_16 * 52 GPU_16N = 2 Reported number of times used per week converted to derivednumber of times used per year  
GPU_16 * 12 GPU_16N = 3 Reported number of times used per month converted to derivednumber of times used per year  
GPU_16 GPU_16N = 4 Reported number of times used per year  
9996 GPU_16N = NA Population exclusions NA
9999 Else   NS

6. GPUD17Y - Uses manicure preparations- times per year

Variable name:
GPUD17Y

Based on:
GPU_17, GPU_17N

Description:
The number of times per year the respondent uses manicurepreparations.

Note:
Created in the Household Post-Verify process.

Table 6
GPUD17Y Specifications
Value Condition(s) Description Notes
0 GPU_17 = 0 Never  
GPU_17 * 365 GPU_17N = 1 Reported number of times used per day converted to derivednumber of times used per year  
GPU_17 * 52 GPU_17N = 2 Reported number of times used per week converted to derivednumber of times used per year  
GPU_17 * 12 GPU_17N = 3 Reported number of times used per month converted to derivednumber of times used per year  
GPU_17 GPU_17N = 4 Reported number of times used per year  
9996 GPU_17N = NA Population exclusions NA
9999 Else   NS

7. GPUD18Y - Uses scented body products- times per year

Variable name:
GPUD18Y

Based on:
GPU_18, GPU_18N

Description:
The number of times per year the respondent uses scented bodyproducts (including lotion, cream and body wash).

Note:
Created in the Household Post-Verify process.

Table 7
GPUD18Y Specifications
Value Condition(s) Description Notes
0 GPU_18 = 0 Never  
GPU_18 * 365 GPU_18N = 1 Reported number of times used per day converted to derivednumber of times used per year  
GPU_18 * 52 GPU_18N = 2 Reported number of times used per week converted to derivednumber of times used per year  
GPU_18 * 12 GPU_18N = 3 Reported number of times used per month converted to derivednumber of times used per year  
GPU_18 GPU_18N = 4 Reported number of times used per year  
9996 GPU_18N = NA Population exclusions NA
9999 Else   NS

Grip Strength (4 DVs)

1. GSCDELG - Eligibility - GripStrength component

Variable name:
GSCDELG

Based on:
ATG_33A, PHC_42H, MHR_611C, PAR_5A3B, PAR_5B3B, PAR_5C3B, PAR_5D3B,PAR_5E3B, PAR_5F3B, PAR_5G3B, PAR_5H3B, PAR_5I3B, PAR_5J3B,PAR_5K3B, PAR_62E, PAR_72B, ORS_1

Description:
This variable indicates whether the respondent was eligible for theGrip Strength Component. As there are multiple reasons to bescreened out of this measure, the prevalence of screen outs byreason should not be based on frequency counts for thisvariable.

Note:
Created in the Clinic Post-Verify process.

Table 1
GSCDELG Specifications
Value Condition(s) Description Notes
5 ATG_33A = 1 Not eligible - drank alcohol too close to visit time  
9 PHC_42H = 1 Not eligible - acute or chronic condition  
12 MHR_611C = 1 Not eligible - medication use  
13 PAR_5A3B = 1 or
PAR_5B3B = 1 or
PAR_5C3B = 1 or
PAR_5D3B = 1 or
PAR_5E3B = 1 or
PAR_5F3B = 1 or
PAR_5G3B = 1 or
PAR_5H3B = 1 or
PAR_5I3B = 1 or
PAR_5J3B = 1 or
PAR_5K3B = 1 or
PAR_62E = 1 or
PAR_72B = 1
Not eligible - PAR-Q answer  
14 ORS_1 = 1 Not eligible - other reason  
1 Else Eligible  

2. GSMD51 - Total hand gripstrength

Variable name:
GSMD51

Based on:
GSCDELG, GSM_11, GSM_12, GSM_21, GSM_22

Description:
This variable indicates the respondent's total hand gripstrength.

Note:
Created in the Clinic data collection application

Table 2
GSMD51 Specifications
Value Condition(s) Description Notes
999 (GSM_11 > NA and
GSM_21 > NA) or
(GSM_12 > NA and
GSM_22 > NA)
At least one required question was not answered (don'tknow, refusal, not stated) NS
996 (1 < GSCDELG < NA) Population exclusions NA
GSM_21 +
GSM_22
((0 < GSM_11 < NA) and
(0 < GSM_21 < NA) and
(0 < GSM_12 < NA) and
(0 < GSM_22 < NA) and
(GSM_11 < GSM_21) and
(GSM_12 < GSM_22)) or
((0 < GSM_11 < NA) and
(0 < GSM_21 < NA) and
(GSM_12 >= NA) and
(0 < GSM_22 < NA) and
(GSM_11 < GSM_21)) or
((GSM_11 >= NA) and
(0 < GSM_21 < NA) and
(0 < GSM_12 < NA) and
(0 < GSM_22 < NA) and
(GSM_12 < GSM_22)) or
((GSM_11 >= NA) and
(0 < GSM_21 < NA) and
(GSM_12 >= NA) and
(0 < GSM_22 < NA))
Second grip strength measurement for the right hand and theleft hand  
GSM_21 +
GSM_12
((0 < GSM_11 < NA) and
(0 < GSM_21 < NA) and
(0 < GSM_12 < NA) and
(0 < GSM_22 < NA) and
(GSM_11 < GSM_21) and
(GSM_12 >= GSM_22)) or
((0 < GSM_11 < NA) and
(0 < GSM_21 < NA) and
(0 < GSM_12 < NA) and
(GSM_22 >= NA) and
(GSM_11 < GSM_21)) or
((GSM_11 >= NA) and
(0 < GSM_21 < NA) and
(0 < GSM_12 < NA) and
(0 < GSM_22 < NA) and
(GSM_12 >= GSM_22)) or
((GSM_11 >= 996) and
(0 < GSM_21 < 996) and
(0 < GSM_12 < 996) and
(GSM_22 >= 996))
Second grip strength measurement for the right hand and firstgrip strength measurement for the left hand  
GSM_11 +
GSM_22
((0 < GSM_11 < NA) and
(0 < GSM_21 < NA) and
(0 < GSM_12 < NA) and
(0 < GSM_22 < NA) and
(GSM_11 >= GSM_21) and
(GSM_12 < GSM_22)) or
((0 < GSM_11 < NA) and
(0 < GSM_21 < NA) and
(GSM_12 >= NA) and
(0 < GSM_22 < NA) and
(GSM_11 >= GSM_21)) or
((0 < GSM_11 < NA) and
(GSM_21 >= NA) and
(0 < GSM_12 < NA) and
(0 < GSM_22 < NA) and
(GSM_12 < GSM_22)) or
((0 < GSM_11 < NA) and
(GSM_21 >= NA) and
(GSM_12 >= NA) and
(0 < GSM_22 < NA))
First grip strength measurement for the right hand and secondgrip strength measurement for the left hand  
GSM_11 +
GSM_12
((0 < GSM_11 < NA) and
(0 < GSM_21 < NA) and
(0 < GSM_12 < NA) and
(0 < GSM_22 < NA) and
(GSM_11 >= GSM_21) and
(GSM_12 >= GSM_22)) or
((0 < GSM_11 < NA) and
(0 < GSM_21 < NA) and
(0 < GSM_12 < NA) and
(GSM_22 >= NA) and
(GSM_11 >= GSM_21)) or
((0 < GSM_11 < NA) and
(GSM_21 >= NA) and
(0 < GSM_12 < NA) and
(0 < GSM_22 < NA) and
(GSM_12 >= GSM_22)) or
((0 < GSM_11 < NA) and
(GSM_21 >= NA) and
(0 < GSM_12 < NA) and
(GSM_22 >= NA))
First grip strength measurement for the right hand and the lefthand  

3. GSMD52 - Grip strength norms forrespondents 15 – 69

Variable name:
GSMD52

Based on:
CLC_AGE, CLC_SEX, GSMD51

Description:
This variable indicates the grip strength norms for respondents 15to 69 years of age.

Note:
Created in the Clinic data collection application

Source:
The Canadian Physical Activity, Fitness and Lifestyle Approach: 3rdEdition, 2003 by the Canadian Society for Exercise Physiology(CSEP)

Table 3
GSMD52 Specifications
Value Condition(s) Description Notes
6 CLC_AGE < 15 or
CLC_AGE > 69 or
GSMD51 = NA
Population exclusions NA
9 GSMD51 = NS At least one required question was not answered (don'tknow, refusal, not stated) NS
0 (CLC_SEX = 1 and
((CLC_AGE < 20 and
(0 < GSMD51 < 79)) or
((19 < CLC_AGE < 30) and
(0 < GSMD51 < 84)) or
((29 < CLC_AGE < 40) and
(0 < GSMD51 < 84)) or
((39 < CLC_AGE < 50) and
(0 < GSMD51 < 80)) or
((49 < CLC_AGE < 60) and
(0 < GSMD51 < 76)) or
((59 < CLC_AGE < 70) and
(0 < GSMD51 < 73)))) or
(CLC_SEX = 2 and
((CLC_AGE < 20 and
(0 < GSMD51 < 48)) or
((19 < CLC_AGE < 30) and
(0 < GSMD51 < 52)) or
((29 < CLC_AGE < 40) and
(0 < GSMD51 < 51)) or
((39 < CLC_AGE < 50) and
(0 < GSMD51 < 49)) or
((49 < CLC_AGE < 60) and
(0 < GSMD51 < 45)) or
((59 < CLC_AGE < 70) and
(0 < GSMD51 < 41))))
Needs improvement  
1 (CLC_SEX = 1 and
((CLC_AGE < 20 and
(78 < GSMD51 < 90)) or
((19 < CLC_AGE < 30) and
(83 < GSMD51 < 95)) or
((29 < CLC_AGE < 40) and
(83 < GSMD51 < 95)) or
((39 < CLC_AGE < 50) and
(79 < GSMD51 < 88)) or
((49 < CLC_AGE < 60) and
(75 < GSMD51 < 84)) or
((59 < CLC_AGE < 70) and
(72 < GSMD51 < 84)))) or
(CLC_SEX = 2 and
((CLC_AGE < 20 and
(47 < GSMD51 < 53)) or
((19 < CLC_AGE < 30) and
(51 < GSMD51 < 58)) or
((29 < CLC_AGE < 40) and
(50 < GSMD51 < 58)) or
((39 < CLC_AGE < 50) and
(48 < GSMD51 < 54)) or
((49 < CLC_AGE < 60) and
(44 < GSMD51 < 49)) or
((59 < CLC_AGE < 70) and
(40 < GSMD51 < 45))))
Fair  
2 (CLC_SEX = 1 and
((CLC_AGE < 20 and
(89 < GSMD51 < 98)) or
((19 < CLC_AGE < 30) and
(94 < GSMD51 < 104)) or
((29 < CLC_AGE < 40) and
(94 < GSMD51 < 104)) or
((39 < CLC_AGE < 50) and
(87 < GSMD51 < 97)) or
((49 < CLC_AGE < 60) and
(83 < GSMD51 < 92)) or
((59 < CLC_AGE < 70) and
(83 < GSMD51 < 91)))) or
(CLC_SEX = 2 and
((CLC_AGE < 20 and
(52 < GSMD51 < 60)) or
((19 < CLC_AGE < 30) and
(57 < GSMD51 < 63)) or
((29 < CLC_AGE < 40) and
(57 < GSMD51 < 63)) or
((39 < CLC_AGE < 50) and
(53 < GSMD51 < 61)) or
((49 < CLC_AGE < 60) and
(48 < GSMD51 < 54)) or
((59 < CLC_AGE < 70) and
(44 < GSMD51 < 48))))
Good  
3 (CLC_SEX = 1 and
((CLC_AGE < 20 and
(97 < GSMD51 < 108)) or
((19 < CLC_AGE < 30) and
(103 < GSMD51 < 115)) or
((29 < CLC_AGE < 40) and
(103 < GSMD51 < 115)) or
((39 < CLC_AGE < 50) and
(96 < GSMD51 < 108)) or
((49 < CLC_AGE < 60) and
(91 < GSMD51 < 101)) or
((59 < CLC_AGE < 70) and
(90 < GSMD51 < 100)))) or
(CLC_SEX = 2 and
((CLC_AGE < 20 and
(59 < GSMD51 < 68)) or
((19 < CLC_AGE < 30) and
(62 < GSMD51 < 70)) or
((29 < CLC_AGE < 40) and
(62 < GSMD51 < 71)) or
((39 < CLC_AGE < 50) and
(60 < GSMD51 < 69)) or
((49 < CLC_AGE < 60) and
(53 < GSMD51 < 61)) or
((59 < CLC_AGE < 70) and
(47 < GSMD51 < 54))))
Very good  
4 (CLC_SEX = 1 and
((CLC_AGE < 20) and
(107 < GSMD51 < NA)) or
((19 < CLC_AGE < 30) and
(114 < GSMD51 < NA)) or
((29 < CLC_AGE < 40) and
(114 < GSMD51 < NA)) or
((39 < CLC_AGE < 50) and
(107 < GSMD51 < NA)) or
((49 < CLC_AGE < 60) and
(100 < GSMD51 < NA)) or
((59 < CLC_AGE < 70) and
(99 < GSMD51 < NA)))) or
(CLC_SEX = 2 and
((CLC_AGE < 20 and
(67 < GSMD51 < NA)) or
((19 < CLC_AGE < 30) and
(69 < GSMD51 < NA)) or
((29 < CLC_AGE < 40) and
(70 < GSMD51 < NA)) or
((39 < CLC_AGE < 50) and
(68 < GSMD51 < NA)) or
((49 < CLC_AGE < 60) and
(60 < GSMD51 < NA)) or
((59 < CLC_AGE < 70) and
(53 < GSMD51 < NA))))
Excellent  

4. GSMD53 - Grip strength norms forrespondents less than 15

Variable name:
GSMD53

Based on:
CLC_AGE, CLC_SEX, GSMD51

Description:
This variable indicates the grip strength norms for respondentsless than 15 years of age.

Note:
Created in the Clinic data collection application

Source:
Stephens, T. & C.L. Craig. 1985. Fitness and activitymeasurement in the 1981 Canada Fitness Survey. In: Drury, T. (ed.).1989. Assessing physical fitness and activity patterns in generalpopulation surveys. Department of Health and Human Services, PublicHealth Service, Center for Disease Control, National Center forHealth Statistics. Hyattsville, MD. pub. No. (PHS) 89-1253.

Table 4
GSMD53 Specifications
Value Condition(s) Description Notes
6 CLC_AGE > 14 or
GSMD51 = NA
Population exclusions NA
9 GSMD51 = NS At least one required question was not answered (don'tknow, refusal, not stated) NS
1 (CLC_SEX = 1 and
(((6 < CLC_AGE < 10) and
(0 < GSMD51 < 28)) or
((9 < CLC_AGE < 13) and
(0 < GSMD51 < 43)) or
((12 < CLC_AGE < 15) and
(0 < GSMD51 < 61)))) or
(CLC_SEX = 2 and
(((6 < CLC_AGE < 10) and
(0 < GSMD51 < 26)) or
((9 < CLC_AGE < 13) and
(0 < GSMD51 < 36)) or
((12 < CLC_AGE < 15) and
(0 < GSMD51 < 52))))
Below average  
2 (CLC_SEX = 1 and
(((6 < CLC_AGE < 10) and
(27 < GSMD51 < 33)) or
((9 < CLC_AGE < 13) and
(42 < GSMD51 < 48)) or
((12 < CLC_AGE < 15) and
(60 < GSMD51 < 70)))) or
(CLC_SEX = 2 and
(((6 < CLC_AGE < 10) and
(25 < GSMD51 < 29)) or
((9 < CLC_AGE < 13) and
(35 < GSMD51 < 41)) or
((12 < CLC_AGE < 15) and
(51 < GSMD51 < 57))))
Average  
3 (CLC_SEX = 1 and
(((6 < CLC_AGE < 10) and
(32 < GSMD51 < NA)) or
((9 < CLC_AGE < 13) and
(47 < GSMD51 < NA)) or
((12 < CLC_AGE < 15) and
(69 < GSMD51 < NA)))) or
(CLC_SEX = 2 and
(((6 < CLC_AGE < 10) and
(28 < GSMD51 < NA)) or
((9 < CLC_AGE < 13) and
(40 < GSMD51 < NA)) or
((12 < CLC_AGE < 15) and
(56 < GSMD51 < NA))))
Above average  
5 CLC_AGE = 6 No norms for this age group  

Hobbies (10 DVs)

1. HOBD12Y - Arts - times peryear

Variable name:
HOBD12Y

Based on:
HOB_12, HOB_12N

Description:
The number of times per yearthe respondent did arts activities, including arts using paints,glazes, finger paints, water colours or crayons in his/her leisuretime or at school.

Note:
Created in the Household Post-Verify process.

Table 1
HOBD12Y Specifications
Value Condition(s) Description Notes
0 HOB_12 = 0 Never  
HOB_12 * 365 HOB_12N = 1 Reported number of times per day converted to derived number oftimes per year  
HOB_12 * 52 HOB_12N = 2 Reported number of times per week converted to derived numberof times per year  
HOB_12 * 12 HOB_12N = 3 Reported number of times per month converted to derived numberof times per year  
HOB_12 HOB_12N = 4 Reported number of times per year  
9996 HOB_12N = NA Population exclusions NA
9999 Else   NS

2. HOBD13Y - Pottery - times peryear

Variable name:
HOBD13Y

Based on:
HOB_13, HOB_13N

Description:
The number of times per year the respondent made pottery orceramics in his/her leisure time or at school.

Note:
Created in the Household Post-Verify process.

Table 2
HOBD13Y Specifications
Value Condition(s) Description Notes
0 HOB_13 = 0 Never  
HOB_13 * 365 HOB_13N = 1 Reported number of times per day converted to derived number oftimes per year  
HOB_13 * 52 HOB_13N = 2 Reported number of times per week converted to derived numberof times per year  
HOB_13 * 12 HOB_13N = 3 Reported number of times per month converted to derived numberof times per year  
HOB_13 HOB_13N = 4 Reported number of times per year  
9996 HOB_13N = NA Population exclusions NA
9999 Else   NS

3. HOBD14Y - Model making - times peryear

Variable name:
HOBD14Y

Based on:
HOB_14, HOB_14N

Description:
The number of times per year the respondent made models usingglues, solders, paints or metals in his/her leisure time or atschool.

Note:
Created in the Household Post-Verify process.

Table 3
HOBD14Y Specifications
Value Condition(s) Description Notes
0 HOB_14 = 0 Never  
HOB_14 * 365 HOB_14N = 1 Reported number of times per day converted to derived number oftimes per year  
HOB_14 * 52 HOB_14N = 2 Reported number of times per week converted to derived numberof times per year  
HOB_14 * 12 HOB_14N = 3 Reported number of times per month converted to derived numberof times per year  
HOB_14 HOB_14N = 4 Reported number of times per year  
9996 HOB_14N = NA Population exclusions NA
9999 Else   NS

4. HOBD15Y - Making fishing sinkers -times per year

Variable name:
HOBD15Y

Based on:
HOB_15, HOB_15N

Description:
The number of times per year the respondent made fishing sinkers orweights in his/her leisure time or at school.

Note:
Created in the Household Post-Verify process.

Table 4
HOBD15Y Specifications
Value Condition(s) Description Notes
0 HOB_15 = 0 Never  
HOB_15 * 365 HOB_15N = 1 Reported number of times per day converted to derived number oftimes per year  
HOB_15 * 52 HOB_15N = 2 Reported number of times per week converted to derived numberof times per year  
HOB_15 * 12 HOB_15N = 3 Reported number of times per month converted to derived numberof times per year  
HOB_15 HOB_15N = 4 Reported number of times per year  
9996 HOB_15N = NA Population exclusions NA
9999 Else   NS

5. HOBD16Y - Welding - times peryear

Variable name:
HOBD16Y

Based on:
HOB_16, HOB_16N

Description:
The number of times per year the respondent did welding orsoldering in his/her leisure time or at school.

Note:
Created in the Household Post-Verify process.

Table 5
HOBD16Y Specifications
Value Condition(s) Description Notes
0 HOB_16 = 0 Never  
HOB_16 * 365 HOB_16N = 1 Reported number of times per day converted to derived number oftimes per year  
HOB_16 * 52 HOB_16N = 2 Reported number of times per week converted to derived numberof times per year  
HOB_16 * 12 HOB_16N = 3 Reported number of times per month converted to derived numberof times per year  
HOB_16 HOB_16N = 4 Reported number of times per year  
9996 HOB_16N = NA Population exclusions NA
9999 Else   NS

6. HOBD17Y - Auto repairs - times peryear

Variable name:
HOBD17Y

Based on:
HOB_17, HOB_17N

Description:
The number of times per year the respondent did auto repairs inhis/her leisure time or at school.

Note:
Created in the Household Post-Verify process.

Table 6
HOBD17Y Specifications
Value Condition(s) Description Notes
0 HOB_17 = 0 Never  
HOB_17 * 365 HOB_17N = 1 Reported number of times per day converted to derived number oftimes per year  
HOB_17 * 52 HOB_17N = 2 Reported number of times per week converted to derived numberof times per year  
HOB_17 * 12 HOB_17N = 3 Reported number of times per month converted to derived numberof times per year  
HOB_17 HOB_17N = 4 Reported number of times per year  
9996 HOB_17N = NA Population exclusions NA
9999 Else   NS

7. HOBD18Y - Electronics - times peryear

Variable name:
HOBD18Y

Based on:
HOB_18, HOB_18N

Description:
The number of times per year the respondent did electronicsassembly or repairs of components in his/her leisure time or atschool.

Note:
Created in the Household Post-Verify process.

Table 7
HOBD18Y Specifications
Value Condition(s) Description Notes
0 HOB_18 = 0 Never  
HOB_18 * 365 HOB_18N = 1 Reported number of times per day converted to derived number oftimes per year  
HOB_18 * 52 HOB_18N = 2 Reported number of times per week converted to derived numberof times per year  
HOB_18 * 12 HOB_18N = 3 Reported number of times per month converted to derived numberof times per year  
HOB_18 HOB_18N = 4 Reported number of times per year  
9996 HOB_18N = NA Population exclusions NA
9999 Else   NS

8. HOBD19Y - Plumbing - times peryear

Variable name:
HOBD19Y

Based on:
HOB_19, HOB_19N

Description:
The number of times per year the respondent did plumbing in his/herleisure time or at school.

Note:
Created in the Household Post-Verify process.

Table 8
HOBD19Y Specifications
Value Condition(s) Description Notes
0 HOB_19 = 0 Never  
HOB_19 * 365 HOB_19N = 1 Reported number of times per day converted to derived number oftimes per year  
HOB_19 * 52 HOB_19N = 2 Reported number of times per week converted to derived numberof times per year  
HOB_19 * 12 HOB_19N = 3 Reported number of times per month converted to derived numberof times per year  
HOB_19 HOB_19N = 4 Reported number of times per year  
9996 HOB_19N = NA Population exclusions NA
9999 Else   NS

9. HOBD20Y - Refinishing furniture -times per year

Variable name:
HOBD20Y

Based on:
HOB_20, HOB_20N

Description:
The number of times per year the respondent refinished furniture inhis/her leisure time or at school.

Note:
Created in the Household Post-Verify process.

Table 9
HOBD20Y Specifications
Value Condition(s) Description Notes
0 HOB_20 = 0 Never  
HOB_20 * 365 HOB_20N = 1 Reported number of times per day converted to derived number oftimes per year  
HOB_20 * 52 HOB_20N = 2 Reported number of times per week converted to derived numberof times per year  
HOB_20 * 12 HOB_20N = 3 Reported number of times per month converted to derived numberof times per year  
HOB_20 HOB_20N = 4 Reported number of times per year  
9996 HOB_20N = NA Population exclusions NA
9999 Else   NS

10. HOBD21Y - Woodworking - times peryear

Variable name:
HOBD21Y

Based on:
HOB_21, HOB_21N

Description:
The number of times per year the respondent did woodworking inhis/her leisure time or at school.

Note:
Created in the Household Post-Verify process.

Table 10
HOBD21Y Specifications
Value Condition(s) Description Notes
0 HOB_21 = 0 Never  
HOB_21 * 365 HOB_21N = 1 Reported number of times per day converted to derived number oftimes per year  
HOB_21 * 52 HOB_21N = 2 Reported number of times per week converted to derived numberof times per year  
HOB_21 * 12 HOB_21N = 3 Reported number of times per month converted to derived numberof times per year  
HOB_21 HOB_21N = 4 Reported number of times per year  
9996 HOB_21N = NA Population exclusions NA
9999 Else   NS

Health utility index (HUI) (10DVs)

1. HUIDCOG - Cognition (FunctionCode)

Variable name:
HUIDCOG

Based on:
HUI_26, HUI_27

Description:
This variable classifies respondents based on their level ofcognitive problems.

Introduced in:
CCHS - Cycle 1.1

Table 1
HUIDCOG Specifications
Value Condition(s) Description Notes
99 (HUI_26 = DK, RF, NS) or
(HUI_27 = DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NS
1 HUI_26 = 1 and
HUI_27 = 1
No cognitive problems  
2 (HUI_26 = 1 and
HUI_27 = 2) or
(HUI_26 = 1 and
HUI_27 = 3)
A little difficulty thinking  
3 HUI_26 = 2 and
HUI_27 = 1
Somewhat forgetful  
4 (HUI_26 = 2 and
HUI_27 = 2) or
(HUI_26 = 2 and
HUI_27 = 3)
Somewhat forgetful / a little difficulty thinking  
5 (HUI_26 = 1 and
HUI_27 = 4) or
(HUI_26 = 2 and
HUI_27 = 4) or
(HUI_26 = 3 and
HUI_27 = 1) or
(HUI_26 = 3 and
HUI_27 = 2) or
(HUI_26 = 3 and
HUI_27 = 3) or
(HUI_26 = 3 and
HUI_27 = 4)
Very forgetful / great deal of difficulty thinking  
6 (HUI_26 = 1 and
HUI_27 = 5) or
(HUI_26 = 2 and
HUI_27 = 5) or
(HUI_26 = 3 and
HUI_27 = 5) or
(HUI_26 = 4 and
HUI_27 = 1) or
(HUI_26 = 4 and
HUI_27 = 2) or
(HUI_26 = 4 and
HUI_27 = 3) or
(HUI_26 = 4 and
HUI_27 = 4) or
(HUI_26 = 4 and
HUI_27 = 5)
Unable to remember and / or to think  

2. HUIDDEX - Dexterity Trouble(Function Code)

Variable name:
HUIDDEX

Based on:
HUI_21, HUI_22, HUI_23, HUI_24

Description:
This variable classifies the respondents based on their state ofdexterity trouble.

Introduced in:
CCHS - Cycle 1.1

Table 2
HUIDDEX Specifications
Value Condition(s) Description Notes
99 (HUI_21 = DK, RF, NS) or
(HUI_22 = DK, RF, NS) or
(HUI_23 = DK, RF, NS) or
(HUI_24 = DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NS
1 HUI_21 = 1 and
HUI_22 = 6 and
HUI_23 = 6 and
HUI_24 = 6
No dexterity problems  
2 HUI_21 = 2 and
HUI_22 = 2 and
HUI_23 = 6 and
HUI_24 = 2
Dexterity problem - no help required  
3 HUI_21 = 2 and
HUI_22 = 2 and
HUI_23 = 6 and
HUI_24 = 1
Dexterity problem - requires special equipment  
4 (HUI_21 = 2 and
HUI_22 = 1 and
HUI_23 = 1 and
HUI_24 = 1) or
(HUI_21 = 2 and
HUI_22 = 1 and
HUI_23 = 1 and
HUI_24 = 2)
Dexterity problem - requires help with some tasks  
5 (HUI_21 = 2 and
HUI_22 = 1 and
HUI_23 = 2 and
HUI_24 = 1) or
(HUI_21 = 2 and
HUI_22 = 1 and
HUI_23 = 2 and
HUI_24 = 2) or
(HUI_21 = 2 and
HUI_22 = 1 and
HUI_23 = 3 and
HUI_24 =1) or
(HUI_21 = 2 and
HUI_22 = 1 and
HUI_23 = 3 and
HUI_24 = 2)
Dexterity problem - requires help with most tasks  
6 (HUI_21 = 2 and
HUI_22 = 1 and
HUI_23 = 4 and
HUI_24 = 1) or
(HUI_21 = 2 and
HUI_22 = 1 and
HUI_23 = 4 and
HUI_24 = 2)
Dexterity problem - requires help with all tasks  

3. HUIDEMO - Emotional Problems(Function Code)

Variable name:
HUIDEMO

Based on:
HUI_25

Description:
This variable classifies the respondents based on their level ofemotional problems.

Introduced in:
CCHS - Cycle 1.1

Table 3
HUIDEMO Specifications
Value Condition(s) Description Notes
9 (HUI_25 = DK, RF, NS) At least one required question was not answered (don'tknow, refusal, not stated) NS
1 HUI_25 = 1 Happy and interested in life  
2 HUI_25 = 2 Somewhat happy  
3 HUI_25 = 3 Somewhat unhappy  
4 HUI_25 = 4 Very unhappy  
5 HUI_25 = 5 So unhappy that life is not worthwhile  

4. HUIDHER - Hearing Problems(Function Code)

Variable name:
HUIDHER

Based on:
HUI_06, HUI_07, HUI_07A, HUI_08, HUI_09

Description:
This variable classifies the respondents based on their hearingstate.

Introduced in:
CCHS - Cycle 1.1

Table 4
HUIDHER Specifications
Value Condition(s) Description Notes
99 (HUI_06 = DK, RF, NS) or
(HUI_07 = DK, RF, NS) or
(HUI_07A = DK, RF, NS) or
(HUI_08 = DK, RF, NS) or
(HUI_09 = DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NS
1 HUI_06 = 1 and
HUI_07 = 6 and
HUI_07A = 6 and
HUI_08 = 6 and
HUI_09 = 6
No hearing problems  
2 HUI_06 = 2 and
HUI_07 = 1 and
HUI_07A = 6 and
HUI_08 = 1 and
HUI_09 = 6
Problem hearing in group - corrected  
3 (HUI_06 = 2 and
HUI_07 = 1 and
HUI_07A = 6 and
HUI_08 = 2 and
HUI_09 = 1) or
(HUI_06 = 2 and
HUI_07 = 1 and
HUI_07A = 6 and
HUI_08 = 2 and
HUI_09 = 2)
Problem hearing in group and individual - corrected  
4 HUI_06 = 2 and
HUI_07 = 2 and
HUI_07A = 1 and
HUI_08 = 1 and
HUI_09 = 6
Problem hearing in group - not corrected  
5 HUI_06 = 2 and
HUI_07 = 2 and
HUI_07A = 1 and
HUI_08 = 2 and
HUI_09 = 1
Problem hearing in group and individual - individualcorrected  
6 (HUI_06 = 2 and
HUI_07 = 2 and
HUI_07A = 1 and
HUI_08 = 2 and
HUI_09 = 2) or
(HUI_06 = 2 and
HUI_07 = 2 and
HUI_07A = 2 and
HUI_08 = 6 and
HUI_09 = 6)
Cannot hear  

5. HUIDHSC - Health Utility Index -categorical variable

Variable name:
HUIDHSC

Based on:
HUIDHSI

Description:
This variable categorizes the respondent's HUI score into one offour categories: no disability, mild disability, moderatedisability or severe disability.

Table 5
HUIDHSC Specifications
Value Condition(s) Description Notes
9 HUIDHSI = NS At least one required question was not answered (don'tknow, refusal, not stated) NS
1 HUIDHSI = 1 No disability  
2 HUIDHSI >= 0.89 and
HUIDHSI < 1
Mild disability  
3 HUIDHSI >= 0.7 and
HUIDHSI < 0.89
Moderate disability  
4 HUIDHSI < 0.7 Severe disability  

6. HUIDHSI - Health UtilityIndex

Variable name:
HUIDHSI

Based on:
HUIDVIS, HUIDHER, HUIDSPE, HUIDMOB, HUIDDEX, HUIDEMO, HUIDCOG,HUIDPAD

Description:
The Health Status Index or Health Utility INDEX (HUI) is a generichealth status index that is able to synthesize both quantitativeand qualitative aspects of health. The index, developed at McMasterUniversity's Centre for Health Economics and Policy Analysis,is based on the Comprehensive Health Status Measurement System(CHSMS). It provides a description of an individual's overallfunctional health, based on eight attributes: vision, hearing,speech, mobility (ability to get around), dexterity (use of handsand fingers), cognition (memory and thinking), emotion (feelings),and pain and discomfort.

Introduced in:
CCHS - Cycle 1.1

Note:
In addition to describing functional health status levels, theCHSMS is the basis for HUI3. The HUI3 is a single numerical valuefor any possible combination of levels of these eight self-reportedhealth attributes. The HUI3 maps any one of the vectors of eighthealth attribute levels into a summary health value between -0.360and 1. For instance, an individual who is near-sighted, yet fullyhealthy on the other seven attributes, receives a score of 0.973.On that scale, the most preferred health level (perfect health) israted 1.000 and death is rated 0.000, while negative scores reflecthealth states considered worse than death.

The scores of the HUI embody the views of society concerninghealth status. These views are termed societal preferences, sincepreferences about various health states are elicited from arepresentative sample of individuals.

The HUI3 (Mark 3) was developed by McMaster University'sCentre for Health Economics and Policy Analysis, and is derivedusing societal preferences from a random sample of 500 peoplewithin the boundaries of the City of Hamilton-Wentworth, Ontario,Canada.

The algorithm mapping the questions to the CHSMS itself is theproperty of Health Utilities Inc. and is protected by copyright.Statistics Canada is authorized, when requested, to share thisalgorithm with users who wish to replicate results or analysesconducted by Statistics Canada. The use of the algorithm for otherpurposes, or the sharing of it with others, is prohibited.

Higher scale indicates better health index
Range: -0.360 to 1 in increments of 0.001
Reference: For a detailed explanation of the calculation of theHUI3, refer to:
-Furlong WJ, Feeny DH, Torrance GW. "Health Utilities Index (HUI):Algorithm for determining HUI Mark 2 (HUI2)/ Mark 3 (HUI3) healthstatus classification levels, health states, health-related qualityof life utility scores and single-attribute utility score from40-item interviewer-administered health status questionnaires."Dundas, Canada: Health Utilities Inc. February 1999.

-Furlong WJ, Feeny DH, Torrance GW, et al. "Multiplicativemulti-attribute utility function for the Health Utilities IndexMark 3 (HUI3) system: a technical report" Hamilton, Canada:McMaster University Centre for Health Economics and Policy AnalysisWorking Paper #98-11, December 1998.

7. HUIDMOB - Mobility Trouble(Function Code)

Variable name:
HUIDMOB

Based on:
HUI_14, HUI_15, HUI_16, HUI_17, HUI_18

Description:
This variable classifies the respondents based on their state ofmobility trouble.

Introduced in:
CCHS - Cycle 1.1

Table 7
HUIDMOB Specifications
Value Condition(s) Description Notes
99 (HUI_14 = DK, RF, NS) or
(HUI_15 = DK, RF, NS) or
(HUI_16 = DK, RF, NS) or
(HUI_17 = DK, RF, NS) or
(HUI_18 = DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NS
1 HUI_14 = 1 and
HUI_15 = 6 and
HUI_16 = 6 and
HUI_17 = 6 and
HUI_18 = 6
No mobility problems  
2 HUI_14 = 2 and
HUI_15 = 1 and
HUI_16 = 2 and
HUI_17 = 2 and
HUI_18 = 2
Problem - no aid required  
3 HUI_14 = 2 and
HUI_15 = 1 and
HUI_16 = 1 and
HUI_17 = 2 and
HUI_18 = 2
Problem - requires mechanical support  
4 (HUI_14 = 2 and
HUI_15 = 1 and
HUI_16 = 1 and
HUI_17 = 2 and
HUI_18 = 1) or
(HUI_14 = 2 and
HUI_15 = 1 and
HUI_16 = 2 and
HUI_17 = 2 and
HUI_18 = 1)
Problem - requires wheelchair  
5 (HUI_14 = 2 and
HUI_15 = 1 and
HUI_16 = 1 and
HUI_17 = 1 and
HUI_18 = 1) or
(HUI_14 = 2 and
HUI_15 = 1 and
HUI_16 = 1 and
HUI_17 = 1 and
HUI_18 = 2) or
(HUI_14 = 2 and
HUI_15 = 1 and
HUI_16 = 2 and
HUI_17 = 1 and
HUI_18 = 1) or
(HUI_14 = 2 and
HUI_15 = 1 and
HUI_16 = 2 and
HUI_17 = 1 and
HUI_18 = 2)
Problem - requires help from people  
6 (HUI_14 = 2 and
HUI_15 = 2 and
HUI_16 = 6 and
HUI_17 = 6 and
HUI_18 = 1) or
(HUI_14 = 2 and
HUI_15 = 2 and
HUI_16 = 6 and
HUI_17 = 6 and
HUI_18 = 2)
Cannot walk  

8. HUIDPAD - Activities Prevented /Pain (Function Code)

Variable name:
HUIDPAD

Based on:
HUI_28, HUI_30

Description:
This variable classifies the respondents based on their activitylimitation due to pain or discomfort.

Introduced in:
CCHS - Cycle 1.1

Table 8
HUIDPAD Specifications
Value Condition(s) Description Notes
9 (HUI_28 = DK, RF, NS) or
(HUI_30 = DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NS
1 HUI_28 = 1 and
HUI_30 = 6
No pain or discomfort  
2 HUI_28 = 2 and
HUI_30 = 1
Pain - does not prevent activity  
3 HUI_28 = 2 and
HUI_30 = 2
Pain prevents a few activities  
4 HUI_28 = 2 and
HUI_30 = 3
Pain prevents some activities  
5 HUI_28 = 2 and
HUI_30 = 4
Pain prevents most activities  

9. HUIDSPE - Speech Trouble (FunctionCode)

Variable name:
HUIDSPE

Based on:
HUI_10, HUI_11, HUI_12, HUI_13

Description:
This variable classifies the respondents based on their state ofspeech trouble.

Introduced in:
CCHS - Cycle 1.1

Table 9
HUIDSPE Specifications
Value Condition(s) Description Notes
9 (HUI_10 = DK, RF, NS) or
(HUI_11 = DK, RF, NS) or
(HUI_12 = DK, RF, NS) or
(HUI_13 = DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NS
1 HUI_10 = 1 and
HUI_11 = 6 and
HUI_12 = 6 and
HUI_13 = 6
No speech problems  
2 HUI_10 = 2 and
HUI_11 = 1 and
HUI_12 = 1 and
HUI_13 = 6
Partially understood by strangers  
3 HUI_10 = 2 and
HUI_11 = 1 and
HUI_12 = 2 and
HUI_13 = 1
Partially understood by friends  
4 (HUI_10 = 2 and
HUI_11 = 2 and
HUI_12 = 1 and
HUI_13 = 6) or
(HUI_10 = 2 and
HUI_11 = 2 and
HUI_12 = 2 and
HUI_13 = 1)
Not understood by strangers  
5 (HUI_10 = 2 and
HUI_11 = 1 and
HUI_12 = 2 and
HUI_13 = 2) or
(HUI_10 = 2 and
HUI_11 = 2 and
HUI_12 = 2 and
HUI_13 = 2)
Not understood by friends  

10. HUIDVIS - Vision Trouble (FunctionCode)

Variable name:
HUIDVIS

Based on:
HUI_01, HUI_02, HUI_03, HUI_04, HUI_05

Description:
This variable classifies the respondents based on their visionstate.

Introduced in:
CCHS - Cycle 1.1

Table 10
HUIDVIS Specifications
Value Condition(s) Description Notes
99 (HUI_01 = DK, RF, NS) or
(HUI_02 = DK, RF, NS) or
(HUI_03 = DK, RF, NS) or
(HUI_04 = DK, RF, NS) or
(HUI_05 = DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NS
1 HUI_01 = 1 and
HUI_02 = 6 and
HUI_03 = 6 and
HUI_04 = 1 and
HUI_05 = 6
No visual problems  
2 (HUI_01 = 1 and
HUI_02 = 6 and
HUI_03 = 6 and
HUI_04 = 2 and
HUI_05 = 1) or
(HUI_01 = 2 and
HUI_02 = 1 and
HUI_03 = 6 and
HUI_04 = 1 and
HUI_05 = 6) or
(HUI_01 = 2 and
HUI_02 = 1 and
HUI_03 = 6 and
HUI_04 = 2 and
HUI_05 = 1)
Problems corrected by lenses (distance, close, or both)  
3 (HUI_01 = 1 and
HUI_02 = 6 and
HUI_03 = 6 and
HUI_04 = 2 and
HUI_05 = 2) or
(HUI_01 = 2 and
HUI_02 = 1 and
HUI_03 = 6 and
HUI_04 = 2 and
HUI_05 = 2)
Problems seeing distance - not corrected  
4 (HUI_01 = 2 and
HUI_02 = 2 and
HUI_03 = 1 and
HUI_04 = 1 and
HUI_05 = 6) or
(HUI_01 = 2 and
HUI_02 = 2 and
HUI_03 = 1 and
HUI_04 = 2 and
HUI_05 = 1)
Problems seeing close - not corrected  
5 HUI_01 = 2 and
HUI_02 = 2 and
HUI_03 = 1 and
HUI_04 = 2 and
HUI_05 = 2
Problem seeing close and distance - not corrected  
6 HUI_01 = 2 and
HUI_02 = 2 and
HUI_03 = 2 and
HUI_04 = 6 and
HUI_05 = 6
No sight at all  

Height and weight (9 DVs)

1. HWTDBMI - Body Mass Index(self-reported)

Variable name:
HWTDBMI

Based on:
HWTDHTM, HWTDKG

Description:
Body Mass Index (BMI) is a comparison of "weight" relative to the"height" of respondents. BMI is calculated by dividing weightin kilograms by height in metres squared.
(BMI = WEIGHT (kilograms) / HEIGHT (metres) SQUARED)

Introduced in:
CCHS - Cycle 1.1

Note:
BMI is not calculated for pregnant women.
This BMI classification is created using "self-reported height" and"self-reported weight" variables.

Table 1
HWTDBMI Specifications
Value Condition(s) Description Notes
999.96 PRS_11 = 1 Population exclusion - Pregnant NA
999.99 HWTDHTM = NS or
HWTDKG = NS
Respondents for whom a valid self-reported height and weightwas not obtained NS
999.99 DHH_SEX = 2 and
(PRS_11 = DK, RF, NS)
Females who did not answer the pregnancy question (don'tknow, refusal, not stated) NS
Round(HWTDKG /
(HWTDHTM * HWTDHTM), .2)
HWTDHTM < NA and
HWTDKG < NA
BMI calculated from both self-reported height and self-reportedweight values Rounded to two decimal places

2. HWTDBMIA - BMI Classification forAdults Aged 18 and Over (self-reported) - InternationalStandard

Variable name:
HWTDBMIA

Based on:
HWMDBMI, CLC_AGE

Description:
This variable assigns adult respondents aged 18 and over (exceptpregnant women) to one of the following categories, according totheir Body Mass Index (BMI): underweight; normal weight;overweight; obese class I; obese class II; and, obese class III.Here, the BMI categories are adopted from a body weightclassification system recommended by Health Canada and the WorldHealth Organization (WHO) which has been widely usedinternationally.

Introduced in:
CCHS - Cycle 3.1

Note:
According to Health Canada, this BMI classification system can beused as a screening tool to identify weight-related risks at thepopulation and individual levels. The following health risksare associated with each of the BMI categories for adults aged 18and over:
normal weight = least health risk;
underweight and overweight = increased health risk;
obese class I = high health risk;
obese class II = very high health risk;
obese class III = extremely high health risk
At the population level, the BMI classification system can be usedto compare body weight patterns and related health risks within andbetween populations and to establish population trends in bodyweight patterns. The classification should be used withcaution at the individual level because the health risk associatedwith each BMI category varies considerably betweenindividuals. Particular caution should be used whenclassifying: adults who are naturally very lean, very muscularadults, some ethnic and racial groups, and seniors.
This variable excludes female respondents aged 18 and over who werepregnant.

Internet site:
http://www.hc-sc.gc.ca/hpfb-dgpsa/onpp-bppn/weight

Table 2
HWTDBMIA Specifications
Value Condition(s) Description Notes
99 HWTDBMI = NS or
(PRS_11 = DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NS
96 DHH_AGE < 18 or
PRS_11 = 1
Population exclusions NA
1 HWTDBMI < 18.50 Underweight  
2 (18.50 <= HWTDBMI <= 24.99) Normal weight  
3 (25.00 <= HWTDBMI <= 29.99) Overweight  
4 (30.00 <= HWTDBMI <= 34.99) Obese - Class I  
5 (35.00 <= HWTDBMI <= 39.99) Obese - Class II  
6 HWTDBMI >= 40.00 Obese - Class III  

Reference:
For more detailed information, see Canadian Guidelines for BodyWeight Classification in Adults, Health Canada, 2003.

3. HWTDBMIK - BMI Classification forChildren Less Than 18 Years of Age (self-reported) - CDCBMI-for-age

Variable name:
HWTDBMIK

Based on:
DHH_AGE, PRS_11, HWTDBMI

Description:
BMI growth charts can be used beginning at 2 years of age. BMI is calculated from weight and height measurements and is usedto determine whether an individual's weight is appropriate fortheir height. The growth charts consist of a series of percentilecurves illustrating the distribution of measurements in U.S.children. Most of the data used to construct the charts comesfrom the National Health and Nutrition Examination Survey (NHANES),which has periodically collected height and weight data (and otherhealth information) on the American population since the early1960's.

Note:
This variable excludes femalerespondents who were pregnant and respondents who were 18 years ofage or older.
In these charts, the following percentiles were selected as cutoffpoints:
5th percentile and below = underweight;
From the 6th percentile up to and including the 85th percentile =normal;
From the 86th percentile up to and including the 95th percentile =overweight;
Above the 95th percentile = obese.

Source:
http://www.cdc.gov/growthcharts

Table 3
HWTDBMIK Specifications
Value Condition(s) Description Notes
6 DHH_AGE >17 or
PRS_11 = 1
Population exclusions NA
9 HWTDBMI = NS or
(PRS_11 = DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NS
1 At and below the 5th percentile for the child's age in days,and sex Underweight  
2 Between the 6th and up to and including the 85th percentile forthe child's age in days, and sex Normal weight  
3 Between the 86th and up to and including the 95th percentilefor the child's age in days, and sex Overweight  
4 Above the 95th percentile for the child's age in days, andsex Obese  

4. HWTDCM - Height (centimetres) -self-reported

Variable name:
HWTDCM

Based on:
HWT_2, HWT_2A, HWT_2B, HWT_2C, HWT_2D, HWT_2E, HWT_2F, HWT_2G,HWTDIN

Description:
This variable contains the self-reported standing height incentimetres.

Note:
Created in the Household Post-Verify process.

Table 4
HWTDCM Specifications
Value Condition(s) Description Notes
0 HWT_2 = 0    
Round(HWTDIN * 2.54) HWT_2A < 12 or 
HWT_2B < 12 or
HWT_2C < 12 or
HWT_2D < 12 or
HWT_2E < 12 or
HWT_2F < 12 or
HWT_2G < 12
Self-reported standing height in centimetres  
999 Else   NS

5. HWTDCOL - BMI classification forchildren aged 6 to 17 (self-reported) - Cole classificationsystem

Variable name:
HWTDCOL

Based on:
HWTDBMI, CLC_SEX, CLC_AGE, age in months, age in days

Description:
This variable classifies children aged 6 to 17 (except femalerespondents aged 14 to 17 who were pregnant or did not answer thepregnancy question) as "obese", "overweight" or "neither obese oroverweight" according to the age-and-sex-specific BMI cut-offpoints as defined by Cole et al. The Cole cut-off points are basedon pooled international data (Brazil, Great Britain, Hong Kong,Netherlands, Singapore, and United States) for BMI and linked tothe widely internationally accepted adult BMI cut-off points of 25(overweight) and 30 (obese).

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents who do not fall within the categories of "Obese" or"Overweight" (as defined by Cole et al.) have been classified byCCHS and CHMS as "neither obese nor overweight". Thisvariable excludes respondents who are 18 years of age or over.

Table 5
HWTDCOL Temporary Reformat

AGET1

Value Condition(s) Description Notes
round(((mdy(C2_MONTH, C2_DAY, C2_YEAR) -mdy(DHH_MOB, DHH_DOB, DHH_YOB))/365.25), 0.5) Interview date converted to months (C2_MONTH, C2_DAY andC2_YEAR) - Date of birth converted in months (DHH_MOB, DHH_DOB andDHH_YOB) Create respondent's age in months at time of theinterview  
Table
HWTDCOL Specifications
Value Condition(s) Description Notes
9 HWTDBMI = NS or
(PRS_11 = DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NS
6 DHH_AGE > 17 or
PRS_11 = 1
Population exclusions NA
3 (AGET1 = 6 and
CLC_SEX = 1 and
HWMDBMI >= 19.78) or
(AGET1 = 6 and
CLC_SEX = 2 and
HWMDBMI >= 19.65) or
(AGET1 = 6.5 and
CLC_SEX = 1 and
HWMDBMI >= 20.23) or
(AGET1 = 6.5 and
CLC_SEX = 2 and
HWMDBMI >= 20.08) or
(AGET1 = 7 and
CLC_SEX = 1 and
HWMDBMI >= 20.63) or
(AGET1 = 7 and
CLC_SEX = 2 and
HWMDBMI >= 20.51) or
(AGET1 = 7.5 and
CLC_SEX = 1 and
HWMDBMI >= 21.09) or
(AGET1 = 7.5 and
CLC_SEX = 2 and
HWMDBMI >= 21.01) or
(AGET1 = 8 and
CLC_SEX = 1 and
HWMDBMI >= 21.60) or
(AGET1 = 8 and
CLC_SEX = 2 and
HWMDBMI >= 21.57) or
(AGET1 = 8.5 and
CLC_SEX = 1 and
HWMDBMI >= 22.17) or
(AGET1 = 8.5 and
CLC_SEX = 2 and
HWMDBMI >= 22.18) or
(AGET1 = 9 and
CLC_SEX = 1 and
HWMDBMI >= 22.77) or
(AGET1 = 9 and
CLC_SEX = 2 and
HWMDBMI >= 22.81) or
(AGET1 = 9.5 and
CLC_SEX = 1 and
HWMDBMI >= 23.39) or
(AGET1 = 9.5 and
CLC_SEX = 2 and
HWMDBMI >= 23.46) or
(AGET1 = 10 and
CLC_SEX = 1 and
HWMDBMI >= 24.00) or
(AGET1 = 10 and
CLC_SEX = 2 and
HWMDBMI >= 24.41) or
(AGET1 = 10.5 and
CLC_SEX = 1 and
HWMDBMI >= 24.57) or
(AGET1 = 10.5 and
CLC_SEX = 2 and
HWMDBMI >= 24.77) or
(AGET1 = 11 and
CLC_SEX = 1 and
HWMDBMI >= 25.10) or
(AGET1 = 11 and
CLC_SEX = 2 and
HWMDBMI >= 24.42) or
(AGET1 = 11.5 and
CLC_SEX = 1 and
HWMDBMI >= 25.58) or
(AGET1 = 11.5 and
CLC_SEX = 2 and
HWMDBMI >= 26.05) or
(AGET1 = 12 and
CLC_SEX = 1 and
HWMDBMI >= 26.02) or
(AGET1 = 12 and
CLC_SEX = 2 and
HWMDBMI >= 26.67) or
(AGET1 = 12.5 and
CLC_SEX = 1 and
HWMDBMI >= 26.43) or
(AGET1 = 12.5 and
CLC_SEX = 2 and
HWMDBMI >= 27.24) or
(AGET1 = 13 and
CLC_SEX = 1 and
HWMDBMI >= 26.84) or
(AGET1 = 13 and
CLC_SEX = 2 and
HWMDBMI >= 27.76) or
(AGET1 = 13.5 and
CLC_SEX = 1 and
HWMDBMI >= 27.25) or
(AGET1 = 13.5 and
CLC_SEX = 2 and
HWMDBMI >= 28.20) or
(AGET1 = 14 and
CLC_SEX = 1 and
HWMDBMI >= 27.63) or
(AGET1 = 14 and
CLC_SEX = 2 and
HWMDBMI >= 28.57) or
(AGET1 = 14.5 and
CLC_SEX = 1 and
HWMDBMI >= 27.98) or
(AGET1 = 14.5 and
CLC_SEX = 2 and
HWMDBMI >= 28.87) or
(AGET1 = 15 and
CLC_SEX = 1 and
HWMDBMI >= 28.30) or
(AGET1 = 15 and
CLC_SEX = 2 and
HWMDBMI >= 29.11) or
(AGET1 = 15.5 and
CLC_SEX = 1 and
HWMDBMI >= 28.60) or
(AGET1 = 15.5 and
CLC_SEX = 2 and
HWMDBMI >= 29.29) or
(AGET1 = 16 and
CLC_SEX = 1 and
HWMDBMI >= 28.88) or
(AGET1 = 16 and
CLC_SEX = 2 and
HWMDBMI >= 29.43) or
(AGET1 = 16.5 and
CLC_SEX = 1 and
HWMDBMI >= 29.14) or
(AGET1 = 16.5 and
CLC_SEX = 2 and
HWMDBMI >= 29.56) or
(AGET1 = 17 and
CLC_SEX = 1 and
HWMDBMI >= 29.41) or
(AGET1 = 17 and
CLC_SEX = 2 and
HWMDBMI >= 29.69) or
(AGET1 = 17.5 and
CLC_SEX = 1 and
HWMDBMI >= 29.70) or
(AGET1 = 17.5 and
CLC_SEX = 2 and
HWMDBMI >= 29.84) or
(AGET1 = 18 and
CLC_SEX = 1 and
HWMDBMI >= 30.00) or
(AGET1 = 18 and
CLC_SEX = 2 and
HWMDBMI >= 30.00)
Obese  
2 (AGET1 = 6 and
CLC_SEX = 1 and
(HWMDBMI >= 17.55 and
HWMDBMI < 19.78)) or
(AGET1 = 6 and
CLC_SEX = 2 and
(HWMDBMI >= 17.34 and
HWMDBMI < 19.65)) or
(AGET1 = 6.5 and
CLC_SEX = 1 and
(HWMDBMI >= 17.71 and
HWMDBMI < 20.23)) or
(AGET1 = 6.5 and
CLC_SEX = 2 and
(HWMDBMI >= 17.53 and
HWMDBMI < 20.08)) or
(AGET1 = 7 and
CLC_SEX = 1 and
(HWMDBMI >= 17.92 and
HWMDBMI < 20.63)) or
(AGET1 = 7 and
CLC_SEX = 2 and
(HWMDBMI >= 17.75 and
HWMDBMI < 20.51)) or
(AGET1 = 7.5 and
CLC_SEX = 1 and
(HWMDBMI >= 18.16 and
HWMDBMI < 21.09)) or
(AGET1 = 7.5 and
CLC_SEX = 2 and
(HWMDBMI >= 18.03 and
HWMDBMI < 21.01)) or
(AGET1 = 8 and
CLC_SEX = 1 and
(HWMDBMI >= 18.44 and
HWMDBMI < 21.60)) or
(AGET1 = 8 and
CLC_SEX = 2 and
(HWMDBMI >= 18.35 and
HWMDBMI < 21.57)) or
(AGET1 = 8.5 and
CLC_SEX = 1 and
(HWMDBMI >= 18.76 and
HWMDBMI < 22.17)) or
(AGET1 = 8.5 and
CLC_SEX = 2 and
(HWMDBMI >= 18.69 and
HWMDBMI < 22.18)) or
(AGET1 = 9 and
CLC_SEX = 1 and
(HWMDBMI >= 19.10 and
HWMDBMI < 22.77)) or
(AGET1 = 9 and
CLC_SEX = 2 and
(HWMDBMI >= 19.07 and
HWMDBMI < 22.81)) or
(AGET1 = 9.5 and
CLC_SEX = 1 and
(HWMDBMI >= 19.46 and
HWMDBMI < 23.39)) or
(AGET1 = 9.5 and
CLC_SEX = 2 and
(HWMDBMI >= 19.45 and
HWMDBMI < 23.46)) or
(AGET1 = 10 and
CLC_SEX = 1 and
(HWMDBMI >= 19.84 and
HWMDBMI < 24.00)) or
(AGET1 = 10 and
CLC_SEX = 2 and
(HWMDBMI >= 19.86 and
HWMDBMI < 24.11)) or
(AGET1 = 10.5 and
CLC_SEX = 1 and
(HWMDBMI >= 20.20 and
HWMDBMI < 24.57)) or
(AGET1 = 10.5 and
CLC_SEX = 2 and
(HWMDBMI >= 20.29 and
HWMDBMI < 24.77)) or
(AGET1 = 11 and
CLC_SEX = 1 and
(HWMDBMI >= 20.55 and
HWMDBMI < 25.10)) or
(AGET1 = 11 and
CLC_SEX = 2 and
(HWMDBMI >= 20.74 and
HWMDBMI < 25.42)) or
(AGET1 = 11.5 and
CLC_SEX = 1 and
(HWMDBMI >= 20.89 and
HWMDBMI < 25.58)) or
(AGET1 = 11.5 and
CLC_SEX = 2 and
(HWMDBMI >= 21.20 and
HWMDBMI < 26.05)) or
(AGET1 = 12 and
CLC_SEX = 1 and
(HWMDBMI >= 21.22 and
HWMDBMI < 26.02)) or
(AGET1 = 12 and
CLC_SEX = 2 and
(HWMDBMI >= 21.68 and
HWMDBMI < 26.67)) or
(AGET1 = 12.5 and
CLC_SEX = 1 and
(HWMDBMI >= 21.56 and
HWMDBMI < 26.43)) or
(AGET1 = 12.5 and
CLC_SEX = 2 and
(HWMDBMI >= 22.14 and
HWMDBMI < 27.24)) or
(AGET1 = 13 and
CLC_SEX = 1 and
(HWMDBMI >= 21.91 and
HWMDBMI < 26.84)) or
(AGET1 = 13 and
CLC_SEX = 2 and
(HWMDBMI >= 22.58 and
HWMDBMI < 27.76)) or
(AGET1 = 13.5 and
CLC_SEX = 1 and
(HWMDBMI >= 22.27 and
HWMDBMI < 27.25)) or
(AGET1 = 13.5 and
CLC_SEX = 2 and
(HWMDBMI >= 22.98 and
HWMDBMI < 28.20)) or
(AGET1 = 14 and
CLC_SEX = 1 and
(HWMDBMI >= 22.62 and
HWMDBMI < 27.63)) or
(AGET1 = 14 and
CLC_SEX = 2 and
(HWMDBMI >= 23.34 and
HWMDBMI < 28.57)) or
(AGET1 = 14.5 and
CLC_SEX = 1 and
(HWMDBMI >= 22.96 and
HWMDBMI < 27.98)) or
(AGET1 = 14.5 and
CLC_SEX = 2 and
(HWMDBMI >= 23.66 and
HWMDBMI < 28.87)) or
(AGET1 = 15 and
CLC_SEX = 1 and
(HWMDBMI >= 23.29 and
HWMDBMI < 28.30)) or
(AGET1 = 15 and
CLC_SEX = 2 and
(HWMDBMI >= 23.94 and
HWMDBMI < 29.11)) or
(AGET1 = 15.5 and
CLC_SEX = 1 and
(HWMDBMI >= 23.60 and
HWMDBMI < 28.60)) or
(AGET1 = 15.5 and
CLC_SEX = 2 and
(HWMDBMI >= 24.17 and
HWMDBMI < 29.29)) or
(AGET1 = 16 and
CLC_SEX = 1 and
(HWMDBMI >= 23.90 and
HWMDBMI < 28.88)) or
(AGET1 = 16 and
CLC_SEX = 2 and
(HWMDBMI >= 24.37 and
HWMDBMI < 29.43)) or
(AGET1 = 16.5 and
CLC_SEX = 1 and
(HWMDBMI >= 24.19 and
HWMDBMI < 29.14)) or
(AGET1 = 16.5 and
CLC_SEX = 2 and
(HWMDBMI >= 24.54 and
HWMDBMI < 29.56)) or
(AGET1 = 17 and
CLC_SEX = 1 and
(HWMDBMI >= 24.46 and
HWMDBMI < 29.41)) or
(AGET1 = 17 and
CLC_SEX = 2 and
(HWMDBMI >= 24.70 and
HWMDBMI < 29.69)) or
(AGET1 = 17.5 and
CLC_SEX = 1 and
(HWMDBMI >= 24.73 and
HWMDBMI < 29.70)) or
(AGET1 = 17.5 and
CLC_SEX = 2 and
(HWMDBMI >= 24.85 and
HWMDBMI < 29.84)) or
(AGET1 = 18 and
CLC_SEX = 1 and
(HWMDBMI >= 25.00 and
HWMDBMI < 30.00)) or
(AGET1 = 18 and
CLC_SEX = 2 and
(HWMDBMI >= 25.00 and
HWMDBMI < 30.00))
Overweight  
1 Else Neither overweight nor obese  

Reference:
For more information about the Cole BMI classification system, seeEstablishing a Standard Definition for Child Overweight and ObesityWorldwide - International survey, by Tim J Cole, Mary C Bellizzi,Katherine M. Flegal, William H Dietz, published in British MedicalJournal, Volume: 320, May 2000.

6. HWTDHTM - Height (metres) -self-reported

Variable name:
HWTDHTM

Based on:
HWTDCM

Description:
This variable indicates the respondent's self-reported heightin metres.

Introduced in:
CCHS - Cycle 1.1

Table 6
HWTDHTM Specifications
Value Condition(s) Description Notes
9.99 HWTDCM = NS At least one required question was not answered (don't know, refusal, not stated) NS
HWTDCM/100 Else Self-reported height in metres  

7. HWTDIN - Height (inches) -self-reported

Variable name:
HWTDIN

Based on:
HWT_2, HWT_2A, HWT_2B, HWT_2C, HWT_2D, HWT_2E, HWT_2F, HWT_2G

Description:
This variable contains the self-reported standing height ininches.

Note:
Created in the Household Post-Verify process

Table 7
HWTDIN Specifications
Value Condition(s) Description Notes
0 HWT_2 = 0 Less than 12”  
HWT_2A + 12 HWT_2A < 12 Between 12” and 23”  
HWT_2B + 24 HWT_2B < 12 Between 24” and 35”  
HWT_2C + 36 HWT_2C < 12 Between 36” and 47”  
HWT_2D + 48 HWT_2D < 12 Between 48” and 59”  
HWT_2E + 60 HWT_2E < 12 Between 60” and 71”  
HWT_2F + 72 HWT_2F < 12 Between 72” and 83”  
HWT_2G + 84 HWT_2G < 12 Between 84” and 95”  
99 Else   NS

8. HWTDKG - Weight (kilograms) -self-reported

Variable name:
HWTDKG

Based on:
HWT_3, HWT_3N, PRS_11

Description:
This variable contains the self-reported weight in kilograms.

Introduced in:
CCHS - Cycle 1.1

Note:
Created in the Household Post-Verify process.  This variableexcludes female respondents who were pregnant.

Table 8
HWTDKG Specifications
Value Condition(s) Description Notes
996 PRS_11 = 1 Population exclusions NA
Round(HWT_3 * 0.4536) HWT_3N = 1 Self-reported weight in pounds converted to kilograms  
HWT_3 HWT_3N = 2 Self-reported weight in kilograms  
999 Else   NS

9. HWTDLB - Weight (pounds) -self-reported

Variable name:
HWTDLB

Based on:
HWT_3, HWT_3N, PRS_11

Description:
This variable contains the self-reported weight in pounds.

Note:
Created in the Household Post-Verify process. This variableexcludes female respondents who were pregnant.

Table 9
HWTDLB Specifications
Value Condition(s) Description Notes
996 PRS_11 = 1 Population exclusions NA
HWT_3 HWT_3N = 1 Self-reported weight in pounds  
Round(HWT_3 * 2.205) HWT_3N = 2 Self-reported weight in kilograms converted to pounds  
999 Else   NS

Income (5 DVs)

1. INCDDIA2 - Total household income- 2 categories

Variable name:
INCDDIA2

Based on:
DHHDHSZ, INCDHH

Description:
This variable classifies the total household income into twocategories based on total household income and the number of peopleliving in the household.

Introduced in:
NPHS - Cycle 1

Table 1
INCDDIA2 Specifications
Value Condition(s) Description Notes
1 (DHHDHSZ in (1,2) and
INCDHH in (1,2,3,4)) or
(DHHDHSZ in (3,4) and
INCDHH in (1,2,3,4,5)) or
(DHHDHSZ > 4 and
INCDHH in (1,2,3,4,5,6))
Low income  
2 (DHHDHSZ in (1,2) and
INCDHH in (5,6,7,8,9,10,11,12)) or
(DHHDHSZ in (3,4) and
INCDHH in (6,7,8,9,10,11,12)) or
(DHHDHSZ > 4 and
INCDHH in (7,8,9,10,11,12))
Middle or high income  
9 Else Not enough information for the classification NS

2. INCDDIA4 - Total household income -4 categories

Variable name:
INCDDIA4

Based on:
DHHDHSZ, INCDHH

Description:
This variable classifies the total household income into fourcategories based on total household income and the number of peopleliving in the household.

Introduced in:
NPHS - Cycle 1

Table 2
INCDDIA4 Specifications
Value Condition(s) Description Notes
1 (DHHDHSZ in (1,2) and
INCDHH in (1,2,3,4)) or
(DHHDHSZ in (3,4) and
INCDHH in (1,2,3,4,5)) or
(DHHDHSZ > 4 and
INCDHH in (1,2,3,4,5,6))
Lowest income grouping  
2 (DHHDHSZ in (1,2) and
INCDHH in (5,6)) or
(DHHDHSZ in (3,4) and
INCDHH in (6,7)) or
(DHHDHSZ > 4 and
INCDHH in (7,8,9))
Lower middle income grouping  
3 (DHHDHSZ in (1,2) and
INCDHH in (7,8,9)) or
(DHHDHSZ in (3,4) and
INCDHH in (8,9,10)) or
(DHHDHSZ > 4 and
INCDHH in (10))
Upper middle income grouping  
4 (DHHDHSZ in (1,2) and
INCDHH in (10,11,12)) or
(DHHDHSZ > 2 and
INCDHH in (11,12))
Highest income grouping  
9 Else Not enough information for the classification NS

3. INCDDIA5 - Total household income -5 categories

Variable name:
INCDDIA5

Based on:
DHHDHSZ, INCDHH

Description:
This variable classifies the total household income into fivecategories based on total household income and the number of peopleliving in the household.

Introduced in:
NPHS - Cycle 1

Table 3
INCDDIA5 Specifications
Value Condition(s) Description Notes
1 (DHHDHSZ in (1,2,3,4) and
INCDHH in (1,2,3)) or
(DHHDHSZ > 4 and
INCDHH in (1,2,3,4))
Lowest income grouping  
2 (DHHDHSZ in (1,2) and
INCDHH in (4)) or
(DHHDHSZ in (3,4) and
INCDHH in (4,5)) or
(DHHDHSZ > 4 and
INCDHH in (5,6))
Lower middle income grouping  
3 (DHHDHSZ in (1,2) and
INCDHH in (5,6)) or
(DHHDHSZ in (3,4) and
INCDHH in (6,7)) or
(DHHDHSZ > 4 and
INCDHH in (7,8,9))
Middle income grouping  
4 (DHHDHSZ in (1,2) and
INCDHH in (7,8,9)) or
(DHHDHSZ in (3,4) and
INCDHH in (8,9,10)) or
(DHHDHSZ > 4 and
INCDHH in (10))
Upper middle income grouping  
5 (DHHDHSZ in (1,2) and
INCDHH in (10,11,12)) or
(DHHDHSZ > 2 and
INCDHH in (11,12))
Highest income grouping  
9 Else Not enough information for the classification NS

4. INCDHH - Total Household Income -All Sources

Variable name:
INCDHH

Based on:
INC_22, INC_23, INC_24, INC_25, INC_26, INC_27, INC_28

Description:
This variable groups the total household income from all sources. Arange value was assigned by the application to respondents whoprovided an exact amount in question INC_21.

Introduced in:
CCHS - Cycle 1.1

Table 4
INCDHH Specifications
Value Condition(s) Description Notes
99 (INC_22 = DK, RF, NS) None of the income questions were answered (don't know,refusal, not stated) NS
1 INC_22 = 3 No income  
2 INC_24 = 1 Less than $5,000  
3 INC_24 = 2 $5,000 to $9,999  
4 INC_25 = 1 $10,000 to $14,999  
5 INC_25 = 2 $15,000 to $19,999  
6 INC_27 = 1 $20,000 to $29,999  
7 INC_27 = 2 $30,000 to $39,999  
8 INC_28 = 1 $40,000 to $49,999  
9 INC_28 = 2 $50,000 to $59,999  
10 INC_28 = 3 $60,000 to $79,999  
11 INC_28 = 4 $80,000 to $99,999  
12 INC_28 = 5 $100,000 +  
99 Else Not enough information for the classification NS

5. INCDPER - Personal Income - AllSources

Variable name:
INCDPER

Based on:
INC_32, INC_34, INC_35, INC_37, INC_38

Description:
This variable indicates the respondent's personal income fromall sources. A range value was assigned by the application torespondents who provided an exact amount in question INC_31.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents less than 15 years old were excluded from thepopulation.

Table 5
INCDPER Specifications
Value Condition(s) Description Notes
96 DHH_AGE < 15 Population exclusions NA
99 (INC_32 = DK, RF, NS) None of the income questions were answered (don't know,refusal, not stated) NS
1 (INC_32 = 3, NA) No income  
2 INC_34 = 1 Less than $5,000  
3 INC_34 = 2 $5,000 to $9,999  
4 INC_35 = 1 $10,000 to $14,999  
5 INC_35 = 2 $15,000 to $19,999  
6 INC_37 = 1 $20,000 to $29,999  
7 INC_37 = 2 $30,000 to $39,999  
8 INC_38 = 1 $40,000 to $49,999  
9 INC_38 = 2 $50,000 to $59,999  
10 INC_38 = 3 $60,000 to $79,999  
11 INC_38 = 4 $80,000 to $99,999  
12 INC_38 = 5 $100,000 +  
99 Else Not enough information for the classification NS

Labour force (8 DVs)

1. LBFDHPW - Total usual hoursworked per week

Variable name:
LBFDHPW

Based on:
DHH_AGE, LBF_42, LBF_53

Description:
This variable indicates the total number of hours the respondentworked per week.

Introduced in:
CCHS - Cycle 3.1

Note:
Respondents aged less than 15 or more than 75 years old or who didnot answer whether they had worked in the year preceding theinterview have been excluded from the population.

Table 1
LBFDHPW Specifications
Value Condition(s) Description Notes
996 DHH_AGE < 15 or
DHH_AGE > 75 or
LBF_42 = NA
Population exclusion NA
999 (LBF_42 = DK, RF, NS) or
(LBF_53 = DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NS
LBF_42 LBF_42 < NA and
LBF_53 = NA
Number of hours usually worked for respondents with onejob  
LBF_42 +
LBF_53
LBF_42 < NA and
LBF_53 < NA
Number of hours usually worked for respondents with more thanone job  

2. LBFDJST - Job status over pastyear

Variable name:
LBFDJST

Based on:
DHH_AGE, LBF_01, LBF_11, LBF_22, LBF_61, LBF_71

Description:
This variable indicates the respondent's job status over thepast year.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents aged less than 15 or more than 75 years old or who didnot work in the week preceding the interview were excluded from thepopulation.

Table 2
LBFDJST Specifications
Value Condition(s) Description Notes
96 LBF_01 = NA or
DHH_AGE < 15 or
DHH_AGE > 75
Population exclusion NA
99 (LBF_22 = DK, RF, NS) or
(LBF_61 = DK, RF, NS) or
(LBF_71 = DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NS
1 LBF_61 = 52 Has had a job throughout the past year  
2 LBF_71 = 52 Was without a job and looking for work throughout the pastyear  
3 LBF_22 = 2 Was without a job and not looking for work throughout pastyear  
4 (LBF_61 + LBF_71) = 52 and
(0 < LBF_71 < 52) and
LBF_61 < 52
Has had a job part of the year - was without a job and lookingfor other part of the year  
5 LBF_61 < 52 and
LBF_71 = 0
Has had a job part of the year - was without a job and notlooking for other part of the year  
6 LBF_71 < 52 and
LBF_21 = 2 and
(LBF_11 = 1 or
LBF_22 = 1)
Was without a job and looking for part of the year - waswithout a job and not looking for other part of the year  
7 (LBF_61 + LBF_71) < 52 and
(0 < LBF_71 < 52) and
LBF_61 < 52
Has had a job part of the year - was without a job and lookingfor part of the year - was without a job and not looking for otherpart of year  

3. LBFDMJS - Multiple jobstatus

Variable name:
LBFDMJS

Based on:
DHH_AGE, LBF_03, LBF_21, LBF_23, LBF_51

Description:
This variable classifies respondents based on whether or not theyhad multiple jobs in the past year and if they still do.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents aged less than 15 or more than 75 years old have beenexcluded from the population.

Table 3
LBFDMJS Specifications
Value Condition(s) Description Notes
6 DHH_AGE < 15 or
DHH_AGE > 75
Population exclusion NA
9 (LBF_03 = DK, RF, NS) or
(LBF_21 = DK, RF, NS) or
(LBF_23 = DK, RF, NS) or
(LBF_51 = DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NS
1 LBF_51 = 52 Currently has multiple jobs - had them all past year  
2 LBF_03 = 1 and
LBF_51 < 52
Currently has multiple jobs - did not have them all pastyear  
3 LBF_03 = 2 Currently has only one job  
4 LBF_23 = 1 Currently does not have a job - held multiple jobs over pastyear  
5 LBF_23 = 2 or
LBF_21 = 2
Currently does not have a job - did not hold multiple jobs overthe year  

4. LBFDPFT - Full-time/ part-timeworking status (for total usual hours)

Variable name:
LBFDPFT

Based on:
LBFDHPW

Description:
This variable indicates if the respondent works full-time orpart-time.

Introduced in:
CCHS - Cycle 3.1

Note:
Respondents aged less than 15 or more than 75 years old or who didnot work in the year preceding the interview have been excludedfrom the population.

Table 4
LBFDPFT Specifications
Value Condition(s) Description Notes
6 LBFDHPW = NA Population exclusion NA
9 LBFDHPW = NS At least one required question was not answered (don'tknow, refusal, not stated) NS
1 LBFDHPW >= 30 Full-time  
2 LBFDHPW < 30 Part-time  

5. LBFDRNW - Main reason for notworking last week

Variable name:
LBFDRNW

Based on:
DHH_AGE, LBF_01, LBF_11, LBF_13, LBF_41

Description:
This variable indicates the main reason why the respondent did notwork in the week prior to the interview.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents aged less than 15 or more than 75 years old or who didnot work in the week preceding the interview have been excludedfrom the population.

Table 5
LBFDRNW Specifications
Value Condition(s) Description Notes
96 DHH_AGE < 15 or
DHH_AGE > 75 or
LBF_01 = 1
Population exclusion NA
99 (LBF_11 = DK, RF, NS) or
(LBF_13 = DK, RF, NS) or
(LBF_41 = DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NS
1 LBF_01 = 3 Permanently unable to work  
2 LBF_13 = 1 or
LBF_41 = 1
Own illness or disability  
3 LBF_13 = 2 or
LBF_41 = 2
Caring for - own children  
4 LBF_13 = 3 or
LBF_41 = 3
Caring for - elder relative  
5 LBF_13 = 4 or
LBF_41 = 4
Pregnancy/ maternity leave  
6 LBF_13 = 5 or
LBF_41 = 5
Other personal or family responsibilities  
7 LBF_13 = 6 or
LBF_41 = 6
Vacation  
8 LBF_13 = 7 or
LBF_41 = 14
School or educational leave  
9 LBF_13 = 8 Retired  
10 LBF_13 = 9 Believes no work is available (in area or suited toskills)  
11 LBF_41 = 7 Labour dispute  
12 LBF_41 = 8 Temporary layoff due to business conditions  
13 LBF_41 = 9 Seasonal layoff  
14 LBF_41 = 10 Casual job, no work available  
15 LBF_41 = 12 Self-employed, no work available  
16 LBF_41 = 13 Seasonal business  
17 LBF_11 = 1 Looking for work  
18 LBF_41 = 11 Work schedule  
19 LBF_13 = 10 or
LBF_41 = 15
Other reason  

6. LBFDSTU - Student workingstatus

Variable name:
LBFDSTU

Based on:
DHH_AGE, EDU_01, EDU_02, LBF_01, LBF_02, LBF_21

Description:
This variable indicates the respondent's working status ifhe/she was a student.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents aged less than 15 years or more than 75 years old orwho were not studying at the time of the interview have beenexcluded from the population.

Table 6
LBFDSTU Specifications
Value Condition(s) Description Notes
6 DHH_AGE < 15 or
DHH_AGE > 75 or
EDU_01 = 2
Population exclusion NA
9 (LBF_21 = DK, RF, NS) or
(EDU_02 = DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NS
1 (LBF_01 = 1 or
LBF_02 = 1 or
LBF_21 = 1) and
EDU_02 = 1
Worked during last 12 months and currently attending schoolfull-time  
2 (LBF_01 = 1 or
LBF_02 = 1 or
LBF_21 = 1) and
EDU_02 = 2
Worked during last 12 months and currently attending schoolpart-time  
3 LBF_21 = 2 and
EDU_02 = 1
Did not work during last 12 months and currently attendingschool full-time  
4 LBF_21 = 2 and
EDU_02 = 2
Did not work during last 12 months and currently attendingschool part-time  

7. LBFDWSL - Working status lastweek

Variable name:
LBFDWSL

Based on:
DHH_AGE, LBF_01, LBF_11, LBF_41

Description:
This variable classifies the respondent based on his/her workingstatus in the week prior to the interview and also includesgrouping for reasons of not working.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents aged less than 15 or more than 75 years old have beenexcluded from the population.

Table 7
LBFDWSL Specifications
Value Condition(s) Description Notes
96 DHH_AGE < 15 or
DHH_AGE > 75
Population exclusion NA
99 (LBF_11 = DK, RF, NS) or
(LBF_41 = DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NS
1 LBF_01 = 1 Worked at a job or business  
2 (LBF_41 = 8, 9, 10, 12, 13) Had a job - on temporary or seasonal layoff  
3 (0 < LBF_41 < 8) or
LBF_41 = 11 or
(13 < LBF_41 < NA)
Had a job - absent for some other reason  
4 LBF_11 = 1 Did not have a job - looked for work over past 4 weeks  
5 LBF_11 = 2 Did not have a job - did not look for work over past 4weeks  
6 LBF_01 = 3 Permanently unable to work  

8. LBFDWSS - Working status lastweek

Variable name:
LBFDWSS

Based on:
DHH_AGE, LBF_01, LBF_02

Description:
This variable classifies the respondent based on his/her workingstatus in the week prior to the interview.

Introduced in:
CCHS - Cycle 3.1

Note:
Respondents aged less than 15 or more than 75 years old have beenexcluded from the population.

Table 8
LBFDWSS Specifications
Value Condition(s) Description Notes
6 DHH_AGE < 15 or
DHH_AGE > 75
Population exclusions NA
1 LBF_01 = 1 Worked at a job or business  
2 LBF_02 = 1 Had a job but did not work (absent)  
3 LBF_02 = 2 Did not have a job  
4 LBF_02 = 3 Permanently unable to work  
9 (LBF_02 = DK, R, NS) or
(LBF_01 = DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NS

Milk and dairy product consumption (4DVs)

1. MDCD11Y - Drinks milk - times peryear

Variable name:
MDCD11Y

Based on:
MDC_11, MDC_11N

Description:
The number of times per year the respondent drinks milk or enrichedmilk substitutes or uses them on cereal.

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 1
MDCD11Y Specifications
Value Condition(s) Description Notes
0 MDC_11 = 0 Never  
MDC_11 * 365 MDC_11N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MDC_11 * 52 MDC_11N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MDC_11 * 12 MDC_11N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MDC_11 MDC_11N = 4 Reported number of times consumed per year  
9996 MDC_11N = NA Population exclusions NA
9999 Else   NS

2. MDCD13Y - Eats cottage cheese -times per year

Variable name:
MDCD13Y

Based on:
MDC_13, MDC_13N

Description:
The number of times per year the respondent eats cottagecheese.

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 2
MDCD13Y Specifications
Value Condition(s) Description Notes
0 MDC_13 = 0 Never  
MDC_13 * 365 MDC_13N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MDC_13 * 52 MDC_13N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MDC_13 * 12 MDC_13N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MDC_13 MDC_13N = 4 Reported number of times consumed per year  
9996 MDC_13N = NA Population exclusions NA
9999 Else   NS

3. MDCD14Y - Eats yogurt - times peryear

Variable name:
MDCD14Y

Based on:
MDC_14, MDC_14N

Description:
The number of times per year the respondent eats yogurt, excludingfrozen yogurt.

Note:
Created in the Household Post-Verify process. Based onCCHS 2.2 but no direct variables.

Table 3
MDCD14Y Specifications
Value Condition(s) Description Notes
0 MDC_14 = 0 Never  
MDC_14 * 365 MDC_14N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MDC_14 * 52 MDC_14N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MDC_14 * 12 MDC_14N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MDC_14 MDC_14N = 4 Reported number of times consumed per year  
9996 MDC_14N = NA Population exclusions NA
9999 Else   NS

4. MDCD15Y - Eats ice cream or frozenyogurt - times per year

Variable name:
MDCD15Y

Based on:
MDC_15, MDC_15N

Description:
The number of times per year the respondent eats ice cream orfrozen yogurt.

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 4
MDCD15Y Specifications
Value Condition(s) Description Notes
0 MDC_15 = 0 Never  
MDC_15 * 365 MDC_15N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MDC_15 * 52 MDC_15N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MDC_15 * 12 MDC_15N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MDC_15 MDC_15N = 4 Reported number of times consumed per year  
9996 MDC_15N = NA Population exclusions NA
9999 Else   NS

Meat and fish consumption (11DVs)

1. MFCD11Y - Eats red meat - timesper year

Variable name:
MFCD11Y

Based on:
MFC_11, MFC_11N

Description:
The number of times per year the respondent eats red meat(including beef, hamburger, pork or lamb).

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 1
MFCD11Y Specifications
Value Condition(s) Description Notes
0 MFC_11 = 0 Never  
MFC_11 * 365 MFC_11N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MFC_11 * 52 MFC_11N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MFC_11 * 12 MFC_11N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MFC_11 MFC_11N = 4 Reported number of times consumed per year  
9996 MFC_11N = NA Population exclusions NA
9999 Else   NS

2. MFCD12Y - Eats liver - times peryear

Variable name:
MFCD12Y

Based on:
MFC_12, MFC_12N

Description:
The number of times per year the respondent eats liver (includingall types of liver such as beef, veal, pork or chicken butexcluding liverwurst and liver pâté).

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 2
MFCD12Y Specifications
Value Condition(s) Description Notes
0 MFC_12 = 0 Never  
MFC_12 * 365 MFC_12N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MFC_12 * 52 MFC_12N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MFC_12 * 12 MFC_12N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MFC_12 MFC_12N = 4 Reported number of times consumed per year  
9996 MFC_12N = NA Population exclusions NA
9999 Else   NS

3. MFCD13Y - Eats other organ meats -times per year

Variable name:
MFCD13Y

Based on:
MFC_13, MFC_13N

Description:
The number of times per year the respondent eats other organ meats(including kidneys, heart or giblets).

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 3
MFCD13Y Specifications
Value Condition(s) Description Notes
0 MFC_13 = 0 Never  
MFC_13 * 365 MFC_13N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MFC_13 * 52 MFC_13N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MFC_13 * 12 MFC_13N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MFC_13 MFC_13N = 4 Reported number of times consumed per year  
9996 MFC_13N = NA Population exclusions NA
9999 Else   NS

4. MFCD14Y - Eats beef or pork hotdogs - times per year

Variable name:
MFCD14Y

Based on:
MFC_14, MFC_14N

Description:
The number of times per year the respondent eats beef or porkhotdogs.

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 4
MFCD14Y Specifications
Value Condition(s) Description Notes
0 MFC_14 = 0 Never  
MFC_14 * 365 MFC_14N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MFC_14 * 52 MFC_14N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MFC_14 * 12 MFC_14N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MFC_14 MFC_14N = 4 Reported number of times consumed per year  
9996 MFC_14N = NA Population exclusions NA
9999 Else   NS

5. MFCD15Y - Eats sausage or bacon-times per year

Variable name:
MFCD15Y

Based on:
MFC_15, MFC_15N

Description:
The number of times per year the respondent eats sausages or bacon(including all types of sausages such as breakfast, pepperoni andKielbassa but excluding low-fat, light or turkey varieties).

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 5
MFCD15Y Specifications
Value Condition(s) Description Notes
0 MFC_15 = 0 Never  
MFC_15 * 365 MFC_15N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MFC_15 * 52 MFC_15N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MFC_15 * 12 MFC_15N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MFC_15 MFC_15N = 4 Reported number of times consumed per year  
9996 MFC_15N = NA Population exclusions NA
9999 Else   NS

6. MFCD16Y - Eats salt water fish -times per year

Variable name:
MFCD16Y

Based on:
MFC_16, MFC_16N

Description:
The number of times per year the respondent eats salt water fish(including salmon, tuna or fish sticks).

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 6
MFCD16Y Specifications
Value Condition(s) Description Notes
0 MFC_16 = 0 Never  
MFC_16 * 365 MFC_16N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MFC_16 * 52 MFC_16N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MFC_16 * 12 MFC_16N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MFC_16 MFC_16N = 4 Reported number of times consumed per year  
9996 MFC_16N = NA Population exclusions NA
9999 Else   NS

7. MFCD17Y - Eats fresh water fish -times per year

Variable name:
MFCD17Y

Based on:
MFC_17, MFC_17N

Description:
The number of times per year the respondent eats fresh water fish(including trout, walleye or pickerel).

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 7
MFCD17Y Specifications
Value Condition(s) Description Notes
0 MFC_17 = 0 Never  
MFC_17 * 365 MFC_17N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MFC_17 * 52 MFC_17N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MFC_17 * 12 MFC_17N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MFC_17 MFC_17N = 4 Reported number of times consumed per year  
9996 MFC_17N = NA Population exclusions NA
9999 Else   NS

8. MFCD18Y - Eats shellfish - timesper year

Variable name:
MFCD18Y

Based on:
MFC_18, MFC_18N

Description:
The number of times per year the respondent eats shellfish(including shrimp, mussels, scallops, lobster, clams, oysters orcrab).

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 8
MFCD18Y Specifications
Value Condition(s) Description Notes
0 MFC_18 = 0 Never  
MFC_18 * 365 MFC_18N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MFC_18 * 52 MFC_181N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MFC_18 * 12 MFC_18N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MFC_18 MFC_18N = 4 Reported number of times consumed per year  
9996 MFC_18N = NA Population exclusions NA
9999 Else   NS

9. MFCD19Y - Eats eggs and egg dishes- times per year

Variable name:
MFCD19Y

Based on:
MFC_19, MFC_19N

Description:
The number of times per year the respondent eats eggs and eggdishes including the yolk such as omelettes, frittata or quiche(excluding all egg dishes made with only egg whites).

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 9
MFCD19Y Specifications
Value Condition(s) Description Notes
0 MFC_19 = 0 Never  
MFC_19 * 365 MFC_19N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MFC_19 * 52 MFC_19N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MFC_19 * 12 MFC_19N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MFC_19 MFC_19N = 4 Reported number of times consumed per year  
9996 MFC_19N = NA Population exclusions NA
9999 Else   NS

10. MFCD20Y - Eats cooked dried beans- times per year

Variable name:
MFCD20Y

Based on:
MFC_20, MFC_20N

Description:
The number of times per year the respondent eats cooked dried beans(including refried beans, baked beans, pea soup or kidney beans,excluding green and yellow beans).

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 10
MFCD20Y Specifications
Value Condition(s) Description Notes
0 MFC_20 = 0 Never  
MFC_20 * 365 MFC_20N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MFC_20 * 52 MFC_20N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MFC_20 * 12 MFC_20N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MFC_20 MFC_20N = 4 Reported number of times consumed per year  
9996 MFC_20N = NA Population exclusions NA
9999 Else   NS

11. MFCD21Y - Eats peanuts, walnuts,seeds or other nuts - times per year

Variable name:
MFCD21Y

Based on:
MFC_21, MFC_21N

Description:
The number of times per year the respondent eats peanuts, walnuts,seeds, or other nuts (excluding nut butters such as peanutbutter).

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 11
MFCD21Y Specifications
Value Condition(s) Description Notes
0 MFC_21 = 0 Never  
MFC_21 * 365 MFC_21N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
MFC_21 * 52 MFC_21N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
MFC_21 * 12 MFC_21N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
MFC_21 MFC_21N = 4 Reported number of times consumed per year  
9996 MFC_21N = NA Population exclusions NA
9999 Else   NS

Oral Health (77 DVs)

1. OHCDELG - Eligibility - OralHealth

Variable name:
OHCDELG

Based on:
PHC_42K

Description:
This variable indicates whether the respondent was eligible for theOral Health component. As there are multiple reasons to be screenedout of this measure, the prevalence of screen outs by reason shouldnot be based on frequency counts for this variable.

Note:
Created in the Clinic Post-Verify process

Table 1
OHCDELG Specifications
Value Condition(s) Description Notes
9 PHC_42K = 1 Not eligible - acute or chronic condition  
1 Else Eligible  

2. OHEDAC01 - Total number of adultcrowns - code 1

Variable name:
OHEDAC01

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 1 (Sound - never decayed or restored) during the clinic dentalexaminations. The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 2
OHEDAC01 Temporary Reformat
Value Condition(s) Description Notes
DVC01_11   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 11  
DVC01_12   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 12  
DVC01_13   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 13  
DVC01_14   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 14  
DVC01_15   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 15  
DVC01_16   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 16  
DVC01_17   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 17  
DVC01_21   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 21  
DVC01_22   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 22  
DVC01_23   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 23  
DVC01_24   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 24  
DVC01_25   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 25  
DVC01_26   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 26  
DVC01_27   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 27  
DVC01_31   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 31  
DVC01_32   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 32  
DVC01_33   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 33  
DVC01_34   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 34  
DVC01_35   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 35  
DVC01_36   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 36  
DVC01_37   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 37  
DVC01_41   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 41  
DVC01_42   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 42  
DVC01_43   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 43  
DVC01_44   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 44  
DVC01_45   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 45  
DVC01_46   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 46  
DVC01_47   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 47  
Table 2
OHEDAC01 Specifications
Value Condition(s) Description Notes
sum (of
DVC01_11-
DVC01_17
DVC01_21-
DVC01_27
DVC01_31-
DVC01_37
DVC01_41-
DVC01_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 1  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

3. OHEDAC02 - Total number of adultcrowns - code 2

Variable name:
OHEDAC02

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 2 (Sound - crown sealed, never decayed or otherwise restored)during the clinic dental examinations. The probing portion ofthe oral health exam was completed by all respondents except thosemeeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 3
OHEDAC02 Temporary Reformat
Value Condition(s) Description Notes
DVC02_11   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 11  
DVC02_12   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 12  
DVC02_13   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 13  
DVC02_14   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 14  
DVC02_15   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 15  
DVC02_16   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 16  
DVC02_17   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 17  
DVC02_21   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 21  
DVC02_22   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 22  
DVC02_23   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 23  
DVC02_24   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 24  
DVC02_25   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 25  
DVC02_26   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 26  
DVC02_27   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 27  
DVC02_31   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 31  
DVC02_32   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 32  
DVC02_33   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 33  
DVC02_34   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 34  
DVC02_35   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 35  
DVC02_36   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 36  
DVC02_37   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 37  
DVC02_41   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 41  
DVC02_42   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 42  
DVC02_43   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 43  
DVC02_44   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 44  
DVC02_45   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 45  
DVC02_46   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 46  
DVC02_47   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 47  
Table 3
OHEDAC02 Specifications
Value Condition(s)  Description Notes
sum (of
DVC02_11-
DVC02_17
DVC02_21-
DVC02_27
DVC02_31-
DVC02_37
DVC02_41-
DVC02_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 2  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

4. OHEDAC03 - Total number of adultcrowns - code 3

Variable name:
OHEDAC03

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 3 (Missing - due to orthodontic treatment) during the clinicdental examinations. The probing portion of the oral healthexam was completed by all respondents except those meeting theexclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 4
OHEDAC03 Temporary Reformat
Value Condition(s) Description Notes
DVC03_11   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 11  
DVC03_12   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 12  
DVC03_13   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 13  
DVC03_14   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 14  
DVC03_15   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 15  
DVC03_16   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 16  
DVC03_17   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 17  
DVC03_21   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 21  
DVC03_22   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 22  
DVC03_23   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 23  
DVC03_24   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 24  
DVC03_25   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 25  
DVC03_26   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 26  
DVC03_27   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 27  
DVC03_31   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 31  
DVC03_32   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 32  
DVC03_33   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 33  
DVC03_34   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 34  
DVC03_35   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 35  
DVC03_36   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 36  
DVC03_37   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 37  
DVC03_41   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 41  
DVC03_42   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 42  
DVC03_43   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 43  
DVC03_44   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 44  
DVC03_45   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 45  
DVC03_46   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 46  
DVC03_47   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 47  
Table 4
OHEDAC03 Specifications
Value Condition(s) Description Notes
sum (of
DVC03_11-
DVC03_17
DVC03_21-
DVC03_27
DVC03_31-
DVC03_37
DVC03_41-
DVC03_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 3  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

5. OHEDAC04 - Total number of adultcrowns - code 4

Variable name:
OHEDAC04

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 4 (Missing - due to trauma) during the clinic dentalexaminations. The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 5
OHEDAC04 Temporary Reformat
Value Condition(s) Description Notes
DVC04_11   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 11  
DVC04_12   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 12  
DVC04_13   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 13  
DVC04_14   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 14  
DVC04_15   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 15  
DVC04_16   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 16  
DVC04_17   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 17  
DVC04_21   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 21  
DVC04_22   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 22  
DVC04_23   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 23  
DVC04_24   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 24  
DVC04_25   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 25  
DVC04_26   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 26  
DVC04_27   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 27  
DVC04_31   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 31  
DVC04_32   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 32  
DVC04_33   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 33  
DVC04_34   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 34  
DVC04_35   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 35  
DVC04_36   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 36  
DVC04_37   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 37  
DVC04_41   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 41  
DVC04_42   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 42  
DVC04_43   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 43  
DVC04_44   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 44  
DVC04_45   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 45  
DVC04_46   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 46  
DVC04_47   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 47  
Table 5
OHEDAC04 Specifications
Value Condition(s) Description Notes
sum (of
DVC04_11-
DVC04_17
DVC04_21-
DVC04_27
DVC04_31-
DVC04_37
DVC04_41-
DVC04_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 4  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

6. OHEDAC05 - Total number of adultcrowns - code 5

Variable name:
OHEDAC05

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 5 (Missing - due to caries or periodontal disease) during theclinic dental examinations. The probing portion of the oralhealth exam was completed by all respondents except those meetingthe exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 6
OHEDAC05 Temporary Reformat
Value Condition(s) Description Notes
DVC05_11   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 11  
DVC05_12   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 12  
DVC05_13   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 13  
DVC05_14   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 14  
DVC05_15   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 15  
DVC05_16   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 16  
DVC05_17   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 17  
DVC05_21   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 21  
DVC05_22   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 22  
DVC05_23   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 23  
DVC05_24   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 24  
DVC05_25   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 25  
DVC05_26   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 26  
DVC05_27   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 27  
DVC05_31   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 31  
DVC05_32   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 32  
DVC05_33   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 33  
DVC05_34   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 34  
DVC05_35   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 35  
DVC05_36   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 36  
DVC05_37   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 37  
DVC05_41   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 41  
DVC05_42   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 42  
DVC05_43   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 43  
DVC05_44   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 44  
DVC05_45   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 45  
DVC05_46   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 46  
DVC05_47   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 47  
Table 6
OHEDAC05 Specifications
Value Condition(s) Description Notes
sum (of
DVC05_11-
DVC05_17
DVC05_21-
DVC05_27
DVC05_31-
DVC05_37
DVC05_41-
DVC05_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 5  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

7. OHEDAC06 - Total number of adultcrowns - code 6

Variable name:
OHEDAC06

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 6 (Unerupted tooth, congenitally missing or unexposed root)during the clinic dental examinations. The probing portion ofthe oral health exam was completed by all respondents except thosemeeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 7
OHEDAC06 Temporary Reformat
Value Condition(s) Description Notes
DVC06_11   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 11  
DVC06_12   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 12  
DVC06_13   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 13  
DVC06_14   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 14  
DVC06_15   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 15  
DVC06_16   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 16  
DVC06_17   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 17  
DVC06_21   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 21  
DVC06_22   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 22  
DVC06_23   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 23  
DVC06_24   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 24  
DVC06_25   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 25  
DVC06_26   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 26  
DVC06_27   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 27  
DVC06_31   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 31  
DVC06_32   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 32  
DVC06_33   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 33  
DVC06_34   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 34  
DVC06_35   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 35  
DVC06_36   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 36  
DVC06_37   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 37  
DVC06_41   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 41  
DVC06_42   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 42  
DVC06_43   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 43  
DVC06_44   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 44  
DVC06_45   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 45  
DVC06_46   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 46  
DVC06_47   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 47  
Table 7
OHEDAC06 Specifications
Value Condition(s) Description Notes
sum (of
DVC06_11-
DVC06_17
DVC06_21-
DVC06_27
DVC06_31-
DVC06_37
DVC06_41-
DVC06_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 6  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

8. OHEDAC07 - Total number of adultcrowns - code 7

Variable name:
OHEDAC07

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 7 (Decayed severely) during the clinic dentalexaminations. The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 8
OHEDAC07 Temporary Reformat
Value Condition(s) Description Notes
DVC07_11   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 11  
DVC07_12   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 12  
DVC07_13   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 13  
DVC07_14   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 14  
DVC07_15   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 15  
DVC07_16   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 16  
DVC07_17   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 17  
DVC07_21   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 21  
DVC07_22   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 22  
DVC07_23   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 23  
DVC07_24   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 24  
DVC07_25   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 25  
DVC07_26   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 26  
DVC07_27   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 27  
DVC07_31   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 31  
DVC07_32   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 32  
DVC07_33   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 33  
DVC07_34   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 34  
DVC07_35   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 35  
DVC07_36   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 36  
DVC07_37   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 37  
DVC07_41   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 41  
DVC07_42   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 42  
DVC07_43   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 43  
DVC07_44   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 44  
DVC07_45   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 45  
DVC07_46   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 46  
DVC07_47   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 47  
Table 8
OHEDAC07 Specifications
Value Condition(s) Description Notes
sum (of
DVC07_11-
DVC07_17
DVC07_21-
DVC07_27
DVC07_31-
DVC07_37
DVC07_41-
DVC07_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 7  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

9. OHEDAC08 - Total number of adultcrowns - code 8

Variable name:
OHEDAC08

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 8 (Decayed - pit and fissure caries) during the clinic dentalexaminations. The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 9
OHEDAC08 Temporary Reformat
Value Condition(s) Description Notes
DVC08_11   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 11  
DVC08_12   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 12  
DVC08_13   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 13  
DVC08_14   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 14  
DVC08_15   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 15  
DVC08_16   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 16  
DVC08_17   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 17  
DVC08_21   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 21  
DVC08_22   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 22  
DVC08_23   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 23  
DVC08_24   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 24  
DVC08_25   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 25  
DVC08_26   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 26  
DVC08_27   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 27  
DVC08_31   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 31  
DVC08_32   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 32  
DVC08_33   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 33  
DVC08_34   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 34  
DVC08_35   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 35  
DVC08_36   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 36  
DVC08_37   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 37  
DVC08_41   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 41  
DVC08_42   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 42  
DVC08_43   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 43  
DVC08_44   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 44  
DVC08_45   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 45  
DVC08_46   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 46  
DVC08_47   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 47  
Table 9
OHEDAC08 Specifications
Value Condition(s) Description Notes
sum (of
DVC08_11-
DVC08_17
DVC08_21-
DVC08_27
DVC08_31-
DVC08_37
DVC08_41-
DVC08_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 8  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

10. OHEDAC09 - Total number of adultcrowns - code 9

Variable name:
OHEDAC09

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 9 (Decayed - smooth surface caries) during the clinic dentalexaminations. The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 10
OHEDAC09 Temporary Reformat
Value Condition(s) Description Notes
DVC09_11   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 11  
DVC09_12   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 12  
DVC09_13   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 13  
DVC09_14   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 14  
DVC09_15   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 15  
DVC09_16   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 16  
DVC09_17   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 17  
DVC09_21   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 21  
DVC09_22   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 22  
DVC09_23   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 23  
DVC09_24   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 24  
DVC09_25   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 25  
DVC09_26   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 26  
DVC09_27   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 27  
DVC09_31   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 31  
DVC09_32   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 32  
DVC09_33   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 33  
DVC09_34   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 34  
DVC09_35   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 35  
DVC09_36   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 36  
DVC09_37   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 37  
DVC09_41   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 41  
DVC09_42   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 42  
DVC09_43   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 43  
DVC09_44   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 44  
DVC09_45   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 45  
DVC09_46   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 46  
DVC09_47   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 47  
Table 10
OHEDAC09 Specifications
Value Condition(s) Description Notes
sum (of
DVC09_11-
DVC09_17
DVC09_21-
DVC09_27
DVC09_31-
DVC09_37
DVC09_41-
DVC09_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 9  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

11. OHEDAC10 - Total number of adultcrowns - code 10

Variable name:
OHEDAC10

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 10 (Decayed - both smooth surface and pit and fissure caries)during the clinic dental examinations. The probing portion ofthe oral health exam was completed by all respondents except thosemeeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 11
OHEDAC10 Temporary Reformat
Value Condition(s) Description Notes
DVC10_11   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 11  
DVC10_12   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 12  
DVC10_13   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 13  
DVC10_14   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 14  
DVC10_15   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 15  
DVC10_16   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 16  
DVC10_17   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 17  
DVC10_21   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 21  
DVC10_22   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 22  
DVC10_23   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 23  
DVC10_24   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 24  
DVC10_25   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 25  
DVC10_26   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 26  
DVC10_27   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 27  
DVC10_31   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 31  
DVC10_32   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 32  
DVC10_33   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 33  
DVC10_34   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 34  
DVC10_35   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 35  
DVC10_36   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 36  
DVC10_37   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 37  
DVC10_41   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 41  
DVC10_42   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 42  
DVC10_43   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 43  
DVC10_44   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 44  
DVC10_45   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 45  
DVC10_46   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 46  
DVC10_47   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 47  
Table 11
OHEDAC10 Specifications
Value Condition(s) Description Notes
sum (of
DVC10_11-
DVC10_17
DVC10_21-
DVC10_27
DVC10_31-
DVC10_37
DVC10_41-
DVC10_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 10  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

12. OHEDAC12 - Total number of adultcrowns - code 12

Variable name:
OHEDAC12

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 12 (Filled with amalgam, no other decay) during the clinicdental examinations. The probing portion of the oral healthexam was completed by all respondents except those meeting theexclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 12
OHEDAC12 Temporary Reformat
Value Condition(s) Description Notes
DVC12_11   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 11  
DVC12_12   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 12  
DVC12_13   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 13  
DVC12_14   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 14  
DVC12_15   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 15  
DVC12_16   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 16  
DVC12_17   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 17  
DVC12_21   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 21  
DVC12_22   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 22  
DVC12_23   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 23  
DVC12_24   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 24  
DVC12_25   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 25  
DVC12_26   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 26  
DVC12_27   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 27  
DVC12_31   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 31  
DVC12_32   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 32  
DVC12_33   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 33  
DVC12_34   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 34  
DVC12_35   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 35  
DVC12_36   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 36  
DVC12_37   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 37  
DVC12_41   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 41  
DVC12_42   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 42  
DVC12_43   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 43  
DVC12_44   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 44  
DVC12_45   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 45  
DVC12_46   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 46  
DVC12_47   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 47  
Table 12
OHEDAC12 Specifications
Value Condition(s) Description Notes
sum (of
DVC12_11-
DVC12_17
DVC12_21-
DVC12_27
DVC12_31-
DVC12_37
DVC12_41-
DVC12_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 12  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

13. OHEDAC13 - Total number of adultcrowns - code 13

Variable name:
OHEDAC13

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 13 (Filled with other material (resin, GIC, inlay, crown), noother decay) during the clinic dental examinations. Theprobing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 13
OHEDAC13 Temporary Reformat
Value Condition(s) Description Notes
DVC13_11   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 11  
DVC13_12   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 12  
DVC13_13   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 13  
DVC13_14   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 14  
DVC13_15   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 15  
DVC13_16   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 16  
DVC13_17   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 17  
DVC13_21   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 21  
DVC13_22   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 22  
DVC13_23   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 23  
DVC13_24   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 24  
DVC13_25   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 25  
DVC13_26   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 26  
DVC13_27   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 27  
DVC13_31   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 31  
DVC13_32   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 32  
DVC13_33   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 33  
DVC13_34   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 34  
DVC13_35   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 35  
DVC13_36   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 36  
DVC13_37   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 37  
DVC13_41   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 41  
DVC13_42   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 42  
DVC13_43   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 43  
DVC13_44   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 44  
DVC13_45   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 45  
DVC13_46   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 46  
DVC13_47   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 47  
Table 13
OHEDAC13 Specifications
Value Condition(s) Description Notes
sum (of
DVC13_11-
DVC13_17
DVC13_21-
DVC13_27
DVC13_31-
DVC13_37
DVC13_41-
DVC13_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 13  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

14. OHEDAC14 - Total number of adultcrowns - code 14

Variable name:
OHEDAC14

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 14 (Filled with amalgam and other material (resin, GIC, inlay,crown), no other decay) during the clinic dentalexaminations. The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 14
OHEDAC14 Temporary Reformat
Value Condition(s) Description Notes
DVC14_11   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 11  
DVC14_12   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 12  
DVC14_13   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 13  
DVC14_14   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 14  
DVC14_15   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 15  
DVC14_16   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 16  
DVC14_17   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 17  
DVC14_21   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 21  
DVC14_22   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 22  
DVC14_23   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 23  
DVC14_24   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 24  
DVC14_25   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 25  
DVC14_26   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 26  
DVC14_27   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 27  
DVC14_31   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 31  
DVC14_32   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 32  
DVC14_33   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 33  
DVC14_34   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 34  
DVC14_35   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 35  
DVC14_36   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 36  
DVC14_37   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 37  
DVC14_41   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 41  
DVC14_42   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 42  
DVC14_43   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 43  
DVC14_44   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 44  
DVC14_45   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 45  
DVC14_46   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 46  
DVC14_47   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 47  
Table 14
OHEDAC14 Specifications
Value Condition(s) Description Notes

sum (of
DVC14_11-
DVC14_17
DVC14_21-
DVC14_27
DVC14_31-
DVC14_37
DVC14_41-
DVC14_47)

OHE_11 in (1 2 3)

Sum of all permanent (adult) crowns coded as 14

 

6

OHE_11 in (4 5)

Population exclusions

NA

9

OHE_11 > NA

At least one required question was not answered (don'tknow, refusal, not stated)

NS

9

Else

 

NS

15. OHEDAC15 - Total number of adultcrowns - code 15

Variable name:
OHEDAC15

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 15 (Filled with amalgam, no other decay, but filling isdefective and needs replacement) during the clinic dentalexaminations. The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 15
OHEDAC15 Temporary Reformat
Value Condition(s) Description Notes
DVC15_11   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 11  
DVC15_12   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 12  
DVC15_13   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 13  
DVC15_14   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 14  
DVC15_15   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 15  
DVC15_16   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 16  
DVC15_17   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 17  
DVC15_21   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 21  
DVC15_22   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 22  
DVC15_23   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 23  
DVC15_24   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 24  
DVC15_25   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 25  
DVC15_26   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 26  
DVC15_27   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 27  
DVC15_31   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 31  
DVC15_32   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 32  
DVC15_33   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 33  
DVC15_34   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 34  
DVC15_35   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 35  
DVC15_36   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 36  
DVC15_37   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 37  
DVC15_41   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 41  
DVC15_42   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 42  
DVC15_43   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 43  
DVC15_44   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 44  
DVC15_45   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 45  
DVC15_46   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 46  
DVC15_47   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 47  
Table 15
OHEDAC15 Specifications
Value Condition(s) Description Notes
sum (of
DVC15_11-
DVC15_17
DVC15_21-
DVC15_27
DVC15_31-
DVC15_37
DVC15_41-
DVC15_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 15  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

16. OHEDAC16 - Total number of adultcrowns - code 16

Variable name:
OHEDAC16

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 16 (Filled with other material (resin, GIC, inlay, crown) butfilling is defective and needs replacement) during the clinicdental examinations. The probing portion of the oral healthexam was completed by all respondents except those meeting theexclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 16
OHEDAC16 Temporary Reformat
Value Condition(s) Description Notes
DVC16_11   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 11  
DVC16_12   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 12  
DVC16_13   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 13  
DVC16_14   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 14  
DVC16_15   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 15  
DVC16_16   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 16  
DVC16_17   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 17  
DVC16_21   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 21  
DVC16_22   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 22  
DVC16_23   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 23  
DVC16_24   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 24  
DVC16_25   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 25  
DVC16_26   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 26  
DVC16_27   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 27  
DVC16_31   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 31  
DVC16_32   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 32  
DVC16_33   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 33  
DVC16_34   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 34  
DVC16_35   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 35  
DVC16_36   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 36  
DVC16_37   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 37  
DVC16_41   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 41  
DVC16_42   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 42  
DVC16_43   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 43  
DVC16_44   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 44  
DVC16_45   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 45  
DVC16_46   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 46  
DVC16_47   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 47  
Table 16
OHEDAC16 Specifications
Value Condition(s) Description Notes
sum (of
DVC16_11-
DVC16_17
DVC16_21-
DVC16_27
DVC16_31-
DVC16_37
DVC16_41-
DVC16_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 16  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else At least one required question was not answered (don'tknow, refusal, not stated) NS

17. OHEDAC17 - Total number of adultcrowns - code 17

Variable name:
OHEDAC17

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 17 (Filled with amalgam and other material (resin, GIC, inlay,crown) but filling is defective and needs replacement) during theclinic dental examinations. The probing portion of the oralhealth exam was completed by all respondents except those meetingthe exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 17
OHEDAC17 Temporary Reformat
Value Condition(s) Description Notes
DVC17_11   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 11  
DVC17_12   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 12  
DVC17_13   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 13  
DVC17_14   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 14  
DVC17_15   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 15  
DVC17_16   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 16  
DVC17_17   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 17  
DVC17_21   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 21  
DVC17_22   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 22  
DVC17_23   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 23  
DVC17_24   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 24  
DVC17_25   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 25  
DVC17_26   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 26  
DVC17_27   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 27  
DVC17_31   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 31  
DVC17_32   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 32  
DVC17_33   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 33  
DVC17_34   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 34  
DVC17_35   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 35  
DVC17_36   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 36  
DVC17_37   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 37  
DVC17_41   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 41  
DVC17_42   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 42  
DVC17_43   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 43  
DVC17_44   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 44  
DVC17_45   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 45  
DVC17_46   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 46  
DVC17_47   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 47  
Table 17
OHEDAC17 Specifications
Value Condition(s) Description Notes
sum (of
DVC17_11-
DVC17_17
DVC17_21-
DVC17_27
DVC17_31-
DVC17_37
DVC17_41-
DVC17_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 17  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

18. OHEDAC18 - Total number of adultcrowns - code 18

Variable name:
OHEDAC18

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 18 (Bridge abutment, special crown or veneer) during the clinicdental examinations. The probing portion of the oral healthexam was completed by all respondents except those meeting theexclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 18
OHEDAC18 Temporary Reformat
Value Condition(s) Description Notes
DVC18_11   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 11  
DVC18_12   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 12  
DVC18_13   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 13  
DVC18_14   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 14  
DVC18_15   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 15  
DVC18_16   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 16  
DVC18_17   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 17  
DVC18_21   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 21  
DVC18_22   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 22  
DVC18_23   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 23  
DVC18_24   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 24  
DVC18_25   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 25  
DVC18_26   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 26  
DVC18_27   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 27  
DVC18_31   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 31  
DVC18_32   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 32  
DVC18_33   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 33  
DVC18_34   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 34  
DVC18_35   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 35  
DVC18_36   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 36  
DVC18_37   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 37  
DVC18_41   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 41  
DVC18_42   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 42  
DVC18_43   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 43  
DVC18_44   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 44  
DVC18_45   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 45  
DVC18_46   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 46  
DVC18_47   Temporary variable used to keep a count of tooth conditioncoded as 18, tooth 47  
Table 18
OHEDAC18 Specifications
Value Condition(s) Description Notes
sum (of
DVC18_11-
DVC18_17
DVC18_21-
DVC18_27
DVC18_31-
DVC18_37
DVC18_41-
DVC18_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 18  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

19. OHEDAC19 - Total number of adultcrowns - code 19

Variable name:
OHEDAC19

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 19 (Implant) during the clinic dental examinations. Theprobing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 19
OHEDAC19 Temporary Reformat
Value Condition(s) Description Notes
DVC19_11   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 11  
DVC19_12   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 12  
DVC19_13   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 13  
DVC19_14   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 14  
DVC19_15   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 15  
DVC19_16   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 16  
DVC19_17   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 17  
DVC19_21   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 21  
DVC19_22   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 22  
DVC19_23   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 23  
DVC19_24   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 24  
DVC19_25   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 25  
DVC19_26   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 26  
DVC19_27   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 27  
DVC19_31   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 31  
DVC19_32   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 32  
DVC19_33   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 33  
DVC19_34   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 34  
DVC19_35   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 35  
DVC19_36   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 36  
DVC19_37   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 37  
DVC19_41   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 41  
DVC19_42   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 42  
DVC19_43   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 43  
DVC19_44   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 44  
DVC19_45   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 45  
DVC19_46   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 46  
DVC19_47   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 47  
Table 19
OHEDAC19 Specifications
Value Condition(s) Description Notes
sum (of
DVC19_11-
DVC19_17
DVC19_21-
DVC19_27
DVC19_31-
DVC19_37
DVC19_41-
DVC19_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 19  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

20. OHEDAC20 - Total number of adultcrowns - code 20

Variable name:
OHEDAC20

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 20 (Fractured due to trauma) during the clinic dentalexaminations. The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 20
OHEDAC20 Temporary Reformat
Value Condition(s) Description Notes
DVC20_11   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 11  
DVC20_12   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 12  
DVC20_13   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 13  
DVC20_14   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 14  
DVC20_15   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 15  
DVC20_16   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 16  
DVC20_17   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 17  
DVC20_21   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 21  
DVC20_22   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 22  
DVC20_23   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 23  
DVC20_24   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 24  
DVC20_25   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 25  
DVC20_26   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 26  
DVC20_27   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 27  
DVC20_31   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 31  
DVC20_32   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 32  
DVC20_33   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 33  
DVC20_34   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 34  
DVC20_35   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 35  
DVC20_36   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 36  
DVC20_37   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 37  
DVC20_41   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 41  
DVC20_42   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 42  
DVC20_43   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 43  
DVC20_44   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 44  
DVC20_45   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 45  
DVC20_46   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 46  
DVC20_47   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 47  
Table 20
OHEDAC20 Specifications
Value Condition(s) Description Notes
sum (of
DVC20_11-
DVC20_17
DVC20_21-
DVC20_27
DVC20_31-
DVC20_37
DVC20_41-
DVC20_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 20  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

21. OHEDAC21 - Total number of adultcrowns - code 21

Variable name:
OHEDAC21

Based on:
OHE_11, OHE_1C11, OHE_1C12, OHE_1C13, OHE_1C14, OHE_1C15, OHE_1C16,OHE_1C17, OHE_1C21, OHE_1C22, OHE_1C23, OHE_1C24, OHE_1C25,OHE_1C26, OHE_1C27, OHE_1C31, OHE_1C32, OHE_1C33, OHE_1C34,OHE_1C35, OHE_1C36, OHE_1C37, OHE_1C41, OHE_1C42, OHE_1C43,OHE_1C44, OHE_1C45, OHE_1C46, OHE_1C47

Description:
This variable is a count of all permanent (adult) crowns recordedas 21 (Other) during the clinic dental examinations. Theprobing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 21
OHEDAC21 Temporary Reformat
Value Condition(s) Description Notes
DVC21_11   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 11  
DVC21_12   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 12  
DVC21_13   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 13  
DVC21_14   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 14  
DVC21_15   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 15  
DVC21_16   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 16  
DVC21_17   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 17  
DVC21_21   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 21  
DVC21_22   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 22  
DVC21_23   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 23  
DVC21_24   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 24  
DVC21_25   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 25  
DVC21_26   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 26  
DVC21_27   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 27  
DVC21_31   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 31  
DVC21_32   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 32  
DVC21_33   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 33  
DVC21_34   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 34  
DVC21_35   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 35  
DVC21_36   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 36  
DVC21_37   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 37  
DVC21_41   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 41  
DVC21_42   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 42  
DVC21_43   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 43  
DVC21_44   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 44  
DVC21_45   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 45  
DVC21_46   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 46  
DVC21_47   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 47  
Table 21
OHEDAC21 Specifications
Value Condition(s) Description Notes
sum (of
DVC21_11-
DVC21_17
DVC21_21-
DVC21_27
DVC21_31-
DVC21_37
DVC21_41-
DVC21_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) crowns coded as 21  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

22. OHEDAR01 - Total number of adultroots - code 1

Variable name:
OHEDAR01

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as1 (Sound - never decayed or restored) during the clinic dentalexaminations. The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 22
OHEDAR01 Temporary Reformat
Value Condition(s) Description Notes
DVR01_11   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 11  
DVR01_12   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 12  
DVR01_13   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 13  
DVR01_14   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 14  
DVR01_15   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 15  
DVR01_16   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 16  
DVR01_17   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 17  
DVR01_21   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 21  
DVR01_22   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 22  
DVR01_23   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 23  
DVR01_24   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 24  
DVR01_25   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 25  
DVR01_26   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 26  
DVR01_27   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 27  
DVR01_31   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 31  
DVR01_32   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 32  
DVR01_33   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 33  
DVR01_34   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 34  
DVR01_35   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 35  
DVR01_36   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 36  
DVR01_37   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 37  
DVR01_41   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 41  
DVR01_42   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 42  
DVR01_43   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 43  
DVR01_44   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 44  
DVR01_45   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 45  
DVR01_46   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 46  
DVR01_47   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 47  
Table 22
OHEDAR01 Specifications
Value Condition(s) Description Notes
sum (of
DVR01_11-
DVR01_17
DVR01_21-
DVR01_27
DVR01_31-
DVR01_37
DVR01_41-
DVR01_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 1  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

23. OHEDAR03 - Total number of adultroots - code 3

Variable name:
OHEDAR03

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as3 (Missing - due to orthodontic treatment) during the clinic dentalexaminations. The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 23
OHEDAR03 Temporary Reformat
Value Condition(s) Description Notes
DVR03_11   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 11  
DVR03_12   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 12  
DVR03_13   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 13  
DVR03_14   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 14  
DVR03_15   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 15  
DVR03_16   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 16  
DVR03_17   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 17  
DVR03_21   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 21  
DVR03_22   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 22  
DVR03_23   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 23  
DVR03_24   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 24  
DVR03_25   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 25  
DVR03_26   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 26  
DVR03_27   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 27  
DVR03_31   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 31  
DVR03_32   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 32  
DVR03_33   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 33  
DVR03_34   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 34  
DVR03_35   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 35  
DVR03_36   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 36  
DVR03_37   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 37  
DVR03_41   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 41  
DVR03_42   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 42  
DVR03_43   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 43  
DVR03_44   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 44  
DVR03_45   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 45  
DVR03_46   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 46  
DVR03_47   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 47  
Table 23
OHEDAR03 Specifications
Value Condition(s) Description Notes
sum (of
DVR03_11-
DVR03_17
DVR03_21-
DVR03_27
DVR03_31-
DVR03_37
DVR03_41-
DVR03_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 3  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

24. OHEDAR04 - Total number of adultroots - code 4

Variable name:
OHEDAR04

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as4 (Missing - due to trauma) during the clinic dentalexaminations. The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 24
OHEDAR04 Temporary Reformat
Value Condition(s) Description Notes
DVR04_11   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 11  
DVR04_12   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 12  
DVR04_13   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 13  
DVR04_14   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 14  
DVR04_15   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 15  
DVR04_16   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 16  
DVR04_17   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 17  
DVR04_21   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 21  
DVR04_22   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 22  
DVR04_23   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 23  
DVR04_24   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 24  
DVR04_25   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 25  
DVR04_26   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 26  
DVR04_27   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 27  
DVR04_31   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 31  
DVR04_32   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 32  
DVR04_33   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 33  
DVR04_34   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 34  
DVR04_35   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 35  
DVR04_36   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 36  
DVR04_37   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 37  
DVR04_41   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 41  
DVR04_42   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 42  
DVR04_43   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 43  
DVR04_44   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 44  
DVR04_45   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 45  
DVR04_46   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 46  
DVR04_47   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 47  
Table 24
OHEDAR04 Specifications
Value Condition(s) Description Notes
sum (of
DVR04_11-
DVR04_17
DVR04_21-
DVR04_27
DVR04_31-
DVR04_37
DVR04_41-
DVR04_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 4  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

25. OHEDAR05 - Total number of adultroots - code 5

Variable name:
OHEDAR05

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as5 (Missing - due to caries or periodontal disease) during theclinic dental examinations. The probing portion of the oralhealth exam was completed by all respondents except those meetingthe exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated bycreating arrays for each of 4 quadrants and also creating arraysfor the temporary variables used to maintain a total count for eachquadrant.

Table 25
OHEDAR05 Temporary Reformat
Value Condition(s) Description Notes
DVR05_11   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 11  
DVR05_12   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 12  
DVR05_13   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 13  
DVR05_14   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 14  
DVR05_15   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 15  
DVR05_16   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 16  
DVR05_17   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 17  
DVR05_21   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 21  
DVR05_22   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 22  
DVR05_23   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 23  
DVR05_24   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 24  
DVR05_25   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 25  
DVR05_26   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 26  
DVR05_27   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 27  
DVR05_31   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 31  
DVR05_32   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 32  
DVR05_33   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 33  
DVR05_34   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 34  
DVR05_35   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 35  
DVR05_36   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 36  
DVR05_37   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 37  
DVR05_41   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 41  
DVR05_42   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 42  
DVR05_43   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 43  
DVR05_44   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 44  
DVR05_45   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 45  
DVR05_46   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 46  
DVR05_47   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 47  
Table 25
OHEDAR05 Specifications
Value Condition(s) Description Notes
sum (of
DVR05_11-
DVR05_17
DVR05_21-
DVR05_27
DVR05_31-
DVR05_37
DVR05_41-
DVR05_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 5  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

26. OHEDAR06 - Total number of adultroots - code 6

Variable name:
OHEDAR06

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as6 (Unerupted tooth, congenitally missing or unexposed root) duringthe clinic dental examinations. The probing portion of theoral health exam was completed by all respondents except thosemeeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 26
OHEDAR06 Temporary Reformat
Value Condition(s) Description Notes
DVR06_11   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 11  
DVR06_12   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 12  
DVR06_13   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 13  
DVR06_14   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 14  
DVR06_15   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 15  
DVR06_16   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 16  
DVR06_17   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 17  
DVR06_21   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 21  
DVR06_22   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 22  
DVR06_23   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 23  
DVR06_24   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 24  
DVR06_25   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 25  
DVR06_26   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 26  
DVR06_27   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 27  
DVR06_31   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 31  
DVR06_32   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 32  
DVR06_33   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 33  
DVR06_34   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 34  
DVR06_35   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 35  
DVR06_36   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 36  
DVR06_37   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 37  
DVR06_41   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 41  
DVR06_42   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 42  
DVR06_43   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 43  
DVR06_44   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 44  
DVR06_45   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 45  
DVR06_46   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 46  
DVR06_47   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 47  
Table 26
OHEDAR06 Specifications
Value Condition(s) Description Notes
sum (of
DVR06_11-
DVR06_17
DVR06_21-
DVR06_27
DVR06_31-
DVR06_37
DVR06_41-
DVR06_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 6  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

27. OHEDAR07 - Total number of adultroots - code 7

Variable name:
OHEDAR07

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as7 (Decayed severely) during the clinic dental examinations. The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 27
OHEDAR07 Temporary Reformat
Value Condition(s) Description Notes
DVR07_11   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 11  
DVR07_12   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 12  
DVR07_13   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 13  
DVR07_14   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 14  
DVR07_15   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 15  
DVR07_16   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 16  
DVR07_17   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 17  
DVR07_21   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 21  
DVR07_22   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 22  
DVR07_23   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 23  
DVR07_24   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 24  
DVR07_25   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 25  
DVR07_26   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 26  
DVR07_27   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 27  
DVR07_31   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 31  
DVR07_32   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 32  
DVR07_33   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 33  
DVR07_34   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 34  
DVR07_35   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 35  
DVR07_36   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 36  
DVR07_37   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 37  
DVR07_41   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 41  
DVR07_42   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 42  
DVR07_43   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 43  
DVR07_44   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 44  
DVR07_45   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 45  
DVR07_46   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 46  
DVR07_47   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 47  
Table 27
OHEDAR07 Specifications
Value Condition(s) Description Notes
sum (of
DVR07_11-
DVR07_17
DVR07_21-
DVR07_27
DVR07_31-
DVR07_37
DVR07_41-
DVR07_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 7  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

28. OHEDAR11 - Total number of adultroots - code 11

Variable name:
OHEDAR11

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as11 (Decayed - smooth surface caries) during the clinic dentalexaminations. The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 28
OHEDAR11 Temporary Reformat
Value Condition(s) Description Notes
DVR11_11   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 11  
DVR11_12   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 12  
DVR11_13   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 13  
DVR11_14   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 14  
DVR11_15   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 15  
DVR11_16   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 16  
DVR11_17   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 17  
DVR11_21   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 21  
DVR11_22   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 22  
DVR11_23   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 23  
DVR11_24   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 24  
DVR11_25   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 25  
DVR11_26   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 26  
DVR11_27   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 27  
DVR11_31   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 31  
DVR11_32   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 32  
DVR11_33   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 33  
DVR11_34   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 34  
DVR11_35   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 35  
DVR11_36   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 36  
DVR11_37   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 37  
DVR11_41   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 41  
DVR11_42   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 42  
DVR11_43   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 43  
DVR11_44   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 44  
DVR11_45   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 45  
DVR11_46   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 46  
DVR11_47   Temporary variable used to keep a count of tooth conditioncoded as 11, tooth 47  
Table 28
OHEDAR11 Specifications
Value Condition(s) Description Notes
sum (of
DVR11_11-
DVR11_17
DVR11_21-
DVR11_27
DVR11_31-
DVR11_37
DVR11_41-
DVR11_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 11  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

29. OHEDAR12 - Total number of adultroots - code 12

Variable name:
OHEDAR12

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as12 (Filled with amalgam, no other decay) during the clinic dentalexaminations. The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 29
OHEDAR12 Temporary Reformat
Value Condition(s) Description Notes
DVR12_11   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 11  
DVR12_12   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 12  
DVR12_13   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 13  
DVR12_14   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 14  
DVR12_15   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 15  
DVR12_16   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 16  
DVR12_17   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 17  
DVR12_21   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 21  
DVR12_22   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 22  
DVR12_23   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 23  
DVR12_24   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 24  
DVR12_25   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 25  
DVR12_26   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 26  
DVR12_27   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 27  
DVR12_31   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 31  
DVR12_32   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 32  
DVR12_33   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 33  
DVR12_34   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 34  
DVR12_35   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 35  
DVR12_36   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 36  
DVR12_37   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 37  
DVR12_41   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 41  
DVR12_42   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 42  
DVR12_43   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 43  
DVR12_44   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 44  
DVR12_45   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 45  
DVR12_46   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 46  
DVR12_47   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 47  
Table 29
OHEDAR12 Specifications
Value Condition(s) Description Notes
sum (of
DVR12_11-
DVR12_17
DVR12_21-
DVR12_27
DVR12_31-
DVR12_37
DVR12_41-
DVR12_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 12  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

30. OHEDAR13 - Total number of adultroots - code 13

Variable name:
OHEDAR13

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as13 (Filled with other material, (resin, GIC, inlay, crown), noother decay) during the clinic dental examinations. Theprobing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 30
OHEDAR13 Temporary Reformat
Value Condition(s) Description Notes
DVR13_11   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 11  
DVR13_12   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 12  
DVR13_13   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 13  
DVR13_14   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 14  
DVR13_15   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 15  
DVR13_16   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 16  
DVR13_17   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 17  
DVR13_21   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 21  
DVR13_22   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 22  
DVR13_23   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 23  
DVR13_24   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 24  
DVR13_25   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 25  
DVR13_26   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 26  
DVR13_27   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 27  
DVR13_31   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 31  
DVR13_32   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 32  
DVR13_33   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 33  
DVR13_34   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 34  
DVR13_35   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 35  
DVR13_36   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 36  
DVR13_37   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 37  
DVR13_41   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 41  
DVR13_42   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 42  
DVR13_43   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 43  
DVR13_44   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 44  
DVR13_45   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 45  
DVR13_46   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 46  
DVR13_47   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 47  
Table 30
OHEDAR13 Specifications
Value Condition(s) Description Notes
sum (of
DVR13_11-
DVR13_17
DVR13_21-
DVR13_27
DVR13_31-
DVR13_37
DVR13_41-
DVR13_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 13  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

31. OHEDAR14 - Total number of adultroots - code 14

Variable name:
OHEDAR14

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as14 (Filled with amalgam and other material, (resin, GIC, inlay,crown), no other decay) during the clinic dentalexaminations. The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 31
OHEDAR14 Temporary Reformat
Value Condition(s) Description Notes
DVR14_11   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 11  
DVR14_12   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 12  
DVR14_13   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 13  
DVR14_14   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 14  
DVR14_15   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 15  
DVR14_16   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 16  
DVR14_17   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 17  
DVR14_21   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 21  
DVR14_22   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 22  
DVR14_23   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 23  
DVR14_24   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 24  
DVR14_25   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 25  
DVR14_26   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 26  
DVR14_27   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 27  
DVR14_31   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 31  
DVR14_32   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 32  
DVR14_33   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 33  
DVR14_34   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 34  
DVR14_35   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 35  
DVR14_36   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 36  
DVR14_37   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 37  
DVR14_41   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 41  
DVR14_42   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 42  
DVR14_43   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 43  
DVR14_44   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 44  
DVR14_45   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 45  
DVR14_46   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 46  
DVR14_47   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 47  
Table 31
OHEDAR14 Specifications
Value Condition(s) Description Notes
sum (of
DVR14_11-
DVR14_17
DVR14_21-
DVR14_27
DVR14_31-
DVR14_37
DVR14_41-
DVR14_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 14  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

32. OHEDAR15 - Total number of adultroots - code 15

Variable name:
OHEDAR15

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as15 (Filled with amalgam, no other decay, but filling is defectiveand needs replacement) during the clinic dental examinations. The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 32
OHEDAR15 Temporary Reformat
Value Condition(s) Description Notes
DVR15_11   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 11  
DVR15_12   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 12  
DVR15_13   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 13  
DVR15_14   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 14  
DVR15_15   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 15  
DVR15_16   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 16  
DVR15_17   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 17  
DVR15_21   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 21  
DVR15_22   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 22  
DVR15_23   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 23  
DVR15_24   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 24  
DVR15_25   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 25  
DVR15_26   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 26  
DVR15_27   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 27  
DVR15_31   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 31  
DVR15_32   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 32  
DVR15_33   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 33  
DVR15_34   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 34  
DVR15_35   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 35  
DVR15_36   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 36  
DVR15_37   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 37  
DVR15_41   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 41  
DVR15_42   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 42  
DVR15_43   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 43  
DVR15_44   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 44  
DVR15_45   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 45  
DVR15_46   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 46  
DVR15_47   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 47  
Table 32
OHEDAR15 Specifications
Value Condition(s) Description Notes
sum (of
DVR15_11-
DVR15_17
DVR15_21-
DVR15_27
DVR15_31-
DVR15_37
DVR15_41-
DVR15_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 15  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

33. OHEDAR16 - Total number of adultroots - code 16

Variable name:
OHEDAR16

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as16 (Filled with other material (resin, GIC, inlay, crown) butfilling is defective and needs replacement) during the clinicdental examinations. The probing portion of the oral healthexam was completed by all respondents except those meeting theexclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 33
OHEDAR16 Temporary Reformat
Value Condition(s) Description Notes
DVR16_11   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 11  
DVR16_12   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 12  
DVR16_13   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 13  
DVR16_14   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 14  
DVR16_15   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 15  
DVR16_16   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 16  
DVR16_17   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 17  
DVR16_21   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 21  
DVR16_22   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 22  
DVR16_23   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 23  
DVR16_24   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 24  
DVR16_25   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 25  
DVR16_26   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 26  
DVR16_27   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 27  
DVR16_31   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 31  
DVR16_32   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 32  
DVR16_33   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 33  
DVR16_34   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 34  
DVR16_35   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 35  
DVR16_36   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 36  
DVR16_37   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 37  
DVR16_41   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 41  
DVR16_42   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 42  
DVR16_43   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 43  
DVR16_44   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 44  
DVR16_45   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 45  
DVR16_46   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 46  
DVR16_47   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 47  
Table 33
OHEDAR16 Specifications
Value Condition(s) Description Notes
sum (of
DVR16_11-
DVR16_17
DVR16_21-
DVR16_27
DVR16_31-
DVR16_37
DVR16_41-
DVR16_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 16  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

34. OHEDAR17 - Total number of adultroots - code 17

Variable name:
OHEDAR17

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as17 (Filled with amalgam and other material (resin, GIC, inlay,crown) but filling is defective and needs replacement) during theclinic dental examinations. The probing portion of the oralhealth exam was completed by all respondents except those meetingthe exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 34
OHEDAR17 Temporary Reformat
Value Condition(s) Description Notes
DVR17_11   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 11  
DVR17_12   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 12  
DVR17_13   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 13  
DVR17_14   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 14  
DVR17_15   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 15  
DVR17_16   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 16  
DVR17_17   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 17  
DVR17_21   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 21  
DVR17_22   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 22  
DVR17_23   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 23  
DVR17_24   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 24  
DVR17_25   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 25  
DVR17_26   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 26  
DVR17_27   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 27  
DVR17_31   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 31  
DVR17_32   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 32  
DVR17_33   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 33  
DVR17_34   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 34  
DVR17_35   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 35  
DVR17_36   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 36  
DVR17_37   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 37  
DVR17_41   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 41  
DVR17_42   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 42  
DVR17_43   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 43  
DVR17_44   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 44  
DVR17_45   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 45  
DVR17_46   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 46  
DVR17_47   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 47  
Table 34
OHEDAR17 Specifications
Value Condition(s) Description Notes
sum (of
DVR17_11-
DVR17_17
DVR17_21-
DVR17_27
DVR17_31-
DVR17_37
DVR17_41-
DVR17_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 17  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

35. OHEDAR19 - Total number of adultroots - code 19

Variable name:
OHEDAR19

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as19 (Implant) during the clinic dental examinations. Theprobing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:This variable is calculated by creatingarrays for each of 4 quadrants and also creating arrays for thetemporary variables used to maintain a total count for eachquadrant.

Table 35
OHEDAR19 Temporary Reformat
Value Condition(s) Description Notes
DVR19_11   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 11  
DVR19_12   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 12  
DVR19_13   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 13  
DVR19_14   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 14  
DVR19_15   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 15  
DVR19_16   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 16  
DVR19_17   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 17  
DVR19_21   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 21  
DVR19_22   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 22  
DVR19_23   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 23  
DVR19_24   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 24  
DVR19_25   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 25  
DVR19_26   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 26  
DVR19_27   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 27  
DVR19_31   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 31  
DVR19_32   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 32  
DVR19_33   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 33  
DVR19_34   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 34  
DVR19_35   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 35  
DVR19_36   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 36  
DVR19_37   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 37  
DVR19_41   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 41  
DVR19_42   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 42  
DVR19_43   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 43  
DVR19_44   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 44  
DVR19_45   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 45  
DVR19_46   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 46  
DVR19_47   Temporary variable used to keep a count of tooth conditioncoded as 19, tooth 47  
Table 35
OHEDAR19 Specifications
Value Condition(s) Description Notes
sum (of
DVR19_11-
DVR19_17
DVR19_21-
DVR19_27
DVR19_31-
DVR19_37
DVR19_41-
DVR19_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 19  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

36. OHEDAR20 - Total number of adultroots - code 20

Variable name:
OHEDAR20

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as20 (Fractured due to trauma) during the clinic dentalexaminations. The probing portion of the oral health exam wascompleted by all respondents except those meeting the exclusioncriteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 36
OHEDAR20 Temporary Reformat
Value Condition(s) Description Notes
DVR20_11   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 11  
DVR20_12   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 12  
DVR20_13   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 13  
DVR20_14   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 14  
DVR20_15   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 15  
DVR20_16   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 16  
DVR20_17   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 17  
DVR20_21   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 21  
DVR20_22   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 22  
DVR20_23   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 23  
DVR20_24   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 24  
DVR20_25   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 25  
DVR20_26   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 26  
DVR20_27   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 27  
DVR20_31   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 31  
DVR20_32   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 32  
DVR20_33   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 33  
DVR20_34   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 34  
DVR20_35   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 35  
DVR20_36   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 36  
DVR20_37   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 37  
DVR20_41   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 41  
DVR20_42   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 42  
DVR20_43   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 43  
DVR20_44   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 44  
DVR20_45   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 45  
DVR20_46   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 46  
DVR20_47   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 47  
Table 36
OHEDAR20 Specifications
Value Condition(s) Description Notes
sum (of
DVR20_11-
DVR20_17
DVR20_21-
DVR20_27
DVR20_31-
DVR20_37
DVR20_41-
DVR20_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 20  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

37. OHEDAR21 - Total number of adultroots - code 21

Variable name:
OHEDAR21

Based on:
OHE_11, OHE_1R11, OHE_1R12, OHE_1R13, OHE_1R14, OHE_1R15, OHE_1R16,OHE_1R17, OHE_1R21, OHE_1R22, OHE_1R23, OHE_1R24, OHE_1R25,OHE_1R26, OHE_1R27, OHE_1R31, OHE_1R32, OHE_1R33, OHE_1R34,OHE_1R35, OHE_1R36, OHE_1R37, OHE_1R41, OHE_1R42, OHE_1R43,OHE_1R44, OHE_1R45, OHE_1R46, OHE_1R47

Description:
This variable is a count of all permanent (adult) roots recorded as21 (Other) during the clinic dental examinations. The probingportion of the oral health exam was completed by all respondentsexcept those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 37
OHEDAR21 Temporary Reformat
Value Condition(s) Description Notes
DVR21_11   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 11  
DVR21_12   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 12  
DVR21_13   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 13  
DVR21_14   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 14  
DVR21_15   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 15  
DVR21_16   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 16  
DVR21_17   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 17  
DVR21_21   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 21  
DVR21_22   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 22  
DVR21_23   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 23  
DVR21_24   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 24  
DVR21_25   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 25  
DVR21_26   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 26  
DVR21_27   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 27  
DVR21_31   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 31  
DVR21_32   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 32  
DVR21_33   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 33  
DVR21_34   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 34  
DVR21_35   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 35  
DVR21_36   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 36  
DVR21_37   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 37  
DVR21_41   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 41  
DVR21_42   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 42  
DVR21_43   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 43  
DVR21_44   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 44  
DVR21_45   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 45  
DVR21_46   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 46  
DVR21_47   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 47  
Table 37
OHEDAR21 Specifications
Value Condition(s) Description Notes
sum (of
DVR21_11-
DVR21_17
DVR21_21-
DVR21_27
DVR21_31-
DVR21_37
DVR21_41-
DVR21_47)
OHE_11 in (1 2 3) Sum of all permanent (adult) roots coded as 21  
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
9 Else   NS

38. OHEDCS01 - Calculus score recode -teeth 17 and 16

Variable name:
OHEDCS01

Based on:
OHE_32C1

Description:
This variable takes the original calculus score for teeth 17 and 16which was recorded using a scale from 1 to 4 during the clinicdental examinations and recodes the score as a scale from 0 to3.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 38
OHEDCS01 Specifications
Value Condition(s) Description Notes
6 OHE_32C1 = NA Population exclusions NA
9 (OHE_32C1 = DK, RF, NS) At least one required question was not answered (don'tknow, refusal, not stated) NS
0 OHE_32C1 = 1 No calculus  
1 OHE_32C1 = 2 Less than 1/3 of surface covered  
2 OHE_32C1 = 3 1/3 to 2/3 of surface covered  
3 OHE_32C1 = 4 More than 2/3 of surface covered  

39. OHEDCS02 - Calculus score recode -tooth 11

Variable name:
OHEDCS02

Based on:
OHE_32C2

Description:
This variable takes the original calculus score for tooth 11 whichwas recorded using a scale from 1 to 4 during the clinic dentalexaminations and recodes the score as a scale from 0 to 3.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 39
OHEDCS02 Specifications
Value Condition(s) Description Notes
6 OHE_32C2 = NA Population exclusions NA
9 (OHE_32C2 = DK, RF, NS) At least one required question was not answered (don'tknow, refusal, not stated) NS
0 OHE_32C2 = 1 No calculus  
1 OHE_32C2 = 2 Less than 1/3 of surface covered  
2 OHE_32C2 = 3 1/3 to 2/3 of surface covered  
3 OHE_32C2 = 4 More than 2/3 of surface covered  

40. OHEDCS03 - Calculus score recode -teeth 26 and 27

Variable name:
OHEDCS03

Based on:
OHE_32C3

Description:
This variable takes the original calculus score for teeth 26 and 27which was recorded using a scale from 1 to 4 during the clinicdental examinations and recodes the score as a scale from 0 to3.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 40
OHEDCS03 Specifications
Value Condition(s) Description Notes
6 OHE_32C3 = NA Population exclusions NA
9 (OHE_32C3 = DK, RF, NS) At least one required question was not answered (don'tknow, refusal, not stated) NS
0 OHE_32C3 = 1 No calculus  
1 OHE_32C3 = 2 Less than 1/3 of surface covered  
2 OHE_32C3 = 3 1/3 to 2/3 of surface covered  
3 OHE_32C3 = 4 More than 2/3 of surface covered  

41. OHEDCS04 - Calculus score recode -teeth 37 and 36

Variable name:
OHEDCS04

Based on:
OHE_32C4

Description:
This variable takes the original calculus score for teeth 37 and 36which was recorded using a scale from 1 to 4 during the clinicdental examinations and recodes the score as a scale from 0 to3.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 41
OHEDCS04 Specifications
Value Condition(s) Description Notes
6 OHE_32C4 = NA Population exclusions NA
9 (OHE_32C4 = DK, RF, NS) At least one required question was not answered (don'tknow, refusal, not stated) NS
0 OHE_32C4 = 1 No calculus  
1 OHE_32C4 = 2 Less than 1/3 of surface covered  
2 OHE_32C4 = 3 1/3 to 2/3 of surface covered  
3 OHE_32C4 = 4 More than 2/3 of surface covered  

42. OHEDCS05 - Calculus score recode -tooth 31

Variable name:
OHEDCS05

Based on:
OHE_32C5

Description:
This variable takes the original calculus score for tooth 31 whichwas recorded using a scale from 1 to 4 during the clinic dentalexaminations and recodes the score as a scale from 0 to 3.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 42
OHEDCS05 Specifications
Value Condition(s) Description Notes
6 OHE_32C5 = NA Population exclusions NA
9 (OHE_32C5 = DK, RF, NS) At least one required question was not answered (don'tknow, refusal, not stated) NS
0 OHE_32C5 = 1 No calculus  
1 OHE_32C5 = 2 Less than 1/3 of surface covered  
2 OHE_32C5 = 3 1/3 to 2/3 of surface covered  
3 OHE_32C5 = 4 More than 2/3 of surface covered  

43. OHEDCS06 - Calculus score recode -teeth 46 and 47

Variable name:
OHEDCS06

Based on:
OHE_32C6

Description:
This variable takes the original calculus score for teeth 46 and 47which was recorded using a scale from 1 to 4 during the clinicdental examinations and recodes the score as a scale from 0 to3.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 43
OHEDCS06 Specifications
Value Condition(s) Description Notes
6 OHE_32C6 = NA Population exclusions NA
9 (OHE_32C6 = DK, RF, NS) At least one required question was not answered (don'tknow, refusal, not stated) NS
0 OHE_32C6 = 1 No calculus  
1 OHE_32C6 = 2 Less than 1/3 of surface covered  
2 OHE_32C6 = 3 1/3 to 2/3 of surface covered  
3 OHE_32C6 = 4 More than 2/3 of surface covered  

44. OHEDDS01 - Debris score recode -teeth 17 and 16

Variable name:
OHEDDS01

Based on:
OHE_32D1

Description:
This variable takes the original debris score for teeth 17 and 16which was recorded using a scale from 1 to 5 during the clinicdental examinations and recodes the score as a scale from 0 to4.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 44
OHEDDS01 Specifications
Value Condition(s) Description Notes
6 OHE_32D1 = NA Population exclusions NA
9 (OHE_32D1 = DK, RF, NS) At least one required question was not answered (don'tknow, refusal, not stated) NS
0 OHE_32D1 = 1 No soft debris or stain  
1 OHE_32D1 = 2 Less than 1/3 of surface covered  
2 OHE_32D1 = 3 1/3 to 2/3 of surface covered  
3 OHE_32D1 = 4 More than 2/3 of surface covered  
4 OHE_32D1 = 5 Teeth missing  

45. OHEDDS02 - Debris score recode -tooth 11

Variable name:
OHEDDS02

Based on:
OHE_32D2

Description:
This variable takes the original debris score for tooth 11 whichwas recorded using a scale from 1 to 5 during the clinic dentalexaminations and recodes the score as a scale from 0 to 4.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 45
OHEDDS02 Specifications
Value Condition(s) Description Notes
6 OHE_32D2 = NA Population exclusions NA
9 (OHE_32D2 = DK, RF, NS) At least one required question was not answered (don'tknow, refusal, not stated) NS
0 OHE_32D2 = 1 No soft debris or stain  
1 OHE_32D2 = 2 Less than 1/3 of surface covered  
2 OHE_32D2 = 3 1/3 to 2/3 of surface covered  
3 OHE_32D2 = 4 More than 2/3 of surface covered  
4 OHE_32D2 = 5 Teeth missing  

46. OHEDDS03 - Debris score recode -teeth 26 and 27

Variable name:
OHEDDS03

Based on:
OHE_32D3

Description:
This variable takes the original debris score for teeth 26 and 27which was recorded using a scale from 1 to 5 during the clinicdental examinations and recodes the score as a scale from 0 to4.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 46
OHEDDS03 Specifications
Value Condition(s) Description Notes
6 OHE_32D3 = NA Population exclusions NA
9 (OHE_32D3 = DK, RF, NS) At least one required question was not answered (don'tknow, refusal, not stated) NS
0 OHE_32D3 = 1 No soft debris or stain  
1 OHE_32D3 = 2 Less than 1/3 of surface covered  
2 OHE_32D3 = 3 1/3 to 2/3 of surface covered  
3 OHE_32D3 = 4 More than 2/3 of surface covered  
4 OHE_32D3 = 5 Teeth missing  

47. OHEDDS04 - Debris score recode -teeth 37 and 36

Variable name:
OHEDDS04

Based on:
OHE_32D4

Description:
This variable takes the original debris score for teeth 37 and 36which was recorded using a scale from 1 to 5 during the clinicdental examinations and recodes the score as a scale from 0 to4.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 47
OHEDDS04 Specifications
Value Condition(s) Description Notes
6 OHE_32D4 = NA Population exclusions NA
9 (OHE_32D4 = DK, RF, NS) At least one required question was not answered (don'tknow, refusal, not stated) NS
0 OHE_32D4 = 1 No soft debris or stain  
1 OHE_32D4 = 2 Less than 1/3 of surface covered  
2 OHE_32D4 = 3 1/3 to 2/3 of surface covered  
3 OHE_32D4 = 4 More than 2/3 of surface covered  
4 OHE_32D4 = 5 Teeth missing  

48. OHEDDS05 - Debris score recode -tooth 31

Variable name:
OHEDDS05

Based on:
OHE_32D5

Description:
This variable takes the original debris score for tooth 31 whichwas recorded using a scale from 1 to 5 during the clinic dentalexaminations and recodes the score as a scale from 0 to 4.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 48
OHEDDS05 Specifications
Value Condition(s) Description Notes
6 OHE_32D5 = NA Population exclusions NA
9 (OHE_32D5 = DK, RF, NS) At least one required question was not answered (don'tknow, refusal, not stated) NS
0 OHE_32D5 = 1 No soft debris or stain  
1 OHE_32D5 = 2 Less than 1/3 of surface covered  
2 OHE_32D5 = 3 1/3 to 2/3 of surface covered  
3 OHE_32D5 = 4 More than 2/3 of surface covered  
4 OHE_32D5 = 5 Teeth missing  

49. OHEDDS06 - Debris score recode -teeth 46 and 47

Variable name:
OHEDDS06

Based on:
OHE_32D6

Description:
This variable takes the original debris score for teeth 46 and 47which was recorded using a scale from 1 to 5 during the clinicdental examinations and recodes the score as a scale from 0 to4.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 49
OHEDDS06 Specifications
Value Condition(s) Description Notes
6 OHE_32D6 = NA Population exclusions NA
9 (OHE_32D6 = DK, RF, NS) At least one required question was not answered (don'tknow, refusal, not stated) NS
0 OHE_32D6 = 1 No soft debris or stain  
1 OHE_32D6 = 2 Less than 1/3 of surface covered  
2 OHE_32D6 = 3 1/3 to 2/3 of surface covered  
3 OHE_32D6 = 4 More than 2/3 of surface covered  
4 OHE_32D6 = 5 Teeth missing  

50. OHEDDT01 - Total number ofdeciduous teeth - code 1

Variable name:
OHEDDT01

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 1 (Sound - never decayed or restored) during the clinic dental examinations.

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 50
OHEDDT01 Temporary Reformat
Value Condition(s) Description Notes
DVT01_51   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 51  
DVT01_52   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 52  
DVT01_53   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 53  
DVT01_54   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 54  
DVT01_55   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 55  
DVT01_61   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 61  
DVT01_62   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 62  
DVT01_63   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 63  
DVT01_64   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 64  
DVT01_65   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 65  
DVT01_71   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 71  
DVT01_72   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 72  
DVT01_73   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 73  
DVT01_74   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 74  
DVT01_75   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 75  
DVT01_81   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 81  
DVT01_82   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 82  
DVT01_83   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 83  
DVT01_84   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 84  
DVT01_85   Temporary variable used to keep a count of tooth conditioncoded as 1, tooth 85  
Table 50
OHEDDT01 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
sum (of
DVT01_51-
DVT01_55 DVT01_61-
DVT01_65 DVT01_71-
DVT01_75 DVT01_81-DVT01_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 1  
9 Else   NS

51. OHEDDT02 - Total number ofdeciduous teeth - code 2

Variable name:
OHEDDT02

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 2 (Sound - crown sealed, never decayed or otherwise restored) during the clinic dental examinations.

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 51
OHEDDT02 Temporary Reformat
Value Condition(s) Description Notes
DVT02_51   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 51  
DVT02_52   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 52  
DVT02_53   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 53  
DVT02_54   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 54  
DVT02_55   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 55  
DVT02_61   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 61  
DVT02_62   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 62  
DVT02_63   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 63  
DVT02_64   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 64  
DVT02_65   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 65  
DVT02_71   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 71  
DVT02_72   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 72  
DVT02_73   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 73  
DVT02_74   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 74  
DVT02_75   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 75  
DVT02_81   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 81  
DVT02_82   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 82  
DVT02_83   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 83  
DVT02_84   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 84  
DVT02_85   Temporary variable used to keep a count of tooth conditioncoded as 2, tooth 85  
Table 51
OHEDDT02 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
sum (of
DVT02_51-
DVT02_55 DVT02_61-
DVT02_65 DVT02_71-
DVT02_75 DVT02_81-DVT02_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 2  
9 Else   NS

52. OHEDDT03 - Total number ofdeciduous teeth - code 3

Variable name:
OHEDDT03

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 3 (Missing - due to orthodontic treatment) during the clinic dental examinations.

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 52
OHEDDT03 Temporary Reformat
Value Condition(s) Description Notes
DVT03_51   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 51  
DVT03_52   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 52  
DVT03_53   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 53  
DVT03_54   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 54  
DVT03_55   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 55  
DVT03_61   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 61  
DVT03_62   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 62  
DVT03_63   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 63  
DVT03_64   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 64  
DVT03_65   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 65  
DVT03_71   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 71  
DVT03_72   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 72  
DVT03_73   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 73  
DVT03_74   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 74  
DVT03_75   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 75  
DVT03_81   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 81  
DVT03_82   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 82  
DVT03_83   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 83  
DVT03_84   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 84  
DVT03_85   Temporary variable used to keep a count of tooth conditioncoded as 3, tooth 85  
Table 52
OHEDDT03 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
sum (of
DVT03_51-
DVT03_55 DVT03_61-
DVT03_65 DVT03_71-
DVT03_75 DVT03_81-DVT03_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 3  
9 Else   NS

53. OHEDDT04 - Total number ofdeciduous teeth - code 4

Variable name:
OHEDDT04

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 4 (Missing - due to trauma) during the clinic dental examinations.

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 53
OHEDDT04 Temporary Reformat
Value Condition(s) Description Notes
DVT04_51   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 51  
DVT04_52   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 52  
DVT04_53   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 53  
DVT04_54   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 54  
DVT04_55   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 55  
DVT04_61   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 61  
DVT04_62   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 62  
DVT04_63   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 63  
DVT04_64   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 64  
DVT04_65   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 65  
DVT04_71   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 71  
DVT04_72   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 72  
DVT04_73   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 73  
DVT04_74   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 74  
DVT04_75   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 75  
DVT04_81   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 81  
DVT04_82   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 82  
DVT04_83   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 83  
DVT04_84   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 84  
DVT04_85   Temporary variable used to keep a count of tooth conditioncoded as 4, tooth 85  
Table 53
OHEDDT04 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
sum (of
DVT04_51-
DVT04_55 DVT04_61-
DVT04_65 DVT04_71-
DVT04_75 DVT04_81-DVT04_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 4  
9 Else   NS

54. OHEDDT05 - Total number ofdeciduous teeth - code 5

Variable name:
OHEDDT05

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 5 (Missing - due to caries or periodontal disease) during the clinic dental examinations.

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 54
OHEDDT05 Temporary Reformat
Value Condition(s) Description Notes
DVT05_51   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 51  
DVT05_52   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 52  
DVT05_53   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 53  
DVT05_54   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 54  
DVT05_55   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 55  
DVT05_61   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 61  
DVT05_62   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 62  
DVT05_63   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 63  
DVT05_64   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 64  
DVT05_65   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 65  
DVT05_71   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 71  
DVT05_72   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 72  
DVT05_73   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 73  
DVT05_74   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 74  
DVT05_75   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 75  
DVT05_81   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 81  
DVT05_82   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 82  
DVT05_83   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 83  
DVT05_84   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 84  
DVT05_85   Temporary variable used to keep a count of tooth conditioncoded as 5, tooth 85  
Table 54
OHEDDT05 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
sum (of
DVT05_51-
DVT05_55 DVT05_61-
DVT05_65 DVT05_71-
DVT05_75 DVT05_81-DVT05_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 5  
9 Else   NS

55. OHEDDT06 - Total number ofdeciduous teeth - code 6

Variable name:
OHEDDT06

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 6 (Unerupted tooth, congenitally missing or unexposed root) during the clinic dental examinations.

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 55
OHEDDT06 Temporary Reformat
Value Condition(s) Description Notes
DVT06_51   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 51  
DVT06_52   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 52  
DVT06_53   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 53  
DVT06_54   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 54  
DVT06_55   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 55  
DVT06_61   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 61  
DVT06_62   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 62  
DVT06_63   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 63  
DVT06_64   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 64  
DVT06_65   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 65  
DVT06_71   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 71  
DVT06_72   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 72  
DVT06_73   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 73  
DVT06_74   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 74  
DVT06_75   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 75  
DVT06_81   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 81  
DVT06_82   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 82  
DVT06_83   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 83  
DVT06_84   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 84  
DVT06_85   Temporary variable used to keep a count of tooth conditioncoded as 6, tooth 85  
Table 55
OHEDDT06 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
sum (of
DVT06_51-
DVT06_55 DVT06_61-
DVT06_65 DVT06_71-
DVT06_75 DVT06_81-DVT06_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 6  
9 Else   NS

56. OHEDDT07 - Total number ofdeciduous teeth - code 7

Variable name:
OHEDDT07

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 7 (Decayed severely) during the clinic dental examinations.

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 56
OHEDDT07 Temporary Reformat
Value Condition(s) Description Notes
DVT07_51   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 51  
DVT07_52   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 52  
DVT07_53   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 53  
DVT07_54   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 54  
DVT07_55   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 55  
DVT07_61   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 61  
DVT07_62   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 62  
DVT07_63   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 63  
DVT07_64   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 64  
DVT07_65   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 65  
DVT07_71   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 71  
DVT07_72   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 72  
DVT07_73   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 73  
DVT07_74   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 74  
DVT07_75   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 75  
DVT07_81   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 81  
DVT07_82   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 82  
DVT07_83   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 83  
DVT07_84   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 84  
DVT07_85   Temporary variable used to keep a count of tooth conditioncoded as 7, tooth 85  
Table 56
OHEDDT07 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
sum (of
DVT07_51-
DVT07_55 DVT07_61-
DVT07_65 DVT07_71-
DVT07_75 DVT07_81-DVT07_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 7  
9 Else   NS

57. OHEDDT08 - Total number ofdeciduous teeth - code 8

Variable name:
OHEDDT08

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 8 (Decayed - pit and fissure caries) during the clinic dental examinations.

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 57
OHEDDT08 Temporary Reformat
Value Condition(s) Description Notes
DVT08_51   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 51  
DVT08_52   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 52  
DVT08_53   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 53  
DVT08_54   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 54  
DVT08_55   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 55  
DVT08_61   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 61  
DVT08_62   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 62  
DVT08_63   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 63  
DVT08_64   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 64  
DVT08_65   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 65  
DVT08_71   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 71  
DVT08_72   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 72  
DVT08_73   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 73  
DVT08_74   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 74  
DVT08_75   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 75  
DVT08_81   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 81  
DVT08_82   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 82  
DVT08_83   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 83  
DVT08_84   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 84  
DVT08_85   Temporary variable used to keep a count of tooth conditioncoded as 8, tooth 85  
Table 57
OHEDDT08 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
sum (of
DVT08_51-
DVT08_55 DVT08_61-
DVT08_65 DVT08_71-
DVT08_75 DVT08_81-DVT08_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 8  
9 Else   NS

58. OHEDDT09 - Total number ofdeciduous teeth - code 9

Variable name:
OHEDDT09

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 9 (Decayed - smooth surface caries) during the clinic dental examinations.

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 58
OHEDDT09 Temporary Reformat
Value Condition(s) Description Notes
DVT09_51   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 51  
DVT09_52   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 52  
DVT09_53   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 53  
DVT09_54   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 54  
DVT09_55   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 55  
DVT09_61   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 61  
DVT09_62   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 62  
DVT09_63   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 63  
DVT09_64   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 64  
DVT09_65   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 65  
DVT09_71   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 71  
DVT09_72   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 72  
DVT09_73   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 73  
DVT09_74   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 74  
DVT09_75   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 75  
DVT09_81   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 81  
DVT09_82   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 82  
DVT09_83   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 83  
DVT09_84   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 84  
DVT09_85   Temporary variable used to keep a count of tooth conditioncoded as 9, tooth 85  
Table 58
OHEDDT09 Specifications
Value Condition(s)  Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
sum (of
DVT09_51-
DVT09_55 DVT09_61-
DVT09_65 DVT09_71-
DVT09_75 DVT09_81-DVT09_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 9  
9 Else   NS

59. OHEDDT10 - Total number ofdeciduous teeth - code 10

Variable name:
OHEDDT10

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 10 (Decayed - both smooth surface and pit and fissure caries) during the clinic dental examinations.

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 59
OHEDDT10 Temporary Reformat
Value Condition(s) Description Notes
DVT10_51   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 51  
DVT10_52   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 52  
DVT10_53   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 53  
DVT10_54   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 54  
DVT10_55   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 55  
DVT10_61   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 61  
DVT10_62   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 62  
DVT10_63   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 63  
DVT10_64   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 64  
DVT10_65   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 65  
DVT10_71   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 71  
DVT10_72   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 72  
DVT10_73   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 73  
DVT10_74   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 74  
DVT10_75   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 75  
DVT10_81   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 81  
DVT10_82   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 82  
DVT10_83   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 83  
DVT10_84   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 84  
DVT10_85   Temporary variable used to keep a count of tooth conditioncoded as 10, tooth 85  
Table 59
OHEDDT10 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
sum (of
DVT10_51-
DVT10_55 DVT10_61-
DVT10_65 DVT10_71-
DVT10_75 DVT10_81-DVT10_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 10  
9 Else   NS

60. OHEDDT12 - Total number ofdeciduous teeth - code 12

Variable name:
OHEDDT12

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 12 (Filled with amalgam, no other decay) during the clinic dental examinations.

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 60
OHEDDT12 Temporary Reformat
Value Condition(s) Description Notes
DVT12_51   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 51  
DVT12_52   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 52  
DVT12_53   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 53  
DVT12_54   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 54  
DVT12_55   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 55  
DVT12_61   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 61  
DVT12_62   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 62  
DVT12_63   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 63  
DVT12_64   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 64  
DVT12_65   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 65  
DVT12_71   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 71  
DVT12_72   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 72  
DVT12_73   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 73  
DVT12_74   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 74  
DVT12_75   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 75  
DVT12_81   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 81  
DVT12_82   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 82  
DVT12_83   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 83  
DVT12_84   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 84  
DVT12_85   Temporary variable used to keep a count of tooth conditioncoded as 12, tooth 85  
Table 60
OHEDDT12 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
sum (of
DVT12_51-
DVT12_55 DVT12_61-
DVT12_65 DVT12_71-
DVT12_75 DVT12_81-DVT12_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 12  
9 Else   NS

61. OHEDDT13 - Total number ofdeciduous teeth - code 13

Variable name:
OHEDDT13

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 13 (Filled with other material (resin, GIC, inlay, crown), no other decay) during the clinic dental examinations.

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 61
OHEDDT13 Temporary Reformat
Value Condition(s) Description Notes
DVT13_51   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 51  
DVT13_52   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 52  
DVT13_53   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 53  
DVT13_54   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 54  
DVT13_55   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 55  
DVT13_61   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 61  
DVT13_62   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 62  
DVT13_63   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 63  
DVT13_64   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 64  
DVT13_65   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 65  
DVT13_71   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 71  
DVT13_72   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 72  
DVT13_73   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 73  
DVT13_74   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 74  
DVT13_75   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 75  
DVT13_81   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 81  
DVT13_82   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 82  
DVT13_83   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 83  
DVT13_84   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 84  
DVT13_85   Temporary variable used to keep a count of tooth conditioncoded as 13, tooth 85  
Table 61
OHEDDT13 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
sum (of
DVT13_51-
DVT13_55 DVT13_61-
DVT13_65 DVT13_71-
DVT13_75 DVT13_81-DVT13_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 13  
9 Else   NS

62. OHEDDT14 - Total number ofdeciduous teeth - code 14

Variable name:
OHEDDT14

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 14 (Filled with amalgam and other material (resin, GIC, inlay, crown), no other decay) during the clinic dental examinations.

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 62
OHEDDT14 Temporary Reformat
Value Condition(s) Description Notes
DVT14_51   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 51  
DVT14_52   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 52  
DVT14_53   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 53  
DVT14_54   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 54  
DVT14_55   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 55  
DVT14_61   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 61  
DVT14_62   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 62  
DVT14_63   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 63  
DVT14_64   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 64  
DVT14_65   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 65  
DVT14_71   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 71  
DVT14_72   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 72  
DVT14_73   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 73  
DVT14_74   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 74  
DVT14_75   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 75  
DVT14_81   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 81  
DVT14_82   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 82  
DVT14_83   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 83  
DVT14_84   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 84  
DVT14_85   Temporary variable used to keep a count of tooth conditioncoded as 14, tooth 85  
Table 62
OHEDDT14 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
sum (of
DVT14_51-
DVT14_55 DVT14_61-
DVT14_65 DVT14_71-
DVT14_75 DVT14_81-DVT14_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 14  
9 Else   NS

63. OHEDDT15 - Total number ofdeciduous teeth - code 15

Variable name:
OHEDDT15

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 15 (Filled with amalgam, no other decay, but filling is defective and needs replacement) during the clinic dental examinations

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 63
OHEDDT15 Temporary Reformat
Value Condition(s) Description Notes
DVT15_51   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 51  
DVT15_52   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 52  
DVT15_53   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 53  
DVT15_54   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 54  
DVT15_55   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 55  
DVT15_61   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 61  
DVT15_62   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 62  
DVT15_63   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 63  
DVT15_64   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 64  
DVT15_65   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 65  
DVT15_71   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 71  
DVT15_72   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 72  
DVT15_73   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 73  
DVT15_74   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 74  
DVT15_75   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 75  
DVT15_81   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 81  
DVT15_82   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 82  
DVT15_83   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 83  
DVT15_84   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 84  
DVT15_85   Temporary variable used to keep a count of tooth conditioncoded as 15, tooth 85  
Table 63
OHEDDT15 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
sum (of
DVT15_51-
DVT15_55 DVT15_61-
DVT15_65 DVT15_71-
DVT15_75 DVT15_81-DVT15_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 15  
9 Else   NS

64. OHEDDT16 - Total number ofdeciduous teeth - code 16

Variable name:
OHEDDT16

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 16 (Filled with other material (resin, GIC, inlay, crown) but filling is defective and needs replacement) during the clinic dental examinations.

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 64
OHEDDT16 Temporary Reformat
Value Condition(s) Description Notes
DVT16_51   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 51  
DVT16_52   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 52  
DVT16_53   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 53  
DVT16_54   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 54  
DVT16_55   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 55  
DVT16_61   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 61  
DVT16_62   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 62  
DVT16_63   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 63  
DVT16_64   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 64  
DVT16_65   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 65  
DVT16_71   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 71  
DVT16_72   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 72  
DVT16_73   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 73  
DVT16_74   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 74  
DVT16_75   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 75  
DVT16_81   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 81  
DVT16_82   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 82  
DVT16_83   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 83  
DVT16_84   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 84  
DVT16_85   Temporary variable used to keep a count of tooth conditioncoded as 16, tooth 85  
Table 64
OHEDDT16 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
sum (of
DVT16_51-
DVT16_55 DVT16_61-
DVT16_65 DVT16_71-
DVT16_75 DVT16_81-DVT16_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 16  
9 Else   NS

65. OHEDDT17 - Total number ofdeciduous teeth - code 17

Variable name:
OHEDDT17

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 17 (Filled with amalgam and other material (resin, GIC, inlay, crown) but filling is defective and needs replacement) during the clinic dental examinations.

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 65
OHEDDT17 Temporary Reformat
Value Condition(s) Description Notes
DVT17_51   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 51  
DVT17_52   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 52  
DVT17_53   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 53  
DVT17_54   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 54  
DVT17_55   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 55  
DVT17_61   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 61  
DVT17_62   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 62  
DVT17_63   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 63  
DVT17_64   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 64  
DVT17_65   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 65  
DVT17_71   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 71  
DVT17_72   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 72  
DVT17_73   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 73  
DVT17_74   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 74  
DVT17_75   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 75  
DVT17_81   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 81  
DVT17_82   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 82  
DVT17_83   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 83  
DVT17_84   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 84  
DVT17_85   Temporary variable used to keep a count of tooth conditioncoded as 17, tooth 85  
Table 65
OHEDDT17 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
sum (of
DVT17_51-
DVT17_55 DVT17_61-
DVT17_65 DVT17_71-
DVT17_75 DVT17_81-DVT17_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 17  
9 Else   NS

66. OHEDDT20 - Total number ofdeciduous teeth - code 20

Variable name:
OHEDDT20

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 20 (Fractured due to trauma) during the clinic dental examinations.

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 66
OHEDDT20 Temporary Reformat
Value Condition(s) Description Notes
DVT20_51   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 51  
DVT20_52   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 52  
DVT20_53   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 53  
DVT20_54   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 54  
DVT20_55   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 55  
DVT20_61   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 61  
DVT20_62   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 62  
DVT20_63   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 63  
DVT20_64   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 64  
DVT20_65   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 65  
DVT20_71   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 71  
DVT20_72   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 72  
DVT20_73   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 73  
DVT20_74   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 74  
DVT20_75   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 75  
DVT20_81   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 81  
DVT20_82   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 82  
DVT20_83   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 83  
DVT20_84   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 84  
DVT20_85   Temporary variable used to keep a count of tooth conditioncoded as 20, tooth 85  
Table 66
OHEDDT20 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
sum (of
DVT20_51-
DVT20_55 DVT20_61-
DVT20_65 DVT20_71-
DVT20_75 DVT20_81-DVT20_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 20  
9 Else   NS

67. OHEDDT21 - Total number ofdeciduous teeth - code 21

Variable name:
OHEDDT21

Based on:
OHE_11, OHE_1T51, OHE_1T52, OHE_1T53, OHE_1T54, OHE_1T55, OHE_1T61,OHE_1T62, OHE_1T63, OHE_1T64, OHE_1T65, OHE_1T71, OHE_1T72,OHE_1T73, OHE_1T74, OHE_1T75, OHE_1T81, OHE_1T82, OHE_1T83,OHE_1T84, OHE_1T85

Description:
This variable is a count of all deciduous (baby) teeth recorded as 21 (Other) during the clinic dental examinations.

Note:
This variable is calculated by creating arrays for each of 4quadrants and also creating arrays for the temporary variables usedto maintain a total count for each quadrant.

Table 67
OHEDDT21 Temporary Reformat
Value Condition(s) Description Notes
DVT21_51   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 51  
DVT21_52   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 52  
DVT21_53   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 53  
DVT21_54   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 54  
DVT21_55   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 55  
DVT21_61   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 61  
DVT21_62   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 62  
DVT21_63   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 63  
DVT21_64   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 64  
DVT21_65   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 65  
DVT21_71   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 71  
DVT21_72   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 72  
DVT21_73   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 73  
DVT21_74   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 74  
DVT21_75   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 75  
DVT21_81   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 81  
DVT21_82   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 82  
DVT21_83   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 83  
DVT21_84   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 84  
DVT21_85   Temporary variable used to keep a count of tooth conditioncoded as 21, tooth 85  
Table 67
OHEDDT21 Specifications
Value Condition(s) Description Notes
6 OHE_11 in (4 5) Population exclusions NA
9 OHE_11 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
sum (of
DVT21_51-
DVT21_55 DVT21_61-
DVT21_65 DVT21_71-
DVT21_75 DVT21_81-DVT21_85)
OHE_11 in (1 2 3) Sum of all deciduous (baby) teeth coded as 21  
9 Else   NS

68. OHEDFLUO - Fluorosis scorerecode

Variable name:
OHEDFLUO

Based on:
OHE_20

Description:
During the clinic dental examinations the fluorosis score wasrecorded using a scale of 1 to 7 for the most affected pair ofteeth for teeth 11, 12, 21 or 22. If the two teeth were notequally affected, the score for the less affected of the two wasrecorded. This variable recodes the fluorosis score into ascale of 0 to 6.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 68
OHEDFLUO Specifications
Value Condition(s) Description Notes
99 (OHE_N20 = DK, RF, NS) At least one required question was not answered (don'tknow, refusal, not stated) NS
96 OHE_20 = NA Population exclusions NA
0 OHE_20 = 1 Normal  
1 OHE_20 = 2 Questionable  
2 OHE_20 = 3 Very mild  
3 OHE_20 = 4 Mild  
4 OHE_20 = 5 Moderate  
5 OHE_20 = 6 Severe  
6 OHE_20 = 7 All 4 anterior teeth absent  

69. OHEDGS12 - Gingivitis score recode- tooth 12

Variable name:
OHEDGS12

Based on:
OHE_31G2

Description:
This variable takes theoriginal gingivitis score for tooth 12 which was recorded using ascale from 1 to 5 during the clinic dental examinations and recodesthe score as a scale from 0 to 4.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 69
OHEDGS12 Specifications
Value Condition(s) Description Notes
6 OHE_31G2 = NA Population exclusions NA
9 (OHE_31G2 = DK, RF, NS) At least one required question was not answered (don'tknow, refusal, not stated) NS
0 OHE_31G2 = 1 No inflammation  
1 OHE_31G2 = 2 Mild inflammation  
2 OHE_31G2 = 3 Moderate inflammation  
3 OHE_31G2 = 4 Severe inflammation  
4 OHE_31G2 = 5 Tooth missing  

70. OHEDGS16 - Gingivitis score recode- tooth 16

Variable name:
OHEDGS16

Based on:
OHE_31G1

Description:
This variable takes the original gingivitis score for tooth 16which was recorded using a scale from 1 to 5 during the clinicdental examinations and recodes the score as a scale from 0 to4.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 70
OHEDGS16 Specifications
Value Condition(s) Description Notes
6 OHE_31G1 = NA Population exclusions NA
9 (OHE_31G1 = DK, RF, NS) At least one required question was not answered (don'tknow, refusal, not stated) NS
0 OHE_31G1 = 1 No inflammation  
1 OHE_31G1 = 2 Mild inflammation  
2 OHE_31G1 = 3 Moderate inflammation  
3 OHE_31G1 = 4 Severe inflammation  
4 OHE_31G1 = 5 Tooth missing  

71. OHEDGS24 - Gingivitis score recode- tooth 24

Variable name:
OHEDGS24

Based on:
OHE_31G3

Description:
This variable takes the original gingivitis score for tooth 24which was recorded using a scale from 1 to 5 during the clinicdental examinations and recodes the score as a scale from 0 to4.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 71
OHEDGS24 Specifications
Value Condition(s) Description Notes
6 OHE_31G3 = NA Population exclusions NA
9 (OHE_31G3 = DK, RF, NS) At least one required question was not answered (don'tknow, refusal, not stated) NS
0 OHE_31G3 = 1 No inflammation  
1 OHE_31G3 = 2 Mild inflammation  
2 OHE_31G3 = 3 Moderate inflammation  
3 OHE_31G3 = 4 Severe inflammation  
4 OHE_31G3 = 5 Tooth missing  

72. OHEDGS32 - Gingivitis score recode- tooth 32

Variable name:
OHEDGS32

Based on:
OHE_31G5

Description:
This variable takes the original gingivitis score for tooth 32which was recorded using a scale from 1 to 5 during the clinicdental examinations and recodes the score as a scale from 0 to4.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 72
OHEDGS32 Specifications
Value Condition(s) Description Notes
6 OHE_31G5 = NA Population exclusions NA
9 (OHE_31G5 = DK, RF, NS) At least one required question was not answered (don'tknow, refusal, not stated) NS
0 OHE_31G5 = 1 No inflammation  
1 OHE_31G5 = 2 Mild inflammation  
2 OHE_31G5 = 3 Moderate inflammation  
3 OHE_31G5 = 4 Severe inflammation  
4 OHE_31G5 = 5 Tooth missing  

73. OHEDGS36 - Gingivitis score recode- tooth 36

Variable name:
OHEDGS36

Based on:
OHE_31G4

Description:
This variable takes the original gingivitis score for tooth 36which was recorded using a scale from 1 to 5 during the clinicdental examinations and recodes the score as a scale from 0 to4.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 73
OHEDGS36 Specifications
Value Condition(s) Description Notes
6 OHE_31G4 = NA Population exclusions NA
9 (OHE_31G4 = DK, RF, NS) At least one required question was not answered (don'tknow, refusal, not stated) NS
0 OHE_31G4 = 1 No inflammation  
1 OHE_31G4 = 2 Mild inflammation  
2 OHE_31G4 = 3 Moderate inflammation  
3 OHE_31G4 = 4 Severe inflammation  
4 OHE_31G4 = 5 Tooth missing  

74. OHEDGS44 - Gingivitis score recode- tooth 44

Variable name:
OHEDGS44

Based on:
OHE_31G6

Description:
This variable takes the original gingivitis score for tooth 44which was recorded using a scale from 1 to 5 during the clinicdental examinations and recodes the score as a scale from 0 to4.

Note:
The probing portion of the oral health exam was completed by allrespondents except those meeting the exclusion criteria:

  1. Respondents with hemophilia
  2. Respondents who have had chemotherapy within the past 4weeks
  3. Respondents who answer "yes" to any question in the Oral HealthRestrictions block (OHR)
  4. Respondents who are younger than 15
Table 74
OHEDGS44 Specifications
Value Condition(s) Description Notes
6 OHE_31G6 = NA Population exclusions NA
9 (OHE_31G6 = DK, RF, NS) At least one required question was not answered (don'tknow, refusal, not stated) NS
0 OHE_31G6 = 1 No inflammation  
1 OHE_31G6 = 2 Mild inflammation  
2 OHE_31G6 = 3 Moderate inflammation  
3 OHE_31G6 = 4 Severe inflammation  
4 OHE_31G6 = 5 Tooth missing  

75. OHRD25 - Test exclusion –probing

Variable name:
OHRD25

Based on:
OHR_11, OHR_12, OHR_13, OHR_14,OHR_15, OHR_16, OHR_17, OHR_19, OHR_20, OHR_21, OHR_22, OHR_23,OHR_24

Description:
If the respondent answered yesto any of the Oral Health Restriction questions, probing was notperformed.

Note:
Created in the Clinic data collection application

Table 75
OHRD25 Specifications
Value Condition(s) Description Notes
9 OHR_11 > NA or
OHR_12 > NA or
OHR_13 > NA or
OHR_14 > NA or
OHR_15 > NA or
OHR_16 > NA or
OHR_17 > NA or
OHR_19 > NA or
OHR_20 > NA or
OHR_21 > NA or
OHR_22 > NA or
OHR_23 > NA or
OHR_24 > NA
At least one required question was not answered (don'tknow, refusal, not stated) NS
6 OHR_11 = NA and
OHR_12 = NA and
OHR_13 = NA and
OHR_14 = NA and
OHR_15 = NA and
OHR_16 = NA and
OHR_17 = NA and
OHR_19 = NA and
OHR_20 = NA and
OHR_21 = NA and
OHR_22 = NA and
OHR_23 = NA and
OHR_24 = NA
Population exclusions NA
1 OHR_11 = 1 or
OHR_12 = 1 or
OHR_13 = 1 or
OHR_14 = 1 or
OHR_15 = 1 or
OHR_16 = 1 or
OHR_17 = 1 or
OHR_19 = 1 or
OHR_20 = 1 or
OHR_21 = 1 or
OHR_22 = 1 or
OHR_23 = 1 or
OHR_24 = 1
The respondent answered yes to one of the Oral HealthRestriction questions  
2 Else    

76. OHMD31Y - Brushing teeth - numbertimes per year

Variable name:
OHMD31Y

Based on:
OHM_31, OHM_31N

Description:
The number of times per year the respondent brushes his/her teethand/or dentures.

Note:
Created in the Household Post-Verify process.

Table 76
OHMD31Y Specifications
Value Condition(s) Description Notes
9996 OHM_31N = NA Population exclusions NA
0 OHM_31 = 0 Never  
OHM_31 * 365 OHM_31N = 1 Reported number of times per day converted to derived number oftimes per year  
OHM_31 * 52 OHM_31N = 2 Reported number of times per week converted to derived numberof times per year  
OHM_31 * 12 OHM_31N = 3 Reported number of times per month converted to derived numberof times per year  
OHM_31 OHM_31N = 4 Reported number of times per year  
9999 Else At least one required question was not answered (don'tknow, refusal, not stated) NS

77. OHMD32Y - Flossing teeth - numbertimes per year

Variable name:
OHMD32Y

Based on:
OHM_32, OHM_32N

Description:
The number of times per year the respondent flosses his/herteeth.

Note:
Created in the Household Post-Verify process.

Table 77
OHMD32Y Specifications
Value Condition(s) Description Notes
9996 OHM_32N = NA Population exclusions NA
0 OHM_32 = 0 Never  
OHM_32 * 365 OHM_32N = 1 Reported number of times per day converted to derived number oftimes per year  
OHM_32 * 52 OHM_32N = 2 Reported number of times per week converted to derived numberof times per year  
OHM_32 * 12 OHM_32N = 3 Reported number of times per month converted to derived numberof times per year  
OHM_32 OHM_32N = 4 Reported number of times per year  
9999 Else At least one required question was not answered (don'tknow, refusal, not stated) NS

Physical activities (6 DVs)

1. PACDEE - Daily EnergyExpenditure

Variable name:
PACDEE

Based on:
PAC_11W, PAC_12A, PAC_12B, PAC_12C, PAC_12D, PAC_12E, PAC_12F,PAC_12G, PAC_12H, PAC_12I, PAC_12J, PAC_12K, PAC_12L, PAC_12M,PAC_12N, PAC_12O, PAC_12P, PAC_12Q, PAC_12R, PAC_12S, PAC_12T,PAC_12U, PAC_12V, PAC_12X, PAC_12Y, PAC_13A, PAC_13B, PAC_13C,PAC_13D, PAC_13E, PAC_13F, PAC_13G, PAC_13H, PAC_13I, PAC_13J,PAC_13K, PAC_13L, PAC_13M, PAC_13N, PAC_13O, PAC_13P, PAC_13Q,PAC_13R, PAC_13S, PAC_13T, PAC_13U, PAC_13V, PAC_13X,PAC_13Y, DHH_AGE

Description:
This variable is a measure of the average daily energy expendedduring leisure time activities by the respondent in the past threemonths.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents less than 12 years of age were excluded from thepopulation.
Energy Expenditure is calculated using the frequency and durationper session of the physical activity as well as the MET value ofthe activity. The MET is a value of metabolic energy cost expressedas a multiple of the resting metabolic rate. For example, anactivity of 4 METS requires four times the amount of energy ascompared to when the body is at rest.
EE (Energy Expenditure for each activity) = (N X D X METvalue) /365
Where:
N = the number of times a respondent engaged in an activity over a12 month period
D = the average duration in hours of the activity
MET value = the energy cost of the activity expressed askilocalories expended per kilogram of body weight per hour ofactivity (kcal/kg per hour)/365 (to convert yearly data into dailydata)

MET values tend to be expressed in three intensity levels (i.e.low, medium, high). The CCHS questions did not ask therespondent to specify the intensity level of their activities.Therefore the MET values adopted correspond to the low intensityvalue of each activity. This approach is adopted from the CanadianFitness and Lifestyle Research Institute because individuals tendto overestimate the intensity, frequency and duration of theiractivities.

* Times were assigned an average duration value for thecalculation, as with NPHS:
(13 minutes or .2167 hour, 23 minutes or .3833 hour, 45 minutes or.75 hour, 60 minutes or 1 hour)

Internet site:
Canadian Fitness and Lifestyle Research Institute: www.cflri.ca

Table 1
PACDEE Temporary Reformat

PACDEEA

Value Condition(s) Description Notes
0 PAC_13A = NA Did not participate in activity Walking for exercise
0 (PAC_13A = DK, RF, NS) Required question was not answered (don't know, refusal,not stated) Walking for exercise
(PAC_12A × 4 ×
.2167 × 3) / 365
PAC_13A = 1 Calculate EE for < 15 min* Walking for exercise
(PAC_12A × 4 ×
.3833 × 3) / 365
PAC_13A = 2 Calculate EE for 16 to 30 min* Walking for exercise
(PAC_12A × 4 ×
.75 × 3) / 365
PAC_13A = 3 Calculate EE for 31 to 60 min* Walking for exercise
(PAC_12A × 4 × 1
× 3) / 365
PAC_13A = 4 Calculate EE for > 60 min* Walking for exercise


PACDEEB

Value Condition(s) Description Notes
0 PAC_13B = NA Did not participate in activity Gardening or yard work
0 (PAC_13B = DK, RF, NS) Required question was not answered (don't know, refusal,not stated) Gardening or yard work
(PAC_12B × 4 ×
.2167 × 3) / 365
PAC_13B = 1 Calculate EE for < 15 min* Gardening or yard work
(PAC_12B × 4 ×
.3833 × 3) / 365
PAC_13B = 2 Calculate EE for 16 to 30 min* Gardening or yard work
(PAC_12B × 4 ×
.75 × 3) / 365
PAC_13B = 3 Calculate EE for 31 to 60 min* Gardening or yard work
(PAC_12B × 4 × 1
× 3) / 365
PAC_13B = 4 Calculate EE for > 60 min* Gardening or yard work


PACDEEC

Value Condition(s) Description Notes
0 PAC_13C = NA Did not participate in activity Swimming
0 (PAC_13C = DK, RF, NS) Required question was not answered (don't know, refusal,not stated) Swimming
(PAC_12C × 4 ×
.2167 × 3) / 365
PAC_13C = 1 Calculate EE for < 15 min* Swimming
(PAC_12C × 4 ×
.3833 × 3) / 365
PAC_13C = 2 Calculate EE for 16 to 30 min* Swimming
(PAC_12C × 4 ×
.75 × 3) / 365
PAC_13C = 3 Calculate EE for 31 to 60 min* Swimming
(PAC_12C × 4 × 1
× 3) / 365
PAC_13C = 4 Calculate EE for > 60 min* Swimming


PACDEED

Value Condition(s) Description Notes
0 PAC_13D = NA Did not participate in activity Bicycling
0 (PAC_13D = DK, RF, NS) Required question was not answered (don't know, refusal,not stated) Bicycling
(PAC_12D × 4 ×
.2167 × 4) / 365
PAC_13D = 1 Calculate EE for < 15 min* Bicycling
(PAC_12D × 4 ×
.3833 × 4) / 365
PAC_13D = 2 Calculate EE for 16 to 30 min* Bicycling
(PAC_12D × 4 ×
.75 × 4) / 365
PAC_13D = 3 Calculate EE for 31 to 60 min* Bicycling
(PAC_12D × 4 × 1
× 4) / 365
PAC_13D = 4 Calculate EE for > 60 min* Bicycling


PACDEEE

Value Condition(s) Description Notes
0 PAC_13E = NA Did not participate in activity Popular or social dance
0 (PAC_13E = DK, RF, NS) Required question was not answered (don't know, refusal,not stated) Popular or social dance
(PAC_12E × 4 ×
.2167 × 3) / 365
PAC_13E = 1 Calculate EE for < 15 min* Popular or social dance
(PAC_12E × 4 ×
.3833 × 3) / 365
PAC_13E = 2 Calculate EE for 16 to 30 min* Popular or social dance
(PAC_12E × 4 ×
.75 × 3) / 365
PAC_13E = 3 Calculate EE for 31 to 60 min* Popular or social dance
(PAC_12E × 4 × 1
× 3) / 365
PAC_13E = 4 Calculate EE for > 60 min* Popular or social dance


PACDEEF

Value Condition(s) Description Notes
0 PAC_13F = NA Did not participate in activity Home exercises
0 (PAC_13F = DK, RF, NS) Required question was not answered (don't know, refusal,not stated) Home exercises
(PAC_12F × 4 ×
.2167 × 3) / 365
PAC_13F = 1 Calculate EE for < 15 min* Home exercises
(PAC_12F × 4 ×
.3833 × 3) / 365
PAC_13F = 2 Calculate EE for 16 to 30 min* Home exercises
(PAC_12F × 4 ×
.75 × 3) / 365
PAC_13F = 3 Calculate EE for 31 to 60 min* Home exercises
(PAC_12F × 4 × 1
× 3) / 365
PAC_13F = 4 Calculate EE for > 60 min* Home exercises


PACDEEG

Value Condition(s) Description Notes
0 PAC_13G = NA Did not participate in activity Ice hockey
0 (PAC_13G = DK, RF, NS) Required question was not answered (don't know, refusal,not stated) Ice hockey
(PAC_12G × 4 ×
.2167 × 6) / 365
PAC_13G = 1 Calculate EE for < 15 min* Ice hockey
(PAC_12G × 4 ×
.3833 × 6) / 365
PAC_13G = 2 Calculate EE for 16 to 30 min* Ice hockey
(PAC_12G × 4 ×
.75 × 6) / 365
PAC_13G = 3 Calculate EE for 31 to 60 min* Ice hockey
(PAC_12G × 4 × 1
× 6) / 365
PAC_13G = 4 Calculate EE for > 60 min* Ice hockey


PACDEEH

Value Condition(s) Description Notes
0 PAC_13H = NA Did not participate in activity Ice skating
0 (PAC_13H = DK, RF, NS) Required question was not answered (don't know, refusal,not stated) Ice skating
(PAC_12H × 4 ×
.2167 × 4) / 365
PAC_13H = 1 Calculate EE for < 15 min* Ice skating
(PAC_12H × 4 ×
.3833 × 4) / 365
PAC_13H = 2 Calculate EE for 16 to 30 min* Ice skating
(PAC_12H × 4 ×
.75 × 4) / 365
PAC_13H = 3 Calculate EE for 31 to 60 min* Ice skating
(PAC_12H × 4 × 1
× 4) / 365
PAC_13H = 4 Calculate EE for > 60 min* Ice skating


PACDEEI

Value Condition(s) Description Notes
0 PAC_13I = NA Did not participate in activity In-line skating OR ROLLERBLADING
0 (PAC_13I = DK, RF, NS) Required question was not answered (don't know, refusal,not stated) In-line skating OR ROLLERBLADING
(PAC_12I × 4 ×
.2167 × 5) / 365
PAC_13I = 1 Calculate EE for < 15 min* In-line skating OR ROLLERBLADING
(PAC_12I × 4 ×
.3833 × 5) / 365
PAC_13I = 2 Calculate EE for 16 to 30 min* In-line skating OR ROLLERBLADING
(PAC_12I × 4 ×
.75 × 5) / 365
PAC_13I = 3 Calculate EE for 31 to 60 min* In-line skating OR ROLLERBLADING
(PAC_12I × 4 × 1× 5) / 365 PAC_13I = 4 Calculate EE for > 60 min* In-line skating OR ROLLERBLADING


PACDEEJ

Value Condition(s) Description Notes
0 PAC_13J = NA Did not participate in activity Jogging or running
0 (PAC_13J = DK, RF, NS) Required question was not answered (don't know, refusal,not stated) Jogging or running
(PAC_12J × 4 ×
.2167 × 9.5) / 365
PAC_13J = 1 Calculate EE for < 15 min* Jogging or running
(PAC_12J × 4 ×
.3833 × 9.5) / 365
PAC_13J = 2 Calculate EE for 16 to 30 min* Jogging or running
(PAC_12J × 4 ×
.75 × 9.5) / 365
PAC_13J = 3 Calculate EE for 31 to 60 min* Jogging or running
(PAC_12J × 4 × 1
× 9.5) / 365
PAC_13J = 4 Calculate EE for > 60 min* Jogging or running


PACDEEK

Value Condition(s) Description Notes
0 PAC_13K = NA Did not participate in activity Golfing
0 (PAC_13K = DK, RF, NS) Required question was not answered (don't know, refusal,not stated) Golfing
(PAC_12K × 4 ×
.2167 × 4) / 365
PAC_13K = 1 Calculate EE for < 15 min* Golfing
(PAC_12K × 4 ×
.3833 × 4) / 365
PAC_13K = 2 Calculate EE for 16 to 30 min* Golfing
(PAC_12K × 4 ×
.75 × 4) / 365
PAC_13K = 3 Calculate EE for 31 to 60 min* Golfing
(PAC_12K × 4 × 1
× 4) / 365
PAC_13K = 4 Calculate EE for > 60 min* Golfing


PACDEEL

Value Condition(s) Description Notes
0 PAC_13L = NA Did not participate in activity Exercise class or aerobics
0 (PAC_13L = DK, RF, NS) Required question was not answered (don't know, refusal,not stated) Exercise class or aerobics
(PAC_12L × 4 ×
.2167 × 4) / 365
PAC_13L = 1 Calculate EE for < 15 min* Exercise class or aerobics
(PAC_12L × 4 ×
.3833 × 4) / 365
PAC_13L = 2 Calculate EE for 16 to 30 min* Exercise class or aerobics
(PAC_12L × 4 ×
.75 × 4) / 365
PAC_13L = 3 Calculate EE for 31 to 60 min* Exercise class or aerobics
(PAC_12L × 4 × 1× 4) / 365 PAC_13L = 4 Calculate EE for > 60 min* Exercise class or aerobics


PACDEEM

Value Condition(s) Description Notes
0 PAC_13M = NA Did not participate in activity Downhill skiing or snowboarding
0 (PAC_13M = DK, RF, NS) Required question was not answered (don't know, refusal,not stated) Downhill skiing or snowboarding
(PAC_12M × 4 ×
.2167 × 4) / 365
PAC_13M = 1 Calculate EE for < 15 min* Downhill skiing or snowboarding
(PAC_12M × 4 ×
.3833 × 4) / 365
PAC_13M = 2 Calculate EE for 16 to 30 min* Downhill skiing or snowboarding
(PAC_12M × 4 ×
.75 × 4) / 365
PAC_13M = 3 Calculate EE for 31 to 60 min* Downhill skiing or snowboarding
(PAC_12M × 4 × 1× 4) / 365 PAC_13M = 4 Calculate EE for > 60 min* Downhill skiing or snowboarding


PACDEEN

Value Condition(s) Description Notes
0 PAC_13N = NA Did not participate in activity Bowling
0 (PAC_13N = DK, RF, NS) Required question was not answered (don't know, refusal,not stated) Bowling
(PAC_12N × 4 ×
.2167 × 2) / 365
PAC_13N = 1 Calculate EE for < 15 min* Bowling
(PAC_12N × 4 ×
.3833 × 2) / 365
PAC_13N = 2 Calculate EE for 16 to 30 min* Bowling
(PAC_12N × 4 ×
.75 × 2) / 365
PAC_13N = 3 Calculate EE for 31 to 60 min* Bowling
(PAC_12N × 4 × 1
× 2) / 365
PAC_13N = 4 Calculate EE for > 60 min* Bowling


PACDEEO

Value Condition(s) Description Notes
0 PAC_13O = NA Did not participate in activity Baseball or softball
0 (PAC_13O = DK, RF, NS) Required question was not answered (don't know, refusal,not stated) Baseball or softball
(PAC_12O × 4 ×
.2167 × 3) / 365
PAC_13O = 1 Calculate EE for < 15 min* Baseball or softball
(PAC_12O × 4 ×
.3833 × 3) / 365
PAC_13O = 2 Calculate EE for 16 to 30 min* Baseball or softball
(PAC_12O × 4 ×
.75 × 3) / 365
PAC_13O = 3 Calculate EE for 31 to 60 min* Baseball or softball
(PAC_12O × 4 × 1
× 3) / 365
PAC_13O = 4 Calculate EE for > 60 min* Baseball or softball


PACDEEP

Value Condition(s) Description Notes
0 PAC_13P = NA Did not participate in activity Tennis
0 (PAC_13P = DK, RF, NS) Required question was not answered (don't know, refusal,not stated) Tennis
(PAC_12P × 4 ×
.2167 × 4) / 365
PAC_13P = 1 Calculate EE for < 15 min* Tennis
(PAC_12P × 4 ×
.3833 × 4) / 365
PAC_13P = 2 Calculate EE for 16 to 30 min* Tennis
(PAC_12P × 4 ×
.75 × 4) / 365
PAC_13P = 3 Calculate EE for 31 to 60 min* Tennis
(PAC_12P × 4 × 1
× 4) / 365
PAC_13P = 4 Calculate EE for > 60 min* Tennis


PACDEEQ

Value Condition(s) Description Notes
0 PAC_13Q = NA Did not participate in activity Weight-training
0 (PAC_13Q = DK, RF, NS) Required question was not answered (don't know, refusal,not stated) Weight-training
(PAC_12Q × 4 ×
.2167 × 3) / 365
PAC_13Q = 1 Calculate EE for < 15 min* Weight-training
(PAC_12Q × 4 ×
.3833 × 3) / 365
PAC_13Q = 2 Calculate EE for 16 to 30 min* Weight-training
(PAC_12Q × 4 ×
.75 × 3) / 365
PAC_13Q = 3 Calculate EE for 31 to 60 min* Weight-training
(PAC_12Q × 4 × 1
× 3) / 365
PAC_13Q = 4 Calculate EE for > 60 min* Weight-training


PACDEER

Value Condition(s) Description Notes
0 PAC_13R = NA Did not participate in activity Fishing
0 (PAC_13R = DK, RF, NS) Required question was not answered (don't know, refusal,not stated) Fishing
(PAC_12R × 4 ×
.2167 × 3) / 365
PAC_13R = 1 Calculate EE for < 15 min* Fishing
(PAC_12R × 4 ×
.3833 × 3) / 365
PAC_13R = 2 Calculate EE for 16 to 30 min* Fishing
(PAC_12R × 4 ×
.75 × 3) / 365
PAC_13R = 3 Calculate EE for 31 to 60 min* Fishing
(PAC_12R × 4 × 1
× 3) / 365
PAC_13R = 4 Calculate EE for > 60 min* Fishing


PACDEES

Value Condition(s) Description Notes
0 PAC_13S = NA Did not participate in activity Volleyball
0 (PAC_13S = DK, RF, NS) Required question was not answered (don't know, refusal,not stated) Volleyball
(PAC_12S × 4 ×
.2167 × 5) / 365
PAC_13S = 1 Calculate EE for < 15 min* Volleyball
(PAC_12S × 4 ×
.3833 × 5) / 365
PAC_13S = 2 Calculate EE for 16 to 30 min* Volleyball
(PAC_12S × 4 ×
.75 × 5) / 365
PAC_13S = 3 Calculate EE for 31 to 60 min* Volleyball
(PAC_12S × 4 × 1
× 5) / 365
PAC_13S = 4 Calculate EE for > 60 min* Volleyball


PACDEET

Value Condition(s) Description Notes
0 PAC_13T = NA Did not participate in activity Basketball
0 (PAC_13T = DK, RF, NS) Required question was not answered (don't know, refusal,not stated) Basketball
(PAC_12T × 4 ×
.2167 × 6) / 365
PAC_13T = 1 Calculate EE for < 15 min* Basketball
(PAC_12T × 4 ×
.3833 × 6) / 365
PAC_13T = 2 Calculate EE for 16 to 30 min* Basketball
(PAC_12T × 4 ×
.75 × 6) / 365
PAC_13T = 3 Calculate EE for 31 to 60 min* Basketball
(PAC_12T × 4 × 1
× 6) / 365
PAC_13T = 4 Calculate EE for > 60 min* Basketball


PACDEEU

Value Condition(s) Description Notes
0 PAC_13U = NA Did not participate in activity Soccer (U)
0 (PAC_13U = DK, RF, NS) Required question was not answered (don't know, refusal,not stated) Soccer (U)
(PAC_12U × 4 ×
.2167 × 5) / 365
PAC_13U = 1 Calculate EE for < 15 min* Soccer (U)
(PAC_12U × 4 ×
.3833 × 5) / 365
PAC_13U = 2 Calculate EE for 16 to 30 min* Soccer (U)
(PAC_12U × 4 ×
.75 × 5) / 365
PAC_13U = 3 Calculate EE for 31 to 60 min* Soccer (U)
(PAC_12U × 4 × 1
× 5) / 365
PAC_13U = 4 Calculate EE for > 60 min* Soccer (U)


PACDEEV

Value Condition(s) Description Notes
0 PAC_13V = NA Did not participate in activity Other (V)
0 (PAC_13V = DK, RF, NS) Required question was not answered (don't know, refusal,not stated) Other (V)
(PAC_12V × 4 ×
.2167 × 4) / 365
PAC_13V = 1 Calculate EE for < 15 min* Other (V)
(PAC_12V × 4 ×
.3833 × 4) / 365
PAC_13V = 2 Calculate EE for 16 to 30 min* Other (V)
(PAC_12V × 4 ×
.75 × 4) / 365
PAC_13V = 3 Calculate EE for 31 to 60 min* Other (V)
(PAC_12V × 4 × 1
× 4) / 365
PAC_13V = 4 Calculate EE for > 60 min* Other (V)


PACDEEX

Value Condition(s) Description Notes
0 PAC_13X = NA Did not participate in activity Other (X)
0 (PAC_13X = DK, RF, NS) Required question was not answered (don't know, refusal,not stated) Other (X)
(PAC_12X × 4 ×
.2167 × 4) / 365
PAC_13X = 1 Calculate EE for < 15 min* Other (X)
(PAC_12X × 4 ×
.3833 × 4) / 365
PAC_13X = 2 Calculate EE for 16 to 30 min* Other (X)
(PAC_12X × 4 ×
.75 × 4) / 365
PAC_13X = 3 Calculate EE for 31 to 60 min* Other (X)
(PAC_12X × 4 × 1
× 4) / 365
PAC_13X = 4 Calculate EE for > 60 min* Other (X)


PACDEEY

Value Condition(s) Description Notes
0 PAC_13Y = NA Did not participate in activity Other (Y)
0 (PAC_13Y = DK, RF, NS) Required question was not answered (don't know, refusal,not stated) Other (Y)
(PAC_12Y × 4 ×
.2167 × 4) / 365
PAC_13Y = 1 Calculate EE for < 15 min* Other (Y)
(PAC_12Y × 4 ×
.3833 × 4) / 365
PAC_13Y = 2 Calculate EE for 16 to 30 min* Other (Y)
(PAC_12Y × 4 ×
.75 × 4) / 365
PAC_13Y = 3 Calculate EE for 31 to 60 min* Other (Y)
(PAC_12Y × 4 × 1
× 4) / 365
PAC_13Y = 4 Calculate EE for > 60 min* Other (Y)
Table 1
PACDEE Specifications
Value Condition(s) Description Notes
99.6 DHH_AGE < 12 or
PAC_11W = NA
Population exclusions NA
99.9 (PAC_11W = DK, RF, NS) Required question was
not answered (don't know, refusal, not stated)
NS
0 PAC_11W = 1 No physical activity  
PACDEEA +
PACDEEB +
PACDEEC +
PACDEED +
PACDEEE +
PACDEEF +
PACDEEG +
PACDEEH +
PACDEEI +
PACDEEJ +
PACDEEK +
PACDEEL +
PACDEEM +
PACDEEN +
PACDEEO +
PACDEEP +
PACDEEQ +
PACDEER +
PACDEES +
PACDEET +
PACDEEU +
PACDEEV +
PACDEEX +
PACDEEY
(0 <= PACDEEA < NA) and
(0 <= PACDEEB < NA) and
(0 <= PACDEEC < NA) and
(0 <= PACDEED < NA) and
(0 <= PACDEEE < NA) and
(0 <= PACDEEF < NA) and
(0 <= PACDEEG < NA) and
(0 <= PACDEEH < NA) and
(0 <= PACDEEI < NA) and
(0 <= PACDEEJ < NA) and
(0 <= PACDEEK < NA) and
(0 <= PACDEEL < NA) and
(0 <= PACDEEM < NA) and
(0 <= PACDEEN < NA) and
(0 <= PACDEEO < NA) and
(0 <= PACDEEP < NA) and
(0 <= PACDEEQ < NA) and
(0 <= PACDEER < NA) and
(0 <= PACDEES < NA) and
(0 <= PACDEET < NA) and
(0 <= PACDEEU < NA) and
(0 <= PACDEEV < NA) and
(0 <= PACDEEX < NA) and
(0 <= PACDEEY < NA)
Total daily energy expenditure (kcal/kg/day) Rounded to one decimal place (min: 0.0; max: 99.5)

2. PACDFM - Average Monthly Frequencyof Physical Activity Lasting Over 15 Minutes

Variable name:
PACDFM

Based on:
PAC_11W, PAC_12A, PAC_12B, PAC_12C, PAC_12D, PAC_12E, PAC_12F,PAC_12G, PAC_12H, PAC_12I, PAC_12J, PAC_12K, PAC_12L, PAC_12M,PAC_12N, PAC_12O, PAC_12P, PAC_12Q, PAC_12R, PAC_12S,PAC_12T,PAC_12U, PAC_12V, PAC_12X, PAC_12Y, PAC_13A, PAC_13B, PAC_13C,PAC_13D, PAC_13E, PAC_13F, PAC_13G, PAC_13H, PAC_13I, PAC_13J,PAC_13K, PAC_13L, PAC_13M, PAC_13N, PAC_13O, PAC_13P, PAC_13Q,PAC_13R, PAC_13S, PAC_13T, PAC_31U, PAC_13V, PAC_13X, PAC_13Y,DHH_AGE

Description:
This variable measures the total number of times per month thatrespondents took part in a physical activity(ies) lasting more than15 minutes.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents less than 12 years of age were excluded from thepopulation.
The survey questions refer to "the past three months". Thisvariable calculates a one-month average by dividing the totalreported frequency by three.

Source:
Ontario Health Survey

Internet site:
www.chass.utoronto.ca/datalib/codebooks/utm/ohs/ohs90.htm

Table 2
PACDFM Temporary Reformat

PACT2A

Value Condition(s) Description Notes
0 (PAC_13A = 1, NA, DK, RF, NS) Set all values for PAC_12A (number of times/3months respondentsdid physical activity) to 0 if PAC_13A is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)  
PAC_12A Else Set PACT2A = PAC_12A  

PACT2B

Value Condition(s) Description Notes
0

(PAC_13B = 1, NA, DK, RF, NS)

Set all values for PAC_12B (number of times/3months respondentsdid physical activity) to 0 if PAC_13B is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 
PAC_12B Else Set PACT2B = PAC_12B  

PACT2C

Value Condition(s) Description Notes
0

(PAC_13C = 1, NA, DK, RF, NS)

Set all values for PAC_12C (number of times/3months respondentsdid physical activity) to 0 if PAC_13C is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 
PAC_12C Else Set PACT2C = PAC_12C  

PACT2D

Value Condition(s) Description Notes
0

(PAC_13D = 1, NA, DK, RF, NS)

Set all values for PAC_12D (number of times/3months respondentsdid physical activity) to 0 if PAC_13D is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 
PAC_12D Else Set PACT2D = PAC_12D  

PACT2E

Value Condition(s) Description Notes
0

(PAC_13E = 1, NA, DK, RF, NS)

Set all values for PAC_12E (number of times/3months respondentsdid physical activity) to 0 if PAC_13E is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 
PAC_13E Else Set PACT2E = PAC_12E  

PACT2F

Value Condition(s) Description Notes
0

(PAC_13F = 1, NA, DK, RF, NS)

Set all values for PAC_12F (number of times/3months respondentsdid physical activity) to 0 if PAC_13F is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 
PAC_12F Else Set PACT2F = PAC_12F  

PACT2G

Value Condition(s) Description Notes
0

(PAC_13G = 1, NA, DK, RF, NS)

Set all values for PAC_12G (number of times/3months respondentsdid physical activity) to 0 if PAC_13G is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 
PAC_12G Else Set PACT2G = PAC_12G  

PACT2H

Value Condition(s) Description Notes
0

(PAC_13H = 1, NA, DK, RF, NS)

Set all values for PAC_12H (number of times/3months respondentsdid physical activity) to 0 if PAC_13H is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 
PAC_12H Else Set PACT2H = PAC_12H  

PACT2I

Value Condition(s) Description Notes
0

(PAC_13I = 1, NA, DK, RF, NS)

Set all values for PAC_12I (number of times/3months respondentsdid physical activity) to 0 if PAC_13I is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 
PAC_12I Else Set PACT2I = PAC_12I  

PACT2J

Value Condition(s) Description Notes
0

(PAC_13J = 1, NA, DK, RF, NS)

Set all values for PAC_12J (number of times/3months respondentsdid physical activity) to 0 if PAC_13J is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 
PAC_12J Else Set PACT2J = PAC_12J  

PACT2K

Value Condition(s) Description Notes
0

(PAC_13K = 1, NA, DK, RF, NS)

Set all values for PAC_12K (number of times/3months respondentsdid physical activity) to 0 if PAC_13K is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 
PAC_12K Else Set PACT2K = PAC_12K  

PACT2L

Value Condition(s) Description Notes
0

(PAC_13L = 1, NA, DK, RF, NS)

Set all values for PAC_12L (number of times/3months respondentsdid physical activity) to 0 if PAC_13L is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 
PAC_12L Else Set PACT2L = PAC_12L  

PACT2M

Value Condition(s) Description Notes
0

(PAC_13M = 1, NA, DK, RF, NS)

Set all values for PAC_12M (number of times/3months respondentsdid physical activity) to 0 if PAC_13M is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 
PAC_12M Else Set PACT2M = PAC_12M  

PACT2N

Value Condition(s) Description Notes
0

(PAC_13N = 1, NA, DK, RF, NS)

Set all values for PAC_12N (number of times/3months respondentsdid physical activity) to 0 if PAC_13N is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 
PAC_12N Else Set PACT2N = PAC_12N  

PACT2O

Value Condition(s) Description Notes
0

(PAC_13O = 1, NA, DK, RF, NS)

Set all values for PAC_12O (number of times/3months respondentsdid physical activity) to 0 if PAC_13O is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 
PAC_12O Else Set PACT2O = PAC_12O  

PACT2P

Value Condition(s) Description Notes
0

(PAC_13P = 1, NA, DK, RF, NS)

Set all values for PAC_12P (number of times/3months respondentsdid physical activity) to 0 if PAC_13P is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 
PAC_12P Else Set PACT2P = PAC_12P  

PACT2Q

Value Condition(s) Description Notes
0

(PAC_13Q = 1, NA, DK, RF, NS)

Set all values for PAC_12Q (number of times/3months respondentsdid physical activity) to 0 if PAC_13Q is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 
PAC_12Q Else Set PACT2Q = PAC_12Q  

PACT2R

Value Condition(s) Description Notes
0

(PAC_13R = 1, NA, DK, RF, NS)

Set all values for PAC_12R (number of times/3months respondentsdid physical activity) to 0 if PAC_13R is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 
PAC_12R Else Set PACT2R = PAC_12R  

PACT2S

Value Condition(s) Description Notes
0

(PAC_13S = 1, NA, DK, RF, NS)

Set all values for PAC_12S (number of times/3months respondentsdid physical activity) to 0 if PAC_13S is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 
PAC_12S Else Set PACT2S = PAC_12S  

PACT2T

Value Condition(s) Description Notes
0

(PAC_13T = 1, NA, DK, RF, NS)

Set all values for PAC_12T (number of times/3months respondentsdid physical activity) to 0 if PAC_13T is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 
PAC_12T Else Set PACT2T = PAC_12T  

PACT2U

Value Condition(s) Description Notes
0

(PAC_13U = 1, NA, DK, RF, NS)

Set all values for PAC_12U (number of times/3months respondentsdid physical activity) to 0 if PAC_13U is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 
PAC_12U Else Set PACT2U = PAC_12U  

PACT2V

Value Condition(s) Description Notes
0

(PAC_13V = 1, NA, DK, RF, NS)

Set all values for PAC_12V (number of times/3months respondentsdid physical activity) to 0 if PAC_13V is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 
PAC_12V Else Set PACT2V = PAC_12V  

PACT2X

Value Condition(s) Description Notes
0

(PAC_13X = 1, NA, DK, RF, NS)

Set all values for PAC_12X (number of times/3months respondentsdid physical activity) to 0 if PAC_13X is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 
PAC_12X Else Set PACT2X = PAC_12X  

PACT2Y

Value Condition(s) Description Notes
0

(PAC_13Y = 1, NA, DK, RF, NS)

Set all values for PAC_12Y (number of times/3months respondentsdid physical activity) to 0 if PAC_13Y is 1 (1 to 15 minutes), NA(did not participate in activity), or DK, RF, NS (did not answerquestion)

 
PAC_12Y Else Set PACT2Y = PAC_12Y  
Table 2
PACDFM Specifications
Value Condition(s) Description Notes
996 DHH_AGE < 12 or
PAC_11W = NA
Population exclusions NA
999 (PAC_11W = DK, RF, NS) Required question was not answered (don't know, refusal,not stated) NS
0 PAC_11W=1 No physical activity  
(PACT2A +
PACT2B +
PACT2C +
PACT2D +
PACT2E +
PACT2F +
PACT2G +
PACT2H +
PACT2I +
PACT2J +
PACT2K +
PACT2L +
PACT2M +
PACT2N +
PACT2O +
PACT2P +
PACT2Q +
PACT2R +
PACT2S +
PACT2T +
PACT2U +
PACT2V +
PACT2X +
PACT2Y) / 3
(0 <= PACT2A < NA) and
(0 <= PACT2B < NA) and
(0 <= PACT2C < NA) and
(0 <= PACT2D < NA) and
(0 <= PACT2E < NA) and
(0 <= PACT2F < NA) and
(0 <= PACT2G < NA) and
(0 <= PACT2H < NA) and
(0 <= PACT2I < NA) and
(0 <= PACT2J < NA) and
(0 <= PACT2K < NA) and
(0 <= PACT2L < NA) and
(0 <= PACT2M < NA) and
(0 <= PACT2N < NA) and
(0 <= PACT2O < NA) and
(0 <= PACT2P < NA) and
(0 <= PACT2Q < NA) and
(0 <= PACT2R <NA) and
(0 <= PACT2S < NA) and
(0 <= PACT2T < NA) and
(0 <= PACT2U < NA) and
(0 <= PACT2V < NA) and
(0 <= PACT2X < NA) and
(0 <= PACT2Y < NA)
Monthly frequency of all physical activity lasting over 15minutes Rounded to nearest integer (min: 0; max: 995)

3. PACDFR - Frequency of All PhysicalActivity Lasting Over 15 Minutes

Variable name:
PACDFR

Based on:
DHH_AGE, PACDFM

Description:
This variable classifies respondents according to their pattern, orregularity of physical activity lasting more than 15 minutes.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents less than 12 years of age were excluded from thepopulation.
This variable uses values for the derived variable MonthlyFrequency of Physical Activity (PACDFM). The values for PACDFMreflect a one-month average based on data reported for athree-month period.

Table 3
PACDFR Specifications
Value Condition(s) Description Notes
6 DHH_AGE < 12 or
PACDFM = NA
Population exclusion NA
9 PACDFM = NS Required question was not answered (don't know, refusal,not stated) NS
1 (12 <= PACDFM < NA) Regular practice of activities  
2 (4 <= PACDFM < 12) Occasional practice of activities  
3 PACDFM < 4 Infrequent practice of activities  

4. PACDPAI - Physical ActivityIndex

Variable name:
PACDPAI

Based on:
DHH_AGE, PACDEE

Description:
This variable categorizes respondents as being "active","moderate", or "inactive" based on the total daily EnergyExpenditure values (kcal/kg/day) calculated for PACDEE.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents less than 12 years of age were excluded from thepopulation.
The Physical Activity Index follows the same criteria used tocategorize individuals in the Ontario Health Survey (OHS) and inthe Campbell's Survey on Well Being.

Internet site:
Campbell Survey on Well-Being in Canada: www.cflri.ca/cflri/pa/surveys/88survey.html

Table 4
PACDPAI Specifications
Value Condition(s) Description Notes
6 DHH_AGE < 12 or
PACDEE = NA
Population exclusions NA
9 PACDEE = NS Required question was not answered (don't know, refusal,not stated) NS
1 (3 <= PACDEE < NA) Active  
2 (1.5 <= PACDEE < 3.0) Moderate  
3 (0 <= PACDEE < 1.5) Inactive  

5. PACFD - Participant In DailyPhysical Activity Lasting Over 15 Minutes

Variable name:
PACFD

Based on:
DHH_AGE, PACDFM

Description:
This variable indicates whether the respondent participated dailyin physical activity lasting over 15 minutes.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents less than 12 years of age were excluded from thepopulation.
This variable is based on values for Monthly Frequency of PhysicalActivity (PACDFM). Values for PACDFM reflect a one-monthaverage based on data reported for a three-month period.

Table 5
PACFD Specifications
Value Condition(s) Description Notes
6 DHH_AGE < 12 or
PACDFM = NA
Population exclusions NA
9 PACDFM = NS Required question was not answered (don't know, refusal,not stated) NS
1 (30 <= PACDFM < NA) Participates in daily physical activity  
2 PACDFM < 30 Does not participate in daily physical activity  

6. PACFLEI - Participant In LeisurePhysical Activity

Variable name:
PACFLEI

Based on:
DHH_AGE, PAC_11W

Description:
This variable indicates whether the respondent participated in anyleisure physical activities in the three months prior to theinterview.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents less than 12 years of agewere excluded from the population.

Source:
Ontario Health Survey

Internet site:
www.chass.utoronto.ca/datalib/codebooks/utm/ohs/ohs90.htm

Table 6
PACFLEI Specifications
Value Condition(s) Description Notes
6 DHH_AGE < 12 or
PAC_11W = NA
Population exclusions NA
9 (PAC_11W = DK, RF, NS) Required question was not answered (don't know, refusal,not stated) NS
1 PAC_11W = 2 Participates in leisure physical activity  
2 PAC_11W = 1 Does not participate in leisure physical activity  

Partial Curl-Ups (2 DVs)

1. PCCDELG - Eligibility - PartialCurl-up component

Variable name:
PCCDELG

Based on:
CLC_AGE, V2_TYPE, ATG_13, ATG_33B, PHC_11, PHC_12, PHC_36, PHC_37,PHC_42G, MHR_611B, PAR_11, PAR_21, PAR_31,PAR_5A3A, PAR_5B3A, PAR_5B3A, PAR_5D3A, PAR_5E3A, PAR_5F3A,PAR_5G3A, PAR_5H3A, PAR_5I3A, PAR_5J3A, PAR_5K3A, PAR_62E, PAR_72D,ORS_3, BPMDBPS, BPMDBPD, BPMDHR

Description:
This variable indicates whether the respondent was eligible for thePartial Curl-up component. As there are multiple reasons to bescreened out of this measure, the prevalence of screen outs byreason should not be based on frequency counts for thisvariable.

Note:
Created in the Clinic Post-Verify process.

Table 1
PCCDELG Specifications
Value Condition(s) Description Notes
2 V2_TYPE = 2 Not eligible - home visit  
3 CLC_AGE > 69 Not eligible - age  
5 ATG_33D = 1 Not eligible - drank alcohol too close to visit time  
6 PHC_11 = 1 and
(12 < PHC_12 < NA)
Not eligible - more than 12 weeks pregnant  
9 PHC_42J = 1 Not eligible - acute or chronic condition  
12 MHR_611E = 1 Not eligible - medication use  
13 PAR_N11 = 1 or
PAR_21 = 1 or
PAR_31 = 1 or
PAR_5A3A = 1 or
PAR_5B3A = 1 or
PAR_5C3A = 1 or
PAR_5D3A = 1 or
PAR_5E3A = 1 or
PAR_5F3A = 1 or
PAR_5G3A = 1 or
PAR_5H3A = 1 or
PAR_5I3A = 1 or
PAR_5J3A = 1 or
PAR_5K3A = 1 or
PAR_62E = 1 or
PAR_72D = 1
Not eligible - PAR-Q answer  
14 ORS_5 = 1 Not eligible - other reason  
15 (CLC_AGE > 14 and
(144 < BPMDBPS < NA)) or
(CLC_AGE > 14 and
(144 < BPMDBPD < NA))
Not eligible - high blood pressure  
16 CLC_AGE > 14 and
(99 < BPMDHR < NA)
Not eligible - high heart rate  
1 Else Eligible  

2. PCMD11 - Partial curl-up norms forrespondents 15 - 69

Variable name:
PCMD11

Based on:
CLC_AGE, CLC_SEX, PCM_01

De2. scription:
This variable indicates the partial curl-up norms for respondents15 - 69.

Note:
Created in the Clinic data collection application. 
This variable applies to respondents aged 15-69 years old. Thecategories are:
Needs improvement
Fair
Good
Very good
Excellent

Source:
The Canadian Physical Activity, Fitness and Lifestyle Approach (3rdEdition, 2004) by the Canadian Society for Exercise Physiology(CSEP)

Table 2
PCMD11 Specifications
Value Condition(s) Description Notes
6 CLC_AGE < 15 or
CLC_AGE > 69 or
PCM_01 = NA
Population exclusions NA
9 PCM_01 > NA At least one required question was not answered (don'tknow, refusal, not stated) NS
0 (CLC_SEX = 1 and
((CLC_AGE < 20 and
PCM_01 < 16) or
((19 < CLC_AGE < 30) and
PCM_01 < 11) or
((29 < CLC_AGE < 40) and
PCM_01 < 11) or
((39 < CLC_AGE < 50) and
PCM_01 < 6) or
((49 < CLC_AGE < 60) and
PCM_01 < 8) or
(CLC_AGE > 59 and
PCM_01 < 6)) or
(CLC_SEX = 2 and
((CLC_AGE < 20 and
PCM_01 < 12) or
((19 < CLC_AGE < 30) and
PCM_01 < 5) or
((29 < CLC_AGE < 40) and
PCM_01 < 6) or
((39 < CLC_AGE < 50) and
PCM_01 < 4) or
((49 < CLC_AGE < 60) and
PCM_01 < 6) or
(CLC_AGE > 59 and
PCM_01 < 3))
Needs improvement  
1 (CLC_SEX = 1 and
(((19 < CLC_AGE < 30) and
(10 < PCM_01 < 16)) or
((29 < CLC_AGE < 40) and
(10 < PCM_01 < 15)) or
((39 < CLC_AGE < 50) and
(5 < PCM_01 < 13)) or
((49 < CLC_AGE < 60) and
(7 < PCM_01 < 11)) or
(CLC_AGE > 59 and
(5 < PCM_01 < 11))) or
(CLC_SEX = 2 and
((CLC_AGE < 20 and
(11 < PCM_01 < 17)) or
((19 < CLC_AGE < 30) and
(4 < PCM_01 < 14)) or
((29 < CLC_AGE < 40) and
(5 < PCM_01 < 10)) or
((39 < CLC_AGE < 50) and
(3 < PCM_01 < 11)) or
((49 < CLC_AGE < 60) and
(5 < PCM_01 < 10)) or
(CLC_AGE > 59 and
(2 < PCM_01 < 8)))
Fair  
2 (CLC_SEX = 1 and
((CLC_AGE < 20 and
(20 < PCM_01 < 23)) or
((19 < CLC_AGE < 30) and
(15 < PCM_01 < 21)) or
((29 < CLC_AGE < 40) and
(14 < PCM_01 < 18)) or
((39 < CLC_AGE < 50) and
(12 < PCM_01 < 18)) or
((49 < CLC_AGE < 60) and
(10 < PCM_01 < 17)) or
(CLC_AGE > 59 and
(10 < PCM_01 < 16))) or
(CLC_SEX = 2 and
((CLC_AGE < 20 and
(16 < PCM_01 < 22)) or
((19 < CLC_AGE < 30) and
(13 < PCM_01 < 18)) or
((29 < CLC_AGE < 40) and
(9 < PCM_01 < 19)) or
((39 < CLC_AGE < 50) and
(10 < PCM_01 < 19)) or
((49 < CLC_AGE < 60) and
(9 < PCM_01 < 19)) or
(CLC_AGE > 59 and
(7 < PCM_01 < 17)))
Good  
3 (CLC_SEX = 1 and
((CLC_AGE < 20 and
(22 < PCM_01 < 25)) or
((19 < CLC_AGE < 30) and
(20 < PCM_01 < 25)) or
((29 < CLC_AGE < 40) and
(17 < PCM_01 < 25)) or
((39 < CLC_AGE < 50) and
(17 < PCM_01 < 25)) or
((49 < CLC_AGE < 60) and
(16 < PCM_01 < 25)) or
(CLC_AGE > 59 and
(15 < PCM_01 < 25))) or
(CLC_SEX = 2 and
((CLC_AGE < 20 and
(21 < PCM_01 < 25)) or
((19 < CLC_AGE < 30) and
(17 < PCM_01 < 25)) or
((29 < CLC_AGE < 40) and
(18 < PCM_01 < 25)) or
((39 < CLC_AGE < 50) and
(18 < PCM_01 < 25)) or
((49 < CLC_AGE < 60) and
(18 < PCM_01 < 25)) or
(CLC_AGE > 59 and
(16 < PCM_01 < 25)))
Very good  
4 Else Excellent  

Phlebotomy (2 DVs)

1. BDCD13 - Blood donationstatus

Variable name:
BDCD13

Based on:
BDC_12, BDC_13D, BDC_13M, BDC_13Y, V2_DAY, V2_MONTH, V2_YEAR

Description:
This variable indicates whether the respondent gave blood the daybefore the clinic visit.

Note:
Created in the Clinic data collection application.

Table 1
BDCD13 Temporary Reformat

V2_YDAY

Value Condition(s) Description Notes
V2_DAY - 1

All records

   


V2_YMTH

Value Condition(s) Description Notes
V2_MTH - 1

V2_DAY = 1

   

V2_MTH

Else

   


V2_YYEAR

Value Condition(s) Description Notes
V2_YEAR - 1

V2_DAY = 1 and
V2_MTH = 1

   

V2_YEAR

Else

   
Table 1
BDCD13 Specifications
Value Condition(s) Description Notes
9 (BDC_12 = DK, RF, NS) At least one required question was not answered (don'tknow, refusal, not stated) NS
6 (1 < PHBDELG < NA) Population exclusions NA
1 BDC_13Y = V2_YYEAR and
BDC_13M = V2_YMTH and
BDC_13D = V2_YDAY
Donated blood the day before the clinic visit  
2 Else Did not donate blood the day before the clinic  

2. PHBDELG - Eligibility - Phlebotomycomponent

Variable name:
PHBDELG

Based on:
PHC_42A, PHC_51, PHC_52

Description:
This variable indicates whether the respondent was eligible for thePhlebotomy component. As there are multiple reasons to be screenedout of this measure, the prevalence of screen outs by reason shouldnot be based on frequency counts for this variable.

Note:
Created in the Clinic Post-Verify process.

Table 2
PHBDELG Specifications
Value Condition(s) Description Notes
9 PHC_42A = 1 Not eligible - acute or chronic condition  
10 PHC_51 = 1 Not eligible - hemophilia  
11 PHC_52 = 1 Not eligible - received chemoptherapy in past four weeks  
1 Else Eligible  

Report of Measurements (2DVs)

1. RMCDBCK - Back fitness norms forrespondents 15 – 69

Variable name:
RMCDBCK

Based on:
CLC_AGE, CLC_SEX, HWMDWSTA, SRMD12, PCMD11

Description:
This variable indicates the back fitness norms for respondents aged 15 to 69, based on the norms for Partial Curl-Ups, Waist Circumference and Sit and Reach.

Note:
Created in the Clinic Post-Verify process.
This variable applies to respondents aged 15-69 years old. Thecategories are:
Considerable health risk
Some health risk
Many health benefits
Considerable health benefits
Optimal health benefits

Table 1
RMCDBCK Temporary Reformat

PTS3

Value Condition(s) Description Notes
Round(((HWMDWSTA + SRMD12 + PCMD11) / 3), .1) CLC_SEX = 1 and
HWMDWSTA in (0,1,2,3,4) and
SRMD12 in (0,1,2,3,4) and
PCMD11 in (0,1,2,3,4)
Calculation for male back fitness given all three norms, i.e.,Waist Circumference, Sit and Reach, and Partial Curl-Up. Rounded to one decimal place
0 CLC_SEX = 1 and
HWMDWSTA in (0,1,2,3,4) and
SRMD12 in (0,1,2,3,4) and
(PCMD11 = DK, RF, NS) and
(HWMDWSTA + SRMD12 = 1)
Value for male back fitness given Waist Circumference and Sitand Reach norms only (no Partial Curl-Up norms), where the sum ofthe available norms is 1  
1 CLC_SEX = 1 and
HWMDWSTA in (0,1,2,3,4) and
SRMD12 in (0,1,2,3,4) and
(PCMD11 = DK, RF, NS) and
(HWMDWSTA + SRMD12 = 3)
Value for male back fitness given Waist Circumference and Sitand Reach norms only (no Partial Curl-Up norms), where the sum ofthe available norms is 3.  
Round(((HWMDWSTA + SRMD12) / 2), .1) CLC_SEX = 1 and
HWMDWSTA in (0,1,2,3,4) and
SRMD12 in (0,1,2,3,4) and
(PCMD11 = DK, RF, NS) and
((HWMDWSTA + SRMD12) not in (1, 3))
Calculation for male back fitness given Waist Circumference andSit and Reach norms only (no Partial Curl-Up norms), where the sumof the available norms is not 1 or 3. Rounded to one decimal place
0 CLC_SEX = 1 and
HWMDWSTA in (0,1,2,3,4) and
(SRMD12 = DK, RF, NS) and
PCMD11 in (0,1,2,3,4) and
(HWMDWSTA + PCMD11 = 1)
Value for male back fitness given Waist Circumference andPartial Curl-Up norms only (no Sit and Reach norms), where the sumof the available norms is 1  
1 CLC_SEX = 1 and
HWMDWSTA in (0,1,2,3,4) and
(SRMD12 = DK, RF, NS) and
PCMD11 in (0,1,2,3,4) and
(HWMDWSTA + PCMD11 = 3)
Value for male back fitness given Waist Circumference andPartial Curl-Up norms only (no Sit and Reach norms), where the sumof the available norms is 3.  
Round(((HWMDWSTA + PCMD11) / 2), .1) CLC_SEX = 1 and
HWMDWSTA in (0,1,2,3,4) and
(SRMD12 = DK, RF, NS) and
PCMD11 in (0,1,2,3,4) and
((HWMDWSTA + PCMD11) not in (1, 3))
Calculation for male back fitness given Waist Circumference andPartial Curl-Up norms only (no Sit and Reach norms), where the sumof the available norms is not 1 or 3 Rounded to one decimal place
0 CLC_SEX = 2 and
HWMDWSTA in (0,1,2,3,4) and
SRMD12 in (0,1,2,3,4) and
PCMD11 in (0,1,2,3,4) and
(HWMDWSTA * 2 + SRMD12 + PCMD11 = 2)
Value for female back fitness given all three norms (i.e.,Waist Circumference, Sit and Reach, and Partial Curl-Up), whereHWMDWSTA * 2 + SRMD12 + PCMD11 = 2  
1 CLC_SEX = 2 and
HWMDWSTA in (0,1,2,3,4) and
SRMD12 in (0,1,2,3,4) and
PCMD11 in (0,1,2,3,4) and
(HWMDWSTA * 2 + SRMD12 + PCMD11 = 6)
Value for female back fitness given all three norms (i.e.,Waist Circumference, Sit and Reach, and Partial Curl-Up), whereHWMDWSTA * 2 + SRMD12 + PCMD11 = 6  
Round(((HWMDWSTA * 2 + SRMD12 + PCMD11) / 4), .1) CLC_SEX = 2 and
HWMDWSTA in (0,1,2,3,4) and
SRMD12 in (0,1,2,3,4) and
PCMD11 in (0,1,2,3,4) and
((HWMDWSTA * 2 + SRMD12 + PCMD11) not in (2, 6))
Calculation for female back fitness given all three norms(i.e., Waist Circumference, Sit and Reach, and Partial Curl-Up),where (HWMDWSTA * 2 + SRMD12 + PCMD11) not in (2, 6) Rounded to one decimal place
Round(((HWMDWSTA * 2 + SRMD12) / 3), .1) CLC_SEX = 2 and
HWMDWSTA in (0,1,2,3,4) and
SRMD12 in (0,1,2,3,4) and
(PCMD11 = DK, RF, NS)
Calculation for female back fitness given Waist Circumferenceand Sit and Reach norms only (no Partial Curl-Up norms) Rounded to one decimal place
Round(((HWMDWSTA * 2 + PCMD11) / 3), .1) CLC_SEX = 2 and
HWMDWSTA in (0,1,2,3,4) and
(SRMD12 = DK, RF, NS) and
PCMD11 in (0,1,2,3,4)
Calculation for female back fitness given Waist Circumferenceand Partial Curl-Up norms only (no Sit and Reach norms) Rounded to one decimal place
0 (HWMDWSTA = DK, RF, NS) and
SRMD12 in (0,1,2,3,4) and
PCMD11 in (0,1,2,3,4) and
(SRMD12 + PCMD11 = 1)
Value for back fitness given Sit and Reach and Partial Curl-Upnorms only (no Waist Circumference norms), where the sum of theavailable norms is 1  
1 (HWMDWSTA = DK, RF, NS) and
SRMD12 in (0,1,2,3,4) and
PCMD11 in (0,1,2,3,4) and
(SRMD12 + PCMD11 = 3)
Value for back fitness given Sit and Reach and Partial Curl-Upnorms only (no Waist Circumference norms), where the sum of theavailable norms is 3  
Round(((SRMD12 + PCMD11) / 2), .1) (HWMDWSTA = DK, RF, NS) and
SRMD12 in (0,1,2,3,4) and
PCMD11 in (0,1,2,3,4) and
((SRMD12 + PCMD11) not in (1, 3))
Calculation for back fitness given Sit and Reach and PartialCurl-Up norms only (no Waist Circumference norms), where the sum ofthe available norms is not 1 or 3 Rounded to one decimal place
HWMDWSTA HWMDWSTA in (0,1,2,3,4) and
(SRMD12 = DK, RF, NS) and
(PCMD11 = DK, RF, NS)
Calculation for back fitness given Waist Circumference normsonly (no Sit and Reach or Partial Curl-Up norms)  
SRMD12 (HWMDWSTA = DK, RF, NS) and
SRMD12 in (0,1,2,3,4) and
(PCMD11 = DK, RF, NS)
Calculation for back fitness given Sit and Reach norms only (noWaist Circumference or Partial Curl-Up norms)  
PCMD11 (HWMDWSTA = DK, RF, NS) and
(SRMD12 = DK, RF, NS) and
PCMD11 in (0,1,2,3,4)
Calculation for back fitness given Partial Curl-Up norms only(no Waist Circumference or Sit and Reach norms)  
Table 1
RMCDBCK Specifications
Value Condition(s) Description Notes
6 CLC_AGE < 15 or
CLC_AGE > 69
Population exclusions NA
9 HWMD24 > NA and
SRMD12 > NA and
PCMD11 > NA
At least one required question was not answered (don'tknow, refusal, not stated) NS
6 HWMD24 = NA and
SRMD12 = NA and
PCMD11 = NA
Population exclusions NA
0 PTS3 = 0 or
(0.0 < PTS3 < 0.5)
Needs Improvement. Respondent's back fitness falls within arange that is generally associated with considerable healthrisk.  
1 (0.4 < PTS3 < 1.5) Fair. Respondent's back fitness falls within a range that isgenerally associated with some health risk.  
2 (1.4 < PTS3 < 2.5) Good. Respondent's back fitness falls within a range that isgenerally associated with many health benefits.  
3 (2.4 < PTS3 < 3.5) Very Good. Respondent's back fitness falls within a range thatis generally associated with considerable health benefits.  
4 (3.4 < PTS3 < 5.0) Excellent. Respondent's back fitness falls within a range thatis generally associated with optimal health benefits.  

2. RMCDMSK - Musculo-skeletal fitnessnorms for respondents 15 – 69

Variable name:
RMCDMSK

Based on:
CLC_AGE, CLC_SEX, GSMD52, SRMD12, PCMD11

Description:
This variable indicates the musculo-skeletal fitness norms for respondents aged 15 to 69, based on the norms for Sit and Reach, Grip Strength and Partial Curl-Ups.

Note:
Created in the Clinic Post-Verify process.
This variable applies to respondents aged 15-69 years old. Thecategories are:
Considerable health risk
Some health risk
Many health benefits
Considerable health benefits
Optimal health benefits

Table 2
RMCDMSK Temporary Reformat

PTS2

Value Condition(s) Description Notes
Round(((GSMD52 * 2 + SRMD12 + PCMD11) / 4), .1) CLC_SEX = 1 and
GSMD52 in (0,1,2,3,4) and
SRMD12 in (0,1,2,3,4) and
PCMD11 in (0,1,2,3,4)
Calculation for male musculo-skeletal fitness given all threenorms, i.e., Grip Strength, Sit and Reach, and PartialCurl-Up. Rounded to one decimal place
Round(((GSMD52 * 2 + SRMD12) / 3), .1) CLC_SEX = 1 and
GSMD52 in (0,1,2,3,4) and
SRMD12 in (0,1,2,3,4) and
(PCMD11 = DK, RF, NS)
Calculation for male musculo-skeletal fitness given GripStrength and Sit and Reach norms only (no Partial Curl-Upnorms). Rounded to one decimal place
Round(((GSMD52 * 2 + PCMD11) / 3), .1) CLC_SEX = 1 and
GSMD52 in (0,1,2,3,4) and
(SRMD12 = DK, RF, NS) and
PCMD11 in (0,1,2,3,4)
Calculation for male musculo-skeletal fitness given GripStrength and Partial Curl-Up norms only (no Sit and Reachnorms). Rounded to one decimal place
0 CLC_SEX = 1 and
(GSMD52 = DK, RF, NS) and
SRMD12 in (0,1,2,3,4) and
PCMD11 in (0,1,2,3,4) and
(SRMD12 + PCMD11 = 1)
Value for male musculo-skeletal fitness given Sit and Reach andPartial Curl-Up norms only (no Grip Strength norms), where the sumof the available norms is 1.  
1 CLC_SEX = 1 and
(GSMD52 = DK, RF, NS) and
SRMD12 in (0,1,2,3,4) and
PCMD11 in (0,1,2,3,4) and
(SRMD12 + PCMD11 = 3)
Value for male musculo-skeletal fitness given Sit and Reach andPartial Curl-Up norms only (no Grip Strength norms), where the sumof the available norms is 3.  
Round(((SRMD12 + PCMD11) / 2), .1) CLC_SEX = 1 and
(GSMD52 = DK, RF, NS) and
SRMD12 in (0,1,2,3,4) and
PCMD11 in (0,1,2,3,4) and
((SRMD12 + PCMD11) not in (1, 3))
Calculation for male musculo-skeletal fitness given Sit andReach and Partial Curl-Up norms only (no Grip Strength norms),where the sum of the available norms is not 1 or 3. Rounded to one decimal place
Round(((GSMD52 * 2 + SRMD12 * 2 + PCMD11) / 5), .1) CLC_SEX = 2 and
GSMD52 in (0,1,2,3,4) and
SRMD12 in (0,1,2,3,4) and
PCMD11 in (0,1,2,3,4)
Calculation for female musculo-skeletal fitness given all threenorms, i.e., Grip Strength, Sit and Reach, and PartialCurl-Up. Rounded to one decimal place
0 CLC_SEX = 2 and
GSMD52 in (0,1,2,3,4) and
SRMD12 in (0,1,2,3,4) and
(PCMD11 = DK, RF, NS) and
((GSM_D52 * 2 + SRM_D12 * 2) = 2)
Value for female musculo-skeletal fitness given Grip Strengthand Sit and Reach norms only (no Partial Curl-Up norms), where thesum of double the available norms is 2.  
1 CLC_SEX = 2 and
GSMD52 in (0,1,2,3,4) and
SRMD12 in (0,1,2,3,4) and
(PCMD11 = DK, RF, NS) and
((GSM_D52 * 2 + SRM_D12 * 2) = 6)
Value for female musculo-skeletal fitness given Grip Strengthand Sit and Reach norms only (no Partial Curl-Up norms), where thesum of double the available norms is 6.  
Round(((GSMD52 * 2 + SRMD12 * 2) / 4), .1) CLC_SEX = 2 and
GSMD52 in (0,1,2,3,4) and
SRMD12 in (0,1,2,3,4) and
(PCMD11 = DK, RF, NS) and
((GSM_D52 * 2 + SRM_D12 * 2) not in (2, 6))
Calculation for female musculo-skeletal fitness given GripStrength and Sit and Reach norms only (no Partial Curl-Up norms),where the sum of double the available norms is not 2 or 6. Rounded to one decimal place
Round(((GSMD52 * 2 + PCMD11) / 3), .1) CLC_SEX = 2 and
GSMD52 in (0,1,2,3,4) and
(SRMD12 = DK, RF, NS) and
PCMD11 in (0,1,2,3,4)
Calculation for female musculo-skeletal fitness given GripStrength and Partial Curl-Up norms only (no Sit and Reachnorms). Rounded to one decimal place
Round(((SRMD12 * 2 + PCMD11) / 3), .1) CLC_SEX = 2 and
(GSMD52 = DK, RF, NS) and
SRMD12 in (0,1,2,3,4) and
PCMD11 in (0,1,2,3,4)
Calculation for female musculo-skeletal fitness given Sit andReach and Partial Curl-Up norms only (no Grip Strength norms). Rounded to one decimal place
GSMD52 GSMD52 in (0,1,2,3,4) and
(SRMD12 = DK, RF, NS) and
(PCMD11 = DK, RF, NS)
Calculation for musculo-skeletal fitness given Grip Strengthnorms only (no Sit and Reach or Partial Curl-Up norms).  
SRMD12 (GSMD52 = DK, RF, NS) and
SRMD12 in (0,1,2,3,4) and
(PCMD11 = DK, RF, NS)
Calculation for musculo-skeletal fitness given Sit and Reachnorms only (no Grip Strength or Partial Curl-Up norms).  
PCMD11 (GSMD52 = DK, RF, NS) and
(SRMD12 = DK, RF, NS) and
PCMD11 in (0,1,2,3,4)
Calculation for musculo-skeletal fitness given Partial Curl-Upnorms only (no Grip Strength or Sit and Reach norms).  
Table 2
RMCDMSK Specifications
Value Condition(s) Description Notes
6 CLC_AGE < 15 or
CLC_AGE > 69
Population exclusions NA
9 GSMD52 > NA and
SRMD12 > NA and
PCMD11 > NA
At least one required question was not answered (don'tknow, refusal, not stated) NS
6 GSMD52 = NA and
SRMD12 = NA and
PCMD11 = NA
Population exclusions NA
0 PTS2 = 0 or
(0.0 < PTS2 < 0.5)
Needs Improvement. Respondent's musculo-skeletal fitness fallswithin a range that is generally associated with considerablehealth risk.  
1 (0.4 < PTS2 < 1.5) Fair. Respondent's musculo-skeletal fitness falls within arange that is generally associated with some health risk.  
2 (1.4 < PTS2 < 2.5) Good. Respondent's musculo-skeletal fitness falls within arange that is generally associated with many health benefits.  
3 (2.4 < PTS2 < 3.5) Very Good. Respondent's musculo-skeletal fitness falls within arange that is generally associated with considerable healthbenefits.  
4 (3.4 < PTS2 < 5.0) Excellent. Respondent's musculo-skeletal fitness falls within arange that is generally associated with optimal healthbenefits.  

Sedentary activities (1 DV)

Table
Sedentary activities Temporary Reformat

SAC_T11

Value Condition(s) Description Notes
0 SAC_11 = 1 Recode to midpoint of response ranges  
0.5 SAC_11 = 2 Recode to midpoint of response ranges  
1.5 SAC_11 = 3 Recode to midpoint of response ranges  
4 SAC_11 = 4 Recode to midpoint of response ranges  
8 SAC_11 = 5 Recode to midpoint of response ranges  
12.5 SAC_11 = 6 Recode to midpoint of response ranges  
17.5 SAC_11 = 7 Recode to midpoint of response ranges  
20 SAC_11 = 8 Recode to midpoint of response ranges  

SAC_T12

Value Condition(s) Description Notes
0 SAC_12 = 1 Recode to midpoint of response ranges  
0.5 SAC_12 = 2 Recode to midpoint of response ranges  
1.5 SAC_12 = 3 Recode to midpoint of response ranges  
4 SAC_12 = 4 Recode to midpoint of response ranges  
8 SAC_12 = 5 Recode to midpoint of response ranges  
12.5 SAC_12 = 6 Recode to midpoint of response ranges  
17.5 SAC_12 = 7 Recode to midpoint of response ranges  
20 SAC_12 = 8 Recode to midpoint of response ranges  

SAC_T13

Value Condition(s) Description Notes
0 SAC_13 = 1 Recode to midpoint of response ranges  
0.5 SAC_13 = 2 Recode to midpoint of response ranges  
1.5 SAC_13 = 3 Recode to midpoint of response ranges  
4 SAC_13 = 4 Recode to midpoint of response ranges  
8 SAC_13 = 5 Recode to midpoint of response ranges  
12.5 SAC_13 = 6 Recode to midpoint of response ranges  
17.5 SAC_13 = 7 Recode to midpoint of response ranges  
20 SAC_13 = 8 Recode to midpoint of response ranges  

SAC_T14

Value Condition(s) Description Notes
0 SAC_14 = 1 Recode to midpoint of response ranges  
0.5 SAC_14 = 2 Recode to midpoint of response ranges  
1.5 SAC_14 = 3 Recode to midpoint of response ranges  
4 SAC_14 = 4 Recode to midpoint of response ranges  
8 SAC_14 = 5 Recode to midpoint of response ranges  
12.5 SAC_14 = 6 Recode to midpoint of response ranges  
17.5 SAC_14 = 7 Recode to midpoint of response ranges  
20 SAC_14 = 8 Recode to midpoint of response ranges  

1. SACDTOT - Total Number of Hours PerWeek Spent In Sedentary Activities

Variable name:
SACDTOT

Based on:
DHH_AGE, SAC_11, SAC_12, SAC_13, SAC_14

Description:
This variable estimates the total number of hours the respondentspent in a typical week in past 3 months doing the followingsedentary activities: computer, computer games and Internet, videogames, television or videos and reading. For all activities, timespent at school or work is excluded.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents less than 12 years of age were excluded from thepopulation.

Table 1
SACDTOT Temporary Reformat

SAC

Value Condition(s) Description Notes
96 DHH_AGE < 12 Module not asked - respondent aged < 12 NA
99 (SAC_T11 = DK, RF, NS) or
(SAC_T12 = DK, RF, NS) or
(SAC_T13 = DK, RF, NS) or
(SAC_T14 = DK, RF, NS)
At least one required question was not answered (don't know,refusal, not stated) NS
SAC_T11 +
SAC_T12 +
SAC_T13 +
SAC_T14
(0 <= SAC_T11 <= 20) and
(0 <= SAC_T12 <= 20) and
(0 <= SAC_T13 <= 20) and
(0 <= SAC_T14 <= 20)
Total number of hours spent in sedentary activities.  
Table 1
SACDTOT Specifications
Value Condition(s) Description Notes
99 SAC = NS At least one required question was not answered (don't know,refusal, not stated) NS
96 SAC = NA Population exclusions NA
1 (0 <= SAC < 5) Less than 5 hours  
2 (5 <= SAC < 10) From 5 to less than 10 hours  
3 (10 <= SAC < 15) From 10 to less than 15  
4 (15 <= SAC < 20) From 15 to less than 20  
5 (20 <= SAC < 25) From 20 to less than 25 hours  
6 (25 <= SAC < 30) From 25 to less than 30 hours  
7 (30 <= SAC < 35) From 30 to less than 35 hours  
8 (35 <= SAC < 40) From 35 to less than 40 hours  
9 (40 <= SAC < 45) From 40 to less than 45 hours  
10 45 <= SAC More than 45 hours  

Screening (1 DV)

1. ATGD12 - Fasting status

Variable name:
ATGD12

Based on:
V2_HOUR, ATG_11H, ATG_12

Description:
This variable indicates whether the respondent had fasted for atleast 10 hours at the time of the clinic visit.

Note:
Created in the Clinic data collection application.

Table 1
ATGD12 Specifications
Value Condition(s) Description Notes
9 ATG_11H > NA At least one required question was not answered (don't know,refusal, not stated) NS
1 ATG_11H < V2_HOUR and
(V2_HOUR - ATG_11H) > 9
Respondent fasted 10 hours or more  
1 ATG_11H > V2_HOUR and
(24 + V2_HOUR - ATG_11H) > 9
Respondent fasted 10 hours or more  
1 ATG_12 = 1 Respondent met the fasting criteria  
2 ATG_12 = 2 Respondent was not fasted  

Socio-demographic characteristics (8DVs)

1. SDCDAIM - Age at time ofimmigration

Variable name:
SDCDAIM

Based on:
SDC_13, DHH_YOB

Description:
This variable indicates the age of the respondent at the time ofimmigration.

Introduced in:
CCHS - Cycle 1.1

Note:
Non-immigrants were excluded from the population.

Table 1
SDCDAIM Specifications
Value Condition(s) Description Notes
996 SDC_13 = NA Population exclusion NA
999 (SDC_13 = DK, RF, NS) At least one required question was not answered (don't know,refusal, not stated) NS
SDC_13 -
DHH_YOB
SDC_13 < NA Age at time of immigration [min: 0; max: 130 (current age)]

2. SDCDCGT - Culture / RaceFlag

Variable name:
SDCDCGT

Based on:
SDC_24A, SDC_24B, SDC_24C, SDC_24D, SDC_24E, SDC_24F, SDC_24G,SDC_24H, SDC_24I, SDC_24J, SDC_24K, SDC_24L, SDC_24M

Description:
This variable indicates the cultural or racial background of therespondent. It excludes all respondents who identify asaboriginal.

Introduced in:
CCHS - Cycle 3.1

Table 2
SDCDCGT Specifications
Value Condition(s) Description Notes
96 SDC_22 = 1 Aboriginal origin NA
99 (SDC_24A = DK, RF, NS) Required question was not answered (don't know, refusal, notstated) NS
1 SDC_24A = 1 and
SDC_24B > 1 and
SDC_24C > 1 and
SDC_24D > 1 and
SDC_24E > 1 and
SDC_24F > 1 and
SDC_24G > 1 and
SDC_24H > 1 and
SDC_24I > 1 and
SDC_24J > 1 and
SDC_24K > 1 and
SDC_24M > 1
White only  
2 SDC_24A > 1 and
SDC_24B > 1 and
SDC_24C > 1 and
SDC_24D = 1 and
SDC_24E > 1 and
SDC_24F > 1 and
SDC_24G > 1 and
SDC_24H > 1 and
SDC_24I > 1 and
SDC_24J > 1 and
SDC_24K > 1 and
SDC_24M > 1
Black only  
3 SDC_24A > 1 and
SDC_24B > 1 and
SDC_24C > 1 and
SDC_24D > 1 and
SDC_24E > 1 and
SDC_24F > 1 and
SDC_24G > 1 and
SDC_24H > 1 and
SDC_24I > 1 and
SDC_24J > 1 and
SDC_24K = 1 and
SDC_24M > 1
Korean only  
4 SDC_24A > 1 and
SDC_24B > 1 and
SDC_24C > 1 and
SDC_24D > 1 and
SDC_24E = 1 and
SDC_24F > 1 and
SDC_24G > 1 and
SDC_24H > 1 and
SDC_24I > 1 and
SDC_24J > 1 and
SDC_24K > 1 and
SDC_24M > 1
Filipino only  
5 SDC_24A > 1 and
SDC_24B > 1 and
SDC_24C > 1 and
SDC_24D > 1 and
SDC_24E > 1 and
SDC_24F > 1 and
SDC_24G > 1 and
SDC_24H > 1 and
SDC_24I > 1 and
SDC_24J = 1 and
SDC_24K > 1 and
SDC_24M > 1
Japanese only  
6 SDC_24A > 1 and
SDC_24B = 1 and
SDC_24C > 1 and
SDC_24D > 1 and
SDC_24E > 1 and
SDC_24F > 1 and
SDC_24G > 1 and
SDC_24H > 1 and
SDC_24I > 1 and
SDC_24J > 1 and
SDC_24K > 1 and
SDC_24M > 1
Chinese only  
7 SDC_24A > 1 and
SDC_24B > 1 and
SDC_24C = 1 and
SDC_24D > 1 and
SDC_24E > 1 and
SDC_24F > 1 and
SDC_24G > 1 and
SDC_24H > 1 and
SDC_24I > 1 and
SDC_24J > 1 and
SDC_24K > 1 and
SDC_24M > 1
South Asian only  
8 SDC_24A > 1 and
SDC_24B > 1 and
SDC_24C > 1 and
SDC_24D > 1 and
SDC_24E > 1 and
SDC_24F > 1 and
SDC_24G = 1 and
SDC_24H > 1 and
SDC_24I > 1 and
SDC_24J > 1 and
SDC_24K > 1 and
SDC_24M > 1
Southeast Asian only  
9 SDC_24A = 1 and
SDC_24B > 1 and
SDC_24C > 1 and
SDC_24D > 1 and
SDC_24E > 1 and
SDC_24F > 1 and
SDC_24G > 1 and
SDC_24H = 1 and
SDC_24I > 1 and
SDC_24J > 1 and
SDC_24K > 1 and
SDC_24M > 1
Arab only  
10 SDC_24A > 1 and
SDC_24B > 1 and
SDC_24C > 1 and
SDC_24D > 1 and
SDC_24E > 1 and
SDC_24F > 1 and
SDC_24G > 1 and
SDC_24H > 1 and
SDC_24I = 1 and
SDC_24J > 1 and
SDC_24K > 1 and
SDC_24M > 1
West Asian only  
11 SDC_24A > 1 and
SDC_24B > 1 and
SDC_24C > 1 and
SDC_24D > 1 and
SDC_24E > 1 and
SDC_24F = 1 and
SDC_24G > 1 and
SDC_24H > 1 and
SDC_24I > 1 and
SDC_24J > 1 and
SDC_24K > 1 and
SDC_24M > 1
Latin American only  
12 SDC_24A > 1 and
SDC_24B > 1 and
SDC_24C > 1 and
SDC_24D > 1 and
SDC_24E > 1 and
SDC_24F > 1 and
SDC_24G > 1 and
SDC_24H > 1 and
SDC_24I > 1 and
SDC_24J > 1 and
SDC_24K > 1 and
SDC_24M = 1
Other racial or cultural origin (only)  
13 SDC_22 > 1 and
More than one category answered
from SDC_24A to SDC_24M
Multiple racial or cultural origin  

3. SDCDFL1 - First official languagelearned and still understood

Variable name:
SDCDFL1

Based on:
SDC_33A, SDC_33B, SDC_33C, SDC_33D, SDC_33E, SDC_33F, SDC_33G,SDC_33H, SDC_33I, SDC_33J, SDC_33K, SDC_33L, SDC_33M, SDC_33N,SDC_33O, SDC_33P, SDC_33Q, SDC_33R, SDC_33S, SDC_33T, SDC_33U,SDC_33V, SDC_33W

Description:
This variable indicates the first official language spoken andstill understood by the respondent.

Introduced in:
CCHS - Cycle 2.1

Table 3
SDCDFL1 Specifications
Value Condition(s) Description Notes
99 (SDC_33A = DK, RF, NS) Required question was not answered (don't know, refusal, notstated) NS
1 SDC_33A = 1 and
SDC_33B > 1 and
SDC_33C > 1 and
SDC_33D > 1 and
SDC_33E > 1 and
SDC_33F > 1 and
SDC_33G > 1 and
SDC_33H > 1 and
SDC_33I > 1 and
SDC_33J > 1 and
SDC_33K > 1 and
SDC_33L > 1 and
SDC_33M > 1 and
SDC_33N > 1 and
SDC_33O > 1 and
SDC_33P > 1 and
SDC_33Q > 1 and
SDC_33R > 1 and
SDC_33S > 1 and
SDC_33T > 1 and
SDC_33U > 1 and
SDC_33V > 1 and
SDC_33W > 1
English only  
2 SDC_33A > 1 and
SDC_33B = 1 and
SDC_33C > 1 and
SDC_33D > 1 and
SDC_33E > 1 and
SDC_33F > 1 and
SDC_33G > 1 and
SDC_33H > 1 and
SDC_33I > 1 and
SDC_33J > 1 and
SDC_33K > 1 and
SDC_33L > 1 and
SDC_33M > 1 and
SDC_33N > 1 and
SDC_33O > 1 and
SDC_33P > 1 and
SDC_33Q > 1 and
SDC_33R > 1 and
SDC_33S > 1 and
SDC_33T > 1 and
SDC_33U > 1 and
SDC_33V > 1 and
SDC_33W > 1
French only  
3 (SDC_33A = 1 and
SDC_33B = 1) and
SDC_33C > 1 and
SDC_33D > 1 and
SDC_33E > 1 and
SDC_33F > 1 and
SDC_33G > 1 and
SDC_33H > 1 and
SDC_33I > 1 and
SDC_33J > 1 and
SDC_33K > 1 and
SDC_33L > 1 and
SDC_33M > 1 and
SDC_33N > 1 and
SDC_33O > 1 and
SDC_33P > 1 and
SDC_33Q > 1 and
SDC_33R > 1 and
SDC_33S > 1 and
SDC_33T > 1 and
SDC_33U > 1 and
SDC_33V > 1 and
SDC_33W > 1
English and French only  
4 (SDC_33A = 1 and
SDC_33B = 1) and
(SDC_33C = 1 or
SDC_33D = 1 or
SDC_33E = 1 or
SDC_33F = 1 or
SDC_33G = 1 or
SDC_33H = 1 or
SDC_33I = 1 or
SDC_33J = 1 or
SDC_33K = 1 or
SDC_33L = 1 or
SDC_33M = 1 or
SDC_33N = 1 or
SDC_33O = 1 or
SDC_33P = 1 or
SDC_33Q = 1 or
SDC_33R = 1 or
SDC_33S = 1 or
SDC_33T = 1 or
SDC_33U = 1 or
SDC_33V = 1 or
SDC_33W = 1)
English, French and Other  
5 (SDC_33A = 1 and
SDC_33B > 1) and
(SDC_33C = 1 or
SDC_33D = 1 or
SDC_33E = 1 or
SDC_33F = 1 or
SDC_33G = 1 or
SDC_33H = 1 or
SDC_33I = 1 or
SDC_33J = 1 or
SDC_33K = 1 or
SDC_33L = 1 or
SDC_33M = 1 or
SDC_33N = 1 or
SDC_33O = 1 or
SDC_33P = 1 or
SDC_33Q = 1 or
SDC_33R = 1 or
SDC_33S = 1 or
SDC_33T = 1 or
SDC_33U = 1 or
SDC_33V = 1 or
SDC_33W = 1)
English and Other (not French)  
6 (SDC_33A > 1 and
SDC_33B = 1) and
(SDC_33C = 1 or
SDC_33D = 1 or
SDC_33E = 1 or
SDC_33F = 1 or
SDC_33G = 1 or
SDC_33H = 1 or
SDC_33I = 1 or
SDC_33J = 1 or
SDC_33K = 1 or
SDC_33L = 1 or
SDC_33M = 1 or
SDC_33N = 1 or
SDC_33O = 1 or
SDC_33P = 1 or
SDC_33Q = 1 or
SDC_33R = 1 or
SDC_33S = 1 or
SDC_33T = 1 or
SDC_33U = 1 or
SDC_33V = 1 or
SDC_33W = 1)
French and Other (not English)  
7 (SDC_33A > 1 and
SDC_33B > 1) and
(SDC_33C = 1 or
SDC_33D = 1 or
SDC_33E = 1 or
SDC_33F = 1 or
SDC_33G = 1 or
SDC_33H = 1 or
SDC_33I = 1 or
SDC_33J = 1 or
SDC_33K = 1 or
SDC_33L = 1 or
SDC_33M = 1 or
SDC_33N = 1 or
SDC_33O = 1 or
SDC_33P = 1 or
SDC_33Q = 1 or
SDC_33R = 1 or
SDC_33S = 1 or
SDC_33T = 1 or
SDC_33U = 1 or
SDC_33V = 1 or
SDC_33W = 1)
Other (neither English nor French)  

4. SDCDLNG - Language(s) in whichrespondent can converse

Variable name:
SDCDLNG

Based on:
SDC_31A, SDC_31B, SDC_31C, SDC_31D, SDC_31E, SDC_31F, SDC_31G,SDC_31H, SDC_31I, SDC_31J, SDC_31K, SDC_31L, SDC_31M, SDC_31N,SDC_31O, SDC_31P, SDC_31Q, SDC_31R, SDC_31S, SDC_31T, SDC_31U,SDC_31V, SDC_31W

Description:
This variable indicates the language(s) in which the respondent canconverse.

Introduced in:
CCHS - Cycle 1.1

Table 4
SDCDLNG Specifications
Value Condition(s) Description Notes
99 (SDC_31A = DK, RF, NS) Required question was not answered (don't know, refusal, notstated) NS
1 SDC_31A = 1 and
SDC_31B > 1 and
SDC_31C > 1 and
SDC_31D >1 and
SDC_31E > 1 and
SDC_31F > 1 and
SDC_31G > 1 and
SDC_31H > 1 and
SDC_31I > 1 and
SDC_31J > 1 and
SDC_31K > 1 and
SDC_31L > 1 and
SDC_31M > 1 and
SDC_31N > 1 and
SDC_31O > 1 and
SDC_31P > 1 and
SDC_31Q > 1 and
SDC_31R > 1 and
SDC_31S > 1 and
SDC_31T > 1 and
SDC_31U > 1 and
SDC_31V > 1 and
SDC_31W > 1
English only  
2 SDC_31A > 1 and
SDC_31B = 1 and
SDC_31C > 1 and
SDC_31D > 1 and
SDC_31E > 1 and
SDC_31F > 1 and
SDC_31G > 1 and
SDC_31H > 1 and
SDC_31I > 1 and
SDC_31J > 1 and
SDC_31K > 1 and
SDC_31L > 1 and
SDC_31M > 1 and
SDC_31N > 1 and
SDC_31O > 1 and
SDC_31P > 1 and
SDC_31Q > 1 and
SDC_31R > 1 and
SDC_31S > 1 and
SDC_31T > 1 and
SDC_31U > 1 and
SDC_31V > 1 and
SDC_31W > 1
French only  
3 SDC_31A = 1 and
SDC_31B = 1 and
SDC_31C > 1 and
SDC_31D > 1 and
SDC_31E > 1 and
SDC_31F > 1 and
SDC_31G > 1 and
SDC_31H > 1 and
SDC_31I > 1 and
SDC_31J > 1 and
SDC_31K > 1 and
SDC_31L > 1 and
SDC_31M > 1 and
SDC_31N > 1 and
SDC_31O > 1 and
SDC_31P > 1 and
SDC_31Q > 1 and
SDC_31R > 1 and
SDC_31S > 1 and
SDC_31T > 1 and
SDC_31U > 1 and
SDC_31V > 1 and
SDC_31W > 1
English and French only  
4 (SDC_31A = 1 and
SDC_31B = 1) and
(SDC_31C = 1 or
SDC_31D = 1 or
SDC_31E = 1 or
SDC_31F = 1 or
SDC_31G = 1 or
SDC_31H = 1 or
SDC_31I = 1 or
SDC_31J = 1 or
SDC_31K = 1 or
SDC_31L = 1 or
SDC_31M = 1 or
SDC_31N = 1 or
SDC_31O = 1 or
SDC_31P = 1 or
SDC_31Q = 1 or
SDC_31R = 1 or
SDC_31S = 1 or
SDC_31T = 1 or
SDC_31U = 1 or
SDC_31V = 1 or
SDC_31W = 1)
English, French and Other  
5 (SDC_31A = 1 and
SDC_31B > 1) and
(SDC_31C = 1 or
SDC_31D = 1 or
SDC_31E = 1 or
SDC_31F = 1 or
SDC_31G = 1 or
SDC_31H = 1 or
SDC_31I = 1 or
SDC_31J = 1 or
SDC_31K = 1 or
SDC_31L = 1 or
SDC_31M = 1 or
SDC_31N = 1 or
SDC_31O = 1 or
SDC_31P = 1 or
SDC_31Q = 1 or
SDC_31R = 1 or
SDC_31S = 1 or
SDC_31T = 1 or
SDC_31U = 1 or
SDC_31V = 1 or
SDC_31W = 1)
English and Other (not French)  
6 (SDC_31A > 1 and
SDC_31B = 1) and
(SDC_31C = 1 or
SDC_31D = 1 or
SDC_31E = 1 or
SDC_31F = 1 or
SDC_31G = 1 or
SDC_31H = 1 or
SDC_31I = 1 or
SDC_31J = 1 or
SDC_31K = 1 or
SDC_31L = 1 or
SDC_31M = 1 or
SDC_31N = 1 or
SDC_31O = 1 or
SDC_31P = 1 or
SDC_31Q = 1 or
SDC_31R = 1 or
SDC_31S = 1 or
SDC_31T = 1 or
SDC_31U = 1 or
SDC_31V = 1 or
SDC_31W = 1)
French and Other (not English)  
7 (SDC_31A > 1 and
SDC_31B > 1) and
(SDC_31C = 1 or
SDC_31D = 1 or
SDC_31E = 1 or
SDC_31F = 1 or
SDC_31G = 1 or
SDC_31H = 1 or
SDC_31I = 1 or
SDC_31J = 1 or
SDC_31K = 1 or
SDC_31L = 1 or
SDC_31M = 1 or
SDC_31N = 1 or
SDC_31O = 1 or
SDC_31P = 1 or
SDC_31Q = 1 or
SDC_31R = 1 or
SDC_31S = 1 or
SDC_31T = 1 or
SDC_31U = 1 or
SDC_31V = 1 or
SDC_31W = 1)
Other (neither English nor French)  

5. SDCDRES - Length of time inCanada since immigration

Variable name:
SDCDRES

Based on:
SDC_13, C2_YEAR

Description:
This variable indicates the length of time the respondent has beenin Canada since his/her immigration.

Introduced in:
CCHS - Cycle 1.1

Note:
Non-immigrants were excluded from the population.

Table 5
SDCDRES Specifications
Value Condition(s) Description Notes
996 SDC_13 = NA Population exclusion NA
999 (SDC_13 = DK, RF, NS) Required question was not answered (don't know, refusal,not stated) NS
C2_YEAR -
SDC_13
SDC_13 < NA Length of time in Canada since immigration [min: 0; max: 130 (current age)]

6. SDCFABT - Aboriginal flag

Variable name:
SDCFABT

Based on:
SDC_22

Description:
This variable indicates whether the respondent reported being anaboriginal person.

Introduced in:
CCHS - Cycle 4.1

Table 6
SDCFABT Specifications
Value Condition(s) Description Notes
9 (SDC_22 = DK, RF, NS) Required question was not answered (don't know, refusal,not stated) NS
1 SDC_22 = 1 Aboriginal (North American Indian, Métis, Inuit)  
2 SDC_22 = 2 Not Aboriginal  

7. SDCFIMM - Immigration flag

Variable name:
SDCFIMM

Based on:
SDC_13

Description:
This variable indicates if the respondent is an immigrant.

Introduced in:
CCHS - Cycle 1.1

Table 7
SDCFIMM Specifications
Value Condition(s) Description Notes
9 (SDC_13 = DK, RF, NS) Required question was not answered (don't know, refusal,not stated) NS
1 SDC_13 < NA Immigrant  
2 SDC_13 = NA Not an immigrant  

8. SDCGCB - Country of birth –grouped

Variable name:
SDCGCB

Based on:
SDCCCB

Description:
This variable classifies the respondent based on his/her codedcountry of birth.

Introduced in:
CCHS - Cycle 1.1

Table 8
SDCGCB Specifications
Value Condition(s) Description Notes
99 (SDCCCB = 000, 995, DK, RF, NS) Required question was not answered (don't know, refusal,not stated) NS
1 (0 < SDCCCB < 14) Canada  
2 (100 <= SDCCCB < 200) or
SDCCCB = 206
Other North America  
3 (200 < SDCCCB < 206) or
(206 < SDCCCB < 500)
South, Central America and Caribbean  
4 (500 <= SDCCCB < 600) Europe  
5 (600 <= SDCCCB < 700) Africa  
6 (700 <= SDCCCB < 800) Asia  
7 (800 <= SDCCCB < 900) Oceania  

Strengths and difficulties (12DVs)

The SDQ is a brief behavioural screening questionnaire,developed for 3-16 year olds. It consists of 25 items dividedamong 5 categories:

  1. Emotional Symptoms
  2. Conduct Problems
  3. Hyperactivity/Inattention
  4. Peer relationship problems
  5. Prosocial Behaviour

The scores can be used as continuous variables or classified asnormal, borderline or abnormal.

Table
Strengths and difficulties Temporary Reformat

SDQT11

Value Condition(s) Description Notes
0 (SDQ_11 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_11 = 2 Recode to SDQ scoring  
2 SDQ_11 = 3 Recode to SDQ scoring  

SDQT12

Value Condition(s) Description Notes
0 (SDQ_12 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_12 = 2 Recode to SDQ scoring  
2 SDQ_12 = 3 Recode to SDQ scoring  

SDQT13

Value Condition(s) Description Notes
0 (SDQ_13 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_13 = 2 Recode to SDQ scoring  
2 SDQ_13 = 3 Recode to SDQ scoring  

SDQT14

Value Condition(s) Description Notes
0 (SDQ_14 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_14 = 2 Recode to SDQ scoring  
2 SDQ_14 = 3 Recode to SDQ scoring  

SDQT15

Value Condition(s) Description Notes
0 (SDQ_15 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_15 = 2 Recode to SDQ scoring  
2 SDQ_15 = 3 Recode to SDQ scoring  

SDQT16

Value Condition(s) Description Notes
0 (SDQ_16 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_16 = 2 Recode to SDQ scoring  
2 SDQ_16 = 3 Recode to SDQ scoring  

SDQT17

Value Condition(s) Description Notes
0 (SDQ_17 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_17 = 2 Recode to SDQ scoring  
2 SDQ_17 = 3 Recode to SDQ scoring  

SDQT18

Value Condition(s) Description Notes
0 (SDQ_18 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_18 = 2 Recode to SDQ scoring  
2 SDQ_18 = 3 Recode to SDQ scoring  

SDQT19

Value Condition(s) Description Notes
0 (SDQ_19 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_19 = 2 Recode to SDQ scoring  
2 SDQ_19 = 3 Recode to SDQ scoring  

SDQT20

Value Condition(s) Description Notes
0 (SDQ_20 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_20 = 2 Recode to SDQ scoring  
2 SDQ_20 = 3 Recode to SDQ scoring  

SDQT21

Value Condition(s) Description Notes
0 (SDQ_21 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_21 = 2 Recode to SDQ scoring  
2 SDQ_21 = 3 Recode to SDQ scoring  

SDQT22

Value Condition(s) Description Notes
0 (SDQ_22 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_22 = 2 Recode to SDQ scoring  
2 SDQ_22 = 3 Recode to SDQ scoring  

SDQT23

Value Condition(s) Description Notes
0 (SDQ_23 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_23 = 2 Recode to SDQ scoring  
2 SDQ_23 = 3 Recode to SDQ scoring  

SDQT24

Value Condition(s) Description Notes
0 (SDQ_24 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_24 = 2 Recode to SDQ scoring  
2 SDQ_24 = 3 Recode to SDQ scoring  

SDQT25

Value Condition(s) Description Notes
0 (SDQ_25 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_25 = 2 Recode to SDQ scoring  
2 SDQ_25 = 3 Recode to SDQ scoring  

SDQT26

Value Condition(s) Description Notes
0 (SDQ_26 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_26 = 2 Recode to SDQ scoring  
2 SDQ_26 = 3 Recode to SDQ scoring  

SDQT27

Value Condition(s) Description Notes
0 (SDQ_27 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_27 = 2 Recode to SDQ scoring  
2 SDQ_27 = 3 Recode to SDQ scoring  

SDQT28

Value Condition(s) Description Notes
0 (SDQ_28 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_28 = 2 Recode to SDQ scoring  
2 SDQ_28 = 3 Recode to SDQ scoring  

SDQT29

Value Condition(s) Description Notes
0 (SDQ_29 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_29 = 2 Recode to SDQ scoring  
2 SDQ_29 = 3 Recode to SDQ scoring  

SDQT30

Value Condition(s) Description Notes
0 (SDQ_30 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_30 = 2 Recode to SDQ scoring  
2 SDQ_30 = 3 Recode to SDQ scoring  

SDQT31

Value Condition(s) Description Notes
0 (SDQ_31 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_31 = 2 Recode to SDQ scoring  
2 SDQ_31 = 3 Recode to SDQ scoring  

SDQT32

Value Condition(s) Description Notes
0 (SDQ_32 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_32 = 2 Recode to SDQ scoring  
2 SDQ_32 = 3 Recode to SDQ scoring  

SDQT33

Value Condition(s) Description Notes
0 (SDQ_33 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_33 = 2 Recode to SDQ scoring  
2 SDQ_33 = 3 Recode to SDQ scoring  

SDQT34

Value Condition(s) Description Notes
0 (SDQ_34 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_34 = 2 Recode to SDQ scoring  
2 SDQ_34 = 3 Recode to SDQ scoring  

SDQT35

Value Condition(s) Description Notes
0 (SDQ_35 = 1, DK, RF, NS) Recode to SDQ scoring  
1 SDQ_35 = 2 Recode to SDQ scoring  
2 SDQ_35 = 3 Recode to SDQ scoring  

1. SDQDCON - Conduct Problems

Variable name:
SDQDCON

Based on:
DHH_AGE, SDQ_15, SDQ_17, SDQ_22, SDQ_28, SDQ_32

Description:
The Conduct Problems Scale forms part of the Strengths andDifficulties Questionnaire (SDQ), a brief behavioural screeningquestionnaire developed by Robert Goodman. There are 5 itemswhich comprise the Conduct Problems portion of thequestionnaire.

Note:
The scale can be prorated if at least 3 items were completed. Thescore can be used as a continuous variable, or else classified asnormal, borderline, or abnormal (see SDQGCON). Respondentsgreater than 17 years of age were excluded from the population.

Internet site:
www.sdqinfo.com

Table 1
SDQDCON Temporary Reformat

SDQT15C

Value Condition(s) Description Notes
1 SDQ_15 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT17C

Value Condition(s) Description Notes
1 SDQ_17 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT22C

Value Condition(s) Description Notes
1 SDQ_22 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT28C

Value Condition(s) Description Notes
1 SDQ_28 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT32C

Value Condition(s) Description Notes
1 SDQ_32 <> (DK, RF, NS) Counts the response Else set value to zero

TOCNTCON

Value Condition(s) Description Notes
SDQT15C +
SDQT17C +
SDQT22C +
SDQT28C +
SDQT32C
(SDQT15C +
SDQT17C +
SDQT22C +
SDQT28C +
SDQT32C) > = 3
Sums the total number of responses Else value = x

TOSUMCON

Value Condition(s) Description Notes
SDQT15 +
SDQT17 +
SDQT22 +
SDQT28 +
SDQT32
  Generates the total raw score (not pro-rated) on the ConductProblems Scale  
Table 1
SDQDCON Specifications
Value Condition(s) Description Notes
96 DHH_AGE > 17 Population exclusions NA
99 TOCNTCON = x At least one required question was not answered (don'tknow, refusal, not stated) NS
5 * TOSUMCON /
TOCNTCON
TOCNTCON <> x Conduct Problems Score  

2. SDQDEMO - EmotionalSymptoms

Variable name:
SDQDEMO

Based on:
DHH_AGE, SDQ_13, SDQ_18, SDQ_23, SDQ_26, SDQ_34

Description:
The Emotional Symptoms Scale forms part of the Strengths andDifficulties Questionnaire (SDQ), a brief behavioural screeningquestionnaire developed by Robert Goodman. There are 5 itemswhich comprise the Emotional Symptoms portion of thequestionnaire.

Note:
The scale can be prorated if at least 3 items were completed. Thescore can be used as a continuous variable, or else classified asnormal, borderline, or abnormal (see SDQGEMO). Respondentsgreater than 17 years of age were excluded from the population.

Internet site:
www.sdqinfo.com

Table 2
SDQDEMO Temporary Reformat

SDQT13C

Value Condition(s) Description Notes
1 SDQ_13 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT18C

Value Condition(s) Description Notes
1 SDQ_18 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT23C

Value Condition(s) Description Notes
1 SDQ_23 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT26C

Value Condition(s) Description Notes
1 SDQ_26 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT34C

Value Condition(s) Description Notes
1 SDQ_34 <> (DK, RF, NS) Counts the response Else set value to zero

TOCNTEMO

Value Condition(s) Description Notes
SDQT13C +
SDQT18C +
SDQT23C +
SDQT26C +
SDQT34C
(SDQT13C +
SDQT18C +
SDQT23C +
SDQT26C +
SDQT34C) > = 3
Sums the total number of responses Else value = x

TOSUMEMO

Value Condition(s) Description Notes
SDQT13 +
SDQT18 +
SDQT23 +
SDQT26 +
SDQT34
  Generates the total raw score (not pro-rated) on the EmotionalSymptoms Scale  
Table 2
SDQDEMO Specifications
Value Condition(s) Description Notes
96 DHH_AGE > 17 Population exclusions NA
99 TOCNTEMO = x At least one required question was not answered (don'tknow, refusal, not stated) NS
5 * TOSUMEMO /
TOCNTEMO
TOCNTEMO <> x Emotional Symptoms Score  

3. SDQDHYP -Hyperactivity/Inattention

Variable name:
SDQDHYP

Based on:
DHH_AGE, SDQ_12, SDQ_20, SDQ_25, SDQ_31, SDQ_35

Description:
The Hyperactivity/InattentionScale forms part of the Strengths and Difficulties Questionnaire(SDQ), a brief behavioural screening questionnaire developed byRobert Goodman. There are 5 items which comprise theHyperactivity/Inattention portion of the questionnaire.

Note:
The scale can be prorated if at least 3 items were completed. Thescore can be used as a continuous variable, or else classified asnormal, borderline, or abnormal (see SDQGHYP). Respondentsgreater than 17 years of age were excluded from the population.

Internet site:
www.sdqinfo.com

Table 3
SDQDHYPTemporary Reformat

SDQT12C

Value Condition(s) Description Notes
1 SDQ_12 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT20C

Value Condition(s) Description Notes
1 SDQ_20 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT25C

Value Condition(s) Description Notes
1 SDQ_25 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT31C

Value Condition(s) Description Notes
1 SDQ_31 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT35C

Value Condition(s) Description Notes
1 SDQ_35 <> (DK, RF, NS) Counts the response Else set value to zero

TOCNTHYP

Value Condition(s) Description Notes
SDQT12C +
SDQT20C +
SDQT25C +
SDQT31C +
SDQT35C
(SDQT12C +
SDQT20C +
SDQT25C +
SDQT31C +
SDQT35C) >= 3
Sums the total number of responses Else value = x

TOSUMHYP

Value Condition(s) Description Notes
SDQT12 +
SDQT20 +
SDQT25 +
SDQT31 +
SDQT35
  Generates the total raw score (not pro-rated) on theHyperactivity/Inattention Scale  
Table 3
SDQDHYP Specifications
Value Condition(s) Description Notes
96 DHH_AGE > 17 Population exclusions NA
99 TOCNTHYP = x At least one required question was not answered (don'tknow, refusal, not stated) NS
5 * TOSUMHYP /
TOCNTHYP
TOCNTHYP <> x Hyperactivity/Inattention Score  

4. SDQDPRO - ProsocialBehaviour

Variable name:
SDQDPRO

Based on:
DHH_AGE, SDQ_11, SDQ_14, SDQ_19, SDQ_27, SDQ_30

Description:
The Prosocial Behaviour Scale forms part of the Strengths andDifficulties Questionnaire (SDQ), a brief behavioural screeningquestionnaire developed by Robert Goodman. There are 5 itemswhich comprise the Prosocial Behaviour portion of thequestionnaire. The prosocial behaviour score is the onlyscore which does not comprise part of the Total DifficultiesScore.

Note:
The scale can be prorated if at least 3 items were completed. Thescore can be used as a continuous variable, or else classified asnormal, borderline, or abnormal (see SDQGPRO). Respondentsgreater than 17 years of age were excluded from the population.

Table 4
SDQDPRO Temporary Reformat

SDQT11C

Value Condition(s) Description Notes
1 SDQ_11 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT14C

Value Condition(s) Description Notes
1 SDQ_14 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT19C

Value Condition(s) Description Notes
1 SDQ_19 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT27C

Value Condition(s) Description Notes
1 SDQ_27 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT30C

Value Condition(s) Description Notes
1 SDQ_30 <> (DK, RF, NS) Counts the response Else set value to zero

TOCNTPRO

Value Condition(s) Description Notes
SDQT11C +
SDQT14C +
SDQT19C +
SDQT27C +
SDQT30C
(SDQT11C +
SDQT14C +
SDQT19C +
SDQT27C +
(SDQT30C) >= 3
Sums the total number of responses Else value = x

TOSUMPRO

Value Condition(s) Description Notes
SDQT11 +
SDQT14 +
SDQT19 +
SDQT27 +
SDQT30
  Generates the total raw score (not pro-rated) on the ProsocialBehaviour Scale  
Table 4
SDQDPRO Specifications
Value Condition(s) Description Notes
96 DHH_AGE > 17 Population exclusions NA
99 TOCNTPRO = x At least one required question was not answered (don'tknow, refusal, not stated) NS
5 * TOSUMPRO /
TOCNTPRO
TOCNTPRO <> x Prosocial Behaviour Score  

5. SDQDPRP - Peer RelationshipProblems

Variable name:
SDQDPRP

Based on:
DHH_AGE, SDQ_16, SDQ_21, SDQ_24, SDQ_29, SDQ_33

Description:
The Peer Relationship Problems Scale forms part of the Strengthsand Difficulties Questionnaire (SDQ), a brief behavioural screeningquestionnaire developed by Robert Goodman. There are 5 itemswhich comprise the Peer Relationship Problems portion of thequestionnaire.

Note:
The scale can be prorated if at least 3 items were completed. Thescore can be used as a continuous variable, or else classified asnormal, borderline, or abnormal (see SDQGPRP). Respondentsgreater than 17 years of age were excluded from the population.

Table 5
SDQDPRP Temporary Reformat

SDQT16C

Value Condition(s) Description Notes
1 SDQ_16 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT21C

Value Condition(s) Description Notes
1 SDQ_21 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT24C

Value Condition(s) Description Notes
1 SDQ_24 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT29C

Value Condition(s) Description Notes
1 SDQ_29 <> (DK, RF, NS) Counts the response Else set value to zero

SDQT33C

Value Condition(s) Description Notes
1 SDQ_33 <> (DK, RF, NS) Counts the response Else set value to zero

TOCNTPRP

Value Condition(s) Description Notes
SDQT16C +
SDQT21C +
SDQT24C +
SDQT29C +
SDQT33C
(SDQT16C +
SDQT21C +
SDQT24C +
SDQT29C +
(SDQT33C) >= 3
Sums the total number of responses Else value = x

TOSUMPRP

Value Condition(s) Description Notes
SDQT16 +
SDQT21 +
SDQT24 +
SDQT29 +
SDQT33
  Generates the total raw score (not pro-rated) on the PeerRelationship Problems Scale  
Table 5
SDQDPRP Specifications
Value Condition(s) Description Notes
96 DHH_AGE > 17 Population exclusions NA
99 TOCNTPRP = x At least one required question was not answered (don'tknow, refusal, not stated) NS
5 * TOSUMPRP /
TOCNTPRP
TOCNTPRP <> x Peer Relationship Problems Score  

6. SDQDTOT - Total DifficultiesScore

Variable name:
SDQDTOT

Based on:
DHH_AGE, SDQDEMO, SDQDCON, SDQDHYP, SDQDPRP

Description:
The Total Difficulties Score is generated by summing the scoresfrom all the scales except the Prosocial Behaviour Scale. Theresultant score can range from 0 to 40 (and is counted as missingif one of the component scores is missing).

Note:
The score can be used as a continuous variable, or else classifiedas normal, borderline, or abnormal (see SDQGTOT). Respondentsgreater than 17 years of age were excluded from the population.

Table 6
SDQDTOT Specifications
Value Condition(s) Description Notes
96 DHH_AGE > 17 Population exclusions NA
99 SDQDEMO = 99 or
SDQDCON = 99 or
SDQDHYP = 99 or
SDQDPRP = 99
At least one required question was not answered (don'tknow, refusal, not stated) NS
SDQDEMO +
SDQDCON +
SDQDHYP +
SDQDPRP
Else Total Difficulties Score min: 0; max: 40

7. SDQGCON - Conduct Problems Score– Grouped

Variable name:
SDQGCON

Based on:
DHH_AGE, SDQDCON

Description:
Although SDQ scores can be used as continuous variables (seeSDQDCON), they are also sometimes classified as "normal","borderline", and "abnormal".

Note:
Respondents greater than 17 years of age were excluded from thepopulation.

Internet site:
www.sdqinfo.com

Table 7
SDQGCON Specifications
Value Condition(s) Description Notes
6 DHH_AGE > 17 Population exclusions NA
9 SDQDCON = 99 At least one required question was not answered (don'tknow, refusal, not stated) NS
1 0 < = SDQDCON < 3 Normal  
2 SDQDCON = 3 Borderline  
3 3 < SDQDCON < 11 Abnormal  

8. SDQGEMO - Emotional Symptoms Score– Grouped

Variable name:
SDQGEMO

Based on:
DHH_AGE, SDQDEMO

Description:
Although SDQ scores can be used as continuous variables (seeSDQDEMO), they are also sometimes classified as "normal","borderline", and "abnormal".

Note:
Respondents greater than 17 years of age were excluded from thepopulation.

Internet site:
www.sdqinfo.com

Table 8
SDQGEMO Specifications
Value Condition(s) Description Notes
6 DHH_AGE > 17 Population exclusions NA
9 SDQDEMO = 99 At least one required question was not answered (don'tknow, refusal, not stated) NS
1 0 < = SDQDEMO < 4 Normal  
2 SDQDEMO = 4 Borderline  
3 4 < SDQDEMO < 11 Abnormal  

9. SDQGHYP - Hyperactivity Score– Grouped

Variable name:
SDQGHYP

Based on:
DHH_AGE, SDQDHYP

Description:
Although SDQ scores can be used as continuous variables (seeSDQDHYP), they are also sometimes classified as "normal","borderline", and "abnormal".

Note:
Respondents greater than 17 years of age were excluded from thepopulation.

Internet site:
www.sdqinfo.com

Table 9
SDQGHYP Specifications
Value Condition(s) Description Notes
6 DHH_AGE > 17 Population exclusions NA
9 SDQDHYP = 99 At least one required question was not answered (don'tknow, refusal, not stated) NS
1 0 < = SDQDHYP < 6 Normal  
2 SDQDHYP = 6 Borderline  
3 6 < SDQDHYP < 11 Abnormal  

10. SDQGPRO - Prosocial BehaviourScore – Grouped

Variable name:
SDQGPRO

Based on:
DHH_AGE, SDQDPRO

Description:
Although SDQ scores can be used as continuous variables (seeSDQDPRO), they are also sometimes classified as "normal","borderline", and "abnormal".

Note:
Respondents greater than 17 years of age were excluded from thepopulation.

Internet site:
www.sdqinfo.com

Table 10
SDQGPRO Specifications
Value Condition(s) Description Notes
6 DHH_AGE > 17 Population exclusions NA
9 SDQDPRO =99 At least one required question was not answered (don'tknow, refusal, not stated) NS
1 5 < SDQDPRO < 11 Normal  
2 SDQDPRO = 5 Borderline  
3 0 <= SDQDPRO < 5 Abnormal  

11. SDQGPRP - Peer RelationshipProblems Score – Grouped

Variable name:
SDQGPRP

Based on:
DHH_AGE, SDQDPRP

Description:
Although SDQ scores can be used as continuous variables (seeSDQDPRP), they are also sometimes classified as "normal","borderline", and "abnormal".

Note:
Respondents greater than 17 years of age were excluded from thepopulation.

Internet site:
www.sdqinfo.com

Table 11
SDQGPRP Specifications
Value Condition(s) Description Notes
6 DHH_AGE > 17 Population exclusions NA
9 SDQDPRP = 99 At least one required question was not answered (don'tknow, refusal, not stated) NS
1 0 < = SDQDPRP < 3 Normal  
2 SDQDPRP = 3 Borderline  
3 3 > SDQDPRP > 11 Abnormal  

12. SDQGTOT - Total Difficulties Score– Grouped

Variable name:
SDQGTOT

Based on:
DHH_AGE, SDQTOT

Description:
Although SDQ scores can be used as continuous variables (seeSDQDTOT), they are also sometimes classified as "normal","borderline", and "abnormal".

Note:
Respondents greater than 17 years of age were excluded from thepopulation.

Internet site:
www.sdqinfo.com

Table 12
SDQGTOT Specifications
Value Condition(s) Description Notes
6 DHH_AGE > 17 Population exclusions NA
9 SDQDTOT = 99 At least one required question was not answered (don'tknow, refusal, not stated) NS
1 0 < = SDQDTOT < 14 Normal  
2 13 < SDQDTOT < 17 Borderline  
3 16 < SDQDTOT <= 40 Abnormal  

Smoking (3 DVs)

1. SMKDSTP - Number of Years SinceStopping Smoking Completely

Variable name:
SMKDSTP

Based on:
DHH_AGE, SMK_11, SMK_12, SMK_22, SMK_51, SMK_54, SMKDSTY

Description:
This variable indicates the approximate number of years sinceformer daily smokers completely quit smoking.

Introduced in:
CCHS - Cycle 1.1

Note:
Respondents less than 12 years of age,current smokers and respondents who did not smoke a total of 100cigarettes or more in their lifetime were excluded from thepopulation.

Table 1
SMKDSTP Specifications
Value Condition(s) Description Notes
996 DHH_AGE < 12 or
(SMKDSTY = 1, 2, 3, 6) or
(SMK_12 = 3 and
SMK_11 = 2) or
SMK_22 = 0 or
SMK_51 = 2
Population exclusions NA
999 SMKDSTY = NS or
(SMK_22 = DK, RF, NS) or
(SMK_51 = DK, RF, NS) or
(SMK_54 = DK, RF, NS) or
(DHH_AGE = DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NS
DHH_AGE –
SMK_54
SMK_11 = 1 and
SMK_12 = 3 and
SMK_51 = 1
Number of years since completely quit smoking  

2. SMKDSTY - Type of Smoker

Variable name:
SMKDSTY

Based on:
DHH_AGE, SMK_11, SMK_12, SMK_22, SMK_51

Description:
This variable indicates the type of smoker the respondent is, basedon his/her smoking habits.

Note:
Respondents less than 12 years of age were excluded from thepopulation.

Introduced in:
CCHS - Cycle 1.1

Table 2
SMKDSTY Specifications
Value Condition(s) Description Notes
96 DHH_AGE < 12 Population exclusions NA
99 (SMK_11 = DK, RF, NS) or
(SMK_12 = DK, RF, NS) or
(SMK_22 = DK, RF, NS) or
(SMK_51 = DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NS
1 SMK_12 = 1 Current Daily smoker  
2 SMK_12 = 2 and
SMK_51 = 1
Occasional smoker (former daily smoker)  
3 SMK_12 = 2 and
(SMK_51 = 2, NA)
Occasional smoker (never a daily smoker or has smoked less than100 cigarettes lifetime)  
4 SMK_12 = 3 and
SMK_51 = 1
Non-smoker (former daily smoker)  
5 SMK_12 = 3 and
(SMK_51 = 2 or
SMK_22 = 0) and
SMK_11 = 1
Non-smoker (former occasional smoker, at least 100 cigarettesin lifetime)  
6 SMK_12 = 3 and
SMK_11 = 2
Never smoked (at least 100 cigarettes)  

3. SMKDYFS - Number of Years SmokedDaily (Former Daily Smokers Only)

Variable name:
SMKDYFS

Based on:
DHH_AGE, SMK_52, SMK_54

Description:
This variable indicates the number of years the respondent smokeddaily.

Note:
Respondents less than 12 years of age, respondents who are dailysmokers, respondents who have never been daily smokers or who neversmoked at least 1 cigarette per month or respondents who have notsmoked a total of 100 cigarettes in their lifetime have beenexcluded from the population.

Table 3
SMKDYFS Specifications
Value Condition(s) Description Notes
996 DHH_AGE < 12 or
SMK_12 =1 or
(SMK_51 = 2 or
SMK_22 = 0) or 
SMK_11=2
Population exclusion NA
999 (SMK_12 = DK, RF, NS) or
(SMK_52 = DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NS
SMK_54 –
SMK_52
(SMK_12 = 2,3) and
SMK_51 = 1)
Number of years smoking daily (min: 0; max: 125)

Spirometry (4 DVs)

1. SPCDELG - Eligibility -Spirometry component

Variable name:
SPCDELG

Based on:
PHC_12, PHC_42F, MHR_611A, ORS_2

Description:
This variable indicates whether the respondent was eligible for theSpirometry component. As there are multiple reasons to be screenedout of this measure, the prevalence of screen outs by reason shouldnot be based on frequency counts for this variable.

Note:
Created in the Clinic Post-Verify process.

Table 1
SPCDELG Specifications
Value Condition(s) Description Notes
7 (27 < PHC_12 < NA) Not eligible - more than 27 weeks pregnant  
9 PHC_42F = 1 Not eligible - acute or chronic condition  
12 MHR_611A = 1 Not eligible - medication use  
14 ORS_2 = 1 Not eligible - other reason  
1 Else Eligible  

2. SPMDB1FP - Percent predictedFEV1/FVC

Variable name:
SPMDB1FP

Based on:
SPM_B1F, SPM_PV1F

Description:
This variable indicates the forced expiratory volume in one second(FEV1.0) as a fraction of the forced vital capacity (FVC)expressed as a percentage of the predicted value. The predictedvalue is a reference value (in litres) obtained from a well-definedpopulation of subjects with traits similar to the person beingtested.

Note:
Created in the Clinic data collection application.
The predicted reference value for respondents aged 6-7 years wasCorey 1976. An ethnic correction of 10% was applied for the blackand Asian ethnic groups.
The predicted reference value for respondents aged 8 - 79 years wasHankinson (NHANES III). An ethnic correction of 10% was applied forthe Asian ethnic group.
Hankinson, J.L., Odencrantz, J.R. and Fedan, K.B. 1999. SpirometricReference Values from a Sample of the General U.S.Population. American Journal of Respiratory and Critical CareMedicine. 159:179-187
Corey M.L., Levison H., Crozier D. 1976. Five- to seven-year courseof pulmonary function in cystic fibrosis. American Review ofRespiratory Disease. 111; 1085-1092.Created in the ClinicPost-Verify process.

Table 2
SPMDB1FP Specifications
Value Condition(s) Description Notes

999.6

SPM_B1F = NA or SPM_PV1F = NA

Population exclusions

NA
999.9 SPM_B1F > NA or SPM_PV1F > NA At least one required question was not answered (don't know, refusal, not stated) NS
Round((SPM_B1F/SPM_PV1F * 100), .1) Else Percent predicted FEV1/FVC  

3. SPMDB1P - Percent predicted ForcedExpiratory Volume (FEV1)

Variable name:
SPMDB1P

Based on:
SPM_B1, SPM_PV1

Description:
This variable indicates the total volume of air that can beforcibly blown out in the first second of a forced vital capacitymanoeuvre (forced expiratory volume in one second), measured inlitres and expressed as a percentage of the predicted value. Thepredicted value is a reference value (in litres) obtained from awell-defined population of subjects with traits similar to theperson being tested.

Note:
Created in the Clinic data collection application.
The predicted reference value for respondents aged 6-7 years wasCorey 1976. An ethnic correction of 10% was applied for the blackand Asian ethnic groups.
The predicted reference value for respondents aged 8 - 79 years wasHankinson (NHANES III). An ethnic correction of 10% was applied forthe Asian ethnic group.
Hankinson, J.L., Odencrantz, J.R. and Fedan, K.B. 1999. SpirometricReference Values from a Sample of the General U.S.Population. American Journal of Respiratory and Critical CareMedicine. 159:179-187
Corey M.L., Levison H., Crozier D. 1976. Five- to seven-year courseof pulmonary function in cystic fibrosis. American Review ofRespiratory Disease. 111; 1085-1092.Created in the ClinicPost-Verify process.

Table 3
SPMDB1P Specifications
Value Condition(s) Description Notes
999.6 SPM_B1 = NA or
SPM_PV1 = NA
Popuolation exclusions NA
999.9 SPM_B1 > NA or SPM_PV1 > NA At least one required question was not answered (don't know, refusal, not stated) NS
Round((SPM_104 / SPM_052 * 100), .1) Else Percent predicted FEV1  

4. SPMDBFVP - Percent predicted ForcedVital Capacity (FVC)

Variable name:
SPMDBFVP

Based on:
SPM_BFVC, SPM_PFVC

Description:
This variable indicates the total volume of air that can beforcibly blown out after full inspiration (forced vital capacity),measured in litres and expressed as a percentage of the predictedvalue. The predicted value is a reference value (in litres)obtained from a well-defined population of subjects with traitssimilar to the person being tested.

Note:
Created in the Clinic data collection application.
The predicted reference value for respondents aged 6-7 years wasCorey 1976. An ethnic correction of 10% was applied for the blackand Asian ethnic groups.
The predicted reference value for respondents aged 8 - 79 years wasHankinson (NHANES III). An ethnic correction of 10% was applied forthe Asian ethnic group.
Hankinson, J.L., Odencrantz, J.R. and Fedan, K.B. 1999. SpirometricReference Values from a Sample of the General U.S.Population. American Journal of Respiratory and Critical CareMedicine. 159:179-187
Corey M.L., Levison H., Crozier D. 1976. Five- to seven-year courseof pulmonary function in cystic fibrosis. American Review ofRespiratory Disease. 111; 1085-1092

Table 4
SPMDBFVP Specifications
Value Condition(s) Description Notes
999.6 SPM_BFVC = NA or SPM_PFVC = NA Population exclusions NA
999.9 SPM_BFVC = NA or SPM_PFVC = NA At least one required question was not answered (don't know, refusal, not stated) NS
Round((SPM_BFVC / SPM_PFVC * 100), .1) Else Percent predicted FVC  

Sit and Reach (4 DVs)

1. SRCDELG - Eligibility - Sit andReach component

Variable name:
SRCDELG

Based on:
CLC_AGE, V2_TYPE, ATG_33C, PHC_12, PHC_42I, MHR_611D, PAR_5A3C,PAR_5B3C, PAR_5C3C, PAR_5D3C, PAR_5E3C, PAR_5F3C, PAR_5G3C,PAR_5H3C, PAR_5I3C, PAR_5J3C, PAR_5K3C, PAR_72C, ORS_4

Description:
This variable indicates whether the respondent was eligible for theSit and Reach component. As there are multiple reasons to bescreened out of this measure, the prevalence of screen outs byreason should not be based on frequency counts for thisvariable.

Note:
Created in the Clinic Post-Verify process.

Table 1
SRCDELG Specifications
Value Condition(s) Description Notes
2 V2_TYPE = 2 Not eligible - home visit  
3 CLC_AGE > 69 Not eligible - age  
5 ATG_33C = 1 Not eligible - drank alcohol too close to visit time  
6 (12 < PHC_12 < NA) Not eligible - more than 12 weeks pregnant  
9 PHC_42I = 1 Not eligible - acute or chronic condition  
12 MHR_611D = 1 Not eligible - medication use  
13 PAR_5A3C = 1 or
PAR_5B3C = 1 or
PAR_5C3C = 1 or
PAR_5D3C = 1 or
PAR_5E3C = 1 or
PAR_5F3C = 1 or
PAR_5G3C = 1 or
PAR_5H3C = 1 or
PAR_5I3C = 1 or
PAR_5J3C = 1 or
PAR_5K3C = 1 or
PAR_72C = 1
Not eligible - PAR-Q answer  
14 ORS_4 = 1 Not eligible - other reason  
1 Else Eligible  

2. SRMD11 - Sit and reachmeasure

Variable name:
SRMD11

Based on:
SRM_01, SRM_02

Description:
This variable indicates which of the two Sit and Reach Measurementswill be used in subsequent Derived Variables.

Note:
Created in the Clinic data collection application.

Table 2
SRMD11 Specifications
Value Condition(s) Description Notes
99.9 (SRM_01 = DK, RF, NS) and
(SRM_02 = DK, RF, NS)
At least one required question was not answered (don'tknow, refusal, not stated) NS
99.6 (1 < SRCDELG < NA) Population exclusions NA
SRMD11 = SRM_01 ((0 =< SRM_01 < 99.6) and
(0 =< SRM_02 < 99.6) and
(SRM_01 > SRM_02)) or
((0 =< SRM_01 < 99.6) and
(SRM_02 => 99.6))
SRMD11 is equal to the first Sit and Reach measurement.  
SRMD11 = SRM_02 ((0 =< SRM_01 < 99.6) and
(0 =< SRM_02 < 99.6) and
(SRM_01 <= SRM_02)) or
((SRM_01 => 99.6) and
(0 < SRM_02 < 99.6))
SRMD11 is equal to the second Sit and Reach measurement.  

3. SRMD12 - Sit and reach norms -respondents 15 – 69

Variable name:
SRMD12

Based on:
CLC_AGE, CLC_SEX, SRMD11

Description:
This variable indicates the flexibility norms for respondents aged15 to 69.

Note:
Created in the Clinic data collection application. Thisvariable categorizes the respondent's sit and reach score into oneof five categories: needs improvement, fair, good, very good orexcellent.

Source:
The Canadian Physical Activity, Fitness and Lifestyle Approach: 3rdEdition, 2003 by the Canadian Society for Exercise Physiology(CSEP)

Table 3
SRMD12 Specifications
Value Condition(s) Description Notes
6 CLC_AGE < 15 or
CLC_AGE > 69 or
SRMD11 = NA
Population exclusions NA
9 SRMD11 = NS At least one required question was not answered (don'tknow, refusal, not stated) NS
0 (CLC_SEX = 1 and
(((14 < CLC_AGE < 20) and
(0 < SRMD11 < 23.5)) or
((19 < CLC_AGE < 30) and
(0 < SRMD11 < 24.5)) or
((29 < CLC_AGE < 40) and
(0 < SRMD11 < 22.5)) or
((39 < CLC_AGE < 50) and
(0 < SRMD11 < 17.5)) or
((49 < CLC_AGE < 60) and
(0 < SRMD11 < 15.5)) or
((59 < CLC_AGE < 70) and
(0 < SRMD11 < 14.5)))) or
(CLC_SEX = 2 and 
(((14 < CLC_AGE < 20) and
(0 < SRMD11 < 28.5)) or
((19 < CLC_AGE < 30) and
(0 < SRMD11 < 27.5)) or
((29 < CLC_AGE < 40) and
(0 < SRMD11 < 26.5)) or
((39 < CLC_AGE < 50) and
(0 < SRMD11 < 24.5)) or
((49 < CLC_AGE < 60) and
(0 < SRMD11 < 24.5)) or
((59 < CLC_AGE < 70) and
(0 < SRMD11 < 22.5))))
Needs Improvement  
1 (CLC_SEX = 1 and
(((14 < CLC_AGE < 20) and
(23.4 < SRMD11 < 28.5)) or
((19 < CLC_AGE < 30) and
(24.4 < SRMD11 < 29.5)) or
((29 < CLC_AGE < 40) and
(22.4 < SRMD11 < 27.5)) or
((39 < CLC_AGE < 50) and
(17.4 < SRMD11 < 23.5)) or
((49 < CLC_AGE < 60) and
(15.4 < SRMD11 < 23.5)) or
((59 < CLC_AGE < 70) and
(14.4 < SRMD11 < 19.5)))) or
(CLC_SEX = 2 and
(((14 < CLC_AGE < 20) and
(28.4 < SRMD11 < 33.5)) or
((19 < CLC_AGE < 30) and
(27.4 < SRMD11 < 32.5)) or
((29 < CLC_AGE < 40) and
(26.4 < SRMD11 < 31.5)) or
((39 < CLC_AGE < 50) and
(24.4 < SRMD11 < 29.5)) or
((49 < CLC_AGE < 60) and
(24.4 < SRMD11 < 29.5)) or
((59 < CLC_AGE < 70) and
(22.4 < SRMD11 < 26.5))))
Fair  
2 (CLC_SEX = 1 and
(((14 < CLC_AGE < 20) and
(28.4 < SRMD11 < 33.5)) or
((19 < CLC_AGE < 30) and
(29.4 < SRMD11 < 33.5)) or
((29 < CLC_AGE < 40) and
(27.4 < SRMD11 < 32.5)) or
((39 < CLC_AGE < 50) and
(23.4 < SRMD11 < 28.5)) or
((49 < CLC_AGE < 60) and
(23.4 < SRMD11 < 27.5)) or
((59 < CLC_AGE < 70) and
(19.4 < SRMD11 < 24.5)))) or
(CLC_SEX = 2 and
(((14 < CLC_AGE < 20) and
(33.4 < SRMD11 < 37.5)) or
((19 < CLC_AGE < 30) and
(32.4 < SRMD11 < 36.5)) or
((29 < CLC_AGE < 40) and
(31.4 < SRMD11 < 35.5)) or
((39 < CLC_AGE < 50) and
(29.4 < SRMD11 < 33.5)) or
((49 < CLC_AGE < 60) and
(29.4 < SRMD11 < 32.5)) or
((59 < CLC_AGE < 70) and
(26.4 < SRMD11 < 30.5))))
Good  
3 (CLC_SEX = 1 and
(((14 < CLC_AGE < 20) and
(33.4 < SRMD11 < 38.5)) or
((19 < CLC_AGE < 30) and
(33.4 < SRMD11 < 39.5)) or
((29 < CLC_AGE < 40) and
(32.4 < SRMD11 < 37.5)) or
((39 < CLC_AGE < 50) and
(28.4 < SRMD11 < 34.5)) or
((49 < CLC_AGE < 60) and
(27.4 < SRMD11 < 34.5)) or
((59 < CLC_AGE < 70) and
(24.4 < SRMD11 < 32.5)))) or
(CLC_SEX = 2 and
(((14 < CLC_AGE < 20) and
(37.4 < SRMD11 < 42.5)) or
((19 < CLC_AGE < 30) and
(36.4 < SRMD11 < 40.5)) or
((29 < CLC_AGE < 40) and
(35.4 < SRMD11 < 40.5)) or
((39 < CLC_AGE < 50) and
(33.4 < SRMD11 < 37.5)) or
((49 < CLC_AGE < 60) and
(32.4 < SRMD11 < 38.5)) or
(59 < CLC_AGE < 70) and
(30.4 < SRMD11 < 34.5))))
Very good  
4 (CLC_SEX = 1 and
(((14 < CLC_AGE < 20) and
(38.4 < SRMD11 < 99.6)) or
((19 < CLC_AGE < 30) and
(39.4 < SRMD11 < 99.6)) or
((29 < CLC_AGE < 40) and
(37.4 < SRMD11 < 99.6)) or
((39 < CLC_AGE < 50) and
(34.4 < SRMD11 < 99.6)) or
((49 < CLC_AGE < 60) and
(34.4 < SRMD11 < 99.6)) or
((59 < CLC_AGE < 70) and
(32.4 < SRMD11 < 99.6)))) or
(CLC_SEX = 2 and
(((14 < CLC_AGE < 20) and
(42.4 < SRMD11 < 99.6)) or
((19 < CLC_AGE < 30) and
(40.4 < SRMD11 < 99.6)) or
((29 < CLC_AGE < 40) and
(40.4 < SRMD11 < 99.6)) or
((39 < CLC_AGE < 50) and
(37.4 < SRMD11 < 99.6)) or
((49 < CLC_AGE < 60) and
(38.4 < SRMD11 < 99.6)) or
((59 < CLC_AGE < 70) and
(34.4 < SRMD11 < 99.6))))
Excellent  

4. SRMD13 - Sit and reach norms -respondents less than 15

Variable name:
SRMD13

Based on:
CLC_AGE, CLC_SEX, SRMD11

Description:
This variable indicates the flexibility norms for respondents aged7 to 14.

Note:
Created in the Clinic data collection application. Thisvariable categorizes the respondent's sit and reach score into oneof three categories: below average, average or above average.

Source:
Stephens, T. & C.L. Craig. 1985. Fitness and activitymeasurement in the 1981 Canada Fitness Survey. In: Drury, T. (ed.).1989. Assessing physical fitness and activity patterns in generalpopulation surveys. Department of Health and Human Services, PublicHealth Service, Center for Disease Control, National Center forHealth Statistics. Hyattsville, MD. pub. No. (PHS) 89-1253.

Table 4
SRMD13 Specifications
Value Condition(s) Description Notes
6 CLC_AGE > 14 or
SRMD11 = NA
Population exclusions NA
9 SRMD11 = NS At least one required question was not answered (don'tknow, refusal, not stated) NS
1 (CLC_SEX = 1 and
(((6 < CLC_AGE < 10) and
(0 < = SRMD11 < 25.5)) or
((9 < CLC_AGE < 13) and
(0 < = SRMD11 < 25.5)) or
((12 < CLC_AGE < 15) and
(0 < = SRMD11 < 24.5)))) or
(CLC_SEX = 2 and
(((6 < CLC_AGE < 10) and
(0 < = SRMD11 < 30.5)) or
((9 < CLC_AGE < 13) and
(0 < = SRMD11 < 29.5)) or
((12 < CLC_AGE < 15) and
(0 < = SRMD11 < 31.5))))
Below average  
2 (CLC_SEX = 1 and
(((6 < CLC_AGE < 10) and
(25.4 < SRMD11 < 30.5)) or
((9 < CLC_AGE < 13) and
(25.4 < SRMD11 < 29.5)) or
((12 < CLC_AGE < 15) and
(24.4 < SRMD11 < 29.5)))) or
(CLC_SEX = 2 and
(((6 < CLC_AGE < 10) and
(30.4 < SRMD11 < 34.5)) or
((9 < CLC_AGE < 13) and
(29.4 < SRMD11 < 34.5)) or
((12 < CLC_AGE < 15) and
(31.4 < SRMD11 < 35.5))))
Average  
3 (CLC_SEX = 1 and
(((6 < CLC_AGE < 10) and
(30.4 < SRMD11 < 99.6)) or
((9 < CLC_AGE < 13) and
(29.4 < SRMD11 < 99.6)) or
((12 < CLC_AGE < 15) and
(29.4 < SRMD11 < 99.6)))) or
(CLC_SEX = 2 and
((6 < CLC_AGE < 10) and
(34.4 < SRMD11 < 99.6)) or
((9 < CLC_AGE < 13) and
(34.4 < SRMD11 < 99.6)) or
((12 < CLC_AGE < 15) and
(35.4 < SRMD11 < 99.6))))
Above average  
4 CLC_AGE = 6 No norm available  

Urine Collection (1 DV)

Variable name:
1. URCDELG - Eligibility - UrineCollection component

Based on:
PHC_42B

Description:
This variable indicates whether the respondent was eligible for theUrine Collection component. As there are multiple reasons to bescreened out of this measure, the prevalence of screen outs byreason should not be based on frequency counts for thisvariable.

Note:
Created in the Clinic Post-Verify process.

Table 1
URCDELG Specifications
Value Condition(s) Description Notes
9 PHC_42B = 1 Not eligible - acute or chronic condition  
1 Else Eligible  

Water and soft drink consumption (7DVs)

1. WSDD11Y - Drinks regular softdrinks - times per year

Variable name:
WSDD11Y

Based on:
WSD_11, WSD_11N

Description:
The number of times per year the respondent drinks regular softdrinks.

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 1
WSDD11Y Specifications
Value Condition(s) Description Notes
0 WSD_11 = 0 Never  
WSD_11 * 365 WSD_11N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
WSD_11 * 52 WSD_11N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
WSD_11 * 12 WSD_11N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
WSD_11 WSD_11N = 4 Reported number of times consumed per year  
9996 WSD_11N = NA Population exclusions NA
9999 Else   NS

2. WSDD12Y - Drinks diet soft drinks -times per year

Variable name:
WSDD12Y

Based on:
WSD_12, WSD_12N

Description:
The number of times per year the respondent drinks diet softdrinks.

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 2
WSDD12Y Specifications
Value Condition(s) Description Notes
0 WSD_12 = 0 Never  
WSD_12 * 365 WSD_12N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
WSD_12 * 52 WSD_12N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
WSD_12 * 12 WSD_12N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
WSD_12 WSD_12N = 4 Reported number of times consumed per year  
9996 WSD_12N = NA Population exclusions NA
9999 Else   NS

3. WSDD13Y - Drinks sport drinks -times per year

Variable name:
WSDD13Y

Based on:
WSD_13, WSD_13N

Description:
The number of times per year the respondent drinks sport drinks(including Gatorade® or Powerade®).

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 3
WSDD13Y Specifications
Value Condition(s) Description Notes
0 WSD_13 = 0 Never  
WSD_13 * 365 WSD_13N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
WSD_13 * 52 WSD_13N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
WSD_13 * 12 WSD_13N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
WSD_13 WSD_13N = 4 Reported number of times consumed per year  
9996 WSD_13N = NA Population exclusions NA
9999 Else   NS

4. WSDD14Y - Drinks fruit juices -times per year

Variable name:
WSDD14Y

Based on:
WSD_14, WSD_14N

Description:
The number of times per year the respondent drinks fruitjuices.

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 4
WSDD14Y Specifications
Value Condition(s) Description Notes
0 WSD_14 = 0 Never  
WSD_14 * 365 WSD_14N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
WSD_14 * 52 WSD_14N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
WSD_14 * 12 WSD_14N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
WSD_14 WSD_14N = 4 Reported number of times consumed per year  
9996 WSD_14N = NA Population exclusions NA
9999 Else   NS

5. WSDD15Y - Drinks fruit flavoureddrinks - times per year

Variable name:
WSDD15Y

Based on:
WSD_15, WSD_15N

Description:
The number of times per year the respondent drinks fruit flavoureddrinks.

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 5
WSDD15Y Specifications
Value Condition(s) Description Notes
0 WSD_15 = 0 Never  
WSD_15 * 365 WSD_15N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
WSD_15 * 52 WSD_15N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
WSD_15 * 12 WSD_15N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
WSD_15 WSD_15N = 4 Reported number of times consumed per year  
9996 WSD_15N = NA Population exclusions NA
9999 Else   NS

6. WSDD16Y - Drinks vegetable juices -times per year

Variable name:
WSDD16Y

Based on:
WSD_16, WSD_16N

Description:
The number of times per year the respondent drinks vegetablejuices.

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 6
WSDD16Y Specifications
Value Condition(s) Description Notes
0 WSD_16 = 0 Never  
WSD_16 * 365 WSD_16N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
WSD_16 * 52 WSD_16N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
WSD_16 * 12 WSD_16N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
WSD_16 WSD_16N = 4 Reported number of times consumed per year  
9996 WSD_16N = NA Population exclusions NA
9999 Else   NS

7. WSDD21Y - Drinks water - times peryear

Variable name:
WSDD21Y

Based on:
WSD_21, WSD_21N

Description:
The number of times per year the respondent drinks water.

Note:
Created in the Household Post-Verify process. Based on CCHS2.2 but no direct variables.

Table 7
WSDD21Y Specifications
Value Condition(s) Description Notes
0 WSD_21 = 0 Never  
WSD_21 * 365 WSD_21N = 1 Reported number of times consumed per day converted to derivednumber of times consumed per year  
WSD_21 * 52 WSD_21N = 2 Reported number of times consumed per week converted to derivednumber of times consumed per year  
WSD_21 * 12 WSD_21N = 3 Reported number of times consumed per month converted toderived number of times consumed per year  
WSD_21 WSD_21N = 4 Reported number of times consumed per year  
9996 WSD_21N = NA Population exclusions NA
9999 Else   NS

Weight change (10 DVs)

1. WTCD11KG - Weight one year ago(kilograms) - self-reported

Variable name:
WTCD11KG

Based on:
DHH_AGE, WTC_11, WTC_11N

Description:
This variable contains the self-reported weight one year ago inkilograms.

Note:
Created in the Household Post-Verify process. Respondentsless than 18 years of age were excluded from the population.

Table 1
WTCD11KG Specifications
Value Condition(s) Description Notes
996 DHH_AGE < 18 Population exclusions NA
Round(WTC_11 * 0.4536) WTC_11N = 1 Weight in pounds converted to kilograms  
WTC_11 WTC_11N = 2 Weight in kilograms  
999 Else   NS

2. WTCD11LB - Weight one year ago(pounds) - self-reported

Variable name:
WTCD11LB

Based on:
DHH_AGE, WTC_11, WTC_11N

Description:
This variable contains the self-reported weight one year ago inpounds.

Note:
Created in the Household Post-Verify process. Respondentsless than 18 years of age were excluded from the population.

Table 2
WTCD11LB Specifications
Value Condition(s) Description Notes
996 DHH_AGE < 18 Population exclusions NA
WTC_11 WTC_11N = 1 Weight in pounds  
Round(WTC_11 * 2.205) WTC_11N = 2 Weight in kilograms converted to pounds  
999 Else   NS

3. WTCD21KG - Weight ten years ago(kilograms) - self-reported

Variable name:
WTCD21KG

Based on:
DHH_AGE, WTC_21, WTC_21N

Description:
This variable contains the self-reported weight ten years ago inkilograms.

Note:
Created in the Household Post-Verify process. Respondentsless than 28 years of age were excluded from the population.

Table 3
WTCD21KG Specifications
Value Condition(s) Description Notes
996 DHH_AGE < 28 Population exclusions NA
Round(WTC_21 * 0.4536) WTC_21N = 1 Weight in pounds converted to kilograms  
WTC_21 WTC_21N = 2 Weight in kilograms  
999 Else   NS

4. WTCD21LB - Weight ten years ago(pounds) - self-reported

Variable name:
WTCD21LB

Based on
DHH_AGE, WTC_21, WTC_21N

Description:
This variable contains the self-reported weight ten years ago inpounds. Respondents less than 28 years of age were excludedfrom the population.

Note:
Created in the Household Post-Verify process.

Table 4
WTCD21LB Specifications
Value Condition(s) Description Notes
996 DHH_AGE < 28 Population exclusions NA
WTC_21 WTC_21N = 1 Weight in pounds  
Round(WTC_21 * 2.205) WTC_21N = 2 Weight in kilograms converted to pounds  
999 Else   NS

5. WTCD22KG - Weight at age 25(kilograms) - self-reported

Variable name:
WTCD22KG

Based on:
DHH_AGE, WTC_22, WTC_22N

Description:
This variable contains the self-reported weight at age 25 inkilograms. Respondents less than 27 years of age or who were35 years of age were excluded from the population.

Note:
Created in the Household Post-Verify process.

Table 5
WTCD22KG Specifications
Value Condition(s) Description Notes
996 DHH_AGE < 27 or
DHH_AGE = 35
Population exclusions NA
Round(WTC_22 * 0.4536) WTC_22N = 1 Weight in pounds converted to kilograms  
WTC_22 WTC_22N = 2 Weight in kilograms  
999 Else   NS

6. WTCD22LB - Weight at age 25(pounds) - self-reported

Variable name:
WTCD22LB

Based on:
DHH_AGE, WTC_22, WTC_22N

Description:
This variable contains the self-reported weight at age 25 inpounds. Respondents less than 27 years of age or who were 35years of age were excluded from the population.

Note: 
Created in the Household Post-Verify process.

Table 6
WTCD22LB Specifications
Value Condition(s) Description Notes
996 DHH_AGE < 27 or
DHH_AGE = 35
Population exclusions NA
WTC_22 WTC_22N = 1 Weight in pounds  
Round(WTC_22 * 2.205) WTC_22N = 2 Weight in kilograms converted to pounds  
999 Else   NS

7. WTCD23KG - Most ever weighed(kilograms) - self-reported

Variable name:
WTCD23KG

Based on:
DHH_AGE, WTC_23, WTC_23N

Description:
This variable contains the self-reported highest weight inkilograms. Respondents less than 18 years of age wereexcluded from the population.

Note:
Created in the Household Post-Verify process.

Table 7
WTCD23KG Specifications
Value Condition(s) Description Notes
996 DHH_AGE < 18 Population exclusions NA
Round(WTC_23 * 0.4536) WTC_23N = 1 Weight in pounds converted to kilograms  
WTC_23 WTC_23N = 2 Weight in kilograms  
999 Else   NS

8. WTCD23LB - Most ever weighed(pounds) - self-reported

Variable name:
WTCD23LB

Based on:
DHH_AGE, WTC_23, WTC_23N

Description:
This variable contains the self-reported highest weight inpounds. Respondents less than 18 years of age were excludedfrom the population.

Note:
Created in the Household Post-Verify process.

Table 8
WTCD23LB Specifications
Value Condition(s) Description Notes
996 DHH_AGE < 18 Population exclusions NA
WTC_23 WTC_23N = 1 Weight in pounds  
Round(WTC_23 * 2.205) WTC_23N = 2 Weight in kilograms converted to pounds  
999 Else   NS

9. WTCD25KG - Least ever weighed(kilograms) - self-reported

Variable name:
WTCD25KG

Based on:
DHH_AGE, WTC_25, WTC_25N

Description:
This variable contains the self-reported lowest weight inkilograms. Respondents less than 19 years of age wereexcluded from the population.

Note:
Created in the Household Post-Verify process.

Table 9
WTCD25KG Specifications
Value Condition(s) Description Notes
996 DHH_AGE < 19 Population exclusions NA
Round(WTC_25 * 0.4536) WTC_25N = 1 Weight in pounds converted to kilograms  
WTC_25 WTC_25N = 2 Weight in kilograms  
999 Else   NS

10. WTCD25LB - Least ever weighed(pounds) - self-reported

Variable name:
WTCD25LB

Based on:
DHH_AGE, WTC_25, WTC_25N

Description:
This variable contains the self-reported lowest weight inpounds. Respondents less than 19 years of age were excludedfrom the population.

Note:
Created in the Household Post-Verify process.

Table 10
WTCD25LB Specifications
Value Condition(s) Description Notes
996 DHH_AGE < 19 Population exclusions NA
WTC_25 WTC_25N = 1 Weight in pounds  
Round(WTC_25 * 2.205) WTC_25N = 2 Weight in kilograms converted to pounds  
999 Else   NS

Canadian Health Measures Survey (CHMS) Data User Guide: Cycle 1

April 2011

Acknowledgements

Statistics Canada relies heavily on the cooperation and good will of survey participants who donate their time. That is why the team of the Canadian Health Measures Survey (CHMS) is extremely grateful to participants for helping it collect key information relevant to the health of Canadians. This information will contribute to decision-making that will guide future health care policies and public health programs that will affect Canadians for years to come.

Statistics Canada and the team of the CHMS would also like to thank their partners, Health Canada and the Public Health Agency of Canada, for their support, cooperation and guidance.

On behalf of everyone working on the CHMS, Statistics Canada would like to extend its sincere appreciation for the time, effort and expertise that the CHMS advisory committee members have contributed in the development of this unique and ground breaking survey.

We would also like to thank all those who contributed to the preparation of this document.

Table of contents

1. Introduction
2. Canadian Health Measures Survey (CHMS) background and objectives
2.1 CHMS background
2.2 CHMS objectives
3. Survey approval
3.1 Authority
3.2 Ethical protocols and privacy standards
4. Survey content
5. Sample design
5.1 Target population
5.2 Sample size and allocation
5.3 Sampling frames and sampling strategy
5.3.1 Sampling of collection sites
5.3.2 Dwelling sampling
5.3.2.1 Fasted sub-sampling
5.3.2.2 Polybrominated diphenyl ether (PBDE) / Polychlorinated biphenyls (PCB) sub-sampling
5.3.2.3 Inorganic mercury sub-sampling
5.3.2.4 Perfluorinated sub-sampling
5.3.2.5 Phthalates sub-sampling
5.3.3 Respondent sampling
5.3.3.1 Activity monitor sub-sampling
5.3.3.2 Tobacco sub-sampling
6. Data collection
6.1 Preparation for collection
6.1.1 The Canadian Health Measures Survey (CHMS) team
6.1.1.1 Field team
6.1.1.2 Mobile examination centre (MEC) team
6.1.1.3 Head office staff
6.1.2 The mobile examination centre (MEC)
6.1.3 Informatics environment
6.1.4 Questionnaire design
6.1.4.1 Household questionnaire
6.1.4.2 Clinic questionnaire
6.1.4.3 Pre-test
6.2 Collection
6.2.1 Collection – Household interview
6.2.2 Collection – Mobile examination centre (MEC)
6.2.3 Collection – Home visit
6.3 Minimizing non-response
6.3.1 Minimizing non-response – Household interview
6.3.1.1 Introductory letters and brochures
6.3.1.2 Initiating contact
6.3.1.3 Refusal procedures – Household interview
6.3.1.4 Language barriers – Household interview
6.3.1.5 Youth respondents – Household interview
6.3.1.6 Proxy interviews
6.3.2 Minimizing non-response – Mobile examination centre (MEC)
6.3.2.1 Non-response follow-up
6.3.2.2 Flexible MEC hours
6.3.2.3 Refusal procedures - MEC
6.3.2.4 Language barriers - MEC
6.3.2.5 Youth respondents - MEC
6.4 Clinic measures protocols
6.4.1 Anthropometry
6.4.1.1 Standing height
6.4.1.2 Sitting height
6.4.1.3 Weight
6.4.1.4 Waist circumference
6.4.1.5 Hip circumference
6.4.1.6 Skinfolds
6.4.2 Heart rate and blood pressure
6.4.3 Spirometry
6.4.4 Musculoskeletal fitness
6.4.4.1 Grip strength component
6.4.4.2 Sit and reach component
6.4.4.3 Partial curl-up component
6.4.5 Modified Canadian Aerobic Fitness Test (mCAFT) component
6.4.6 Oral health component
6.4.7 Physical activity monitor
6.5 Laboratory measures protocols
6.5.1 Sample collection
6.5.1.1 Blood collection
6.5.1.2 Urine collection
6.5.2 Analysis of CBC performed at the mobile examination centre (MEC)
6.5.3 Processing and storage of the blood and urine samples
6.5.4 Shipping
7. Data processing
7.1 Verification
7.2 Mark-all-that-apply questions
7.3 Coding
7.4 Editing
7.5 Creation of derived variables
7.6 Limit of detection
7.7 Reference ranges
8. Data file structure
8.1 Description of data files
8.1.1 Wave 1: Master file
8.1.2 Wave 2: Master file
8.1.3 Wave 2: Fasted sub-sample file
8.1.4 Wave 3: Master file
8.1.5 Wave 3: Sub-sample files
8.1.6 Wave 4: Master file
8.1.7 Wave 4: Activity Monitor sub-sample file
8.1.8 Supplementary Data release: Master file
8.1.9 Supplementary Data release: Medication File
8.1.10 Supplementary Data release: Sub-sample files
8.2 Key variables for linking data files
8.3 Key variables and definitions
9. Weighting
9.1 Selection weights for collection sites
9.2 Selection weights for dwellings
9.3 Removal of out-of-scope units
9.4 Household non-response
9.5 Creation of the person weight
9.6 Non-response at the questionnaire level
9.7 Non-response at the MEC level
9.8 Winsorization
9.9 Calibration
9.10 Fasted sub-sample
9.11 Polybrominated diphenyl ether (PBDE) / Polychlorinated biphenyls (PCB) sub-sample
9.12 Inorganic mercury sub-sample
9.13 Perfluorinated compounds sub-sample
9.14 Activity monitor sub-sample
9.15 Phthalates sub-sample
9.16 Tobacco sub-sample
10. Data quality
10.1 Response rate
10.1.1 Blood draw and Urine response rate
10.1.2 Fasted sub-sample response rate
10.1.3 Polybrominated diphenyl ether (PBDE) / Polychlorinated biphenyls (PCB) sub-sample response rates
10.1.4 Inorganic mercury sub-sample response rates
10.1.5 Perfluorinated compounds sub-sample response rates
10.1.6 Activity monitor sub-sample response rates
10.1.7 Phthalates sub-sample response rates
10.1.8 Tobacco sub-sample response rate
10.2 Errors in surveys
10.2.1 Non-sampling errors
10.2.2 Sampling errors
10.3 Quality assurance and control
10.3.1 Training of household interview and mobile examination centre (MEC) Staff
10.3.1.1 Initial training
10.3.1.2 Dress rehearsal
10.3.1.3 Ongoing training – Dry run day
10.3.1.4 Annual retraining
10.3.2 Household component
10.3.2.1 Monitoring – Household interview
10.3.2.2 Household questionnaire response rates.
10.3.2.3 Validation of questionnaire responses.
10.3.3 Mobile examination centre (MEC) component
10.3.3.1 Equipment selection
10.3.3.2 Protocols and procedures
10.3.3.3 Mobile examination centre (MEC) environment
10.3.3.4 Adherence to pre-testing guidelines
10.3.3.5 Equipment monitoring
10.3.3.6 Data entry verification
10.3.3.7 Spirometry data review
10.3.3.8 Data validation
10.3.3.9 Mobile examination centre (MEC) laboratory
10.3.3.10 Replicate Testing
10.3.3.11 Proficiency Testing
10.3.3.12 Processing and storage of the blood and urine samples
10.3.3.13 Shipping
10.3.3.14 Field Blanks
10.3.3.15 Activity Monitor Data Review
10.3.4 Head Office
10.3.4.1 Correcting for bias
11. Guidelines for tabulation, analysis and release
11.1 Rounding guidelines
11.2 Sample weighting guidelines for tabulation
11.3 Precise variances or coefficients of variation
11.4 Some Recommendations for doing analysis with data from Cycle 1 of CHMS
12. File Usage
12.1 Use of weight variable
12.2 Environment Canada Climate and Air Quality File
12.3 Variable naming convention
12.3.1 Positions 1 to 3: Module section name
12.3.2 Position 4: Place Holder or Variable Type
12.3.3 Positions 6 to 8: Question reference
12.4 Access to Master file data
12.5 Variable Concordance
12.6 Special notes
13. References and end notes
Appendix 1 Pre-testing Guidelines
Appendix 2 Exclusion Criteria
Appendix 3 PAR-Q
Appendix 4 Canadian Health Measure Survey cycle 1 protocols
Appendix 5 Derived variable documentation
Appendix 6 Questionnaires
Appendix 7 Record layout
Appendix 8 Concordance table
Appendix 9 Response rates

1. Introduction

The Canadian Health Measures Survey (CHMS) is a new, comprehensive, direct health measures survey, developed to address important data gaps and limitations in existing health information. It is being conducted by Statistics Canada in partnership with Health Canada and the Public Health Agency of Canada. The results will provide comprehensive health information to advance health surveillance and research in Canada.

For cycle 1 of the CHMS directly measured indicators of health and wellness were collected on a representative sample of approximately 5,600 Canadians aged 6 to 79 years. The survey consisted of an in-home general health interview followed by a visit to a mobile examination centre (MEC). Reference laboratories and the MEC laboratory analyzed biological specimens for indicators of general health, chronic disease, infectious disease, nutritional status and environmental biomarkers.

This document will provide information to data users about the complexity of the data and any limitations that could affect their use. It will explain the methods and concepts used to collect the data at the household, as well as the MEC. Subsequent sections of the document contain information about data processing and the creation of derived variables. Content regarding sampling and weighting methodology, and guidelines for the creation of tabulations have also been included to assist the data user. Quality assurance and quality control information is provided to describe characteristics of the data which might limit their usefulness or interpretation. The document concludes with a series of appendices which provide supporting information that will be helpful to users of the CHMS data files.

All references and end notes will be found in section 13.

For additional information about the Canadian Health Measures Survey:

Toll-free number: 1-888-253-1087
E-mail: chms-ecms@statcan.gc.ca
Telecommunication device for the hearing impaired: 1-866-753-7083
Statistics Canada website: www.statcan.gc.ca/chms

2. Canadian Health Measures Survey (CHMS) background and objectives

2.1  CHMS background

Policy makers, provincial health departments, researchers and health professionals from many fields have expressed a need for a national, comprehensive source of accurate health measures to assist them in addressing the health needs of all Canadians.

In 2003, Health Canada and the Public Health Agency of Canada supported Statistics Canada in obtaining funding for a 'direct measures' health survey to address longstanding limitations within Canada's health information system. This support was announced in the 2003 federal budget as part of an extension of the Health Information Roadmap Initiative, and permanent funding was secured in the 2008 Federal Budget.

The information collected will create national baseline data on the extent of such major health concerns as obesity, hypertension, cardiovascular disease, exposure to infectious diseases, and exposure to environmental contaminants. In addition, the survey will provide clues about illness and the extent to which many diseases may be undiagnosed among Canadians. The CHMS will enable us to determine relationships between health status and disease risk factors, and to explore emerging public health issues.

2.2  CHMS objectives

Some of the objectives of the CHMS are to:

  • estimate the numbers of people with selected health conditions, characteristics and environmental exposures based on direct health measures;
  • ascertain relationships among risk factors, health promotion and protection behaviours, and health status; and
  • establish a biobank of biospecimens (urine, blood, DNA (Deoxyribonucleic acid)) from a representative sample of Canadians to be used for future research and surveillance.

3. Survey approval

3.1 Authority

The 2003 federal budget funded a national 'direct measures' health survey to be conducted by Statistics Canada in partnership with Health Canada and the Public Health Agency of Canada.

The Canadian Health Measure Survey (CHMS) is a statistical research collection under the federal Statistics Act. Statistics Canada may only collect health information for this purpose and may not use or disclose individual participant information for any other purpose without the written consent of participants.

3.2 Ethical protocols and privacy standards

The cycle 1 of the CHMS was conducted in cooperation with provincial and municipal officials, with the support of health professional associations, and with the highest regard to Canadians' health and safety. 

All processes of cycle 1 of the CHMS were reviewed and approved by the Health Canada Research Ethics Board to ensure that internationally recognized ethical standards for human research were met and maintained. In addition, protocols were developed through extensive consultation with recognized experts and were performed in conformance with universal precautions by accredited health professionals.

Participation in this survey was voluntary. The voluntary nature of the survey was stated in the introductory letter, brochure, video, Information and Consent Booklet, and on the CHMS Questions & Answers section on the Statistics Canada website. The documents also emphasized the safety and standards used in all tests. CHMS staff answered any questions respondents may have had regarding the risks of participating in the tests and the use of their data in a nine-point interactive consent process throughout the household health interview and the visit to the mobile examination centre.

Several meetings were also held with the Office of the Privacy Commissioner of Canada and with provincial privacy commissioners regarding CHMS protocols to ensure that participants' privacy rights were protected. A full Privacy Impact Assessment was completed for the CHMS and reviewed through the Office of the Privacy Commissioner of Canada—the authority that continues to provide oversight to the CHMS as well as a complaint route and redress mechanism to CHMS participants.

4. Survey content

Consultation has been an integral part of the planning of the Canadian Health Measures Survey (CHMS). Statistics Canada has undertaken extensive workshops and discussions with many programs, groups, individuals and agencies since March 2000 to gather input on proposed content, data requirements and operational considerations. Some of the groups that have been most instrumental in the content development include Health Canada, the Public Health Agency of Canada, National Health and Nutrition Examination Survey (NHANES), the CHMS Expert Advisory Committee, the CHMS Physician Advisory Committee, the CHMS Laboratory Advisory Committee, the CHMS Quality Assurance and Quality Control Advisory Committee, the CHMS Steering Committee and Statistics Canada's Policy Committee.

The cycle 1 of the CHMS was made up of a household interview and a visit to a mobile examination centre (MEC). The household interview included general demographic information and an in depth health questionnaire. The MEC visit included not only physical measure tests but also the collection of blood and urine samples from respondents. Some samples were analyzed in a laboratory at the MEC, such as the complete blood count (CBC), which includes platelets, red blood count and white blood count. The remaining samples were analyzed at three external reference laboratories. Finally, respondents were asked to wear an activity monitor for the seven days following their visit to the MEC.

The following tables provide detailed lists of household, clinic and laboratory content for the data releases for cycle 1 of the survey. The tables are organized alphabetically by similar themes and subjects to emphasize the relationships and analytical possibilities between the household, clinic and laboratory content. Further information regarding the staggered release of CHMS data can be found in Chapter 8 of this document.

Table 4.1 CHMS cycle 1 — Household questionnaire
Theme Subject CHMS Age *Source
(Statistics Canada surveys)
Alcohol Alcohol use 12 to 79 CCHS 3.1
NPHS cycle 6
Anthropometry Height and weight 6 to 79 CCHS 3.1
NPHS cycle 6
Weight change 18 to 79  
Chronic conditions Chronic conditions 6 to 79 CCHS 3.1
Phlegm 6 to 79  
Drug/Medication use Illicit drug use 14 to 79 CCHS 3.1
Medication use 6 to 79  
Environmental exposure Grooming product use 6 to 79
Hobbies 6 to 79
Housing characteristics 6 to 79
Family medical history Family medical history 6 to 79
General health General health 6 to 79 CCHS 3.1
NPHS cycle 6
Health utility index 6 to 79 CCHS 3.1
NPHS cycle 6
NLSCY cycle 6
Strengths and difficulties 6 to 17  
Infection markers Hepatitis 6 to 79
Nutrition Dietary fat consumption 6 to 79
Grains, fruits and vegetables consumption 6 to 79
Meat and fish consumption 6 to 79
Milk and dairy product consumption 6 to 79
Salt consumption 6 to 79
Water and soft drink consumption 6 to 79 NPHS cycle 6
Oral health Oral health 6 to 79  
Physical activity Children's physical activity 6 to 11 CCHS 2.2
Physical activities 12 to 79 CCHS 3.1
NPHS cycle 6
Sedentary activities 12 to 79 CCHS 3.1
Pregnancy/Birth Birth information 6 to 11 NLSCY cycle 6
Breastfeeding information 6 to 11 CCHS 3.1
NLSCY cycle 6
Maternal breastfeeding 14 to 79 (F only) CCHS 3.1
Pregnancy 14 to 59 (F only) NPHS cycle 6
Pregnancy information 6 to 11 NLSCY cycle 6
Sexual health Sexual behaviour 14 to 79 CCHS 3.1
Sleep Sleep 6 to 79 CCHS 3.1
NPHS cycle 6
Smoking Exposure to second-hand smoke 6 to 79 CCHS 3.1,
CTUMS cycle 1
Smoking 12 to 79 CCHS 2.2
CCHS 3.1
NPHS cycle 1, CTUMS cycle 1
Socio-demographic characteristics Education 15 to 79 CCHS 3.1
NPHS cycle 6
Income 6 to 79 CCHS 3.1
NPHS cycle 6
Labour force activity 15 to 75 CCHS 3.1
NPHS cycle 6
Socio-demographic characteristics 6 to 79 CCHS 3.1
Sun exposure Sun exposure 6 to 79 CCHS 3.1
* Where no survey name is listed, the CHMS is the only survey at Statistics Canada to collect this information. Otherwise, the CHMS has used content directly from, or similar to, the surveys listed in the table.
CCHS = Canadian Community Health Survey
NPHS = National Population Health Survey
NLSCY = The National Longitudinal Survey of Children and Youth
CTUMS = Canadian Tobacco Use Monitoring Survey

 

Table 4.2 CHMS cycle 1 — Clinic measures
Theme Subject CHMS Age
Anthropometry Hip circumference 6 to 79
Sitting height 6 to 79
Skinfolds 6 to 79
Standing height 6 to 79
Waist circumference 6 to 79
Weight 6 to 79
Cardiovascular health and fitness Blood pressure 6 to 79
Heart rate (resting) 6 to 79
Modified Canadian Aerobic Fitness Test (mCaft step test) 6 to 69
Lung function Spirometry 6 to 79
Musculoskeletal fitness Hand grip strength 6 to 79
Partial curl-ups 6 to 69
Sit and reach 6 to 69
Oral health Oral health examination 6 to 79
Physical activity Accelerometry (activity monitor) 6 to 79
Specimen collection
Blood collection 6 to 79
Storage of blood and urine 6 to 79
Urine collection 6 to 79

 

 

Table 4.3 CHMS cycle 1 — Clinic questionnaire
Theme Subject CHMS Age
General screening Adherence to guidelines 6 to 79
Physical and health conditions 6 to 79
Physical activity readiness (PAR) 6 to 79
Other substance confirmation 14 to 79
Lung function Spirometry questions 6 to 79
Spirometry restriction 6 to 79
Oral health Oral Health questions 6 to 79
Oral health restriction 6 to 79
Specimen collection Blood collection questions 6 to 79

 

 

Table 4.4 CHMS cycle 1 — Laboratory tests
Theme Subject Blood/Urine CHMS Age Reference Laboratory
Cardiovascular health Apolipoprotein A1 B 6 to 79 (s) (fasting) HC
Apolipoprotein B B 6 to 79 (s) (fasting) HC
C-reactive protein (high sensitivity) B 6 to 79 HC
Fibrinogen B 12 to 79 HC
High density lipoproteins (HDL) B 6 to 79 HC
Homocysteine B 6 to 79 HC
Low density lipoproteins (LDL) B 6 to 79 (s) (fasting) HC
Total cholesterol B 6 to 79 HC
Total cholesterol/HDL ratio B 6 to 79 HC
Triglycerides B 6 to 79 (s) (fasting) HC
Chemistry panel Alanine aminotransferase (ALT) B 6 to 79 HC
Albumin B 6 to 79 HC
Alkaline phosphatase (ALP) B 6 to 79 HC
Aspartate aminotransferase (AST) B 6 to 79 HC
Bicarbonate (HCO3) B 6 to 79 HC
Calcium B 6 to 79 HC
Chloride B 6 to 79 HC
Creatinine (see Kidney health theme)      
Gamma glutamyltransaminase (GGT B 6 to 79 HC
Glucose (see Diabetes theme)      
Lactate dehydrogenase (LD) B 6 to 79 HC
Phosphorus B 6 to 79 HC
Potassium B 6 to 79 HC
Sodium B 6 to 79 HC
Total bilirubin B 6 to 79 HC
Total protein B 6 to 79 HC
Urea (see Kidney health theme)      
Uric acid B 6 to 79 HC
Diabetes Glucose B 6 to 79 HC
Glycated hemoglobin (HbA1c) B 6 to 79 HC
Insulin B 6 to 79 (s) (fasting) HC
Environmental Exposure Bisphenol A U 6 to 79 (s) INSPQ
Cotinine - Free U 6 to 79 INSPQ
Metals:      
Antimony U 6 to 79 INSPQ
Arsenic (total) B&U 6 to 79 INSPQ
Cadmium B&U 6 to 79 INSPQ
Copper B&U 6 to 79 INSPQ
Lead B&U 6 to 79 INSPQ
Manganese B&U 6 to 79 INSPQ
Mercury (total) B 6 to 79 INSPQ
Mercury Inorganic B 6 to 79 (s) INSPQ
Mercury Inorganic U 6 to 79 INSPQ
Molybdenum B&U 6 to 79 INSPQ
Nickel B&U 6 to 79 INSPQ
Selenium B&U 6 to 79 INSPQ
Uranium B&U 6 to 79 INSPQ
Vanadium U 6 to 79 INSPQ
Zinc B&U 6 to 79 INSPQ
Organochlorine pesticides B 20 to 79 (s) (fasting) INSPQ
Organophosphate pesticides U 6 to 79 (s) INSPQ
Perfluorinated compounds (PFHxS, PFOS, PFOA) B 20-79 (s) INSPQ
Phenoxy herbicides (2,4-D, 2,4 DCP) U 6 to 79 (s) INSPQ
Polychlorinated biphenyls (PCBs) B 20 to 79 (s) (fasting) INSPQ
Polybrominated biphenyls (PBBs) B 20 to 79 (s) (fasting) INSPQ
Polybrominated diphenyl ethers (PBDEs) B 20 to 79 (s) (fasting) INSPQ
Phthalate metabolites U 6 to 49 INSPQ
Pyrethroid pesticides U 6 to 79 INSPQ
General Complete blood count (CBC):      
Platelets B 6 to 79 MEC
Red blood count: B 6 to 79 MEC
Haematocrit B 6 to 79 MEC
Haemoglobin B 6 to 79 MEC
Mean corpuscular haemoglobin (MCH) B 6 to 79 MEC
Mean corpuscular haemoglobin concentration (MCHC) B 6 to 79 MEC
Mean corpuscular volume (MCV) B 6 to 79 MEC
Red cell distribution width (RDW) B 6 to 79 MEC
White blood count: B 6 to 79 MEC
Basophils B 6 to 79 MEC
Eosinophils B 6 to 79 MEC
Lymphocytes B 6 to 79 MEC
Monocytes B 6 to 79 MEC
Neutrophils B 6 to 79 MEC
Infection markers Hepatitis A (anti HAV) B 14 to 79 NML
Hepatitis B (anti HBs and anti HBc) B 14 to 79 NML
Hepatitis B (HBsAg; positive anti HBc only) B 14 to 79 (s) NML
Hepatitis C (anti HCV) B 14 to 79 NML
Kidney health Creatinine B&U 6 to 79 HC (on blood-chemistry panel)/INSPQ on urine
Microalbumin U 6 to 79 HC
Microalbumin/creatinine ratio U 6 to 79 HC
Urea B 6 to 79 HC
Nutritional status Red blood cell folate B 6 to 79 HC
Iodine U 6 to 79 HC
Iodine/creatinine ratio U 6 to 79 HC
Vitamin B12 B 6 to 79 HC
Vitamin D B 6 to 79 HC
(s) = subgroup (some laboratory tests are only done on a random subgroup of the age range indicated)
HC = Health Canada
INSPQ = Institut national de santé publique du Québec
MEC = Mobile examination centre
NML = National Microbiology Laboratory, Public Health Agency of Canada

 

5. Sample design

5.1 Target population

The Canadian Health Measures Survey (CHMS) targets the population aged 6 to 79 living at home and residing in the 10 provinces and three territories. Excluded from the scope of the survey are persons living on reserves or in other Aboriginal settlements in the provinces, institutional residents, and full-time members of the Canadian Forces. Persons living in certain remote areas and persons living in areas with a low population density are also excluded. The CHMS covers approximately 96.3% of the Canadian population aged 6 to 79.

5.2 Sample size and allocation

To produce reliable estimates at the national level by age group and sex, it was determined that this survey must be carried out on a sample of at least 5,000 persons over a two-year period: a minimum size of 500 is necessary for each sex from the following five age groups: ages 6 to 11, 12 to 19, 20 to 39, 40 to 59 and 60 to 79.

5.3 Sampling frames and sampling strategy

To meet the requirements of the CHMS, a multistage sampling strategy was used.

5.3.1 Sampling of collection sites

Because the CHMS requires that participants report to a mobile examination centre (MEC), they should be able to travel to that clinic within a reasonable period of time. To accommodate these requirements, the Labour Force Survey (LFS) sampling frame was used to create the collection sites and control their size. Using the LFS frame clusters, 257 collection sites were created. The clusters are small geographic units that contain approximately 200 dwellings. A collection site is a geographic area with a population of at least 10,000 and a maximum respondent travel distance of 50 kilometres in urban areas and 100 kilometres in rural areas. Areas not meeting these criteria were excluded. The sites cover 96.3% of the Canadian population aged 6 to 79.

Although only national estimates were required, the collection sites were stratified into five regions to ensure that the allocation of the sample was representative of the national population. The regions identified, based on Statistics Canada's standard regional boundaries, were British Columbia, the Prairies (Alberta, Manitoba and Saskatchewan), Ontario, Quebec and the Atlantic provinces (Newfoundland and Labrador, Prince Edward Island, Nova Scotia and New Brunswick).

A large number of collection sites with few respondents is recommended because it helps optimize the precision of the estimates. However, the logistical and cost constraints associated with the use of MEC restricted the number of collection sites to 15. The 15 collection sites were allocated to the regions in proportion to the size of the population (Table 5.1).

Table 5.1 Selection of collection sites for the CHMS, by region – cycle 1
Region Estimated target population, ages 6 to 79, 2001 Census Number of sites in region Number of  sites allocated
Atlantic 2,061,425 36 1
Quebec 6,560,375 50 4
Ontario 10,248,545 61 6
Prairies (including Yellowknife) 4,538,970 77 2
British Columbia
(including Whitehorse)
3,540,000 33 2
Total 26,949,315 257 15

Within each region, the collection sites were sorted according to whether they belonged to a census metropolitan area (CMA), and then by the size of the population before the selection took place. A CMA is an area consisting of one or more adjacent municipalities centering on a large urban area (known as an urban core). The urban core must have a population of at least 100,000 to form a CMA. The collection sites were then sampled systematically with a probability of selection proportional to the size of their population. This selection method, combined with the sorting of sites by CMA and non-CMA and by population size, ensured that the sites selected would be allocated among CMA and non-CMA areas and among areas with larger and smaller populations. While not every province/territory would have a collection site, the CHMS sites were chosen to represent the Canadian population, east to west, with larger and smaller population densities.

Data collection at the 15 sites was carried out sequentially over two years. The sites were classified to take account of seasonality and the temporal effect, subject to operational and logistical constraints. The temporal effect was corrected by distributing uniformly the number of sites per region between the first year and the second (except for the Atlantic region, where there is only one site).

5.3.2 Dwelling sampling

Several options were examined to determine how best to obtain the required number of participants by age group. The option chosen uses the 2006 Census as a sampling frame. The household composition of dwellings as of May 2006 was available and could be used to develop a design to meet the sample requirements in each age group.

Within each collection site, dwellings with known household composition at the time of the 2006 Census were stratified by the occupants' age at the time of the survey. Five age-group strata were created, corresponding to the five CHMS age groups (6 to 11, 12 to 19, 20 to 39, 40 to 59 and 60 to 79 years). Age was determined based on the starting date of data collection at each site.

  • 6 to 11 stratum: dwellings where at least one 6-to-11-year-old is present, else,
  • 12 to 19 stratum: dwellings where at least one 12-to-19-year-old is present, else,
  • 60 to 79 stratum: dwellings where at least one 60-to-79-year-old is present, else,
  • 20 to 39 stratum: dwellings where at least one 20-to-39-year-old is present, else,
  • 40 to 59 stratum: dwellings where at least one 40-to-59-year-old is present, else,        
  • “Other” stratum: dwellings not included in the above-mentioned strata, such as vacant dwellings at the time of the 2006 Census or dwellings with people outside the CHMS age range based on household composition at the time of the 2006 Census.

Each stratum had a high probability of having dwellings inhabited by persons in the desired age groups, whether they were the same occupants or were replaced by a similar household. Within each site, a simple random sample of dwellings was selected in each stratum. The sample size was allocated in each stratum so that, combined with the strategy for sampling participants in the survey, an equal number of respondents by age group was obtained. Each selected dwelling is contacted to draw up a current list of the members of the household, and this list was then used to select survey respondents. To cover new dwellings constructed since the 2006 Census or dwellings missed in the 2006 Census and to reduce undercoverage, dwellings from the Address Register were sampled as well.

Table 5.2 shows the distribution of the number of dwellings selected per site. In all, 9,349 dwellings were selected, with an average of 623 dwellings per site.

Table 5.2 CHMS cycle 1 — Number of dwellings selected per site
Site Number of dwellings
1 590
2 610
3 611
4 536
5 580
6 626
7 655
8 664
9 656
10 659
11 659
12 654
13 611
14 616
15 622
TOTAL 9,349

5.3.2.1 Fasted sub-sampling

Each sampled dwelling was randomly flagged to indicate whether a respondent should be offered a clinic appointment in the morning or in the afternoon. A morning appointment required that respondents fast overnight, whereas shorter eating restrictions were imposed on those with afternoon appointments. This random allocation reduced the potential for bias, which could occur if respondents were permitted to choose their appointment times. During collection, the sampling fractions were adjusted to obtain approximately half of the sample where respondents were selected to be fasted and were actually fasted.

5.3.2.2 Polybrominated diphenyl ether (PBDE) / Polychlorinated biphenyls (PCB) sub-sampling

This sub-sample was actually a subset of the fasted sub-sample. Only respondents aged 20 to 79 (at the time of the household interview) had this measure performed.

5.3.2.3 Inorganic mercury sub-sampling

Each sampled dwelling was randomly flagged to indicate whether a respondent should have the inorganic mercury measure performed. During collection, the sampling fractions were adjusted to be able to obtain 500 males and 500 females aged 6 to 79 (at the time of the household interview).   In households where two persons were selected, that is one aged  6 to 11 and one aged 12 to 79, the algorithm was designed to select only one person per household.

5.3.2.4 Perfluorinated compounds sub-sampling

Each sampled dwelling was randomly flagged to indicate whether a respondent should have the perfluorinated compounds measure performed.  The original goal was to obtain 250 respondents by sex for the three older age groups (20 to 39, 40 to 59 and 60 to 79) for a total of 1,500 respondents.   Starting with site six, the requirements were changed to include all respondents aged 20 to 79 (at the time of the household interview).  It was not possible however to go back and to have this component analyzed  on leftover blood for the rest of the persons not selected for the first five sites.  Therefore, weighting was necessary to take into account the sub-sample of the first five sites.

5.3.2.5 Phthalates sub-sampling

Each sampled dwelling was randomly flagged to indicate whether a respondent would have the phthalates sub-sample performed.  All youths 6 to 19 (at the time of the household interview) were to be selected for this measure.  Adults 20 to 49 years old were to be selected if they were in households with only one person selected (no 6 to 11 year old in the household).  The total number of respondents desired was around 3,000.  Note that adults 50 years old and older were excluded for this measure.

5.3.3 Respondent sampling

Different selection probabilities by age group within each stratum were used to ensure that the sampling targets were attained (see Table 5.3). The dwellings selected were contacted to obtain a list of current household members. In each dwelling, one or two people were selected, depending on the household composition. Because children have to be accompanied to the mobile examination centre, two people were selected from households with children aged 6 to 11: one child randomly selected among those aged 6 to 11, and a second person aged 12 to 79. If no 6-to-11-year-olds were living in the household, only one person was selected among the household members aged 12 to 79. The weight vector for the selection of people aged 12 to 79 was designed to avoid large person sampling weights. Since some age groups have a weight that is up to five times higher than that of other age groups, it is possible that a selected person would have a very high sampling weight when there are many household members in a dwelling. Hence, when a specified minimum number of people aged 12 to 79 are living in a household, the weight for each person is reset to 1. In such cases, each household member has an equal chance of being selected. A careful balance of the parameters required for each of the measures put in place was obtained through studies and simulations.

Table 5.3 CHMS cycle 1 – Selection weight multiplicative factors for the person-level sampling strategy, by stratum and age group
Stratum1 Age Group
6 to 11 12 to 192 20 to 39 40 to 59 60 to 79

6 to 11 stratum

1 5 1 1 1

12 to 19 stratum

1 5 1 1 1

60 to 79 stratum

1 1 1 1 2

20 to 39 stratum

1 1 2 1 1

40 to 59 stratum

1 1 1 2 1

“Other” stratum

1 5 1 1 1

5.3.3.1 Activity monitor sub-sampling

A sub-sample of respondents aged 6 to 79 who had valid data on their activity monitor for 4 days or more was created.

5.3.3.2 Tobacco sub-sampling

A sub-sample of 2,500 clinic participants aged 12 to 79 was randomly selected for the nicotine, NNAL and metabolites sub-sample. The sample was allocated by age group (12 to 19, 20 to 39, 40 to 59 and 60 to 79) and by smoker status derived from the respondents' answers to the household questionnaire (smoker, non-smoker exposed to smoke and non-smoker non-exposed to smoke). The sample was selected among persons who provided urine and consented to storage of their urine sample for future health studies.

6. Data collection

6.1 Preparation for collection

6.1.1 The Canadian Health Measures Survey (CHMS) team

The CHMS team is a diverse well-trained, experienced group of individuals. The group can be subdivided into three sub-teams: field team, mobile examination centre (MEC) team, and head office staff.  Each of these three sub-teams was responsible for specific portions of the survey.

6.1.1.1 Field team

The CHMS field team was comprised of Statistics Canada household interviewers and an interviewer manager. The household interviewers were primarily responsible for contacting selected households, conducting the household interview, explaining the clinic portion of the survey to respondents and attempting to secure their participation at the MEC. The CHMS interviewers were supervised by an interviewer manager who was responsible for conducting data quality assurance activities for the household component, overseeing the non-response follow-up and monitoring the household collection rates. 

6.1.1.2 Mobile examination centre (MEC) team

The CHMS MEC team consisted of health professionals responsible for various components of the physical measures testing and a site manager who oversaw the day-to-day operation of the MEC. The health measures specialists were responsible for performing the majority of physical measures tests on respondents (e.g., blood pressure, anthropometry, fitness testing, spirometry). The laboratory technologists/phlebotomists conducted the specimen collection (blood and urine), performed the complete blood count analysis and processed the biological samples for storage and shipment to the reference labs. A licensed dentist conducted the oral health component. In addition to the health professionals, the MEC team also consisted of administrative staff who worked at the reception desk, the appointment booking desk and as dental recorders during the oral health component, as well as a site logistics officer who took care of the maintenance of the trailers.

6.1.1.3 Head office staff

The CHMS staff at head office monitored data collection response rates and data quality, and through periodic site visits, staff performance.  These staff members provided human resource support, processed data, and assessed the output from the reference labs.  In addition, head office staff prepared and mailed the respondent's report of selectedlaboratory tests, and provided information about the survey to respondents, the public and the media. Finally, a medical advisor followed-up with respondents about critical or sensitive results.

6.1.2 The mobile examination centre (MEC)

Two sets of trailers were acquired in order to conduct the physical measures and laboratory components of the CHMS. Each MEC was comprised of two trailers, the administrative trailer and the clinic trailer. The trailers had several different rooms, including a reception area, restrooms, an administrative office, fitness testing area, a screening area, an oral health room, anthropometry and phlebotomy areas and a laboratory.

Using MECs provided several benefits over a fixed clinic site (e.g., a clinic set up in an office building or hospital). They provided a standardized collection environment (equipment set up, room size, etc.) that was designed to meet Statistics Canada security and confidentiality policies and the flexibility of locating the MEC near the selected respondents' homes. The MEC also allowed for comparability with the National Health and Nutrition Examination Survey (NHANES) in the United States which also uses MECs.

6.1.3 Informatics environment

Computer assisted interviewing (CAI) was used to capture the responses for the household, physical measure and laboratory components of the CHMS. CAI allowed for custom interviews for every respondent based on their individual characteristics and survey responses. This included:

  • Questions that were not applicable to the respondent were skipped automatically.
  • Edits to check for inconsistent answers or out-of-range responses were applied automatically and on-screen prompts were shown when an invalid entry was recorded. Immediate feedback was given to the respondent and the interviewer was able to correct any inconsistencies.
  • Question text, including reference periods and pronouns, was customised automatically based on factors such as the age and sex of the respondent, the date of the interview and answers to previous questions.

In order to perform computerized data capture within the MEC, a unique data capture architecture had to be developed as there was a requirement for multiple users in different MEC rooms to access a single respondent's case file. This required the development of a complex, fully customized data capture application that used components of the computer assisted telephone interview (CATI) environment.

To reduce data entry errors, increase efficiency of data collection and reduce the need for double entry and data entry verification, the CHMS MEC data capture system was developed to accept direct input from other electronic testing equipment. This included communication (both one and two-way) between the application and the measurement devices (e.g., automated blood pressure cuff, weigh scale). In cases where the direct input was not functioning and manual entry was required, the data were entered in twice.

In order to support the electronic capture of physical measures data and to support the operational and administrative needs, the MEC was equipped with its own computer server. After each session at the MEC, encrypted data were transmitted from the trailer server via a dedicated out-going phone line to Statistics Canada headquarters. Encryption software was used to ensure the confidentiality of the data during transmissions between the MEC and headquarters.

6.1.4 Questionnaire design

6.1.4.1 Household questionnaire

The household questionnaire content was developed with input from stakeholders (Health Canada and the Public Health Agency) and from external experts, who participated as members of various advisory committees. In addition to new questions, existing health questions were taken from other surveys (e.g., Canadian Community Health Survey (CCHS)) to build the CHMS questionnaire. Focus groups and one-on-one interviews were conducted to look at specific questionnaire content under consideration. Improvements were made to questionnaire wording and instructions and to the flow of questions as a result of this testing. Throughout the questionnaire testing process, internal and external experts and stakeholders were consulted before content changes were finalized.

6.1.4.2 Clinic questionnaire

Development of the MEC component of the survey proceeded in much the same way as that of the household questionnaire. A determination was made as to the content and multiple iterations of the collection application were generated. Each iteration was assessed to determine the best flow within the MEC for the respondent and the MEC staff, and the quality and quantity of data collected. As with the household questionnaire, experts were frequently consulted to ensure that the clinic component achieved the goal of collecting high quality results.

6.1.4.3 Pre-test

The final test was a large scale pre-test, which tested modules on general health, sleep, height and weight, chronic conditions, nutrition and physical and sedentary activity. The testing provided the first opportunity to examine the potential household and clinic questionnaire content in conjunction with physical measure tests. The flow of physical measures tests in the mobile examination centre, as well as accompanying screening and administration questions, were also tested.

6.2 Collection

Data for cycle 1 of the CHMS were collected between March 19, 2007 and February 25, 2009 from 15 collection sites spread across Canada from Moncton to Vancouver. While one set of trailers was being used for collection, the second set would be moved to the next location and began the rigorous set of procedures required in order to prepare for collection.

6.2.1 Collection – Household interview

One to two weeks prior to the start of household interviews at each collection site, a letter and brochure were mailed to the dwellings selected for the survey, informing them that they would be contacted to participate in the survey. Interviewers called or drove to each dwelling to book an interview. Once contact was made with the household, the interviewer introduced the survey by outlining the basic steps of the survey and informing the person that participation was voluntary and that any information provided would be kept confidential under the authority of the Statistics Act.

Based on the demographic information collected, one or two persons in the household were selected to participate in the survey using different probabilities of selection by age group. The selection algorithm was designed to try and reach an equal distribution of people among the different age groups. If two persons were selected in a household, one person was always 6 to 11 years old and the other 12 to 79 years old.

Prior to commencing the interview, the respondent was informed about the survey and was shown a brief (four-minute) introductory video. For respondents between the ages of 6 and 11, an adult was present during the interview to answer questions with assistance from the child. All respondents aged 12 to 79 years who were able to answer questions on their own were asked to do so.

At the end of the interview, the interviewer provided the respondent with an information package, explaining the clinic portion of the survey, information about the tests performed at the mobile examination centre (MEC) and general information about the survey. The interviewer briefly reviewed the material in the information package and answered any questions. At that time the interviewer informed the respondent that he/she had been assigned to a morning or afternoon/evening appointment at the MEC. The morning session required the respondent to fast for 12 hours for measurement of fasting glucose, blood lipids and insulin levels, among other tests. See appendix 1 for a list of the pre-testing guidelines provided to respondents during the household interview.

If the respondent was 14 years or older, the interviewer then asked the respondent to set up an appointment at the MEC. Parents were asked to set up the appointment for their 6- to 13-year-old child. At the end of each day, the interviewers transmitted all completed cases back to Statistics Canada using encryption software to ensure the confidentiality of the data during the transmission.

6.2.2 Collection – Mobile examination centre (MEC)

Upon arrival at the MEC, the respondent's information was logged into the database at the reception desk. The MEC staff verified that the respondent's name, sex, date of birth and official language (collected during the household interview) were correct. Adherence to the pre-testing guidelines was verified and documented within the clinic capture application.

Prior to beginning the physical measures tests, the respondent must have given consent to participate in the clinic portion of the survey. Parents or guardians gave consent on behalf of children aged 6 to 13 while the child provided his/her assent to participate.

After the consent module, the respondent (or parent/guardian of younger respondents) was asked some screening questions using the PAR-Q (appendix 3). Although the PAR-Q was intended for people aged 15 to 69, it was used on all respondents. Parents or guardians completed the screening questions on behalf of children aged 6 to 13. Depending on the fasting status, the age of the respondent and the responses to the screening questions some respondents were excluded from certain measures or laboratory tests (see appendix 2 – Exclusion Criteria and appendix 3 – PAR-Q).

The respondent then proceeded with the visit at the MEC, performing all measures or laboratory tests for which he/she was eligible. The respondent could, at any time, refuse to participate in any measure or test. The order of the measures and blood tests was set in such a way that the effects of a certain measure (e.g., increased blood pressure from mCAFT) did not affect the results of another measure (e.g., resting blood pressure). For detailed information describing the protocols followed for all measures see appendix 4.

The blood and urine samples collected from survey respondents were processed, analyzed for the complete blood count (CBC) and temporarily stored in fridges and freezers within the MEC laboratory. Stored samples were sent weekly to reference laboratories in Ottawa, Quebec City and Winnipeg for additional analyses related to general health, diabetes, kidney disease, cardiovascular disease, environmental contaminants and infectious diseases and for storage in the CHMS biobank. Deoxyribonucleic acid (DNA) samples were sent twice weekly to Winnipeg for processing since DNA integrity is time sensitive.

Prior to leaving the MEC, the respondent received a report of their measurements, and possibly one or more letters for their health care provider if required (some blood pressure, and oral health results may have been deemed as requiring follow-up). A few months after the visit to the MEC, a report of laboratory tests containing most of the respondent's blood and urine test results was sent out. At the end of cycle 1 a spirometry report was also sent out to respondents. Respondents 14 years of age or older received their laboratory and spirometry reports, while parents of respondents 6 to 13 years old received their child's reports.

6.2.3 Collection – Home visit

In order to maximize response rates to the CHMS, respondents who were unwilling or unable to attend the mobile examination centre (MEC), but were willing to have a selected number of measures done in their home were offered the option of a home visit. There were 22 home visits during the entire cycle 1 collection period.

The home visit was conducted by a minimum of two CHMS staff members (most often a health measures specialist and laboratory technologist) using paper questionnaires for data recording. There were no differences in the procedures used to conduct the measurements in the home, however, there were minor differences in the equipment used (e.g., scale, stadiometer) because all home visit equipment needed to be portable. As with the visit to the MEC, the respondent could, at any time, refuse to participate in any measure or laboratory test. The home visit took less time because the mCAFT, sit and reach and partial curl-up components were not performed at the home. The oral health component was performed only if a dentist was available at the time of the home visit. Once back at the MEC, the health measures specialist entered the data from the home visit into the application and coded it as a home visit. The senior health measures specialist then verified the data entry. A report of measurements was mailed to the respondent within a few days of completion of the home visit. Respondents received a report of laboratory tests a few months later and a report of their spirometry results at the end of cycle 1.

6.3 Minimizing non-response

6.3.1 Minimizing non-response – Household interview

To ensure the best possible response rate at the household, many practices were used to minimise non-response.

6.3.1.1 Introductory letters and brochures

Before the start of each collection period, introductory letters and brochures were sent to the sampled households, explaining the different steps of the survey and emphasizing the importance of the survey by providing examples of how CHMS data would be used.

6.3.1.2 Initiating contact

Interviewers were instructed to make all reasonable attempts to obtain interviews. When the timing of the interviewer's visit was inconvenient, an appointment was made to come back at a more convenient time. If no one was home on first visit, a notice that a CHMS interviewer had stopped by their home was left at the door. Numerous personal visits were made at different times on different days until potential respondents were home and available to do the interview. If interviewers were unable to make contact with anyone at the household, they tried to obtain a name and telephone number for the dwelling using directory listings, neighbours, superintendents, and management/rental offices in order to call the dwelling later to arrange for a personal visit.

6.3.1.3  Refusal procedures – Household interview

The interviewer tried to convince the respondent of the importance and potential benefits of participating in the survey. If the individuals refused to participate in the survey, they were then contacted a second time by another interviewer who, again, stressed the importance of the survey and the household's participation.

6.3.1.4 Language barriers – Household interview

The introductory letter and the CHMS brochure were available in English, French, Punjabi and Chinese. Respondents were interviewed in the official language of their choice (English or French). To remove language as a barrier to conducting interviews, where possible, the CHMS team recruited interviewers with some language competencies other than the two official languages. When necessary, cases were transferred to an interviewer or external interpreter with the language competency so that questions/instructions could be translated for the respondent in order to complete the interview. If no one with a certain language competency could be found, it was also acceptable for a household member who was willing and able to translate for the respondent to do so. Note that this was not considered a proxy interview. The household member was simply translating the questions and the respondent's answers directly to the interviewer, not answering for the respondent.

6.3.1.5 Youth respondents – Household interview

Interviewers were obliged to obtain verbal permission from parents/guardians to interview youths between the ages of 12 and 17 who were selected for the survey. Several measures were taken to alleviate potential parental concerns and to ensure a completed interview. Interviewers provided the parent or guardian with a copy of the "Note to parents / guardians about interviewing youths for the Canadian Health Measures Survey". This document explained the purpose of collecting information from youth, listed the subjects to be covered in the survey and explained the need to respect a child's right to privacy and confidentiality.

When interviewing respondents 12 to 17 years of age, interviewers ensured that the parent was in the home but that the interview took place outside of parents/siblings earshot, unless permission was obtained from the youth for a parent to be present. If the interviewer was not able to obtain privacy to interview the selected youth the interviewer read the questions out loud with the parent in the room and had the youth enter his/her answers directly on the computer. If privacy and confidentiality could not be respected, the case was coded as a refusal with a permanent note indicating that privacy/confidentiality could not be respected.

If parents asked to know more about the type of questions asked in the survey, interviewers first directed them to the topics listed in the Note to Parents. If they asked to see the actual questions interviewers showed them the content section of the Interviewer's Manual. For those parents who requested a copy of the questions, a copy was available through the Data Collection Manager, as well as at Statistics Canada's head office in Ottawa.

6.3.1.6 Proxy interviews

In the CHMS, parents/guardians answered questions about their children aged 6 to 11. This included all household modules that were applicable to children. Children assisted in responding to some questions for which the parents may not have known the answers (e.g., participation in activity during school hours).

In cases where the selected respondent 12 years of age or over was, for reasons of physical or mental limitations, incapable of completing an interview at the household, another knowledgeable member of the household supplied information about the selected respondent. While these proxy respondents were able to provide accurate answers to most of the survey questions, the more sensitive or personal questions were beyond their scope of knowledge. This resulted in some questions from the proxy interview being unanswered. Every effort was taken to keep proxy interviews to a minimum. The variable "PROXY" on the data set indicates whether a household interview was completed by proxy.

In cycle 1, 20% of the interviews were proxy. Of the proxy interviews, 97% of the respondents were under 12 years of age and 3% of the respondents were 12 years of age or older.

6.3.2 Minimizing non-response – Mobile examination centre(MEC)

Approximately 85% of respondents who completed a household interview in cycle 1 agreed to go to the MEC. Many practices were used to obtain this high level of participation, including:

6.3.2.1 Non-response follow-up

MEC staff were responsible for following up with any respondents who did not book an appointment at the end of their household interview and did not call the MEC booking desk to set up an appointment within a few days after their household interview. The staff members followed similar refusal procedures as household interviewers.

6.3.2.2 Flexible MEC hours

Strategies specific to the MEC included the creation of MEC opening hours and appointment times that provided maximum flexibility to the respondent. The MEC staff tried to accommodate as many respondents as possible at each site. In addition, home visits were offered to respondents unwilling or unable to go to the MEC.

6.3.2.3 Refusal procedures - MEC

To minimize the non-response to the CHMS, the MEC staff were instructed to make all reasonable attempts to convince respondents who participated in the household interview to attend the MEC. The appointment booking desk staff, who had received specific training in handling refusal conversions, followed-up with respondents who refused to participate in the clinic portion of the survey. If they were unsuccessful in booking an appointment, the MEC site manager would call one final time to attempt to book an appointment. Respondents who could not be contacted (e.g., no answer at the home phone number) were sent a "No-contact Letter" asking them to phone the MEC to book an appointment.

6.3.2.4 Language barriers - MEC

Mobile examination centre (MEC) staff handled language barriers in the same way as household interviewers. CHMS staff, external interpreters or family members with knowledge of the third language were used to help the respondent understand instructions and forms in order to complete the visit at the MEC. The consent forms and screening questions were also available in Chinese and Punjabi to try to accommodate respondents from these ethnic minority groups since a high percentage of these groups were known to be living within some of the cycle 1 sample collection areas.

6.3.2.5 Youth respondents - MEC

As with the household interview, parents/guardians answered all questions about their children aged 6 to 11. The questions asked at the MEC pertained to screening, lung health and oral health. Since the age of consent for the clinic portion of the CHMS was 14 years of age, parents/guardians also answered these questions for their 12 and 13 year old youths, though the youths usually assisted. Youths aged 14 and over were responsible for signing their own consent form and answering all questions, though parents/guardians were in some cases present during their visit at the MEC and able to assist on difficult questions as required. To maximize efficiency at the MEC, the selected child or youth usually did the physical measure tests with one CHMS staff member while their selected parent was doing tests with another CHMS staff member.

In cases where the selected respondent 14 years of age or over was, for reasons of physical or mental limitations, incapable of answering questions and completing the consent form at the MEC, the parent/guardian assisted.

6.4 Clinic measures protocols

For detailed information describing the protocols see appendix 4. For detailed information on test exclusion criteria see appendix 2.

6.4.1 Anthropometry

The Anthropometric Component consisted of height (which included standing and sitting height) and weight measurement, measurement of circumferences (including waist and hip circumferences) and skinfold measurement. The six anthropometric measures were taken on all eligible respondents aged 6 to 79 years old. Acute or chronic conditions specifically affecting one or more of the anthropometry measures were reasons why a respondent would not have been eligible for any of the following measures.

6.4.1.1 Standing height

Standing height is an assessment of maximum vertical size. This measure was taken of all the respondents who were able to stand unassisted. Standing height was measured with a fixed stadiometer with a vertical backboard and a moveable headboard using a procedure based on the 3rd edition of the Canadian Physical Activity, Fitness and Lifestyle Approach (CPAFLA) 3rd Edition3. A self-reported height was captured for respondents who were not eligible because of an acute or chronic condition (e.g., in a wheelchair) or who refused to have their height measured.

6.4.1.2 Sitting height

Sitting height is an assessment of maximum vertical size when the respondent is sitting. It was measured on respondents who were able to sit unassisted. Sitting height was measured with a fixed stadiometer with a vertical backboard and a moveable headboard. The respondent's sitting height was measured, following the International Society for the Advancement of Kinanthropometry (ISAK) protocol4.

6.4.1.3 Weight

The respondent's weight was taken on a Mettler Toledo digital scale. The respondent's weight was measured, following the CPAFLA protocol (3rd Edition) 3.

6.4.1.4 Waist circumference

Waist circumference provides an indicator of abdominal fat distribution. The respondent's waist circumference was measured, following the CPAFLA protocol (3rd Edition)3. This protocol was modified by the Canadian Society for Exercise Physiology in the fall of 2008. Note that the CHMScontinued using the previous protocol throughout cycle 1 and a cross over study is being performed to allow the comparison between cycle 1 and cycle 2 data.

6.4.1.5 Hip circumference

Hip circumference is the maximal circumference measured at the hips or buttocks region (whichever is larger). It is used to calculate the waist-to-hip ratio (waist circumference divided by hip circumference) and is a simple method of determining body fat pattern. The protocol for hip circumference was based on the Canadian Standard Test of Fitness 3rd Edition5.

6.4.1.6 Skinfolds

Skinfold measurement is used to estimate the amount of body fat and the distribution of subcutaneous adipose tissue. The principle behind this technique is that the amount of subcutaneous fat (fat that lies directly beneath the skin) is proportional to the total amount of body fat. The respondent's skinfolds were measured following the five site method of the CPAFLA protocol3. Skinfold mesurements were not done on respondents with a body mass index (BMI) equal to or greater than 30 kg/m2.

6.4.2 Heart rate and blood pressure

The respondent's resting heart rate and blood pressure (BP) were measured, following a new protocol created by the CHMS and inspired by the report entitled "Hypertension Surveillance in Canada: Minimum Standards For Assessing Blood Pressure In Surveys" report6. This report was published by an expert committee consisting of members of the Canadian Hypertension Society, the Canadian Coalition for High Blood Pressure Prevention and Control and the Heart and Stroke Foundation of Canada.

Heart rate and blood pressure measurements were taken on all eligible respondents aged 6 to 79 years old using an oscillometric blood pressure measurement device. A series of BP and heart rate measurements were taken at one minutes intervals following a five minute rest period and the last five measurements were used in the determination of average resting heart rate and blood pressure.

6.4.3 Spirometry

Spirometry measurements were taken on all eligible respondents aged 6 to 79 years old, following the 1994 Update of the Standardization of Spirometry article, published by the American Thoracic Society7. Heart attacks, chest or abdomen surgeries within 3 months, eye surgery within 6 weeks, tuberculosis medication, pregnancy >27 weeks and acute or chronic conditions were some reasons for exclusion.

6.4.4 Musculoskeletal fitness

Fitness tests were done on all eligible respondents aged 6 to 69, except for the grip strength component which was done on all eligible respondents aged 6 to 79 years old. Medication use, acute and chronic conditions, pregnancy, and failure to adhere to pre-testing guidelines (appendix 1) were some reasons why a respondent would not have been eligible for any of the measures. Respondents aged 70-79 were excluded from the sit and reach, partial curl-ups and aerobic fitness tests.

6.4.4.1 Grip strength component

Muscular strength refers to the maximum force that can be generated by a specific muscle or muscle group. The most common method of measuring muscular strength in the field is isometric grip strength. Isometric grip strength is measured using a handgrip dynamometer.

The protocol for the Grip Strength Component was based on the Canadian Physical Activity, Fitness and Lifestyle Approach 3rd Edition (CPAFLA)3.

6.4.4.2 Sit and reach component

The sit and reach test is a commonly used field test to assess low back and hip-joint flexibility. The protocol for the Sit and Reach Component was based on the Canadian Physical Activity, Fitness and Lifestyle Approach (CPAFLA)3.

6.4.4.3 Partial curl-up component

The partial curl-up test evaluates the endurance of the abdominal muscles. The protocol for the Partial Curl-up Component is based on the Canadian Physical Activity, Fitness and Lifestyle Approach (CPAFLA)3.

6.4.5 Modified Canadian Aerobic Fitness Test (mCAFT) component

Aerobic fitness is a measure of the combined efficiency of the lungs, heart, vasculature, and exercising muscles. The eligible age group for the mCAFT was 6 to 69 years of age. The protocol for the modified Canadian Aerobic Fitness Test (mCAFT) Component is based on the Canadian Physical Activity, Fitness and Lifestyle Approach (CPAFLA) 3rd Edition  for adults 15-69 years of age3, but was applied to all age groups.

6.4.6 Oral health component

For the oral health component a dentist assessed the oral health status of respondents based on criteria from the World Health Organization and was done on all eligible respondents aged 6 to 69 years old. The results of the oral exam were directly entered into a computer, with the help of a dental recorder.  The World Dental Federation (FDI) numbering system was used.

6.4.7 Physical activity monitor

Activity monitors were administered to all eligible respondents aged 6 to 79 years old. Respondents in wheelchairs were excluded. An Actical activity monitor was given to respondents, along with an adjustable belt, an XPRESSPOST envelope, and an information sheet. Respondents were to wear the monitor for seven days and then return it in the envelope provided.

6.5 Laboratory measures protocols

6.5.1 Sample collection

Blood and urine were collected to obtain laboratory results that provided prevalence estimates of disease, risk factors for certain diseases, and baseline information on health, nutritional status of the population and environmental contaminants.

6.5.1.1 Blood collection

The blood was collected by the phlebotomist using a standardized venipuncture technique. The amount of blood taken from respondents depended on their age:

  • 6 to 11 years: < 28 ml
  • 12 to 13 years: < 38 ml
  • 14 to 19 years: < 50 ml
  • 20 to 79 years: < 80 ml

An increasing amount of blood was taken by age because more tests were done for older respondents. For example, 6 to 11 year olds had less than half the number of tests done as compared to 20 to 79 year olds.

The blood test selected for the CHMS were ranked in order of priority and so it should be noted that a deviation from the standard order of blood draw was made to accommodate the priority of the test(s) being measured. The order of vacutainer collected was dependent upon the priority of the test versus the anticoagulant used.

6.5.1.2 Urine collection

The urine was collected using mid stream collection and the respondent was asked to provide approximately 60 ml of urine. This collection was done for all respondents.

6.5.2 Analysis of CBC performed at the mobile examination centre (MEC)

The complete blood count (CBC) was analyzed in the MEC laboratory by the technologist and performed for all respondents from whom a sample was collected. Results from any unsuitable samples (ie: severe lipemia or clot in tube) were not reported.

6.5.3 Processing and storage of the blood and urine samples

It was important to process the specimens as soon as possible because the quality and integrity of the blood and urine specimens would deteriorate over time. Whole blood was centrifuged to separate plasma from cells and serum from a clot, to allow for the aliquoting into smaller tubes. The urine was also aliquoted into smaller tubes. These tubes were placed in shipping trays and stored in the MEC laboratory in either the refrigerator or the freezer depending on the test. All specimens were stored as soon as processing was complete to ensure the samples viability.

6.5.4 Shipping

With the exception of the DNA samples, which were sent twice a week, the shipping of the blood and urine aliquots was done once a week to the reference laboratory on pre-assigned shipping days. All packages were sent to one of the 3 reference labs: Health Canada in Ottawa for chronic disease, general health (chemistry panel) and nutritional lab results, Institut National de Santé Publique du Québec (INSPQ) in Quebec City for environmental lab tests plus urine creatinine (environmental adjustments and kidney health) and the National Microbiology Laboratory (NML) in Winnipeg for infectious disease lab results and the CHMS biobank. Shipments were packaged according to the International Air Transport Association (IATA) and transport of dangerous goods regulations.(biological specimens). All shipments were sent by overnight delivery using a courier company certified to handle dangerous goods and were scheduled to arrive at the reference laboratory only on weekdays. A specimen tracking system was also developed so that staff could determine the status of every tube shipped to the reference laboratory. In addition, the temperature of refrigerated shipments was monitored using pre programmed devices that took the temperature every 15 to 30 minutes during shipping. This allowed assurance that the samples received by the reference labs were maintained at an adequate temperature to preserve the sample integrity during shipping.

There were some occurrences where shipments were delayed and once received it was noted that the shipment conditions had been compromised. Any results from compromised samples were removed to ensure that only the highest quality of data was reported to the CHMS by the reference laboratory.

7. Data processing

7.1 Verification

One of the unique features of Canadian Health Measures Survey (CHMS) is that three different sets of data were collected for the same respondent: household interview data, clinic measurement data, and laboratory result data. Each set of data had to be processed on its own, yet they could not be completely separated from each other because at various points during processing the three sets of data had to be used together.

The processing of the household interview data was performed in a manner similar to that of other health surveys at Statistics Canada. The data were validated first at the record level and then at the individual variable level, followed by detailed top-down editing. During data collection processing took place on a daily basis (including weekends). The household interview responses had to be processed quickly in order for the data to be available at the mobile examination centre (MEC) in time for the respondent's visit to the MEC.

Similarly, the processing of the clinic measurement data began with the data being validated first at the record level and then at the individual variable level, followed by detailed top-down editing. Also, because the laboratory tests were determined based on responses during the clinic portion at the MEC, the clinic data were used to generate a file containing a list of the tests for which results were expected to be received. This laboratory "control" file was used in processing the laboratory result data.

The processing of the laboratory result data involved significant file manipulation due to the fact that several different file types were received from the MEC and the three reference laboratories. Then the data were validated at the record level and at the individual variable level, and several new variables were derived. The laboratory data were processed as quickly as possible so that any critical results that had been identified at the reference laboratories and the MEC were immediately available for reporting to respondents.

7.2 Mark-all-that-apply questions

During the initial phase of data processing, mark-all-that-apply questions are expanded with each response category in the original question becoming a series of separate questions with a yes or no response.  In the example below, the respondent selected both 2 and 3 as answers to the original question.  The answers to the new questions are based on answers from the original question.

Original question:

CCC_Q96 What type of hepatitis do you have?

Interviewer: Read categories to respondent. Mark all that apply.

  1. Hepatitis A
  2. X Hepatitis B
  3. X Hepatitis C

Final questions / responses:

CCC_96A What type of hepatitis do you have? - Hepatitis A

  1. Yes
  2. X No
  3. Don’t Know, Refused                        

CCC_96B  What type of hepatitis do you have? - Hepatitis B

  1. X Yes
  2. No
  3. Don’t Know, Refused        

CCC_96C What type of hepatitis do you have? - Hepatitis C

  1. X Yes
  2. No
  3. Don’t Know, Refused

7.3 Coding

Pre-coded answer categories were supplied for all suitable variables, and the interviewers and health measures specialists were trained to assign a respondent’s answers to the appropriate category. In the event that a respondent’s answer could not be easily assigned to an existing category, several questions also allowed the interviewer to enter a long-answer text in the “Other-specify” category. All such questions were closely examined at head office during processing. For some household questions, the long answers were coded into one of the existing listed categories if the long answer duplicated a listed category. If not, the response was coded as ‘Other’. For the clinic responses, at the end of processing, long answers were reviewed and some responses were coded to existing categories. For the remaining ‘Other- Specify’ answers, some new categories were created where there were sufficient numbers of responses. The remaining responses were coded as ‘Other’. For all questions, the “Other-specify” responses will be taken into account when refining the answer categories for future cycles.

Statistics Canada is not permitted to release specific drug names and cigarette brands. As a result, this information, while collected, is not available on the master files. Instead, coded variables representing information about these responses (ATC, AHFS and tar values (see section 12.6)) are placed on the master files.

Certain data were collected as long answers and had codes assigned, specifically medication and other health product names and dosages, cigarette brand names, and job description information. For medications and cigarette brand names, databases of standard descriptions were available in the computer-assisted interviewing (CAI) applications, and a code could be assigned at the time of collection based on a search of the appropriate database. Any description without a code was extracted during processing and coded manually. Over the course of the full survey, there were 1,832 medications and other health products that were manually assigned a Drug Identification Number (DIN), and 154 cigarette brand names that were manually assigned a brand code. For the assignment of North American Industry Classification System (NAICS) 2002 and National Occupational Classification - Statistics (NOC-S) 2001 codes, all 3,485 records with data in the job description fields were extracted and sent for manual industry and occupation coding. A preliminary step of matching to a database of previously coded descriptions was performed to provide starting points for the manual coding.

7.4 Editing

Most editing of the data was performed at the time of the interview by the CAI application. It was not possible for interviewers to enter out-of-range values, and flow errors were controlled through programmed skip patterns. For example, CAI ensured that questions that did not apply to the respondent were not asked. Edits requiring corrective action were incorporated in the CAI application to deal with inconsistent responses, and warnings not requiring corrective action were also included to identify unusual (i.e., improbable rather than impossible) values as a means of catching potential errors and allowing correction at source.

At head-office the data underwent a series of processing steps that may have resulted in some of the data being adjusted. As a final validation step, the CAI edits were re-applied to the processed data. As a result, the final data were complete and contained reserve codes for responses of “less than limit of detection”, “not applicable”, “don’t know”, “refused” and “not stated”.

Table 7.1 Reserve code of responses
Reserve Code label Reserve code
Less than limit of detection 9.5, 99.5  etc.
Not Applicable 6, 96, 99.6  etc.
Don’t Know 7, 97, 99.7  etc.
Refusal 8, 98, 99.8  etc.
Not Stated 9, 99, 99.9  etc.

7.5 Creation of derived variables

Derived variables (DV) for cycle 1 of the Canadian Health Measures Survey (CHMS) were created to facilitate data analysis and to minimize the risk of errors. The three most common types of derived variables were created by: collapsing data from one variable into groups; combining the data from one or more survey questions for a single respondent; or combining data from more than one respondent. Derived variables generally have a "D" or "G" in the fourth character of the variable name.

Three other types of derived variables can be found on the cycle 1 CHMS data file: converting responses given in various time units (days, weeks, months or a year) into one type of units such as yearly; calculation of body mass index (BMI); and the creation of the Health Utility Index which is based on the responses from a series of questions.

Specifications were received which provided details as to how to proceed with the creation of each derived variable. Cycle 1 of the CHMS has 599 derived variables. Half were created within the capture application in order to be able to provide initial results to the respondents at the end of their visit to the mobile examination centre and the remaining derived variables were created after the completion of data processing.

All derived variables underwent a validation process after creation in order to ensure that the output provided the requested data. Modifications to the specifications may have been necessary if, during validation by subject matter experts, the output from the derived variables was determined to be flawed. Complete documentation for all cycle 1 derived variables can be found in the DV documentation (see appendix 5).

7.6 Limit of detection

The data released for waves 2 and 3 had never been collected or released by Statistics Canada in the past.  This data differed from the typical survey data collected through interviews or the data collected through actual physical measurements.  The vast majority of the data for waves 2 and 3 came from the blood and urine samples collected at the Mobile Examination Centres. 

Once collected, the samples were sent to the reference laboratories for analysis.  The instruments and methods used to perform the analysis have limits as to what they can actually detect in the blood and urine samples.  For that reason, from time to time, results were returned from the laboratories with a code that indicated that the results for a particular sample were above or below a level of concentration that could be measured by the instrument for that test.

During processing this information was translated into a reserve code. 

7.7 Reference ranges

Commonly referred to as the normal range a reference range is an interval into which 95% of the population falls. The ranges are established over time by testing a large number of people.  They provide guidelines as to what are usual values in the population being measured but are not optimal health ranges

Reference ranges may vary depending on factors such as age, sex, and race.  The instruments used in the laboratory may also affect these ranges.  For that reason, reference ranges are provided by each laboratory for each type of test they perform for a specific time period.  The ranges may change over time as characteristics of the population being measured change.

For tests performed on samples collected by the CHMS, a document is available upon request that lists the reference ranges for each test.  As these ranges are provided by the various laboratories performing the tests, Statistics Canada provides them to data users for informational purposes only. 

8. Data file structure

8.1 Description of data files

The dissemination files only contain data from respondents who attended the mobile examination centre (MEC) and agreed to share their responses with Health Canada and the Public Health Agency of Canada. For cycle 1 of the CHMS, after the completion of processing, and with the removal of non-share records, 5,604 records remain on the main master file.

By the end of cycle 1 dissemination, nine files containing CHMS data will have been released. One file will contain the complete household, MEC visit, full sample laboratory, and activity monitor derived variables. Six files will contain sub-sampled laboratory data. There will also be one file that contains the activity monitor derived variables for people who wore their activity monitor for four or more days, and one file with all the medication data. An additional file containing Environment Canada weather and air quality data was also released.

Waves
Wave 1 Household & MEC data January 2010
Wave 2 Laboratory data (excluding environmental measures) + selected fasted sub-sample file March 2010
Wave 3

Laboratory data (including environmental measures) + three sub-sample files

  • Polybrominated diphenyl ether (PBDE) / Polychlorinated biphenyls (PCB) sub-sampling
  • Inorganic mercury sub-sampling
  • Perfluorinated sub-sampling
August 2010
Wave 4 Activity monitoring data + sub-sample file for people who wore their activity monitor for 4 or more days November 2010
Supplementary Data release

Master file with updated 2,4,D data

Tobacco sub-sample data:

  • Nicotine
  • Nicotine metabolites
  • NNAL (4-(methylnitrosoamino)-1-(3-pyridyl)-1-butanol)

Phthalate sub-sample data
Medication data

April 2011

The basic sample for the survey covers respondents 6 to 79 years of age. However, some of the measures or tests were only done for one sex, on fasting respondents or on a random subgroup of ages. Refer to chapter 4 for detailed content information.

8.1.1 Wave 1: Master file

This first data file contains the responses collected during the household interview, the MEC visit, derived variables created by the collection applications and some created after data processing. The 5,604 records represent one record for each respondent who went to the MEC and participated in at least some of the measures and then agreed to share those results with Health Canada and the Public Health Agency of Canada.

The data contained in this file covers the following topics:

  • Alcohol use
  • Anthropometry
  • Cardiovascular health and fitness
  • Chronic conditions
  • General health
  • Lung function
  • Medication use
  • Musculoskeletal fitness
  • Nutrition
  • Oral Health
  • Physical activity
  • Pregnancy
  • Sexual health
  • Sleep
  • Smoking
  • Sun exposure

8.1.2 Wave 2: Master file

This file contains all of the data from wave 1 master file, as well as the first group of laboratory variables. These variables contain laboratory data on cardiovascular health, chemistry panel, diabetes, general health, infection markers, kidney health and nutritional status.

8.1.3 Wave 2: Fasted sub-sample file

This was the first of the sub-sample files to be released CHMS. This file contains data for a subset of the CHMS respondents; those who had fasted for a minimum of 10 hours. The file contains the following variables:

  • Apolipoprotein A1
  • Apolipoprotein B
  • Low density lipoproteins (LDL)
  • Triglycerides
  • Insulin

Note that this file also contains a weight specific to this sub-population.

8.1.4 Wave 3: Master file

This file created for this release contains all of the data from the wave 1 and wave 2 master files, as well as the laboratory variables concerning environmental contaminants and chemical substances. These variables contain laboratory data on bisphenol A, cotinine, metals, Organophosphate pesticides, Phenoxy herbicides (2,4-D, 2,4 DCP) and Pyrethroid pesticides.

8.1.5 Wave 3: Sub-sample files

Three more sub-sample files were released in wave 3. These files contained data for a subset of the CHMS respondents.

Wave 3: Sub-sample files
Sub-sample File Sample
1) PFCS:
 - Perfluorinated compounds (PFHxS, PFOS, PFOA) 20 to 79 (s)
2) PBDE:
- Organochloride pesticides 20 to 79 (s) (fasting)
 - Polychlorinated biphenyls (PCBs)
 - Polybrominated biphenyls (PBBs)
 - Polybrominated diphenyl ethers (PBDEs)
3) BIHG
- Inorganic mercury - Blood 6 to 79 (s)
(s) = some laboratory tests are only done on a random subgroup of the age range indicated

Note that each of these files contain a weight specific to the sub-population of the file.

8.1.6 Wave 4: Master file

The file created for this release contains all of the data from the wave 1, wave 2 and wave 3 master files, as well as 98 activity monitor derived variables.

8.1.7 Wave 4: Sub-sample file

This file contains data for a subset of the CHMS respondents; those who wore their activity monitor for a minimum of 4 days. The file contains the 98 activity monitor derived variables. The file also contains a weight specific to this sub-population.

8.1.8 Supplementary Data release: Master file

The file created for this release contains all of the data from the wave 1, wave 2 and wave 3 master files with the following changes:

  • The medication data has been removed and placed on a separate file.
  • The 2,4,D data has been updated.

8.1.9 Supplementary Data release: Medication File

In an effort to make the medication data collected during the CHMS household interview and clinic visit easier to work with, a separate database containing all medication responses was created.  This database contains information for all respondents and so uses the same weight as the Wave 1 master file – WGT_FULL.

During the household interview, respondents were asked to report any prescription medication, over-the-counter medication and health products or herbal remedies that they took during the previous month. The interviewer was able to capture information for up to 15 prescription medications, 15 over-the-counter medications, and 15 health products or herbal remedies, for a total of 45 possible entries.

During the clinic visit the continued use of each medication, over-the-counter product and health product or herbal remedy reported at the household was confirmed. Respondents then had an opportunity to add up to five new prescription medications, five new over-the-counter products, and five new health products or herbal remedies that they started to take after the household interview had been completed.

Using this information a series of derived variables was created to indicate where the products were reported, how many total products were reported, and when the products were last taken by product type (prescription medications, over-the-counter products or health products or herbal remedies).  In addition, both ATC and AHFS codes were assigned for each reported medication; a second AHFS code was added when applicable.

Variable naming convention

As per the general rules for the CHMS variable naming convention, the medication database variable names are limited to 8 characters and each character of the variable name contains information about the data contained in the variable.

Positions 1-3:

  • “MED” or “MHR”: collected or derived variables from the household and/or clinic interviews
  • “ATC”: Anatomical Therapeutic Chemical (ATC) classification variables
  • “AHF”: American Hospital Formulary Service (AHFS) classification variables

Position 4: Identifies whether the variable was collected during the household or clinic interview (“_”) or was later derived (“D”).

Position 5: Identifies the medication category:

  • “1”: prescription medication
  • “2”: over-the-counter medication
  • “3”: health product or herbal remedy

Positions 6-7: Identifies the list number of the medication:

  • “01” to “15”: Medications collected during the household interview which were then confirmed during the clinic visit
  • “31” to 35”: Additional medications collected during the clinic visit

Description of key variables

Note: The variables are described below, using an “X” in position 5 of the variable name as the same logic applies for each medication category (prescription medication, over-the-counter medication, and health products or herbal remedy).

The variable MEDDX00A indicates whether or not the respondent took any medication within a given category in the past month. The variable MEDDX00B is the sum of the medications within a given category taken by the respondent during the past month. Both MEDDX00A and MEDDX00B are derived from information collected during both the household interview and the clinic visit. For more information, refer the Derived Variable Documentation.

It should be noted that although a maximum of 20 medications were captured (15 from the household and 5 from the clinic) for each medication category, the value for MEDDX00B represents the actual number of medications being taken by the respondent within a given category, and therefore may exceed a value of 20. Due to the limitations of the data capture application, details are only available for the first 20 medications reported. For example, if a respondent indicated taking 17 different prescription medications in the last month at the time of the household interview then MEDD100B will equal 17, although details would only have been captured for the first 15 of the 17 prescription medications.

Six additional variables are associated with each of the medications reported within a given category at the household and five additional variables are associated with each new medication reported at the clinic.

MEDDX01A to MEDDX15A and MEDDX31A to MEDDX35A
This variable is derived from the information collected at the clinic during the confirmation of medication-use reported during the household interview. It provides information about whether the respondent was still taking the medication, had stopped taking the medication since the household interview, or had never taken the medication.

ATC_X01A to ATC_X15A and ATC_X31A to ATC_X35A
The ATC code derived from the drug identification number (DIN) collected during the household and/or clinic interview.

AHF_X01A to AHF_X15A and AHF_X31A to AHF_X35A
The first AHFS code derived from the DIN collected during the household and/or clinic interview.
Note: If the DIN was not available for a given medication, the AHF code will appear as “Not Stated” in the database.

AHF_X01B to AHF_X15B and AHF_X31B to AHF_X35B
The second AHFS code derived from the DIN collected during the household and/or clinic interview (if applicable).
Note: If the DIN was not available for a given medication, the AHF code will appear as “Not Stated” in the database.

MED_X01B to MED_X15B
This information was collected at the household and indicates the time the respondent last took each medication from the time of the household interview.
Note: This variable is suggested for use during analysis if attempting to relate medication use to one or more other variables from the household interview.

MHR_X01B to MHR_X15B and MHRDX31B to MHRDX35B
These variables are collected at the clinic and indicate the last time the respondent took each medication from the time of the clinic interview.
Note: This variable is suggested for use during analysis if attempting to relate medication use to one or more other variables from the clinic visit.

8.1.10 Supplementary Data release: Sub-sample files

Two more sub-sample files were released. These files contained data for a subset of the CHMS respondents.

Supplementary release: Sub-sample files
Sub-sample File Sample
1) Phthalates:
 - Phthalates 6 to 49
2) Tobacco:
- Nicotine 12 to 79 (s)
 - Nicotine metabolites
 - NNAL (4-(methylnitrosoamino)-1-(3-pyridyl)-1-butanol)
(s) = some laboratory tests are only done on a random subgroup of the age range indicated

Note that each these files contain a weight specific to the sub-population of the file.

8.2 Key variables for linking data files

As a result of the large number of files disseminated for cycle 1, there is a requirement to be able to link to these files in order to have access to a larger pool of information. This also applies to the sub-sample files.

In order to facilitate the linking of two or more files, a variable that uniquely identifies each respondent on each file is required. For the CHMS, the variable to be used is called CLINICID. With this variable, data users are able to join the data from any sub-sample file to the master file for a particular respondent.

8.3 Key variables and definitions

Other variables which may be particularly useful for data users are listed below:

Variables
CLC_AGE Respondent's age at the time of the mobile examination centre visit
CLC_SEX Gender of Respondent
DHH_MS Marital Status of Respondent
EDUDR04 Highest level of education - respondent, 4 levels
EDUDR10 Highest level of education - respondent, 10 levels - (D)
WGT_FULL Weight for the full sample file and the medication file
WGT_FAST Weight for the fasted sub-sample file
WGT_PFCS Weight for the PFCS sub-sample file
WGT_PBDE Weight for the PBDE sub-sample file
WGT_BIHG Weight for the BIHG sub-sample file
WGT_ACMO Weight for the Activity Monitor sub-sample file
WGT_PHTH Weight for the Phthalate sub-sample file
WGT_SMOK Weight for the Tobacco sub-sample file

For information regarding the actual questions asked of the respondents, the household and clinic questionnaires are attached to this document (appendix 6). A record layout of all of the variables on the files is also attached to this document (appendix 7). Data dictionaries containing descriptions and characteristics of all of the released variables are available upon request. Each file released will have a separate dictionary.

9. Weighting

In order for estimates produced from survey data to be representative of the population covered and not merely of the sample itself, users must incorporate weighting factors (survey weights) into their calculations. A survey weight is assigned to each person included in the final sample, that is, in the sample of persons who responded to the entire survey. This weight corresponds to the number of people represented by the respondent in the population as a whole.

As described in chapter 5 (Sample Design), the Canadian Health Measures Survey (CHMS) uses two sampling frames for selecting its sample: an area frame of geographic units (clusters) for constructing and selecting collection sites, and an area frame of dwellings within each site.

In accordance with the weighting strategy, the selection weights for collection sites are multiplied by the selection weights for dwellings (households), adjusted for non-response. Following the conversion of household weights into person weights, the latter are adjusted for non-response at the interview stage and the mobile examination (MEC) stage, and with several other adjustments, this weight becomes the final person weight.

9.1 Selection weights for collection sites

The first step is to calculate the selection weight for each collection site. For each site, this weight is calculated as follows within each of the standard regional boundaries8 (SRB):

Selection weight of a collection site within a given SRB9 =

Formula 1

There is no adjustment for non-response at the level of the collection sites, since all sites participated in the survey.

9.2 Selection weights for dwellings

For each collection site selected, a list of all dwellings was obtained from the 2006 Census. These dwellings were stratified into six groups corresponding to the five age group strata and one other strata, using household composition as specified in the section 5.3.2 (Dwelling sampling). The sample of dwellings was allocated among these strata.

For a given dwelling, the selection weight is equal to the inverse of the probability of selection of the dwelling within the stratum to which it belongs.

This weight is then multiplied by the collection site selection weight.

9.3 Removal of out-of-scope units

Among all the dwellings sampled, a proportion are identified during collection as being outside the scope of the survey. Examples of out-of-scope cases for the CHMS are demolished dwellings; dwellings under construction; vacant, seasonal or secondary dwellings; institutions; and dwellings in which all household members are under 6 or over 79 years of age or are full-time members of the Canadian Forces. These dwellings are simply removed from the sample, leaving only dwellings in the scope of the survey. The dwellings that remain in the sample retain the same weight as at the previous stage.

9.4 Household non-response

During collection, a proportion of the households sampled inevitably resulted in a non-response. This usually occurs when the household refuses to participate in the survey, provides unusable data or cannot be reached to conduct the interview. The weight of non-respondent households is redistributed to respondents within homogeneous response groups (HRGs). In order to create these HRGs, the score method based on logistic regression is used to determine the response probability, and then these probabilities are used to divide the sample into groups with similar response properties. Since the information available for non-respondent dwellings (households) is limited, the regression model includes a few variables from the 2006 Census such as dwelling type, as well as geographic information and paradata, which includes the number of weeks between the first and last contact. An adjustment factor was therefore calculated within each HRG as follows:

Formula 2

The weight of respondent households is multiplied by this adjustment factor to produce the adjusted household weight. Non-respondent households are eliminated from the weighting process starting at this point.

9.5 Creation of the person weight

Since the final sampling unit for the CHMS is the person, the adjusted household weight up to this point must be converted into a person weight. This is obtained by multiplying the adjusted household weight by the inverse of the probability of selection of the person selected in the household. It should be kept in mind that the probability of a person being selected changes depending on the number of persons in the household and their ages (see section 5.3.3, Sample Design for more details).

9.6 Non-response at the questionnaire level

The CHMS has a three-stage collection process. First, the interviewer obtains the complete list of persons living in the household, then he or she interviews the person(s) selected in the household, and finally, the selected person or persons report to the CHMS mobile examination centre.

In some cases, interviewers succeed in completing only the first step, either because they cannot contact the person(s) selected, or because the person or persons selected refuse to be interviewed. Such cases are defined as non-responses at the questionnaire level, and an adjustment factor must be applied to the weights of respondent persons to compensate for this non-response. Just as for non-response at the dwelling (household) level, the adjustment is applied within classes defined according to the characteristics available for respondents and non-respondents. All the characteristics collected when the members of the household are listed, such as the number of persons in the household, in addition to geographic information and paradata, were in fact available to create these classes. The "score" method is used to define the classes. An adjustment factor is calculated within each class, as follows:

Formula 3

Thus, the weight of respondent persons is multiplied by this adjustment factor. Persons not responding to the questionnaires are eliminated from weighting starting at this point.

9.7 Non-response at the MEC level

Respondents to the questionnaire are then invited to go to the CHMS mobile examination centre for physical measurements. In some cases, people refuse to participate or do not keep their appointment at the mobile examination centre. Such cases are defined as non-responses at the MEC level, and to compensate for this non-response, an adjustment factor must be applied to the weights of the clinic participants. Just as for non-response at the dwelling (household) and questionnare levels, the adjustment is applied within classes defined on the basis of characteristics available for respondents and non-respondents. All the characteristics collected on the questionnaire during the interview (such as income class and whether or not the respondent is employed), in addition to geographic information and paradata, were made available to create these classes. The "score" method is used to define the classes. An adjustment factor is calculated within each class as follows:

Formula 4

The weights of the persons participating in the clinic were accordingly multiplied by this adjustment factor. Persons who did not report to the MEC are eliminated.

9.8 Winsorization

Note that following a series of adjustments applied to the weights, it is possible that some units will have weights that stand out from the other weights to the point of being aberrant. Some respondents may actually represent an abnormally high proportion in their group and therefore strongly influence both the estimates and the variance. To avoid this situation, a respondent weight that contributes aberrantly to the age-sex group is adjusted downward using a method known as "winsorization."

9.9 Calibration

The last step required to obtain the final CHMS weight is calibration. This procedure is applied to ensure that the sum of the final weights corresponds to the estimates of populations defined at the scale of the five Canadian geographic regions, for each of the 10 age-sex groups of interest, namely the five age groups 6 to 11, 12 to 19, 20 to 39, 40 to 59 and 60 to 79 for each sex.

The population estimates are based on the most recent census counts, as well as on counts of births, deaths, immigration and emigration since then. The calibration was carried out using the mean of the monthly estimates (covering the survey period) for each cross-tabulation of standard regional boundaries and age-sex groups. After calibration, the weight adjustment was obtained. The resulting weight is the final CHMS weight found in the data file bearing the variable name WGT_FULL.

9.10 Fasted sub-sample

The steps described in sections 9.1 to 9.4 were carried out on the fasted sub-sample. At the person weight creation step (section 9.5) the fasted sub-sample flag assigned to the dwellings (see section 5.3.2.1) was attributed to the selected person(s). Before adjusting for non-response at the questionnaire level (section 9.6), the person weights of those selected to be fasted were adjusted to incorporate the fasted sub-sample sampling weights. An adjustment factor was derived by collection site and stratum as follows:

Formula 13

The weights of the persons selected to be fasted were accordingly multiplied by this adjustment factor. Persons who were not selected to be fasted are eliminated.

Adjustment for non-response at the questionnaire level and the MEC level (sections 9.6 and 9.7) were carried out on the fasted sub-sample.

An additional step was required to adjust for persons who were selected to be fasted, but had not fasted or did not provide blood. Such cases are defined as non-responses to the fasted sub-sample, and to compensate for this non-response, an adjustment factor was applied to the weights of the persons who fasted and gave blood. Just as for non-response at the collection site, dwelling (household), questionnaire and clinic levels, the adjustment is applied within classes defined on the basis of characteristics available for respondents and non-respondents. All the characteristics collected on the questionnaire during the household interview and measures taken at the clinic, in addition to geographic information and paradata, were made available to create these classes. The “score” method is used to define the classes. An adjustment factor is calculated within each class as follows:

Formula 14

The weights of the persons who were fasted and provided blood were accordingly multiplied by this adjustment factor. Persons who were not fasted or did not provide blood were eliminated.

The final two steps, winsorization and calibration (see sections 9.8 and 9.8) were then applied to the fasted sub-sample. After calibration, the weight adjustment was obtained. The resulting weight is the final CHMS weight found in the fasted sub-sample data file bearing the variable name WGT_FAST.

9.11 Polybrominated diphenyl ether (PBDE) / Polychlorinated biphenyls (PCB) sub-sample

The steps described in section 9.10 (fasted sub-sample) were carried out.  Only respondents aged 20 year old and over (at the time of the household interview) from the fasted sub-sample were kept.  The resulting weight is the final CHMS weight found in the PBDE/PCB sub-sample data file bearing the variable name WGT_PBDE.

9.12 Inorganic mercury sub-sample

The steps described in sections 9.1 to 9.4 were carried out on the inorganic mercury sub-sample.  At the person weight creation step (section 9.5) the inorganic mercury flag assigned to the dwellings (see section 5.3.2.3) was attributed to the selected person(s). Before adjusting for non-response at the questionnaire level (section 9.6), the person weights of those selected for the inorganic mercury sub-sample were adjusted to incorporate the inorganic mercury sub-sample sampling weights. An adjustment factor was derived by collection site and stratum as follows: 

Formula 25

The weights of the persons selected for inorganic mercury were accordingly multiplied by this adjustment factor. Persons who were not selected for inorganic mercury are eliminated.

Adjustment for non-response at the questionnaire level and the MEC level (section 9.6 and 9.7) were carried out on the inorganic mercury sub-sample. 

An additional step was required to adjust for persons who were selected for inorganic mercury but for whom the measure could not be performed.  Such cases are defined as non-responses to the inorganic mercury sub-sample, and to compensate for this non-response, an adjustment factor was applied to the weights of the persons with a valid inorganic mercury measure. Just as for non-response at the collection site and dwelling (household) levels and clinic, the adjustment is applied within classes defined on the basis of characteristics available for respondents and non-respondents. All the characteristics collected on the questionnaire during the interview and measures taken at the clinic, in addition to geographic information and paradata, were made available to create these classes. The “score” method is used to define the classes. An adjustment factor is calculated within each class as follows:

Formula 26

The weights of the persons who were selected for inorganic mercury who had a valid measure were accordingly multiplied by this adjustment factor. Persons who did not have a valid measure were eliminated.

The final two steps, winsorization and calibration (see sections 9.8 and 9.9) were then applied to the inorganic mercury sub-sample. After calibration, the weight adjustment was obtained. The resulting weight is the final CHMS weightfound in the inorganic mercury sub-sample data file bearing the variable name WGT_BIHG.

9.13 Perfluorinated compounds sub-sample

The steps described in sections 9.1 to 9.4 were carried out on the perfluorinated compounds  sub-sample. At the person weight creation step (section 9.5) the perfluorinated compounds flag assigned to the dwellings (see section 5.3.2.4) was attributed to the selected person(s). Before adjusting for non-response at the questionnaire level (section 9.6), the person weights of those selected for the perfluorinated compounds sub-sample were adjusted to incorporate the perfluorinated compounds sub-sample sampling weights. An adjustment factor was derived by collection site and stratum as follows: 

Formula 27

The weights of the persons selected for perfluorinated compounds were accordingly multiplied by this adjustment factor. Persons who were not selected for perfluorinated compounds are eliminated.

Adjustment for non-response at the questionnaire level and the MEC level (section 9.6 and 9.7) were carried out on the perfluorinated compounds sub-sample. 

An additional step was required to adjust for persons who were selected for perfluorinated compounds for whom the measures could not be performed. Such cases are defined as non-responses to the perfluorinated compounds sub-sample, and to compensate for this non-response, an adjustment factor was applied to the weights of the persons with a valid perfluorinated compounds measure. Just as for non-response at the collection site and dwelling (household) levels and clinic, the adjustment is applied within classes defined on the basis of characteristics available for respondents and non-respondents. All the characteristics collected on the questionnaire during the interview and measures taken at the clinic, in addition to geographic information and paradata, were made available to create these classes. The “score” method is used to define the classes. An adjustment factor is calculated within each class as follows:

Formula 28

The weights of the persons who were selected for perfluorinated compounds who had a valid measure were accordingly multiplied by this adjustment factor. Persons who did not have a valid measure were eliminated.

The final two steps, winsorization and calibration (see sections 9.8 and 9.9) were then applied to the perfluorinated compounds sub-sample. After calibration, the weight adjustment was obtained. The resulting weight is the final CHMS weightfound in the perfluorinated compounds sub-sample data file bearing the variable name WGT_PFCS.

9.14 Activity monitor sub-sample

The steps described in sections 9.1 to 9.7 were carried out. Activity monitors were to be offered to all the clinic participants once their visits at the clinic was completed. However, due to technical problems, not all of them were offered the device. It is therefore necessary to take into account the clinic participants who were not offered to participate in this component of the survey. The weights of the 5,468 respondents for whom an activity monitor was offered were inflated to take into account the weights of the clinic respondents who were not offered one. An adjustment factor was derived by collection site and stratum as follows: 

Formula 47

The weights of the persons offered an activity monitor were accordingly multiplied by this adjustment factor. Persons who were not offered an activity monitor are eliminated.

An additional step was required to adjust for persons who were offered an activity monitor but did not have four days or more of valid entries. Such cases are defined as non-responses to the activity monitor component, and to compensate for this non-response, an adjustment factor was applied to the weights of the persons who had four days or more of valid entries. Just as for non-response at the collection site and dwelling (household) levels and clinic, the adjustment is applied within classes defined on the basis of characteristics available for respondents and non-respondents. All the characteristics collected on the questionnaire during the interview and measures taken at the clinic, in addition to geographic information and paradata, were made available to create these classes. The "score" method is used to define the classes. An adjustment factor is calculated within each class as follows:

Formula 48

The weights of the persons who have valid entries for four days or more on their activity monitor were accordingly multiplied by this adjustment factor. Persons who had less than four days of valid entries were eliminated.

The final two steps, winsorization and calibration (see sections 9.8 and 9.9) were then applied to the respondents. After calibration, the weight adjustment was obtained. The resulting weight is the final CHMS weight found in the activity monitor data file bearing the variable name WGT_ACMO.

9.15 Phthalates sub-sample

The steps described in sections 9.1 to 9.4 were carried out on the phthalates sub-sample. At the person weight creation step (section 9.5) the phthalates flag assigned to the dwellings (see section 5.3.2.5) was attributed to the selected person(s). Before adjusting for non-response at the questionnaire level (section 9.6), the person weights of those selected for the phthalates sub-sample were adjusted to incorporate the phthalates sub-sample sampling weights. An adjustment factor was derived by collection site and stratum as follows: 

Formula 51

The weights of the persons selected for phthalates were accordingly multiplied by this adjustment factor. Persons who were not selected for phthalates are eliminated.

Adjustment for non-response at the questionnaire level and the MEC level (section 9.6 and 9.9) were carried out on the phthalates sub-sample. 

An additional step was required to adjust for persons who were selected for phthalates for whom the measures could not be performed.    Such cases are defined as non-responses to the phthalates sub-sample, and to compensate for this non-response, an adjustment factor was applied to the weights of the persons with a valid phthalates measure. Just as for non-response at the collection site and dwelling (household) levels and clinic, the adjustment is applied within classes defined on the basis of characteristics available for respondents and non-respondents. All the characteristics collected on the questionnaire during the interview and measures taken at the clinic, in addition to geographic information and paradata, were made available to create these classes. The “score” method is used to define the classes. An adjustment factor is calculated within each class as follows:

Formula 52

The weights of the persons who were selected for phthalates who had a valid measure were accordingly multiplied by this adjustment factor. Persons who did not have a valid measure were eliminated.

The final two steps, winsorization and calibration (see sections 9.8 and 9.9) were then applied to the phthalates sub-sample. After calibration, the weight adjustment was obtained. The resulting weight is the final CHMS weightfound in the phthalates sub-sample data file bearing the variable name WGT_PHTH.

9.16 Tobacco sub-sample

The steps described in sections 9.1 to 9.7 were carried out. For the components that were being measured on clinic participants who provided urine and consented to storage of their urine sample for future health studies, an adjustment factor was necessary to compensate for those who did not provide urine or did not consent. Just as for non-response at the collection site and dwelling (household) levels and clinic, the adjustment is applied within classes defined on the basis of characteristics available for respondents and non-respondents. All characteristics collected on the questionnaire during the interview and measures taken at the clinic, in addition to geographic information and paradata, were made available to create these classes. The “score” method is used to define the classes. An adjustment factor is calculated within each class as follows:

Formula 53

The weights of persons who provided urine and consented to future studies were accordingly multiplied by this adjustment factor.  Persons who did not provide urine or did not consent to storage of their urine for future studies were eliminated.

Each clinic participant aged 12 to 79 was assigned to a stratum defined by an age group  (12 to 19, 20 to 39, 40 to 59 and 60 to 79) and a smoker status (smoker, non-smoker exposed to smoke and non-smoker non-exposed to smoke). To achieve the sample size of approximately 2,500 for the nicotine subsample, a sample has been selected among these participants.  Some respondents were excluded because there was not enough urine left for analysis, mostly because their urine was used to perform other studies. These exclusions are considered random.  To compensate for these exclusions and to factor in the nicotine sub-sample weights, an adjustment factor must be applied to the weights of the participants whose urine was analysed for the nicotine study.  An ajustment factor is calculated within each of the age group by smoker status stratum as follow:

Formula 51

The weights of the persons 12 to 79 on whom nicotine analysis was performed  were accordingly multiplied by this adjustment factor. Persons on whom nicotine analysis was not performed are eliminated.

The final two steps, winsorization and calibration (see sections 9.8 and 9.9) were then applied to the tobacco sub-sample. After calibration, the weight adjustment was obtained. The resulting weight is the final CHMS weightfound in the nicotine sub-sample data file bearing the variable name WGT_SMOK.

10. Data quality

10.1 Response rate

In all, 8,772 of the dwellings selected in the Canadian Health Measures Survey (CHMS) were within the scope of the survey10. Of these dwellings, 6,106 agreed to give the composition of the household, for a household response rate of 69.6%. From these respondent households, 7,483 persons were selected (one or two persons per household) to participate in the survey, of whom 6,604 agreed to respond to the questionnaire, for a response rate of 88.3%. Of these persons, 5,604 then reported to the CHMS mobile examination centre for physical measurements, for a response rate of 84.9%. At the Canadian scale, a combined response rate of 51.7% was observed for cycle 1 of the CHMS. It is important to note that the combined response rate is not obtained by multiplying the response rates by the person and household scales (at the questionnaire level and the clinic level), since two persons were selected in some households. Appendix 9a shows the combined response rates and the relevant information for calculating them for each site.

Below is a description of how the different components of the equation must be manipulated to calculate combined response rates correctly.

Response rate at the household scale

Formula 5

Response rate at the person scale among households where one person was selected ( questionnaire)

Formula 6

Response rate at the person scale among households where two persons were selected (questionnaire)

Fomula 7

Response rate at the person scale among households where one person was selected (clinic)

Formula 8

Response rate at the person scale among households where two persons were selected ( clinic)

Formula 9

Ratio for households where one person was selected

Formula 10

Note: The "# of respondent households among those where one person was selected" is neither more nor less than the number of persons selected among households where one person was selected in appendix 9a.

Ratio for households where two persons were selected (area frame)

Formula 11

Note: It is important to note that the "# of respondent households among those where two persons were selected" is obtained by dividing by 2 the number of persons selected among household where two persons were selected in appendix 9a.

Once all the above components have been calculated, a user can calculate the combined response rate using the following formula.

Combined response rate

COMBRR = HR * [ (RR1 * PQ1 * PC1) + ( RR2 * PQ2 * PC2) ]

Below is an example of calculating the response rate at the household scale for Canada using the information provided in the appendix 9a.

Formula 12

 

Now here is an example of calculating the combined response rate for Canada using the information provided in appendix 9a.

HR = 6,106 / 8,772 = 0.696

PQ1 = 4,158 / 4,734 = 0.878

PC1 = 3,463 / 4,158 = 0.833

PQ2 = 2,446 / 2,744 = 0.891

PC2 = 2,141 / 2,446 = 0.875

RR1 = 4,734 / 6,106 = 0.775

RR2 = 2,744 ÷ 2 / 6,106 = 0.225

Combined response rate = 0.696 * [ (0.775 * 0.878 * 0.833) + ( 0.225 * 0.891 * 0.875) ]

 = 0.517

 = 51.7%

10.1.1 Blood draw and Urine response rate

Although the file with the laboratory data includes all clinic participants, some laboratory analysis could not be performed because the respondents did not or could not provide blood or urine. Of the 5,604 participants who reported to the CHMS mobile examination centre for physical measurements, 5,373 participants provided blood and 5,540 provided urine. The combined response rate for blood draw was 50.0% whereas the combined response rate for urine was 51.2%. It is important to note that the combined response rate is not obtained by multiplying the response rates by the person and household scales, since two persons were selected in some households. Appendix 9b shows the combined response rates and the relevant information for calculating them for each site.

Below is a description of how the different components of the equation must be manipulated to calculate combined response rates correctly. Four additional response rates are required to derive the blood draw and the urine combined response rates:

Response rate at the person scale among households where one person was selected (blood draw)

Formula 15

Response rate at the person scale among households where two persons were selected (blood draw )

Formula 16

Response rate at the person scale among households where one person was selected (urine)

Formula 17

Response rate at the person scale among households where two persons were selected (urine )

Formula 18

Blood draw combined response rate

BCOMBRR = HR * [ (RR1 *PQ1 * PC1 * BC1 ) + ( RR2 * PQ2 * PC2 * BC2 )]

Urine combined response rate

UCOMBRR = HR * [ (RR1 *PQ1 * PC1 * UC1 ) + ( RR2 * PQ2 * PC2 * UC2) ]

where HR, RR1, PQ1, PC1, RR2, PQ2 and PC2 are described in section 10.1.

Now here is an example of calculating the Blood draw combined response rate for Canada using the information provided in Appendices 9 and 9b.

HR = 6,106 / 8,772 = 0.696

PQ1 = 4,158 / 4,734 = 0.878

PC1 = 3,463 / 4,158 = 0.833

PQ2 = 2,446 / 2,744 = 0.891

PC2 = 2,141 / 2,446 = 0.875

RR1 = 4,734 / 6,106 = 0.775

RR2 = (2,722 / 2) / 6,106 = 0.225

BC1 = 3,397 / 3,463 = 0.981

BC2 = 1,976 / 2,141 = 0.923

Blood draw combined response rate =

0.696 * [ (0.775 * 0.878 * 0.833 * 0.981) + ( 0.225 * 0.891 * 0.875 * 0.923) ]

= 0.500

= 50.0%

10.1.2 Fasted sub-sample response rate

From the 6,106 respondent households, 3,948 persons were selected (one or two persons per household) to participate in the fasted sub-sample, of whom 3,483 responded to the questionnaire, for a response rate of 88.2%. Of these persons, 2,969 then reported to the CHMS mobile examination centre for physical measurements, for a response rate of 85.2%. Of these persons, 2,634 were actually fasted and provided blood. At the Canadian scale, a combined response rate of 46.3% was observed. It is important to note that the combined response rate is not obtained by multiplying the response rates by the person and household scales, since two persons were selected in some households. Appendix 9c shows the fasted sub-sample combined response rates and the relevant information for calculating them for each site.

Below is a description of how the different components of the equation must be manipulated to calculate the combined response rate correctly.

Response rate at the person scale among households where one person was selected for the fasted sub-sample ( questionnaire)

Formula 19

Response rate at the person scale among households where two persons were selected for the fasted sub-sample (questionnaire)

Formula 20

Response rate at the person scale among households where one person was selected for the fasted sub-sample (clinic)

Formula 21

Response rate at the person scale among households where two persons were selected for the fasted sub-sample clinic)

Formula 22

Response rate at the person scale among households where one person was selected for the fasted sub-sample (actually fasted and provided blood)

Formula 23

Response rate at the person scale among households where two persons were selected for the fasted sub-sample (actually fasted and provided blood)

Formula 24

Fasted sub-sample combined response rate

FSCOMBRR = HR* [(RR1*FSQ1*FSC1*FSB1) + (RR2*FSQ2* FSC2* FSB2 )]

here HR, RR1 and RR2 are described in section 10.1.

Now here is an example of calculating the Fasted sub-sample combined response rate for Canada using the information provided in Appendices 9a and 9c.

HR = 6,106 / 8,772 = 0.696

PFSQ1 = 2,206 / 2,522 = 0.875

PFSC1 = 1,840 / 2,206 = 0.834

PFSQ2 = 1,277 / 1,426 = 0.896

PFSC2 = 1,129 / 1,277 = 0.884

PRR1 = 4,734 / 6,106 = 0.775

PRR2 = (2,744 / 2) / 6,106 = 0.225

PFSB1 = 1,672 / 1,840 = 0.909

PFSB2 = 962 / 1,129 = 0.852

Fasted sub-sample combined response rate =

0.696 * [ (0.775 * 0.875 * 0.834 * 0.909) + ( 0.225 * 0.896 * 0.884 * 0.852) ]

= 0.463

= 46.3%

10.1.3 Polybrominated diphenyl ether (PBDE) / Polychlorinated biphenyls (PCB) sub-sample response rates

From the 6,106 respondent households, 2,513 persons were select to participate in the PBDE/PCB sub-sample, of whom 2,203 responded to the questionnaire, for a response rate of 87.7%. Of these persons, 1,841 then reported to the CHMS mobile examination centre for physical measurements, for a response rate of 83.6%.  Of these persons, 1,696 were actually fasted and provided blood. At the Canadian scale, a combined response rate of 47.0% was observed. It is important to note that the combined response rate is not necessarily obtained by multiplying the response rates by the person and household scales, since two persons were selected in some households. Appendix 9d shows the PBDE/PCB sub-sample combined response rates and the relevant information for calculating them for each site.

Below is a description of how the different components of the equation must be manipulated to calculate the combined response rate correctly.  

Questionnaire response rate at the person scale for the PBDE/PCB sub-sample among households where one person was selected

Formula 29

Questionnaire response rate at the person scale for the PBDE/PCB sub-sample among households where two persons were selected

Formula 30

Clinic response rate at the person scale for the PBDE/PCB sub-sample among households where one person was selected

Formula 31

Clinic response rate at the person scale for the PBDE/PCB sub-sample among households where two persons were selected

Formula 32

Response rate at the person scale of people who were actually fasted and provided blood for the PBDE/PCB sub-sample  among households where one person was selected

Formula 33

Response rate at the person scale of people who were actually fasted and provided blood for the PBDE/PCB sub-sample among households where two persons were selected

Formula 34

PBDE/PCB sub-sample combined response rate

PBCOMBRR = HR* [(RR1*PBCQ1*PBCC1*PBCB1) + (RR2*PBCQ2* PBCC2* PBCB2 )]

where HR, RR1 and RR2 are described in section 10.1.

Now here is an example of calculating the PBDE/PCB sub-sample combined response rate for Canada using the information provided Appendices 9a and 9d.

HR = 6,106 / 8,772 = 00.696

PPBCQ1 = 1,745 / 1,983 = 0.880

PPBCC1 = 1,438 / 1,745 = 0.824

PPBCQ2 = 458 / 530 = 0.864

PPBCC2 = 403 / 458 = 0.880

PRR1 = 4,734 / 6,106 = 0.775

PRR2 = 2,744/2 / 6,106 = 0.225

PPBCB1 = 1,324 / 1,438 = 0.921

PPBCB2 = 372 / 403 = 0.923

PBDE/PCB sub-sample combined response rate =

 0.696 * [ (0.775 * 0.880 * 0.824 * 0.921) + ( 0.225 * 0.864 * 0.880 * 0.923) ]

= 0.470

= 47.0%

10.1.4 Inorganic mercury sub-sample response rates

From the 6,106 respondent households, 1,592 persons were selected  to participate in the Inorganic mercury sub-sample, of whom 1,414 responded to the questionnaire, for a response rate of 88.8%. Of these persons, 1,191 then reported to the CHMS mobile examination centre for physical measurements, for a response rate of 84.2%.  Of these persons, 1,123 had a measure done. At the Canadian scale, a combined response rate of 49.4% was observed. It is important to note that the combined response rate is not necessarily obtained by multiplying the response rates by the person and household scales, since two persons were selected in some households. Appendix 9e shows the Inorganic mercury sub-sample combined response rates and the relevant information for calculating them for each site.

Below is a description of how the different components of the equation must be manipulated to calculate the combined response rate correctly.  

Questionnaire response rate at the person scale for the Inorganic mercury sub-sample among households where one person was selected

Formula 35

Questionnaire response rate at the person scale for the Inorganic mercury sub-sample among households where two persons were selected

Formula 36

Clinic response rate at the person scale for the Inorganic mercury sub-sample among households where one person was selected

Formula 37

Clinic response rate at the person scale for the Inorganic mercury sub-sample among households where two persons were selected

Formula 38

Response rate at the person scale of people who were actually fasted and provided blood for the Inorganic mercury sub-sample among households where one person was selected

Formula 39

Response rate at the person scale of people who were actually fasted and provided blood for the Inorganic mercury sub-sample among households where two persons were selected

Formula 40

Inorganic mercury sub-sample combined response rate

IMCOMBRR = HR* [(RR1*IMQ1*IMC1*IMB1) + (RR2*IMQ2* IMC2* IMB2)]

where HR, RR1 and RR2 are described in section 10.1.

Now here is an example of calculating the Inorganic mercury sub-sample combined response rate for Canada using the information provided in Appendices 9a and 9e.

HR = 6,106 / 8,772 = 00.696

PIMQ1 = 868 / 981 = 0.885

PIMC1 = 719 / 868 = 0.828

PIMQ2 = 546 / 611 = 0.894

PIMC2 = 472 / 546 = 0.864

PRR1 = 4,734 / 6,106 = 0.775

PRR2 = 2,744/2 / 6,106 = 0.225

PIMB1 = 702 / 719 = 0.976

PIMB2 = 421 / 472 = 0.892

Inorganic mercury sub-sample combined response rate =

0.696 * [ (0.775 * 0.885 * 0.828 * 0.976) + ( 0.225 * 0.894 * 0.864 * 0.892) ]

= 0.494

= 49.4%

10.1.5 Perfluorinated compounds sub-sample response rates

From the 6,106 respondent households, 4,036 persons were selected to participate in the Perfluorinated compounds sub-sample, of whom 3,563 responded to the questionnaire, for a response rate of 88.3%. Of these persons, 2,971 then reported to the CHMS mobile examination centre for physical measurements, for a response rate of 83.4%.  Of these persons, 2,880 had a measure done. At the Canadian scale, a combined response rate of 49.7% was observed. It is important to note that the combined response rate is not necessarily obtained by multiplying the response rates by the person and household scales, since two persons were selected in some households. Appendix 9f shows the Perfluorinated compounds sub-sample combined response rates and the relevant information for calculating them for each site.

Below is a description of how the different components of the equation must be manipulated to calculate the combined response rate correctly.  

Questionnaire response rate at the person scale for the Perfluorinated compounds sub-sample among households where one person was selected

Formula 41

Questionnaire response rate at the person scale for the Perfluorinated compounds sub-sample among households where two persons were selected

Formula 42

Clinic response rate at the person scale for the Perfluorinated compounds  sub-sample among households where one person was selected

Formula 43

Clinic response rate at the person scale for the Perfluorinated compounds sub-sample among households where two persons were selected

Formula 44

Response rate at the person scale of people who were actually fasted and provided blood for the Perfluorinated compounds sub-sample among households where one person was selected

Formula 45

Response rate at the person scale of people who were actually fasted and provided blood for the Perfluorinated compounds sub-sample among households where two persons were selected

Formula 46

Perfluorinated compounds sub-sample combined response rate

PFCCOMBRR = HR* [(RR1*PFCQ1*PFCC1*PFCB1) + (RR2*PFCQ2* PFCC2* PFCB2)]

where HR, RR1 and RR2 are described in section 10.1.

Now here is an example of calculating the Perfluorinated compounds sub-sample combined response rate for Canada using the information provided in Appendices 9a and 9f.

HR = 6,106 / 8,772 = 00.696

PPFCQ1 = 2,798 / 3,167 = 0.883

PPFCC1 = 2,308 / 2,798 = 0.825

PPFCQ2 = 765 / 869 = 0.880

PPFCC2 = 663 / 765 = 0.867

PRR1 = 4,734 / 6,106 = 0.775

PRR2 = 2,744/2 / 6,106 = 0.225

PPFCB1 = 2,242 / 2,308 = 0.971

PPFCB2 = 638 / 663 = 0.962

Perfluorinated compounds sub-sample combined response rate =

0.696 * [ (0.775 * 0.883 * 0.825 * 0.971) + ( 0.225 * 0.880 * 0.867 * 0.962) ]

= 0.497

= 49.7%

10.1.6 Activity monitor response rate

Of the 5,604 participants who reported to the CHMS mobile examination centre for physical measurements, 5,468 participants were offered an activity monitor. Of these persons, 4,441 returned the activity monitor with at least four days of valid entries. The combined response rate for the activity monitor was 41.8%. It is important to note that the combined response rate is not obtained by multiplying the response rates by the person and household scales, since two persons were selected in some households.  Appendix 9g shows the combined response rates and the relevant information for calculating them for each site.

Below is a description of how the different components of the equation must be manipulated to calculate combined response rates correctly. Two additional response rates are required to derive the activity monitor combined response rates:

Response rate at the person scale among households where one person was selected (activity monitor)

AM1= V1 / OF1 = # of participants who returned the activity monitor with at least four days of valid entries among clinic participants where one person was selected / # of participants in the clinic who were offered an activity monitor among households where one person was selected

Response rate at the person scale among households where two persons were selected (activity monitor)

AM2= V2 / OF2 = # of participants who returned the activity monitor with at least four days of valid entries among clinic participants where two persons were selected / # of participants in the clinic who were offered an activity monitor among households where two persons were selected

Activity monitor combined response rate

AMCBRR = HR * [ (RR1 * PQ1 * PC1 * AM1 ) + ( RR2 * PQ2 * PC2 * AM2 )]

where HR, RR1, PQ1, PC1, RR2, PQ2 and PC2 are described in section 10.1.

Now here is an example of calculating the activity monitor combined response rate for Canada using the information provided in Appendices 9a and 9g.

HR = 6,106 / 8,772 = 0.696

PPQ1 = 4,158 / 4,734 = 0.878

PPC1 = 3,463 / 4,158 = 0.833

PPQ2 = 2,446 / 2,744 = 0.891

PPC2 = 2,141 / 2,446 = 0.875

PRR1 = 4,734 / 6,106 = 0.775

PRR2 = (2,744 / 2) / 6,106 = 0.225

PAM1 = 2,709 / 3,372 = 0.803

PAM2 = 1,732 / 2,096 = 0.826

Activity monitor combined response rate =

0.696 * [ (0.775 * 0.878 * 0.833 * 0.803) + ( 0.225 * 0.891 * 0.875 * 0.826) ]

= 0.418

= 41.8%

10.1.7 Phthalates sub-sample response rates

From the 6,106 respondent households, 4,439 persons were selected to participate in the Phthalates sub-sample, of whom 3,902 responded to the questionnaire, for a response rate of 87.9%. Of these persons, 3,310 then reported to the CHMS mobile examination centre for physical measurements, for a response rate of 84.8%.  Of these persons, 3,237 had a measure done. At the Canadian scale, a combined response rate of 50.1% was observed. It is important to note that the combined response rate is not necessarily obtained by multiplying the response rates by the person and household scales, since two persons were selected in some households. Appendix 9h shows the Phthalates sub-sample combined response rates and the relevant information for calculating them for each site.

Below is a description of how the different components of the equation must be manipulated to calculate the combined response rate correctly.

Questionnaire response rate at the person scale for the Phthalates sub-sample among households where one person was selected

PHTQ1 = PHQ1 / PHPS1 = # of respondents to the questionnaire for the Phthalates sub-sample among households where one person was selected / # of persons within the scope of the survey for the Phthalates sub-sample among households where one person was selected

Questionnaire response rate at the person scale for the Phthalates sub-sample among households where two persons were selected

PHTQ2 = PHQ2 / PHPS2 = # of respondents to the questionnaire for the Phthalates sub-sample among households where two persons were selected / # of persons within the scope of the survey for the Phthalates sub-sample among households where two persons were selected

Clinic response rate at the person scale for the Phthalates  sub-sample among households where one person was selected

PHTC1 = PHC1 / PHQ1 = # of participants in the clinic for the Phthalates sub-sample among households where one person was selected / # of respondents to the questionnaire for the Phthalates sub-sample among households where one person was selected

Clinic response rate at the person scale for the Phthalates sub-sample among households where two persons were selected

PHTC2 = PHC2 / PHQ2 = # of participants in the clinic for the Phthalates sub-sample among households where two persons were selected / # of respondents to the questionnaire for the Phthalates sub-sample among households where two persons were selected

Response rate at the person scale of people who were actually fasted and provided blood for the Phthalates sub-sample among households where one person was selected

PHTB1 = PHB1 / PHC1 = # of participants who were fasted and provided blood for the Phthalates sub-sample among clinic participants where one person was selected / of participants in the clinic for the Phthalates sub-sample among households where one person was selected

Response rate at the person scale of people who were actually fasted and provided blood for the Phthalates sub-sample among households where two persons were selected

PHTB2 = PHB2 / PHC2 = # of participants who were fasted and provided blood for the Phthalates sub-sample among clinic participants where two persons were selected / # of participants in the clinic for the Phthalates sub-sample among households where two persons were selected

Phthalates sub-sample combined response rate

PHTCOMBRR = HR* [(RR1*PHTQ1*PHTC1*PHTB1) + (RR2*PHTQ2* PHTC2* PHTB2)]

where HR, RR1 and RR2 are described in section 10.1.

Now here is an example of calculating the Phthalates sub-sample combined response rate for Canada using the information provided in Appendixes 9a and 9h.

HR = 6,106 / 8,772 = 0.696

PHTQ1 = 2,348 / 2,720 = 0.863

PHTC1 = 1,948 / 2,348 = 0.830

PHTQ2 = 1,554 / 1,719 = 0.904

PHTC2 = 1,362 / 1,554 = 0.876

RR1 = 4,734 / 6,106 = 0.775

RR2 = 2,744/2 / 6,106 = 0.225

PHTB1 = 1,921 / 1,948 = 0.986

PHTB2 = 1,316 / 1,362 = 0.966

Phthalates sub-sample combined response rate =

0.696 * [ (0.775 * 0.863 * 0.830 * 0.986) + ( 0.225 * 0.904 * 0.876 * 0.966) ]

= 0.501

= 50.1%

10.1.8 Tobacco sub-sample response rate

Of the 4,530 participants aged 12 to 79 who reported to the CHMS mobile examination centre for physical measurements, 4,356 participants provided urine and consented to storage of their urine sample for future health studies. The tobacco sub-sample was selected among these participants. The combined response rate was 50.1%. It is important to note that the combined response rate is not obtained by multiplying the response rates by the person and household scales, since two persons were selected in some households. Appendix 9i shows the combined response rates and the relevant information for calculating them for each site.

Below is a description of how the different components of the equation must be manipulated to calculate combined response rates correctly. Two additional response rates are required to derive the tobacco sub-sample combined response rates:

Response rate at the person scale among households where one person was selected (tobacco)

NN1= UC / C1 = # of participants in the clinic who provided urine and consented to storage of their urine sample for future health studies in households where one person was selected / # of participants in the clinic among households where one person was selected

Response rate at the person scale among households where two persons were selected (tobacco )

NN2= UC2 / C2 = # of participants in the clinic who provided urine and consented to storage of their urine sample for future health studies in households where two persons were selected / # of participants in the clinic among households where two persons were selected

Tobacco sub-sample combined response rate

NNCBRR = HR * [ (RR1 * PQ1 * PC1 * NN1 ) + ( RR2 * PQ2 * PC2 * NN2 )]

where HR, RR1, PQ1, PC1, RR2, PQ2 and PC2 are described in section 10.1.

Now here is an example of calculating the tobacco sub-sample combined response rate for Canada using the information provided in Appendixes 9a and 9i.

HR = 6,106 / 8,772 = 0.696

PQ1 (12 to 79 only) = 4,156 / 4,732 = 0.878

PC1 (12 to 79 only) = 3,462 / 4,156 = 0.833

PQ2 (12 to 79 only) = 1,200 / 1,373 = 0.874

PC2 (12 to 79 only) = 1,068 / 1,200 = 0.890

RR1 = 4,734 / 6,106 =  0.775

RR2 = 2,744/2 / 6,106 = 0.225

NN1 (12 to 79 only) = 3,330 / 3,462 = 0.962

NN2 (12 to 79 only) = 1,026 / 1,068 = 0.961

Tobacco sub-sample combined response rate =

0.696 * [ (0.775 * 0.878 * 0.833 * 0.962) + ( 0.225 * 0.874 * 0.890 * 0.961) ]

= 0.501

= 50.1%

10.2 Errors in surveys

The survey yields estimates based on the information collected from a sample of persons. Somewhat different estimates might have been obtained if a complete census had been conducted using the same questionnaire, the same interviewers, the same measurement experts, the same supervisors, the same processing methods, etc. as used for the survey. The difference between the estimates based on the sample and those resulting from a complete enumeration conducted in similar conditions is called the sampling error of the estimates.

Errors that are not related to sampling may be made at almost any stage of a survey. Interviewers may have misunderstood the instructions; respondents may have made errors when completing the questionnaire; responses may have been incorrectly captured; measurements may have been made incorrectly; errors may have crept in when the data were processed and totalled. All these are examples of non-sampling errors.

10.2.1 Non-sampling errors

Over a great number of observations, random errors will have little effect on the estimates drawn from the survey. However, errors that occur systematically will contribute to biases in the estimates from the survey. Much time and effort was devoted to reducing non-sampling errors in the survey. Quality assurance measures were applied at each stage of the data collection and processing cycle to control the quality of the data. Further details on the quality assurance procedures for each stage of the survey are provided in the Quality Assurance and Control section.

The effect of non-response on survey results is a major source of non-sampling error in surveys. The scope of non-response varies from partial non-response (where the respondent does not respond to one or more questions) to total non-response. In cycle 1 of the CHMS, there is little partial non-response, since once the questionnaire began, respondents tended to complete it. There was total non-response when the person selected to participate in the survey refused to do so or could not be contacted by the interviewer. In some collection sites, the sample was augmented over the course of the year in order to reach the targeted size. Lastly, cases of total non-response were taken into account during weighting by correcting the weights of persons who responded to the survey in order to compensate for those who did not respond. See chapter 9 (Weighting) for more information on the correction of weighting for non-response.

10.2.2 Sampling errors

Since the estimates from a sampling survey inevitably include sampling errors, good statistical methods require researchers to provide users with some indication of the scope of this error. Measuring the possible scope of sampling errors is based on the standard deviation of the estimates drawn from the survey results. However, owing to the great diversity of estimates that can be drawn from a survey, the standard deviation of an estimate is usually expressed in terms of the estimate that it relates to. The resulting measure, called the coefficient of variation (CV), is obtained by dividing the standard deviation of the estimate by the estimate itself, and it is expressed as a percentage of the estimate.

For example, assume that a person estimates that 20% of Canadians aged 12 to 79 smoke regularly and this estimate has a standard deviation of  0.005. The CV of this estimate is then calculated as follows:

(0.005/0.20) x 100% = 2.5%

Statistics Canada often uses the CV results for data analysis, and it strongly advises users producing estimates based on the data files from cycle 1 of the CHMS to do the same.

Table 10.1 Sampling variability guidelines
Type of Estimate CV (in %) Guidelines
Acceptable 0.0 ≤ CV ≤ 16.6 Estimates can be considered for general unrestricted release. Requires no special notation.
Marginal 16.6 < CV ≤ 33.3 Estimates can be considered for general unrestricted release but should be accompanied by a warning cautioning subsequent users of the high sampling variability associated with the estimates. Such estimates should be identified by the letter E (or in some other similar fashion).
Unacceptable CV > 33.3 Statistics Canada recommends not to release estimates of unacceptable quality. However, if the user chooses to do so then estimates should be flagged with the letter F (or in some other fashion) and the following warning should accompany the estimates: "The user is advised that . . . (specify the data) . . . do not meet Statistics Canada's quality standards for this statistical program. Conclusions based on these data will be unreliable and most likely invalid. These data and any consequent findings should not be published. If the user chooses to publish these data or findings, then this disclaimer must be published with the data."

 

10.3 Quality assurance and control

 

There are many problems that can introduce errors in a direct measures survey. These errors can significantly affect the integrity of survey results. To ensure the success of the Canadian Health Measures Survey (CHMS) in meeting its objectives, quality assurance and quality control measures were implemented in all the processes. Quality assurance (QA) anticipates problems, and therefore consists of those activities that take place before data collection or in improving and refining data collection. Quality control (QC) responds to observed problems and thus consists of those activities that take place during and after data collection. The goal of QA, and QC, is to ensure the reliability and validity of the data and to reduce systematic bias to the lowest possible level.

10.3.1 Training of household interview and mobile examination centre (MEC) Staff

10.3.1.1 Initial training

Training of all staff emphasized the goals and objectives of the survey, survey methodology and quality control guidelines. Training also included questionnaire/application content and functionality, standardization of survey procedures, data transmission, refusal conversion techniques and administrative procedures.

Training involved both formal classroom training and mandatory reading of procedures and training manuals. The core of the position specific training involved hands-on practice with instructors. Experts from various fields related to the survey measures (e.g., blood pressure) and biospecimen collection/processing protocols provided seminar sessions to the appropriate staff and participated in aspects of the hands-on training.

Household interviewers:
A week of training was provided to household interviewers. Household interviewers took part in mock interviews to familiarize themselves with the household questionnaire, to simulate difficult situations and to practice potential non-response situations. They also discussed techniques for dealing with sensitive questions.

Retraining was conducted with household interviewers anytime a change was made with the application, or when clarification was needed on the household questionnaire. Formal and informal training was on-going in order to ensure that proper protocols were followed.

Mobile examination centre staff:
A month of training was provided to MEC staff prior to collection. The administrative staff received specific training on refusal conversion techniques, telephone skills and on the calibration and maintenance of the dental equipment.

The health measures specialists were provided additional training on calibration and maintenance of equipment, health and occupational safety guidelines (including both respondent and staff safety), emergency procedures and media awareness. They also received specific training on Canadian Physical Activity, Fitness and Lifestyle Approach (CPAFLA)3 protocols, blood pressure and heart rate measurement, spirometry and on how to accommodate respondents with disabilities.

The laboratory technologists received supplementary training on blood and urine collection, processing, storage and running of laboratory tests, as well as re-enforcement training on laboratory protocols.

The dentists received specific training on the CHMS dental examination procedure and were calibrated against the World Health Organization gold standard.

The site logistics officer received specific training on how to set-up the trailers for the beginning of collection at each site and how to prepare the trailers for their move to the next collection site once collection was finished. As well, the site logistics officers received training on information technology maintenance and troubleshooting.

10.3.1.2 Dress rehearsal

Before the start of the actual survey, a one month dress rehearsal was done in Ottawa using Statistics Canada, Health Canada and Public Health Agency of Canada employees and their relatives who volunteered. The purpose of the dress rehearsal was to allow both the household interview staff and the MEC staff to practice their skills before beginning collection. The MEC staff had the opportunity to set-up, run and prepare the MEC trailers for transport to another location in the same format as was to be done during the actual survey. This included booking volunteers into the mobile examination centre using the same schedule that the staff was going to use when operating at a site. The dress rehearsal also allowed the MEC staff the opportunity to refine the flow through the MEC and work on other processes that needed testing (e.g., shipping). The dress rehearsal allowed for verification of the accuracy of the documentation (e.g., procedures manuals), and the household interview and MEC staff's understanding of the procedures, processes, and the flows. It also allowed for training/re-training issues to be identified prior to going into the field.

10.3.1.3 Ongoing training – Dry run day

Prior to the start of collection at each site, one day was set aside for community volunteers to participate in a visit to the MEC. These days were referred to as dry runs. The purpose of the dry runs was to perform on-going training for the MEC team. It gave them the opportunity to practice their skills before the beginning of collection at every site, as well as ensure that all the equipment was functioning correctly.

10.3.1.4 Annual retraining

Half way through cycle 1, the household interviewers took part in a debriefing and retraining session. During this session items that were discussed included refusal avoidance and conversion techniques, techniques on dealing with non-response and how to handle sensitive questions.

An eight day annual retraining was attended by MEC staff, during the middle of cycle 1 at head office. These sessions were similar to the initial training and were performed in collaboration with experts in different fields related to the survey but focused on elements that specifically needed retraining.

10.3.2 Household component

10.3.2.1 Monitoring – Household interview

Monitoring of the work performed by the household interviewers was an integral part of the household collection processes. Observations were completed on all interviewers at the beginning of the collection cycle and, thereafter, two to three scheduled observations were done at each site as well as on an ad hoc basis. Debriefing sessions were held in seven of the fifteen sites where factors affecting data quality were discussed.

In addition to monitoring the work of the interviewers, staff from head office performed interview observations to monitor the functionality of the household interviewing system, the respondents' understanding of the household survey content and the usefulness of the communications tools. Observers provided feedback on these items to the content development and communications teams at head office and problems were addressed as required.

10.3.2.2  Household questionnaire response rates

Monitoring the household collection response rates was conducted throughout the cycle by staff at head office preparing collection progress reports. Staff monitored the reasons for non response by age and sex, the number of contact attempts, the distribution of contact attempts by time of day, the refusal rates and refusal conversions attempts and the distribution of the fasting/non-fasting flag to ensure that the target number of respondents per age and sex group would be achieved.

10.3.2.3 Validation of questionnaire responses

At the end of each site notes and remarks made by interviewers within a respondent's case file were reviewed and adjustments to the data were made, when required. In addition, the frequency of answer categories within a question was determined for "other, specify", "don't know", and "refusal". Questions with a high rate of response for these categories were monitored according to expected rates from other Statistics Canada health surveys and investigated if the rate was higher than expected. These data were also monitored between CHMS collection sites to identify site-specific problems.

Validation of questionnaire responses was also performed on questions that are included in other Statistics Canada health survey with similar content, namely cycles 3.1 and 4.1 of the Canadian Community Health Survey.

10.3.3 Mobile examination centre (MEC) component

The following section will provide information concerning the quality assurance and quality control procedures that were put in place and are specific to collection of the physical measures and laboratory data during the visit to the MEC.

10.3.3.1 Equipment selection

The quality of the equipment used for collection was essential to ensure data accuracy and validity. In selecting the appropriate equipment, a combination of consulting, researching, testing, and evaluation was employed. This was done considering industry standards and in conjunction with partners (e.g., Health Canada, Public Health Agency of Canada), experts from other physical measures surveys (e.g., NHANES in the United States) and CHMS advisory committees.

When determining the MEC laboratory equipment needs, many considerations were taken into account such as the size of the equipment (due to space constraints), the cost of the equipment, the accuracy and precision of the testing equipment, as well as the comparability to other international surveys. The reliability of the instrumentation, including frequency of breakdowns, repairs and maintenance, were also examined. Other items considered when selecting the equipment used for data collection include the infrastructure needs (e.g., use of water, energy consumption, waste disposal), the ease of operation and maintenance, training courses included, the availability and timeliness of service throughout the country, the laboratory biosafety guidelines and the test throughput.

10.3.3.2 Protocols and procedures

To ensure consistency between MEC staff on all measurement techniques, several procedures manuals containing detailed protocols for each measure were developed. These protocols were developed in consultation with, and reviewed by experts in each measurement field (when appropriate), ensuring the highest quality and least biased data collection. For standardization purposes, these protocols were covered thoroughly during staff training and scripted within the data capture application. Staff were required to review these protocols periodically during collection so as to keep themselves up to date. When changes to protocols were made all staff members were informed, provided with the updated protocols and re-training was provided if necessary. All changes to protocols were documented (date of update, reason for updating, process that was followed).

An Equipment Verification, Calibration and Maintenance Manual was also developed to ensure that calibration and maintenance of all testing equipment during collection was performed to meet or exceed the established standards. These standards were established by the equipment manufacturers and the experts with whom we consulted for the clinic laboratory standard operating procedures (SOP). This included pre-analytical functions (mixing, aliquoting), testing protocols (e.g., complete blood count (CBC)), non-testing procedures (e.g., specimen storage and shipping), quality control procedures and equipment use, calibration and maintenance.

All three CHMS reference laboratories also followed standard operating procedures that were developed for every test and technique performed in their laboratory. These provided uniform assay protocols that laboratory staff used to ensure similar results and consistent performance.

10.3.3.3 Mobile examination centre (MEC) environment

All efforts were made to ensure measurements were carried out under controlled and standardized conditions and according to specified procedures. Due to the fact that certain measures and equipment were highly sensitive to changes in room temperature (e.g., spirometry, blood pressure, laboratory equipment), every effort was made to keep the MEC at a comfortable and constant room temperature (21°C ± 2°C). The environmental conditions of the MEC testing rooms (temperature, humidity and barometric pressure) were recorded at a minimum once per shift as well as anytime the temperature went outside of the ± 2°C range. In addition, careful monitoring of the conditions within the mobile examination centre laboratory was undertaken to ensure that the collection, analysis, storage and shipment of samples was performed under the appropriate conditions.

10.3.3.4 Adherence to pre-testing guidelines

At the beginning of the visit to the MEC adherence to the pre-testing guidelines (see appendix 1) was verified and documented within the data capture application and adherence rates were assessed at head office. The purpose of these guidelines was to ensure testing standardization, by minimizing the potential that external factors would affect the results of certain tests. Pre-testing standardization was done to enhance the quality of the data collected.

10.3.3.5 Equipment monitoring

Regular verification, calibration and maintenance of all the equipment used for data collection during the CHMS was performed to ensure data accuracy and validity. This testing was performed to meet or exceed the standards established by the equipment manufacturers and/or by experts in the field.

10.3.3.6 Data entry verification

All paper forms such as the respondent verification sheet, the consent form, the PAR-Q as well as all the worksheets from the home visits or MEC visits done on paper, were manually entered and subsequently verified by a manager to ensure data entry accuracy.

10.3.3.7 Spirometry data review

All spirometry tests were reviewed by an external reviewer via a custom application that was developed for the CHMS. The application was designed to reject invalid curves based on American Thoracic Society testing11 criteria and the reviewer's role was to confirm these rejections as well as to identify other ones not flagged by the application.

10.3.3.8 Data validation

Data validation was performed to ensure that the CHMS data were consistent with other similar data sources including other Statistics Canada surveys, as well as international surveys. Data validation was done to compare various physical measures, laboratory measures and the oral health data by site, and to compare self-reported data from the household interview to directly measured data from the MEC visit (e.g., height, weight), by site and overall. The physical measures and oral health data were also compared against data sources that contained directly measured data, such as the Canadian Community Health Survey cycle 2.2 (physical measures only) and the National Health and Nutrition Examination Survey (NHANES) in the United States.

All CBC data received from the mobile examination centre were monitored by comparing the mean values and standard deviations to a normal reference range in order to identify any increased outliers and trends in the QC, findings and respondent results. The laboratory measures analyzed by the reference laboratories were also examined and compared to other surveys such as NHANES.

Prior to the release of cycle 1 data, external data validation was performed by making information available to Health Canada and the Public Health Agency of Canada who informed Statistics Canada of any concerns or anomalies related to data quality.

10.3.3.9 Mobile examination centre (MEC) laboratory

Procedures were put into place to allow for quick detection of errors related to the MEC laboratory CBC analysis. These procedures included internal and external QC, monitoring, and allowed the CHMS to ensure accurate results and data quality for laboratory measures. Aside from weekly review, regular comparisons were made with QC, results obtained by other users of the haematology analyzer employed by the CHMS. In addition, external QC, material from the College of American Pathologists (CAP) and Quality Management Program – Laboratory Service (QMP-LS) were tested according to their respective schedules. The results of these blind QC, samples provided an evaluation of the testing accuracy.

10.3.3.10 Replicate Testing

Replicate samples were collected during dry-run days at the beginning of each site for a variety of laboratory tests, including the complete blood count, and tests analyzed at the reference laboratories (Health Canada only). Approximately 6-8 dry-run replicate samples were performed by splitting the blood and urine samples from the participants into two distinct specimen tubes with different identification numbers (IDs). As the corresponding split sample IDs were unknown to the technician/technologist testing the samples, these “blind QC, samples” were meant to monitor the precision of the assay and poor performance was inferred if the coefficient of variation obtained from the replicate samples is greater than a pre-set criteria. All replicate samples were sent to the reference laboratories along with other respondent samples and were analyzed following the same procedures as respondent samples. Data from the dry-run replicate samples were transmitted as usual along with the other respondent results. The lab section at the head office analysed them and all results outside of the acceptable limit were followed up on with the testing laboratory. Replicates were also done at the MEC on the anthropometry, sit and reach and grip strength components.

10.3.3.11 Proficiency Testing

All CHMS reference laboratories were responsible for having their own quality control programs in place. However, the CHMS also sent reference quality control materials as a form of proficiency testing for the reference laboratories. The CHMS used BioRad control samples with known concentration for all tests included in the CHMS for which reference QC, samples were available. The use of these materials allowed the CHMS to monitor the accuracy of the analytical testing being performed at the reference labs. The CHMS mobile examination centre laboratory sent these BioRad samples to the reference laboratories on a weekly basis during each collection site along with the regular shipments. The test samples were aliquotted into the same type of shipping tubes used for respondent samples and were labelled with unique sample identification numbers so as to blind the laboratories to the process. Testing results were sent back to the CHMS head office and were compared to the reference ranges provided by BioRad. The test results were assessed by head office laboratory staff and feedback was provided to the reference laboratories for review and remedial action, if necessary.

10.3.3.12 Processing and storage of the blood and urine samples

All blood specimens collected in the clinic were centrifuged in the clinic’s laboratory within two hours of collection to preserve the quality and integrity of the specimens. The specimens were stored at the appropriate temperature (e.g., 2-8 oC fridge or -18 oC or colder freezer) and the fridge and freezer temperatures were monitored via readings at each staff shift and by an alarm system at all times. All samples were processed and stored within four hours of collection. Urine samples were refrigerated immediately upon collection and were subsequently processed and stored at the appropriate temperature as soon as possible.

10.3.3.13 Shipping

As described above under Laboratory Measures protocol section 6.5 shipment temperature monitoring ensured that only samples whose integrity remained intact were used for analysis of CHMS measures.

10.3.3.14 Field Blanks

In order to ensure that samples were not being contaminated by the mobile clinic laboratory environment and processes, and that any detected environmental measure was reflective of the respondent’s physical status, the CHMS mobile clinic lab sent field blanks to the Institut national de la santé publique du Québec (INSPQ), the lab responsible for testing the environmental measures. The field blanks contained a blank solution that was tested to be free of any environmental contaminants and these samples were used to mimic the same processes carried out with respondent samples for collection and processing of environmental measures on blood and urine. De-ionized water was used as the blank solution for the baseline testing of environmental measures for all testing on urine and for metals being tested in blood. Similarly, vials of bovine serum were used for field blank collection of the organic components tested on blood. For sites 12-15 only water was used for the field blanks and all samples were sent in triplicate. These blanks were tested and compared to an acceptable upper limit that is three times the limit of detection of each analyte. Results above these limits were reviewed by head office staff and deviations were investigated, in consultation with the analytical lab and other experts and, if necessary, corrective action is taken.

10.3.3.15 Activity Monitor Data Review

A data review process was also developed to clean and process the activity monitor data. The review process was broken down into four distinct steps: Step 1 involved the downloading and saving of respondent data, ensuring that no malfunctioning monitors were returned to the field, and following up with respondents who hadn’t returned the monitor. Step 2 involved stacking of all respondent data into a single SAS file, and dropping non-valid/bad data (such as initialization errors, or spurious data); Step 3 involved accepting only those with at least 1 day of viable wear-time (at least 10hrs of data), and calculating the activity intensity per minute; and Step 4 involved applying reserve codes to missing data and generating the derived variables.

10.3.4 Head Office

10.3.4.1 Correcting for bias

The CHMS experienced several levels of non-response. First, the selected dwelling may refuse to provide the household composition. Second, the person(s) selected amongst the household members may refuse to answer the questionnaire. Third, the person may refuse to participate in the clinic component. Finally, the person may refuse to provide blood and/or urine for the laboratory tests for current or future analysis.

At each level of non-response characteristics available for respondents and non-respondents are used in a logistic regression model to identify variables which explain most non-response. Based on the results of each regression, homogeneous response groups are created. The non-response adjustments are applied within these groups.

The variables which were correlated most with response or non-response were used in the logistic regression models. Just to name a few are region, if the dwelling is detached or not, the collection site, age group, sex, marital status, household size, education and income.

Concerns were expressed by data users that the clinic respondents’ results were biased because it was believed that less healthy people were less likely to go to the clinic. A study was done to compare estimates of some questionnaire variables before and after the clinic non-response adjustment was carried out. Estimates based on all household questionnaire respondents (weighted) were compared to estimates based on clinic respondents (weighted and adjusted for clinic non-response). Several person level variables were examined, including those used in the regression models and others such as stress level, quality of life, frequency of seeing a dental professional, having a regular medical doctor, smoking, alcohol consumption, taking prescription medications in the last month, job status, body mass index class and indicators of health such as cognition, dexterity, emotional problems, hearing problems, disability levels, mobility trouble, pain and vision.  All variables examined above were not significantly different before and after the clinic adjustment. This suggests that clinic respondents, with the clinic non-response adjustment, are similar to household questionnaire respondents.

Another study was done to compare the 20 to 39 year-olds adults living with and without children aged 6 to 11. The ratio of 20 to 39 year-olds living with children is greater in the CHMS sample than it is in the Canadian population. This imbalance is a result of the 2-person selection in households where a child 6 to 11 year-olds is found. When a child 6 to 11 is selected, a second person aged 12 to 79 is selected as well. The second person selected is usually a parent in the 20 to 39 year-olds age range.  As a result, a limited number of 20 to 39 year-olds not living with children aged 6 to 11 are selected. Since the post-stratification step did not differentiate between the two types of 20 to 39 year-olds, a potential bias could have been introduced by the selection method. To evaluate this potential bias, the ratio of 20 to 39 year-olds with and without children aged 6 to 11 was calculated using the 15 sites’ dwelling frame (and household composition). A post-stratification was done using this observed ratio. Estimates were produced using these new weights and then compared to the original estimates. The new estimates were not statistically different from the original ones. The number of 20 to 39 year-olds living with children may be over estimated in CHMS but not high enough to introduce a bias in the overall results.

11. Guidelines for tabulation, analysis and release

This section of the documentation provides guidelines to be applied by data users in tabulating, analyzing, publishing or otherwise releasing any data derived from the survey files.

11.1  Rounding guidelines

In order that estimates for publication or other releases derived from the data files correspond to those produced by Statistics Canada, users are urged to adhere to the following guidelines regarding the rounding of such estimates:

  • Estimates in the main body of a statistical table are to be rounded to the nearest hundred units using the normal rounding technique. In normal rounding, if the first or only digit to be dropped is 0 to 4, the last digit to be retained is not changed. If the first or only digit to be dropped is 5 to 9, the last digit to be retained is raised by one. For example, in normal rounding to the nearest 100, if the last two digits are between 00 and 49, they are changed to 00 and the preceding digit (the hundreds digit) is left unchanged. If the last digits are between 50 and 99 they are changed to 00 and the proceeding digit is incremented by 1;
  • Marginal sub-totals and totals in statistical tables are to be derived from their corresponding unrounded components and then are to be rounded themselves to the nearest 100 units using normal rounding;
  • Averages, proportions, rates and percentages are to be computed from unrounded components (i.e., numerators and/or denominators) and then are to be rounded themselves to one decimal using normal rounding;
  • Sums and differences of aggregates (or ratios) are to be derived from their corresponding unrounded components and then are to be rounded themselves to the nearest 100 units (or the nearest one decimal) using normal rounding;
  • In instances where, due to technical or other limitations, a rounding technique other than normal rounding is used resulting in estimates to be published or otherwise released that differ from corresponding estimates published by Statistics Canada, users are urged to note the reason for such differences in the publication or release document(s);
  • Under no circumstances are unrounded estimates to be published or otherwise released by users. Unrounded estimates imply greater precision than actually exists.

11.2 Sample weighting guidelines for tabulation

The sample design used for this survey is not self-weighted. In other words, the sampling weight is not the same for all the persons included in the sample. Even to produce simple estimates, including ordinary statistical tables, the user must employ the appropriate sampling weight. Otherwise, the estimates calculated on the basis of the master file cannot be considered representative of the population observed, and they will not correspond to those of Statistics Canada.

Users should also keep in mind that because of the treatment reserved for weights, some software packages do not yield estimates that exactly match those of Statistics Canada.

11.3 Precise variances or coefficients of variation

Calculation of a precise variance or coefficient of variation is not an easy matter, since there is no simple mathematical formula that can take into account all aspects of the CHMS sample design and weights. It is therefore necessary to turn to other methods to estimate these measures of precision, such as re-sampling methods. Among these, the bootstrap method is the one recommended for analysing CHMS data.

However, the calculation of coefficients of variation (or any other measure of precision) performed using the bootstrap method requires access to information that is considered confidential and is present only on the master file.

To calculate coefficients of variation, the bootstrap method is recommended. A macro program, called "Bootvar," has been developed to facilitate calculation using the bootstrap method. The Bootvar program is available in SAS and SPSS formats, and it consists of macros for calculating the variances of totals and ratios differences between ratios, and for linear and logistic regressions.

Since geometric means cannot be calculated within BOOTVAR, other statistical packages such SUDAAN should be used. Because SUDAAN and BOOTVAR use different methods in calculating variance, using SUDAAN to replicate tables produced using BOOTVAR (and vice versa) may yield slightly different variance estimations.

11.4  Recommendations for doing analysis with data from Cycle 1 of CHMS

The Canadian Health Measures Survey (CHMS) was designed to provide national baseline prevalence estimates for a variety of health indicators.  Because of cost considerations, 15 collection sites from 5 regional strata were chosen – 1 site from the Atlantic region, 4 sites from the Quebec region, 6 sites from the Ontario region, 2 sites from the Prairies region and 2 sites from the British Columbia region.  Then a sample of individuals of all ages was selected from each chosen site.  This design should yield approximately unbiased national prevalence estimates that would have cv’s of approximately 16.5% for a prevalence of 10% for each of 5 age groups (6-11, 12-19, 20-39, 40-59, and 60-79) by sex. 

While the small number of sampled collection sites can produce baseline prevalence estimates that meet the above criteria, it has the drawback of leaving just 11 “degrees of freedom12” for variance estimation.  Limited degrees of freedom have several consequences for analysis and inference13; in particular:

  • The variability of variance estimates of estimated quantities needs to be taken into account when doing analyses,
  • Estimated covariance matrices of vectors of estimates (such as the vector of estimated coefficients of a model) could be singular or close to singular, thus possibly not invertible14,
  • It may not be possible to calculate some test statistics,
  • The usual asymptotic distributions of many test statistics may not hold when there is only a small number of primary sampling units (PSUs, in this case the collection sites) in the sample, even when the total sample size is large.

Because of the possible consequences of having a small number of PSUs, a researcher is advised to consider the following recommendations when analyzing CHMS data:

  • Produce only national estimates since regional estimates will have even fewer than 11 degrees of freedom because fewer PSUs would be involved in variance estimation.  This still allows the researcher to do analyses of many subpopulations such as a single age group or one sex, since all ages and both sexes are in the sample from each collection site.
  • Avoid fitting models with a large number of coefficients.
  • Use analytical methods that are less impacted by the limited degrees of freedom, or are conservative. In particular, when testing a hypothesis involving a vector of quantities, avoid Wald statistics and their modifications since they have been found to be unstable. Better choices would be Satterthwaite-adjusted statistics or conservative Bonferroni tests.
  • Since bootstrap weights are used for variance estimation with the CHMS, it will likely be necessary  to specify the degrees of freedom in the software being used because often the default degrees of freedom is likely to be incorrect.

12. File Usage

12.1 Use of weight variable

The CHMS is a sample survey, which means that the respondents "represent" many other Canadians not included in the survey. For example, a 1% sample would mean that each CHMS respondent represented 100 other Canadians.  In order that the results of the survey are representative of the population, the CHMS methodologists have created weights. These weights, when applied to the survey results, enable data users to create estimates for the entire population.

Each respondent record on the master file has a unique weight attached to it. In order to produce estimates for a particular characteristic, the data user must sum the weights for each respondent with that characteristic. The total created by that calculation would produce an estimate of that characteristic in the total population.

Because of the small sample size for cycle 1 of the CHMS the results should only be used to produce national estimates. Due to the different number of respondents contained within the various files output for cycle 1, each file produced will contain a different weighting variable. If subsample files are linked to the master file, then the weight stored on the sub-sample file should be used for creating the estimates.

12.2 Environment Canada climate and air quality file

One of the modules included in the CHMS is spirometry, which measures lung function.  As lung function can be affected by the atmosphere, it may be necessary for researchers to adjust for the weather and air quality at the time of the clinic visit when analyzing data from the spirometry module.  To address these needs, a file has been created which contains hourly climate and air quality data for the dates when clinic collection took place at each of the 15 sites.  Data have been obtained from the National Climate Data and Information Archive (www.climate.weatheroffice.gc.ca) and from the National Air Pollution Surveillance Program (http://etc-cte.ec.gc.ca/NAPS/).

The following indicators are on the climate and air quality file:

Air quality: Ozone, nitrogen dioxide, particulate matter (2.5 microns)
Climate: Temperature, barometric pressure, precipitation, relative humidity, humidex, wind speed, wind direction, wind chill

Supporting documentation is available for this file upon request.

12.3 Variable naming convention

The CHMS naming convention follows the same pattern as that used by the Canadian Community Health Survey (CCHS) and, in fact, many Statistics Canada surveys. The variable name is constructed in a way that allows the data users to easily identify the originating section of the survey, the type of variable and the survey question that collected the data. The variable names have also been created in such a way as to identify similar data between different cycles of the CHMS.

Each variable name must adhere to a mandatory requirement, which restricts variable names to a maximum of 8 characters for ease of use by analytical software products. As a result, each character of the variable name contains information about the data contained in the variable.

Generally speaking:

Positions 1 to 3: Section name
Position 4: "_" or Variable type
Position 5  to  8: Question reference

For example: The variable from question 101 of the household Chronic Conditions Section, CCC_101:
Position 1 to 3: CCC chronic conditions section
Position 4: _ underscore ( _ = collected data)
Position 5 to 7: 101 question number

12.3.1 Positions 1 to 3: Module section name

The following values are used for the section name component of the variable name:

Module section name

Subject

Variable

Activity Monitor Derived Variables – Master File AMM
Activity Monitor Derived Variables – Sub-sample file (4+ days) AMS

Alcohol use

ALC

Anthropometric – Measured Height and Weight

HWM

Anthropometric – Eligibility

ANC

Anthropometric – Skin fold Measurements

SFM

Birth information

BIR

Blood and urine laboratory tests

LAB

Blood collection

BDC

Blood pressure

BPM

Breastfeeding information

BRI

Children’s physical activity

CPA

Chronic conditions

CCC

Clinic - General

SITE

Clinic - General

V2

Complete blood count

CBC

Consent

CON

Demographic and household variables

DHH

Dietary fat consumption

DFC

Education

EDU

Exposure to second-hand smoke

ETS

Family medical history

FMH

Fasting status

ATG

General health

GEN

Grains, fruits and vegetables consumption

GFV

Grip strength

GSM

Grip strength – Eligibility

GSC

Grooming product use

GPU

Health utility index

HUI

Height and weight - Reported

HWT

Hepatitis

HEP

Hobbies

HOB

Housing characteristics

HSC

Human papillomavirus vaccine

HPV

Illicit drug use

IDU

Income

INC

Labour force activity

LBF

Maternal breastfeeding

MBF

Meat and fish consumption

MFC

Medication use

AHF

Medication use

ATC

Medication use

MED

Milk and dairy product consumption

MDC

modified Canadian Aerobic Fitness Test (mCAFT)

AFT

modified Canadian Aerobic Fitness Test (mCAFT) – Eligibility

AFC

Oral Health

OHE

Oral Health

OHQ

Oral Health

OHR

Oral Health

OHM

Oral Health – Eligibility

OHC

Partial curl-ups

PCM

Partial curl-up – Eligibility

PCC

Person providing information

PPI

Phlebotomy

BDC

Phlebotomy – Eligibility

PHB

Phlegm

PLM

Physical activity

PAC

Polybrominated biphenyls (PBBs)

PBB

Polybrominated diphenyl ethers (PBDEs)

PBD

Polychlorinated biphenyls (PCBs)

PCB

Pregnancy information

PRG

Pregnancy status

PRS

Report of measurements

RMC

Respondent verification

CLC

Salt consumption

SLT

Screening

ATG

Screening

MHR

Screening

ORS

Screening

PAR

Screening

PHC

Screening

SPQ

Sedentary activities

SAC

Sexual behaviour

SXB

Sit and reach

SRM

Sit and reach – Eligibility

SRC

Sleep

SLP

Smoking

SMK

Socio-demographic characteristics

SDC

Spirometry

SPM

Spirometry – Eligibility

SPC

Strengths and difficulties

SDQ

Sun exposure

SEB

Urine collection

URC

Water and soft drink consumption

WSD

Weight change

WTC

12.3.2 Position 4: Place Holder or Variable Type

_ Collected variable: A variable that appeared directly on the questionnaire

C Coded variable: A variable coded from one or more collected variables (e.g., SIC, NAICS, ATC, Tar)  

D Derived variable: A variable calculated from one or more collected or coded variables

G Grouped variable: Collected, coded, or derived variables collapsed into groups (e.g., age groups)

12.3.3 Positions 6 to 8: Question reference

In general, the last three positions follow the variable numbering used on the questionnaire. The letter "Q" used to represent the word "question" is removed, and all question numbers are presented in a two- digit format. For example, question Q01A in the questionnaire becomes simply 01A, and question Q15 becomes simply 15.

For questions which have more than one response option, the final position in the variable naming sequence is represented by a letter. For this type of question, new variables were created to differentiate between a "yes" or "no" answer for each response option. For example, if Q2 had multiple response options, the new questions would be named Q2A for option 1, Q2B for option 2, Q2C for option 3, etc. If only options 2 and 3 were selected, then Q2A = No, Q2B = Yes, Q2C = Yes and Q2D = No.

12.4  Access to Master file data

Access to the data is provided through the Research Data Centres (RDC). These centres require researchers to submit to Statistics Canada, a research project that will use respondent data from the released files. These projects are accepted based on a set of specific rules. When the project is accepted, the researcher is designated as a "deemed employee" of Statistics Canada for the duration of the research, and given access to the data from designated Statistics Canada sites. For more information, please consult the Statistics Canada webpage:
www.statcan.gc.ca/rdc-cdr/index-eng.htm.

Another means of access to the master file data is to provide to Statistics Canada specifications for tabulations. These tables are programmed and run against the data files by employees of Statistics Canada. This service allows users who do not possess knowledge of tabulation software products or who do not have access to the RDCs, to get custom results. The results are screened for confidentiality and reliability concerns before release.

12.5  Variable Concordance

Variable names found on the master file are different from those that were used to collect the data. The attached household and clinic questionnaires (see appendix 6) show the collection names.  In order to ensure that data users are able to quickly and easily work with either the file or the questionnaires, a concordance table showing the master file variable names with the appropriate collection variable names is attached (see appendix 8).

12.6 Special notes

  • Please note that MEDF1 (a flag on the Canadian Community Health Survey (CCHS) indicating whether a person has taken medication in the past month) is not on the Canadian Health Measures Survey (CHMS) file. Users can find out how many medications a CHMS respondent took by using the variables MED_100B, MED_200B and MED_300B. These variables indicate the number of prescription medications, non-prescription medications, and herbal products and remedies, respectively, which were taken in the past month.

  • Age and sex are collected twice during the survey process for the CHMS, first through the household interview, then again during the clinic component. Because the two appointments could be several days apart, it is possible that a respondent's age could be different on the household and clinic files. Each application uses the age and sex information that was collected as the reference for coverage and skip patterns for sections within that application. For that reason, it is important to use the appropriate age and sex variables for the data being analyzed. Incorrect usage of age and sex variables could lead to errors in analyses, due to respondents whose ages changed between the two appointments. For example, a respondent who is 11 at the time of the household interview and 12 at the time of the mobile examination centre (MEC) visit will be in different age groups depending on the data being analyzed (i.e. 6 to 11 for household analysis and 12 to 19 for clinic analysis)

    For household variables, DHH_AGE and DHH_SEX should be used; for clinic variables, CLC_AGE and CLC_SEX should be used.  If variables from both components are analyzed, use the age and sex variable for the module containing the most important variable of interest.

  • To help give some context to the raw data that was collected at the MEC, normative scales used by analysts for specific types of data have been added to the master file. The norms used for Cycle 1 data collection were agreed upon at the start of collection, and respondents were informed of how they measured against those norms in the final report delivered to them. The norms used throughout Cycle 1 collection do not reflect changes that may have been made between the start of collection in 2007 and the present day. As the raw data is also included on the file, users are free to use norms other than those included on the file.

  • It should be noted that the following laboratory tests had limitations with regards to stability.

    Homocysteine:
    This measure is time and temperature sensitive. MEC protocol required that samples be processed within four hours of collection. Under normal circumstances however, the time from blood draw to aliquotting and storage for this measure was under 1 ½ hours.

    Bilirubin:
    Two thirds of the way through the survey, steps were taken to preserve the integrity of the sample collected for bilirubin analysis. Changes were made to protect the sample from light during collection, processing and storage. A shift in results could be observed.

    Bicarbonate:
    Bicarbonate is time sensitive as levels can decrease over time due to loss of CO2. Ideally, this analyte should be measured within 3 days of collection. Bicarbonate was part of the chemistry panel which was refrigerated and shipped once a week to the reference lab. As some of these samples could consequently be up to eight days old, this time sensitive measure may have been affected.

  • During the household interview, respondents were asked to name all prescription, over the counter and herbal remedies they were taking, to a maximum of 15 per category. At the clinic interview, the respondent was then asked if they were still taking the medication(s) they listed during the household interview, as well as the names of any new ones they started taking since the household interview. A maximum of five additional medications could to be added into each category (prescription, over the counter and herbal). In the case where a respondent indicated more than 5 new medications for a given category, only the first five of those medications were chosen and coded.  

  • Anatomical Therapeutic Chemical (ATC) classification system:
    The Anatomical Therapeutic Chemical (ATC) classification system was developed by the World Health Organization (WHO). It classifies pharmaceutical products according to the organ or system on which they act and their chemical, pharmacological and therapeutic properties. An ATC code was assigned to each medication using the Drug Identification Number (DIN) and Health Canada's ATC coding system. When a medication had more than one indication, the ATC code was decided based on the main indication of the medication. The main indication was determined by Health Canada reviewers using the Product Monograph (a factual document on a drug product that describes the properties, claims, indications, and conditions of use of the drug product). In cases where it was still not clear from the Product Monograph which ATC code to assign Health Canada contacted the ATC group at the WHO Collaborating Centre for Drug Statistics Methodology in Norway for clarification. A medication was not assigned an ATC code if the DIN was missing or if the DIN did not exist in the Health Canada drug database (for example experimental drugs). In these cases the ATC code appears as "not stated" on the file. The classification system is only available in English. For more information on Anatomical Therapeutical Chemical System please refer to: www.whocc.no/atc_ddd_index/.

  • American Hospital Formulary Service (AHFS) classification system:
    The American Hospital Formulary Service (AHFS) classification system is published by the American Society of Health-System Pharmacists to describe the mode of action of pharmaceutical products, including vitamin and mineral supplements. The classification system is only available in English. For more information on the American Hospital Formulary Service (AHFS) classification system please refer to: www.ahfsdruginformation.com/.

  • Tar Value:
    The tar value was provided by Health Canada and was determined as follows:
    • "Five conditioned cigarettes are smoked per port, using an automated 20-port constant volume smoking machine equipped with a CO analyzer, onto a conditioned, pre-weighed glass fiber filter disc (pad). The gas phase is collected in a Vapour Phase (VP) collection bag and then introduced into a Non-Dispersive Infra-Red analyzer (NDIR) and the % CO determined. The pad is then re-weighed and the difference is the Total Particulate Matter (TPM). The pad is extracted with Isopropanol (IPA) containing the internal standards, and the extract analyzed for nicotine and water by gas chromatography. The tar value is determined by subtracting the water and nicotine from the TPM".15
  • Note to data users – phthalate metabolites:
    Canadian Health Measures Survey (CHMS) data on phthalate metabolites have been adjusted to correct a bias introduced by the inaccuracy of the standards used to calibrate the analytical instruments and to allow the comparison of data from one CHMS cycle to the next. The adjustment factors were established based on the difference in accuracy between the standards used in the analysis of the samples and those considered to be accurate. The application of these adjustment factors is currently undergoing peer review.

13. References and end notes

  1. Stratum defined according composition of the household in the 2006 Census.
  2. For the 6 to 11, 12 to 19 and Others strata, the multiplicative factor for the 12 to 19 age group was increased from 3 to 5 during collection to reach the target number of respondents for this age group.
  3. Canadian Society for Exercise Physiology. 2003. Canadian Physical Activity, Fitness and Lifestyle Approach (CPAFLA). 3rd edition. Ottawa.
  4. Ross, W. D. & M.J. Marfell-Jones. 1991."Kinanthropometry" in Physiological Testing of the High-Performance Athlete. 2nd edition. J. D. MacDougall, H. A. Wenger, & H. J. Green, eds., Human Kinetics Books, Champaign, Illinois, pp. 223-308.
  5. Fitness Canada. 1986. Canadian Standard Test of Fitness (CSTF) Operations Manual. 3rd edition. Ottawa.
  6. Campbell, Norm R.C., Joffre Michel R., McKayDonald W. 2005. "Hypertension Surveillance in Canada: Minimum Standards for Assessing Blood Pressure in Surveys." Canadian Journal of Public Health Vol 96, number 3. p. 217 - 220.
  7. Miller M.R., J. Hankinson, V. Brusasco et al. 2005. "Standardization of spirometry." Eur Respir. Vol. 26 p. 319-338.
  8. The five regions are: British Columbia, the Prairies (Alberta, Manitoba and Saskatchewan), Ontario, Quebec and the Atlantic provinces (Newfoundland and Labrador, Prince Edward Island, Nova Scotia and New Brunswick).
  9. The number of sites selected for each SRB is given in Table 5.1 in section 5.3.1 (Sampling of collection sites).
  10. Among the dwellings initially selected, some are not within the scope of the survey. These include, for example, vacant or demolished dwellings, non-residential dwellings or dwellings in which all household members are under 6 or over 79 years of age or are full-time members of the Canadian Forces. These dwellings are identified during collection; otherwise they would have been excluded during the selection process. They are not included when calculating response rates.
  11. American Thoracic Society. 1995. "Standardization of Spirometry 1994 Update." Am J Respir Crit Care Med. Vol. 152, p. 1107-1136.
  12. Degrees of freedom” is being used as a generic term to reflect the amount of information used to estimate variances and covariances.  An approximation often used for the value of “degrees of freedom” is (# of PSUs - # of strata).  For the CHMS, the collection sites (15) are the PSUs.  For the purpose of variance estimation, the one Atlantic region psu is collapsed in with the 4 Quebec region PSUs, thus leaving 4 strata and “degrees of freedom” equal to (15 – 4) = 11.
  13. In particular confidence intervals and tests of hypotheses.
  14. Invertible covariance matrices are needed to perform Wald tests for tests on vectors of parameters.
  15. Health Canada. 1999.  Determination of “Tar”, Nicotine and Carbon Monoxide in Mainstream Tobacco Smoke. Ottawa

Appendix 1 Pre-testing Guidelines

Pre-testing Guidelines for morning appointments

Guidelines to follow

  • Please do not:
    • Eat or drink anything other than water during the 12 hours prior to your clinic appointment—for example, you can’t eat candies, cough lozenges, chewing gum or drink flavoured water during the fasting period
    • Smoke or use other tobacco and nicotine products during the 2 hours prior to your clinic appointment
    • Drink any alcoholic beverages during the 12 hours prior to your clinic appointment
    • Exercise on the day of your clinic appointment (from midnight)
    • Donate blood 2 days prior to your clinic appointment
    • Wear scented products the day of your clinic appointment
       
  • Bring loose fitting clothing (e.g., shorts, sweat pants, short sleeved top), footwear appropriate for exercise (e.g., walking or running shoes) and your health insurance card to your clinic appointment.
     
  • Medication use:
    • Take your medications as usual on the day of your clinic appointment.
    • Please bring with you all medications (prescription or over the counter), herbal remedies or supplements that you began taking since, or did not disclose during, the household interview.
    • If you have a breathing condition (e.g., asthma), please bring your inhaler or medication to your clinic appointment.

Pre-testing Guideline for afternoon/ evening appointments

Guidelines to follow

  • Please do not:
    • Eat or drink anything other than water during the 2 hours prior to your clinic appointment—for example, you can’t eat candies, cough lozenges, chewing gum or drink flavoured water during the fasting period
    • Smoke or use other tobacco and nicotine products during the 2 hours prior to your clinic appointment
    • Drink any alcoholic beverages on the day of your clinic appointment (from midnight)
    • Exercise on the day of your clinic appointment (from midnight)
    • Donate blood 2 days prior to your clinic appointment
    • Wear scented products the day of your clinic appointment
       
  • Bring loose fitting clothing (e.g., shorts, sweat pants, short sleeved top), footwear appropriate for exercise (e.g., walking or running shoes) and your health insurance card to your clinic appointment.
  • Medication use:
    • Take your medications as usual on the day of your clinic appointment.
    • Please bring with you all medications (prescription or over the counter), herbal remedies or supplements that you began taking since, or did not disclose during, the household interview.
    • If you have a breathing condition (e.g., asthma), please bring your inhaler or medication to your clinic appointment.

Appendix 2 

Exclusion Criteria
Measure  

Exclusion Criteria

Hard Coded Staff Decision
Blood Pressure None Test Screen Out
  • Blood pressure cuff too small or too large to fit arm
  • Rashes, gauze dressings, casts, edema, paralysis, tubes, open sores or wounds, withered arms or a-v shunts on both arms
Right Arm Exclusion
  • Rashes, gauze dressings, casts, edema, paralysis, tubes, open sores or wounds, withered arms or a-v shunts on right arm
  • Blood drawn from right arm in the last week
  • Right mastectomy
  • Cast on right arm
  • Right arm amputation
Standing Height None
  • Unable to stand unassisted
  • Acute condition (e.g., cast on leg preventing them from standing up straight, unassisted)
Sitting Height None
  • Unable to sit unassisted
  • Acute condition (e.g., full leg cast)
Weight None
  • Acute condition (e.g., plaster cast)
Waist Circumference
  • Pregnancy > 12 weeks
  • Respondent in wheelchair (if unable to correctly landmark)
  • Unable to stand unassisted
  • Colostomy bag
Hip Circumference
  • Pregnancy > 12 weeks
  • Respondent in wheelchair
  • Unable to stand unassisted
Skinfolds
  • BMI ≥ 30 kg/m2
  • Pregnancy > 12 weeks
Site-specific exclusions :
  • Acute condition (e.g., varicose veins, skin condition)
  • Chronic condition (e.g. respondent in wheelchair, missing limb on right side)
Phlebotomy
  • Chemotherapy within the past 4 weeks
  • Haemophilia
  • Double mastectomy
  • Rashes, gauze dressings, casts, edema, paralysis, tubes, open sores or wounds, withered arms or limbs missing, damaged, sclerosed or occluded veins, allergies to cleansing reagents, burned or scarred tissue, shunt or IV on both arms.
Urine None
  • Mental/physical disability preventing providing a sample
  • Important language barrier preventing proper instruction for collection
Activity Monitor None
  • Respondent in wheelchair
Spirometry
  • Pregnancy (> 27 weeks)
  • Heart attack within the last 3 months
  • Major surgery on chest or abdomen within the last 3 months
  • Acute respiratory condition (e.g., cold, bronchitis, flu, etc.)
  • Respondent with a stoma
  • Important language barrier
  • Respondent taking medication for tuberculosis
  • Difficulty breathing at rest
  • Persistent cough
  • Recent eye surgery (ex: cataract, ≤ 6 weeks)
  • Any other reason (as assessed by the HMS, ex. Cleft pallet)
Grip Strength
  • Positive response(s) to PAR-Q questions 6 and condition is "aneurysm"
  • Positive response(s) to PAR-Q questions 5 or 7 (depending upon probing).
  • Drank alcohol since midnight (depending upon probing of amount)
  • Mentally or physically impaired
  • Acute condition (unable to grip with both hands)
  • Any other reason (as assessed by the HMS)
mCAFT
  • Positive response(s) to PAR-Q questions 1, 2, 3, 6
  • Positive response to PAR-Q question 4 and condition is "During or after exercise" or "At random"
  • Resting BP > 144/94 mmHg* (age>14 )
  • Resting HR > 99 bpm* (age>14)
  • Pregnancy (> 12 weeks)
  • Blood donation in past 24 hours
  • Taking medication for breathing condition (e.g.,. asthma) and did not bring medication with them
  • Age > 69 years
  • Home visit
  • Positive response(s) to PAR-Q questions 4, 5, 7 (depending upon probing).
  • Heart rate or blood pressure altering medications
  • Difficulty breathing at rest
  • Appears ill or complains of fever
  • Persistent cough
  • Lower extremity swelling
  • Mentally/physically impaired
  • Insulin pump
  • Supplemental oxygen
  • Drank alcohol since midnight (depending upon probing of amount)
  • Large meal within 1 hour of appointment start time
  • Any other reason (as assessed by the HMS)
Sit and Reach
  • Pregnancy (> 12 weeks)
  • Age > 69 years
  • Home visit
  • Positive response(s) to PAR-Q questions 5 and 7 (depending upon probing).
  • Colostomy bag
  • Drank alcohol since midnight (depending upon probing of amount)
  • Mentally or physically impaired
  • Acute condition (e.g., upper/lower limb cast)
  • Chronic condition (e.g., lower body paralysis, missing arm)
  • Any other reason (as assessed by the HMS)
Partial Curl-Ups
  • Positive response(s) to PAR-Q questions 1, 2, 3
  • Positive response(s) to PAR-Q questions 6 and condition is "aneurysm"
  • Pregnancy (> 12 weeks)
  • Resting BP > 144/94 mmHg* (age>14)
  • Resting HR > 99 bpm* (age>14)
  • Age > 69 years
  • Home visit
  • Positive response(s) to PAR-Q questions 5 and 7 (depending upon probing).
  • Difficulty breathing at rest
  • Persistent cough
  • Lower extremity swelling
  • Appears ill or complains of fever
  • Colostomy bag
  • Drank alcohol since midnight (depending upon probing of amount)
  • Mentally or physically impaired
  • Acute condition (e.g., upper/lower limb cast)
  • Chronic condition (e.g. lower body paralysis)
  • Any other reason (as assessed by the HMS)
Oral Health (exclusion from probing component only)
  • Haemophilia
  • Chemotherapy within the past 4 weeks
  • Any answer "yes" to one or more questions in the oral health restrictions (OHR) block
  • < 15 yrs of age
  • Acute condition (as assessed by the HMS in consultation with the dentist)

Appendix 3 PAR-Q

PAR-Q & You (A questionnaire for people aged 15 to 69)

Regular physical activity is fun and healthy, and increasingly more people are starting to become more active very day. Being more active is very safe for most people. However, some people should check with their doctor before they start becoming much more physically active.

 

If you are planning to become much more physically active than you are now, start by answering the seven questions in the box below. If you are between the ages of 15 and 69, the PAR-Q will tell you if you should check with your doctor before you start. If you are over 69 years of age, and you are not used to being very active, check with your doctor.

Common sense is your best guide when you answer these questions. Please read the questions carefully and answer each one honestly: check Yes or No.

1. Has your doctor ever said that you have a heart condition and that you should only do physical activity recommended by a doctor?

  • Yes
  • No

2. Do you feel pain in your chest when you do physical activity?

  • Yes
  • No

3. In the past month, have you had chest pain when you were not doing physical activity?

  • Yes
  • No

4. Do you lose your balance because of dizziness or do you ever lose consciousness?

  • Yes
  • No

5. Do you have a bone or joint problem (for example, back, knee or hip) that could be made worse by a change in your physical activity?

  • Yes
  • No

6. Is your doctor currently prescribing drugs (for example, water pills) for your blood pressure or heart condition?

  • Yes
  • No

7. Do you know any other reason you should not do physical activity?

  • Yes
  • No

If you answered Yes to one or more questions
Talk with your doctor by phone or in person before you start becoming physically active or before you have a fitness appraisal. Tell your doctor about the PAR-Q and which questions you answered Yes.

  • You may be able to do any activity you want – as long as you start slowly and build up gradually. Or, you may need to restrict your activities to those which are safe for you. Talk with your doctor about the kinds of activities you wish to participate in and follow his/her advice.

Find out which community programs are safe and helpful for you.

No to all questions
If you answered No honestly to ­all PAR-Q questions, you can be reasonably sure that you can:

  • start becoming much more physically active – begin slowly and build up gradually. This is the safest and easiest way to go.
  • take part in a fitness appraisal – this is an excellent way to determine your basic fitness so that you can plan the best way for you to live actively. It is also highly recommended that you have your blood pressure evaluated. If your reading is over 144/94, talk with your doctor before you can start becoming much more physically active.

Delay becoming more active:

  • if you are not feeling well because of a temporary illness such as a cold or a fever – wait until you feel better; or
  • if you are or may be pregnant – talk to your doctor before you start becoming more active.

Please note:
If your health changes so that you answer Yes to any of the above questions, tell your fitness or health professional. Ask whether you should change your physical activity plan.

Informed use of the PAR-Q:
The Canadian Society for Exercise Physiology, Health Canada, and their agents assume no liability for persons who undertake physical activity, and if in doubt after completing this questionnaire, consult your doctor prior to physical activity.

No changes permitted. You are encourages to photocopy the PAR-Q but only if you use the entire form.

Note:
If the PAR-Q is being given to a person before he or she participates in a physical activity program or a fitness appraisal, this section may be used for legal or administrative purposes. "I have read, understood and completed this questionnaire. Any questions I had were answered to my full satisfaction."

  • Name
  • Signature
  • Date
  • Signature of parent
  • Witness
  • or Guardian (for participants under the age of majority)

Note:
This physical activity clearance is valid for a maximum of 12 months from the date it is completed and becomes invalid if your condition changes so that you would answer Yes to any of the seven questions.

For more information on how the PAR_Q was used by Canadian Health Measures Survey, please contact:
Tel. 1-888-253-1087
Email: chms-ecms@statcan.gc.ca

For other information on the PAR_Q, please contact the:
Canadian Society for Exercise Physiology
202-185 Somerset Street West
Ottawa, ON   K2P 0J2
Tel. 1-877-651-3755
Fax (613) 234-3565
Online: www.csep.ca

Appendix 4 Canadian Health Measure Survey cycle 1 protocols

1.  Anthropometric component

1.1 Standing height

Standing height is an assessment of maximum vertical size. This measure was taken on all respondents ages 6 years and older who were able to stand unassisted. Standing height was measured with a fixed stadiometer with a vertical backboard and a moveable headboard using a procedure based on the Canadian Physical Activity, Fitness and Lifestyle Approach (CPAFLA)1.

1.1.1 Equipment

  • ProScale M150 Digital Stadiometer.

1.1.2 Eligibility

  • All respondents aged 6-79 who are able to stand unassisted.
  • Respondents who were unable to stand unassisted.
  • Respondents who suffered from an acute condition that prevented him/her from completing the measure (e.g., cast on leg preventing the respondent from standing up straight).

1.1.3  Exclusion criteria

  • Respondents who were unable to stand unassisted.

  • Respondents who suffered from an acute condition that prevented him/her from completing the measure (e.g., cast on leg preventing the respondent from standing up straight).

1.1.4 Administering height

Note: If a respondent could not keep his/her head in contact with the stadiometer while the head was in the Frankfort plane position, the Frankfort plane position took precedence over ensuring the rear of the head was in contact with the stadiometer.

  1. The health measurement specialist (HMS) had the respondent remove his/her footwear and move or remove hair ornaments, jewellery, buns and braids from the top of his/her head.

  2. The respondent was instructed to stand erect, arms hanging at the sides with his/her feet together. The respondent was instructed to keep his/her heels, buttocks, back and head in contact with the vertical backboard of the stadiometer. Depending on the overall body shape of the individual, there were times when not all of the points touched. In such cases, it was ensured that the respondent’s trunk was vertical above the waist, and that the arms and shoulders were relaxed. The HMS made sure the body weight was evenly distributed, and that both feet were flat on the floor.

  3. The HMS instructed the respondent to look straight ahead. The respondent’s head was aligned in the Frankfort Plane. The head is considered to be in the Frankfort plane when the horizontal line from the ear canal to the lower border of the orbit of the eye is parallel to the floor and perpendicular to the vertical backboard. If required, the HMS gently tilted the head up or down until proper alignment was achieved with eyes looking straight ahead.

  4. The respondent was instructed to stand as tall as possible, take a deep breath and hold it while the measurement was taken. A deep breath allowed the spine to straighten, yielding a more consistent and reproducible stature measurement.

  5. The head board was positioned firmly on top of the head with sufficient pressure to compress the hair.

  6. The standing height was recorded to the nearest 0.01cm while the breath was being held.

1.2 Sitting height

Sitting height is an assessment of maximum vertical size when the respondent is sitting. It was measured on all respondents ages 6 years and older who were able to sit unassisted. Sitting height was measured with a fixed stadiometer with a vertical backboard and a moveable headboard. Along with standing height, it helps in the assessment of body proportions (e.g., length of the legs relative to the body trunk). Combining stature with sitting height (using a predictive equation) provides an index of maturity status for younger populations. The sitting height was measured following the International Society for the Advancement of Kinanthropometry (ISAK) protocol.2

1.2.1 Equipment

  • ProScale M150 Digital Stadiometer.
  • Standardized bench or block.

1.2.2 Eligibility

  • Respondents aged 6 to 79.

1.2.3 Exclusion criteria

  • Respondents who were unable to sit unassisted.
  • Respondents who suffered from an acute condition preventing them from completing the measure (e.g. full leg cast).

1.2.4 Administering sitting height

Note: If a respondent could not keep his/her head in contact with the stadiometer while the head was in the Frankfort plane position, the Frankfort plane position took precedence over ensuring the rear of the head was in contact with the stadiometer.

  1. The HMS had the respondent move or remove hair ornaments, jewellery, buns and braids from the top of his/her head.

  2. The respondent was instructed to sit on the measuring box with hands resting on his/her thighs and to keep his/her back, shoulders and head in contact with the vertical backboard of the stadiometer. Depending on the overall body shape of the individual, there were times when not all of the points touched. In such cases, it was ensured that respondent’s trunk was vertical above the waist, and that the arms and shoulders were relaxed.

  3. The HMS instructed the respondent to look straight ahead. The respondent’s head was aligned in the Frankfort Plane. The head is considered to be in the Frankfort plane when the horizontal line from the ear canal to the lower border of the orbit of the eye is parallel to the floor and perpendicular to the vertical backboard. If required, the HMS gently tilted the head up or down until proper alignment was achieved with eyes looking straight ahead.

  4. The respondent was instructed to sit as tall as possible, take a deep breath and hold it while the measurement was taken. The HMS ensured that the respondent did not contract the gluteal muscles nor push with the legs.

  5. The head board was positioned firmly on top of the head with sufficient pressure to compress the hair.

  6. The standing height was recorded to the nearest 0.01cm while the breath was being held.

1.3 Weight

The weight was measured in kilograms (kg) using a digital scale and was used to calculate body mass index. The procedure was based on the Canadian Physical Activity, Fitness and Lifestyle Approach (CPAFLA).1

1.3.1 Equipment

  • Mettler Toledo VLC with Panther Plus terminal scale.

1.3.2 Eligibility

  • All respondents aged 6 to 79.

1.3.3 Exclusion criteria

  • Respondent who suffered from an acute condition that prevented him/her from completing the measure (see special considerations section below).

  • Respondent who were wearing a plaster cast.

1.3.4    Administering weight

  • The HMS had the respondent remove his/her footwear, any heavy accessories and empty his/her pockets.

  • The respondent was asked to step on the center of the scale facing the HMS, with his/her hands at the side and looking straight ahead.

  • The weight was recorded to the nearest 0.1kg.

1.3.5    Special considerations

Body weight could be measured with the standard procedure if the individual could support themselves on the scale without assistance. Measurements of body weight did not include the weight of assistive devices (e.g., artificial limbs, leg braces, crutches, etc.), although these were sometimes required in order for the individual to be weighed. In these cases, the assistive device was first placed on the scale and the scale tarred. The individual could then stand on the scale using the assistive device and the weight of the individual was then displayed.

Individuals who were unable to balance independently on the scale could be weighed sitting in a chair. The chair was placed on the scale, the scale was then tarred and the respondent sat in the chair. The weight of the individual was then displayed.

1.4 Waist circumference

The pattern of fat distribution is an important indicator of the health risks of obesity. Central fat (fat on the trunk) distribution, especially abdominal fat, is associated with increased risk of hypertension, type 2 diabetes, hyper-lipidemia, coronary artery disease and premature death. Waist circumference provides an indicator of abdominal fat distribution. The procedure was based on the third edition of the Canadian Physical Activity, Fitness and Lifestyle Approach (CPAFLA)1.

1.4.1 Equipment

  • Gulick tape measure (150cm or 200cm)

1.4.2 Eligibility

  • All respondents aged 6 to 79

1.4.3 Exclusion criteria

  • Pregnant women
  • Respondent in a wheelchair (if cannot correctly landmark)
  • Respondent unable to stand unassisted
  • Colostomy bag

1.4.4 Administering waist circumference

  1. The HMS had the respondent stand erect, in a relaxed manner, with feet shoulder width apart and arms slightly forward (at a 45° angle) with palms facing in. The measure was to be taken directly on the skin.

  2. Both sides of the respondent were landmarked with a washable marker. The location of the first landmark was at the bottom of the rib cage (last floating rib) and the second landmark was at the top of the iliac crest. Both marks were in the mid-axillary line. If needed, the HMS asked the respondent for assistance in locating the landmarks or to confirm the location. The mid-point between these two landmarks was measured and landmarked using the measuring tape.

  3. Standing on the respondent's right side, the HMS placed the measuring tape around the trunk in a horizontal plane at the level marked on the respondent's trunk. A mirror was used to ensure proper level and positioning of tape. If there was a visible difference between the two reference marks, the mark on the right side was used as the guide. The HMS applied sufficient tension to the tape to maintain its position without causing indentation of the skin surface.

  4. Once the measuring tape was in place, The HMS instructed the respondent to place both arms along the side of the body in a relaxed manner.

  5. The respondent was instructed to breathe normally.

  6. The HMS kept his/her eyes at the same level as the measuring tape. The measurement was taken at the end of a normal expiration. The cross-over technique was used, and the measure was read from the bottom of the tape.

  7. The HMS recorded the measurement to the nearest 0.1cm.

1.5 Hip circumference

Hip circumference is the maximal circumference measured at the hips or buttocks region (whichever is larger). It is used to calculate the waist-to-hip ratio (WHR) (waist circumference divided by hip circumference). WHR is a simple method of determining body fat pattern. Although standards for risk vary by age and gender, health risk increases with higher WHR. The protocol for hip circumference was based on the Canadian Standardized Test of Fitness Third Edition3.

1.5.1 Equipment:

  • Gulick tape measure (150cm or 200cm)

1.5.2 Eligibility:

  • All respondents aged 6 to 79

1.5.3 Exclusion criteria:

  • Pregnant women
  • Respondent in a wheelchair
  • Respondent who was unable to stand unassisted

1.5.4 Administering hip circumference

  1. The respondent was asked to wear light clothing. The respondent was instructed to stand erect in a relaxed manner, with feet together and arms slightly forward (at a 45° angle) with palms facing in. If the respondent was not wearing light clothing (e.g., light weight shorts, exercise leggings or lightweight track pants), scrubs were given to ensure minimal clothing interference during the measurement.

  2. The respondent was asked to stand with his/her weight evenly distributed to both feet. The respondent was asked to breathe normally.

  3. The measurement was taken over the clothing. Standing on the respondent's right side, the HMS placed the measuring tape around the hips, at the level of the symphysis pubis and the greatest gluteal protuberance. The HMS used a mirror to ensure proper level and positioning of tape. The measuring tape was held snug but not tight.

  4. Once the tape was in place, the HMS instructed the respondent to relax both arms along the body. The measurement was taken on the respondent's right side. The cross-over technique was used, and the measure was read from the bottom of the tape.

  5. The HMS recorded the measurement to the nearest 0.1cm.

1.6 Skinfold measurement

Skinfold measurements are used to estimate general fatness and the distribution of subcutaneous adipose tissue. The principle behind this technique is that the amount of subcutaneous fat (fat that lies directly beneath the skin) is proportional to the total amount of body fat. Both too much fat and too little fat is associated with increased health risk. The skinfold procedure was based on the Canadian Physical Activity, Fitness and Lifestyle Approach (CPAFLA)1.

1.6.1 Equipment

  • Harpenden skinfold caliper
  • Fine tip washable marker
  • Gulick tape measure (150cm)

1.6.2 Eligibility

  • All respondents aged 6 to 79

1.6.3 Exclusion criteria

  • Pregnant women
  • Respondents with BMI ≥ 30 kg/m2
  • Respondents who had an acute condition that prevents him/her from completing the measure (e.g., varicose veins, skin condition). This resulted in site-specific exclusion only.
  • Respondents who had a chronic condition that prevented him/her from completing the measure (e.g., respondent in a wheelchair which impedes proper landmarking, or missing a limb on the right side of the body). This resulted in site-specific exclusion only.

1.6.4 Administering the skinfolds measurement

Note: If the difference between the first and second measure of a particular skinfold site was found to be greater than 0.4mm, the HMS was prompted by the computer system to take a third measurement of that skinfold site. The computer would then choose, among the three values, the two measurements which most closely matched each other in value and determined the mean of those two measurements. The computer would determine the mean of the three measurements if the measures were of equal distance (e.g. 18.6, 19.4, 19.0mm).

  1. Prior to measuring the skinfolds, the HMS marked each site carefully. The HMS marked both the skinfold site and then the 1cm point from the skinfold landmark to identify where to place the upper edge of the caliper jaws. The marks indicated where the center of the fold would be. All marks and measurements were taken on the right side of the body.

  2. The HMS completed the first set of skinfold measurements at all sites then repeated the procedure to obtain a second measurement at all sites.

  3. It was important that the respondent relaxed the underlying musculature as much as possible during the skinfold measurement.

  4. The HMS completely spread the index finger and the thumb to firmly grasp the fold of skin and underlying subcutaneous adipose tissue between his/her thumb and index finger. The amount grasped depended upon the thickness of the subcutaneous adipose tissue. The HMS grasped enough skin and adipose tissue to form a distinct fold that separated it from the underlying muscle. The HMS ensured that the landmark mark was at the center of the skinfold. The sides of the fold were to be roughly parallel. The skinfold was grasped at the point of the site measurement and gently held with the thumb and forefinger.

  5. The HMS placed the jaws of the caliper at a right angle to the body surface, with the upper edge of the caliper jaws on the 1cm landmark below the point where the skinfold was raised. While maintaining the pressure on the skinfold with his/her fingers, the HMS fully released the trigger of the caliper.

  6. The HMS measured the skinfold thickness to the nearest 0.2mm (nearest even decimal place) while continuing to hold the skinfold in his/her fingers. The HMS read the actual measurement from the caliper once the indicator had stabilized (about 2 seconds after the full pressure of the caliper had been applied to the skin).

  7. The HMS read the skinfold measurement before releasing the fold. The HMS then removed the calipers, released the fold of skin and subcutaneous fat, and recorded the measurement.

1.6.5 Triceps skinfold method

  1. The HMS had the respondent stand with his/her arms relaxed by his/her sides with palms facing the body.

  2. To landmark, the HMS brought the forearm to 90º with the palm facing up.

  3. The HMS palpated the acromion process and the tip of the olecranon process and determined the mid-point between these two locations on the medial aspect of the arm using a tape measure. The mid-point was marked using a washable marker. The mid-point was used as a reference to make a landmark on the midline of the back of the arm. The HMS then placed a second mark on the back of the arm, 1cm below the first mark, to indicate the placement of the upper edge of the caliper jaws.

  4. The HMS had the respondent extend his/her arm down with the palm facing the upper leg.

  5. The skinfold was raised at the midpoint so that the fold ran vertically along the midline of the back of the arm.

  6. The upper edge of the caliper jaw was placed at the 1cm landmark, below the point where the skinfold was raised.

  7. Once the indicator had stabilized, the HMS read the skinfold thickness to the nearest 0.2mm (nearest even decimal place) while continuing to hold the skinfold.

1.6.6 Biceps skinfold method

  1. The HMS had the respondent extend his/her arm at the side with the palm facing forward (supinated).

  2. The HMS marked the upper arm over the biceps at the same level as the mid-point for the triceps.

  3. A second mark was placed 1cm below to indicate the placement of the upper edge of the caliper jaws.

  4. The skinfold was raised at the mid-arm point, so the fold ran vertically along the midline of the front of the arm. The upper edge of the caliper jaws was placed at the 1cm landmark, below the point where the skinfold was raised.

  5. Once the indicator had stabilized, the HMS read the skinfold thickness to the nearest 0.2mm (nearest even decimal place) while continuing to hold the skinfold.

1.6.7 Subscapular skinfold method

  1. The HMS had the respondent stand with his/her back facing them, with shoulders relaxed and arms by the sides.

  2. To landmark, the HMS palpated the inferior angle of the scapula. The HMS placed a mark 1cm below the inferior angle. The HMS placed a second mark 1cm below the skinfold landmark in the direction of the skinfold at an angle of 45° to the spine.

  3. The skinfold ran downward and outward at an angle of 45° to the spine.  The skinfold was to form a line extending diagonally toward the right elbow.

  4. The HMS placed the upper edge of the caliper jaw at the 1cm landmark, below the point where the skinfold was raised.

  5. Once the indicator had stabilized, the HMS read the skinfold thickness to the nearest 0.2 mm (nearest even decimal place) while continuing to hold the skinfold.

1.6.8 Iliac crest skinfold method

  1. The HMS had the respondent stand in a normal erect position with the right arm raised to his/her side (so it was horizontal) with the right hand on the right shoulder. If the respondent was unable to place the right hand on the shoulder, they were to keep the horizontal arm extended.

  2. To landmark, the HMS palpated the crest of the ilium and made a small mark 3cm above the crest at the midline (mid-axillary line) of the body. A second mark was placed 1cm anteriorly from the skinfold landmark in the direction of the skinfold.

  3. The HMS raised the skinfold at the 3cm mark so that the fold ran forward and slightly downward.

  4. The upper edge of the caliper jaws were placed on the 1cm anterior landmark, in the direction of the fold.

  5. Once the indicator had stabilized, the HMS read the skinfold thickness to the nearest 0.2mm (nearest even decimal place) while continuing to hold the skinfold fingers.

1.6.9 Medial calf skinfold method

  1. The HMS had the respondent place his/her unweighted (relaxed) right foot flat on a step so that the knee was at a 90° angle.

  2. To landmark, the HMS used the tape measure to find the maximum calf girth. The HMS placed a mark on the medial aspect of the calf at the maximum girth point. A second mark was placed 1cm below the skinfold landmark.

  3. The HMS raised the skinfold on the medial aspect of the right calf just at the level of the maximum calf girth so that the fold ran vertically along the midline.

  4. The HMS placed the upper edge of the caliper jaws on the 1cm landmark, below the point where the skinfold was raised.

  5. Once the indicator had stabilized, the HMS read the skinfold thickness to the nearest 0.2 mm (nearest even decimal place) while continuing to hold the skinfold.

1.6.10 Special considerations

Although skinfold measurements could virtually always be completed (except when a body part was missing), they may or may not have been appropriate. Skinfold measurements were only made on body parts whose composition was unaffected by disability since some disabilities can increase the difficulty in obtaining reliable skinfold measurements. For example, paralysis makes it difficult to obtain a correct skinfold because of the lack of tone in the underlying muscle. Rolling the skinfold between thumb and forefinger may help to isolate the fat from the muscle layers.

2. Blood pressure component

The respondent's resting heart rate and blood pressure (BP) were measured, following a new protocol created by the CHMS and inspired by the report entitled "Hypertension Surveillance in Canada: Minimum Standards For Assessing Blood Pressure In Surveys" report8. This report was published by an expert committee consisting of members of the Canadian Hypertension Society, the Canadian Coalition for High Blood Pressure Prevention and Control and the Heart and Stroke Foundation of Canada

For the purpose of standardization, all measurements were taken on the right arm, unless specific conditions prohibited the use of the right arm (e.g., right mastectomy), using the automated blood pressure cuff (BpTRU™). The BpTRU™ is designed to measure blood pressure and heart rate using an upper arm cuff. The device automatically inflates and deflates the cuff, and uses the oscillometric technique to calculate systolic and diastolic blood pressure. In the event that the automated cuff was not functioning properly, the HMS performed the measure manually by the auscultation method.

2.1 Equipment

Electronically

  • Automated BP monitor: BpTRU™ BP-300 (with automatic input)
  • Variety of automated BP cuff sizes (child – extra large adult)
  • Foot stool for shorter respondents

Manually (auscultation method)

  • Stethoscope: Littman Classic II SE (adults), Littmanä Classic II pediatric (children)
  • Mercury manometer
  • Variety of manual BP cuff sizes (child – extra large adult)
  • Polar heart rate monitor
  • Foot stool for shorter respondents
  • Stopwatch

2.2 Eligibility

  • All respondents aged 6 to 79

2.3 Exclusion criteria

Test exclusion

  • Presence of the following on both arms: rashes, gauze dressings, casts, oedema, paralysis, tubes, open sores or wounds, withered arms, a-v shunts
  • Blood pressure cuff too small or too large to fit on arm

Right arm exclusion

  • Blood has been drawn from right arm within the last week
  • Presence of the following: rash, gauze dressing, cast, oedema, paralysis, tubes, open sores or wounds, withered arm, a-v shunt
  • Right mastectomy
  • Right arm amputation
  • Cast on right arm

2.4 Administering blood pressure

2.4.1 Electronically

Note: If the respondent's right arm could not be used (refer to the right arm exclusion criteria), then the left arm was used.

  1. The respondent was situated in a quiet, comfortable environment. The respondent sat with his/her right arm supported and resting comfortably at heart level (the location of the heart was taken as the junction of the fourth intercostals space and the lower left sternal border).

  2. The proper cuff size associated with the arm circumference was chosen.

  3. The cuff was wrapped smoothly and snugly around the respondent's bare right arm, centering the bladder over the brachial artery. The lower edge of the cuff was placed 2 to 3cm above the antecubital space (elbow crease). The health measurement specialist (HMS) ensured that the respondent's clothing did not impede the blood flow to the arm (e.g., did not roll up the respondent's sleeve but rather provided a short sleeve shirt).
     
  4. The respondent was asked to rest in the seated position for at least 5 minutes prior to the measurement (with the cuff already on the arm). The respondent was asked to relax and not talk or move around during this 5 minute rest period.

  5. The HMS ensured that the respondent was in the correct seated position, which was as follows:



  6.  
  7.  
  • Feet flat on the floor (for shorter respondents a foot rest was used)
  • Legs/ankles uncrossed
  • Back against the back rest of the chair
  • Right arm resting straight on the table at the level of the heart, with the palm of the hand facing down.



  •  
  •  
  • Before starting the measurement, the respondent were instructed not to move or talk during the test.

  • The blood pressure was determined automatically by the BpTRU™ BP-300 as the average of 5 replicate measurements obtained at 1 minute intervals. (A total of 6 blood pressures were taken, with the first reading excluded from the average calculation).

  • A minimum of 3 readings were required to complete the measurement. If more than 2 errors occurred (e.g., movement artefact), the HMS repeated the series of six measurements.

  • After the series of six measurements was taken, the HMS reviewed the measurements listed on the screen and either accepted or re-did the measurements. There were 3 reasons why the HMS would be prompted to re-do the measurements:
     

a. Less than 3 valid measurements for BP and HR were recorded. A measurement was considered not valid if:

  1. there was a BpTRU™ error
  2. for any trial) systolic BP – diastolic BP was < 20 or > 200

b. If the variability between the measurements was too large

  1. Highest systolic BP – lowest systolic BP > 30
  2. Highest diastolic BP – lowest diastolic BP > 20
  3. Highest HR – lowest HR > 30
     

c. If respondent's mean blood pressure (>144/94 mmHg) and/or heart rate (≥100 bpm) was elevated.
 

  • Once the results of the second set of blood pressure measurements were taken, the HMS decided whether or not a third set of measurements were needed by using the information in table 1.
Table 1 Blood pressure measurement decision table
Outcome of 1st measurement Outcome of 2nd measurement Action
Obtained less than 3 valid measurements or if the variability between measurements was too large Obtained less than 3 valid measurements or the variability was too large. Re-do the measurements a third and last time by auscultation.
The respondent's BP (>144/94 mmHg) and/or heart rate (≥100 bpm ) are elevated. Re-do the measurements a third and last time with the BpTRU™ to confirm.
Obtained at least 3 valid measurements, the variability is within the acceptable range and the BP is considered normal. Accept the measurements and go to the end of the component.
Elevated BP or HR
SBP >144 mmHg
and/or
DBP > 94 mmHg)
and/or
HR ≥100 bpm
BP (>144/94 mmHg) and/or HR (≥100 bpm) are elevated again. Accept the measurements and go to the end of the component. Read the high BP and/or HR message to the respondent.
Obtained less than 3 valid measurements or the variability was too large. Re-do the measurements a third and last time with the BpTRU™ to confirm the first set of results.
Obtained at least 3 valid measurements, the variability is within the acceptable range and mean BP is considered normal. Accept the measurements and go to the end of the component.

2.4.2 Manually (auscultation method)

  1. The respondent was situated in a quiet, comfortable environment. The respondent sat with his/her right arm supported and resting comfortably at heart level (the location of the heart was taken as the junction of the fourth intercostals space and the lower left sternal border).

  2. The HMS assisted the respondent with putting on the heart rate monitor. The strap was adjusted to ensure a strong reading from the heart rate monitor.

  3. The proper blood pressure cuff size associated with the arm circumference was chosen and the brachial artery was land-marked for proper cuff placement.

  4. The cuff was wrapped smoothly and snugly around the respondent's bare right arm, centering the bladder over the brachial artery. The lower edge of the cuff was placed 2 to 3cm above the antecubital space (elbow crease). The HMS ensured that the respondent's clothing did not impede the blood flow to the arm (e.g., did not roll up the respondent's sleeve).
  5. The respondent was asked to remain in the seated position for at least 5 minutes prior to measurement (with the cuff already on his/her arm). The respondent was asked to relax and not talk or move around during the 5 minute rest period.
     
  6. The HMS ensured that the respondent was in the correct seated position, which was as follows:
  • Feet flat on the floor (for shorter respondents a foot rest should be used)
  • Legs/ankles uncrossed
  • Back against the back rest of the chair
  • Right arm resting straight on the table at the level of the heart, with the palm of the hand facing down.



  •  
  •  
  • Before starting the measurement, the respondent was instructed not to move or talk during the test.

  • The maximum inflation level (MIL) was determined. The MIL or palpatory method provided an approximation of the systolic blood pressure to determine the highest level to which the cuff should be inflated when the actual measurement was made. The MIL was determined as follows:



  •  
  •  
  • The respondent was positioned with the right palm upward. The HMS located the radial pulse in the right arm.

  • The HMS inflated the cuff quickly to a pressure of 70 to 80 mmHg. Then they inflated the cuff in increments of 10 mmHg until the radial pulse was no longer palpable (palpated systolic). They continued inflating the cuff in increments of 10 mmHg to a final measure that was 30 mmHg above the pressure where the pulse was last palpated. This number was recorded as the MIL.

  • The cuff was rapidly deflated and the return of the pulse was confirmed.

  • If the HMS was unable to obtain the MIL they waited 1 minute and repeated the process.



  •  
  •  
  • The following procedures were used for seated blood pressure readings:



  •  
  •  

Note: If phase I or V occurred between the millimetre marks on the glass column, then the HMS rounded upward to the nearest digit.
 

  • The HMS placed the stethoscope into his/her ear canals, angled forward to fit snugly.

  • The HMS confirmed that the stethoscope head was in one of the two low-frequency positions. The positions to listen to low frequency sounds were either the open bell or tunable diaphragm using very light skin contact. If the open bell of the stethoscope was used, it was positioned over the brachial artery and held it firmly in place. If the tunable diaphragm was used, it was positioned over the brachial artery and pressed lightly against skin. The HMS ensured that the head made contact with the skin, around its entire circumference, for both positions. The HMS tried to avoid allowing the cuff, tubing, bell or diaphragm to come in contact with each other.

  • The stopwatch was started (to time the intervals between measurements), and the cuff was rapidly and steadily inflated to the MIL.

  • When the MIL was reached, the thumb valve was opened and the cuff was smoothly deflated at a constant rate (about 2 mmHg or one mark per second) while the HMS concurrently listened for Korotkoff sounds.

  • Keeping the manometer at eye level, the HMS watched the top of the mercury column (meniscus) as the pressure in the bladder fell and noted the level of the meniscus when the first repetitive sounds were heard (Phase I) and when they disappeared (Phase V).

  • The cuff was deflated at 2 mmHg per second for at least another 10 mmHg past where the last sounds were heard.

  • The HMS rapidly deflated the cuff and disconnected the manometer tubing between measurements to ensure the cuff deflated completely to zero and had the respondent resting quietly for at least 30 seconds.

  • The HMS entered Phase I (the level of the meniscus on the manometer at the first appearance of repetitive sounds) as the systolic blood pressure reading, and Phase V (the level of the meniscus when the last muffled sound was heard) as the diastolic blood pressure reading.
     
  • The HMS repeated steps "a" to "h" five more times for a total of 6 measurements at 1 minute intervals.

  • After the 6th measurement was entered, the application automatically calculated the average based on predetermined guidelines.

  • The data from all 6 measurements were displayed on the computer screen and the HMS reviewed the measurements and either chose to accept or re-do the measurements based on the same criteria as previously outlined in the procedure for the automated BP measurement.

2.4.2 Manually (auscultation method)

  1. The respondent was situated in a quiet, comfortable environment. The respondent sat with his/her right arm supported and resting comfortably at heart level (the location of the heartwas taken as the junction of the fourth intercostals space and the lower left sternal border).
     
  2. The HMS assisted the respondent with putting on the heart rate monitor. The strap was adjusted to ensure a strong reading from the heart rate monitor.
     
  3. The proper blood pressure cuff size associated with the arm circumference was chosen and the brachial artery was land-marked for proper cuff placement.
     
  4. The cuff was wrapped smoothly and snugly around the respondent’s bare right arm, centering the bladder over the brachial artery. The lower edge of the cuff was placed 2 to 3cm above the antecubital space (elbow crease). The HMS ensured that the respondent’s clothing did not impede the blood flow to the arm (e.g., did not roll up the respondent’s sleeve).

    Note: If the respondent’s right arm could not be used (refer to the right arm exclusion criteria), then the left arm was used.
     
  5. The respondent was asked to remain in the seated position for at least 5 minutes prior to measurement (with the cuff already on his/her arm). The respondent was asked to relax and not talk or move around during the 5 minute rest period.
     
  6. The HMS ensured that the respondent was in the correct seated position, which was as follows:
     
    1. Feet flat on the floor (for shorter respondents a foot rest should be used)
    2. Legs/ankles uncrossed
    3. Back against the back rest of the chair
    4. Right arm resting straight on the table at the level of the heart, with the palm of the hand facing down.
       
  7. Before starting the measurement, the respondent was instructed not to move or talk during the test.
     
  8. The maximum inflation level (MIL) was determined. The MIL or palpatory method provided an approximation of the systolic blood pressure to determine the highest level to which the cuff should be inflated when the actual measurement was made. The MILwasdetermined as follows:
     
    1. The respondent was positioned with the right palm upward. The HMS located the radial pulse in the right arm.
       
    2. The HMS inflated the cuff quickly to a pressure of 70 to 80 mmHg. Then they inflated the cuff in increments of 10 mmHg until the radial pulse was no longer palpable (palpated systolic). They continued inflating the cuff in increments of 10 mmHg to a final measure that was 30 mmHg above the pressure where the pulse was last palpated. This number was recorded as the MIL.
       
    3. The cuff was rapidly deflated and the return of the pulse was confirmed.
       
    4. If the HMS was unable to obtain the MIL they waited 1 minute and repeated the process.
       
  9. The following procedures were used for seated blood pressure readings:
     
    1. The HMS placed the stethoscope into his/her ear canals, angled forward to fit snugly. 
       
    2. The HMS confirmed that the stethoscope head was in one of the two low-frequency positions. The positions to listen to low frequency sounds were either the open bell or tunable diaphragm using very light skin contact. If the open bell of the stethoscope was used, it was positioned over the brachial artery and held it firmly in place. If the tunable diaphragm was used, it was positioned over the brachial artery and pressed lightly against skin. The HMS ensured that the head made contact with the skin, around its entire circumference, for both positions. The HMS tried to avoid allowing the cuff, tubing, bell or diaphragm to come in contact with each other.
       
    3. The stopwatch was started (to time the intervals between measurements), and the cuff was rapidly and steadily inflated to the MIL.
       
    4. When the MIL was reached, the thumb valve was opened and the cuff was smoothly deflated at a constant rate (about 2 mmHg or one mark per second) while the HMS concurrently listened for Korotkoff sounds.
       
    5. Keeping the manometer at eye level, the HMS watched the top of the mercury column (meniscus) as the pressure in the bladder fell and noted the level of the meniscus when the first repetitive sounds were heard (Phase I) and when they disappeared (Phase V).
       
    6. The cuff was deflated at 2 mmHg per second for at least another 10 mmHg past where the last sounds were heard.
       
    7. The HMS rapidly deflated the cuff and disconnected the manometer tubing between measurements to ensure the cuff deflated completely to zero and had the respondent resting quietly for at least 30 seconds.
       
    8. The HMS entered Phase I (the level of the meniscus on the manometer at the first appearance of repetitive sounds) as the systolic blood pressure reading, and Phase V (the level of the meniscus when the last muffled soundwasheard) as the diastolic blood pressure reading.

      Note: If phase I or V occurred between the millimetre marks on the glass column, then the HMS rounded upward to the nearest digit.
       
    9. The HMS repeated steps “a” to “h” five more times for a total of 6 measurements at 1 minute intervals.
       
    10. After the 6th measurement was entered, the application automatically calculated the average based on predetermined guidelines.
       
    11. The data from all 6 measurements were displayed on the computer screen and the HMS reviewed the measurements and either chose to accept or re-do the measurements based on the same criteria as previously outlined in the procedure for the automated BP measurement.

3. Spirometry component

The Spirometry Component consists of two blocks, Spirometry Restriction (SPR) and Spirometry Measurement (SPM). Information related to the spirometry restriction block is included in the clinic questionnaire4.

The main volumes measured are:

  • Forced vital capacity (FVC), which is the maximal volume of air exhaled through forced effort from a position of full inspiration, i.e. vital capacity performed with a maximally forced expiratory effort, expressed in litres at BTPS5.
  • One second forced expiratory volume (FEV1), which is the maximal volume of air exhaled in the first second of a forced expiration from a position of full inspiration. This is expressed in litres at BTPS5.

Note: For respondents aged 6 to 7 the predicted equations were taken from 'Corey 1976'. For respondents 8 years and older the predicted equations were taken from 'Hankinson (NHANES III)'.

If the respondent's age, height or weight, were outside the published range for the selected predicted equation, the predicted values calculated were by extrapolation.

3.1 Equipment

  • Koko spirometer
  • Disposable mouthpieces - filtered
  • Paediatric adapter - if necessary
  • Disposable nose clip
  • 3L Calibration syringe
  • Barometer/thermometer

3.2 Eligibility

  • All respondents aged 6 to 79

3.3 Exclusion criteria

  • Respondent with a stoma (A surgically created opening of an internal organ on the surface of the body, i.e.: colostomy, tracheostomy)
  • Pregnant women (> 27 weeks)
  • Heart attack within the last 3 months
  • Major surgery on chest or abdomen within the last 3 months
  • Taking medication for tuberculosis
  • Recent eye surgery (e.g., cataract, ≤ 6 weeks)
  • Acute respiratory condition such as a cold, bronchitis, flu
  • Respondents with an important language barrier
  • Difficulty breathing at rest
  • Persistent cough

3.4 Administering the spirometry measurement

If, during the household interview, the respondent reported more than one cultural/racial background (e.g., answered both Black & Arab to question SDC_Q24) the HMS selected a racial adjustment based on visual cues. The race variable from the household represents the respondent’s self-reported cultural and racial background while the race adjustment variable (SPM_022) is a variable used to perform a correction on the spirometry data based on the different morphology among the races and as such these two variables may not match for all respondents. Variable SMP_022 should only be used in conjunction with spirometry analyses.

Table 2 Race adjustment categories according to self-reported racial background provided during the household interview.

Race adjustment:

Reported racial background

Correction Factor

To Corey equation

To Hankinson equation

<1> White

White

None

None

Arab

Aboriginal

<2> Black

Black

10% decrease to equation used for whites

None

<3> Hispanic

Mexican American

None

None

<4> Asian

South Asian / South East Asian

10% decrease to equation used for whites

10% decrease to equation used for whites

West Asian

Chinese

Japanese

Korean

Filipino

<5> Other

Other

None

None

Unknown

  1. The health measurement specialist (HMS) recorded the respondent's appropriate 'race adjustment' category (see table 2). For a given standing height, people of certain ethnicities tend to have longer legs and shorter trunks than Caucasians. Consequently, these people have smaller lungs, and should not be assigned the same predicted lung capacity as Caucasians.

  2. The HMS provided thorough instructions, as well as a demonstration (without using the mouthpiece) of the test prior to having the respondent perform the test. The spirometry test depends greatly on the effort of the respondent; therefore it was important that the HMS adapted an appropriate coaching technique to ensure the best possible test results from each respondent.

  3. The respondent was instructed to sit with good posture, with both feet flat on the floor throughout the test. They were instructed not bend over at the waist during the exhalation phase. When testing older respondents, well-fitting false teeth were not routinely removed, since they preserve oropharyngeal geometry and spirometry results are generally better with them in place5.

  4. The HMS assisted the respondent to ensure the nose clip was on securely. The respondent must wear a nose clip during the test to avoid air escaping through his/her nose.

  5. The respondent placed the mouthpiece in his/her mouth and ensured that a good seal was obtained with the lips and that the teeth were resting on the outside of the mouthpiece.

  6. The respondent was instructed to breathe normally in and out through the mouthpiece.

  7. After a few normal breaths, the respondent was instructed to take a big, quick and deep breath in, filling the lungs with as much air as possible.

  8. At the end of the maximal inhalation, the respondent was instructed to immediately blast out all the air as forcefully and quickly as possible. It was important that the respondent did not hold his/her breath before blowing out.

  9. The HMS provided encouragement to the respondent during the exhalation phase. Once the respondent had obtained a 1 second plateau on the volume/time curve and exhaled for at least 6 seconds (or 3 seconds for children 6 to 10 years old), the HMS told him/her to take a big breath in (2nd maximal inspiration).

  10. Following the second maximal inspiration, the respondent was asked to remove the mouthpiece and nose clips.

  11. After each trial the HMS had to decide whether or not to retain the effort. This was done after the HMS assessed the trial quality (explained in the 'Assessing Trial Quality' section below).

  12. The respondent was given a short rest (about 30 to 45 sec) between trials to catch his/her breath. The HMS always observed the respondent for fatigue and did not allow another trial to be performed until the respondent had recovered from the previous trial.

  13. The HMS performed a minimum of 3 acceptable trials over a maximum of 8 attempts. If after 8 trials, there was still no reproducibility in the trials, the HMS selected the best trial that was done by the respondent and saved the efforts.

  14. The best test effort was determined by the sum of FVC and FEV1. At the end of all trials, the HMS confirmed that the chosen trial was indeed the best. If this was not the case, or the chosen trial was unacceptable due to technique or procedure, the HMS selected another trial as 'best'.

  15. All trials were saved and if fewer than 3 trials were performed, the HMS recorded the reason why.

3.5  Assessing Trial Quality

Two types of criteria assessments were done in order for the HMS to accept the trial: the within-manoeuvre criteria and the between-manoeuvre criteria.

3.5.1 Within-manoeuvre criteria

Within-manoeuvre criteria included two different criteria. First, the HMS needed to decide if the trial was usable, if it was, then they needed to decide if it was acceptable as follows:

Usable Trials

To be usable, the trial must:

  • Have had a good start, which means no excessive hesitation or false start. The extrapolated volume (EV) must not have been greater than 0.5% of FVC or 0.150 L, whichever was greater. EV was determined by extrapolation through the steepest part of the curve, where flow was peak expiratory flow (PEF). FVC=4.291 L; EV=0.123 L (2.9% FVC)5.

  • Have been without coughing during the first second of the manoeuvre, that would affect the measured FEV1 value, or any other cough that, in the HMS's judgment, interfered with the measurement of accurate results.

Acceptable Trials

To be acceptable, the trial must have met all of the previous conditions (be usable), plus it must:

  • Have been free from glottis closure (Valsalva manoeuvre) or hesitation that caused a cessation of airflow. This could be seen as an abrupt plateau in the volume-time curve and an abrupt decrease in flow at the end of the manoeuvre in the flow-volume curve.

  • Have been free from early termination or cut-off where it was apparent that the respondent failed to exhale for 6 seconds (or 3 seconds for children 6-10 years old) and there was no 1 second plateau of the volume-time curve

  • Have been free from leaks that could be seen in the volume-time curve as a loss of volume over the 6 second exhalation or even a slightly negative flow at the end of the manoeuvre.

  • Have been free from obstruction (e.g., obstruction due to the tongue being placed in front of the mouthpiece, or teeth in front of the mouthpiece, or mouthpiece deformation due to biting).

  • Have been free from evidence of an extra breath being taken during the manoeuver5.

  • Have had good starts:
    • Extrapolated volume 0.5% of FVC or 0.15 L, whichever is the larger value (refer to "a" in the usable trials section).
    • A 'good peak' was seen on the flow-volume [F(t)] curve (time to peak flow is less than 120 ms).
  • Have shown satisfactory exhalation:
    • There was no early termination (refer to "d" in this section);

Or;

    • There was a plateau in the volume–time [V(t)] curve;
    • There was no instance where the respondent could not or should not continue to exhale;
    • There was an effort that is maximal throughout.

3.5.2 Between-manoeuvre criteria:

Between-manoeuvre criteria were used to assess reproducibility between trials. When three acceptable spirograms were obtained, the HMS checked for between-manoeuvre reproducibility:

  • If respondent's FVC was > 1.0L then reproducibility criteria were when:
    • The two largest FVCs were within ≤ 150ml of each other
    • The two largest FEV1s were within ≤ 150ml of each other



    •  
    •  
  • If respondent's FVC was ≤ 1.0L then reproducibility criteria were when:
    • The two largest FVCs were within ≤ 100ml of each other
    • The two largest FEV1s were within ≤ 100ml of each other

If, after three trials, both of the criteria were met, the test session could be concluded.

  • The HMS ensured that the three trials were acceptable
  • The HMS ensured that two of them were reproducible.

If, after three trials, both of the criteria were not met, the HMS continued testing until

  • Both of the criteria were met with analysis of additional acceptable spirograms

or

  • A total of eight tests had been performed or,
  • The patient/subject could not or should not continue5.

Note: A respondent could give a usable, acceptable, and reproducible effort without giving a maximal effort. The HMS tried to ensure that the respondent gave a maximal effort to blow as hard as possible for as long as possible (e.g., facial expression, body language, etc). Even if the acceptability and reproducibility criteria were met after three trials, doing 1 or 2 extra trials was strongly suggested, particularly if a respondent continue to improve after each trial. There is a learning curve in performing spirometry and respondents often get better and better after each trial.

3.6  Assessing Data Quality

A quality review of all spirometry data was performed by a spirometry expert prior to the results being returned to respondents and data being released. The review included an evaluation of all trials to determine trial acceptability and test reproducibility/quality.

3.6.1 Trial Acceptability

All trials were given an acceptability code (1= acceptable or 2=unacceptable). Only acceptable curves were used in the determination of the best test data.  A trial was coded as unacceptable if any of the following were noted in the trial:

  • There is a cough in the first second of the trial; or
  • There is a large extrapolated volume caused by excessive hesitation; or
  • If the reviewer notes that data within the trial could affect the accuracy of best test data or derived variables (e.g., trial has largest FVC but QC, reviewer feels end of test is not reliable); or
  • If the reviewer notes that the entire trial is of insufficient quality to be used for analysis.

3.6.2 Test Quality and Reproducibility

All acceptable trials were reviewed to determine whether the test results for FVC and FEV1 represented a maximal effort by the respondent (quality) and met the reproducibility of 150ml. The FVC quality factor (SPM_QFVC) and FEV1 quality factor (SPM_QV1) indicate whether a reproducible FVC and/or FEV1 were obtained.

A: Excellent quality and reproducibility. Use in analysis.

B: Good quality and reproducibility. Use in analysis.
Example: A common case is for children and adolescents who do not exhale for the required length of time (3 or 6 seconds). If these respondent’s trials show a 1 second plateau and the reviewer judges that the curves represent a maximum volume (FVC) then a code B is assigned.

C: Questionable quality and reproducibility. Use in analysis with caution.
Example: A respondent has only 2 acceptable curves which are not reproducible and the other curves are unacceptable due to early termination and large extrapolated volumes. However, the curves with the large extrapolated volumes do confirm the FVC reproducibility.
Example: A respondent with chronic obstructive pulmonary disease (COPD) and a low FEV1/FVC (e.g., <0.45). Because of COPD, the respondent cannot provide a repeatable FVC with even 8 manoeuvres. So, the grade should be at least a C or better as the lack of an acceptable curve due to end of test failures is not a sufficient reason to exclude or grade the subject’s results with a D or F.

D: Highly questionable reproducibility and quality. Do not use in analysis.

F: Unacceptable test results. Do not use in analysis.

4. Musculoskeletal fitness

4.1 Grip strength component

Muscular strength refers to the maximum force that can be generated by a specific muscle or muscle group. The most common method of measuring muscular strength in the field is isometric grip strength.Isometric grip strength is measured using a handgrip dynamometer. The protocol for the Grip Strength Component was based on the Canadian Physical Activity, Fitness and Lifestyle Approach (CPAFLA)1 for adults 15 to 69 and on the 1981 Canada Fitness Survey2 for 7 to 14 year old children.

4.1.1 Equipment

  • Smedley III hand dynamometer (Takei Scientific Instruments Grip A).

4.1.2 Eligibility

  • Respondents aged 6-79.

4.1.3 Exclusion criteria

  • Respondents who had positive response(s) to PAR-Q questions 5, 6 and 7 (depending upon probing by the HMS). (See appendix 3)
  • Respondents who had limited upper extremity function—respondent was unable to hold the dynamometer with both hands (e.g., missing fingers on both hands, paralysis of both hands), were screened out. Respondents who were able to grip the dynamometer with one hand still performed the component.

4.1.4 Administering the grip strength

  1. The HMS demonstrated the correct technique, emphasizing that the respondent should not hold his/her breath while performing the test (avoid Valsalva manoeuvre). The respondent was asked to remove any hand and wrist jewellery.

  2. The respondent was instructed to grasp the dynamometer in his/her right hand, with the grip between the fingers and the palm at the base of the thumb.

  3. The grip size of the dynamometer was adjusted using the screw until the second joint of the fingers fit snugly under the handle and took the weight of the instrument.

  4. The respondent was instructed to hold the dynamometer in line with the forearm at the thigh level, away from the body at a 45° angle. The respondent was asked to adopt a stable body position with the feet hip width apart. The respondent was instructed that neither the hand nor the dynamometer were to touch the body or any other object during the test.

  5. The respondent was then asked to squeeze vigorously to exert maximum force, exhaling while squeezing to avoid build-up of intra-thoracic pressure.

  6. The dynamometer was reset and the test was repeated on the left hand. Both hands were measured twice, alternating hands between trials.

  7. The scores were recorded for each hand to the nearest kilogram.

4.2 Sit and reach component

The protocol for the Sit and Reach Component was based on the Canadian Physical Activity, Fitness and Lifestyle Approach (CPAFLA)1 for adults 15-69 and on the 1981 Canada Fitness Survey2 for 7-14 year old children.

4.2.1 Equipment

  • Exercise mat
  • Flexometer

4.2.2 Eligibility

  • Respondents 6-69 years old.

4.2.3 Exclusion criteria

  • Respondents who had positive response(s) to PAR-Q questions 5 and 7 (depending upon probing). (See Appendix 3)
  • Pregnant women (> 12 weeks)
  • Respondents 70 years of age and older
  • Colostomy bag
  • Lower body paralysis
  • Home visit

4.2.4 Administering sit and reach

  1. Respondents performed this test without shoes, after a short stretching warm up. The test was demonstrated prior to having the respondent perform it.

  2. The respondent was asked to sit with legs fully extended with the soles of the feet placed flat against the flexometer. The inner edge of the soles of the feet were positioned 6 inches apart. The flexometer was secured against the wall.

  3. The respondent was asked to bend and reach forward without jerking, keeping the knees fully extended, arms evenly stretched with palms down, and hands placed one on top of the other. The respondent's finger tips pushed the sliding marker along the scale. The fingertips of one hand could not extend beyond the fingertips of the other hand.

  4. The position of the maximum flexion was held for approximately two seconds. Respondents were advised that lowering the head and breathing out would maximize the distance reached.

  5. If the respondent's knees flexed, the trial was not counted. Bouncing or jerking motions were not allowed.

  6. The test was performed twice, with a short rest between trials. The maximum distance reached at the end of each trial was recorded to the nearest 0.1cm.

4.3 Partial curl-up component

The protocol for the Partial Curl-up Component is based on the Canadian Physical Activity, Fitness and Lifestyle Approach (CPAFLA)1.

4.3.1 Equipment

  • Gym mat with 10 cm metal strap on one end
  • Goniometer
  • Metronome

4.3.2 Eligibility

  • Respondents 6-69 years of age.

4.3.3 Exclusion criteria

  • Respondents who had positive response(s) to PAR-Q questions 1, 2, 3 (automatic) and 5, 6 and 7 depending upon probing). (See Appendix 3)
  • Pregnant women (> 12 weeks)
  • Respondents 70 years of age and older
  • Respondents with resting heart rate > 100 bpm or blood pressure > 144/94 mmHg as determined during the blood pressure component.
  • Mentally and physically disabled individuals (at the discretion of the HMS)
  • Difficulty breathing at rest
  • Persistent cough
  • Lower extremity swelling
  • Appears ill or complains of fever
  • Colostomy bag
  • Home visit

4.3.4 Administering partial curl-ups

  1. The correct positioning of the curl-up was first demonstrated to the respondent by the HMS.

  2. The respondent was asked to get into the starting position as follows:



  3.  
  4.  
  • Lie in the supine position with the head resting on the mat, shoulders relaxed, arms straight at the sides and parallel to the trunk, palms of hands in contact with the mat, and the middle finger tip of both hands touching the back edge of the metal strap when the arms are fully extended. If the respondent had one arm that was longer than the other, the back edge of the metal strap was placed at the middle finger of the longest arm.

  • The respondent's legs were bent, shoulder-width apart, knees at a 90 degree angle (the goniometer was used to establish the correct angle).




  •  
  •  
  • The respondent's heels stayed in contact with the floor. The test was performed with shoes on. In the case where the respondent did not have appropriate footwear, the test was performed in sock feet.



  •  
  •  
  • Action:



  •  
  •  
  • The metronome set at 50 beats per minutes. The HMS was allowed to call out "up on a beat, down on a beat" during the test if respondents had difficulty following the beat of the metronome.

  • The respondent was told to slowly curl up far enough so that the tip of the middle finger of both hands reached the far end of the metal strap.

  • It was explained to the respondent that his/her fingers must remain in contact with the metal plate and his/her heels must remain in contact with the floor. Anchoring of the feet was not permitted.

  • The respondent was instructed that on return, the shoulder blades and head must come in contact with the mat, and the tip of the middle finger of both hands must touch the back edge of the metal strap.

  • The movement was to be performed in a slow, controlled manner in order to perform the lifting and lowering stages of the curl-up at a rate of 25 per minute (up on beat, down on a beat).

  • The respondent was asked to perform as many consecutive curl-ups as possible, without pausing, to a maximum of 25 in the one-minute time period.

  • Only properly executed curl-ups were counted and feedback was provided on incorrectly executed curl-ups.



  •  
  •  
  • The test was terminated before the one minute mark if the respondent was:



  •  
  •  
  • experiencing undue discomfort;

  • unable to maintain the required cadence;

  • unable to maintain the proper curl-up technique (e.g., heels came off the floor) over two consecutive repetitions despite corrections by the HMS.



  •  
  •  

Note: The same mistake had to have been made 2 times in a row for the test to be terminated. If two different mistakes were made consecutively then the test continued until two of the same mistakes were made in a row or 25 curl-ups were completed.

  • The number of partial curl-ups completed was recorded. Incorrect curl-ups were not recorded.



  •  
  •  

5. Modified Canadian Aerobic Fitness Test (mCAFT) component

The protocol for the modified Canadian Aerobic Fitness Test (mCAFT) Component is based on the Canadian Physical Activity, Fitness and Lifestyle Approach (CPAFLA)1 for adults 15-69 years of age and on the 1981 Canada Fitness Survey6 for children aged 6-14 years of age.

5.1 Equipment

  • BpTRU™ automated blood pressure cuff (including various cuff sizes)
  • mCAFT step
  • mCAFT CD
  • CD player
  • Timer or stopwatch
  • Metronome (optional)
  • Stethoscope (optional)
  • Heart rate monitor (belt, strap, watch)
  • Mercury sphygmomanometer (optional)

5.2 Eligibility

  • All respondents aged 6-69

5.3 Exclusion criteria

  • Positive response to PAR-Q questions 1, 2, 3 or 6 (automatic) or 4, 5 or 7 (depending upon probing). (See Appendix 3)
  • Respondents taking heart rate or blood pressure altering medications
  • Pregnant women (> 12 weeks)
  • Respondents who are 15 years of age and older with resting heart rate > 99 bpm or resting blood pressure > 144/94 mmHg as determined during the screening component
  • Mentally and physically impaired individuals, at the discretion of the HMS. Every effort should be made to be inclusive of individuals with disabilities provided that all safety precautions are taken into account
  • Respondent donated blood within the last 24 hours
  • Difficulty breathing at rest
  • Respondents taking medication for a breathing condition that worsens during exercise, but do not have his/her medication with them (as assessed during the Screening Component)
  • Appears ill or complains of fever
  • Persistent cough
  • Lower extremity swelling
  • Insulin pump
  • Supplemental oxygen
  • Drank alcohol since midnight
  • Consumed a large meal within 1 hour of appointment start time
  • Home visit

5.4 Administering the mCAFT

Note: If a respondent was unable to complete a stage the reason was recorded. Post-exercise heart rate and blood pressure were monitored in these cases.

Table 3 Reasons why a respondent did not complete the mCAFT test
Key Reason When to choose this answer
1 Refusal Respondent refuses to participate
2 Unable to maintain proper cadence Respondent cannot perform the test at the proper cadence
3 Dizziness Respondent feels dizzy
4 Extreme leg pain Respondent cannot go on or start the test due to leg pain (lactic acid build up, injury, arthritis…)
5 Nausea Respondent feels nauseated or has an extreme headache
6 Chest pain Respondent feels chest pain
7 Facial pallor Respondent appears ill
8 Other – Specify Any other reason not mentioned above. You will be prompted to explain this reason in a text box.

Note: If the HMS was not able to get a reading from the heart rate monitor, they determined the heart rate manually, using the stethoscope. The HMS placed the stethoscope head near the sternum at the 2nd intercostal space. The HMS took the pulse for a 10-second timing sequence.

Note: If a respondent was unable to complete a stage record the reason why. Post-exercise heart rate and blood pressure were monitored in these cases.

  1. The health measurement specialist (HMS) asked all respondents if they need to go to the washroom before they started the test.

  2. The HMS explained the test and assisted the respondent in putting on the heart rate monitor. The strap was adjusted as needed to ensure a strong reading from the heart rate monitor. The HMS ensured that the room temperature was between 21°C ± 2°C.

  3. The HMS demonstrated the two-step stepping pattern, first without music and then with the music set at the respondent's first stepping stage. Each respondent started stepping at a stage where the cadence intensity was 65-70% of the mean aerobic power expected of a person 10 years older than him/her. Male respondents 15-69 years old used a two-step pattern for stages 1 through 6 and a one-step pattern for stages 7 and 8. Female respondents 15-69 years old used the one-step pattern for stage 8 only. All stepping stages for respondents 6-14 years of age were done using the 2-step pattern and the music for the stages was always that of the adult female (based on the 1981 Canada Fitness Survey protocol)2. The starting stage was stage 5, regardless of gender. If the respondent completed the 7th stage, the test was stopped regardless of whether the ceiling heart rate was reached. In these cases, the respondent's heart rate at the end of stage 7 was used to determine the fitness level.

  4. The HMS had the respondent try the two-step stepping pattern with the music. The HMS then demonstrated the one-step stepping pattern to the respondent. If the respondent's heart rate after trying the two-step stepping pattern was under 100 bpm, the HMS had the respondent try the one-step stepping pattern. If the respondent's heart rate was above 100 bpm after trying the stepping patterns, the HMS had the respondent rest before starting the test. The respondent was reminded that each stepping stage was 3 minutes long and that when the music stopped he/she was to stop, turn to face the HMS and to stand still. The respondents were advised not to talk during the mCAFT unless it was necessary to do so.

  5. The HMS began the test at the pre-calculated start stage. The HMS guided the respondent if they had difficulty keeping up with the rhythm. During the test, the HMS stood next to the respondent and monitored them for signs of discomfort. The test was stopped immediately if the respondent began to stagger, complained of dizziness, extreme leg pain, nausea, chest pain or if he/she shows facial pallor.

  6. At the end of each stepping stage, the respondent stopped, turned towards the HMS and stood still. The HMS read the heart rate from the heart rate monitor when the instructor on the CD said "STOP EXERCISING". This value was recorded into the data capture application.
  7. If the respondent's heart rate was below the pre-calculated ceiling heart rate, the HMS had him/her prepare to start the next stepping stage. If the heart rate was equal to or above the pre-calculated ceiling heart rate, the stepping portion of the test was finished. If the respondent reached the pre-calculated ceiling heart rate during a stepping stage, he/she completed the full 3 minutes of the stage. As soon as the stepping portion was complete, the HMS started the stop watch and proceeded to the post-test procedures.

5.5 Post-test procedures

  1. Upon completion of the final stepping stage, the respondent was asked to walk around slowly for 1.5 minutes. The heart rate monitor was removed from the respondent's chest. If the respondent appeared overly fatigued or was light-headed at the end of the test, the HMS had him/her sit down and elevated the legs.

  2. After 1.5 minutes, the respondent was asked to sit down.

  3. The respondent's blood pressure was taken (electronically or manually) at 2:00 minutes post exercise and 3:30 minutes post exercise. These measurements were recorded.

  4. If the respondent's blood pressure reading at 3:30 min was > 144/94 mmHg and/or the heart rate was > 99  bpm the HMS continued to measure the heart rate and blood pressure at two minute intervals until the respondent's readings had dropped below 145/95 mmHg and 100 bpm.

6. Oral Health component

A dentist's survey manual was designed to collect information needed to assess the oral health status of Canadians and was based on the World Health Organization (WHO) criteria.  The survey responses were directly entered into a computer.  The World Dental Federation (FDI) numbering system was used. There were 4 blocks to the dentist's survey manual; the Oral Health Component Introduction, the Oral Health Questions, the Oral Health Restriction and the Oral Health Examination. For more information, please refer to the Canadian Health Measures Survey 2006-2008, Dentist's Survey Manual and Coding Criteria7.

6.1 Equipment

  • a plane mirror
  • a graduated Williams periodontal probe
  • cotton rolls and gauze

6.2 Eligibility

  • All respondents aged 6-79

6.3 Exclusion criteria

The follow criteria excluded the respondent from the probing score assessment portion of the oral health examination component.

  • Respondents who need to take antibiotics (for example, penicillin) before a check-up or get dental care.
  • Respondents who have been diagnosed by a health professional with a heart murmur that requires them to take antibiotics for dental treatment.
  • Respondents who have been diagnosed by a health professional with a heart valve problem.
  • Respondents who have been diagnosed by a health professional with congenital heart disease.
  • Respondents who have been diagnosed by a health professional with bacterial endocarditis?
  • Respondents who have been diagnosed by a health professional with rheumatic fever?
  • Respondents who have had bypass surgery in the past year.
  • Respondents who have had a pacemaker or other automatic defibrillator for less than one year.
  • Respondents who have other artificial material in his/ heryour heart, veins or arteries?
  • Respondents who have had a joint replacement.
  • Respondents who have ever received an organ transplant.
  • Respondents who have kidney disease that requires dialysis.
  • Respondents who are immuno-supressed or are on immuno-suppression therapy (for example, chemotherapy).
  • Respondent who had haemophilia or had received chemotherapy in the past four weeks

6.4 Administering the oral health component

Oral health questions block (OHQ)

  1. Next the dentist asked a series of questions pertaining to the oral health of the respondent. These questions compliment the examination block and help to build a better profile of the respondent. During this component the dental recorder entered the answers provided by the respondent into the data capture application.

Oral health restriction block (OHR)

  1. Before the oral health examination block, the dentist asked specific oral health screening questions to determine whether the respondent could participate in the entire oral health component.

  2. During this component the dental recorder entered the answers provided by the respondent in the data capture application.

  3. If the respondent answered yes to any the restriction questions (with the exception of the question on pacemakers or other automatic defibrillators which had a second probing question) the oral health restrictions block was exited and the respondent was automatically screened out of the probing score assessment portion of the oral health examination component. Any respondent who had had haemophilia or had received chemotherapy in the past four weeks skipped this block of questions completely as he/she had been automatically screened out of probing because of these conditions.

Oral health examination block (OHE)

  1. At the start of the oral health examination block, the dentist explained the process to the respondent and showed the respondent the tools that were used during the examination.

  2. As the dentist progresses from question to question, the dental recorder cued the dentist on which assessment was next and, if applicable, with which tooth number the dentist should start. This was important as the flow of the tooth examinations varied from question to question and a prompt by the dental recorder helped to limit errors.

  3. The oral health examination block assessed the following:
    • Dentate status - This section served to record the condition of the respondent's natural teeth.
    • Prosthetic status - This section served to record whether the respondent had any artificial teeth in either their upper or lower arch. The dentist asked if the respondent has any prosthetic appliances even if the respondent is not wearing them.
    • Mucosal status - This section served to record the presence or absence of any oral pathology. An oral pathology is defined as any abnormality in the oral cavity.
    • Fluorosis - This section served to record a fluorosis score for the anterior permanent maxillary incisors for respondents aged 6-12.
    • Orthodontic status/treatment - This section served to record the orthodontic status and treatment of respondents > 12 years of age. Respondents who are edentulous skipped this section of questions.
    • Periodontal assessments - This portion of the examination included an assessment of gingivitis, debris, calculus, attachment loss and a probing score. The age of the respondent and the medical history already recorded (OHR block, haemophilia, chemotherapy) determined if the respondent could participate in attachment loss and periodontal probing. Respondents who were less than 15 years old or was not medically fit for attachment loss, periodontal probing or sub-gingival calculus assessment, the "Attachment loss" and "Probing score" skipped this section.
    • Tooth status - This section served to record the status of each of the respondent's teeth. For respondents aged 17 years or younger, the dentist did not perform a root examination.  For a child with mixed dentition (having both primary and permanent teeth) the status of whichever tooth was present in the mouth was recorded. If both the primary and permanent teeth were present then the permanent tooth took precedence.
    • Amalgam count - This section served to record the total number of tooth surfaces with amalgam (silver) fillings.
    • Traumatic injury - This section served to record the condition of each of the four permanent upper and four permanent lower incisor teeth.
    • Treatment needs - This section served to record the dentist's view of the treatment needs of what the respondent needs on this day assuming there are no financial barriers. This included prosthetic needs and general treatment needs.
    • Urgent treatment needed - Once the respondent has left the oral health room, the dentist completed the "Urgent Needs" section of the component.
    • Medical condition discovered - If the dentist performing the examination noticed that the respondent has one of the following conditions: oral lesion, severe acute infection and/ or another serious condition requiring attention from a medical professional within a week, then it was recorded.

7. Urine Component

The purpose of the urine collection component was to obtain laboratory results for respondents ages 6 to 79 on a variety of measures that will be used to obtain prevalence estimates of disease, risk factors for diseases, and baseline information on health, nutritional status and environmental exposure of the population. 

Approximately 70mL of urine was collected from each respondent aged 6 to 79 years. The Urine Collection Component could be completed at any time during the clinic visit.

7.1 Exclusion criteria

  • if the respondent has a mental or physical condition that prevents him/her from providing a sample
  • if there is a language barrier that prevents proper instruction of collection.

7.2 Equipment

  • urine cup

7.3 Urine Collection

Table 1 Midstream urine collection instructions
1. Wash hands with soap and water.
2. Open the urine cup. Do not touch the inside of the cup or the lid.
3. Urinate a small amount of urine into the toilet and, without stopping, catch as much urine as possible in the cup. If possible, fill the cup up to the black line with urine.
4. Place the lid tightly on the container, taking care not to touch the edges of the inside of the container. Rinse and dry the container. Place the container in the brown paper bag provided.
5. Wash your hands with soap and water.
6. Return the urine cup in the brown paper bag to the CHMS staff member.

Note: On occasions it may have been necessary to obtain multiple urine samples to meet volume requirements. More than one urine sample was required only if the respondent’s first urine sample was less than ¾ of the requested volume.

7.4 Handling urine samples

Upon receipt, urine samples were placed in the fridge with the barcode facing outward until processing.  If a respondent provided more than one urine sample the sample containers were pooled upon receipt of the second sample.  If time did not permit, they were kept together and labeled 1, 2 etc.

7.4.1 Urine splitting

Table 1 Urine processing protocol for regular respondents
Collection Type Test ID # Test Name Age (years) Preferred
Sample
Volume
(mL)
Minimum
Sample
Volume
(mL)
Specimen
Tube 
Capacity
(mL)
Specimen
Tube
Type
Cap Colour
Urine Cup 701 Microalbumin/
Creatinine
6 to 79 2.0 0.5 2.0

VWR
Cryogenic

Blue
751 Cotinine 6 to 79 4.5 0.5 5.0 VWR
Cryogenic
Red
752 Phthalates 6 to 49
(3500)
15.0 12.0 30.0 Nalgene Clear
753 Inorganic Mercury 6 to 79 4.5 1.6 5.0 VWR
Cryogenic
Clear
754 Bisphenol A 6 to 79
(5000)
(see note) 20.0 30.0 Nalgene Clear
702 Iodine 6 to 79 4.0 2.0 5.0 VWR
Cryogenic
Green
755 Organophosphate Pesticides 6 to 79
(5000)
(see note) With test 754 30.0 Nalgene Clear
756 Phenoxy herbicide 6 to 79
(5000)
(see note) With test 754 30.0 Nalgene Clear
971 Stored Urine 1 6 to 79 4.5 NA 5.0 VWR
Cryogenic
Yellow
972 Stored Urine 2 6 to 79 4.5 NA 5.0 VWR
Cryogenic
Yellow
Note: Test numbers 754, 755, and 756 are all analyzed from the same 30ml bottle.

7.5 Specimen storage

Specimens were stored in the mobile clinic lab in the refrigerator and were shipped once a week to the reference labs. All specimens were to be stored as soon as processing was complete.

For more information regarding the laboratory standard operating procedures (SOP) please contact the Canadian Health Measures Survey at 1-888-253-1087 or chms-ecms@statcan.gc.ca.

8. Phlebotomy Component

During the Phlebotomy Component the phlebotomist collected blood samples in order to measure nutritional status, metabolic syndrome, cardiovascular disease and infectious disease markers.

8.1 Exclusion Criteria

  • Chemotherapy within the past 4 weeks
  • Haemophilia
  • Double mastectomy
  • Rashes, gauze dressings, casts, edema, paralysis, tubes, open sores or wounds, withered arms or limbs missing, damaged, sclerosed or occluded veins, allergies to cleansing reagents, burned or scarred tissue, shunt or IV on both arms.

8.2 Equipment

Table 1 Equipment and supplies that may be used for the venipuncture procedure
  • Vacutainer 8.5mL Red/Grey SST
  • Bandages/Non allergenic tape
  • Vacutainer 2.0mL Light Grey
  • CaviWipes
  • Vacutainer 6.0mL Lavender EDTA
  • Tourniquet
  • Vacutainer 10mL Lavender EDTA
  • Alcohol swabs
  • Vacutainer 5.0mL Gold SST
  • Gauze
  • Vacutainer 1.8mL Light Blue
  • Sharps bin
  • Vacutainer 3.0mL Red
  • Gloves- non sterile, latex free S M L
  • 21 Gauge Needles
  • Antibacterial hand sanitizer
  • 22 Gauge Needles
  • Virkon/ Haztab
  • 21 Gauge Butterfly Needles
  • Blood drop stamp
  • 23 Gauge Butterfly Needles
  • Vacutainer Tube Mixer
  • 25 Gauge Butterfly Needles

 

8.3 Performing the Venipuncture Procedure

8.3.1 Selecting the Appropriate Vein

Whenever possible, a vein on the left arm was looked for first.

The median cubital and cephalic veins were the most common veins to use for the venipuncture procedure. If there were no suitable veins in this area, on either arm, the phlebotomist looked at the back of the hands of the respondent. These veins were used as a last resort and a butterfly needle was always used for this procedure. 

8.3.2 Preparing for the blood draw

  1. The phlebotomist determined the appropriate needle size. 

  2. The site was cleaned with an alcohol wipe in a circular motion beginning with the centre of the site and moving outwards.

  3. All the required supplies for the venipuncture were prepared. All the tubes required were placed in the proper order (see tables 2a and 2b).

  4. The phlebotomist reapplied the tourniquet when they were ready to perform the procedure. They had the respondent make a fist and hold it. They instructed the respondent not to pump his/her fist as this can affect certain test results.

Table 2a Order of draw for fasted survey respondents (minimum 10 hours)
Tube order Tube Type Size Age in Years
6 to 11 12 to 13 14 to 19 20 to 79
01 Red/Grey SST 8.5mL Y Y Y Y
02 Light Grey 2.0mL Y Y Y Y
03 Lavender EDTA 6.0mL Y Y Y Y
04 Lavender EDTA 6.0mL Y Y Y Y
05 Red/Grey SST 8.5mL     Y Y
06 Lavender EDTA 10mL       Y
07 Light Blue 1.8mL   Y Y Y
08 Gold SST 5.0mL Y Y Y Y
09 Lavender EDTA 10mL       Y
10 Lavender EDTA 10mL       Y
11 Red/Grey SST 8.5mL   Y Y Y

 

Table 2b Order of draw for non-fasted survey respondents

Tube order

Tube Type

Size

Age in Years

6 to 11

12 to 13

14 to 19

20 to 79

01

Red/Grey SST

8.5mL

Y

Y

Y

Y

02

Lavender EDTA

6.0mL

Y

Y

Y

Y

03

Lavender EDTA

6.0mL

Y

Y

Y

Y

04

Red-Grey SST

8.5mL

 

 

Y

Y

05

Light Grey

2.0mL

Y

Y

Y

Y

06

Lavender EDTA

10mL

 

 

 

Y

07

Light Blue

1.8mL

 

Y

Y

Y

08

Gold SST

5.0mL

Y

Y

Y

Y

09

Lavender EDTA

10mL

 

 

 

Y

10

Lavender EDTA

10mL

 

 

 

Y

11

Red/Grey SST

8.5mL

 

Y

Y

Y

8.4 Handling blood samples

Blood samples were brought into the lab by the phlebotomist as soon as possible after collection.

Table 3
Specimen Handling Steps Prior to Processing
Time Tube Type  (Test Number) Handling
During first 15 minutes post collection 6.0mL EDTA lavender (03or 02)1
6.0mL EDTA lavender (04 or 03)1
2.0mL light grey (02 or 05)1
10.0mL EDTA lavender (06)
1.8mL light blue (07)
10.0mL EDTA lavender (09 and 10)
  • Place on mixer
8.5mL red/grey (01)
8.5mL red/grey (05 or 04)1
5.0mL gold SST (08)
8.5mL red/grey (11)
3.0mL red (99)
  • Leave in collection rack at room temperature
After first 15 minutes 8.5mL red/grey (01)
8.5mL red/grey (05 or 04)1
5.0mL gold SST (08)
8.5mL red/grey (11)
  • Set the timer for 15 min
  • Leave tubes in rack at room temperature to allow them to clot
10.0mL EDTA lavender (09 and 10)
  • Parafilm tops and place in fridge in designated DNA rack
6.0mL EDTA lavender (03 or 02)
3.0mL red top (99)
  • Aliquot 1.5mL into 3.0mL red top
  • Put 6.0mL tube into rack in fridge
6.0mL EDTA lavender (04 or 03)1
2.0mL light grey (02 or 05)
10.0mL EDTA lavender (06)
1.8mL light blue (07)
  • Place in fridge together in a rack
After second 15 minutes 6.0mL EDTA lavender (03 or 04)1
2.0mL light grey (02 or 05)1
10.0mL EDTA lavender (06)
1.8mL light blue (07)
8.5mL red/grey (01)
8.5mLred/grey (05 or 04)1
5.0mL gold SST (08)
8.5mL red/grey (11)
  • Centrifuge at:
17°C for 15 mins at 1300 RCF
After centrifugation 6.0mL lavender (03 or 02)1
3.0mL red (99)
8.5mL red/grey (01)
8.5mL red/grey (05 or 04)1
5.0mL gold SST (08)
8.5mL red/grey (11)
2.0mL light grey (02 or 05)1
6.0mL lavender (04 or 03)1
10.0mL EDTA lavender (06)
1.8mL light blue (07)
  • Group samples in order used for aliquotting
  • Aliquot immediately or place rack in fridge (see note)
1. the first test number is for fasted respondents, the second is for non-fasted respondents.

All samples were centrifuged within two hours and aliquotted within four hours of the blood draw. Test 132 (homocysteine) was aliquotted within 1.5 hours.

8.4.1 Serum handling

There were a maximum of four serum collection tubes that could be drawn depending on the age and test eligibility of the respondent. Serum from the SST tubes (red/grey and gold) was first pooled into the pre-labelled 30ml Nalgene bottle prior to being aliquotted into individual specimen tubes. 

The phlebotomist was given the following instructions when performing serum handling:  

  1. After centrifugation, inspect all tubes for fibrin strands that may be left in the serum.  If strands of fibrin are visible, remove them from the sample with an applicator stick and dispose of the stick in the biohazard waste.  Also ensure that the gel has indeed separated the cells and serum as it should.

  2. Repeat the above step for each serum collection tube (all red/grey and gold top collection tubes)

  3. Pour off serum from each serum collection tube into the pooled serum bottle. The separation gel will prevent any red cells from decanting. Remove as much serum as possible from each collection tube.

    Note: Avoid pooling serum that is moderately or grossly hemolyzed. Keep these tubes separate and use them for measures such as hepatitis and lipid profile where hemolysis is not an issue. Serum which is slightly hemolyzed would be acceptable to add to the pooled serum bottle.

  4. Screw the lid tightly on the pooled serum bottle and mix the serum by briskly swirling or inverting the bottle 2 to 3 times.

  5. Record whether there is any problem with the specimen that has been transferred to the pooled serum bottle based on the definitions outlined in Table 7.

  6. Set the bottle aside until ready to separate into specimen tubes.

8.5 Specimen processing

Samples were processed as soon as possible to keep sample integrity at its highest.

8.5.1 Whole blood splitting

Table 4
Whole blood processing protocol for regular respondents
Collection Type Test ID # Test Name Age (Years) Preferred
Sample
Volume
(mL)
Minimum
Sample
Volume
(mL)
Specimen
Tube
Capacity
(mL)
Specimen
Tube
Type
Cap Colour
6.0mL EDTA 111 Glycosylated Hemoglobin 6 to 79 1.5 1.0 2.0 Nalgene Clear
112 RBC Folate 6 to 79 0.2 0.1 2.0 VWR Cryogenic Orange
511
or
512
Metal Screen 1 6 to 79 1.8 0.8 2.0 Nalgene Clear
Metal Screen 2 6 to 79 1.8 1.3 2.0 Nalgene Clear
10mL EDTA1 09 DNA 20+ 10.0 NA 10.0 Collection Tube Lavender
10mL EDTA1 10 DNA 20+ 10.0 NA 10.0 Collection Tube Lavender
1. 10 mL EDTA tubes are not aliquotted

8.5.2 Plasma splitting

Table 5
Plasma processing protocol for regular respondents
Collection Type Test ID # Test Name Age (Years) Preferred
Sample
Volume
(mL)
Minimum
Sample
Volume
(mL)
Specimen
Tube
Capacity
(mL)
Specimen
Tube
Type
Cap Colour
2.0mL Light Grey 131 Glucose 6 to 79 1.0 0.3 2.0 VWR Cryogenic Blue
6.0mL Lavender 132 Homocysteine1 6 to 79 1.0 0.4 2.0 VWR Cryogenic Orange
133 Vitamin D 6 to 79 1.0 0.5 2.0 VWR Cryogenic Green
931 Stored Plasma 1 6 to 79 0.5 N/A 0.5 VWR SuperClear Purple/ White
10.0mL Lavender2 531 PBDE + Organochlorine
Pesticides +
Non-Coplanar PCBs
20 to 79 (fasting)
(2500)
2.7 2.2 7.0 Supelco glass vial Black
532 Perfluorinated Compounds 20 to 79 1.8 1.2 2.0 VWR Cryogenic Red
1.8mL Light Blue 134 Fibrinogen 12 to 79 0.5 0.2 2.0 VWR Cryogenic Tan
1. Homocysteine sample was aliquotted within 1.5 hrs of collection and put in the in the freezer immediately.
2. Test 531 and 532 are sub-samples so not all respondents were eligible for these tests.

8.5.3 Pooled serum splitting

Table 6
Serum processing protocol for regular respondents
Collection Type Test ID # Test Name Age (Years) Preferred
Sample
Volume
(mL)
Minimum
Sample
Volume
(mL)
Specimen
Tube
Capacity
(mL)
Specimen
Tube
Type
(Size)
Cap Colour
Pooled Serum from SST Tubes (30mL bottle) 151 Lipid Profile 6 to 79 (fasting) 1.0 0.5 2.0 VWR Cryogenic Pink
152 Insulin 6 to 79 (fasting) 0.5 0.3 2.0 VWR Cryogenic Orange
153 Chemistry Panel 6 to 79 1.0 0.5 2.0 VWR Cryogenic Blue
154 C-Reactive Protein 6 to 79 0.5 0.2 2.0 VWR Cryogenic Blue
155 Vitamin B12 6 to 79 0.7 0.4 2.0 VWR Cryogenic Orange
351
or
352
Hepatitis Panel 1 14 to 79 1.0 0.5 3.0 Fisherbrand Clear
 red O-ring
Hepatitis Panel 2 14 to 79 2.0 0.5 3.0 Fisherbrand Clear   red O-ring
951 Stored Serum 1 6 to 79 0.5 NA 0.5 VWR SuperClear Purple
Yellow
952 Stored Serum 2 6 to 79 0.5 NA 0.5 VWR SuperClear Purple
Yellow
953 Stored Serum 3 6 to 79 0.5 NA 0.5 VWR SuperClear Purple
Yellow
954 Stored Serum 4 6 to 79 0.5 NA 0.5 VWR SuperClear Purple
Yellow
955 Stored Serum 5 12 to 79 0.5 NA 0.5 VWR SuperClear Purple
Yellow
956 Stored Serum 6 12 to 79 0.5 NA 0.5 VWR SuperClear Purple
Yellow
957 Stored Serum 7 12 to 79 1.0 NA 2.0 VWR Cryogenic Yellow
958 Stored Serum 8 12 to 79 1.0 NA 2.0 VWR Cryogenic Yellow
959 Stored Serum 9 12 to 79 1.0 NA 2.0 VWR Cryogenic Yellow

8.6 Specimen storage

Specimens will be stored in the mobile clinic lab in either the refrigerator or the freezer, depending on the test, and will be shipped once a week (twice a week for DNA) to the reference labs.  All specimens are to be stored as soon as processing is complete.

For more information regarding the laboratory standard operating procedures (SOP) please contact the Canadian Health Measures Survey at 1-888-253-1087 or chms-ecms@statcan.gc.ca.

9. Activity monitor component

Activity monitors, also known as accelerometers, are battery operated pager-sized, electronic devices that are worn on a belt around the waist. These devices record a movement count each minute proportional to the average intensity of motion (i.e., acceleration) over that minute.

9.1 Equipment

  • Actical Activity monitor
  • Disposable, adjustable belt

9.2 Eligibility

  • Respondents aged 6 to 79

9.3 Exclusion criteria

  • Persons in a wheelchair

9.4 Administering the activity monitor

  1. Respondents who agreed to take part in the activity monitor component were given an activity monitor and an appropriately sized disposable, adjustable belt. If a respondent was not willing to wear an activity monitor, the reason for the refusal was recorded.

  2. The health measurement specialist (HMS) showed the respondent how to put the belt on. The activity monitor was then placed securely on the belt. The belt was adjusted so that the activity monitor was positioned over the right hip, with the arrow pointing up. The activity monitor could be worn over or under clothing.

  3. The HMS explained that the activity monitor should be put on when the respondent gets up from bed each day and should be worn until the respondent is ready to fall asleep. If the respondent reads or does any other activity before falling asleep, they were to keep wearing the activity monitor. The respondent was instructed to wear the activity monitor for 7 days.

10. References - Canadian Health Measure Survey cycle 1 protocols

  1. Canadian Society for Exercise Physiology. 2003. Canadian Physical Activity, Fitness and Lifestyle Approach (CPAFLA). 3rd edition. Ottawa.
  2. Ross, W. D. & M.J. Marfell-Jones. 1991."Kinanthropometry" in Physiological Testing of the High-Performance Athlete. 2nd edition. J. D. MacDougall, H. A. Wenger, & H. J. Green, eds., Human Kinetics Books, Champaign, Illinois, pp. 223-308.
  3. Fitness Canada. 1986. Canadian Standard Test of Fitness (CSTF) Operations Manual. 3rd edition. Ottawa.
  4. Statistics Canada. No date. Canadian Health Measures Survey Clinic Questionnaire. 92 p. www.statcan.gc.ca/cgi-bin/imdb/p2SV.pl?Function=getSurvey&SDDS=5071&lang=en&db=imdb&adm=8&dis=2
  5. Miller M.R., J. Hankinson, V. Brusasco et al. 2005. "Standardization of spirometry." Eur Respir. Vol. 26 p. 319-338.
  6. Stephens, T. & C.L. Craig. 1985. Fitness and activity measurement in the 1981 Canada Fitness Survey. In: Drury, T. (ed.). 1989. Assessing physical fitness and activity patterns in general population surveys. Department of Health and Human Services, Public Health Service, Center for Disease Control, National Center for Health Statistics. Hyattsville, MD. pub. No. (PHS) 89-1253.
  7. For a copy of the "Canadian Health Measures Survey 2006-2008, Dentist's Survey Manual and Coding Criteria" please contact the Canadian Health Measures Survey at 1-888-253-1087 or chms-ecms@statcan.gc.ca .
  8. Campbell, Norm R.C., Joffre Michel R., McKay Donald W. 2005. "Hypertension Surveillance in Canada: Minimum Standards for Assessing Blood Pressure in Surveys." Canadian Journal of Public Health Vol 96, number 3. p. 217 - 220.

Appendix 5  Derived variable documentation

For more information on the derived variable documentation for Wave 1 please see Canadian Health Measures Survey (CHMS) Cycle 1 Wave 1. Derived Variable (DV) Specifications.

For more information on the derived variable documentation for Wave 2 please see Canadian Health Measures Survey (CHMS) Cycle 1 Wave 2. Derived Variable (DV) Specifications.

For more information on the derived variable documentation for Wave 3 please see Canadian Health Measures Survey (CHMS) Cycle 1 Wave 3. Derived Variable (DV) Specifications.

For more information on the derived variable documentation for Wave 4 please see Canadian Health Measures Survey (CHMS) Cycle 1 Wave 4. Derived Variable (DV) Specifications.

For more information on the derived variable documentation for the Supplementary Data Release please see Canadian Health Measures Survey (CHMS) Cycle 1 Supplementary Data Release. Derived Variable (DV) Specifications.

Appendix 6 Questionnaires

For more information on the household or clinic questionnaires please see Questionnaire(s) and reporting guide(s) – Canadian Health Measures Survey (CHMS).

Appendix 7 Record layout

Appendix 8  Concordance table

Appendix 9 Response rates

Financial and Charitable Donors Databank of the Income Statistics Division User’s Guide

Table of contents

RRSP Contributors (product #17C0006)
RRSP Contribution Limits (ROOM) (product # 17C0011)
Canadian Savers (product #17C0009)
Canadian Investors (product #17C0007)
Canadian Investment Income (product #17C0008)
Canadian Capital Gains (product #17C0012)
Canadian Taxfilers (product #17C0010)
Charitable Donations
Data Source
Data Frequency
Data Quality
Confidentiality and Rounding
Glossary of Terms
Statistical Tables - Footnotes and Historical Availability
Geography
Geographic Levels – Postal Geography
Adding Postal Areas Without Duplication
Concordance Files
Old Walk / New Walk File
Geographic Levels – Census Geography
Geographic Levels – Special Geography
We Invite Your Comments
List of Data Products Available

Extracts from these statistical data may be reproduced for individual use without permission provided the source is fully acknowledged. Users are not authorized to transfer or redistribute any part or version of these data, in any medium, whether it be in their original form or in a modified form, except as approved under a distribution agreement with Statistics Canada. The prior written permission of Statistics Canada is required for any other form of publication or distribution.

Use of these data is acknowledgment that the user will be bound by the terms of the data licensing agreement which forms part of this documentation.

Statistics Canada
Income Statistics Division
saadinfo@statcan.gc.ca
November 2010

End-use Licence Agreement

Copyright

The Government of Canada (Statistics Canada) is the owner or a licensee of all intellectual property rights (including copyright) in this data product. With your payment of the requisite fee, you (hereinafter referred to as 'the Licensee') are granted a non-exclusive, non-assignable and non-transferable licence to use this data product subject to the terms below. This licence is not a sale of any or all of the rights of the owner(s).

Terms of use

  1. All copyright and proprietary notices, as well as all conditions of use associated with the data product, must be communicated to all users of the data product.

  2. The Licensee shall not transfer this data product to, or store the data product in, any electronic network for use by more than three (3) regular users unless the Licensee obtains prior written permission from Statistics Canada and pays any additional fees.

  3. The Licensee shall not lend, rent, lease, sublicense, transfer or sell any part of the data product nor any right granted under this agreement to any person outside the licensed organization or to any other organization.

  4. The Licensee shall not disassemble, decompile or in any way attempt to reverse engineer any software provided as part of the data product.

  5. The Licensee shall not use any part of the data product to develop or derive any other data product or data service for external distribution or commercial sale.

  6. The Licensee is granted reasonable rights of use of the content of this data product only for personal, corporate or public policy research, as well as for educational purposes. This permission includes the use of the content in analyses and in the reporting of results and conclusions, including the citation of limited amounts of supporting data, extracted from the data product, in such documents. In such cases, the source of the data must be acknowledged in all such documents and communications by providing the following source citation at the bottom of each table and graph:

    Source (or 'Adapted from,' if appropriate): Statistics Canada, (name of product), (catalogue number of product), (reference date of product).

  7. The Licensee shall obtain approval from Statistics Canada before publishing any significant volume of material, in any medium, that is extracted from the data product.

  8. The Licensee agrees not to merge or link the data product with any other databases in such a fashion that gives the appearance that the Licensee may have received, or had access to, information held by Statistics Canada about any identifiable individual, family, household, organization or business.

  9. Any violation of this licence renders it void and of no effect. This agreement will terminate automatically without notice if the Licensee fails to comply with any of the terms of this agreement. In the event of termination, the Licensee must immediately return the data product to Statistics Canada or destroy it and certify this destruction in writing to Statistics Canada.

Warranties and disclaimers

This data product is provided ‘as-is,’ and Statistics Canada makes no warranty, either express or implied, including but not limited to, warranties of merchantability and fitness for a particular purpose. In no event will Statistics Canada be liable for any direct, special, indirect, consequential or other damages, however caused.

Acceptance of terms

It is your responsibility to ensure that your use of this data product complies with these terms and to seek prior written permission from Statistics Canada for any uses not permitted or not specified in this agreement. Any infringement of Statistics Canada's rights may result in legal action.

Any use whatsoever of this data product shall constitute your acceptance of the terms of this agreement. Any violation of these terms may result in termination of this licence.

For further information please contact:

Licensing Services
Client Services Division, Statistics Canada
9th Floor, R.H. Coats Building
Ottawa, Ontario  K1A 0T6  Canada

E-mail: licensing@statcan.gc.ca
Telephone: 613-951-1122
Fax: 613-951-1134  
© Statistics Canada, 2010

RRSP Contributors (product #17C0006)

This databank provides information on taxfilers who contributed to a Registered Retirement Savings Plan (RRSP) during the tax year under review.

The content of the databank is as follows:

Table 1:  Summary
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Number of RRSP contributors
Column 8 – Average age of RRSP contributors
Column 9 – Median employment income of RRSP contributors
Column 10 – 75th percentile of employment income of RRSP contributors
Column 11 – Amount of RRSP dollars reported (in thousands of dollars)
Column 12 – Median RRSP contribution

Table 2:  Age groups
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Total number of RRSP contributors
Column 8 – Percent of contributors 0 to 24 years of age
Column 9 – Percent of contributors 25 to 34 years of age
Column 10 – Percent of contributors 35 to 44 years of age
Column 11 – Percent of contributors 45 to 54 years of age
Column 12 – Percent of contributors 55 to 64 years of age
Column 13 – Percent of contributors 65+ years of age
Column 14 – Total amount of RRSP dollars reported (in thousands of dollars)
Column 15 – Percent of contributions reported by age group 0 to 24
Column 16 – Percent of contributions reported by age group 25 to 34
Column 17 – Percent of contributions reported by age group 35 to 44
Column 18 – Percent of contributions reported by age group 45 to 54
Column 19 – Percent of contributions reported by age group 55 to 64
Column 20 – Percent of contributions reported by age group 65+

Table 3:  Sex
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Percent of taxfilers who are male
Column 8 – Percent of taxfilers who are female
Column 9 – Total number of RRSP Contributors
Column 10 – Percent of contributors who are male
Column 11 – Percent of contributors who are female
Column 12 – Total amount of RRSP dollars reported (in thousands of dollars)
Column 13 – Percent of contributions reported by males
Column 14 – Percent of contributions reported by females
Column 15 – Median RRSP contribution of all contributors
Column 16 – Median RRSP contribution of males
Column 17 – Median RRSP contribution of females

Table 4:  Income groups
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Total number of RRSP contributors
Column 8 – Percent of RRSP contributors with total income less than $20,000
Column 9 – Percent of RRSP contributors with total income between $20,000 and $39,999
Column 10 – Percent of RRSP contributors with total income between $40,000 and $59,999
Column 11 – Percent of RRSP contributors with total income between $60,000 and $79,999
Column 12 – Percent of RRSP contributors with total income $80,000+
Column 13 – Total amount of RRSP dollars reported (in thousands of dollars)
Column 14 – Percent of total RRSP amount reported by contributors with total income less than $20,000
Column 15 – Percent of total RRSP amount reported by contributors with total income between $20,000 and $39,999
Column 16 – Percent of total RRSP amount reported by contributors with total income between $40,000 and $59,999
Column 17 – Percent of total RRSP amount reported by contributors with total income between $60,000 and $79,999
Column 18 – Percent of total RRSP amount reported by contributors with total income $80,000+

RRSP Contribution Limits (ROOM) (product # 17C0011)

The Registered Retirement Savings Plan (RRSP) Room databank was created to provide information on the RRSP contribution limit (RRSP Room) available. This product can be used in conjunction with the RRSP databank which concentrates on the RRSP contributors.

In 1989, the legislation dictated that contribution limits for persons not contributing to a registered pension plan (RPP) or a Deferred Profit Sharing Plan (DPSP) was 20% of earned income to a maximum of $7,500. The limit for RPP and DPSP members was 20% of earned income to a maximum of $3,500 less the amount contributed by the employee to the RPP or DPSP.

Further amendments to the Income Tax Act relative to RRSPs, taking effect January 1, 1991, were intended to make RRSP contribution limits more equitable. The RRSP contribution limit was set at 18% of earned income for the previous tax year, to a set maximum minus the Pension Adjustment (PA). The PA represents the calculated value of the pension accrued through an RPP or a DPSP in the previous tax year.

Total RRSP Room represents the deduction limit that Canadians can claim with respect to contributions made to RRSPs. It does not include income eligible for transfers, such as retiring allowances and severance pay that may be rolled over into RRSPs. The sum of the deduction limit and rollovers represents the maximum amount that can be claimed as a deduction on line 208 of the income tax return.

Earned income in tax year New room Unused room Total room (for tax year+1)
1991 For 1992 pre1991 = 0 New room only
1992 For 1993 1991 to 1992 Unused room + new room
1993 For 1994 1991 to 1993 Unused room + new room
1994 For 1995 1991 to 1994 Unused room + new room
1995 For 1996 1991 to 1995 Unused room + new room
1996 For 1997 1991 to 1996 Unused room + new room
1997 For 1998 1991 to 1997 Unused room + new room
1998 For 1999 1991 to 1998 Unused room + new room
1999 For 2000 1991to 1999 Unused room + new room
2000 For 2001 1991 to 2000 Unused room + new room
2001 For 2002 1991 to 2001 Unused room + new room
2002 For 2003 1991 to 2002 Unused room + new room
2003 For 2004 1991 to 2003 Unused room + new room
2004 For 2005 1991 to 2004 Unused room + new room
2005 For 2006 1991 to 2005 Unused room + new room
2006 For 2007 1991 to 2006 Unused room + new room
2007 For 2008 1991 to 2007 Unused room + new room
2008 For 2009 1991 to 2008 Unused room + new room
2009 For 2010 1991 to 2009 Unused room + new room

Calculation of contribution limits

For 1990, maximum contributions are:

  • for non-participants in RPPs and DPSPs, the lesser of 20% of earned income and $7,500
  • for participants in RPPs and DPSPs, 20% of earned income to a maximum of $3,500; the maximum is reduced according to employee contributions to RPPs/DPSPs.

For 1991 to 2008:

New room = 18% of earned income - PA - PSPA

Percentage of earned income to a maximum of

  • $11,500 for 1991
  • $12,500 for 1992 and 1993
  • $13,500 for 1994
  • $14,500 for 1995
  • $13,500 for 1996
  • $13,500 for 1997
  • $13,500 for 1998
  • $13,500 for 1999
  • $13,500 for 2000
  • $13,500 for 2001
  • $13,500 for 2002
  • $14,500 for 2003
  • $15,500 for 2004
  • $16,500 for 2005
  • $18,000 for 2006
  • $19,000 for 2007
  • $20,000 for 2008
  • $21,000 for 2009

Where PA = Pension Adjustment, and PSPA = Past Service Pension Adjustment

Prior to tax year 2000 (Room 2001):

Total Room (for tax year+1) = Unused Room (from 1991 forward) + New Room

For tax years 2000 to 2009 (Room 2001 to Room 2010):

Total Room (for tax year+1) = Unused Room accumulated since 1991 + (18% of earned income – Pension adjustment) – Current tax year contributions excluding rollovers

Data source

Prior to the release of data for tax year 2000, the RRSP ROOM data were derived from a file received annually from the Canada Revenue Agency (CRA, formerly Canada Customs and Revenue Agency). CRA generated the data from an administrative system designed in response to changes to the Income Tax Act with respect to Registered Retirement Savings Plans, changes that took effect January 1, 1991.

The system records information for each taxfiler with "earned income" (income used to determine the RRSP deduction limit). The information includes each year's earned income, new room amounts and unused room amounts carried forward.

Starting with the 2001 ROOM (2000 tax data), the amount of RRSP Room is calculated from other variables on the preliminary file, variables which were previously unavailable.

This year’s release of the RRSP Room data is based on 2009 income tax returns. Contributions towards these limits can be made up to February 2011, to be reported on the 2010 tax returns. The mailing address at the time of filing is the basis for the geographic information in the tables.

Data quality

The calculated Room amount is equal to the amount on the Canada Revenue Agency (CRA) RRSP Room file.

The content of the databank is as follows:

Table 1: Persons with room
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk number
Column 4 – Level of geography (see Geography section)
Column 5 – Place name
Column 6 – Amount of Room dollars reported (in thousands of $)
Column 7 – Amount of Unused Room dollars reported (in thousands of $)
Column 8 – Amount of New Room dollars reported (in thousands of $)
Column 9 – Number of taxfilers with Room
Column 10 – Number of taxfilers with Unused Room
Column 11 – Number of taxfilers with New Room

Table 2: Characteristics of persons with new room
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk number
Column 4 – Level of geography (see Geography section)
Column 5 – Place name
Column 6 – Number of taxfilers with New Room
Column 7 – Average Age of taxfilers with New Room
Column 8 – Percentage Female taxfilers with New Room
Column 9 – Median Earned Income of taxfilers with New Room
Column 10 – Average New Room
Column 11 – Percentage of taxfilers with New Room between $500 and $2,399 1
Column 12 – Percentage of taxfilers with New Room between $2,400 and $4,699 2
Column 13 – Percentage of taxfilers with New Room between $4,700 and $7,799 3
Column 14 – Percentage of taxfilers with New Room between $7,800 and $12,999 4
Column 15 – Percentage of taxfilers with New Room greater than $13,000 5

Canadian Savers (product #17C0009)

Line 120 – Taxable amount of dividends from taxable Canadian corporations
Line 121 – Interest and other investment income

This databank provides information on taxfilers who have been classified as savers.

Savers are defined as taxfilers who reported interest and investment income on line 121, but no dividend income on line 120 of the personal income tax return.

Interest and investment income sources would include interest from Canada Savings bonds, bank accounts, treasury bills, investment certificates, term deposits, earnings on life insurance policies as well as foreign interest and dividend income.

Dividend income would include dividends from taxable Canadian corporations (as stocks or mutual funds), but not dividends from foreign investments.

Taxfilers reporting Canadian dividend income would not be counted as savers, but would be classified as investors.

The content of the databank is as follows:

Table 1: Summary
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Number of savers
Column 8 – Average age of savers
Column 9 – Median total income of savers
Column 10 – Total amount of interest dollars reported (in thousands of dollars)
Column 11 – Median of interest dollars

Table 2: Age groups
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Total number of savers
Column 8 – Percent of savers 0-24 years of age
Column 9 – Percent of savers 25-34 years of age
Column 10 – Percent of savers 35-44 years of age
Column 11 – Percent of savers 45-54 years of age
Column 12 – Percent of savers 55-64 years of age
Column 13 – Percent of savers 65+ years of age
Column 14 – Total amount of interest income dollars reported (in thousands of dollars)
Column 15 – Percent of interest income reported by age group 0-24
Column 16 – Percent of interest income reported by age group 25-34
Column 17 – Percent of interest income reported by age group 35-44
Column 18 – Percent of interest income reported by age group 45-54
Column 19 – Percent of interest income reported by age group 55-64
Column 20 – Percent of interest income reported by age group 65+

Table 3: Sex
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Percent of taxfilers who are male
Column 8 – Percent of taxfilers who are female
Column 9 – Total number of savers
Column 10 – Percent of savers who are male
Column 11 – Percent of savers who are female
Column 12 – Total amount of interest income reported (in thousands of dollars)
Column 13 – Percent of interest income reported by males
Column 14 – Percent of interest income reported by females
Column 15 – Median interest income of all savers
Column 16 – Median interest income of all male savers
Column 17 – Median interest income of all female savers

Table 4: Income groups
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Total number of savers
Column 8 – Percent of savers with total income less than $20,000
Column 9 – Percent of savers with total income between $20,000 and $39,999
Column 10 – Percent of savers with total income between $40,000 and $59,999
Column 11 – Percent of savers with total income between $60,000 and $79,999
Column 12 – Percent of savers with total income $80,000+
Column 13 – Total amount of interest income reported (in thousands of dollars)
Column 14 – Percent of interest income reported by savers with total income less than $20,000
Column 15 – Percent of interest income reported by savers with total income between $20,000 and $39,999
Column 16 – Percent of interest income reported by savers with total income between $40,000 and $59,999
Column 17 – Percent of interest income reported by savers with total income between $60,000 and $79,999
Column 18 – Percent of interest income reported by savers with total income $80,000+

Canadian Investors (product #17C0007)

Line 120 – Taxable amount of dividends from taxable Canadian corporations
Line 121 – Interest and other investment income

This databank provides information on taxfilers classified as investors.

Investors include taxfilers who reported dividend income on line 120 of their personal tax return. They may or may not have also reported interest and other investment income on line 121. When income is also reported on line 121, that amount is added to the amount of dividend income received, and the sum becomes the investment income of the investor.

The content of the databank is as follows:

Table 1: Summary
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk number
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Number of investors
Column 8 – Average age of investors
Column 9 – Median total income of investors
Column 10 – Amount of investment dollars (in thousands of dollars)
Column 11 – Percentage of the investment income derived from dividends
Column 12 – Median investment income

Table 2: Age groups
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Total number of investors
Column 8 – Percent of investors 0-24 years of age
Column 9 – Percent of investors 25-34 years of age
Column 10 – Percent of investors 35-44 years of age
Column 11 – Percent of investors 45-54 years of age
Column 12 – Percent of investors 55-64 years of age
Column 13 – Percent of investors 65+ years of age
Column 14 – Total amount of investment income dollars reported (in thousands of dollars)
Column 15 – Percent of investment income reported by age group 0-24
Column 16 – Percent of investment income reported by age group 25-34
Column 17 – Percent of investment income reported by age group 35-44
Column 18 – Percent of investment income reported by age group 45-54
Column 19 – Percent of investment income reported by age group 55-64
Column 20 – Percent of investment income reported by age group 65+

Table 3: Sex
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Percent of taxfilers who are male
Column 8 – Percent of taxfilers who are female
Column 9 – Total number of investors
Column 10 – Percent of investors who are male
Column 11 – Percent of investors who are female
Column 12 – Total amount of investment income reported (in thousands of dollars)
Column 13 – Percent of investment income reported by males
Column 14 – Percent of investment income reported by females
Column 15 – Median investment income of all investors
Column 16 – Median investment income of all male investors
Column 17 – Median investment income of all female investors

Table 4: Income groups
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Total number of investors
Column 8 – Percent of investors with total income less than $20,000
Column 9 – Percent of investors with total income between $20,000 and $39,999
Column 10 – Percent of investors with total income between $40,000 and $59,999
Column 11 – Percent of investors with total income between $60,000 and $79,999
Column 12 – Percent of investors with total income $80,000+
Column 13 – Total amount of investment income reported (in thousands of dollars)
Column 14 – Percent of investment income reported by investors with total income less than $20,000
Column 15 – Percent of investment income reported by investors with total income between $20,000 and $39,999
Column 16 – Percent of investment income reported by investors with total income between $40,000 and $59,999
Column 17 – Percent of investment income reported by investors with total income
between $60,000 and $79,999
Column 18 – Percent of investment income reported by investors with total income
$80,000+

Canadian Investment Income (product #17C0008)

Line 120 – Taxable amount of dividends from taxable Canadian corporations
Line 121 – Interest and other investment income

This databank provides information on taxfilers who reported dividend income on line 120 of the tax return, or interest and other investment income on line 121, or both. These taxfilers include those designated as savers and those designated as investors in two other databanks available: Canadian Savers and Canadian Investors. In this databank, investment income includes both interest and dividends.

Dividend income includes dividends from taxable Canadian corporations (as stocks or mutual funds).

Interest and other investment income sources include interest from Canada Savings bonds, bank accounts, treasury bills, investment certificates, term deposits, earnings on life insurance policies as well as foreign interest and dividend income.

The content of the databank is as follows:

Table 1: Summary
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Number of taxfilers with investment income
Column 8 – Average age of taxfilers with investment income
Column 9 – Median total income of taxfilers with investment income
Column 10 – Reported investment income dollars for all taxfilers with investment income (in thousands of dollars)
Column 11 – Median investment income for all taxfilers with investment income

Table 2: Age groups
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Total number of receivers of investment income
Column 8 – Percent of receivers of investment income 0-24 years of age
Column 9 – Percent of receivers of investment income 25-34 years of age
Column 10 – Percent of receivers of investment income 35-44 years of age
Column 11 – Percent of receivers of investment income 45-54 years of age
Column 12 – Percent of receivers of investment income 55-64 years of age
Column 13 – Percent of receivers of investment income 65+ years of age
Column 14 - Total amount of investment income dollars reported (in thousands of dollars)
Column 15 – Percent of investment income reported by age group 0-24
Column 16 – Percent of investment income reported by age group 25-34
Column 17 – Percent of investment income reported by age group 35-44
Column 18 – Percent of investment income reported by age group 45-54
Column 19 – Percent of investment income reported by age group 55-64
Column 20 – Percent of investment income reported by age group 65+

Table 3: Sex
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Percent of taxfilers who are male
Column 8 – Percent of taxfilers who are female
Column 9 – Total number of receivers of investment income
Column 10 – Percent of receivers of investment income who are male
Column 11 – Percent of receivers of investment income who are female
Column 12 – Total amount of investment income reported (in thousands of dollars)
Column 13 – Percent of investment income reported by males
Column 14 – Percent of investment income reported by females
Column 15 – Median investment income of all receivers of investment income
Column 16 – Median investment income of all male receivers of investment income
Column 17 – Median investment income of all female receivers of investment income

Table 4: Income groups
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Total number of receivers of investment income
Column 8 – Percent of receivers of investment income with total income less than $20,000
Column 9 – Percent of receivers of investment income with total income between $20,000 and $39,999
Column 10 – Percent of receivers of investment income with total income between $40,000 and $59,999
Column 11 – Percent of receivers of investment income with total income between $60,000 and $79,999
Column 12 – Percent of receivers of investment income with total income $80,000+
Column 13 – Total amount of investment income reported (in thousands of dollars)
Column 14 – Percent of investment income reported by receivers of investment income with total income less than $20,000
Column 15 – Percent of investment income reported by receivers of investment income with total income between $20,000 and $39,999
Column 16 – Percent of investment income reported by receivers of investment income with total income between $40,000 and $59,999
Column 17 – Percent of investment income reported by receivers of investment income with total income between $60,000 and $79,999
Column 18 – Percent of investment income reported by receivers of investment income with total income $80,000+

Canadian Capital Gains (product #17C0012)

Line 127 – Taxable amount of capital gains

This databank provides information on taxfilers who reported capital gains during the tax year under review.

Line 127 of the T1 income tax return contains the amount of taxable capital gains reported by Canadians; this value is half the actual capital gains received. The information in this databank reflects the total capital gains received; amounts reported have been grossed up to reflect this total.

The content of the databank is as follows:

Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Number of taxfilers reporting capital gains
Column 8 – Percent of taxfilers reporting capital gains who had a total income under $20,000
Column 9 – Percent of taxfilers reporting capital gains who had a total income between $20,000 and $39,999
Column 10 – Percent of taxfilers reporting capital gains who had a total income between $40,000 and $59,999
Column 11 – Percent of taxfilers reporting capital gains who had a total income between $60,000 and $79,999
Column 12 – Percent of taxfilers reporting capital gains who had a total income of $80,000+
Column 13 – Total value of capital gains (in thousands of dollars)
Column 14 – Percent of capital gains reported by taxfilers with a total income under $20,000
Column 15 – Percent of capital gains reported by taxfilers with a total income between $20,000 and $39,999
Column 16 – Percent of capital gains reported by taxfilers with a total income between $40,000 and $59,999
Column 17 – Percent of capital gains reported by taxfilers with a total income between $60,000 and $79,999
Column 18 – Percent of capital gains reported by taxfilers with a total income of $80,000+

Canadian Taxfilers (product #17C0010)

This databank provides a demographic and income profile of all Canadians who filed a personal tax return in the reference year.

The content of the databank is as follows:

Table 1: Summary
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk number
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Number of taxfilers
Column 7 – Percent of taxfilers 0-24 years of age
Column 8 – Percent of taxfilers 25-34 years of age
Column 9 – Percent of taxfilers 35-44 years of age
Column 10 – Percent of taxfilers 45-54 years of age
Column 11 – Percent of taxfilers 55-64 years of age
Column 12 – Percent of taxfilers 65+ years of age
Column 13 – Average age of taxfilers
Column 14 – Median total income of taxfilers
Column 15 – 75th percentile of total income of taxfilers
Column 16 – 85th percentile of total income of taxfilers
Column 17 – 95th percentile of total income of taxfilers
Column 18 – Median employment income of taxfilers
Column 19 – 75th percentile of employment income of taxfilers

Table 2: Income Groups
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk number
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Number of taxfilers
Column 7 – Percent of taxfilers with total income less than $20,000
Column 8 – Percent of taxfilers with total income between $20,000 and $39,999
Column 9 – Percent of taxfilers with total income between $40,000 and $59,999
Column 10 – Percent of taxfilers with total income between $60,000 and $79,999
Column 11 – Percent of taxfilers with total income $80,000+
Column 12 – Value of total income (in thousands of dollars)
Column 13 – Percent of total income reported by taxfilers with total income less than $20,000
Column 14 – Percent of total income reported by taxfilers with total income between $20,000 and $39,999
Column 15 – Percent of total income reported by taxfilers with total income between $40,000 and $59,999
Column 16 – Percent of total income reported by taxfilers with total income between $60,000 and $79,999
Column 17 – Percent of total income reported by taxfilers with total income $80,000+

Charitable Donations

Line 340 – Allowable charitable donations and government gifts

This databank provides information on taxfilers classified as charitable donors. Charitable donors are defined as taxfilers reporting donations on line 340 of the tax return.

Canadians contribute in many ways to charitable organizations. The databank on charitable donors provides information on taxfilers who claimed a tax credit for charitable donations on their income tax return in the reference year. These data may include donations that might be denied by the Canada Revenue Agency (CRA) after an audit. To find out more about why donations might be denied (i.e. tax shelter gifting arrangements, false receipting) please go to the Canada Revenue Agency website: www.cra-arc.gc.ca

Persons making charitable donations, but not reporting them on their personal tax return are not included in this databank. These include donations for which no receipt was provided and donations for which the receipt was lost. No estimate of such donations is included in these data.

Only donations made to approved organizations are allowable as deductions in the tax system. Donations are eligible if made to Canadian registered charities and Canadian amateur athletic associations. They are also eligible if made to: prescribed universities outside Canada; certain tax exempt housing organizations in Canada; Canadian municipalities; the United Nations; and certain charities outside Canada to which the Government of Canada has made a gift.

It is possible to carry donations forward for up to five years after the year in which they were made. In the reference year, it is possible to claim donations made in any of the previous five years, as long as they were not already claimed in a prior year. The donations made in the reference year could be claimed the same year, or could be carried forward to any of the next five years. According to tax laws, taxfilers are permitted to claim both their donations and those made by their spouses to get better tax benefits. Consequently, the number of persons who made charitable donations may be higher than the number who claimed tax credits.

A change in tax regulations was introduced in 2007. Taxfilers contributing to a recognized charity (as outlined above) were eligible to claim a tax credit of 15% of their donations on the first $200, and 29% on the rest. In 2006, the tax credit was 15.25% on the first $200 and 29% on the rest. In 2005, the tax credit was 15% on the first $200 and 29% on the rest. From 2001 to 2004, the tax credit was 16% on the first $200 and 29% on the rest. From 1992 to 2000, the tax credit was 17% on the first $200 and 29% on the rest. Previously, taxfilers had to give $250 to charity before the 29% credit was available.

The content of the databank is as follows:

Table 1: Summary
Column 1 - City identification number
Column 2 - Postal area
Column 3 - Postal walk number
Column 4 - Level of geography (see Geography section)
Column 5 - Place name
Column 6 - Total Number of taxfilers
Column 7 - Number of charitable donors
Column 8 - Average age of donors
Column 9 - Average donation for age group 0-24
Column 10 - Average donation for age group 25-34
Column 11 - Average donation for age group 35-44
Column 12 - Average donation for age group 45-54
Column 13 - Average donation for age group 55-64
Column 14 - Average donation for age group 65+
Column 15 - Total amount of charitable donations (thousands of $)
Column 16 - Median donation
Column 17 - Median total income of donors
Column 18 - 75th percentile of donors' total income

Table 2: Age and Sex (new beginning with 1995)
Column 1 - City identification number
Column 2 - Postal area
Column 3 - Postal walk number
Column 4 - Level of geography (see Geography section)
Column 5 - Place name
Column 6 - Total Number of taxfilers
Column 7 - Percent of taxfilers who are male
Column 8 - Percent of taxfilers who are female
Column 9 - Number of charitable donors
Column 10 - Percent of charitable donors who are male
Column 11 - Percent of charitable donors who are female
Column 12 - Percent of donors 0 - 24 years of age
Column 13 - Percent of donors 25 - 34 years of age
Column 14 - Percent of donors 35 - 44 years of age
Column 15 - Percent of donors 45 - 54 years of age
Column 16 - Percent of donors 55 - 64 years of age
Column 17 - Percent of donors 65+ years of age
Column 18 - Total median donation
Column 19 - Median donation of males
Column 20 - Median donation of females
Column 21 - Total amount of charitable donations (thousands of $)
Column 22 - Total amount of charitable donations for males (thousands of $)
Column 23 - Total amount of charitable donations for females (thousands of $)

Table 3: Income Groups (new beginning with 1997)
Column 1 - City identification number
Column 2 - Postal area
Column 3 - Postal walk number
Column 4 - Level of geography (see Geography section)
Column 5 - Place name
Column 6 - Total number of taxfilers
Column 7 - Total number of charitable donors
Column 8 - Percent of charitable donors with total income less than $20,000
Column 9 - Percent of charitable donors with total income between $20,000 and $39,999
Column 10 - Percent of charitable donors with total income between $40,000 and $59,999
Column 11 - Percent of charitable donors with total income between $60,000 and $79,999
Column 12 - Percent of charitable donors with total income $80,000+
Column 13 - Total value of charitable donations (in thousands of dollars)
Column 14 - Percent of donations reported by donors with total income under $20,000
Column 15 - Percent of donations reported by donors with total income between $20,000 and $39,999
Column 16 - Percent of donations reported by donors with total income between $40,000 and $59,999
Column 17 - Percent of donations reported by donors with total income between $60,000 and $79,999
Column 18 - Percent of donations reported by donors with total income $80,000+

Data Source

The financial databanks are derived from income tax returns. For the most part, tax returns were filed in the spring of the year following the reference year. For example, for the 2009 tax year, income tax returns were filed by April 30, 2010.

The mailing address at the time of filing is the basis for the geographic information in the tables.

Demographic characteristics such as age are given as of December 31 of the tax year. Income information is for the calendar year under review.

Data Frequency

Data are updated on an annual basis.

Data Quality

i) Number of Canadian taxfilers

The data used are direct counts from tax files. For the 2009 tax year, 24.3 million Canadians or 71.6% filed tax returns.

Figure 1 – Number of Canadian Taxfilers

Tax year Number of taxfilers ('000) Date of population estimate Population ('000) Coverage (%)
1991 18,786 April 1, 1992 28,270 66.5
1992 19,267 April 1, 1993 28,601 67.4
1993 19,882 April 1, 1994 28,907 68.8
1994 20,184 April 1, 1995 29,212 69.1
1995 20,536 April 1, 1996 29,514 69.6
1996 20,772 April 1, 1997 29,818 69.7
1997 21,113 April 1, 1998 30,080 70.2
1998 21,431 April 1, 1999 30,315 70.7
1999 21,893 April 1, 2000 30,594 71.6
2000 22,249 April 1, 2001 30,911 72.0
2001 22,804 April 1, 2002 31,252 73.0
2002 22,968 April 1, 2003 31,548 72.8
2003 23,268 April 1, 2004 31,846 73.1
2004 23,625 April 1, 2005 32,143 73.5
2005 23,952 April 1, 2006 32,471 73.8
2006 24,258 April 1, 2007 32,818 73.9
2007 24,624 April 1, 2008 33,187 74.2
2008 24,987 April 1, 2009 33,599 74.4
2009* 24,321 April 1, 2010 33,988 71.6

Percent coverage is based on a comparison of the number of taxfilers in the Income Statistics Division's taxfilers databank and the population estimates from the Statistics Canada CANSIM table 051-0005, now available on the Statistics Canada web site www.statcan.gc.ca.

* The 2009 count of taxfilers is taken from a preliminary 2009 tax file from the Canada Revenue Agency.

ii) Elderly population

Some elderly Canadians receiving only Old Age Security and Guaranteed Income Supplement do not file because they have low or no taxable income. However, with the introduction of the Federal Sales Tax (FST) Credit in 1986 and the Goods and Services Tax (GST) Credit in 1990, the percentage of the elderly population filing tax returns has increased. In 2008, approximately 95%of the population aged 65 and over filed tax returns, up from 75% in 1989 (when comparing the number of taxfilers aged 65 years or more with the corresponding population estimate to July 1, 2009, available on CANSIM 051-0001 from Statistics Canada).

Figure 2 ─ Coverage by Age and by Province, 2008

Rates of Coverage by Age
Age Rates of Coverage
under 20 101.9%
20-24 85.7%
25-29 87.9%
30-34 91.8%
35-39 95.5%
40-44 96.8%
45-49 94.6%
50-54 94.2%
55-59 93.3%
60-64 93.7%
65-74 96.2%
75+ 94.7%
Total 95.2%

 

Rates of Coverage by Province
Province Rates of Coverage
Newfoundland & Labrador 99.6%
Prince Edward Island 97.0%
Nova Scotia 95.7%
New Brunswick 97.7%
Quebec 97.0%
Ontario 94.6%
Manitoba 95.2%
Saskatchewan 96.9%
Alberta 94.0%
British Columbia 93.5%
Yukon 91.9%
Northwest Territories 93.9%
Nunavut 93.9%
Canada 95.2%

Coverage rates by age and by province are based on comparisons with the estimated population counts to July 1, 2009 available on CANSIM table 051-0001 from Statistics Canada.

iii) Income

Persons with low income have no tax liability and are not required to file tax returns. However, with the introduction of the Child Tax Credit in 1978, the Federal Sales Tax (FST) Credit in 1986, the Goods and Services Tax (GST) Credit in 1990, and the Child Tax Benefits in 1993, persons with low income are likely to file tax returns to apply for these credits.

Confidentiality and Rounding

Over the years since its creation, the T1 Family File (T1FF) has become known as a reliable, annual source for income and demographic estimates. To protect the confidentiality of Canadians, all data are subject to the confidentiality procedures of rounding and suppression.

Developmental work and testing resulted in different confidentiality procedures that were applied to the Financial and Charitable Donors databank for the reference year 2007; it consisted of introducing a certain distortion in the data instead of using the suppression method. However, when the new methodology was applied to the data of the other standard products of Income Statistics Division, the distortion component was no more an option due to the complexity of all the other databanks. Therefore, in an effort to harmonize the confidentiality rules across all the standard products of Income Statistics division, it has been decided to revert back to the suppression rules.

These measures maintain the confidentiality of the data. All counts are rounded. Rounding may increase, decrease, or cause no change to counts. Rounding can affect the results obtained from calculations. For example, when calculating percentages from rounded data, results may be distorted as both the numerator and denominator have been rounded. The distortion can be greatest with small numbers.

All reported amounts are rounded to the nearest $5,000 dollars.

Since 1990, data cells represent counts of 15 or greater, and are rounded to a base of 10. For example, a cell count of 15 would be rounded to 20 and a cell count of 24 would be rounded to 20.

Note: Counts represent the number of persons.
Reported amounts are aggregate dollar amounts reported.

In the data tables:

Medians, Percentiles and Average amount are rounded to the nearest ten dollars.

Percentages are published with no decimal and calculated on rounded data; therefore, the sum of percentages might not equal 100% in the case of small counts.

Suppressed Data

To maintain confidentiality, data cells have been suppressed whenever:

  • areas comprise less than 100 taxfilers;
  • cells represent less than 15 taxfilers6;
  • cells were dominated by a single filer.

Suppressed data may occur:

i) Within one area:

  • when one of the income categories is suppressed, a second category must also be suppressed to avoid disclosure of confidential data by subtraction (called residual disclosure);
  • when one of the gender categories is suppressed, the other gender category must also be suppressed to avoid residual disclosure;
  • when one age group category is suppressed, another age group must also be suppressed to avoid residual disclosure.

ii) Between areas:

  • when a variable amount in one area is suppressed, that variable amount is also suppressed in another area to prevent disclosure by subtraction.

Glossary of Terms

75th percentile

Total income values are ranked from highest to lowest and the value reported as being the 75th percentile indicates that 25% of the taxfilers report an income equal or above that amount and 75% fall below. Percentiles are calculated for each geographical level.

For example, if the 75th percentile of total income is shown as $60,000 this means that 25% of the population under review has a total income greater than or equal to $60,000 and 75% of the population has a total income less than or equal to $60,000.

85th percentile

Starting with the 2007 data, the dollar value of the 85th percentile appears in the tables instead of the percentage above the 85th percentile like it was in previous years. Total income values are ranked from highest to lowest and the value reported as being the 85th percentile indicates that 15% of the taxfilers report an income equal or above that amount and 85% fall below. Percentiles are calculated for each geographical level.

For example, if the 85th percentile of total income is shown as $65,000 this means that 15% of the taxfilers has a total income greater than or equal to $65,000

95th percentile

Starting with the 2007 data, the dollar value of the 95th percentile appears in the tables instead of the percentage above the 95th percentile like it was in previous years. Total income values are ranked from highest to lowest and the value reported as being the 95th percentile indicates that 5% of the taxfilers report an income equal or above that amount and 95% fall below. Percentiles are calculated for each geographical level.

For example, if the 95th percentile of total income is shown as $90,000 this means that 5% of the population under review has a total income greater than or equal to $90,000

Age

Calculated as of December 31 of the reference year (i.e., tax year minus year of birth).

Capital Gains

Line 127 of the T1 income tax return shows "taxable capital gains" or half of the capital gains actually received.  The information in this databank has been grossed up to represent the total capital gains received.

Charitable donation

Is the allowable portion of total donations, as reported on the income tax return.

Charitable donor

Is defined as a taxfiler reporting a charitable donation amount on line 340 of the personal income tax form.

City identification number (CityID)

Since municipality names can be, in some cases, quite long and cumbersome for handling in electronic files, municipalities are given a "city identification number". Starting in 2007, the CityID is a five digits alpha-numeric component. It is created with the first letter of postal code followed by “9” and a four digits number. Each first letter of postal code is allocated a range of number from 1 to 9999 (more explanation in geography section).

Deferred profit sharing plan (DPSP)

An employer-sponsored savings plan registered by the Canada Revenue Agency. Contributions to these plans by the employer (employees cannot contribute) are based on profits. The amount accumulated in these plans can be paid out as a lump sum at retirement or termination of employment, transferred to an RRSP, received in instalments over a period not to exceed ten years, or used to purchase an annuity.

Dividend income

Includes taxable amount of dividends (eligible and other than eligible) received from taxable Canadian corporations (as stocks or mutual funds) as reported on line 120 of the personal income tax return, and then grossed down to the actual amounts received; dividend income does not include dividends received from foreign investments (which are included in interest income and reported on line 121).

Earned income

The income used to determine the RRSP deduction limit. It includes such items as employment income (less union dues and expenses), net business and rental income, disability payments and alimony received. Alimony payments, current year business and rental losses are deducted from this amount. Most investment income (other than rents) is not considered earned income. In calculating the RRSP deduction limit, earned income from the previous year is used.

Employment income

The total reported employment income. Employment income includes wages and salaries, commissions from employment, training allowances, tips and gratuities, and self-employment income (net income from business, profession, farming, fishing and commissions) and Indian Employment Income (new in 1999).

Interest income

Amounts Canadians claimed on line 121 of the personal income tax return. This amount includes interest generated from bank deposits, Canada Savings Bonds, corporate bonds, treasury bills, investment certificates, term deposits, annuities, mutual funds, earnings on life insurance policies and all foreign interest and foreign dividend incomes.

Investment income

Includes both interest income and dividend income.

Investors

Taxfilers who reported dividend income on line 120 of their personal tax return. They may or may not have also reported interest and other investment income on line 121. When such income is reported on line 121, this amount is added to the amount of dividend income received, and the sum becomes the investment income of the investor.

Level of geography

A code designating the type of geographic area to which the information in the table applies. See the section on Geography for further information.

Median

The middle number in a group of numbers. Where a median income, for example, is given as $26,000, it means that exactly half of the incomes reported are greater than or equal to $26,000, and that the other half is less than or equal to the median amount. With the exception of "Total Income", zero values are not included in the calculation of medians for individuals.

New room

For 2009 is calculated as 18% of 2008 earned income (from definition above) to a maximum of $21,000 minus pension adjustment (PA) minus past service pension adjustment (PSPA). Since the focus of these data is for net new room for potential RRSP contributions, PA and/or PSPA details will be omitted.

Past service pension adjustment (PSPA)

Applies only to members of defined benefit RPPs. A PSPA occurs when the pension benefit is upgraded, or additional credits purchased, for service in past years. In the first case, it is called an exempt (from certification) PSPA; in the second case, a certifiable PSPA. Only service after 1989 is considered.

Pension adjustment (PA)

Calculated value of the pension accrued in the year in an RPP or a DPSP. The PA decreases the RRSP deduction limit. To calculate this limit, the PA from the previous year is used.

Registered disability savings plan income (RDSP)

It consists of an individual disability savings plan governed by RRSP investment rules. Private contributions that can be made by anyone are subject to a lifetime limit of $200,000. They will be matched in some degree by government contributions; the lifetime limit is $90,000. Contributions are not deductible and income earned in the plan will not be taxed while in the plan.

Registered pension plan (RPP)

An employer-sponsored plan registered with the Canada Revenue Agency and most commonly also with one of the pension regulatory authorities. The purpose of such plans is to provide employees with a regular income at retirement. The two main types of RPPs are called defined benefit (where the benefit formula is specified) and defined contribution (where only the contribution formula is defined).

Registered retirement savings plan (RRSP)

An individual retirement savings plan that is registered by the Canada Revenue Agency. It permits limited contributions, and income earned in the RRSP is exempt from tax until payments are received from the plan.

Savers

Taxfilers who reported interest and investment income on line 121 of the personal income tax return, but no dividend income on line 120.

Taxfiler

Individual who filed a personal income tax return for the reference year.

Total income

The reported amounts of income by taxfilers from any of the following sources:

  • Labour force income;
    • Employment income;
      • Wages, salaries and commissions;
      • Other employment income as reported on line 104 of the tax form (tips, gratuities, royalties, etc.);
      • Net self-employment income;
      • Indian Employment Income (beginning in 1999);
    • Employment Insurance (EI) benefits;
  • Pension income;
    • Old Age Security/Net Federal Supplements (the latter including guaranteed income supplements and spouses' allowances since 1994);
    • Canada/Quebec Pension Plans;
    • Superannuation and other (private) pensions;
  • Family Allowance benefits (up to and including 1992);
  • Interest and other investment income;
  • Dividend income;
  • RRSP income (since 1999, for taxfilers 65+ only);
  • Net limited partnership income;
  • Alimony;
  • Net rental income;
  • Other income (e.g. alimony, and incomes reported on line 130, such as fellowships, bursaries, grants, etc.);
  • Federal Sales Tax (FST) credit (for 1989-1990 inclusive);
  • Goods and Services Tax (GST) credit (beginning in 1990);
  • Harmonized Sales Tax (HST) credit (beginning in 1997);
  • Child tax credit (up to and including 1992);
  • Canada child tax benefit (starting with 1993);
  • Provincial refundable tax credits (beginning in 1994);
  • Other non-taxable income (beginning in 1993);
    • Workers' compensation payments;
    • Social assistance payments;
    • Guaranteed income supplements;
    • Spouses' allowances;
  • Universal child care benefit (beginning in 2006);
  • Registered disability savings plan income (beginning in 2008)

Total room (in thousands of dollars)

The sum of "new room" and "unused room" as defined here.

Total room (number of persons)

The number of taxfilers who have either unused room from previous years, new room based on their earned income, or both. The number of persons with total room does not correspond to the sum of persons with new room and unused room, as an individual can be included in both categories.

Universal Child Care Benefit

Beginning in July 2006, the Universal Child Care Benefit (UCCB) is a taxable amount of $100 paid monthly for each child under 6 years of age. Included in Canada Child Tax Benefits in the statistical tables.

Unused RRSP contribution room (unused room)

The amount of the RRSP deduction limit that is not claimed by the taxfiler, or the amount remaining after subtracting actual contributions claimed on the tax return from that year's contribution room. Unused room can be carried forward indefinitely. The first year of unused room is from 1991 (see table).

Statistical Tables - Footnotes and Historical Availability

RRSP Contributors

  1. Table 1 is available in its current format starting with the 1990 data, according to the postal geography. Census metropolitan areas (CMAs) are available starting with the 1993 data, census divisions (CDs) with the 1994 data and federal electoral districts (FEDs) with the 1997 data.
  2. Table 2 (age groups) and table 3 (sex) are available in their current formats starting with the 1994 data, for postal areas, CMAs, CDs and FEDs (since 1997). Some changes were made to the age groupings over the years.
  3. Table 4 (income groups) is available in its current format starting with the 2007 data, for postal areas, CMAs, CDs and FEDs. From 1997 to 2006, the income groups were cumulative.

RRSP Contribution Limits (Room)

  1. Both tables are available in their current format starting with the 1993 data.
  2. Data are available for all levels of the postal geography starting with the 1993 tax year.
  3. Data for census metropolitan areas (CMAs) are available starting with the 1993 tax year (1994 room), census divisions (CDs) with the 1994 tax year (1995 room) and federal electoral districts (FEDs) with the 1997 tax year (1998 room).
  4. The figures in Table 2 ($500, $2,400, $4,700, $7,800 and $13,000) represent the 25th, 50th, 75th, 90th and 97th percentiles of new room and are recalculated periodically.

Canadian Savers

  1. Table 1 is available in its current format starting with the 1990 data, according to the postal geography. Census metropolitan areas (CMAs) are available starting with the 1993 data, census divisions (CDs) with the 1995 data and federal electoral districts (FEDs) with the 1997 data.
  2. Table 2 (age groups) and table 3 (sex) are available in their current formats starting with the 1995 data, for postal areas, CMAs, CDs and FEDs (since 1997). Some changes were made to the age groupings over the years.
  3. Table 4 (income groups) is available in its current format starting with the 2007 data, for postal areas, CMAs, CDs and FEDs. From 1997 to 2006, the income groups were cumulative.

Canadian Investors

  1. Table 1 is available in its current format starting with the 1990 data, according to the postal geography. Census metropolitan areas (CMAs) are available starting with the 1993 data, census divisions (CDs) with the 1995 data and federal electoral districts (FEDs) with the 1997 data.
  2. The proportion of investment income from dividends is available starting with the 1996 data (Table 1).
  3. Table 2 (age groups) and table 3 (sex) are available in their current formats starting with the 1995 data, for postal areas, CMAs, CDs and FEDs (since 1997). Some changes were made to the age groupings over the years.
  4. Table 4 (income groups) is available in its current format starting with the 2007 data, for postal areas, CMAs, CDs and FEDs. From 1997 to 2006, the income groups were cumulative.

Canadian Investment Income

  1. Table 1 is available in its current format starting with the 1990 data, according to the postal geography. Census metropolitan areas (CMAs) are available starting with the 1993 data, census divisions (CDs) with the 1995 data and federal electoral districts (FEDs) with the 1997 data.
  2. Table 2 (age groups) and table 3 (sex) are available in their current formats starting with the 1995 data, for postal areas, CMAs, CDs and FEDs (since 1997). Some changes were made to the age groupings over the years.
  3. Table 4 (income groups) is available in its current format starting with the 2007 data, for postal areas, CMAs, CDs and FEDs. From 1997 to 2006, the income groups were cumulative.

Canadian Capital Gains

  1. The standard table on capital gains by income group is available in its current format starting with the 2007 data. From 1998 data up to 2006, the income groups were cumulative.
  2. All levels of geography are available since the 1998 data, including census divisions, census metropolitan areas, federal electoral districts and all levels of the postal geography.

Canadian Taxfilers

  1. Table 1 is available in its current format starting with the 1990 data, according to the postal geography. Census metropolitan areas (CMAs) are available starting with the 1993 data, census divisions (CDs) with the 1995 data and federal electoral districts (FEDs) with the 1997 data.
  2. Starting with the 2007 data, the column on the “% reporting in French” in table 1 has been suppressed.
  3. Table 2 (income groups) is available in its current format starting with the 2007 data, for postal areas, CMAs, CDs and FEDs. From 1997 to 2006, the income groups were cumulative.

Charitable Donations

  1. Table 1 (summary) is available starting with the 1990 data, according to the postal geography. Census metropolitan areas (CMAs) are available starting with the 1993 data, census divisions (CDs) with the 1995 data and federal electoral districts (FEDs) with the 1997 data.
  2. Changes were made to the age groups in table 1 in 1991 and in 1997.
  3. Table 2 (age groups) is available starting with the 1995 data, for the postal geography and for CMAs. CDs are available starting with the 1995 data and FEDs with the 1997 data.
  4. Changes were made to the age groups in table 2 in 1997.
  5. Table 3 (Income groups) is available in its current format starting with the 2007 data, for the postal geography, for CMAs, CDs and FEDs. From 1997 to 2006, the income groups were cumulative.

Geography

The data are available for the following geographic areas. See "Statistical Tables - Footnotes and Historical Availability" for further details. The mailing address at the time of filing is the basis for the geographic information in the tables.

Standard areas:

  1. Canada,
  2. Provinces and territories,
  3. Census divisions,
  4. Census metropolitan areas,
  5. Federal electoral districts, and
  6. Postal geography.

User-defined areas:

Users may select a specific area of interest that is not a standard area for which data can be made available in standard format. To obtain data, provide us with a list of the postal codes for which data are required and we will provide the aggregated data. Of course, the area must satisfy our confidentiality requirements, or no data can be produced. See the "Special Geography" section for further information.

Geographic Levels – Postal Geography

The various databanks compiled from the taxfile are available for different levels of the postal geography, and for some levels of the Census geography. Coded geographic indicators appearing on the data tables are shown below with a brief description.

Level of Geography (L.O.G.) Postal Area Description
12 Canada This level of data is an aggregation of the provincial/territorial totals (code 11). The national total is identified by the region code Z99099.
11 Province or Territory Total

This level of data is an aggregation of the following geographies within a province:

City Totals (Code 08)
Rural Postal Codes (Code 09)
Other Provincial Totals (Code 10)

These totals are identified by a provincial/territorial postal letter, then a "990" followed by the province/territory code, as follows:

Newfoundland and Labrador (A99010)
Nova Scotia (B99012)
Prince Edward Island (C99011)
New Brunswick (E99013)
Quebec (J99024)
Ontario (P99035)
Manitoba (R99046)
Saskatchewan (S99047)
Alberta (T99048)
British Columbia (V99059)
Northwest Territories (X99061)
Nunavut (X99062)
Yukon Territory (Y99060)

10 Other Provincial Total ("P" Pot)

This level of data is an aggregation of small communities in the province that had less than 100 taxfilers, where these communities are combined into a "pot". Before 1992, it was identified by the same codes as the provincial/territorial totals, and only the "Delivery Mode" codes 2 and 3 distinguished between the two. To avoid this problem, starting with the 1992 data, an "8" appears after the provincial/territorial letter instead of a "9". The "9" will be reserved for the provincial/territorial total, as explained in 11 above. These "pot" codes are as follows:

Newfoundland and Labrador (A89010)
Nova Scotia (B89012)
Prince Edward Island (C89011)
New Brunswick (E89013)
Quebec (J89024)
Ontario (P89035)
Manitoba (R89046)
Saskatchewan (S89047)
Alberta (T89048)
British Columbia (V89059)
Northwest Territories (X89061)
Nunavut (X89062)
Yukon Territory (Y89060)

09 Rural Postal Code (Not in City )

This level of geography pertains to rural communities that have one and only one rural postal code. These stand-alone rural postal codes can be identified by a "zero" in the second position of the postal code and a level of geography code 09.

The 2009 databanks contain 4,012 areas coded as level of geography 09.

08 City Total

This level of data is an aggregation of the following geographies for unique place names within a province/territory:

Urban FSA (Residential) (Code 03)
Rural Route (Code 04)
Suburban Services (Code 05)
Rural Postal Code (within city) (Code 06)
Other Urban Area (Code 07)

They have the following format: e.g., Edmonton = T95479; Regina = S94876. The pattern is the postal letter of the city plus "9" in the second position (indicating a total), followed by a 4 digit numeric code for the community (often called "CityID").

In general, postal cities do not coincide with census subdivisions.

The 2009 databanks contain 1,590 areas coded as level of geography 08.

07 Other Urban Area (Non-residential within city - "E" Pot)

This aggregation of data (or "pot") covers non-residential addresses within an urban centre and all other data not otherwise displayed. Commercial addresses, post office boxes and general delivery are included, as are residential addresses with too few taxfilers to report separately. They can be recognized by codes that are similar to the city totals, with a distinguishing difference: an "8" will follow the city postal letter rather than the "9" of the city total (e.g., Edmonton = T85479; Regina = S84876).

The 2009 databanks contain 459 areas coded as level of geography 07.

06 Rural Postal Code (Within City)

These data pertain to rural postal codes that belong to communities with more than one rural postal code. These occur in areas that were formerly serviced by rural delivery service and changed by Canada Post to urban delivery service or in communities served by more than one rural postal code. Rural postal codes of this type can be identified by a "zero" in the second position of the postal code and a level of geography code 06.

The 2009 databanks contain 467 areas coded as level of geography 06.

05 Suburban Service

Sparsely populated fringe areas of urban centres may receive their postal service from an urban post office by delivery designated as "suburban service". Their region code retains all six characters of the postal code. Suburban Services are usually near or on the perimeters of urban areas, and mail is delivered by a contractor to group mail boxes, community mail boxes and/or external delivery sites (e.g., kiosks, miniparks).

The 2009 databanks contain 80 areas coded as level of geography 05.

04 Rural Route

Reasonably well-settled rural areas may receive their postal service from an urban post office by delivery designated as "rural route". Mail is delivered by a contractor to customers living along or near well-defined roads. Their region code retains all six characters of the postal code.

The 2009 databanks contain 713 areas coded as level of geography 04.

03 Urban FSA (Residential Area)

The urban Forward Sortation Area (FSA, identified by the first three characters of the postal code) includes all residential addresses covered by the first three characters of a postal code in a particular urban area (not including levels 04 and 05). Only residential FSAs are considered for these databanks. This level of data is an aggregation of:

Postal Walk (Code 01)
Other Postal Walk (Code 02)

An Urban FSA of this type can be identified by the FSA followed by three blanks.

The 2009 databanks contain 2,397 areas coded as level of geography 03.

02 Other Postal Walk

This level of data is an aggregation of urban residential postal codes unallocated to a letter carrier route and postal walks with less than 100 taxfilers. A postal walk record of this type can be identified by the FSA followed by three blanks, and the postal walk number "XXXX".

The 2009 databanks contain 197 areas coded as level of geography 02.

01 Postal Walk

This is the finest level of data and is an aggregation of urban residential postal codes allocated to a letter carrier route. A postal walk of this type can be identified by a region code which is the FSA followed by three blanks, and the postal walk number. An average FSA contains 11 walks.

The 2009 databanks contain 21,839 areas coded as level of geography 01.

Adding Postal Areas Without Duplication

Data files according to the postal geography will often contain subtotals and totals. Many data users need to add certain geographies in order to come up with a total for their particular area of interest. However, including subtotals during this process results in double-counting some populations, and this leads to an erroneous total. The following is a summary of which postal areas are aggregations in the standard postal geography.

Postal walks (Level of Geography, or LOG 1) and walk pots (LOG 2) add up to urban Forward Sortation Areas (FSAs, LOG 3).

Urban FSAs (LOG 3), rural routes (LOG 4), suburban services (LOG 5), rural postal codes within a city (LOG 6) and other urban areas (LOG 7) add up to city totals (LOG 8).

City totals (LOG 8), rural postal codes not in a city (LOG 9) and other areas in a province (LOG 10) add up to provincial/territorial totals (LOG 11).

Provincial/territorial totals (LOG 11) add up to the Canada total (LOG 12).

Thus, using the Level of geography codes:
1 + 2 = 3
3 + 4 + 5 + 6 + 7 = 8
8 + 9 + 10 = 11

Geography for small area and administrative data

City identification number (CityID)

As of 2007, CityID has been modified.

Previous to 2007:

  1. CityID was a 4 digits number
  2. Each municipality had a unique number between 1 and 9999
  3. Almost every number was allocated to a municipality. Few numbers remained available for future new municipalities.

Starting with 2007data:
To create more possibilities without changing the CityID length in our systems:

  1. CityID number is now combined with 1st letter of postal code
  2. Each 1st letter of postal code has a possibility of numbers, ranged from 1 to 9999 (Table 2)
  3. Old numbers have been kept for existing municipality and 1st letters of postal code have been added to them (Table 1)
  4. New municipalities have been assigned a new CityID number in new format (Table 1)
Table 1
Postal Code Municipality name 2006 and Prior 2007 and Follow
K1A 1K6 Ottawa 2434 K2434
G3C 0A1 Stoneham-et-Tewkesbury n/a G2

 

Table 2
Province Letter file Range of number
Newfoundland & Labrador A 1 – 9999
Prince Edward Island C 1 – 9999
Nova Scotia B 1 – 9999
New Brunswick E 1 – 9999
Quebec G 1 – 9999
Quebec H 1 – 9999
Quebec J 1 – 9999
Ontario K 1 – 9999
Ontario L 1 – 9999
Ontario M 1 – 9999
Ontario N 1 – 9999
Ontario P 1 – 9999
Manitoba R 1 – 9999
Saskatchewan S 1 – 9999
Alberta T 1 – 9999
British Columbia V 1 – 9999
Yukon Y 1 – 9999
Northwest Territories X 1 – 9999
Nunavut X 1 – 9999

Therefore, it is now essential to identify a municipality by adding the postal code 1st letter to the number in order to get the proper municipality in the proper province (Table 3):

Table 3
Letter Number Municipality name Province
A 2 Avondale NL
B 2 Bible Hill NS
T 2 Rocky View AB
G 2 Stoneham-et-Tewkesbury QC

Concordance Files

A concordance file accompanies data that are aggregated by postal walk. This file lists all of the six-character postal codes for which there is information, and identifies the postal walk to which each postal code is assigned. An urban Forward Sortation Area (FSA) may be split between two or more municipalities, and so the FSA label as well as the city identification number (or CityID) becomes important parts of the geographic identifiers. It is a combination of CityID, FSA label and postal walk number that creates unique geographic identifiers. The concordance file consists therefore of the CityID, the FSA label (called the postal area), the postal walk number and the six-character urban postal code. By simply browsing the concordance file, one can determine which postal codes make up a given walk. The following illustration is an example of a concordance file.

CityID Postal area Postal walk Postal code
K6092 K1B 52 K1B3K5
K6092 K1B 52 K1B3V5
K6092 K1B 52 K1B4C6
K6092 K1B 52 K1B4N7
K6092 K1B 52 K1B4N9
K6092 K1B 52 K1B4M8
K6092 K1B 52 K1B4N9

Vintage of the Postal Walks

The postal walks represented in the 2008 databanks were coded from a March 2009 Canada Post Corporation file.

Old Walk / New Walk File

Since postal walks are subject to change, we will also supply on request, along with postal walk aggregated data and the corresponding concordance file, a third file called the Old walk/New walk file. This file shows the percentage change in the postal walks between the date of the walks to which the data are attached and the latest such information available to us from Canada Post. This file compares the six-character urban postal codes that make up the postal walk at two different points in time. It shows the percentage of the postal codes from the original (old) walk that are included in the newer walk, and the percentage of the new walk that is derived from the old. The following illustration is an example of an old walk/new walk file.

Comparison Between Old Walks (Month XXXX) and New Walks (Month YYYY)
CityID FSA Old walk # New walk # % of old included in new % of new derived from old
K2434 K1B 50 50 94 74
K2434 K1B 50 51 6 8
K2434 K1B 51 50 33 26
K2434 K1B 51 51 61 92
K2434 K1B 51 57 6 5
K2434 K1B 57 57 91 50
K2434 K1B 57 58 9 100
K2434 K1B 52 52 29 10
K2434 K1B 52 60 71 100
K2434 K1B 53 52 20 24
K2434 K1B 53 53 60 100
K2434 K1B 53 58 20 33
K2434 K1B 54 54 93 83
K2434 K1B 54 55 7 5
K2434 K1B 55 55 100 89
K2434 K1B 56 52 30 14
K2434 K1B 56 56 70 100
K2434 K1B 58 52 12 10
K2434 K1B 58 55 12 5

Geographic Levels – Census Geography

Data are also available for the following levels of the Census geography; the following table shows the coded designators for these geographies, as well as a brief description of each.

Level of Geography (L.O.G.) Name Description
61 Census Tract

Census tracts (CTs) are small geographic units representing urban or rural neighbourhood-like communities in census metropolitan areas (see definition below) or census agglomerations with an urban core population of 50,000 or more at time of 1996 Census. CTs are delineated by a committee of local specialists (such as planners, health and social workers and educators) in conjunction with Statistics Canada.

The 2009 databanks contain 4,990 areas coded as level of geography 61, based on 2006 Census.

51 Economic Region

An economic region is a grouping of complete census divisions (see definition below) with one exception in Ontario. Economic regions (ERs) are used to analyse regional economic activity. Within the province of Quebec, ERs are designated by law. In all other provinces, they are created by agreement between Statistics Canada and the provinces concerned. Prince Edward Island and the territories each consist of one economic region.

The 2009 databanks contain 76 areas coded as level of geography 51, based on 2006 Census.

42 Census Agglomeration

The general concept of a census agglomeration (CA) is one of a very large urban area, together with adjacent urban and rural areas that have a high degree of economic and social integration with that urban area. CAs have an urban core population of at least 10,000, based on the previous census.

The 2009 databanks contain 117 areas coded as level of geography 42, based on 2006 Census.

41 Census Metropolitan Area

The general concept of a census metropolitan area (CMA) is one of a very large urban area, together with adjacent urban and rural areas that have a high degree of economic and social integration with that urban area. CMAs have an urban core population of at least 100,000, based on the previous census.

There are 35 CMAs in the 2009 databanks (2006 Census):

001, St. John's, Newfoundland
205, Halifax, Nova Scotia
305, Moncton, New Brunswick
310, Saint John, New Brunswick
408, Saguenay, Québec
421, Québec, Québec
433, Sherbrooke, Québec
442, Trois-Rivières, Québec
462, Montréal, Québec
505, Ottawa-Gatineau (Québec part)
505, Ottawa-Gatineau (Ontario part)
505, Ottawa-Gatineau (Combined)
521, Kingston, Ontario
529, Peterborough, Ontario
532, Oshawa, Ontario
535, Toronto, Ontario
537, Hamilton, Ontario
539, St-Catharines-Niagara, Ontario
541, Kitchener, Ontario
543, Brantford, Ontario
550, Guelph, Ontario
555, London, Ontario
559, Windsor, Ontario
568, Barrie, Ontario
580, Greater Sudbury, Ontario
595, Thunder Bay, Ontario
602, Winnipeg, Manitoba
705, Regina, Saskatchewan
725, Saskatoon, Saskatchewan
825, Calgary, Alberta
835, Edmonton, Alberta
915, Kelowna, British Columbia
932, Abbotsford-Mission, British Columbia
933, Vancouver, British Columbia
935, Victoria, British Columbia

31 Federal Electoral District

A federal electoral district (FED) refers to any place or territorial area represented by a member of Parliament elected to the House of Commons. There are 308 FEDs in Canada according to the 2003 Representation Order. The Representation Order is prepared by the Chief Electoral Officer describing, naming and specifying the population of each electoral district established by the Electoral Boundaries Commission and sent to the Governor in Council.

The 2009 databanks contain 308 areas coded as level of geography 31.

21 Census Division

A census division (CD) is a group of neighbouring municipalities joined together for the purposes of regional planning and managing common services (such as police or ambulance services). A CD might correspond to a county, a regional municipality or a regional district.

CDs are established under laws in effect in certain provinces and territories of Canada. In other provinces and territories where laws do not provide for such areas (Newfoundland, Manitoba, Saskatchewan and Alberta), Statistics Canada defines equivalent areas for statistical reporting purposes in cooperation with these provinces and territories.

The 2009 databanks contain 288 areas coded as level of geography 21, based on the 2006 Census.

Starting in 2008, Census divisions are identified in the tables by an eight digits code:
2 first digits = Province
2 next digits = Economic Region
2 last digits = Census Division

Geographic Levels – Special Geography

Clients may select geographical areas of their own definition; areas that are not part of the standard areas listed here (for example, bank service areas, retail store catchment areas). For this, clients must submit a list of the postal codes that make up their special area, and we will aggregate the micro data to correspond to that area of interest. Information ordered for special, or "user-defined" areas will be coded according to the following:

Level of Geography Name Description
93 Total for all user-defined areas This level represents the sum total of all user-defined areas, and is the total of levels 91 and 92 described below.
92 Other user-defined areas This level of geography represents all user-defined areas that were too small, in terms of population; to have information compiled on those areas individually (i.e. fewer than 100 taxfilers). Such areas are grouped into this "other" category.
91 Special user-defined area Any area showing a code "91" is an area defined by a specific user according to that user's needs (for example, school catchment areas, health districts, etc.)

Conversion files

When a client is interested in purchasing data for areas that are considered non‑standard geography by Income Statistics Division, a conversion file is usually necessary. A combination of postal codes making up one or more special area(s) is commonly referred to as a conversion file – an electronic file used by our staff to aggregate the different postal codes that make up the user-defined area. Simply provide us with the postal codes related to the area and we will compile the data (subject to our confidentiality restrictions). This list should include all postal codes for each area.

This would apply only to an area that is not a standard area. It could include any one or a combination of areas whose boundaries are a combination of standard areas or a combination of postal codes. User-defined areas may be branch service or school catchment areas, neighbourhoods or almost any other region.

Each postal code on a conversion file is linked to a corresponding area code. The postal code is used as the basis for the tabulation of economic and demographic data for each area. Refer to the example below for a typical conversion file received by the Income Statistics Division.

Postal code User Area
A1A1A1 0001
A1A1A2 0001
A1A1A3 0001
A1A1A4 0001
A1A1A5 0001
A1A1A6 0001
A1A1A7 0002
A1A1A8 0002
A1A1A9 0002
A1A1B1 0002
A1A1B2 0002
A1A1B3 0003
A1A1B4 0003
A1A1B5 0003
A1A1B6 0003
A1A1B7 0003
A1A1B8 0004
A1A1B9 0004
A1A1C1 0004
A1A1C2 0004
A1A1C3 0004
Note:
1. The conversion file should have a record length of 10 bytes. The first six bytes should represent the postal code and the following four bytes should represent the user-defined area.
2. The postal code does not have a space between the third and fourth characters.
3. The user-defined area code is only four characters in length.
Our system cannot accommodate user-defined areas with hierarchical levels.  In the previous example, areas 0001 and 0002 could not add up to their own total, with areas 0003 and 0004 adding up to their own separate total. Generating this type of hierarchical information means submitting this conversion file to our programs several times and increasing costs.

We Invite Your Comments

We are always working on ways to improve our products. The comments we receive concerning quality and presentation are essential to meet this objective. If you have any suggestions in this regard, we encourage you, the user, to provide us with your comments.

Data in many forms

Statistics Canada disseminates data in a variety of forms. In addition to publications, both standard and special tabulations are offered. Data are available on the Internet, compact disk, diskette, computer printouts, microfiche and microfilm and magnetic tape. Maps and other geographic reference materials are available for some types of data. Direct online access to aggregated information is possible through CANSIM, Statistics Canada's machine-readable database and retrieval system.

How to obtain more information

Inquiries about these data and related statistics or services should be directed to:

Client Services
Small Area and Administrative Data Division
Statistics Canada
Room 1306, Main Building
Ottawa, Ontario K1A 0T6

Telephone: (613) 951-9720
Toll-Free (866) 652-8443
Fax: (613) 951-4745
Toll-Free (866) 652-8444
saadinfo@statcan.gc.ca

National enquiries line 1-800-263-1136
National telecommunications device for the hearing impaired 1-800-363-7629
National Toll-free Fax line 1-877-287-4369

You can also visit us on the web: http://www.statcan.gc.ca.

Standards of service to the public

Statistics Canada is committed to serving its clients in a prompt, reliable and courteous manner and in the official language of their choice.  To this end, the agency has developed standards of service which its employees observe in serving its clients.  To obtain a copy of these service standards, please contact your nearest Statistics Canada Regional Reference Centre.

List of Data Products Available

The Income Statistics Division of Statistics Canada tabulates statistical data derived from administrative records - most notably, the taxfile.  The resulting demographic and socio-economic databanks available are listed in the table below, along with their identifying product number and the usual release dates.

Product name Product number Release date
RRSP Contributors 17C0006 Fall
RRSP Contribution Limits (Room) 17C0011 Fall
Canadian Savers 17C0009 Fall
Canadian Investors 17C0007 Fall
Canadian Investment Income 17C0008 Fall
Canadian Taxfilers 17C0010 Fall
Canadian Capital Gains 17C0012 Fall
Charitable Donors 13C0014 Fall
Neighbourhood Income and Demographics 13C0015 Spring
Economic Dependency Profiles 13C0017 Spring
Labour Income Profiles 71C0018 Spring
Families 13C0016 Spring
Seniors 89C0022 Spring
Migration Estimates 91C0025 Fall

 


Notes:

1. The first value represents the 25th percentile and is recalculated periodically.

2. The first value represents the 50th percentile and is recalculated periodically.

3. The first value represents the 75th percentile and is recalculated periodically.

4. The first value represents the 90th percentile and is recalculated periodically.

5. The first value represents the 97th percentile and is recalculated periodically.

6. Likewise, the median income is omitted when the rounded count of a category is less than 20.

 

Financial and Charitable Donors Databank of the Income Statistics Division User’s Guide

Table of contents

RRSP Contributors (product #17C0006)
RRSP Contribution Limits (ROOM) (product # 17C0011)
Canadian Savers (product #17C0009)
Canadian Investors (product #17C0007)
Canadian Investment Income (product #17C0008)
Canadian Capital Gains (product #17C0012)
Canadian Taxfilers (product #17C0010)
Charitable Donations
Data Source
Data Frequency
Data Quality
Confidentiality and Rounding
Glossary of Terms
Statistical Tables - Footnotes and Historical Availability
Geography
Geographic Levels – Postal Geography
Adding Postal Areas Without Duplication
Concordance Files
Old Walk / New Walk File
Geographic Levels – Census Geography
Geographic Levels – Special Geography
We Invite Your Comments
List of Data Products Available

Extracts from these statistical data may be reproduced for individual use without permission provided the source is fully acknowledged. Users are not authorized to transfer or redistribute any part or version of these data, in any medium, whether it be in their original form or in a modified form, except as approved under a distribution agreement with Statistics Canada. The prior written permission of Statistics Canada is required for any other form of publication or distribution.

Use of these data is acknowledgment that the user will be bound by the terms of the data licensing agreement which forms part of this documentation.

Statistics Canada
Income Statistics Division
income@statcan.gc.ca
November 2011

End-use Licence Agreement

Copyright

The Government of Canada (Statistics Canada) is the owner or a licensee of all intellectual property rights (including copyright) in this data product. With your payment of the requisite fee, you (hereinafter referred to as 'the Licensee') are granted a non-exclusive, non-assignable and non-transferable licence to use this data product subject to the terms below. This licence is not a sale of any or all of the rights of the owner(s).

Terms of use

  1. All copyright and proprietary notices, as well as all conditions of use associated with the data product, must be communicated to all users of the data product.

  2. The Licensee shall not transfer this data product to, or store the data product in, any electronic network for use by more than three (3) regular users unless the Licensee obtains prior written permission from Statistics Canada and pays any additional fees.

  3. The Licensee shall not lend, rent, lease, sublicense, transfer or sell any part of the data product nor any right granted under this agreement to any person outside the licensed organization or to any other organization.

  4. The Licensee shall not disassemble, decompile or in any way attempt to reverse engineer any software provided as part of the data product.

  5. The Licensee shall not use any part of the data product to develop or derive any other data product or data service for external distribution or commercial sale.

  6. The Licensee is granted reasonable rights of use of the content of this data product only for personal, corporate or public policy research, as well as for educational purposes. This permission includes the use of the content in analyses and in the reporting of results and conclusions, including the citation of limited amounts of supporting data, extracted from the data product, in such documents. In such cases, the source of the data must be acknowledged in all such documents and communications by providing the following source citation at the bottom of each table and graph:

    Source (or 'Adapted from,' if appropriate): Statistics Canada, (name of product), (catalogue number of product), (reference date of product).

  7. The Licensee shall obtain approval from Statistics Canada before publishing any significant volume of material, in any medium, that is extracted from the data product.

  8. The Licensee agrees not to merge or link the data product with any other databases in such a fashion that gives the appearance that the Licensee may have received, or had access to, information held by Statistics Canada about any identifiable individual, family, household, organization or business.

  9. Any violation of this licence renders it void and of no effect. This agreement will terminate automatically without notice if the Licensee fails to comply with any of the terms of this agreement. In the event of termination, the Licensee must immediately return the data product to Statistics Canada or destroy it and certify this destruction in writing to Statistics Canada.

Warranties and disclaimers

This data product is provided ‘as-is,’ and Statistics Canada makes no warranty, either express or implied, including but not limited to, warranties of merchantability and fitness for a particular purpose. In no event will Statistics Canada be liable for any direct, special, indirect, consequential or other damages, however caused.

Acceptance of terms

It is your responsibility to ensure that your use of this data product complies with these terms and to seek prior written permission from Statistics Canada for any uses not permitted or not specified in this agreement. Any infringement of Statistics Canada's rights may result in legal action.

Any use whatsoever of this data product shall constitute your acceptance of the terms of this agreement. Any violation of these terms may result in termination of this licence.

For further information please contact:

Licensing Services
Client Services Division, Statistics Canada
9th Floor, R.H. Coats Building
Ottawa, Ontario  K1A 0T6  Canada

E-mail: licensing@statcan.gc.ca
Telephone: 613-951-1122
Fax: 613-951-1134  
© Statistics Canada, 2011

RRSP Contributors (product #17C0006)

This databank provides information on taxfilers who contributed to a Registered Retirement Savings Plan (RRSP) during the tax year under review.

The content of the databank is as follows:

Table 1:  Summary
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Number of RRSP contributors
Column 8 – Average age of RRSP contributors
Column 9 – Median employment income of RRSP contributors
Column 10 – 75th percentile of employment income of RRSP contributors
Column 11 – Amount of RRSP dollars reported (in thousands of dollars)
Column 12 – Median RRSP contribution

Table 2:  Age groups
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Total number of RRSP contributors
Column 8 – Percent of contributors 0 to 24 years of age
Column 9 – Percent of contributors 25 to 34 years of age
Column 10 – Percent of contributors 35 to 44 years of age
Column 11 – Percent of contributors 45 to 54 years of age
Column 12 – Percent of contributors 55 to 64 years of age
Column 13 – Percent of contributors 65+ years of age
Column 14 – Total amount of RRSP dollars reported (in thousands of dollars)
Column 15 – Percent of contributions reported by age group 0 to 24
Column 16 – Percent of contributions reported by age group 25 to 34
Column 17 – Percent of contributions reported by age group 35 to 44
Column 18 – Percent of contributions reported by age group 45 to 54
Column 19 – Percent of contributions reported by age group 55 to 64
Column 20 – Percent of contributions reported by age group 65+

Table 3:  Sex
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Percent of taxfilers who are male
Column 8 – Percent of taxfilers who are female
Column 9 – Total number of RRSP Contributors
Column 10 – Percent of contributors who are male
Column 11 – Percent of contributors who are female
Column 12 – Total amount of RRSP dollars reported (in thousands of dollars)
Column 13 – Percent of contributions reported by males
Column 14 – Percent of contributions reported by females
Column 15 – Median RRSP contribution of all contributors
Column 16 – Median RRSP contribution of males
Column 17 – Median RRSP contribution of females

Table 4:  Income groups
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Total number of RRSP contributors
Column 8 – Percent of RRSP contributors with total income less than $20,000
Column 9 – Percent of RRSP contributors with total income between $20,000 and $39,999
Column 10 – Percent of RRSP contributors with total income between $40,000 and $59,999
Column 11 – Percent of RRSP contributors with total income between $60,000 and $79,999
Column 12 – Percent of RRSP contributors with total income $80,000+
Column 13 – Total amount of RRSP dollars reported (in thousands of dollars)
Column 14 – Percent of total RRSP amount reported by contributors with total income less than $20,000
Column 15 – Percent of total RRSP amount reported by contributors with total income between $20,000 and $39,999
Column 16 – Percent of total RRSP amount reported by contributors with total income between $40,000 and $59,999
Column 17 – Percent of total RRSP amount reported by contributors with total income between $60,000 and $79,999
Column 18 – Percent of total RRSP amount reported by contributors with total income $80,000+

RRSP Contribution Limits (ROOM) (product # 17C0011)

The Registered Retirement Savings Plan (RRSP) Room databank was created to provide information on the RRSP contribution limit (RRSP Room) available. This product can be used in conjunction with the RRSP databank which concentrates on the RRSP contributors.

In 1989, the legislation dictated that contribution limits for persons not contributing to a registered pension plan (RPP) or a Deferred Profit Sharing Plan (DPSP) was 20% of earned income to a maximum of $7,500. The limit for RPP and DPSP members was 20% of earned income to a maximum of $3,500 less the amount contributed by the employee to the RPP or DPSP.

Further amendments to the Income Tax Act relative to RRSPs, taking effect January 1, 1991, were intended to make RRSP contribution limits more equitable. The RRSP contribution limit was set at 18% of earned income for the previous tax year, to a set maximum minus the Pension Adjustment (PA). The PA represents the calculated value of the pension accrued through an RPP or a DPSP in the previous tax year.

Total RRSP Room represents the deduction limit that Canadians can claim with respect to contributions made to RRSPs. It does not include income eligible for transfers, such as retiring allowances and severance pay that may be rolled over into RRSPs. The sum of the deduction limit and rollovers represents the maximum amount that can be claimed as a deduction on line 208 of the income tax return.

Earned income in tax year New room Unused room Total room (for tax year+1)
1991 For 1992 pre1991 = 0 New room only
1992 For 1993 1991 to 1992 Unused room + new room
1993 For 1994 1991 to 1993 Unused room + new room
1994 For 1995 1991 to 1994 Unused room + new room
1995 For 1996 1991 to 1995 Unused room + new room
1996 For 1997 1991 to 1996 Unused room + new room
1997 For 1998 1991 to 1997 Unused room + new room
1998 For 1999 1991 to 1998 Unused room + new room
1999 For 2000 1991to 1999 Unused room + new room
2000 For 2001 1991 to 2000 Unused room + new room
2001 For 2002 1991 to 2001 Unused room + new room
2002 For 2003 1991 to 2002 Unused room + new room
2003 For 2004 1991 to 2003 Unused room + new room
2004 For 2005 1991 to 2004 Unused room + new room
2005 For 2006 1991 to 2005 Unused room + new room
2006 For 2007 1991 to 2006 Unused room + new room
2007 For 2008 1991 to 2007 Unused room + new room
2008 For 2009 1991 to 2008 Unused room + new room
2009 For 2010 1991 to 2009 Unused room + new room
2010 For 2011 1991 to 2010 Unused room + new room

Calculation of contribution limits

For 1990, maximum contributions are:

  • for non-participants in RPPs and DPSPs, the lesser of 20% of earned income and $7,500
  • for participants in RPPs and DPSPs, 20% of earned income to a maximum of $3,500; the maximum is reduced according to employee contributions to RPPs/DPSPs.

For 1991 to 2010:

New room = 18% of earned income - PA - PSPA

Percentage of earned income to a maximum of

  • $11,500 for 1991
  • $12,500 for 1992 and 1993
  • $13,500 for 1994
  • $14,500 for 1995
  • $13,500 for 1996
  • $13,500 for 1997
  • $13,500 for 1998
  • $13,500 for 1999
  • $13,500 for 2000
  • $13,500 for 2001
  • $13,500 for 2002
  • $14,500 for 2003
  • $15,500 for 2004
  • $16,500 for 2005
  • $18,000 for 2006
  • $19,000 for 2007
  • $20,000 for 2008
  • $21,000 for 2009
  • $22,000 for 2010

Where PA = Pension Adjustment, and PSPA = Past Service Pension Adjustment

Prior to tax year 2000 (Room 2001):

Total Room (for tax year+1) = Unused Room (from 1991 forward) + New Room

For tax years 2000 to 2010 (Room 2001 to Room 2011):

Total Room (for tax year+1) = Unused Room accumulated since 1991 + (18% of earned income – Pension adjustment) – Current tax year contributions excluding rollovers

Data source

Prior to the release of data for tax year 2000, the RRSP ROOM data were derived from a file received annually from the Canada Revenue Agency (CRA, formerly Canada Customs and Revenue Agency). CRA generated the data from an administrative system designed in response to changes to the Income Tax Act with respect to Registered Retirement Savings Plans, changes that took effect January 1, 1991.

The system records information for each taxfiler with "earned income" (income used to determine the RRSP deduction limit). The information includes each year's earned income, new room amounts and unused room amounts carried forward.

Starting with the 2001 ROOM (2000 tax data), the amount of RRSP Room is calculated from other variables on the preliminary file, variables which were previously unavailable.

This year’s release of the RRSP Room data is based on 2010 income tax returns. Contributions towards these limits can be made up to February 2012, to be reported on the 2011 tax returns. The mailing address at the time of filing is the basis for the geographic information in the tables.

Data quality

The calculated Room amount is equal to the amount on the Canada Revenue Agency (CRA) RRSP Room file.

The content of the databank is as follows:

Table 1: Persons with room
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk number
Column 4 – Level of geography (see Geography section)
Column 5 – Place name
Column 6 – Amount of Room dollars reported (in thousands of $)
Column 7 – Amount of Unused Room dollars reported (in thousands of $)
Column 8 – Amount of New Room dollars reported (in thousands of $)
Column 9 – Number of taxfilers with Room
Column 10 – Number of taxfilers with Unused Room
Column 11 – Number of taxfilers with New Room

Table 2: Characteristics of persons with new room
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk number
Column 4 – Level of geography (see Geography section)
Column 5 – Place name
Column 6 – Number of taxfilers with New Room
Column 7 – Average Age of taxfilers with New Room
Column 8 – Percentage Female taxfilers with New Room
Column 9 – Median Earned Income of taxfilers with New Room
Column 10 – Average New Room
Column 11 – Percentage of taxfilers with New Room between $500 and $2,399 1
Column 12 – Percentage of taxfilers with New Room between $2,400 and $4,699 2
Column 13 – Percentage of taxfilers with New Room between $4,700 and $7,799 3
Column 14 – Percentage of taxfilers with New Room between $7,800 and $12,999 4
Column 15 – Percentage of taxfilers with New Room greater than $13,000 5

Canadian Savers (product #17C0009)

Line 120 – Taxable amount of dividends from taxable Canadian corporations
Line 121 – Interest and other investment income

This databank provides information on taxfilers who have been classified as savers.

Savers are defined as taxfilers who reported interest and investment income on line 121, but no dividend income on line 120 of the personal income tax return.

Interest and investment income sources would include interest from Canada Savings bonds, bank accounts, treasury bills, investment certificates, term deposits, earnings on life insurance policies as well as foreign interest and dividend income.

Dividend income would include dividends from taxable Canadian corporations (as stocks or mutual funds), but not dividends from foreign investments.

Taxfilers reporting Canadian dividend income would not be counted as savers, but would be classified as investors.

The content of the databank is as follows:

Table 1: Summary
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Number of savers
Column 8 – Average age of savers
Column 9 – Median total income of savers
Column 10 – Total amount of interest dollars reported (in thousands of dollars)
Column 11 – Median of interest dollars

Table 2: Age groups
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Total number of savers
Column 8 – Percent of savers 0-24 years of age
Column 9 – Percent of savers 25-34 years of age
Column 10 – Percent of savers 35-44 years of age
Column 11 – Percent of savers 45-54 years of age
Column 12 – Percent of savers 55-64 years of age
Column 13 – Percent of savers 65+ years of age
Column 14 – Total amount of interest income dollars reported (in thousands of dollars)
Column 15 – Percent of interest income reported by age group 0-24
Column 16 – Percent of interest income reported by age group 25-34
Column 17 – Percent of interest income reported by age group 35-44
Column 18 – Percent of interest income reported by age group 45-54
Column 19 – Percent of interest income reported by age group 55-64
Column 20 – Percent of interest income reported by age group 65+

Table 3: Sex
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Percent of taxfilers who are male
Column 8 – Percent of taxfilers who are female
Column 9 – Total number of savers
Column 10 – Percent of savers who are male
Column 11 – Percent of savers who are female
Column 12 – Total amount of interest income reported (in thousands of dollars)
Column 13 – Percent of interest income reported by males
Column 14 – Percent of interest income reported by females
Column 15 – Median interest income of all savers
Column 16 – Median interest income of all male savers
Column 17 – Median interest income of all female savers

Table 4: Income groups
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Total number of savers
Column 8 – Percent of savers with total income less than $20,000
Column 9 – Percent of savers with total income between $20,000 and $39,999
Column 10 – Percent of savers with total income between $40,000 and $59,999
Column 11 – Percent of savers with total income between $60,000 and $79,999
Column 12 – Percent of savers with total income $80,000+
Column 13 – Total amount of interest income reported (in thousands of dollars)
Column 14 – Percent of interest income reported by savers with total income less than $20,000
Column 15 – Percent of interest income reported by savers with total income between $20,000 and $39,999
Column 16 – Percent of interest income reported by savers with total income between $40,000 and $59,999
Column 17 – Percent of interest income reported by savers with total income between $60,000 and $79,999
Column 18 – Percent of interest income reported by savers with total income $80,000+

Canadian Investors (product #17C0007)

Line 120 – Taxable amount of dividends from taxable Canadian corporations
Line 121 – Interest and other investment income

This databank provides information on taxfilers classified as investors.

Investors include taxfilers who reported dividend income on line 120 of their personal tax return. They may or may not have also reported interest and other investment income on line 121. When income is also reported on line 121, that amount is added to the amount of dividend income received, and the sum becomes the investment income of the investor.

The content of the databank is as follows:

Table 1: Summary
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk number
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Number of investors
Column 8 – Average age of investors
Column 9 – Median total income of investors
Column 10 – Amount of investment dollars (in thousands of dollars)
Column 11 – Percentage of the investment income derived from dividends
Column 12 – Median investment income

Table 2: Age groups
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Total number of investors
Column 8 – Percent of investors 0-24 years of age
Column 9 – Percent of investors 25-34 years of age
Column 10 – Percent of investors 35-44 years of age
Column 11 – Percent of investors 45-54 years of age
Column 12 – Percent of investors 55-64 years of age
Column 13 – Percent of investors 65+ years of age
Column 14 – Total amount of investment income dollars reported (in thousands of dollars)
Column 15 – Percent of investment income reported by age group 0-24
Column 16 – Percent of investment income reported by age group 25-34
Column 17 – Percent of investment income reported by age group 35-44
Column 18 – Percent of investment income reported by age group 45-54
Column 19 – Percent of investment income reported by age group 55-64
Column 20 – Percent of investment income reported by age group 65+

Table 3: Sex
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Percent of taxfilers who are male
Column 8 – Percent of taxfilers who are female
Column 9 – Total number of investors
Column 10 – Percent of investors who are male
Column 11 – Percent of investors who are female
Column 12 – Total amount of investment income reported (in thousands of dollars)
Column 13 – Percent of investment income reported by males
Column 14 – Percent of investment income reported by females
Column 15 – Median investment income of all investors
Column 16 – Median investment income of all male investors
Column 17 – Median investment income of all female investors

Table 4: Income groups
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Total number of investors
Column 8 – Percent of investors with total income less than $20,000
Column 9 – Percent of investors with total income between $20,000 and $39,999
Column 10 – Percent of investors with total income between $40,000 and $59,999
Column 11 – Percent of investors with total income between $60,000 and $79,999
Column 12 – Percent of investors with total income $80,000+
Column 13 – Total amount of investment income reported (in thousands of dollars)
Column 14 – Percent of investment income reported by investors with total income less than $20,000
Column 15 – Percent of investment income reported by investors with total income between $20,000 and $39,999
Column 16 – Percent of investment income reported by investors with total income between $40,000 and $59,999
Column 17 – Percent of investment income reported by investors with total income
between $60,000 and $79,999
Column 18 – Percent of investment income reported by investors with total income
$80,000+

Canadian Investment Income (product #17C0008)

Line 120 – Taxable amount of dividends from taxable Canadian corporations
Line 121 – Interest and other investment income

This databank provides information on taxfilers who reported dividend income on line 120 of the tax return, or interest and other investment income on line 121, or both. These taxfilers include those designated as savers and those designated as investors in two other databanks available: Canadian Savers and Canadian Investors. In this databank, investment income includes both interest and dividends.

Dividend income includes dividends from taxable Canadian corporations (as stocks or mutual funds).

Interest and other investment income sources include interest from Canada Savings bonds, bank accounts, treasury bills, investment certificates, term deposits, earnings on life insurance policies as well as foreign interest and dividend income.

The content of the databank is as follows:

Table 1: Summary
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Number of taxfilers with investment income
Column 8 – Average age of taxfilers with investment income
Column 9 – Median total income of taxfilers with investment income
Column 10 – Reported investment income dollars for all taxfilers with investment income (in thousands of dollars)
Column 11 – Median investment income for all taxfilers with investment income

Table 2: Age groups
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Total number of receivers of investment income
Column 8 – Percent of receivers of investment income 0-24 years of age
Column 9 – Percent of receivers of investment income 25-34 years of age
Column 10 – Percent of receivers of investment income 35-44 years of age
Column 11 – Percent of receivers of investment income 45-54 years of age
Column 12 – Percent of receivers of investment income 55-64 years of age
Column 13 – Percent of receivers of investment income 65+ years of age
Column 14 - Total amount of investment income dollars reported (in thousands of dollars)
Column 15 – Percent of investment income reported by age group 0-24
Column 16 – Percent of investment income reported by age group 25-34
Column 17 – Percent of investment income reported by age group 35-44
Column 18 – Percent of investment income reported by age group 45-54
Column 19 – Percent of investment income reported by age group 55-64
Column 20 – Percent of investment income reported by age group 65+

Table 3: Sex
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Percent of taxfilers who are male
Column 8 – Percent of taxfilers who are female
Column 9 – Total number of receivers of investment income
Column 10 – Percent of receivers of investment income who are male
Column 11 – Percent of receivers of investment income who are female
Column 12 – Total amount of investment income reported (in thousands of dollars)
Column 13 – Percent of investment income reported by males
Column 14 – Percent of investment income reported by females
Column 15 – Median investment income of all receivers of investment income
Column 16 – Median investment income of all male receivers of investment income
Column 17 – Median investment income of all female receivers of investment income

Table 4: Income groups
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Total number of receivers of investment income
Column 8 – Percent of receivers of investment income with total income less than $20,000
Column 9 – Percent of receivers of investment income with total income between $20,000 and $39,999
Column 10 – Percent of receivers of investment income with total income between $40,000 and $59,999
Column 11 – Percent of receivers of investment income with total income between $60,000 and $79,999
Column 12 – Percent of receivers of investment income with total income $80,000+
Column 13 – Total amount of investment income reported (in thousands of dollars)
Column 14 – Percent of investment income reported by receivers of investment income with total income less than $20,000
Column 15 – Percent of investment income reported by receivers of investment income with total income between $20,000 and $39,999
Column 16 – Percent of investment income reported by receivers of investment income with total income between $40,000 and $59,999
Column 17 – Percent of investment income reported by receivers of investment income with total income between $60,000 and $79,999
Column 18 – Percent of investment income reported by receivers of investment income with total income $80,000+

Canadian Capital Gains (product #17C0012)

Line 127 – Taxable amount of capital gains

This databank provides information on taxfilers who reported capital gains during the tax year under review.

Line 127 of the T1 income tax return contains the amount of taxable capital gains reported by Canadians; this value is half the actual capital gains received. The information in this databank reflects the total capital gains received; amounts reported have been grossed up to reflect this total.

The content of the databank is as follows:

Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Total number of taxfilers
Column 7 – Number of taxfilers reporting capital gains
Column 8 – Percent of taxfilers reporting capital gains who had a total income under $20,000
Column 9 – Percent of taxfilers reporting capital gains who had a total income between $20,000 and $39,999
Column 10 – Percent of taxfilers reporting capital gains who had a total income between $40,000 and $59,999
Column 11 – Percent of taxfilers reporting capital gains who had a total income between $60,000 and $79,999
Column 12 – Percent of taxfilers reporting capital gains who had a total income of $80,000+
Column 13 – Total value of capital gains (in thousands of dollars)
Column 14 – Percent of capital gains reported by taxfilers with a total income under $20,000
Column 15 – Percent of capital gains reported by taxfilers with a total income between $20,000 and $39,999
Column 16 – Percent of capital gains reported by taxfilers with a total income between $40,000 and $59,999
Column 17 – Percent of capital gains reported by taxfilers with a total income between $60,000 and $79,999
Column 18 – Percent of capital gains reported by taxfilers with a total income of $80,000+

Canadian Taxfilers (product #17C0010)

This databank provides a demographic and income profile of all Canadians who filed a personal tax return in the reference year.

The content of the databank is as follows:

Table 1: Summary
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk number
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Number of taxfilers
Column 7 – Percent of taxfilers 0-24 years of age
Column 8 – Percent of taxfilers 25-34 years of age
Column 9 – Percent of taxfilers 35-44 years of age
Column 10 – Percent of taxfilers 45-54 years of age
Column 11 – Percent of taxfilers 55-64 years of age
Column 12 – Percent of taxfilers 65+ years of age
Column 13 – Average age of taxfilers
Column 14 – Median total income of taxfilers
Column 15 – 75th percentile of total income of taxfilers
Column 16 – 85th percentile of total income of taxfilers
Column 17 – 95th percentile of total income of taxfilers
Column 18 – Median employment income of taxfilers
Column 19 – 75th percentile of employment income of taxfilers

Table 2: Income Groups
Column 1 – City identification number
Column 2 – Postal area
Column 3 – Postal walk number
Column 4 – Level of geography (see geography section)
Column 5 – Place name
Column 6 – Number of taxfilers
Column 7 – Percent of taxfilers with total income less than $20,000
Column 8 – Percent of taxfilers with total income between $20,000 and $39,999
Column 9 – Percent of taxfilers with total income between $40,000 and $59,999
Column 10 – Percent of taxfilers with total income between $60,000 and $79,999
Column 11 – Percent of taxfilers with total income $80,000+
Column 12 – Value of total income (in thousands of dollars)
Column 13 – Percent of total income reported by taxfilers with total income less than $20,000
Column 14 – Percent of total income reported by taxfilers with total income between $20,000 and $39,999
Column 15 – Percent of total income reported by taxfilers with total income between $40,000 and $59,999
Column 16 – Percent of total income reported by taxfilers with total income between $60,000 and $79,999
Column 17 – Percent of total income reported by taxfilers with total income $80,000+

Charitable Donations

Line 340 – Allowable charitable donations and government gifts

This databank provides information on taxfilers classified as charitable donors. Charitable donors are defined as taxfilers reporting donations on line 340 of the tax return.

Canadians contribute in many ways to charitable organizations. The databank on charitable donors provides information on taxfilers who claimed a tax credit for charitable donations on their income tax return in the reference year. These data may include donations that might be denied by the Canada Revenue Agency (CRA) after an audit. To find out more about why donations might be denied (i.e. tax shelter gifting arrangements, false receipting) please go to the Canada Revenue Agency website: www.cra-arc.gc.ca

Persons making charitable donations, but not reporting them on their personal tax return are not included in this databank. These include donations for which no receipt was provided and donations for which the receipt was lost. No estimate of such donations is included in these data.

Only donations made to approved organizations are allowable as deductions in the tax system. Donations are eligible if made to Canadian registered charities and Canadian amateur athletic associations. They are also eligible if made to: prescribed universities outside Canada; certain tax exempt housing organizations in Canada; Canadian municipalities; the United Nations; and certain charities outside Canada to which the Government of Canada has made a gift.

It is possible to carry donations forward for up to five years after the year in which they were made. In the reference year, it is possible to claim donations made in any of the previous five years, as long as they were not already claimed in a prior year. The donations made in the reference year could be claimed the same year, or could be carried forward to any of the next five years. According to tax laws, taxfilers are permitted to claim both their donations and those made by their spouses to get better tax benefits. Consequently, the number of persons who made charitable donations may be higher than the number who claimed tax credits.

A change in tax regulations was introduced in 2007. Taxfilers contributing to a recognized charity (as outlined above) were eligible to claim a tax credit of 15% of their donations on the first $200, and 29% on the rest. In 2006, the tax credit was 15.25% on the first $200 and 29% on the rest. In 2005, the tax credit was 15% on the first $200 and 29% on the rest. From 2001 to 2004, the tax credit was 16% on the first $200 and 29% on the rest. From 1992 to 2000, the tax credit was 17% on the first $200 and 29% on the rest. Previously, taxfilers had to give $250 to charity before the 29% credit was available.

The content of the databank is as follows:

Table 1: Summary
Column 1 - City identification number
Column 2 - Postal area
Column 3 - Postal walk number
Column 4 - Level of geography (see Geography section)
Column 5 - Place name
Column 6 - Total Number of taxfilers
Column 7 - Number of charitable donors
Column 8 - Average age of donors
Column 9 - Average donation for age group 0-24
Column 10 - Average donation for age group 25-34
Column 11 - Average donation for age group 35-44
Column 12 - Average donation for age group 45-54
Column 13 - Average donation for age group 55-64
Column 14 - Average donation for age group 65+
Column 15 - Total amount of charitable donations (thousands of $)
Column 16 - Median donation
Column 17 - Median total income of donors
Column 18 - 75th percentile of donors' total income

Table 2: Age and Sex (new beginning with 1995)
Column 1 - City identification number
Column 2 - Postal area
Column 3 - Postal walk number
Column 4 - Level of geography (see Geography section)
Column 5 - Place name
Column 6 - Total Number of taxfilers
Column 7 - Percent of taxfilers who are male
Column 8 - Percent of taxfilers who are female
Column 9 - Number of charitable donors
Column 10 - Percent of charitable donors who are male
Column 11 - Percent of charitable donors who are female
Column 12 - Percent of donors 0 - 24 years of age
Column 13 - Percent of donors 25 - 34 years of age
Column 14 - Percent of donors 35 - 44 years of age
Column 15 - Percent of donors 45 - 54 years of age
Column 16 - Percent of donors 55 - 64 years of age
Column 17 - Percent of donors 65+ years of age
Column 18 - Total median donation
Column 19 - Median donation of males
Column 20 - Median donation of females
Column 21 - Total amount of charitable donations (thousands of $)
Column 22 - Total amount of charitable donations for males (thousands of $)
Column 23 - Total amount of charitable donations for females (thousands of $)

Table 3: Income Groups (new beginning with 1997)
Column 1 - City identification number
Column 2 - Postal area
Column 3 - Postal walk number
Column 4 - Level of geography (see Geography section)
Column 5 - Place name
Column 6 - Total number of taxfilers
Column 7 - Total number of charitable donors
Column 8 - Percent of charitable donors with total income less than $20,000
Column 9 - Percent of charitable donors with total income between $20,000 and $39,999
Column 10 - Percent of charitable donors with total income between $40,000 and $59,999
Column 11 - Percent of charitable donors with total income between $60,000 and $79,999
Column 12 - Percent of charitable donors with total income $80,000+
Column 13 - Total value of charitable donations (in thousands of dollars)
Column 14 - Percent of donations reported by donors with total income under $20,000
Column 15 - Percent of donations reported by donors with total income between $20,000 and $39,999
Column 16 - Percent of donations reported by donors with total income between $40,000 and $59,999
Column 17 - Percent of donations reported by donors with total income between $60,000 and $79,999
Column 18 - Percent of donations reported by donors with total income $80,000+

Data Source

The financial databanks are derived from income tax returns. For the most part, tax returns were filed in the spring of the year following the reference year. For example, for the 2010 tax year, income tax returns were filed by April 30, 2011.

The mailing address at the time of filing is the basis for the geographic information in the tables.

Demographic characteristics such as age are given as of December 31 of the tax year. Income information is for the calendar year under review.

Data Frequency

Data are updated on an annual basis.

Data Quality

i) Number of Canadian taxfilers

The data used are direct counts from tax files.  For the 2010 tax year, 24.5 million Canadians or 71.3% filed tax returns.

Figure 1 – Number of Canadian Taxfilers

Tax year Number of taxfilers ('000) Date of population estimate Population ('000) Coverage (%)
1991 18,786 April 1, 1992 28,270 66.5
1992 19,267 April 1, 1993 28,601 67.4
1993 19,882 April 1, 1994 28,907 68.8
1994 20,184 April 1, 1995 29,212 69.1
1995 20,536 April 1, 1996 29,514 69.6
1996 20,772 April 1, 1997 29,818 69.7
1997 21,113 April 1, 1998 30,080 70.2
1998 21,431 April 1, 1999 30,315 70.7
1999 21,893 April 1, 2000 30,594 71.6
2000 22,249 April 1, 2001 30,911 72.0
2001 22,804 April 1, 2002 31,252 73.0
2002 22,968 April 1, 2003 31,548 72.8
2003 23,268 April 1, 2004 31,846 73.1
2004 23,625 April 1, 2005 32,143 73.5
2005 23,952 April 1, 2006 32,471 73.8
2006 24,258 April 1, 2007 32,818 73.9
2007 24,624 April 1, 2008 33,191 74.2
2008 24,987 April 1, 2009 33,604 74.4
2009* 24,321 April 1, 2010 34,002 71.5
2010* 24,495 April 1, 2011 34,368 71.3

Percent coverage is based on a comparison of the number of taxfilers in the Income Statistics Division's taxfilers databank and the population estimates from the Statistics Canada CANSIM table 051-0005, now available on the Statistics Canada web site www.statcan.gc.ca.

*The 2009 and 2010 count of taxfilers is taken from a preliminary 2009 and 2010 tax file from the Canada Revenue Agency.

ii) Elderly population

Some elderly Canadians receiving only Old Age Security and Guaranteed Income Supplement do not file because they have low or no taxable income. However, with the introduction of the Federal Sales Tax (FST) Credit in 1986 and the Goods and Services Tax (GST) Credit in 1990, the percentage of the elderly population filing tax returns has increased. In 2008, approximately 95%of the population aged 65 and over filed tax returns, up from 75% in 1989 (when comparing the number of taxfilers aged 65 years or more with the corresponding population estimate available on CANSIM 051-0001 from Statistics Canada).

Figure 2 ─ Coverage by Age and by Province, 2009

Rates of Coverage by Age
Age Rates of Coverage
under 20 101.8%
20-24 84.7%
25-29 87.5%
30-34 91.6%
35-39 95.5%
40-44 96.6%
45-49 94.9%
50-54 94.3%
55-59 93.1%
60-64 94.1%
65-74 96.1%
75+ 94.8%
Total 95.1%

 

Rates of Coverage by Province
Province Rates of Coverage
Newfoundland & Labrador 99.9%
Prince Edward Island 96.8%
Nova Scotia 95.5%
New Brunswick 97.9%
Quebec 96.7%
Ontario 94.7%
Manitoba 95.2%
Saskatchewan 96.6%
Alberta 93.9%
British Columbia 92.8%
Yukon 91.0%
Northwest Territories 93.4%
Nunavut 93.0%
Canada 95.1%

Coverage rates by age and by province are based on comparisons with the estimated population counts to July 1, 2010 available on CANSIM table 051-0001 from Statistics Canada.

iii) Income

Persons with low income have no tax liability and are not required to file tax returns. However, with the introduction of the Child Tax Credit in 1978, the Federal Sales Tax (FST) Credit in 1986, the Goods and Services Tax (GST) Credit in 1990, and the Child Tax Benefits in 1993, persons with low income are likely to file tax returns to apply for these credits.

Confidentiality and Rounding

Over the years since its creation, the T1 Family File (T1FF) has become known as a reliable, annual source for income and demographic estimates. To protect the confidentiality of Canadians, all data are subject to the confidentiality procedures of rounding and suppression.

Developmental work and testing resulted in different confidentiality procedures that were applied to the Financial and Charitable Donors databank for the reference year 2007; it consisted of introducing a certain distortion in the data instead of using the suppression method. However, when the new methodology was applied to the data of the other standard products of Income Statistics Division, the distortion component was no more an option due to the complexity of all the other databanks. Therefore, in an effort to harmonize the confidentiality rules across all the standard products of Income Statistics division, it has been decided to revert back to the suppression rules.

These measures maintain the confidentiality of the data. All counts are rounded. Rounding may increase, decrease, or cause no change to counts. Rounding can affect the results obtained from calculations. For example, when calculating percentages from rounded data, results may be distorted as both the numerator and denominator have been rounded. The distortion can be greatest with small numbers.

All reported amounts are rounded to the nearest $5,000 dollars.

Since 1990, data cells represent counts of 15 or greater, and are rounded to a base of 10. For example, a cell count of 15 would be rounded to 20 and a cell count of 24 would be rounded to 20.

Note: Counts represent the number of persons.
Reported amounts are aggregate dollar amounts reported.

In the data tables:

Medians, Percentiles and Average amount are rounded to the nearest ten dollars.

Percentages are published with no decimal and calculated on rounded data; therefore, the sum of percentages might not equal 100% in the case of small counts.

Suppressed Data

To maintain confidentiality, data cells have been suppressed whenever:

  • areas comprise less than 100 taxfilers;
  • cells represent less than 15 taxfilers6;
  • cells were dominated by a single filer.

Suppressed data may occur:

i) Within one area:

  • when one of the income categories is suppressed, a second category must also be suppressed to avoid disclosure of confidential data by subtraction (called residual disclosure);
  • when one of the gender categories is suppressed, the other gender category must also be suppressed to avoid residual disclosure;
  • when one age group category is suppressed, another age group must also be suppressed to avoid residual disclosure.

ii) Between areas:

  • when a variable amount in one area is suppressed, that variable amount is also suppressed in another area to prevent disclosure by subtraction.

Glossary of Terms

75th percentile

Total income values are ranked from highest to lowest and the value reported as being the 75th percentile indicates that 25% of the taxfilers report an income equal or above that amount and 75% fall below. Percentiles are calculated for each geographical level.

For example, if the 75th percentile of total income is shown as $60,000 this means that 25% of the population under review has a total income greater than or equal to $60,000 and 75% of the population has a total income less than or equal to $60,000.

85th percentile

Starting with the 2007 data, the dollar value of the 85th percentile appears in the tables instead of the percentage above the 85th percentile like it was in previous years. Total income values are ranked from highest to lowest and the value reported as being the 85th percentile indicates that 15% of the taxfilers report an income equal or above that amount and 85% fall below. Percentiles are calculated for each geographical level.

For example, if the 85th percentile of total income is shown as $65,000 this means that 15% of the taxfilers has a total income greater than or equal to $65,000

95th percentile

Starting with the 2007 data, the dollar value of the 95th percentile appears in the tables instead of the percentage above the 95th percentile like it was in previous years. Total income values are ranked from highest to lowest and the value reported as being the 95th percentile indicates that 5% of the taxfilers report an income equal or above that amount and 95% fall below. Percentiles are calculated for each geographical level.

For example, if the 95th percentile of total income is shown as $90,000 this means that 5% of the population under review has a total income greater than or equal to $90,000

Age

Calculated as of December 31 of the reference year (i.e., tax year minus year of birth).

Capital Gains

Line 127 of the T1 income tax return shows "taxable capital gains" or half of the capital gains actually received.  The information in this databank has been grossed up to represent the total capital gains received.

Charitable donation

Is the allowable portion of total donations, as reported on the income tax return.

Charitable donor

Is defined as a taxfiler reporting a charitable donation amount on line 340 of the personal income tax form.

City identification number (CityID)

Since municipality names can be, in some cases, quite long and cumbersome for handling in electronic files, municipalities are given a "city identification number". Starting in 2007, the CityID is a five digits alpha-numeric component. It is created with the first letter of postal code followed by “9” and a four digits number. Each first letter of postal code is allocated a range of number from 1 to 9999 (more explanation in geography section).

Deferred profit sharing plan (DPSP)

An employer-sponsored savings plan registered by the Canada Revenue Agency. Contributions to these plans by the employer (employees cannot contribute) are based on profits. The amount accumulated in these plans can be paid out as a lump sum at retirement or termination of employment, transferred to an RRSP, received in instalments over a period not to exceed ten years, or used to purchase an annuity.

Dividend income

Includes taxable amount of dividends (eligible and other than eligible) received from taxable Canadian corporations (as stocks or mutual funds) as reported on line 120 of the personal income tax return, and then grossed down to the actual amounts received; dividend income does not include dividends received from foreign investments (which are included in interest income and reported on line 121).

Earned income

The income used to determine the RRSP deduction limit. It includes such items as employment income (less union dues and expenses), net business and rental income, disability payments and alimony received. Alimony payments, current year business and rental losses are deducted from this amount. Most investment income (other than rents) is not considered earned income. In calculating the RRSP deduction limit, earned income from the previous year is used.

Employment income

The total reported employment income. Employment income includes wages and salaries, commissions from employment, training allowances, tips and gratuities, and self-employment income (net income from business, profession, farming, fishing and commissions) and Indian Employment Income (new in 1999).

Interest income

Amounts Canadians claimed on line 121 of the personal income tax return. This amount includes interest generated from bank deposits, Canada Savings Bonds, corporate bonds, treasury bills, investment certificates, term deposits, annuities, mutual funds, earnings on life insurance policies and all foreign interest and foreign dividend incomes.

Investment income

Includes both interest income and dividend income.

Investors

Taxfilers who reported dividend income on line 120 of their personal tax return. They may or may not have also reported interest and other investment income on line 121. When such income is reported on line 121, this amount is added to the amount of dividend income received, and the sum becomes the investment income of the investor.

Level of geography

A code designating the type of geographic area to which the information in the table applies. See the section on Geography for further information.

Median

The middle number in a group of numbers. Where a median income, for example, is given as $26,000, it means that exactly half of the incomes reported are greater than or equal to $26,000, and that the other half is less than or equal to the median amount. With the exception of "Total Income", zero values are not included in the calculation of medians for individuals.

New room

For 2010 is calculated as 18% of 2009 earned income (from definition above) to a maximum of $22,000 minus pension adjustment (PA) minus past service pension adjustment (PSPA). Since the focus of these data is for net new room for potential RRSP contributions, PA and/or PSPA details will be omitted.

Past service pension adjustment (PSPA)

Applies only to members of defined benefit RPPs. A PSPA occurs when the pension benefit is upgraded, or additional credits purchased, for service in past years. In the first case, it is called an exempt (from certification) PSPA; in the second case, a certifiable PSPA. Only service after 1989 is considered.

Pension adjustment (PA)

Calculated value of the pension accrued in the year in an RPP or a DPSP. The PA decreases the RRSP deduction limit. To calculate this limit, the PA from the previous year is used.

Registered disability savings plan income (RDSP)

It consists of an individual disability savings plan governed by RRSP investment rules. Private contributions that can be made by anyone are subject to a lifetime limit of $200,000. They will be matched in some degree by government contributions; the lifetime limit is $90,000. Contributions are not deductible and income earned in the plan will not be taxed while in the plan.

Registered pension plan (RPP)

An employer-sponsored plan registered with the Canada Revenue Agency and most commonly also with one of the pension regulatory authorities. The purpose of such plans is to provide employees with a regular income at retirement. The two main types of RPPs are called defined benefit (where the benefit formula is specified) and defined contribution (where only the contribution formula is defined).

Registered retirement savings plan (RRSP)

An individual retirement savings plan that is registered by the Canada Revenue Agency. It permits limited contributions, and income earned in the RRSP is exempt from tax until payments are received from the plan.

Savers

Taxfilers who reported interest and investment income on line 121 of the personal income tax return, but no dividend income on line 120.

Taxfiler

Individual who filed a personal income tax return for the reference year.

Total income

The reported amounts of income by taxfilers from any of the following sources:

  • Labour force income;
    • Employment income;
      • Wages, salaries and commissions;
      • Other employment income as reported on line 104 of the tax form (tips, gratuities, royalties, etc.);
      • Net self-employment income;
      • Status Indian exempt self-employment income (beginning 2010);
      • Indian Employment Income (beginning in 1999);
    • Employment Insurance (EI) benefits;
  • Pension income;
    • Old Age Security/Net Federal Supplements (the latter including guaranteed income supplements and spouses' allowances since 1994);
    • Canada/Quebec Pension Plans;
    • Superannuation and other (private) pensions;
  • Family Allowance benefits (up to and including 1992);
  • Interest and other investment income;
  • Dividend income;
  • RRSP income (since 1999, for taxfilers 65+ only);
  • Net limited partnership income;
  • Alimony;
  • Net rental income;
  • Other income (e.g. alimony, and incomes reported on line 130, such as fellowships, bursaries, grants, etc.);
  • Federal Sales Tax (FST) credit (for 1989-1990 inclusive);
  • Goods and Services Tax (GST) credit (beginning in 1990);
  • Harmonized Sales Tax (HST) credit (beginning in 1997);
  • Child tax credit (up to and including 1992);
  • Canada child tax benefit (starting with 1993);
  • Provincial refundable tax credits (beginning in 1994);
  • Other non-taxable income (beginning in 1993);
    • Workers' compensation payments;
    • Social assistance payments;
    • Guaranteed income supplements;
    • Spouses' allowances;
  • Universal child care benefit (both claimed by filer and designated to child) (beginning in 2006);
  • Registered disability savings plan income (beginning in 2008)

Total room (in thousands of dollars)

The sum of "new room" and "unused room" as defined here.

Total room (number of persons)

The number of taxfilers who have either unused room from previous years, new room based on their earned income, or both. The number of persons with total room does not correspond to the sum of persons with new room and unused room, as an individual can be included in both categories.

Universal Child Care Benefit

Beginning in July 2006, the Universal Child Care Benefit (UCCB) is a taxable amount of $100 paid monthly for each child under 6 years of age. Included in Canada Child Tax Benefits in the statistical tables.

Unused RRSP contribution room (unused room)

The amount of the RRSP deduction limit that is not claimed by the taxfiler, or the amount remaining after subtracting actual contributions claimed on the tax return from that year's contribution room. Unused room can be carried forward indefinitely. The first year of unused room is from 1991 (see table).

Statistical Tables - Footnotes and Historical Availability

RRSP Contributors

  1. Table 1 is available in its current format starting with the 1990 data, according to the postal geography. Census metropolitan areas (CMAs) are available starting with the 1993 data, census divisions (CDs) with the 1994 data and federal electoral districts (FEDs) with the 1997 data.
  2. Table 2 (age groups) and table 3 (sex) are available in their current formats starting with the 1994 data, for postal areas, CMAs, CDs and FEDs (since 1997). Some changes were made to the age groupings over the years.
  3. Table 4 (income groups) is available in its current format starting with the 2007 data, for postal areas, CMAs, CDs and FEDs. From 1997 to 2006, the income groups were cumulative.

RRSP Contribution Limits (Room)

  1. Both tables are available in their current format starting with the 1993 data.
  2. Data are available for all levels of the postal geography starting with the 1993 tax year.
  3. Data for census metropolitan areas (CMAs) are available starting with the 1993 tax year (1994 room), census divisions (CDs) with the 1994 tax year (1995 room) and federal electoral districts (FEDs) with the 1997 tax year (1998 room).
  4. The figures in Table 2 ($500, $2,400, $4,700, $7,800 and $13,000) represent the 25th, 50th, 75th, 90th and 97th percentiles of new room and are recalculated periodically.

Canadian Savers

  1. Table 1 is available in its current format starting with the 1990 data, according to the postal geography. Census metropolitan areas (CMAs) are available starting with the 1993 data, census divisions (CDs) with the 1995 data and federal electoral districts (FEDs) with the 1997 data.
  2. Table 2 (age groups) and table 3 (sex) are available in their current formats starting with the 1995 data, for postal areas, CMAs, CDs and FEDs (since 1997). Some changes were made to the age groupings over the years.
  3. Table 4 (income groups) is available in its current format starting with the 2007 data, for postal areas, CMAs, CDs and FEDs. From 1997 to 2006, the income groups were cumulative.

Canadian Investors

  1. Table 1 is available in its current format starting with the 1990 data, according to the postal geography. Census metropolitan areas (CMAs) are available starting with the 1993 data, census divisions (CDs) with the 1995 data and federal electoral districts (FEDs) with the 1997 data.
  2. The proportion of investment income from dividends is available starting with the 1996 data (Table 1).
  3. Table 2 (age groups) and table 3 (sex) are available in their current formats starting with the 1995 data, for postal areas, CMAs, CDs and FEDs (since 1997). Some changes were made to the age groupings over the years.
  4. Table 4 (income groups) is available in its current format starting with the 2007 data, for postal areas, CMAs, CDs and FEDs. From 1997 to 2006, the income groups were cumulative.

Canadian Investment Income

  1. Table 1 is available in its current format starting with the 1990 data, according to the postal geography. Census metropolitan areas (CMAs) are available starting with the 1993 data, census divisions (CDs) with the 1995 data and federal electoral districts (FEDs) with the 1997 data.
  2. Table 2 (age groups) and table 3 (sex) are available in their current formats starting with the 1995 data, for postal areas, CMAs, CDs and FEDs (since 1997). Some changes were made to the age groupings over the years.
  3. Table 4 (income groups) is available in its current format starting with the 2007 data, for postal areas, CMAs, CDs and FEDs. From 1997 to 2006, the income groups were cumulative.

Canadian Capital Gains

  1. The standard table on capital gains by income group is available in its current format starting with the 2007 data. From 1998 data up to 2006, the income groups were cumulative.
  2. All levels of geography are available since the 1998 data, including census divisions, census metropolitan areas, federal electoral districts and all levels of the postal geography.

Canadian Taxfilers

  1. Table 1 is available in its current format starting with the 1990 data, according to the postal geography. Census metropolitan areas (CMAs) are available starting with the 1993 data, census divisions (CDs) with the 1995 data and federal electoral districts (FEDs) with the 1997 data.
  2. Starting with the 2007 data, the column on the “% reporting in French” in table 1 has been suppressed.
  3. Table 2 (income groups) is available in its current format starting with the 2007 data, for postal areas, CMAs, CDs and FEDs. From 1997 to 2006, the income groups were cumulative.

Charitable Donations

  1. Table 1 (summary) is available starting with the 1990 data, according to the postal geography. Census metropolitan areas (CMAs) are available starting with the 1993 data, census divisions (CDs) with the 1995 data and federal electoral districts (FEDs) with the 1997 data.
  2. Changes were made to the age groups in table 1 in 1991 and in 1997.
  3. Table 2 (age groups) is available starting with the 1995 data, for the postal geography and for CMAs. CDs are available starting with the 1995 data and FEDs with the 1997 data.
  4. Changes were made to the age groups in table 2 in 1997.
  5. Table 3 (Income groups) is available in its current format starting with the 2007 data, for the postal geography, for CMAs, CDs and FEDs. From 1997 to 2006, the income groups were cumulative.

Geography

The data are available for the following geographic areas. See "Statistical Tables - Footnotes and Historical Availability" for further details. The mailing address at the time of filing is the basis for the geographic information in the tables.

Standard areas:

  1. Canada,
  2. Provinces and territories,
  3. Census divisions,
  4. Census metropolitan areas,
  5. Federal electoral districts, and
  6. Postal geography.

User-defined areas:

Users may select a specific area of interest that is not a standard area for which data can be made available in standard format. To obtain data, provide us with a list of the postal codes for which data are required and we will provide the aggregated data. Of course, the area must satisfy our confidentiality requirements, or no data can be produced. See the "Special Geography" section for further information.

Geographic Levels – Postal Geography

The various databanks compiled from the taxfile are available for different levels of the postal geography, and for some levels of the Census geography. Coded geographic indicators appearing on the data tables are shown below with a brief description.

Level of Geography (L.O.G.) Postal Area Description
12 Canada This level of data is an aggregation of the provincial/territorial totals (code 11). The national total is identified by the region code Z99099.
11 Province or Territory Total

This level of data is an aggregation of the following geographies within a province:

City Totals (Code 08)
Rural Postal Codes (Code 09)
Other Provincial Totals (Code 10)

These totals are identified by a provincial/territorial postal letter, then a "990" followed by the province/territory code, as follows:

Newfoundland and Labrador (A99010)
Nova Scotia (B99012)
Prince Edward Island (C99011)
New Brunswick (E99013)
Quebec (J99024)
Ontario (P99035)
Manitoba (R99046)
Saskatchewan (S99047)
Alberta (T99048)
British Columbia (V99059)
Northwest Territories (X99061)
Nunavut (X99062)
Yukon Territory (Y99060)

10 Other Provincial Total ("P" Pot)

This level of data is an aggregation of small communities in the province that had less than 100 taxfilers, where these communities are combined into a "pot". Before 1992, it was identified by the same codes as the provincial/territorial totals, and only the "Delivery Mode" codes 2 and 3 distinguished between the two. To avoid this problem, starting with the 1992 data, an "8" appears after the provincial/territorial letter instead of a "9". The "9" will be reserved for the provincial/territorial total, as explained in 11 above. These "pot" codes are as follows:

Newfoundland and Labrador (A89010)
Nova Scotia (B89012)
Prince Edward Island (C89011)
New Brunswick (E89013)
Quebec (J89024)
Ontario (P89035)
Manitoba (R89046)
Saskatchewan (S89047)
Alberta (T89048)
British Columbia (V89059)
Northwest Territories (X89061)
Nunavut (X89062)
Yukon Territory (Y89060)

09 Rural Postal Code (Not in City )

This level of geography pertains to rural communities that have one and only one rural postal code. These stand-alone rural postal codes can be identified by a "zero" in the second position of the postal code and a level of geography code 09.

The 2010 databanks contain 3,994 areas coded as level of geography 09.

08 City Total

This level of data is an aggregation of the following geographies for unique place names within a province/territory:

Urban FSA (Residential) (Code 03)
Rural Route (Code 04)
Suburban Services (Code 05)
Rural Postal Code (within city) (Code 06)
Other Urban Area (Code 07)

They have the following format: e.g., Edmonton = T95479; Regina = S94876. The pattern is the postal letter of the city plus "9" in the second position (indicating a total), followed by a 4 digit numeric code for the community (often called "CityID").

In general, postal cities do not coincide with census subdivisions.

The 2010 databanks contain 1,602 areas coded as level of geography 08.

07 Other Urban Area (Non-residential within city - "E" Pot)

This aggregation of data (or "pot") covers non-residential addresses within an urban centre and all other data not otherwise displayed. Commercial addresses, post office boxes and general delivery are included, as are residential addresses with too few taxfilers to report separately. They can be recognized by codes that are similar to the city totals, with a distinguishing difference: an "8" will follow the city postal letter rather than the "9" of the city total (e.g., Edmonton = T85479; Regina = S84876).

The 2010 databanks contain 472 areas coded as level of geography 07.

06 Rural Postal Code (Within City)

These data pertain to rural postal codes that belong to communities with more than one rural postal code. These occur in areas that were formerly serviced by rural delivery service and changed by Canada Post to urban delivery service or in communities served by more than one rural postal code. Rural postal codes of this type can be identified by a "zero" in the second position of the postal code and a level of geography code 06.

The 2010 databanks contain 501 areas coded as level of geography 06.

05 Suburban Service

Sparsely populated fringe areas of urban centres may receive their postal service from an urban post office by delivery designated as "suburban service". Their region code retains all six characters of the postal code. Suburban Services are usually near or on the perimeters of urban areas, and mail is delivered by a contractor to group mail boxes, community mail boxes and/or external delivery sites (e.g., kiosks, miniparks).

The 2010 databanks contain 105 areas coded as level of geography 05.

04 Rural Route

Reasonably well-settled rural areas may receive their postal service from an urban post office by delivery designated as "rural route". Mail is delivered by a contractor to customers living along or near well-defined roads. Their region code retains all six characters of the postal code.

The 2010 databanks contain 685 areas coded as level of geography 04.

03 Urban FSA (Residential Area)

The urban Forward Sortation Area (FSA, identified by the first three characters of the postal code) includes all residential addresses covered by the first three characters of a postal code in a particular urban area (not including levels 04 and 05). Only residential FSAs are considered for these databanks. This level of data is an aggregation of:

Postal Walk (Code 01)
Other Postal Walk (Code 02)

An Urban FSA of this type can be identified by the FSA followed by three blanks.

The 2010 databanks contain 2,400 areas coded as level of geography 03.

02 Other Postal Walk

This level of data is an aggregation of urban residential postal codes unallocated to a letter carrier route and postal walks with less than 100 taxfilers. A postal walk record of this type can be identified by the FSA followed by three blanks, and the postal walk number "XXXX".

The 2010 databanks contain 184 areas coded as level of geography 02.

01 Postal Walk

This is the finest level of data and is an aggregation of urban residential postal codes allocated to a letter carrier route. A postal walk of this type can be identified by a region code which is the FSA followed by three blanks, and the postal walk number. An average FSA contains 11 walks.

The 2010 databanks contain 21,762 areas coded as level of geography 01.

Adding Postal Areas Without Duplication

Data files according to the postal geography will often contain subtotals and totals. Many data users need to add certain geographies in order to come up with a total for their particular area of interest. However, including subtotals during this process results in double-counting some populations, and this leads to an erroneous total. The following is a summary of which postal areas are aggregations in the standard postal geography.

Postal walks (Level of Geography, or LOG 1) and walk pots (LOG 2) add up to urban Forward Sortation Areas (FSAs, LOG 3).

Urban FSAs (LOG 3), rural routes (LOG 4), suburban services (LOG 5), rural postal codes within a city (LOG 6) and other urban areas (LOG 7) add up to city totals (LOG 8).

City totals (LOG 8), rural postal codes not in a city (LOG 9) and other areas in a province (LOG 10) add up to provincial/territorial totals (LOG 11).

Provincial/territorial totals (LOG 11) add up to the Canada total (LOG 12).

Thus, using the Level of geography codes:
1 + 2 = 3
3 + 4 + 5 + 6 + 7 = 8
8 + 9 + 10 = 11

Geography for small area and administrative data

City identification number (CityID)

As of 2007, CityID has been modified.

Previous to 2007:

  1. CityID was a 4 digits number
  2. Each municipality had a unique number between 1 and 9999
  3. Almost every number was allocated to a municipality. Few numbers remained available for future new municipalities.

Starting with 2007data:
To create more possibilities without changing the CityID length in our systems:

  1. CityID number is now combined with 1st letter of postal code
  2. Each 1st letter of postal code has a possibility of numbers, ranged from 1 to 9999 (Table 2)
  3. Old numbers have been kept for existing municipality and 1st letters of postal code have been added to them (Table 1)
  4. New municipalities have been assigned a new CityID number in new format (Table 1)
Table 1
Postal Code Municipality name 2006 and Prior 2007 and Follow
K1A 1K6 Ottawa 2434 K2434
G3C 0A1 Stoneham-et-Tewkesbury n/a G2

 

Table 2
Province Letter file Range of number
Newfoundland & Labrador A 1 – 9999
Prince Edward Island C 1 – 9999
Nova Scotia B 1 – 9999
New Brunswick E 1 – 9999
Quebec G 1 – 9999
Quebec H 1 – 9999
Quebec J 1 – 9999
Ontario K 1 – 9999
Ontario L 1 – 9999
Ontario M 1 – 9999
Ontario N 1 – 9999
Ontario P 1 – 9999
Manitoba R 1 – 9999
Saskatchewan S 1 – 9999
Alberta T 1 – 9999
British Columbia V 1 – 9999
Yukon Y 1 – 9999
Northwest Territories X 1 – 9999
Nunavut X 1 – 9999

Therefore, it is now essential to identify a municipality by adding the postal code 1st letter to the number in order to get the proper municipality in the proper province (Table 3):

Table 3
Letter Number Municipality name Province
A 2 Avondale NL
B 2 Bible Hill NS
T 2 Rocky View AB
G 2 Stoneham-et-Tewkesbury QC

Concordance Files

A concordance file accompanies data that are aggregated by postal walk. This file lists all of the six-character postal codes for which there is information, and identifies the postal walk to which each postal code is assigned. An urban Forward Sortation Area (FSA) may be split between two or more municipalities, and so the FSA label as well as the city identification number (or CityID) becomes important parts of the geographic identifiers. It is a combination of CityID, FSA label and postal walk number that creates unique geographic identifiers. The concordance file consists therefore of the CityID, the FSA label (called the postal area), the postal walk number and the six-character urban postal code. By simply browsing the concordance file, one can determine which postal codes make up a given walk. The following illustration is an example of a concordance file.

CityID Postal area Postal walk Postal code
K6092 K1B 52 K1B3K5
K6092 K1B 52 K1B3V5
K6092 K1B 52 K1B4C6
K6092 K1B 52 K1B4N7
K6092 K1B 52 K1B4N9
K6092 K1B 52 K1B4M8
K6092 K1B 52 K1B4N9

Vintage of the Postal Walks

The postal walks represented in the 2010 databanks were coded from a December 2010 Canada Post Corporation file.

Old Walk / New Walk File

Since postal walks are subject to change, we will also supply on request, along with postal walk aggregated data and the corresponding concordance file, a third file called the Old walk/New walk file. This file shows the percentage change in the postal walks between the date of the walks to which the data are attached and the latest such information available to us from Canada Post. This file compares the six-character urban postal codes that make up the postal walk at two different points in time. It shows the percentage of the postal codes from the original (old) walk that are included in the newer walk, and the percentage of the new walk that is derived from the old. The following illustration is an example of an old walk/new walk file.

Comparison Between Old Walks (Month XXXX) and New Walks (Month YYYY)
CityID FSA Old walk # New walk # % of old included in new % of new derived from old
K2434 K1B 50 50 94 74
K2434 K1B 50 51 6 8
K2434 K1B 51 50 33 26
K2434 K1B 51 51 61 92
K2434 K1B 51 57 6 5
K2434 K1B 57 57 91 50
K2434 K1B 57 58 9 100
K2434 K1B 52 52 29 10
K2434 K1B 52 60 71 100
K2434 K1B 53 52 20 24
K2434 K1B 53 53 60 100
K2434 K1B 53 58 20 33
K2434 K1B 54 54 93 83
K2434 K1B 54 55 7 5
K2434 K1B 55 55 100 89
K2434 K1B 56 52 30 14
K2434 K1B 56 56 70 100
K2434 K1B 58 52 12 10
K2434 K1B 58 55 12 5

Geographic Levels – Census Geography

Data are also available for the following levels of the Census geography; the following table shows the coded designators for these geographies, as well as a brief description of each.

Level of Geography (L.O.G.) Name Description
61 Census Tract

Census tracts (CTs) are small geographic units representing urban or rural neighbourhood-like communities in census metropolitan areas (see definition below) or census agglomerations with an urban core population of 50,000 or more at time of 1996 Census. CTs are delineated by a committee of local specialists (such as planners, health and social workers and educators) in conjunction with Statistics Canada.

The 2010 databanks contain 4,990 areas coded as level of geography 61, based on 2006 Census.

51 Economic Region

An economic region is a grouping of complete census divisions (see definition below) with one exception in Ontario. Economic regions (ERs) are used to analyse regional economic activity. Within the province of Quebec, ERs are designated by law. In all other provinces, they are created by agreement between Statistics Canada and the provinces concerned. Prince Edward Island and the territories each consist of one economic region.

The 2010 databanks contain 76 areas coded as level of geography 51, based on 2006 Census.

42 Census Agglomeration

The general concept of a census agglomeration (CA) is one of a very large urban area, together with adjacent urban and rural areas that have a high degree of economic and social integration with that urban area. CAs have an urban core population of at least 10,000, based on the previous census.

The 2010 databanks contain 117 areas coded as level of geography 42, based on 2006 Census.

41 Census Metropolitan Area

The general concept of a census metropolitan area (CMA) is one of a very large urban area, together with adjacent urban and rural areas that have a high degree of economic and social integration with that urban area. CMAs have an urban core population of at least 100,000, based on the previous census.

There are 35 CMAs in the 2010 databanks (2006 Census):

001, St. John's, Newfoundland
205, Halifax, Nova Scotia
305, Moncton, New Brunswick
310, Saint John, New Brunswick
408, Saguenay, Québec
421, Québec, Québec
433, Sherbrooke, Québec
442, Trois-Rivières, Québec
462, Montréal, Québec
505, Ottawa-Gatineau (Québec part)
505, Ottawa-Gatineau (Ontario part)
505, Ottawa-Gatineau (Combined)
521, Kingston, Ontario
529, Peterborough, Ontario
532, Oshawa, Ontario
535, Toronto, Ontario
537, Hamilton, Ontario
539, St-Catharines-Niagara, Ontario
541, Kitchener, Ontario
543, Brantford, Ontario
550, Guelph, Ontario
555, London, Ontario
559, Windsor, Ontario
568, Barrie, Ontario
580, Greater Sudbury, Ontario
595, Thunder Bay, Ontario
602, Winnipeg, Manitoba
705, Regina, Saskatchewan
725, Saskatoon, Saskatchewan
825, Calgary, Alberta
835, Edmonton, Alberta
915, Kelowna, British Columbia
932, Abbotsford-Mission, British Columbia
933, Vancouver, British Columbia
935, Victoria, British Columbia

31 Federal Electoral District

A federal electoral district (FED) refers to any place or territorial area represented by a member of Parliament elected to the House of Commons. There are 308 FEDs in Canada according to the 2003 Representation Order. The Representation Order is prepared by the Chief Electoral Officer describing, naming and specifying the population of each electoral district established by the Electoral Boundaries Commission and sent to the Governor in Council.

The 2010 databanks contain 308 areas coded as level of geography 31.

21 Census Division

A census division (CD) is a group of neighbouring municipalities joined together for the purposes of regional planning and managing common services (such as police or ambulance services). A CD might correspond to a county, a regional municipality or a regional district.

CDs are established under laws in effect in certain provinces and territories of Canada. In other provinces and territories where laws do not provide for such areas (Newfoundland, Manitoba, Saskatchewan and Alberta), Statistics Canada defines equivalent areas for statistical reporting purposes in cooperation with these provinces and territories.

The 2010 databanks contain 288 areas coded as level of geography 21, based on the 2006 Census.

Starting in 2008, Census divisions are identified in the tables by an eight digits code:
2 first digits = Province
2 next digits = Economic Region
2 last digits = Census Division

Geographic Levels – Special Geography

Clients may select geographical areas of their own definition; areas that are not part of the standard areas listed here (for example, bank service areas, retail store catchment areas). For this, clients must submit a list of the postal codes that make up their special area, and we will aggregate the micro data to correspond to that area of interest. Information ordered for special, or "user-defined" areas will be coded according to the following:

Level of Geography Name Description
93 Total for all user-defined areas This level represents the sum total of all user-defined areas, and is the total of levels 91 and 92 described below.
92 Other user-defined areas This level of geography represents all user-defined areas that were too small, in terms of population; to have information compiled on those areas individually (i.e. fewer than 100 taxfilers). Such areas are grouped into this "other" category.
91 Special user-defined area Any area showing a code "91" is an area defined by a specific user according to that user's needs (for example, school catchment areas, health districts, etc.)

Conversion files

When a client is interested in purchasing data for areas that are considered non‑standard geography by Income Statistics Division, a conversion file is usually necessary. A combination of postal codes making up one or more special area(s) is commonly referred to as a conversion file – an electronic file used by our staff to aggregate the different postal codes that make up the user-defined area. Simply provide us with the postal codes related to the area and we will compile the data (subject to our confidentiality restrictions). This list should include all postal codes for each area.

This would apply only to an area that is not a standard area. It could include any one or a combination of areas whose boundaries are a combination of standard areas or a combination of postal codes. User-defined areas may be branch service or school catchment areas, neighbourhoods or almost any other region.

Each postal code on a conversion file is linked to a corresponding area code. The postal code is used as the basis for the tabulation of economic and demographic data for each area. Refer to the example below for a typical conversion file received by the Income Statistics Division.

Postal code User Area
A1A1A1 0001
A1A1A2 0001
A1A1A3 0001
A1A1A4 0001
A1A1A5 0001
A1A1A6 0001
A1A1A7 0002
A1A1A8 0002
A1A1A9 0002
A1A1B1 0002
A1A1B2 0002
A1A1B3 0003
A1A1B4 0003
A1A1B5 0003
A1A1B6 0003
A1A1B7 0003
A1A1B8 0004
A1A1B9 0004
A1A1C1 0004
A1A1C2 0004
A1A1C3 0004
Note:
1. The conversion file should have a record length of 10 bytes. The first six bytes should represent the postal code and the following four bytes should represent the user-defined area.
2. The postal code does not have a space between the third and fourth characters.
3. The user-defined area code is only four characters in length.
Our system cannot accommodate user-defined areas with hierarchical levels.  In the previous example, areas 0001 and 0002 could not add up to their own total, with areas 0003 and 0004 adding up to their own separate total. Generating this type of hierarchical information means submitting this conversion file to our programs several times and increasing costs.

We Invite Your Comments

We are always working on ways to improve our products. The comments we receive concerning quality and presentation are essential to meet this objective. If you have any suggestions in this regard, we encourage you, the user, to provide us with your comments.

Data in many forms

Statistics Canada disseminates data in a variety of forms. In addition to publications, both standard and special tabulations are offered. Data are available on the Internet, compact disk, diskette, computer printouts, microfiche and microfilm and magnetic tape. Maps and other geographic reference materials are available for some types of data. Direct online access to aggregated information is possible through CANSIM, Statistics Canada's machine-readable database and retrieval system.

How to obtain more information

Inquiries about these data and related statistics or services should be directed to:

Client Services
Income Statistics Division
Statistics Canada
5th Floor, Jean Talon Building
Ottawa, Ontario K1A 0T6

Telephone: (613) 951-7355
Toll-Free (888) 267-7355
Fax: (613) 951-3012
Toll-Free (888) 267-7355
income@statcan.gc.ca

National enquiries line 1-800-263-1136
National telecommunications device for the hearing impaired 1-800-363-7629
Order-only line (Canada and the United States) 1-800-267-6677
National Toll-free Fax line 1-877-287-4369

You can also visit us on the web: http://www.statcan.gc.ca.

Standards of service to the public

Statistics Canada is committed to serving its clients in a prompt, reliable and courteous manner and in the official language of their choice.  To this end, the agency has developed standards of service which its employees observe in serving its clients.  To obtain a copy of these service standards, please contact your nearest Statistics Canada Regional Reference Centre.

List of Data Products Available

The Income Statistics Division of Statistics Canada tabulates statistical data derived from administrative records - most notably, the taxfile.  The resulting demographic and socio-economic databanks available are listed in the table below, along with their identifying product number and the usual release dates.

Product name Product number Release date
RRSP Contributors 17C0006 Fall
RRSP Contribution Limits (Room) 17C0011 Fall
Canadian Savers 17C0009 Fall
Canadian Investors 17C0007 Fall
Canadian Investment Income 17C0008 Fall
Canadian Taxfilers 17C0010 Fall
Canadian Capital Gains 17C0012 Fall
Charitable Donors 13C0014 Fall
Neighbourhood Income and Demographics 13C0015 Spring
Economic Dependency Profiles 13C0017 Spring
Labour Income Profiles 71C0018 Spring
Families 13C0016 Spring
Seniors 89C0022 Spring
Migration Estimates 91C0025 Fall

 


Notes:

1. The first value represents the 25th percentile and is recalculated periodically.

2. The first value represents the 50th percentile and is recalculated periodically.

3. The first value represents the 75th percentile and is recalculated periodically.

4. The first value represents the 90th percentile and is recalculated periodically.

5. The first value represents the 97th percentile and is recalculated periodically.

6. Likewise, the median income is omitted when the rounded count of a category is less than 20.

 

Canadian Cancer Registry (CCR) System Guide – 2010 Edition

Part II – Data Loading and Tabulation Master Files

Introduction

  • Canadian Cancer Registry Overview
  • CCR System Guide Document Organization
  • Part II Document organization – Data Loading and TMF
  • Changes to the CCR Data Loading and TMF for the 2009 and 2010 Reference Years
    Changes to the CCR Data Loading and TMF for the 2007 and 2008 Reference Years
  • Statistics Canada Contacts

0.1 Canadian Cancer Registry Overview

The patient-oriented Canadian Cancer Registry (CCR) evolved from the event-oriented National Cancer Incidence Reporting System (NCIRS). Beginning with cases diagnosed in 1992, incidence figures collected by Provincial and Territorial Cancer Registries (PTCRs) have been reported to the CCR, which is maintained by Statistics Canada. Established as a person-oriented database, the CCR includes mechanisms for updating and clearing death records and is linked to provincial and territorial databases to help track patients across Canada who have been diagnosed with tumours.

0.2 CCR System Guide Document Organization

The CCR System Guide has been separated into three parts to improve access and navigation. Although the three parts are separate, the three documents should be used in conjunction with each other. The different sections of the three-part CCR System Guide often refer to each other. The CCR System Guide is now composed of:

Part I: CCR Data Dictionary provides explanation on the reporting of data, including the scope and detailed information on the input and derived variables.

Part II: CCR Data Loading and Tabulation Master Files provides information on the data loading process, including in-depth descriptions of the various edits performed on the data. Part II also provides information on the Tabulation Master Files, including the scope, content and layout. Part II is followed by several appendices that contain sup
porting information such as explicit code set tables, guidelines to assist coders and other supportive information.

Part III: CCR Core Reference Tables provides detailed information on the CCR Core Reference Tables such as descriptions of the tables, their usage and any revisions made. Part III is an accompanying document to the Core Reference Tables 2010.xls.

0.3 Part II Document organization – Data Loading and TMF

Chapter 3 – Data loading describes in great detail all the verification performed against reported data prior to their loading into the CCR System. Related business rules, Edit logic and feedback report messages are described for all edits. It also describes the data conditioning and the data posting phase.

Chapter 4 – Tabulation master file describes the main output of the system.

Appendices contain supporting information such as explicit code set tables, guidelines to assist coders, lists of changes from previous versions of the system, etc.

Table 0.4
Changes to the CCR Data Loading and TMF for the 2009 and 2010 Reference Years

Please refer to the relevant section in the System Guide – Data Loading and TMF for more details related to these changes.

Section Item (s) Description of change Effective (reference year
3.3.1 Table 21 Impact of data formatting step on patient data items New variables added – P20, P21 2010
3.3.1 Table 22 Impact of data formatting step on tumour data items New variables added – T58 – T87, change in name for variables T31 and T52, , change in length of variables T24 and T25 and they are now left justified. 2010
3.4.1 PVAL20, PVAL21 New edits added for Date of birth flag, Date of death flag 2010
3.3.1, 3.4.2,4.3 Table 22, Table 25, TVAL27-TVAL41, TVAL52, TCOR1, and TCOR18, Table 36 - TMF record layout Variable Names changed - CS version 1st to CS version input original (acronym changed from TCSFVER to TCSVERINORIG), CS reg nodes eval to CS lymph nodes eval (acronym changed from TCSRNEVAL to TCSLNEVAL). 2010
3.4.2, 3.5.2, 4.3 TVAL27-TVAL41, TCOR1, TCOR18, Table 36 - TMF record layout Length of CS Extension and CS lymph nodes has been changed from 2 to 3. 2010
3.4.2 TABLE 25 New edits added TVAL58 – TVAL83 2010
3.4.2 TVAL24, TVAL25 Edits updated for new code Positive histology PLUS (10) 2010
3.4.2 TVAL58 – TVAL60 New edits added for Date of diagnosis flag, Date of conclusive diagnosis flag, and Date of multiple tumours flag 2010
3.4.2 TVAL42 – TVAL51 Edits no longer applicable (AJCC variables no longer reported) 2009
3.4.2, 3.5.2 TVAL65-TVAL83, TCOR1, TCOR18 New edits added, and edits modified for new site-specific factors 7 - 25 2010
3.4.2, 3.5.2 TVAL61, TVAL62, TCOR36, TCOR37 New edits added for new variables T61 Grade path value and T62 Grade path system 2010
3.4.2 TVAL27-TVAL41, TVAL52 CS version input current added to edits 2010
3.4.2 TVAL64 New edit added for new variable T64 CS version input current 2010
3.4.2 TVAL63 New edit added for new variable T63 Lymph-vascular invasion 2010
3.4.2 TVAL84 – TVAL87 New edits added for new variables T84 CS Mets at Dx – bone, T85 – CS Mets at Dx Brain, T86 – CS Mets at Dx Liver, T87 – CS Mets at Dx Lung 2010
3.5.1 PCOR1 New variables added P20, P21  
3.5.2 TCOR1 New variables added – T58 – T83, change in name for variables T31 and T52. Change in length of the variables T24, T25, T28, T30. 2010
3.5.2 TCOR13 New sub-edits added and existing edits modified to account for new code 10 - Positive histology plus added to Method used to establish date of diagnosis and Diagnostic confirmation  
3.5.2 TCOR19-TCOR24 Edits no longer applicable (AJCC variables no longer reported) 2009
3.5.2 TCOR34 Business rules and edit logic changed : Modified to accept additional combinations. 2008
3.7.1, 3.7.3 Add/Update patient record processing New variables added: Core data items P20 and P21 2010
3.7.2. 3.7.4 Add/Update tumour record processing New variables added: Core data items T53 to T63, T84 to T87, and CS data items T64 to T83. 2010
4.2.2 Table 35 Algorithm used to eliminate duplicate tumours from IARC TMF Behaviour/site ranking to take precedence for duplicate tumours 2008
4.2.2 New table : Table 35b Ranking of behaviour to identify the most 'malignant' tumour: 2008
4.3 Table 36 TMF record layout modified Variables were renamed, changed in length and new variables added. There was also a re-order in the table affecting some positions of variables. 2010
Appendix D Appendix D - Multiple primary tumour rules for CCR Laterality codes changed and were modified for all years. 2007 (changed in guide 2010)
Appendices Appendix K Flavours of null table 2010
Table
Changes to the CCR Data Loading and TMF for the 2007 and 2008 Reference Years
Section Item(s) Description of change Effective (reference year)
3.1.5 Step 2: Core data items validation New validation edits added, TVAL53-57 2008
3.1.5 Step 7: CS data items validation New validation edit TVAL52 added in to step 2007
3.1.7 CS fatal error CS data item T52 added 2007
3.1.7 CS error CS data item T52 added 2007
3.3.1 Data formatting – Table 22 Impact of data formatting step on tumour data items New variables added: T53, T54, T55, T56, T57 2008
New variable added – T52 2007
3.4 Validation Edits –
PVAL6
PVAL7
PVAL8
PVAL9
PVAL13
Business rules changed – acceptable accented characters specified 2007
3.4.2 Tumour validation edits – Table 25 New Tumour validation edits – TVAL53, TVAL54, TVAL55, TVAL56, TVAL57 2008
New Tumour validation edit – TVAL52 2007
3.4.2 Tumour validation edits –
TVAL6
Business rules changed – acceptable accented characters and special characters specified
Edit logic – New edit logic added
Feedback report messages – New messages added
2007
3.4.2 Tumour validation edits –TVAL8 Business rules, Edit logic and Feedback report messages added – SGC 2006 2006
3.4.2 Tumour validation edits –
TVAL9
Business rules, Edit logic and Feedback report messages added – Census tract effective date range ended in 2005. For 2006 onwards T9 must be blank 2006
3.4.2 Tumour validation edits –
TVAL27
TVAL28
TVAL29
TVAL30
TVAL31
TVAL32
TVAL33
TVAL34
TVAL35
TVAL36
TVAL37
TVAL38
TVAL39
TVAL40
TVAL41
Referenced fields, Business rules, Edit logic and Feedback report messages updated: now using recommended version of AJCC CS algorithm 2007
3.4.2 Tumour validation edits –
TVAL52
New validation edit added 2007
3.4.2 Tumour validation edits –
TVAL53
TVAL54
TVAL55
TVAL56
TVAL57
New validation edits added 2008
3.5.2 Tumour correlation edits – Table 27 New correlation edits – TCOR26, TCOR27 2008
3.5.2 Tumour correlation edits – Table 27 New correlation edits – TCOR13 2007
3.5.2 Tumour correlation edits – TCOR1 Referenced fields, Business rules, edit logic changed – new data items added T53, T54, T55, T56, T57 2008
Referenced fields, Business rules, edit logic changed – new data items added T52 2007
3.5.2 Tumour correlation edits – TCOR3 Business rules and Edit logic changed: includes combinations where census tract indicates area outside CMA 2006
3.5.2 Tumour correlation edits – TCOR10
TCOR11
Referenced fields, Business rules, Edit logic and Feedback report messages changed: Verification now includes Date of diagnosis. 2007
3.5.2 Tumour correlation edits – TCOR13 New correlation edit added 2007
3.5.2 Tumour correlation edits – TCOR18 Referenced fields and Edit logic updated: T52 added as a new CS variable 2007
3.5.2 Tumour correlation edits – TCOR26, TCOR27, TCOR29 – TCOR35 New correlation edits 2008
3.6.3 Data item match edits –
DIM6
Revision – Edit no longer used after 2006 2006
3.7.2 Add tumour record processing – CS data items Added new data item T52 2007
3.7.7 Patient derived variable calculation PD7 – Name of variable changed 2007
4.2 Table 24 – Scope - topography codes from ICD-O-2 and ICD-O-3 considered a single site in the definition of multiple cancers Topography group added: C38.4 2007
4.3 Table 36 TMF record layout Addition/deletion of variable – T52 CS version 1st added TD20 deleted 2007
PD7 – Variable acronym changed
New variables added – T53 to T57
2008
4.3 Table 37 – Derived variable calculations at TMF time PD2 – Vital status now derived at TMF time 2007
Appendices Appendices – Appendix A moved to Part III of system guide. Appendix A now included in Part III of system guide 2008
Additions to Appendices Appendix H now includes T53
Appendix I now includes P18
2008
Table 50 – updated table Updated stage group II with T1a, T1b and T1c 2008
New Appendices added to system guide New Appendices
Appendix G – Grade, differentiation or cell indicator guidelines
Appendix H - CCR Ambiguous Terms
Appendix I – Guidelines for abstracting and determining death certificate only (DCO) cases for PTCRs in Canada
2007
Appendix J – Interval between two dates (complete or partial) 2008
Appendices deleted from system guide Appendix Y - Removed and replaced with Section 0.4 Changes to the CCR Data Loading and TMF for the 2007 and 2008 reference years 2008
Appendix Z - References Updates to several references 2007
  • Additional updates have been made; however, only the changes that require action on the part of the PTCRs have been included in this table.

0.5 Statistics Canada Contacts

PTCRs employees are encouraged to bring forward any questions by contacting one of the following:

For additional information regarding the processing of CCR data, please contact:

Colette Brassard
Section Chief
Operations and Integration Division
Statistics Canada
Tel: 613-951-7282
Fax: 613-951-0709
For any subject matter related questions/queries, please contact:

Kim Boyuk
Chief, Cancer Statistics
Health Statistics Division
Statistics Canada
Tel: 613-951-2510
Fax: 613-951-0792

Hollie Anderson
Manager, Canadian Cancer Registry
Health Statistics Division
Statistics Canada
Tel: 613-951-0757
Fax: 613-951-0792

Chapter 3 – Data loading

  • Data importing
  • Data conditioning
  • Data editing
  • Data posting

3.1 Introduction

The data loading process is done in 4 distinct phases:

1. Data importing: Reads in input patient and tumour record files and breaks them down into separate data items using the proper record layout.
2. Data conditioning: Formats the data, filters the old classification data, computes some missing input variables and adjusts the laterality code. This phase alters the reported data.
3. Data editing: Identifies errors in input records and provides sufficient feedback to correct them. This phase does not alter the data. The documentation about this phase has been divided into 3 sections:

  • Validations edits,
  • Correlation edits,
  • Match edits.

4. Data posting: Computes some derived variables, transfers valid data in the CCR database and generates additional reports.

Since the data editing is the most complex phase of the overall process, the remaining pages of the introduction present its key components. An overview of the overall data loading process is also presented at the end of the introduction.

3.1.1 Business rules

The main purpose of the edit process is to enforce a given number of rules on the CCR Data items. Some rules are related to the subject matter (subject matter rules) whereas some others are related to the transmission of data between the PTCR and Statistics Canada (transactional rules). The expression "Business rules" has been retained to express both subject matter and transactional rules that apply to the CCR System.

3.1.2 Edits and sub-edits

Each individual edit in the CCR system enforces a set of related business rules. For the purpose of reporting, an edit may be divided into sub-edits in order to provide more detailed feedback. Thus, each Sub-edit has its own logic and message.

3.1.3 Edit logic

Edit logic are logical expressions that can be evaluated to true or false. They are built from data item names, operators and functions. The principal language elements are described in the following tables.

Table 14
Logical operators
Operator Syntax and meaning
AND expr1 AND expr2
The expression is true if and only if both expr1 and expr2 are true, otherwise the expression is false.
OR expr1 OR expr2
The expression is true whenever expr1 or expr2 is true, otherwise the expression is false.
NOT NOT expr1
The expression is true only if it does not equal expr1, otherwise the expression is false.
Table 15
Comparison operators
Operator Syntax and meaning
<> Expr1 <> expr2
Assesses whether expr1 is different from expr2.
= Expr1 = expr2
Assesses whether expr1 is equal to expr2.
> Expr1 > expr2
Assesses whether expr1 is greater than expr2.
>= Expr1 >= expr2
Assesses whether expr1 is greater than or equal to expr2.
< Expr1 < expr2
Assesses whether expr1 is less than expr2.
<= Expr1 <= expr2
Assesses whether expr1 is less than or equal to expr2.
BETWEEN Expr1 BETWEEN (expr2, expr3)
Assesses whether expr1 is greater than or equal to expr2 and less than or equal to expr3.
LIKE Expr1 LIKE expr2
Assesses whether expr1 complies with expr2 pattern. Expr2 may contain Underscore (_) and percent (%) characters which stand respectively for any single character and any number (including 0) of characters.
Ex: '951-5555' LIKE '951-_ _ _ _' is true.
EX: '951-5555' LIKE '653-_ _ _ _' is false.
Table 16
Functions
Function Syntax and meaning
AVERAGE AVERAGE (X1, X2, ..., Xn)
Returns the arithmetic mean of X: X1+X2+...+Xn / n. This function ignores NULL values.
BLANK BLANK(x1)
Returns x1 blank character(s).
CALCULATE_CCR_CHECK_DIGIT CALCULATE_CCR_CHECK_DIGIT (str1)
Returns a CCR_ID check digit based on str1.
CONTAINS_WORD CONTAINS_WORD (str1, str2, x1)
Assesses whether str1 contains a word of at least x1 character(s) from str2.
IS_COMPOSED_OF IS_COMPOSED_OF (str1, str2)
Assesses whether str1 is only composed of characters from str2.
IS_VALID_DATE IS_VALID_DATE (str1)
Assesses whether str1 is a calendar date.
LENGTH LENGTH (str1)
Returns the length of str1 including trailing blanks.
UPPER UPPER (str1)
Returns str1 where letters and accented characters are converted to their uppercase equivalent. Special characters and numbers remain the same.
Table 17
String operator
Operator Syntax and meaning
|| str1 || str2
Returns a unique string containing str1 and str2 concatenated (juxtaposed).
Table 18
Set operators and symbols
Operator and symbol Syntax and meaning
[] [Expr1,...]
[A-Z]
[A]
Indicates an explicit list of values, a range of values or set of values known as Set A.
IN expr1 IN [A]
Assesses whether expr1 is included in Set A.

3.1.4 Edit families and groups

For ease of use, edits have been grouped into families and groups depending on the scope of the business rules they enforce. There are 3 families:

  1. Validation edits: Enforce business rules on each individual field.
  2. Correlation edits: Enforce business rules between valid fields on the same input record.
  3. Match edits: Enforce business rules between valid fields on different records.

The following table describes the scope of each edit group.

Table 19
Edit scope by family and group
Family Group  Scope
Validation Patient validation (PVAL)  Enforce business rules on Patient fields.
Tumour validation (TVAL)  Enforce business rules on Tumour fields.
Correlation Patient correlation (PCOR)  Enforce business rules between valid Patient fields.
Tumour correlation (TCOR)  Enforcebusiness rules between valid Tumour fields.
Match Key input match (KIM) Ensure that Input patient and Tumour records respect the submission rules in terms of matching keys.
Key base match (KBM) Ensure that Input patient and Tumour records respect the actual state of the CCR in terms of matching keys.
Data item match (DIM) Enforce the business rules between data items (other than keys) found on different records.
Pre–posting match (PPM) Identify error–free4 Input records that cannot be posted to CCR because some other related Input records are either missing or in error.

3.1.5 Edits order of execution and edit control

Because of the dependencies between the edits, edit processing must respect a given order of execution. Since CS and AJCC <abbr title="Tumour, Node, Metastases">TNM</abbr> data item edits depend on core data items, core data item edits must be done first. For each of the following steps, the number of eligible input records will depend on the outcome of preceding steps.

Step 1: Core data items minimum requirements assessment

The core data items minimum requirements consist of an Input record with a valid record type and date of transmission and no missing core data items (P1-P19 or T1-T26). The following edits must be successful in order to respect the minimum requirements:

  • Patient records: PCOR1, PVAL4 and PVAL19.
  • Tumour records: TCOR1, TVAL5 and TVAL26.

Step 2: Core data items validation

Remaining core data items validation edits (PVAL1-19, TVAL1-26 and TVAL53-57) can be performed on the Input records that respect the core data items minimum requirements. The following order must be respected:

  • PVAL11 before PVAL12;
  • PVAL14 before PVAL15 and PVAL17;
  • TVAL12 before TVAL8 and TVAL9;

Step 3: Core data items correlation, key input match and key base match edits

These edits are run based on the outcome of the core data item validation edits. That is, for a given edit, only the Input records where all referenced fields have been successfully validated are eligible. (This implies that Input records that do not respect the minimum requirements or that fail a required field validation edit are not eligible.) These edits can be run in any order.

Step 4: Core data item match edits

Those edits can only be performed on Input records that have no core data items errors. A special processing order must be respected. See Section 3.6.3 Data Item Match Edits for details.

Step 5: Core data items pre-posting match edits

Those edits can only be performed on Input records that have no core data items errors. These edits can be run in any order.

Step 6: CS data items minimum requirements assessment

CS data items minimum requirements consist of an input tumour record with valid date of diagnosis and no missing CS data items. The following edit must be successful in order to respect the minimum requirements:

Tumour records: TCOR18.

Step 7: CS data items validation

CS Validation edits (TVAL27 to 41 and TVAL52) can be performed on the input tumour records that respect the CS minimum requirements and where all core referenced fields are valid. These edits can be run in any order.

Step 8: AJCC TNM data items minimum requirements assessment

AJCC TNM data items minimum requirements consist of an input tumour record with valid date of diagnosis, ICD-O-2/3 topography, ICD-O-3 histology and ICD-O-3 behaviour and no missing AJCC TNM data items. The following edit must be successful in order to respect the minimum requirements SITE-SPECIFIC MEANING: Tumour records: TCOR19.

Step 9: AJCC TNM data items validation

AJCC TNM validation edits (TVAL42 to 51) can be performed on the input tumour records that respect the AJCC TNM minimum requirements and where all core referenced fields are valid. These edits can be run in any order.

Step 10: AJCC TNM data items correlation

These edits are run based on the outcome of previous validation edits. That is, for a given edit, only the Input records where all referenced fields (core and AJCC TNM) have been successfully validated are eligible. These edits can be run in any order.

See section 3.1.9 flowchart of the data loading process for an illustration of the edits dependencies.

3.1.6 Sub-edits order of execution

Except for data item match Sub-edits; all sub-edits from a given edit may be performed in any order. See Section 3.6.3.1 Special order of execution for more details about data item match Sub-edits special order of execution.

3.1.7 Message types

The severity of an error is expressed by its corresponding message's type. The following list describes each possible message type and gives an indication of when they are issued and how they change the editing process flow.

Fatal error: When a group of data items does not respect the minimum requirements. Related editing is stopped.

Core fatal error: Core data items (P1 to P21 and T1 to T26) (except T5 – Input record type), T53 to T63, and T84 to T87) do not respect the minimum requirements. The input record will not undergo any other edits and will be rejected.

CS fatal error: CS data items (T27 to T41 and T52 (CSV1) OR T27 to T41,T52 and T64 to T83 (CSV2))do not respect the minimum requirements. CS data items will not undergo any other related edits and will not be loaded on the CCR database. CS Fatal error does not prevent valid core and AJCC TNM data items from being loaded on the CCR database.1

AJCC TNM Fatal error: AJCC TNM data items (T42 to T51) do not respect the minimum requirements. AJCC TNM data items will not undergo any other related edits and will not be loaded on the CCR database. AJCC TNM fatal error does not prevent valid core and CS data items from being loaded on the CCR database.5

Error: Normal edits failure. Editing is not stopped. Unless specified otherwise, the input record can be edited by other edits based on the validity of their corresponding referenced fields.

Core error: Error found in core patient (P1 to P21) or Tumour (T1 to T26) data items. Core error causes the Input record to be rejected.

CS error: Error found in CS data items (T27 to T41 and T52 (CSV1) OR T27 to T41, T52 and T64 to T83 (CSV2))). CS data items will not be loaded on the CCR database.CS error does not prevent valid core and AJCC TNM data items from being loaded on the CCR database.5

AJCC TNM error: Error found in AJCC TNM data items (T42 to T51). AJCC TNM data items will not be loaded on the CCR database. AJCC TNM error does not prevent valid core and CS data items from being loaded on the CCR database.5

Warning: Informative message to PTCR. Warnings do not prevent Inputrecords from being loaded on the CCR.

3.1.8 Edit description pages

For ease of use, each edit is described using a standard format: name, purpose, referenced fields, business rules, edit logic and feedback report messages. When needed, other parameters, revisions and notes are also added to give more detail. The following table describes each possible section.

Table 20
Edit presentation breakdown
Section Description
Name A unique name for the edit.
Purpose Edit main purpose.
Referenced fields List of all input file fields (or part of fields) involved in the edit.
Other parameters List of additional parameters needed to perform the edit.
Business rules Rules that describe the eligible field value or relationship between many field values. These rules are written in plain English.
Edit logic Each Sub-edit condition that identifies invalid records. These conditions are usually written using logical expressions.
Feedback report messages List of all possible edit messages.
Revision List of all changes that have been applied to the edit over time.
Notes Any remarks.

3.1.9 Flowchart of the data loading process

3.1.9 Flowchart of the data loading process

Notes:
*See 3.1.5 Edits Order of Execution and Edit Control for exact sequencing.
**DIM Edits have a special processing order. See specific section for more details.

3.2 Data importing

During the data importing phase, the input patient record file and/or input tumour record file is read in by the system. Every record is then cut into separate data items using the proper record layout.

3.2 Data Importing

3.3 Data conditioning

The purpose of the data conditioning phase is threefold. Its intent is to:

  • Reduce PTCR response burden by automatically correcting small errors such as the use of lowercase characters in code fields or improper alignment of values.
  • Eliminate older classification data (ICD-9 and ICD-O-2) when not reported as the source classification data. This eliminates the risk of incoherence between the source classification and any former classification data.
  • Bring all reported data up to a uniform classification (ICD-O-3). This facilitates a comparison of all tumours reported to the CCR.

To achieve these objectives, the following steps are performed on the data:

  1. Data formatting;
  2. Old classification filtering;
  3. ICD-O-2/3 topography calculation;
  4. ICD-O-3 histology and behaviour calculation; and,
  5. Laterality adjustment.

The steps listed above must be executed in sequential order. Each step may alter the reported data. Refer to the corresponding section below for a description of how these reported data are altered.

3.3.1 Data formatting

Description

Data formatting is composed of three operations:

Left justified: Removes blank character preceding the data item value.

Uppercase: Converts all lower case alphabetic characters to uppercase letters.
Converts lower case French accents (é, è, ê, ë, ç…) to corresponding uppercase letters (é à É). Special characters and digits remain unchanged.

Removal of trailing blanks: Removes any blank characters trailing the data item value. Data items containing only blank characters will be converted to NULL. This is an important assumption used in the data editing phase.

Purpose

Data formatting reduces PTCR response burden by fixing small formatting errors that would otherwise cause an input record to be rejected. It also converts blank data items to NULL values in order to be compliant with the data editing specification.

Logic

  • Left justification is applied on any fields longer than 1 character.
  • Uppercase is applied on any fields that may contain letters.
  • Removal of trailing blanks is applied on all fields.

The following two tables summarize the impact of the data formatting step on patient and tumour data items. X and – indicate whether the corresponding transformation is applicable or not.

Table 21
Impact of data formatting step on patient data items
Variable Name  Variable Left justify Uppercase Removal of trailing blanks
P1 Patient reporting province/territory X - X
P2 Patient identification number X X X
P3 CCR identification number X - X
P4 Patient record type - - X
P5 Type of current surname - - X
P6 Current surname X X X
P7 First given name X X X
P8 Second given name X X X
P9 Third given name X X X
P10 Sex - - X
P11 Date of birth X - X
P12 Province/territory or country of birth X - X
P13 Birth surname X X X
P14 Date of death X - X
P15 Province/territory or country of death X - X
P16 Death registration number X - X
P17 Underlying cause of death X X X
P18 Autopsy confirming cause of death - - X
P19 Patient date of transmission X - X
P20 Date of birth flag X - X
P21 Date of death flag X - X
Table 22
Impact of data formatting step on tumour data items
Variable Name  Variable Left justify Uppercase Remove trailing blank
T1 Tumour reporting province/territory X - X
T2 Tumour patient identification number X X X
T3 Tumour reference number X X X
T4 CCR identification number X - X
T5 Tumour record type - - X
T6 Name of place of residence X X X
T7 Postal code X X X
T8 Standard geographic code X - X
T9 Census tract X - X
T10 Health insurance number X X X
T11 Method of diagnosis - - X
T12 Date of diagnosis X - X
T13 ICD–9 cancer code X - X
T14 Source classification flag - - X
T15 ICD–O–2/3 Topography X X X
T16 ICD–O–2 Histology X - X
T17 ICD–O–2 Behaviour X - X
T18 Filler - - -
T19 Laterality - - X
T20 Filler - - -
T21 ICD–O–3 Histology X - X
T22 ICD–O–3 Behaviour - - X
T23 Grade, differentiation or cell indicator - - X
T24 Method used to establish the date of diagnosis X - X
T25 Diagnostic confirmation X - X
T26 Date of transmission X - X
T27 CS tumour size X - X
T28 CS extension X - X
T29 CS tumour size/ext eval - - X
T30 CS lymph nodes X - X
T31 CS lymph nodes eval - - X
T32 Regional nodes examined X - X
T33 Regional nodes positive X - X
T34 CS mets at dx X - X
T35 CS mets eval - - X
T36 CS site-specific factor 1 X - X
T37 CS site-specific factor 2 X - X
T38 CS site-specific factor 3 X - X
T39 CS site-specific factor 4 X - X
T40 CS site-specific factor 5 X - X
T41 CS site-specific factor 6 X - X
T42 AJCC clinical T X X X
T43 AJCC clinical N X X X
T44 AJCC clinical M X X X
T45 AJCC pathologic T X X X
T46 AJCC pathologic N X X X
T47 AJCC pathologic M X X X
T48 AJCC clinical TNM stage group X X X
T49 AJCC pathologic TNM stage group X X X
T50 AJCC TNM stage group X X X
T51 AJCC TNM edition number X - X
T52 CS version input original X - X
T53 Ambiguous terminology diagnosis - - X
T54 Date of conclusive diagnosis X - X
T55 Type of multiple tumours reported as one primary X - X
T56 Date of multiple tumours X - X
T57 Multiplicity counter X - X
T58 Date of diagnosis flag X - X
T59 Date of conclusive diagnosis flag X - X
T60 Date of multiple tumours flag X - X
T61 Grade path Value - - X
T62 Grade path System - - X
T63 Lymph-vascular invasion - - X
T64 CS version input current X - X
T65 CS site-specific factor 7 X - X
T66 CS site-specific factor 8 X - X
T67 CS site-specific factor 9 X - X
T68 CS site-specific factor 10 X - X
T69 CS site-specific factor 11 X - X
T70 CS site-specific factor 12 X - X
T71 CS site-specific factor 13 X - X
T72 CS site-specific factor 14 X - X
T73 CS site-specific factor 15 X - X
T74 CS site-specific factor 16 X - X
T75 CS site-specific factor 17 X - X
T76 CS site-specific factor 18 X - X
T77 CS site-specific factor 19 X - X
T78 CS site-specific factor 20 X - X
T79 CS site-specific factor 21 X - X
T80 CS site-specific factor 22 X - X
T81 CS site-specific factor 23 X - X
T82 CS site-specific factor 24 X - X
T83 CS site-specific factor 25 X - X
T84 CS Mets at Dx - Bone - - X
T85 CS Mets at Dx - Brain - - X
T86 CS Mets at Dx - Liver - - X
T87 CS Mets at Dx - Lung - - X

Revision

Year Description
2010 Tumour variables T58 – T87 have been added to the record layout. There have been name changes to T31 and T52, and the length of T24 and T25 have been modified so they must now be left justified.
2008 Tumour input variables T53 to T57 have been added to the record layout. Different formatting processes are done to each new variable.
2007 T52 – CS version input original (formerly CS Version 1st) – tumour input variable added to record layout. It is left justified and trailing blanks are removed.
2004 In order to reduce response burden, some data items will automatically be uppercased, left justified and right truncated (removal of trailing blanks) by the CCR system.
T3 – Tumour reference number: Values will not be zero left filled anymore.

3.3.2 Old classification filtering

Description

This step deletes disease classification information reported by PTCRs older than that indicated by the source classification flag.

Purpose

This step eliminates the possibility of incoherence between source classification data (as identified by the source classification flag) and any former classification data.

Logic

  • If the Source classification flag indicates that ICD-9 is the source classification, then all reported data are kept as is.
  • If the Source classification flag indicates that ICD-O-2 is the source classification, then reported ICD-9 Cancer Code is replaced by '0000'.
  • If the Source classification flag indicates that ICD-O-3 is the source classification, then reported ICD-9 Cancer Code and ICD-O-2 Histology are replaced by '0000' and reported ICD-O-2 Behaviour is replaced by '0'.
  • In any other case, all reported data are kept as is.

This step will not create a feedback message. The following examples and table illustrate possible scenarios.

Example 1: If source classification flag indicates ICD-9, then no change.
Example 2: If source classification flag indicates ICD-O-2, then ICD-9 is not loaded.
Example 3: If source classification flag indicates ICD-O-3, then ICD-9 and ICD-O-2H/B are not loaded. ICD-O-2/3T is kept since it also belongs to ICD-O-3.

Table 23
Old classification filtering
Example TSCF ICD-9 ICD-O-2/3T ICD-O-2H ICD-O-2B ICD-O-3H ICD-O-3B
1 Before 1 175 C509 8521 3 8521 3
After 1 175 C509 8521 3 8521 3
2 Before 2 175 C509 8521 3 8521 3
After 2 0000 C509 8521 3 8521 3
3 Before 4 175 C509 8521 3 8521  
After 4 0000 C509 0000 0 8521 3

3.3.3 ICD-O-2/3 Topography calculation

Background

For cases diagnosed from 1992 to 2000, the Canadian Council of Cancer Registries adopted the International Classification of Diseases for Oncology, Second Edition (ICD-O-2) as the standard for reporting diagnostic information to the Canadian Cancer Registry (CCR). This classification was chosen because it provides detailed information on the site (topography), the histology and the behaviour of the neoplasm. The site codes are based on the malignant neoplasms section (C00-C80) of the International Statistical Classification of Diseases and Related Health Problems, Tenth revision (ICD-10). The morphology codes are revised and expanded from its predecessor, the ICD-O-1. The International Classification of Diseases is a classification system which covers the broad range of diseases and other health problems for which health care services may be rendered. The ICD has been in use in Canada for many decades for morbidity (hospitalization) and mortality (death) reporting. The Ninth revision (ICD-9), in use since 1979, has been replaced by the ICD-10 for morbidity and mortality. Chapter 2 of the ICD-9 (Neoplasms) provides a classification of tumours, primarily by site and includes behaviour. The ICD-O-2 supplements site information with tumour morphology detail. This greater level of specificity makes ICD-O more suitable for cancer registration purposes.

By 1992, the data year for which the CCR became operational, all provincial/territorial cancer registries except Ontario and Québec had implemented the ICD-O-2 for reporting tumour site and morphology. Ontario and Québec had adopted the ICD-O-2 for reporting tumour morphology information, but continued to report the site of tumours using the ICD-9, for administrative reasons. In order to bring all data to a common basis, the ICD-9 to ICD-O-2 conversion was created, cooperatively by Statistics Canada, the Ontario Cancer Treatment and Research Foundation and the Fichier des tumeurs du Québec.

Description

This step computes ICD-O-2/3 Topography code from the reported ICD-9 Cancer code when needed.

Purpose

This step ensures that, for each reported tumour, the site is described using the ICD-O-3 classification. This facilitates the comparison between all tumours reported to the CCR.

Logic

If ICD-O-2/3 Topography = '0000' and Source classification flag = '1' then
If ICD-9 Cancer code is found in ICD-9 to ICD-O-2 conversion table6 then
ICD-O-2/3 Topography = ICD-O-2/3 Topography code associated to ICD-9 Cancer code in ICD-9 to ICD-O-2 conversion table.
Else (ICD-9 Cancer code is NULL or NOT found in ICD-9 to ICD-O-2 conversion table)
Warning saying "ICD-O-2/3 Topography calculation: Conversion failed." is sent to the reporting PTCR.
End If
End If

Directions

The process of converting coded information from one disease classification system to another can result in a distortion or loss of original diagnostic detail. Whenever possible, it is recommended that the original descriptive diagnosis be coded directly, using the preferred, most recent classification system.

Registries using both the ICD-O-2/3 topography and the ICD-9 to code tumour sites are requested to report only ICD-O-2/3 topography codes to the CCR. ICD-9 codes should only be reported to the CCR if ICD-O-2/3 topography codes are not available.

3.3.4 ICD-O-3 Histology and behaviour calculation

Background

For cases diagnosed from 2001 onwards, the Canadian Council of Cancer Registries adopted the International Classification of Diseases for Oncology, Third edition (ICD-O-3) as the standard for reporting diagnostic information to the Canadian Cancer Registry (CCR). The topography section of the Third edition remains the same as the Second edition; however it includes revised morphologies and new classifications especially for lymphomas and leukemias. This classification was adopted because it represents the most current classification of diseases for oncology.

Description

This step computes the ICD-O-3 Histology and the ICD-O-3 behaviour from reported ICD-O-2 histology and ICD-O-2 behaviour when needed.

Purpose

This step ensures that, for each reported tumour, the histology and behaviour are described using the ICD-O-3 classification. This facilitates the comparison between all tumours reported to the CCR.

If ICD-O-3 Histology = '0000' and ICD-O-3 Behaviour = '0' and Source Classification Flag = '1' or '2' 'then
If ICD-O-2/3 Topography, ICD-O-2 Histology and ICD-O-2 Behaviour combination is found in ICD-O-2 to ICD-O-3 conversion table6 then
ICD-O-3 Histology = ICD-O-3 Histology code associated to ICD-O-2/3 Topography, ICD-O-2 Histology and ICD-O-2 Behaviour combination in ICD-O-2 to ICD-O-3 conversion table
ICD-O-3 Behaviour = ICD-O-3 Behaviour code associated to ICD-O-2/3 Topography, ICD-O-2 Histology and ICD-O-2 Behaviour combination in ICD-O-2 to ICD-O-3 conversion table
If the Review Flag associated to ICD-O-2/3 Topography, ICD-O-2 Histology and ICD-O-2 Behaviour combination in ICD-O-2 to ICD-O-3 conversion table = '1' then
Warning saying "ICD-O-3 Histology and Behaviour calculation: Values must be manually reviewed." is sent to the reporting PTCR.
Else (ICD-O-2/3 Topography is NULL or ICD-O-2 Histology is NULL or ICD-O-2 Behaviour is NULLor the combination is NOT found in ICD-O-2 to ICD-O-3 conversion table)
Warning saying "ICD-O-3 Histology and Behaviour calculation: Conversion failed." is sent to the reporting PTCR.
End If
End If

This step ensures that, for each reported tumour, the histology and behaviour are described using the ICD-O-3 classification. This facilitates the comparison between all tumours reported to the CCR

3.3.5 Laterality adjustment

Background

Although the ICD-9 and the ICD-O-3 may be used for similar purposes, they are not totally compatible. Since the ICD-9 and the ICD-O-3 use different topographic groupings, there are cases where the laterality code may be coherent with a given ICD-9 Cancer code but may be incoherent with the closest corresponding ICD-O-2/3 topography code. Thus, for these exceptional cases, the laterality code must be altered to be compliant with the ICD-O-3 classification.

Description

This step alters the laterality code when specific ICD-9 Cancer codes are reported as source classification data and corresponding ICD-O-2/3 topography codes conflict with the reported laterality code due to classification incompatibility.

Purpose

This step reduces PTCR response burden by fixing classification incompatibility issues that would otherwise cause an input record to be rejected.

Logic

If Source Classification Flag = '1' and ICD-9 Cancer Code in ['1460','2021','2022','2382'] and Laterality = '0' then
Laterality = '9'
Warning saying "Laterality Adjustment: Laterality code has been changed from '0' to '9' in order to be compliant with ICD-O-3 classification." is sent to the reporting PTCR.
End if

3.4 Validation Edits

The purpose of the Validation edits is to enforce the business rules on each individual field. For ease of use, validation edits have been divided into two groups:

  • Patient validation edits: enforce business rules on patient fields;
  • Tumour validation edits: enforce business rules on tumour fields.

3.4.1 Patient validation edits

The following table summarizes the purpose of each individual edit of this category.

Table 24
Patient validation edits summary
Edit name Purpose
PVAL1 Validates the Patient reporting province/territory code.
PVAL2 Validates the Patient identification number.
PVAL3 Validates the CCR identification number.
PVAL4 Validates the Patient record type code.
PVAL5 Validates the Type of current surname code.
PVAL6 Validates the Current surname.
PVAL7 Validates the First given name.
PVAL8 Validates the Second given name.
PVAL9 Validates the Third given name.
PVAL10 Validates the Sex code.
PVAL11 Validates the Date of birth.
PVAL12 Validates the Province/territory or country of birth code.
PVAL13 Validates Birth surname.
PVAL14 Validates Date of death.
PVAL15 Validates the Province/territory or country of death code.
PVAL16 Validates Death registration number.
PVAL17 Validates the Underlying cause of death code.
PVAL18 Validates Autopsy confirming cause of death code.
PVAL19 Validates Patient record date of transmission.
PVAL20 Validates Date of birth flag.
PVAL21 Validates Date of death flag.

PVAL1

This edit validates the patient reporting province/territory code.

Table
Referenced fields (PVAL1)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
Table
Other parameters (PVAL1)
Parameters Length Description
PTCR_CODE 2 Province/territory code of the PTCR that is submitting the data.

Business rules

For Input patient records
  • Patient reporting province/territory must be equal to province/territory code of the PTCR submitting the data7.
Table
Edit logic (PVAL1)
Sub–edit  Conditions Outcome
PVAL1-1 P1 <> PTCR_CODE Record rejected
Table
Feedback report messages (PVAL1)
Sub–edit  Text Type
PVAL1-1 Patient reporting province/territory code does not match PTCR province/territory code. Core error
Table
Revision (PVAL1)
Year Description
Not applicable Not applicable

PVAL2

Purpose

This edit validates the patient identification number.

Table
Referenced fields (PVAL2)
Field Length Description Acronym
P2 12 Patient identification number PPIN

Business rules

On any type of Input patient record, Patient identification number
  • Must be exclusively composed of any of the following:
    • Uppercase letters: A to Z
    • Numbers: 0 to 9
  • Cannot be exclusively composed of zeros.
Table
Edit logic (PVAL2)
Sub–edit  Conditions Outcome
PVAL2-1 IS_COMPOSED_OF (P2, '0') Record rejected
PVAL2-2 NOT IS_COMPOSED_OF (P2, 'ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789') Record rejected
Table
Feedback report messages (PVAL2)
Sub–edit  Text Type
PVAL2-1 Patient identification number cannot be exclusively composed of zeros. Core error
PVAL2-2 Patient identification number is not exclusively composed of uppercase letters and/or numbers. Core error
Table
Revision (PVAL2)
Year Description
2004 Business rule changed: Apostrophes, hyphens, periods and inner spaces are not accepted anymore.

PVAL3

Purpose

This edit validates the CCR identification number.

Table
Referenced fields (PVAL3)
Field Length Description Acronym
P3 9 CCR identification number CCR_ID
P3.ID 8 First 8 digits of P3 (CCR ID sequence number) Not applicable
P3.CHECK_DIGIT 1 9th digit of P3 (CCR ID check digit) Not applicable
P4 1 Patient record type PRECTYPE

Business rules

For Update and Delete Patient records, CCR identification number
  • Must be exclusively composed of numbers: 0 to 9
  • Must be 9 digits long.
  • Cannot be all zeros.
  • Must have a valid check digit8.
Table
Edit logic (PVAL3)
Sub–edit  Conditions Outcome
PVAL3-1 P4 IN ['2', '3'] AND (LENGTH (P3) <> 9 OR NOT IS_COMPOSED_OF (P3, '0123456789')) Record rejected
PVAL3-2 P4 IN ['2', '3'] AND P3 = '000000000' Record rejected
PVAL3-3 P4 IN ['2', '3'] AND P3 <> '000000000' AND LENGTH (P3) = 9 AND IS_COMPOSED_OF (P3, '0123456789') AND P3.CHECK_DIGIT <> CALCULATE_CCR_CHECK_DIGIT (P3.ID) Record rejected
Table
Feedback report messages (PVAL3)
Sub–edit  Text Type
PVAL3-1 CCR identification number is not 9 digits long. Core error
PVAL3-2 CCR identification number cannot be all zeros. Core error
PVAL3-3 CCR identification number is invalid. Core error
Table
Revision (PVAL3)
Year Description
Not applicable Not applicable

PVAL4

Purpose

This edit validates the patient record type code.

Table
Referenced fields (PVAL4)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE

Business rules

For Input Patient records, Patient record type
  • Cannot be blank.
  • Must be one of the Eligible patient record type codes9.
Table
Edit logic (PVAL4)
Sub–edit  Conditions Outcome
PVAL4-1 P4 IS NULL OR P4 NOT IN [Eligible Patient record type codes] Record rejected
Table
Feedback report messages(PVAL4)
Sub–edit  Text Type
PVAL4-1 Patient record type code is missing or invalid. Core fatal error
Table
Revision (PVAL4)
Year Description
Not applicable Not applicable

PVAL5

Purpose

This edit validates the type of current surname code.

Table
Referenced fieldds (PVAL5)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P5 1 Type of current surname PTYP_CUR

Business rules

For Add and Update Patient records
  • Type of Current Surname must be one of the Eligible type of current surname codes10.
Table
Edit logic (PVAL5)
Sub–edit  Conditions Outcome
PVAL5-1 P4 IN ['1', '2'] AND P5 NOT IN [Eligible type of current surname codes] Record rejected
Table
Feedback report messages (PVAL5)
Sub–edit  Text Type
PVAL5-1 Type of current surname code is invalid. Core error
Table
Revision (PVAL5)
Year Description
Not applicable Not applicable

PVAL6

Purpose

This edit validates the current surname.

Table
Referenced fields (PVAL6)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P6 25 Current surname PCURSNAM

Business rules

For Add and Update Patient records
  • Current surname can be blank.
  • If Current surname is not blank then
    • It must be exclusively composed of any of the following:
      • Letters: A to Z (upper or lowercase)
      • Accented characters: Â À Ç É Ê Ë È Î Ï Ô Û Ü (upper or lowercase)
      • Special characters: space ( ), period (.), apostrophe ('), hyphen (-)
    • It must contain at least one letter.
Table
Edit logic (PVAL6)
Sub–edit  Conditions Outcome
PVAL6-1 P4 IN ['1', '2'] AND P6 IS NOT NULL AND NOT IS_COMPOSED_OF (UPPER (P6), 'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') Record rejected
PVAL6-2 P4 IN ['1', '2'] AND P6 IS NOT NULL AND IS_COMPOSED_OF (UPPER (P6), 'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') AND NOT CONTAINS_WORD (UPPER (P6), 'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ', 1) Record rejected
Table
Feedback report messages (PVAL6)
Sub–edit  Text Type
PVAL6-1 Current surname is not exclusively composed of acceptable letters, accented characters or special characters. Core error
PVAL6-2 Current surname does not contain at least one letter. Core error
Table
Revision (PVAL6)
Year Description
2007 Business rules changed: Acceptable accented characters are specified.
2004 Business rules changed: Titles are now allowed in current surname.

PVAL7

Purpose

This edit validates the first given name.

Table
Referenced fields (PVAL7)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P7 15 First given name PGNAME_1

Business rules

For Add and Update Patient records
  • First given name can be blank.
  • If First given name is not blank then
    • It must be exclusively composed of any of the following:
      • Letters: A to Z (upper or lowercase)
      • Accented characters: Â À Ç É Ê Ë È Î Ï Ô Û Ü (upper or lowercase)
      • Special characters: space ( ), period (.), apostrophe ('), hyphen (-)
    • It must contain at least one letter.
Table
Edit logic (PVAL7)
Sub–edit  Conditions Outcome
PVAL7-1 P4 IN ['1', '2'] AND P7 IS NOT NULL AND NOT IS_COMPOSED_OF (UPPER (P7), 'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') Record rejected
PVAL7-2 P4 IN ['1', '2'] AND P7 IS NOT NULL AND IS_COMPOSED_OF (UPPER (P7),'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') AND NOT CONTAINS_WORD (UPPER (P7), 'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ', 1) Record rejected
Table
Feedback report messages (PVAL7)
Sub–edit  Text Type
PVAL7-1 First given name is not exclusively composed of acceptable letters, accented characters or special characters. Core error
PVAL7-2 First given name does not contain at least one letter. Core error
Table
Revision (PVAL7)
Year Description
2007 Business rules changed: Acceptable accented characters are specified.

PVAL8

Purpose

This edit validates the second given name.

Table
Referenced fields (PVAL8)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P8 15 Second given name PGNAME_2

Business rules

For Add and Update Patient records
  • Second given name can be blank.
  • If Second given name is not blank then
    • It must be exclusively composed of any of the following:
      • Letters: A to Z (upper or lowercase)
      • Accented characters: Â À Ç É Ê Ë È Î Ï Ô Û Ü (upper or lowercase)
      • Special characters: space ( ), period (.), apostrophe ('), hyphen (-)
    • It must contain at least one letter
Table
Edit logic(PVAL8)
Sub–edit  Conditions Outcome
PVAL8-1 P4 IN ['1', '2'] AND P8 IS NOT NULL AND NOT IS_COMPOSED_OF (UPPER (P8), 'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') Record rejected
PVAL8-2 P4 IN ['1', '2'] AND P8 IS NOT NULL AND IS_COMPOSED_OF (UPPER (P8), 'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') AND NOT CONTAINS_WORD (UPPER (P8), 'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ', 1) Record rejected
Table
Feedback report messages (PVAL8)
Sub–edit  Text Type
PVAL8-1 Second given name is not exclusively composed of acceptable letters, accented characters or special characters. Core error
PVAL8-2 Second given name does not contain at least one letter. Core error
Table
Revision (PVAL8)
Year Description
2007 Business rules changed: Acceptable accented characters are specified.

PVAL9

Purpose

This edit validates the third given name.

Table
Referenced fields (PVAL9)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P9 7 Third given name PGNAME_3

Business rules

For Add and Update Patient records
  • Third given name can be blank.
  • If Third given name is not blank then
    • It must be exclusively composed of any of the following:
      • Letters: A to Z (upper or lowercase)
      • Accented characters: Â À Ç É Ê Ë È Î Ï Ô Û Ü (upper or lowercase)
      • Special characters: space ( ), period (.), apostrophe ('), hyphen (-)
    • It must contain at least one letter.
Table
Edit logic (PVAL9)
Sub–edit  Conditions Outcome
PVAL9-1 P4 IN ['1', '2'] AND P9 IS NOT NULL AND NOT IS_COMPOSED_OF (UPPER (P9), 'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') Record rejected
PVAL9-2 P4 IN ['1', '2'] AND P9 IS NOT NULL AND IS_COMPOSED_OF (UPPER (P9), 'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') AND NOT CONTAINS_WORD (UPPER (P9), 'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ', 1) Record rejected
Table
Feedback report messages (PVAL9)
Sub edit  Text Type
PVAL9-1 Third given name is not exclusively composed of acceptable letters, accented characters or special characters. Core error
PVAL9-2 Third given name does not contain at least one letter. Core error
Table
Revision (PVAL9)
Year Description
2007 Business rules changed: Acceptable accented characters are specified.

PVAL10

Purpose

This edit validates the sex code.

Table
Referenced fields (PVAL10)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P10 1 Sex PSEX

Business rules

For Add and Update Patient records
  • Sex must be one of the Eligible sex codes11.
Table
Edit logic (PVAL10)
Sub–edit  Conditions Outcome
PVAL10-1 P4 IN ['1', '2'] AND P10 NOT IN [Eligible sex codes] Record rejected
Table
Feedback report messages (PVAL10)
Sub–edit  Text Type
PVAL10-1 Sex code is invalid. Core error
Table
Revision (PVAL10)
Year Description
Not applicable Not applicable

PVAL11

Purpose

This edit validates the date of birth.

Table
Referenced fields (PVAL11)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P11 8 Date of birth PDATBIR
P11.YEAR 4 First 4 digits of P11 (year of date of birth) Not applicable
P11.MONTH 2 5th and 6th digits of P11 (month of date of birth) Not applicable
P11.DAY 2 7th and 8th digits of P11 (day of date of birth) Not applicable
Table
Other parameters (PVAL11)
Parameters Length Description
CYCLE_YEAR 2 Reference year

Business rules

For Add and Update Patient records, Date of birth
  • Must be 8 digits long.
  • Must be between January 1st, 1875 and December 31st of Reference year inclusively.
  • If Year is unknown then Month must be unknown.
  • If Month is unknown then Day must be unknown.
  • If Year, Month and Day are known then it must be a valid calendar date.
  • If Year and Month are known and Day is unknown then month must be a valid month.
Table
Edit logic (PVAL11)
Sub–edit  Conditions Outcome
PVAL11-1 P4 IN ['1', '2'] AND (LENGTH (P11) <> 8 OR NOT IS_COMPOSED_OF (P11, '0123456789')) Record rejected
PVAL11-2 P4 IN ['1', '2'] AND LENGTH (P11) = 8 AND IS_COMPOSED_OF (P11, '0123456789') AND ((P11.YEAR = '9999' AND P11.MONTH <> '99') OR (P11.MONTH = '99' AND P11.DAY <> '99')) Record rejected
PVAL11-3 P4 IN ['1', '2'] AND LENGTH (P11) = 8 AND IS_COMPOSED_OF (P11, '0123456789') AND P11.YEAR <> '9999' AND (P11.YEAR < 1875 OR P11.YEAR > CYCLE_YEAR) Record rejected
PVAL11-4 P4 IN ['1', '2'] AND LENGTH (P11) = 8 AND IS_COMPOSED_OF (P11, '0123456789') AND P11.YEAR <> '9999' AND P11.MONTH <> '99' AND P11.DAY <> '99' AND IS_VALID_DATE (P11) Record rejected
PVAL11-5 P4 IN ['1', '2'] AND LENGTH (P11) = 8 AND IS_COMPOSED_OF (P11, '0123456789') AND P11.YEAR <> '9999' AND P11.MONTH NOT IN ['01'-'12', '99'] AND P11.DAY = '99' Record rejected
Table
Feedback report messages (PVAL11)
Sub–edit  Text Type
PVAL11-1 Date of birth is not 8 digits long. Core error
PVAL11-2 Date of birth: Improper use of the 'Unknown' code. Core error
PVAL11-3 Date of birth must be between the year 1875 and the current reference year inclusively. Core error
PVAL11-4 Date of birth is not a valid calendar date. Core error
PVAL11-5 Date of birth is not a valid partial date: month is invalid. Core error
Table
Revision (PVAL11)
Year Description
Not applicable Not applicable

PVAL12

Purpose

This edit validates the province/territory or country of birth code.

Table
Referenced fields (PVAL12)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P11.YEAR 4 First 4 characters of P11 (year of date of birth) Not applicable
P12 3 Province/territory or country of birth PPROVBIR

Business rules

For Add and Update Patient records
  • If Date of birth is before 1996 then Province/territory or country of birth must be one of the Eligible Province/territory and country codes prior to 199612.
  • If Date of birth is on or after 1996 then Province/territory or country of birth must be one of the Eligible Province/territory and country codes in and after 199612
  • If Date of birth is unknown then Province/territory or country of birth must be either one of the Eligible Province/territory and country codes prior to 199612 or Eligible Province/territory and country codes in and after 199612.
Table
Edit logic (PVAL12)
Sub–edit  Conditions Outcome
PVAL12-1 P4 IN ['1', '2'] AND P11.YEAR <> '9999' AND P11.YEAR < 1996 AND P12 NOT IN [Eligible Province/territory and country code prior to 1996] Record rejected
PVAL12-2 P4 IN ['1', '2'] AND P11.YEAR <> '9999' AND P11.YEAR >= 1996 AND P12 NOT IN [Eligible Province/territory and country code in and after 1996] Record rejected
PVAL12-3 P4 IN ['1', '2'] AND P11.YEAR = '9999' AND P12 NOT IN [Eligible Province/territory and country code prior to 1996] AND P12 NOT IN [Eligible Province/territory and country code in and after 1996] Record rejected
Table
Feedback report messages (PVAL12)
Sub–edit  Text Type
PVAL12-1 Province/territory or country of birth code is invalid for Date of birth prior to 1996. Core error
PVAL12-2 Province/territory or country of birth code is invalid for Date of birth in and after 1996. Core error
PVAL12-3 Province/territory or country of birth code is invalid. Core error
Table
Revision PVAL12)
Year Description
2004 Business rules changed: Province/territory or country of birth code is now validated against Province/territory or country codes valid at time of birth.

PVAL13

Purpose

This edit validates birth surname.

Table
Referenced fields (PVAL13)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P13 25 Birth surname PBIRNAM

Business rules

For Add and Update Patient records
  • Birth surname can be blank.
  • If Birth surname is not blank then
    • It must be exclusively composed of any of the following:
      • Letters: A to Z (upper or lowercase)
      • Accented characters: Â À Ç É Ê Ë È Î Ï Ô Û Ü (upper or lowercase)
      • Special characters: space ( ), period (.), apostrophe ('), hyphen (-)
    • It must contain at least one letter.
Table
Edit logic (PVAL13)
Sub–edit  Conditions Outcome
PVAL13-1 P4 IN ['1', '2'] AND P13 IS NOT NULL AND NOT IS_COMPOSED_OF (UPPER (P13), 'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') Record rejected
PVAL13-2 P4 IN ['1', '2'] AND P13 IS NOT NULL AND IS_COMPOSED_OF (UPPER (P13), 'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') AND NOT CONTAINS_WORD (UPPER (P13), 'ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ', 1) Record rejected
Table
Feedback report messages (PVAL13)
Sub edit  Text Type
PVAL13-1 Birth surname is not exclusively composed of acceptable letters, accented characters or special characters. Core error
PVAL13-2 Birth surname does not contain at least one letter. Core error
Table
Revision Feedback report messages (PVAL13)
Year Description
2007 Business rules changed: Acceptable accented characters are specified.

PVAL14

Purpose

This edit validates date of death.

Table
Referenced fields (PVAL14)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P14 8 Date of death PDATDEA
P14.YEAR 4 First 4 digits of P14 (year of date of death) Not applicable
P14.MONTH 2 5th and 6th digits of P14 (month of date of death) Not applicable
P14.DAY 2 7th and 8th digits of P14 (day of date of death) Not applicable
P19.YEAR 4 First 4 digits of P19 (year of date of transmission) Not applicable
P19.MONTH 2 5th and 6th digits of P19 (Month of date of transmission) Not applicable
P19.DAY 2 7th and 8th digits of P19 (Day of date of transmission) Not applicable

Business rules

For Add and Update Patient records, Date of death
  • Must be 8 digits long.
  • Can be all zeros (when patient is not known to have died).
  • Must be between January 1st, 1992 and Date of transmission inclusively.
  • If Year is unknown then Month must be unknown.
  • If Month is unknown then Day must be unknown.
  • If Year, Month and Day are known then it must be a valid calendar date.
  • If Year and Month are known and Day is unknown then Month must be a valid month.
Table
Edit logic (PVAL14)
Sub–edit  Conditions Outcome
PVAL14-1 P4 IN ['1', '2'] AND (LENGTH (P14) <> 8 OR NOT IS_COMPOSED_OF (P14, '0123456789')) Record rejected
PVAL14-2 P4 IN ['1', '2'] AND (P14.YEAR = '0000' OR P14.MONTH = '00' OR P14.DAY = '00') AND NOT (P14.YEAR = '0000' AND P14.MONTH = '00' AND P14.DAY = '00') Record rejected
PVAL14-3 P4 IN ['1', '2'] AND LENGTH (P14) = 8 AND IS_COMPOSED_OF (P14, '0123456789') AND P14.YEAR NOT IN ['0000', '9999'] AND ((P14.MONTH = '99' AND P14.DAY = '99' AND (P14.YEAR < 1992 OR P14.YEAR > P19.YEAR)) OR (P14.MONTH IN ['01'-'12'] AND P14.DAY = '99' AND (P14.YEAR < 1992 OR P14.YEAR||P14.MONTH > P19.YEAR||P19.MONTH)) OR (P14.MONTH IN ['01'-'12'] AND P14.DAY IN ['01', '31'] AND IS_VALID_DATE (P14) AND (P14.YEAR < 1992 OR P14 > P19)) Record rejected
PVAL14-4 P4 IN ['1', '2'] AND LENGTH (P14) = 8 AND IS_COMPOSED_OF (P14, '0123456789') AND ((P14.YEAR = '9999' AND P14.MONTH <> '99') or (P14.MONTH = '99' AND P14.DAY <> '99')) Record rejected
PVAL14-5 P4 IN ['1', '2'] AND LENGTH (P14) = 8 AND IS_COMPOSED_OF (P14, '0123456789') AND P14.YEAR NOT IN ['0000', '9999'] AND P14.MONTH NOT IN ['00', '99'] AND P14.DAY NOT IN ['00', '99'] AND NOT IS_VALID_DATE (P14) Record rejected
PVAL14-6 P4 IN ['1', '2'] AND LENGTH (P14) = 8 AND IS_COMPOSED_OF (P14, '0123456789') AND P14.YEAR NOT IN ['0000', '9999'] AND P14.MONTH NOT IN ['00', '01'-'12', '99'] AND P14.DAY = '99' Record rejected
Table
Feedback report messages (PVAL14)
Sub–edit  Text Type
PVAL14-1 Date of death is not 8 digits long. Core error
PVAL14-2 Date of death: Improper use of 'Patient is not known to have died' code. Core error
PVAL14-3 Date of death must be between January 1st, 1992 and the Date of Transmission inclusively. Core error
PVAL14-4 Date of death: Improper use of 'Unknown' code. Core error
PVAL14-5 Date of death is not a valid calendar date. Core error
PVAL14-6 Date of death is not a valid partial date: month is invalid. Core error
Table
Revision (PVAL14)
Year Description
2004 Business rules changed: Date of death cannot be beyond Date of transmission.

PVAL15

Purpose

This edit validates the province/territory or country of death code.

Table
Referenced fields (PVAL15)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P14.YEAR 4 First 4 characters of P14 (year of date of death) Not applicable
P15 3 Province/territory or country of death PPROVDEA

Business rules

For Add and Update Patient records
  • If Date of death is before 1996 then Province/territory or country of death must be one of the Eligible province/territory and country codes prior to 199612.
  • If Date of death is on or after 1996 then Province/territory or country of death must be one of the Eligible province/territory and country codes in and after 199612.
  • If Date of death is unknown then Province/territory or country of death must be either one of the Eligible province/territory and country codes prior to 199612 or Eligible province/territory and country codes in and after 199612.
Table
Edit Logic (PVAL15)
Sub–edit  Conditions Outcome
PVAL15-1 P4 IN ['1', '2'] AND P14.YEAR NOT IN ['0000', '9999'] AND P14.YEAR < 1996 AND P15 NOT IN [Eligible province/territory or country codes prior to 1996] Record rejected
PVAL15-2 P4 IN ['1', '2'] AND P14.YEAR NOT IN ['0000', '9999'] AND P14.YEAR >= 1996 AND P15 NOT IN [Eligible province/territory or country codes in and after 1996] Record rejected
PVAL15-3 P4 IN ['1', '2'] AND P14.YEAR = '9999' AND P15 NOT IN [Eligible Province/Territory or Country of Death codes in and after 1996] AND P15 NOT IN [Eligible province/territory or country codes prior to 1996] Record rejected
Table
Feedback report messages (PVAL15)
Sub–edit  Text Type
PVAL15-1 Province/territory or country of death code is invalid for Date of death prior to 1996. Core error
PVAL15-2 Province/territory or country of death code is invalid for Date of death in and after 1996. Core error
PVAL15-3 Province/territory or country of death code is invalid. Core error
Table
Revision (PVAL15)
Year Description
2004 Business rules changed: Province/territory or country of death code is now validated against Province/territory or country codes valid at time of death.

PVAL16

Purpose

This edit validates the death registration number.

Table
Referenced fields (PVAL16)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P16 6 Death registration number PDEAREG

Business rules

For Add and Update Patient records, Death registration number
  • Must be exclusively composed of numbers: 0 to 9
  • Must be 6 digits long
Table
Edit logic (PVAL16)
Sub–edit  Conditions Outcome
PVAL16-1 P4 IN ['1', '2'] AND (LENGTH (P16) <> 6 OR NOT IS_COMPOSED_OF (P16, '0123456789')) Record rejected
Table
Feedback report messages (PVAL16
Sub–edit  Text Type
PVAL16-1 Death registration number is not 6 digits long. Core error
Table
Revision (PVAL16)
Year Description
Not applicable Not applicable

PVAL17

Purpose

This edit validates the underlying cause of death code.

Table
Referenced fields (PVAL17)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P14.YEAR 4 First 4 characters of P14 (year of date of death) Not applicable
P17 3 Underlying cause of death PCAUSDEA

Business rules

For Add and Update Patient records
  • IF Date of death is unknown then Underlying cause of death must be coded as 'Unknown/unavailable Underlying cause of death'.
  • IF Date of death is before 2000 then Underlying cause of death must be one of the Eligible ICD-9 underlying cause of death codes12.
  • IF Date of death is between 2000 and 2002 inclusively then Underlying cause of death must be one of the Eligible ICD-10 underlying cause of death codes in 2000-200212
  • IF Date of death is in or after 2003 then Underlying cause of death must be one of the Eligible ICD-10 underlying cause of death codes in 2003 and after13.
Table
Edit logic (PVAL17)
Sub–edit  Conditions Outcome
PVAL17-1 P4 IN ['1', '2'] AND P14.YEAR = '9999' AND P17 <> '0009' Record rejected
PVAL17-2 P4 IN ['1', '2'] AND P14.YEAR NOT IN ['0000', '9999'] AND P14.YEAR < 2000 AND P17 NOT IN [ICD-9 – Cause of death] Record rejected
PVAL17-3 P4 IN ['1', '2'] AND P14.YEAR NOT IN ['0000', '9999'] AND P14.YEAR >= 2000 AND P14.YEAR <= 2002 AND P17 NOT IN [ICD-10 – Cause of death in 2000-2002] Record rejected
PVAL17-4 P4 IN ['1', '2'] AND P14.YEAR NOT IN ['0000', '9999'] AND P14.YEAR >= 2003 AND P17 NOT IN [ICD-10 – Cause of death in 2003 and after] Record rejected
Table
Feedback report messages (PVAL17)
Sub–edit  Text Type
PVAL17-1 Underlying cause of death must be set to unknown when the Date of death is unknown. Core error
PVAL17-2 Underlying cause of death code is either invalid or not eligible for Date of death prior to 2000. Core error
PVAL17-3 Underlying cause of death code is either invalid or not eligible for Date of death between 2000 and 2002 inclusively. Core error
PVAL17-4 Underlying cause of death code is either invalid or not eligible for Date of death in or after 2003. Core error
Table
Revision (PVAL17)
Year Description
2004 Business rules added:
If Date of death is unknown then Underlying cause of death must be coded as 'Unknown/unavailable Underlying cause of death'.
If Date of death is in 2003 or after then Underlying cause of death must be coded using the latest revision of ICD-10 Underlying cause of death (2003 and after).

PVAL18

Purpose

This edit validates autopsy confirming cause of death code.

Table
Referenced fields (PVAL18)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P18 1 Autopsy confirming cause of death PAUTOPSY

Business rules

For Add and Update Patient records
  • Autopsy confirming cause of death must be one of the eligible autopsy confirming cause of death codes14.
Table
Edit logic (PVAL18)
Sub–edit  Conditions Outcome
PVAL18-1 P4 IN ['1', '2'] AND P18 NOT IN [Eligible Autopsy confirming cause of death codes] Record rejected
Table
Feedback report messages (PVAL18)
Sub–edit  Text Type
PVAL18-1 Autopsy confirming cause of death code is invalid. Core error
Table
Revision (PVAL18)
Year Description
Not applicable Not applicable

PVAL19

Purpose

This edit validates the patient record date of transmission.

Table
Referenced fields (PVAL19)
Field Length Description Acronym
P19 8 Patient Date of transmission PDATTRAN
P19.YEAR 4 First 4 digits of P19 (year of date of transmission) Not applicable
P19.MONTH 2 5th and 6th digits of P19 (month of date of transmission) Not applicable
P19.DAY 2 7th and 8th digits of P19 (day of date of transmission) Not applicable
Table
Other parameters (PVAL19)
Parameters Length Description
LOAD_DATE 8 Statistics Canada loading date: date on the Statistics Canada computer clock when the data are loaded on the CCR database.

Business rules

For Input Patient records, Patient Date of transmission
  • Cannot be blank
  • Must be exclusively composed of numbers: 0 to 9
  • Must be 8 digits long
  • Must be a valid calendar date
  • Must be within the previous 10 months from Statistics Canada loading date
Table
Edit logic (PVAL19)
Sub–edit  Conditions Outcome
PVAL19-1 P19 IS NULL Record rejected
PVAL19-2 P19 IS NOT NULL AND (LENGTH (P19) <> 8 OR NOT IS_COMPOSED_OF (P19, '0123456789')) Record rejected
PVAL19-3 P19 IS NOT NULL AND LENGTH (P19) = 8 AND IS_COMPOSED_OF (P19, '0123456789') AND NOT IS_VALID_DATE (P19) Record rejected
PVAL19-4 P19 IS NOT NULL AND LENGTH (P19) = 8 AND IS_COMPOSED_OF (P19, '0123456789') AND IS_VALID_DATE (P19) AND P19 > LOAD_DATE () Record rejected
PVAL19-5 P19 IS NOT NULL AND LENGTH (P19) = 8 AND IS_COMPOSED_OF (P19, '0123456789') AND IS_VALID_DATE (P19) AND P19 < (LOAD_DATE – 10 months) Record rejected
Table
Feedback report messages (PVAL19)
Sub–edit  Text Type
PVAL19-1 Patient Date of transmission is missing. Core fatal error
PVAL19-2 Patient Date of transmission is not 8 digits long. Core fatal error
PVAL19-3 Patient Date of transmission is not a valid calendar date. Core fatal error
PVAL19-4 Patient Date of transmission is after Statistics Canada loading date. Core fatal error
PVAL19-5 Patient Date of transmission is more than 10 months before Statistics Canada loading date. Core fatal error
Table
Revision (PVAL19)
Year Description
Not applicable Not applicable

PVAL20

Purpose

This edit validates the date of birth flag.

Table
Referenced fields (PVAL20)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P20 1 Date of birth flag PDATBIRFLAG

Business rules

For Add and Update Patient records
  • Date of death flag must be one of the Eligible date of death flag codes.
Table
Edit logic (PVAL20)
Sub–edit  Conditions Outcome
PVAL20-1 P4 IN ['1', '2'] AND P12 NOT IN [Eligible date of death flag codes] Record rejected
Table
Feedback report messages (PVAL20)
Sub–edit  Text Type
PVAL20-1 Date of death flag code is invalid. Core fatal error
Table
Revision (PVAL20)
Year Description
2010 New edit added.

PVAL21

Purpose

This edit validates the date of death flag.

Table
Referenced fields (PVAL21)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P21 1 Date of death flag PDATDEAFLAG

Business rules

For Add and Update Patient records
  • Date of death flag must be one of the Eligible date of death flag codes.
Table
Edit logic (PVAL21)
Sub–edit  Conditions Outcome
PVAL21-1 P4 IN ['1', '2'] AND P12 NOT IN [Eligible date of death flag codes] Record rejected
Table
Feedback report messages (PVAL21)
Sub–edit  Text Type
PVAL21-1 Date of death flag code is invalid. Core fatal error
Table
Table
Revision (PVAL21)
Year Description
2010 New edit added

3.4.2 Tumour validation edits

The following table summarizes the purpose of each individual edit of this category.

Table 25 Tumour validation edits summary

Table
Table 25 Tumour validation edits summary
Edit name Purpose
TVAL1 Validates the Tumour reporting province/territory code.
TVAL2 Validates the Tumour patient identification number.
TVAL3 Validates the Tumour reference number.
TVAL4 Validates the CCR identification number.
TVAL5 Validates the Tumour record type code.
TVAL6 Validates the Name of place of residence.
TVAL7 Validates the Postal code.
TVAL8 Validates the Standard geographic code.
TVAL9 Validates the Census tract.
TVAL10 Validates the Health insurance number (HIN).
TVAL11 Validates the Method of diagnosis code.
TVAL12 Validates the Date of diagnosis.
TVAL13 Validates the ICD-9 cancer code.
TVAL14 Validates the Source classification flag.
TVAL15 Validates the ICD-O-2/3 Topography code.
TVAL16 Validates the ICD-O-2 Histology code.
TVAL17 Validates the ICD-O-2 Behaviour code.
TVAL18 Not applicable
TVAL19 Validates the Laterality code.
TVAL20 Not applicable
TVAL21 Validates the ICD-O-3 Histology code.
TVAL22 Validates the ICD-O-3 Behaviour code.
TVAL23 Validates the grade, differentiation or cell indicator code.
TVAL24 Validates the Method used to establish the date of diagnosis code.
TVAL25 Validates the Diagnostic confirmation code.
TVAL26 Validates the Date of transmission.
TVAL27 Validates CS tumour size.
TVAL28 Validates CS extension.
TVAL29 Validates CS tumour size/ext eval.
TVAL30 Validates CS lymph nodes.
TVAL31 Validates CS lymph nodes eval.
TVAL32 Validates Regional nodes examined.
TVAL33 Validates Regional nodes positive.
TVAL34 Validates CS mets at dx.
TVAL35 Validates CS mets eval.
TVAL36 Validates CS site-specific factor 1.
TVAL37 Validates CS site-specific factor 2.
TVAL38 Validates CS site-specific factor 3.
TVAL39 Validates CS site-specific factor 4.
TVAL40 Validates CS site-specific factor 5.
TVAL41 Validates CS site-specific factor 6.
TVAL42 Validates AJCC clinical T.
TVAL43 Validates AJCC clinical N.
TVAL44 Validates AJCC clinical M.
TVAL45 Validates AJCC pathologic T.
TVAL46 Validates AJCC pathologic N.
TVAL47 Validates AJCC pathologic M.
TVAL48 Validates AJCC clinical TNM stage group.
TVAL49 Validates AJCC pathologic TNM stage group.
TVAL50 Validates AJCC TNM stage group.
TVAL51 Validates AJCC edition number code.
TVAL52 Validates CS version input original.
TVAL53 Validates Ambiguous terminology diagnosis.
TVAL54 Validates Date of conclusive diagnosis.
TVAL55 Validates Type of multiple tumours reported as one primary.
TVAL56 Validates Date of multiple tumours.
TVAL57 Validates multiplicity counter.
TVAL58 Validates Date of diagnosis flag.
TVAL59 Validates Date of conclusive diagnosis flag.
TVAL60 Validates Date of multiple tumours flag.
TVAL61 Validates Grade path value.
TVAL62 Validates Grade path system.
TVAL63 Validates Lymph-vascular invasion.
TVAL64 Validates CS Version input current.
TVAL65 to TVAL83 Validates site-specific factors 7 - 25
TVAL84 Validates CS Mets at Dx - Bone
TVAL85 Validates CS Mets at Dx - Brain
TVAL86 Validates CS Mets at Dx - Liver
TVAL87 Validates CS Mets at Dx - Lung

TVAL1

Purpose

This edit validates the Tumour reporting province/territory code.

Table
Referenced Fields (TVAL1)
Field Length Description Acronym
T1 2 Tumour reporting province/territory TREPPROV
Table
Other parameters (TVAL1)
Parameters Length Description
PTCR_CODE 2 Province/territory code of the PTCR that is submitting the data.

Business rules

For Input Tumour records
  • Tumour reporting province/territory must be equal to province/territory code of the PTCR that is submitting the data15.
Table
Edit logic (TVAL1)
Sub–edit  Conditions Outcome
TVAL1-1 T1 <> PTCR_CODE Record rejected
Table
Feedback report messages (TVAL1)
Sub–edit  Text Type
TVAL1-1 Tumour reporting province/territory code does not match PTCR province/territory code. Core error
Table
Revision (TVAL1)
Year Description
Not applicable Not applicable

TVAL2

Purpose

This edit validates the tumour patient identification number.

Table
Referenced fields (TVAL2)
Field Length Description Acronym
T2 12 Tumour patient identification number TPIN

Business rules

For Input Tumour records, Patient identification number
  • Must be exclusively composed of any of the following:
    • Uppercase letters: A to Z
    • Numbers: 0 to 9
  • Cannot be exclusively composed of zeros.
Table
Edit logic (TVAL2)
Sub–edit  Conditions Outcome
TVAL2-1 IS_COMPOSED_OF (T2, '0') Record rejected
TVAL2-2 NOT IS_COMPOSED_OF (T2, 'ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789') Record rejected
Table
Feedback report messages (TVAL2)
Sub–edit  Text Type
TVAL2-1 Patient identification number cannot be exclusively composed of zeros. Core error
TVAL2-2 Patient identification number is not exclusively composed of uppercase letters and/or numbers. Core error
Table
Revision (TVAL2)
Year Description
2004 Business rule changed: Apostrophes, hyphens, periods and inner spaces are not accepted anymore.

TVAL3

Purpose

This edit validates the tumour reference number.

Table
Referenced fields (TVAL3)
Field Length Description Acronym
T3 9 Tumour reference number TTRN

Business rules

For Input Tumour records, Tumour reference number
  • Must be exclusively composed of any of the following:
    • Numbers: 0 to 9
    • Uppercase letters: A to Z
    • Special characters: space ( ), period (.), apostrophe ('), hyphens (-)
  • Cannot be exclusively composed of zeros.
Table
Edit logic (TVAL3)
Sub–edit  Conditions Outcome
TVAL3-1 IS_COMPOSED_OF (T3, '0') Record rejected
TVAL3-2 NOT IS_COMPOSED_OF (T3, 'ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789 -'.') Record rejected
Table
Feedback report messages (TVAL3)
Sub–edit  Text Type
TVAL3-1 Tumour reference number cannot be exclusively composed of zeros. Core error
TVAL3-2 Tumour reference number is not exclusively composed of acceptable letters, numbers or special characters. Core error
Table
Revision (TVAL3)
Year Description
2004 Business rule added: Tumour reference number cannot be exclusively composed of zeros.

TVAL4

Purpose

This edit validates the CCR identification number.

Table
Referenced fields (TVAL4)
Field Length Description Acronym
T4 9 CCR identification number CCR_ID
T4.ID 8 First 8 digits of T4 (CCR ID sequence number) Not applicable
T4.CHECK_DIGIT 1 9th digit of T4 (CCR ID check digit) Not applicable

Business rules

For Input Tumour records
  • If CCR identification number is reported then
    • Must be exclusively composed of numbers: 0 to 9
    • Must be 9 digits long;
    • Cannot be all zeros;
    • Must have a valid check digit16.
Table
Edit logic (TVAL4)
Sub–edit  Conditions Outcome
TVAL4-1 T4 IS NOT NULL AND (LENGTH (T4) <> 9 OR NOT IS_COMPOSED_OF (T4, '0123456789')) Record rejected
TVAL4-2 T4 = '000000000' Record rejected
TVAL4-3 T4 IS NOT NULL AND T4 <> '000000000' AND LENGTH (T4) = 9 AND IS_COMPOSED_OF (T4, '0123456789') AND T4.CHECK_DIGIT <> CALCULATE_CCR_CHECK_DIGIT (T4.ID) Record rejected
Table
Feedback report messages (TVAL4)
Sub–edit  Text Type
TVAL4-1 CCR identification number is not 9 digits long. Core error
TVAL4-2 CCR identification number cannot be all zeros. Core error
TVAL4-3 CCR identification number is invalid. Core error
Table
Revision (TVAL4)
Year Description
Not applicable Not applicable

TVAL5

Purpose

This edit validates the tumour record type code.

Table
Referenced fields (TVAL5)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE

Business rules

For Input Tumour records, Tumour record type
  • Cannot be blank.
  • Must be one of the Eligible tumour record type codes17 .
Table
Edit logic (TVAL5)
Sub–edit  Conditions Outcome
TVAL5-1 T5 IS NULL OR T5 NOT IN [Eligible tumour record type codes] Record rejected
Table
Feedback report messages (TVAL5)
Sub–edit  Text Type
TVAL5-1 Tumour record type code is missing or invalid. Core fatal error
Table
Revision (TVAL5)
Year Description
Not applicable Not applicable

TVAL6

Purpose

This edit validates the name of place of residence.

Table
Referenced fileds (TVAL6)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T6 25 Name of place of residence TPLACRES

Business rules

For Add and Update Tumour records
  • Name of place of residence can be blank.
  • If Name of place of residence is not blank then it can be any combination of the following:
    • Letters: A to Z (upper or lowercase)
      • Accented characters: Â À Ç É Ê Ë È Î Ï Ô Û Ü (upper or lowercase)
      • Special characters: space ( ), period (.), apostrophe ('), hyphen (-), exclamation mark (!), ampersand (&), forward slash (/), parentheses ["("and")"], number sign (#), comma (,)
  • It must contain a word of at least 2 letters.
Table
Edit logic TVAL6)
Sub–edit  Conditions Outcome
TVAL6-1 T5 IN ['1', '2'] AND T6 IS NOT NULL AND IS NOT COMPOSED OF (UPPER (T6), 'ABCDEFGHILKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ.'-!&/()#,') Record rejected
TVAL6-2 T5 IN ['1', '2'] AND T6 IS NOT NULL AND IS_COMPOSED_OF (UPPER (T6), 'ABCDEFGHILKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-!&/()#,') AND NOT CONTAINS_WORD (UPPER (T6), 'ABCDEFGHILKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ', 2) Record rejected
Table
Feedback report messages (TVAL6)
Sub–edit  Text Type
TVAL6-1 Name of place of residence is not exclusively composed of acceptable letters, accented characters or special characters. Core error
TVAL6-2 Name of place of residence does not contain a word of at least 2 letters. Core error
Table
Revision (TVAL6)
Year Description
2007 Business rules changed: Acceptable accented characters and special characters are specified.
Edit logic: New edit logic added.
Feedback report messages: New message added.

TVAL7

Purpose

This edit validates the postal code.

Table
Referenced fields (TVAL7)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T7 6 Postal code TPOSTCOD
T7.FIRST 1 1st character of T7 Not applicable
T7.SECOND 1 2nd character of T7 Not applicable
T7.THIRD 1 3rd character of T7 Not applicable
T7.FOURTH 1 4th character of T7 Not applicable
T7.FIFTH 1 5th character of T7 Not applicable
T7.SIXTH 1 6th character of T7 Not applicable

Business rules

For Add and Update Tumour records, Postal code
  • Must be 6 characters long.
  • Can be unknown.
  • If not unknown then
    • 1st, 3rd and 5th characters must be uppercase letters: A-Z
    • 2nd, 4th and 6th characters must be numbers: 0-9
Table
Edit logic (TVAL7)
Sub–edit  Conditions Outcome
TVAL7-1 T5 IN ['1', '2'] AND (LENGTH(T7) <> 6 OR (T7 <> '999999' AND (T7.FIRST NOT IN [A-Z] OR T7.SECOND NOT IN [0-9] OR T7.THIRD NOT IN [A-Z] OR T7.FOURTH NOT IN [0-9] OR T7.FIFTH NOT IN [A-Z] OR T7.SIXTH NOT IN [0-9]))) Record rejected
Table
Feedback report messages (TVAL7)
Sub–edit  Text Type
TVAL7-1 Postal code has an invalid format. Core error
Table
Revision (TVAL7)
Year Description
Not applicable Not applicable

TVAL8

Purpose

This edit validates the Standard geographic code.

Table
Referenced fields (TVAL8)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T8 7 Standard geographic code TCODPLAC
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable

Business rules

For Add and Update Tumour records
  • If Date of diagnosis is between 1992 and 1995 then Standard geographic code must be one of the Eligible Standard geographic classification codes from 1992 to 199512.
  • If Date of diagnosis is between 1996 and 2000 then Standard geographic code must be one of the Eligible Standard geographic classification codes from 1996 to 200012.
  • If Date of diagnosis is between 2001 and 2005 then Standard geographic code must be one of the Eligible Standard geographic classification codes from 2001 to 200512.
  • If Date of Diagnosis is between 2006 and 2010 then Standard geographic code must be one of the Eligible Standard geographic classification codes from 2006 and 2010.
Table
Edit logic (TVAL8)
Sub–edit  Conditions Outcome
TVAL8-1 T5 IN ['1', '2'] AND T12.YEAR BETWEEN ('1992', '1995') AND T8 NOT IN [Eligible Standard geographic classification codes from 1992 to 1995] Record rejected
TVAL8-2 T5 IN ['1', '2'] AND T12.YEAR BETWEEN ('1996', '2000') AND T8 NOT IN [Eligible Standard geographic classification codes from 1996 to 2000] Record rejected
TVAL8-3 T5 IN ['1', '2'] AND T12.YEAR BETWEEN ('2001', '2005') AND T8 NOT IN [Eligible Standard geographic classification codes from 2001 to 2005] Record rejected
TVAL8-4 T5 IN ['1', '2'] AND T12.YEAR BETWEEN ('2006', '2010') AND T8 NOT IN [Eligible Standard Geographic Classification codes from 2006 to 2010] Record rejected
Table
Feedback report messages (TVAL8)
Sub–edit  Text Type
TVAL8-1 Standard geographic code is invalid according to the Standard geographic classification – 1991. Core error
TVAL8-2 Standard geographic code is invalid according to the Standard geographic classification – 1996. Core error
TVAL8-3 Standard geographic code is invalid according to the Standard geographic classification – 2001. Core error
TVAL8-4 Standard geographic code is invalid according to the Standard geographic classification – 2006. Core error
Table
Revision (TVAL8)
Year Description
2006 Business rules, Edit logic and Feedback report messages added: SGC – 2006 added
2001 Business rules, Edit logic and Feedback report messages added: SGC – 2001 added
1996 Business rules, Edit logic and Feedback report messages added: SGC – 1996 added

TVAL9

Purpose

This edit validates the census tract.

Table
Referenced fields (TVAL9)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T9 9 Census tract TCENTRAC
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable

Business rules

For Add and Update Tumour records
  • If Date of diagnosis is between 1992 and 1995 then Census tract must be reported and must be one of the Eligible Census tracts from 1992 to 199512.
  • If Date of diagnosis is between 1996 and 2000 then Census tract must be reported and must be one of the Eligible Census tracts from 1996 to 200012.
  • If Date of diagnosis is between 2001 and 2005 then Census tract must be reported and must be one of the Eligible Census tracts from 2001 to 200512
  • If Date of Diagnosis is 2006 and onwards then Census Tract must not be reported (field should be left blank).
Table
Edit logic (TVAL9)
Sub–edit  Conditions Outcome
TVAL9-1 T5 IN ['1', '2'] AND T12.YEAR BETWEEN ('1992', '1995') AND (T9 IS NULL OR T9 NOT IN [Eligible Census tracts from 1992 to 1995]) Record rejected
TVAL9-2 T5 IN ['1', '2'] AND T12.YEAR BETWEEN ('1996', '2000') AND (T9 IS NULL OR T9 NOT IN [Eligible Census tracts from 1996 to 2000]) Record rejected
TVAL9-3 T5 IN ['1', '2'] AND T12.YEAR BETWEEN ('2001', '2005') AND (T9 IS NULL OR T9 NOT IN [Eligible Census tracts from 2001 to 2005]) Record rejected
TVAL9-4 T5 IN ['1', '2'] AND T12.YEAR >= ('2006') AND T9 <> NULL Record rejected
Table
Feedback report messages (TVAL9)
Sub–edit  Text Type
TVAL9-1 Census tract is invalid according to the Census tract Data Dictionary – 1991. Core error
TVAL9-2 Census tract is invalid according to the Census tract Data Dictionary – 1996. Core error
TVAL9-3 Census tract is invalid according to the Census tract Data Dictionary – 2001. Core error
TVAL9-4 Census tract must not be reported for cases diagnosed in 2006 and onwards. Core error
Table
Revision (TVAL9)
Year Description
2006 Business rules, Edit logic and Feedback report messages added: Census tract effective date range ended in 2005. For cases diagnosed in 2006 and onwards, T9 (Census Tract) must be reported as blank (null)
2001 Business rules, Edit logic and Feedback report messages added: Eligible Census tracts – 2001 added
1996 Business rules, Edit logic and Feedback report messages added: Eligible Census tracts – 1996 added

TVAL10

Purpose

This edit validates the health insurance number (HIN).

Table
Referenced fields (TVAL10)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T10 15 Health insurance number THIN

Business rules

For Add and Update Tumour records,
  • If Health insurance number is reported then
  • It must be at least 6 characters long.
  • It must be exclusively composed of any of the following:
    • Uppercase letters: A to Z
    • Numbers: 0 to 9
Table
Edit logic (TVAL10)
Sub–edit  Conditions Outcome
TVAL10-1 T5 IN ['1', '2'] AND T10 IS NOT NULL AND LENGTH (T10) < 6 Record rejected
TVAL10-2 T5 IN ['1', '2'] AND T10 IS NOT NULL AND NOT IS_COMPOSED_OF (T10, 'ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789') Record rejected
Table
Feddback report messages (TVAL10)
Sub–edit  Text Type
TVAL10-1 Health insurance number is less than 6 characters long. Core error
TVAL10-2 Health insurance number is not exclusively composed of uppercase letters and/or numbers. Core error
Table
Revision (TVAL10)
Year Description
Not applicable Not applicable

TVAL11

Purpose

This edit validates the method of diagnosis code.

Table
Referenced fields (TVAL11)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T11 1 Method of diagnosis TMETHDIAG

Business rules

For Add and Update Tumour records
  • Method of diagnosis must be one of the Eligible method of diagnosis codes18.
Table
Edit logic (TVAL11)
Sub–edit  Conditions Outcome
TVAL11-1 T5 IN ['1', '2'] AND T11 NOT IN [Eligible method of diagnosis codes] Record rejected
Table
Feedback report messages (TVAL11)
Sub–edit  Text Type
TVAL11-1 Method of diagnosis code is invalid. Core error
Table
Revision (TVAL11)
Year Description
Not applicable Not applicable

TVAL12

Purpose

This edit validates the date of diagnosis.

Table
Referenced fields (TVAL12)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12 8 Date of diagnosis TDATDIAG
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T12.MONTH 2 5th and 6th digits of T12 (month of date of diagnosis) Not applicable
T12.DAY 2 Last 2 digits of T12 (day of date of diagnosis) Not applicable
Table
Other parameters (TVAL12)
Parameters Length Description
CYCLE_YEAR 4 Reference year

Business rules

For Add and Update Tumour records, Date of Diagnosis
  • Must be exclusively composed of numbers: 0 to 9.
  • Must be 8 digits long.
  • Must be between January 1st, 1992 and December 31st of Reference year inclusively.
  • Year cannot be unknown.
  • If Month is unknown then Day must be unknown.
  • If Year, Month and Day are known then it must be a valid calendar date.
  • If Year and Month are known and Day is unknown then Month must be a valid month.

Table
Edit logic (TVAL12)
Sub–edit  Conditions Outcome
TVAL12-1 T5 IN ['1', '2'] AND (LENGTH (T12) <> 8 OR NOT IS_COMPOSED_OF (T12, '0123456789')) Record rejected
TVAL12-2 T5 IN ['1', '2'] AND LENGTH (T12) = 8 AND IS_COMPOSED_OF (T12, '0123456789') AND T12.MONTH = '99' AND T12.DAY <> '99' Record rejected
TVAL12-3 T5 IN ['1', '2'] AND LENGTH (T12) = 8 AND IS_COMPOSED_OF (T12, '0123456789'' AND (T12.YEAR < 1992 OR T12.YEAR > CYCLE_YEAR) Record rejected
TVAL12-4 T5 IN ['1', '2'] AND LENGTH (T12) = 8 AND IS_COMPOSED_OF (T12, '0123456789') AND T12.MONTH <> '99' AND T12.DAY <> '99' AND NOT IS_VALID_DATE (T12) Record rejected
TVAL12-5 T5 IN ['1', '2'] AND LENGTH (T12) = 8 AND IS_COMPOSED_OF (T12, '0123456789') AND T12.MONTH NOT IN ['01'-'12', '99'] AND T12.DAY = '99' Record rejected

Table
Feedback report messages (TVAL12)
Sub–edit  Text Type
TVAL12-1 Date of diagnosis is not composed of 8 numbers. Core error
TVAL12-2 Date of diagnosis: Improper use of 'Unknown' code. Core error
TVAL12-3 Date of diagnosis must be between January 1st, 1992 and December 31st of Reference year inclusively. Core error
TVAL12-4 Date of diagnosis is not a valid calendar date. Core error
TVAL12-5 Date of diagnosis is not a valid partial date: month is invalid. Core error

Table
Revision (TVAL12)
Year Description
Not applicable Not applicable

TVAL13

Purpose

This edit validates the ICD-9 cancer code.


Table
Referenced fields (TVAL13)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T13 4 ICD-9 cancer code TICD_9

Business rules

For Add and Update Tumour records
  • If ICD-9 Cancer code is reported then it must be one of the Eligible ICD-9 Cancer codes19.

Table
Edit logic (TVAL13)
Sub–edit  Conditions Outcome
TVAL13-1 T5 IN ['1', '2'] AND T13 <> '0000' AND T13 NOT IN [Eligible ICD-9 Cancer codes] Record rejected

Table
Feedback report messages (TVAL13)
Sub–edit  Text Type
TVAL13-1 ICD-9 Cancer code is either invalid or not eligible for the CCR system. Core error

Table
Revision (TVAL13)
Year Description
Not applicable Not applicable

TVAL14

Purpose

This edit validates the source classification flag.


Table
Referenced fields (TVAL14)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T14 1 Source classification flag TSCF

Business rules

For Add and Update Tumour records
  • Source classification flag must be one of the Eligible source classification flags20.

Table
Edit logic (TVAL14)
Sub–edit  Conditions Outcome
TVAL14-1 T5 IN ['1', '2'] AND T14 NOT IN [Eligible source classification flags] Record rejected

Table
Feedback report messages (TVAL14)
Sub–edit  Text Type
TVAL14-1 Source classification flag is invalid. Core error

Table
Revision (TVAL14)
Year Description
Not applicable Not applicable

TVAL15

Purpose

This edit validates the ICD-O-2/3 topography code.


Table
Referenced fields (TVAL15)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T15 4 ICD-O-2/3 Topography TICD_O2T

Business rules

For Add and Update Tumour records
  • ICD-O-2/3 Topography must be one of the Eligible ICD-O-2/3 Topography codes12.
Table
Edit logic (TVAL15)
Sub–edit  Conditions Outcome
TVAL15-1 T5 IN ['1', '2'] AND T15 NOT IN [Eligible ICD-O-2/3 Topography codes] Record rejected
Table
Feedback report messages (TVAL15)
Sub–edit  Text Type
TVAL15-1 ICD-O-2/3 Topography code is either invalid or not eligible for the CCR System. Core error

Table
Revision (TVAL15)
Year Description
Not applicable Not applicable

TVAL16

Purpose

This edit validates the ICD-O-2 histology code.

Table
Referenced fields (TVAL16)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T15 4 ICD-O-2/3 Topography TICD_O2T
T16 4 ICD-O-2 Histology TICD_O2H

Business rules

For Add and Update Tumour records
  • If ICD-O-2 Histology is reported then it must be one of the Eligible ICD–O–2 Histology codes12.
Table
Edit logic (TVAL16)
Sub–edit  Conditions Outcome
TVAL16-1 T5 IN ['1', '2'] AND T15 <> '0000' AND T16 NOT IN [Eligible ICD-O-2 Histology codes] Record rejected
Table
Feedback report messages (TVAL16)
Sub–edit  Text Type
TVAL16-1 ICD-O-2 Histology code is either invalid or not eligible for the CCR System. Core error
Table
Revision (TVAL16)
Year Description
Not applicable Not applicable

TVAL17

Purpose

This edit validates the ICD-O-2 Behaviour code.

Table
Referenced fields (TVAL17)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T17 1 ICD-O-2 Behaviour TICD_O2B

Business rules

For Add and Update Tumour records
  • If ICD-O-2 Behaviour is reported then it must be one of the Eligible ICD–O–2 Behaviour codes21.
Table
Edit logic (TVAL17)
Sub–edit  Conditions Outcome
TVAL17-1 T5 IN ['1', '2'] AND T17 NOT IN [Eligible ICD–O–;2 Behaviour codes] Record rejected
Table
Feedback report messages (TVAL17)
Sub–edit  Text Type
TVAL17-1 ICD-O-2 Behaviour code is either invalid or not eligible for the CCR system. Core error
Table
Revision (TVAL17)
Year Description
Not applicable Not applicable

TVAL18

Purpose

Not applicable

Table
Referenced fields (TVAL18)
Field Length Description Acronym
T18 4 Filler Not applicable

Business rules

For Input Tumour records
  • Filler can be anything, including blank.
Table
Edit logic (TVAL18)
Sub–edit  Conditions Outcome
Not applicable Not applicable Not applicable
Table
Feedback report messages (TVAL18)
Sub–edit  Text Type
Not applicable Not applicable Not applicable
Table
Revision (TVAL18)
Year Description
2004 Edit removed: Filler can be anything, including blank.

Note
This empty validation is kept as a placeholder for future requirement implementation.

TVAL19

Purpose

This edit validates the laterality code.

Table
Referenced fields (TVAL19)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T19 1 Laterality TLATERAL

Business rules

For Add and Update Tumour records
  • Laterality must be one of the Eligible laterality codes22.
Table
Edit logic (TVAL19)
Sub–edit  Conditions Outcome
TVAL19-1 T5 IN ['1', '2'] AND T19 NOT IN [Eligible laterality codes] Record rejected
Table
Feedback report messages (TVAL19)
Sub–edit  Text Type
TVAL19-1 Laterality code is invalid. Core error
Table
Revision (TVAL19)
Year Description
Not applicable Not applicable

TVAL20

Purpose

Not applicable

Table
Referenced fields (TVAL20)
Field Length Description Acronym
T20 1 Filler Not applicable

Business rules

For Input Tumour records
  • Filler can be anything, including blank.
Table
Edit logic TVAL20)
Sub–edit  Conditions Outcome
Not applicable Not applicable Not applicable
Table
Feedback report messages (TVAL20)
Sub–edit  Text Type
Not applicable Not applicable Not applicable
Table
Revision (TVAL20)
Year Description
2004 Edit removed: Filler can be anything, including blank.

Note:
This empty validation is kept as a placeholder for future requirement implementation.

TVAL21

Purpose

This edit validates the ICD-O-3 Histology code.

Table
Referenced fields (TVAL21)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T21 4 ICD-O-3 Histology TICD_O3H

Business rules

For Add and Update Tumour records
  • ICD-O-3 Histology must be one of the Eligible ICD–O–3 Histology codes12,23.
Table
Edit logic (TVAL21)
Sub–edit  Conditions Outcome
TVAL21-1 T5 IN ['1', '2'] AND T21 NOT IN [Eligible ICD-O-3 Histology codes] Record rejected
Table
Feedback report messages (TVAL21)
Sub–edit  Text Type
TVAL21-1 ICD-O-3 Histology code is either invalid or not eligible for the CCR System. Core error
Table
Revision (TVAL21)
Year Description
2004 Edit renamed: Current edit was formerly known as Validation edit No.21M.

TVAL22

Purpose

This edit validates the ICD-O-3 Behaviour code.

Table
Referenced fields TVAL22)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T22 1 ICD-O-3 Behaviour TICD_O3B

Business rules

For Add and Update Tumour records
  • ICD-O-3 Behaviour must be one of the Eligible ICD–O–3 Behaviour codes24.
Table
Edit logic (TVAL22)
Sub–edit  Conditions Outcome
TVAL22-1 T5 IN ['1', '2'] AND T22 NOT IN [Eligible ICD–O–3 Behaviour codes] Record rejected
Table
Feedback report messages TVAL22)
Sub–edit  Text Type
TVAL22-1 ICD-O-3 Behaviour code is either invalid or not eligible for the CCR system. Core error
Table
Revision (TVAL22)
Year Description
2004 Edit reorganized: Edit formerly known as Validation edit No.22 moved to TVAL26.
Edit renamed: Current edit was formerly known as Validation edit No.21B.

TVAL23

Purpose

This edit validates the grade, differentiation or cell indicator code.

Table
Referenced fields (TVAL23)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T23 1 Grade, differentiation or cell indicator TGRADE

Business rules

For Add and Update Tumour records
  • Grade, differentiation or cell indicator must be one of the Eligible grade, differentiation or cell indicator codes25.
Table
Edit logic (TVAL23)
Sub–edit  Conditions Outcome
TVAL23-1 T5 IN ['1', '2'] AND T23 NOT IN [Eligible grade, differentiation or cell indicator codes] Record rejected
Table
Feedback report messages (TVAL23)
Sub–edit  Text Type
TVAL23-1 Grade, differentiation or cell indicator code is invalid. Core error
Table
Revision (TVAL23)
Year Description
2004 Edit reorganized: Edit formerly known as Validation edit No.23 moved to TVAL24.
Edit added: New edit.

TVAL24

Purpose

This edit validates the method used to establish the date of diagnosis code.

Table
Referenced fields (TVAL24)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T24 1 Method used to establish the date of diagnosis TMETHUSED

Business rules

For Add and Update Tumour records
  • Method used to establish the date of diagnosis must be one of the Eligible method used to establish the date of diagnosis codes26.
Table
Edit logic (TVAL24)
Sub–edit  Conditions Outcome
TVAL24-1 T5 IN ['1', '2'] AND (T12.YEAR >= '1992' and T12.YEAR <= '2009') AND T24 NOT IN [0,1,2,3,4,5,6,7,8,9] Record rejected
TVAL24-2 T5 IN ['1', '2'] AND (T12.YEAR >= '2010') AND T24 NOT IN [0,1,2,3,4,5,6,7,8,9,10] Record rejected
Table
Feedback report messages (TVAL24)
Sub–edit  Text Type
TVAL24-1 Method used to establish the date of diagnosis code is invalid (Date of diagnosis 1992 to 2009). Core error
TVAL24-2 Method used to establish the date of diagnosis code is invalid (Date of diagnosis 2010 and onwards). Core error
Table
Revision(TVAL24)
Year Description
2010 Referenced Fields: T12.YEAR added
Edit Logic: New sub-edit added, T12.YEAR added and new code added to eligible method used to establish the date of diagnosis codes.
Feedback report messages: New feedback report message added for new sub-edit.
2004 Edit reorganized: Edit formerly known as Validation edit No.24 moved to TVAL25.
Edit renamed: Current edit formerly known as Validation edit No.23.

TVAL25

Purpose

This edit validates the diagnostic confirmation code.

Table
Referenced fields (TVAL25)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T25 1 Diagnostic Confirmation TMETHCONF

Business rules

For Add and Update Tumour records
  • Diagnostic confirmation must be one of the Eligible diagnostic confirmation codes27.
Table
Edit logic (TVAL25)
Sub–edit  Conditions Outcome
TVAL25-1 T5 IN ['1', '2'] AND (T12.YEAR >= '1992' and T12.YEAR <= '2009') AND T25 NOT IN [0,1,2,3,4,5,6,7,8,9] Record rejected
TVAL25-2 T5 IN ['1', '2'] AND (T12.YEAR >= '2010') AND T25 NOT IN [0,1,2,3,4,5,6,7,8,9,10] Record rejected
Table
Feedback report messages (TVAL25)
Sub–edit  Text Type
TVAL25-1 Diagnostic confirmation code is invalid (Date of diagnosis 1992 to 2009) Core error
TVAL25-2 Diagnostic confirmation code is invalid (Date of diagnosis 2010 and onwards). Core error
Table
Revision (TVAL25)
Year Description
2010 Referenced Fields: T12.YEAR added
Edit Logic: New sub-edit added, T12.YEAR added and new code added to eligible diagnostic confirmation codes.
Feedback report messages: New feedback report message added for new sub-edit.
2004 Edit renamed: Current edit formerly known as Validation edit No.24.

TVAL26

Purpose

This edit validates the tumour date of transmission.

Table
Referenced fields (TVAL26)
Field Length Description Acronym
T26 8 Tumour date of transmission TDATTRAN
T26.YEAR 4 First 4 digits of T26 (year of date of transmission) Not applicable
T26.MONTH 2 5th and 6th digits of T26 (month of date of transmission) Not applicable
T26.DAY 2 7th and 8th digits of T26 (day of date of transmission) Not applicable
Table
Other parameters (TVAL26)
Parameters Length Description
LOAD_DATE 8 Statistics Canada loading date: Date on the Statistics Canada computer clock when the data are loaded on the CCR database.

Business rules

For Input Tumour records, Tumour date of transmission
  • Cannot be blank.
  • Must be exclusively composed of numbers: 0 to 9.
  • Must be 8 digits long.
  • Must be a valid calendar date.
  • Must be within the previous 10 months from Statistics Canada loading date.
Table
Edit logic (TVAL26)
Sub–edit  Conditions Outcome
TVAL26-1 T26 IS NULL Record rejected
TVAL26-2 T26 IS NOT NULL AND (LENGTH (T26) <> 8 OR NOT IS_COMPOSED_OF (T26, '0123456789')) Record rejected
TVAL26-3 T26 IS NOT NULL AND LENGTH (T26) = 8 AND IS_COMPOSED_OF (T26, '0123456789') AND NOT IS_VALID_DATE (T26) Record rejected
TVAL26-4 T26 IS NOT NULL AND LENGTH (T26) = 8 AND IS_COMPOSED_OF (P26, '0123456789') AND IS_VALID_DATE (T26) AND T26 > LOAD_DATE Record rejected
TVAL26-5 T26 IS NOT NULL AND LENGTH (T26) = 8 AND IS_COMPOSED_OF (T26, '0123456789') AND IS_VALID_DATE (T26) AND T26 < (LOAD_DATE – 10 months) Record rejected
Table
Feedback report messages (TVAL26)
Sub–edit  Text Type
TVAL26-1 Tumour date of transmission is missing. Core fatal error
TVAL26-2 Tumour date of transmission is not 8 digits long. Core fatal error
TVAL26-3 Tumour date of transmission is not a valid calendar date. Core fatal error
TVAL26-4 Tumour date of transmission is after Statistics Canada loading date. Core fatal error
TVAL26-5 Tumour date of transmission is more than 10 months before Statistics Canada loading date. Core fatal error
Table
Revision (TVAL26)
Year Description
2004 Edit renamed: Current edit formerly known as Validation edit No.22.

TVAL27

Purpose

This edit validates CS tumour size.

Table
Referenced fields (TVAL27)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 3 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 3 CS lymph nodes TCSLNODE
T31 1 CS lymph nodes eval TCSLNEVAL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS version input original TCSVERINORIG
T64 6 CS version input current TCSVERINCUR

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS tumour size must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL27)
Sub–edit  Conditions Outcome
TVAL27-1 T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <>'999999') AND NOT VALID_CS_TUMOUR_SIZE(T15, T21, T27) CS data items filled with 'R' at posting.
TVAL27-2 Edit for CSV2 to follow  
Table
Feedback report messages (TVAL27)
Sub–edit  Text Type
TVAL27-1 CS tumour size is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm (using CSV1). CS error
TVAL27-2 Edit for CSV2 to follow  
Table
Revision (TVAL27)
Year Description
2010 Referenced Fields: Name and acronym of CS version 1st(TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL).Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added.
Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2.
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL28

Purpose

This edit validates CS extension.

Table
Referenced fields (TVAL28)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 3 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 3 CS lymph nodes TCSLNODE
T31 1 CS lymph nodes eval TCSLNEVAL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS version input original TCSVERINORIG
T64 6 CS version input current TCSVERINCUR

Business rules

For Add and Update Tumour records within the CCR Collaborative staging scope28 and with at least one known CS variable,
  • CS extension must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL28)
Sub–edit  Conditions Outcome
TVAL28-1 T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> '999999') AND NOT VALID_CS_EXTENSION(T15, T21, T28) CS data items filled with 'R' at posting.
TVAL28-2 Edit for CSV2 to follow  
Table
Feedback report messages (TVAL28)
Sub–edit  Text Type
TVAL28-1 CS extension is invalid for the corresponding CS schema, based on the recommended version of the AJCC CS Algorithm (using CSV1). CS error
TVAL28-2 Edit for CSV2 to follow  
Table
Revision (TVAL28)
Year Description
2010 Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added.
Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2.
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL29

Purpose

This edit validates CS tumour size/ext eval.

Table
Referenced fields (TVAL29)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 3 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 3 CS lymph nodes TCSLNODE
T31 1 CS lymph nodes eval TCSLNEVAL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS version input original TCSVERINORIG
T64 6 CS version input current TCSVERINCUR

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS tumour size/ext eval must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL29)
Sub–edit  Conditions Outcome
TVAL29-1 T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> '999999') AND NOT VALID _CS_TUMOUR_SIZE/EXT_EVAL(T15, T21, T29) CS data items filled with 'R' at posting.
TVAL29-2 Edit for CSV2 to follow  
Table
Feedback report messages (TVAL29)
Sub–edit  Text Type
TVAL29-1 CS tumour size/ext eval is invalid for the corresponding CS schema, based on the recommended version of the AJCC CS Algorithm (using CSV1). CS error
TVAL29-2 Edit for CSV2 to follow  
Table
Revision (TVAL29)
Year Description
2010 Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added.
Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2.
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm.
2004 Edit added: New edit.

TVAL30

Purpose

This edit validates CS lymph nodes.

Table
Referenced fields (TVAL30)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 3 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 3 CS lymph nodes TCSLNODE
T31 1 CS lymph nodes eval TCSLNEVAL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS version input original TCSVERINORIG
T64 6 CS version input current TCSVERINCUR

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS lymph nodes must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL30)
Sub–edit  Conditions Outcome
TVAL30-1 T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> '999999') AND NOT VALID CS_LYMPH_NODES(T15, T21, T30) CS data items filled with 'R' at posting.
TVAL30-2 Edit for CSV2 to follow  
Table
Feedback report messages (TVAL30)
Sub–edit  Text Type
TVAL30-1 CS lymph nodes is invalid for the corresponding CS schema, based on the recommended version of the AJCC CS Algorithm (using CSV1). CS error
TVAL30-2 Edit for CSV2 to follow  
Table
Revision (TVAL30)
Year Description
2010 Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added.
Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2.
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL31

Purpose

This edit validates CS lymph nodes eval.

Table
Referenced fields (TVAL31)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 3 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 3 CS lymph nodes TCSLNODE
T31 1 CS lymph nodes eval TCSLNEVAL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS version input original TCSVERINORIG
T64 6 CS version input current TCSVERINCUR

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS lymph nodes eval must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL31)
Sub–edit  Conditions Outcome
TVAL31-1 T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> '999999') AND NOT VALID_CS_REG_NODES_EVAL(T15, T21, T31) CS data items filled with 'R' at posting.
TVAL31-2 Edit for CSV2 to follow  
Table
Feedback report messages (TVAL31)
Sub–edit  Text Type
TVAL31-1 CS lymph nodes eval is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm.(using CSV1) CS error
TVAL31-2 Edit for CSV2 to follow  
Table
Revision (TVAL31)
Year Description
2010 Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added.
Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2.
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL32

Purpose

This edit validates regional nodes examined.

Table
Referenced fields (TVAL32)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 3 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 3 CS lymph nodes TCSLNODE
T31 1 CS lymph nodes eval TCSLNEVAL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS version input original TCSVERINORIG
T64 6 CS version input current TCSVERINCUR

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • Regional nodes examined must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL32)
Sub–edit  Conditions Outcome
TVAL32-1 T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> '999999') AND NOT VALID_REGIONAL_NODES_EXAMINED(T15, T21, T32) CS data items filled with 'R' at posting.
TVAL32-2 Edit for CSV2 to follow  
Table
Feedback report messages (TVAL32)
Sub–edit  Text Type
TVAL32-1 Regional nodes examined is invalid for the corresponding CS schema, based on the recommended version of the AJCC CS Algorithm (using CSV1). CS error
TVAL32-2 Edit for CSV2 to follow  
Table
Revision (TVAL32)
Year Description
2010 Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added.
Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2.
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL33

Purpose

This edit validates regional nodes positive.

Table
Referenced fields (TVAL33)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 3 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 3 CS lymph nodes TCSLNODE
T31 1 CS lymph nodes eval TCSLNEVAL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS version input original TCSVERINORIG
T64 6 CS version input current TCSVERINCUR

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • Regional nodes positive must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL33)
Sub–edit  Conditions Outcome
TVAL33-1 T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> '999999') AND NOT VALID_REGIONAL_NODES_POSITIVE(T15, T21, T33) CS data items filled with 'R' at posting.
TVAL33-2 Edit for CSV2 to follow  
Table
Feedback report messages TVAL33)
Sub–edit  Text Type
TVAL33-1 Regional nodes positive is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm.(using CSV1). CS error
TVAL33-2 Edit for CSV2 to follow  
Table
Revision (TVAL33)
Year Description
2010 Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added.
Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2.
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL34

Purpose

This edit validates CS mets at dx.

Table
Referenced fields (TVAL34)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 3 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 3 CS lymph nodes TCSLNODE
T31 1 CS lymph nodes eval TCSLNEVAL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS version input original TCSVERINORIG
T64 6 CS version input current TCSVERINCUR

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS mets at dx must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL34)
Sub–edit  Conditions Outcome
TVAL34-1 T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38 <>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> '999999') AND NOT VALID_CS_METS_AT_DX(T15, T21, T34) CS data items filled with 'R' at posting.
TVAL34-2 Edit for CSV2 to follow  
Table
Feedback report messages (TVAL34)
Sub–edit  Text Type
TVAL34-1 CS mets at dx is invalid for the corresponding CS schema, based on the recommended version of the AJCC CS Algorithm (using CSV1) CS error
TVAL34-2 Edit for CSV2 to follow  
Table
Revision (TVAL34)
Year Description
2010 Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added.
Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2.
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL35

Purpose

This edit validates CS mets eval.

Business rules

Table
Referenced fields (TVAL35)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 3 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 3 CS lymph nodes TCSLNODE
T31 1 CS lymph nodes eval TCSLNEVAL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS version input original TCSVERINORIG
T64 6 CS version input current TCSVERINCUR
For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS mets eval must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL35)
Sub–edit  Conditions Outcome
TVAL35-1 T5 IN ['1', '2']AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> '999999') AND NOT VALID_CS_METS_EVAL(T15, T21, T35) CS data items filled with 'R' at posting.
TVAL35-2 Edit for CSV2 to follow  
Table
Feedback report messages (TVAL35)
Sub–edit  Text Type
TVAL35-1 CS mets eval is invalid for the corresponding CS schema, based on the recommended version of the AJCC CS Algorithm (using CSV1). CS error
TVAL35-2 Edit for CSV2 to follow  
Table
Revision (TVAL35)
Year Description
2010 Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added.
Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2.
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL36

Purpose

This edit validates CS site-specific factor 1.

Table
Referenced fields (TVAL36)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 3 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 3 CS lymph nodes TCSLNODE
T31 1 CS lymph nodes eval TCSLNEVAL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS version input original TCSVERINORIG
T64 6 CS version input current TCSVERINCUR

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS site-specific factor 1 must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL36)
Sub–edit  Conditions Outcome
TVAL36-1 T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> '999999') AND NOT VALID_CS_SITE-SPECIFIC_FACTOR_1(T15, T21, T36) CS data items filled with 'R' at posting.
TVAL36-2 Edit for CSV2 to follow  
Table
Feedback report messages (TVAL36)
Sub–edit  Text Type
TVAL36-1 CS site-specific factor 1 is invalid for the corresponding CS schema, based on the recommended version of the AJCC CS Algorithm (using CSV1). CS error
TVAL36-2 Edit for CSV2 to follow  
Table
Revision (TVAL36)
Year Description
2010 Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added.
Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2.
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm.
2004 Edit added: New edit.

TVAL37

Purpose

This edit validates CS site-specific factor 2.

Table
Referenced fields (TVAL37)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 3 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 3 CS lymph nodes TCSLNODE
T31 1 CS lymph nodes eval TCSLNEVAL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS version input original TCSVERINORIG
T64 6 CS version input current TCSVERINCUR

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS site-specific factor 2 must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL37)
Sub–edit  Conditions Outcome
TVAL37-1 T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> '999999') AND NOT VALID_CS_SITE-SPECIFIC_FACTOR_2(T15, T21, T37) CS data items filled with 'R' at posting.
TVAL37-2 Edit for CSV2 to follow  
Table
Feedback report messages (TVAL37)
Sub–edit  Text Type
TVAL37-1 CS site-specific factor 2 is invalid for the corresponding CS schema, based on the recommended version of the AJCC CS Algorithm (using CSV1). CS error
TVAL37-2 Edit for CSV2 to follow  
Table
Revision (TVAL37)
Year Description
2010 Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added.
Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2.
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm.
2004 Edit added: New edit.

TVAL38

Purpose

This edit validates CS site-specific factor 3.

Table
Referenced fields (TVAL38)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 3 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 3 CS lymph nodes TCSLNODE
T31 1 CS lymph nodes eval TCSLNEVAL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS version input original TCSVERINORIG
T64 6 CS version input current TCSVERINCUR

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS site-specific factor 3 must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL38)
Sub–edit  Conditions Outcome
TVAL38-1 T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> '999999') AND NOT VALID_CS_SITE-SPECIFIC_FACTOR_3(T15, T21, T38) CS data items filled with 'R' at posting.
TVAL38-2 Edit for CSV2 to follow  
Table
Feedback report messages (TVAL38)
Sub–edit  Text Type
TVAL38-1 CS site-specific factor 3 is invalid for the corresponding CS schema, based on the recommended version of the AJCC CS Algorithm (using CSV1). CS error
TVAL38-2 Edit for CSV2 to follow  
Table
Revision (TVAL38)
Year Description
2010 Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added.
Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2.
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm.
2004 Edit added: New edit.

TVAL39

Purpose

This edit validates CS site-specific factor 4.

Table
Referenced fields (TVAL39)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 3 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 3 CS lymph nodes TCSLNODE
T31 1 CS lymph nodes eval TCSLNEVAL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS version input original TCSVERINORIG
T64 6 CS version input current TCSVERINCUR

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS site-specific factor 4 must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL39)
Sub–edit  Conditions Outcome
TVAL39-1 T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> '999999') AND NOT VALID_CS_SITE-SPECIFIC_FACTOR_4(T15, T21, T39) CS data items filled with 'R' at posting.
TVAL39-2 Edit for CSV2 to follow  
Table
Feedback report messages (TVAL39)
Sub–edit  Text Type
TVAL39-1 CS site-specific factor 4 is invalid for the corresponding CS schema, based on the recommended version of the AJCC CS Algorithm (using CSV1). CS error
TVAL39-2 Edit for CSV2 to follow  
Table
Revision (TVAL39)
Year Description
2010 Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added.
Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2.
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm.
2004 Edit added: New edit.

TVAL40

Purpose

This edit validates CS site-specific factor 5.

Table
Referenced fields (TVAL40)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 3 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 3 CS lymph nodes TCSLNODE
T31 1 CS lymph nodes eval TCSLNEVAL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS version input original TCSVERINORIG
T64 6 CS version input current TCSVERINCUR

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28and with at least one known CS variable
  • CS site-specific factor 5 must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL40)
Sub–edit  Conditions Outcome
TVAL40-1 T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> '999999') AND NOT VALID_CS_SITE-SPECIFIC_FACTOR_5(T15, T21, T40) CS data items filled with 'R' at posting.
TVAL40-2 Edit for CSV2 to follow  
Table
Feedback report messages (TVAL40)
Sub–edit  Text Type
TVAL40-1 CS site-specific factor 5 is invalid for the corresponding CS schema, based on the recommended version of the AJCC CS Algorithm (using CSV1). CS error
TVAL40-2 Edit for CSV2 to follow  
Table
Revision (TVAL40)
Year Description
2010 Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added.
Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2.
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL41

Purpose

This edit validates CS site-specific factor 6.

Table
Referenced fields (TVAL41)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD–O–2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 3 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 3 CS lymph nodes TCSLNODE
T31 1 CS lymph nodes eval TCSLNEVAL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS version input original TCSVERINORIG
T64 6 CS version input current TCSVERINCUR

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS site-specific factor 6 must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Table
Edit logic (TVAL41)
Sub–edit  Conditions Outcome
TVAL41-1 T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> '999999') AND NOT VALID_CS_SITE-SPECIFIC_FACTOR_6(T15, T21, T41) CS data items filled with 'R' at posting.
TVAL41-2 Edit for CSV2 to follow  
Table
Feedback report messages (TVAL41)
Sub–edit  Text Type
TVAL41-1 CS site-specific factor 6 is invalid for the corresponding CS schema, based on the recommended version of the AJCC CS Algorithm (using CSV1). CS error
TVAL41-2 Edit for CSV2 to follow  
Table
Revision (TVAL41)
Year Description
2010 Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS lymph nodes has been changed from 2 to 3. CS Version input current has been added.
Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields are the correct length according to CS Version 1 or CS Version 2.
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL42

Purpose

This edit validates AJCC clinical T

Table
Referenced fields (TVAL42)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T42 9 AJCC clinical T TAJCCCLINT

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29 and Date of Diagnosis is between 2003 and 2007,
  • AJCC clinical T must be one of the Eligible AJCC clinical T values for the corresponding site30.

Edit Logic

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Table
Edit logic (TVAL42)
Sub–edit  Conditions Outcome
TVAL42-1 T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T42 NOT IN [Eligible AJCC clinical T for Site X] AJCC TNM data items filled with 'R' at posting.
Table
Feedback report messages (TVAL42)
Sub–edit  Text Type
TVAL42-1 AJCC clinical T is invalid for reported site. AJCC TNM error
Table
Revision (TVAL42)
Year Description
2009 Edit no longer applicable:  Variable T42 no longer reported.
2004 Edit added: New edit.

TVAL43

Purpose

This edit validates AJCC clinical N.

Table
Referenced fields (TVAL43)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T43 3 AJCC clinical N TAJCCCLINN

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29 and Date of Diagnosis is between 2003 and 2007,
  • AJCC clinical N must be one of the Eligible AJCC clinical N values for the corresponding site31.

Edit Logic

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example : Colorectal, breast or prostate.

Table
Edit logic (TVAL43)
Sub–edit  Conditions Outcome
TVAL43-1 T5 IN ['1', '2'] AND ( T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T43 NOT IN [Eligible AJCC clinical N for Site X] AJCC TNM data items filled with 'R' at posting.
Table
Feedback report messages (TVAL43)
Sub–edit  Text Type
TVAL43-1 AJCC clinical N is invalid for reported site. AJCC TNM error
Table
Revision (TVAL43)
Year Description
2009 Edit no longer applicable:  Variable T43 no longer reported.
2004 Edit added: New edit.

TVAL44

Purpose

This edit validates AJCC clinical M.

Table
Referenced fields (TVAL44)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T44 3 AJCC clinical M TAJCCCLINM

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29 and Date of Diagnosis is between 2003 and 2007,
  • AJCC clinical M must be one of the Eligible AJCC clinical M values for the corresponding site32.

Edit Logic

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Ex: Colorectal, breast or prostate.

Table
Edit logic (TVAL44)
Sub–edit  Conditions Outcome
TVAL44-1 T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <=2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T44 NOT IN [Eligible AJCC clinical M for Site X] AJCC TNM data items filled with 'R' at posting.
Table
Feedback report messages (TVAL44)
Sub–edit  Text Type
TVAL44-1 AJCC clinical M is invalid for reported site. AJCC TNM error
Table
Revision (TVAL44)
Year Description
2009 Edit no longer applicable:  Variable T44 no longer reported.
2004 Edit added: New edit.

TVAL45

Purpose

This edit validates AJCC pathologic T.

Table
Referenced fields (TVAL45)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T45 9 AJCC pathologic T TAJCCPATHT

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29 and Date of Diagnosis is between 2003 and 2007,
  • AJCC pathologic T must be one of the Eligible AJCC pathologic T values for the corresponding site33.

Edit Logic

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Table
Edit logic (TVAL45)
Sub–edit  Conditions Outcome
TVAL45-1 T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <=2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T45 NOT IN [Eligible AJCC pathologic T for Site X] AJCC TNM data items filled with 'R' at posting.
Table
Feedback report messages (TVAL45)
Sub–edit  Text Type
TVAL45-1 AJCC pathologic T is invalid for reported site. AJCC TNM error
Table
Revision (TVAL45)
Year Description
2009 Edit no longer applicable:  Variable T45 no longer reported.
2004 Edit added: New edit.

TVAL46

Purpose

This edit validates AJCC pathologic N.

Table
Referenced fields (TVAL46)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T46 3 AJCC pathologic N TAJCCPATHN

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29 and Date of Diagnosis is between 2003 and 2007,
  • AJCC pathologic N must be one of the Eligible AJCC pathologic N values for the corresponding site34.

Edit Logic

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Table
Edit logic (TVAL46)
Sub–edit  Conditions Outcome
TVAL46-1 T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T46 NOT IN [Eligible AJCC pathologic N for Site X] AJCC TNM data items filled with 'R' at posting.
Table
Feedback report messages (TVAL46)
Sub–edit  Text Type
TVAL46-1 AJCC pathologic N is invalid for reported site. AJCC TNM error
Table
Revision (TVAL46)
Year Description
2009 Edit no longer applicable:  Variable T46 no longer reported.
2004 Edit added: New edit.

TVAL47

Purpose

This edit validates AJCC pathologic M.

Table
Referenced fields (TVAL47)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T47 3 AJCC pathologic M TAJCCPATHM

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29 and Date of Diagnosis is between 2003 and 2007,
  • AJCC pathologic M must be one of the Eligible pathologic M values for the corresponding site35.

Edit Logic

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Table
Edit logic (TVAL47)
Sub–edit  Conditions Outcome
TVAL47-1 T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T47 NOT IN [Eligible AJCC pathologic M for Site X] AJCC TNM data items filled with 'R' at posting.
Table
Feedback report messages (TVAL47)
Sub–edit  Text Type
TVAL47-1 AJCC pathologic M is invalid for reported site. AJCC TNM error
Table
Revision (TVAL47)
Year Description
2009 Edit no longer applicable:  Variable T47 no longer reported.
2004 Edit added: New edit.

TVAL48

Purpose

This edit validates AJCC clinical TNM stage group.

Table
Referenced fields (TVAL48)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T48 4 AJCC clinical TNM stage group TAJCCCLINSG

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29 and Date of Diagnosis is between 2003 and 2007,
  • AJCC clinical TNM stage group must be one of the Eligible AJCC clinical TNM stage group values for the corresponding site38.

Edit Logic

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Table
Edit logic (TVAL48)
Sub–edit  Conditions Outcome
TVAL48-1 T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T48 NOT IN [Eligible AJCC clinical TNM stage group for Site X] AJCC TNM data items filled with 'R' at posting.
Table
Feedback report messages (TVAL48)
Sub–edit  Text Type
TVAL48-1 AJCC clinical TNM stage group is invalid for reported site. AJCC TNM error
Table
Revision (TVAL48)
Year Description
2009 Edit no longer applicable:  Variable T48 no longer reported.
2004 Edit added: New edit.

TVAL49

Purpose

This edit validates AJCC pathologic TNM stage group.

Table
Referenced fields (TVAL49)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T49 4 AJCC pathologic TNM stage group TAJCCPATHSG

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29 and Date of Diagnosis is between 2003 and 2007,
  • AJCC pathologic TNM stage group must be one of the Eligible AJCC pathologic TNM stage group values for the corresponding site37.

Edit Logic

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Table
Edit logic (TVAL49)
Sub–edit  Conditions Outcome
TVAL49-1 T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T49 NOT IN [Eligible AJCC pathologic TNM stage group for Site X] AJCC TNM data items filled with 'R' at posting.
Table
Feedback report messages (TVAL49)
Sub–edit  Text Type
TVAL49-1 AJCC pathologic TNM stage group is invalid for reported site. AJCC TNM error
Table
Revision (TVAL49)
Year Description
2009 Edit no longer applicable:  Variable T49 no longer reported.
2004 Edit added: New edit.

TVAL50

Purpose

This edit validates AJCC TNM stage group.

Table
Referenced fields (TVAL50)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T50 4 AJCC TNM stage group TAJCCSG

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29 and Date of Diagnosis is between 2003 and 2007,
  • AJCC TNM stage group must be one of the Eligible AJCC TNM stage group values for the corresponding site37.

Edit Logic

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Table
Edit logic (TVAL50)
Sub–edit  Conditions Outcome
TVAL50-1 T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T50 NOT IN [Eligible AJCC TNM stage group for Site X] AJCC TNM data items filled with 'R' at posting.
Table
Feedback report messages (TVAL50)
Sub–edit  Text Type
TVAL50-1 AJCC TNM stage group is invalid for reported site. AJCC TNM error
Table
Revision (TVAL50)
Year Description
2009 Edit no longer applicable:  Variable T50 no longer reported.
2004 Edit added: New edit.

TVAL51

Purpose

This edit validates AJCC edition number code.

Table
Referenced fields (TVAL51)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T51 2 AJCC edition number TAJCCEDNUM

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29 and Date of Diagnosis is between 2003 and 2007,
  • AJCC edition number must be one of the Eligible AJCC edition number codes38.

Edit Logic

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Table
Edit logic (TVAL51)
Sub–edit  Conditions Outcome
TVAL51-1 T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T51 NOT IN [Eligible AJCC edition number codes] AJCC TNM data items filled with 'R' at posting.
Table
Feedback report messages (TVAL51)
Sub–edit  Text Type
TVAL51-1 AJCC edition number code is either invalid or not eligible for the CCR system. AJCC TNM error
Table
Revision (TVAL51)
Year Description
2009 Edit no longer applicable:  Variable T51 no longer reported.
2004 Edit added: New edit.

TVAL52

Purpose

This edit validates CS version input original.

Table
Referenced fields (TVAL52)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T27 3 CS tumour size TCSTSIZE
T28 3 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 3 CS lymph nodes TCSLNODE
T31 1 CS lymph nodes eval TCSLNEVAL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T65 3 CS site-specific factor 7 TCSSSF7
T66 3 CS site-specific factor 8 TCSSSF8
T67 3 CS site-specific factor 9 TCSSSF9
T68 3 CS site-specific factor 10 TCSSSF10
T69 3 CS site-specific factor 11 TCSSSF11
T70 3 CS site-specific factor 12 TCSSSF12
T71 3 CS site-specific factor 13 TCSSSF13
T72 3 CS site-specific factor 14 TCSSSF14
T73 3 CS site-specific factor 15 TCSSSF15
T74 3 CS site-specific factor 16 TCSSSF16
T75 3 CS site-specific factor 17 TCSSSF17
T76 3 CS site-specific factor 18 TCSSSF18
T77 3 CS site-specific factor 19 TCSSSF19
T78 3 CS site-specific factor 20 TCSSSF20
T79 3 CS site-specific factor 21 TCSSSF21
T80 3 CS site-specific factor 22 TCSSSF22
T81 3 CS site-specific factor 23 TCSSSF23
T82 3 CS site-specific factor 24 TCSSSF24
T83 3 CS site-specific factor 25 TCSSSF25
T52 6 CS version input original TCSVERINORIG
T63 1 Lymph-vascular invasion TLYMPHVASINV
T64 6 CS version input current TCSVERINCUR

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope and with at least one known CS variable
  • CS version input original must be one of the Eligible CS version input original codes.
Table
Edit logic (TVAL52)
Sub–edit  Conditions Outcome
TVAL52-1 T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND T64 = NULL AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' or T52 <> '999999') AND T52 NOT IN [Eligible CS version input original codes] CS data items filled with 'R' at posting.
TVAL52-2 T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND (T64 >= '020200' AND T64 <> '999999') AND (T27<>'999' OR T28<>'999' OR T29<>'9' OR T30<>'999' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T63 <> '9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T63 <> '9" OR T65 <> '999' OR T66 <> '999' OR T67 <> '999' OR T68 <> '999' OR T69 <> '999' OR T70 <> '999' OR T71 <> '999' OR T72 <> '999' OR T73 <> '999' OR T74 <> '999' OR T75 <> '999' OR T76 <> '999' OR T77 <> '999' OR T78 <> '999' OR T79 <> '999' OR T80 <> '999' OR T81 <> '999' OR T82 <> '999' OR T83 <> '999' OR T52 <> '999999') AND T52 NOT IN [Eligible CS version input original codes] CS data items filled with 'R' at posting.
Table
Feedback report messages (TVAL52)
Sub–edit  Text Type
TVAL52-1 CS version input original is not a valid version number. CS error
TVAL52-2 CS Version input original is not a valid version number (for CSV2). CS error
Table
Revision (TVAL52)
Year Description
2010 Referenced fields, Business rules, edit logic, and Feedback report messages: Variable Names changed - CS version 1st to CS version input original (acronym changed from TCSFVER to TCSVERINORIG), CS reg nodes eval to CS lymph nodes eval (acronym changed from TCSRNEVAL to TCSLNEVAL). Length of CS Extension and CS Lymph nodes has been changed from 2 to 3. CS Version input current has been added. Lymph-vascular invasion has been added.
Edit Logic and Feedback report messages: CS Version input current is checked to make sure fields checked are the correct length according to CS Version 1 or CS Version 2. New fields added for verifications after implementation of CSV2.
2007 Edit added: New edit.

TVAL53

Purpose

This edit validates the Ambiguous terminology diagnosis code.

Table
Referenced fields (TVAL53)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T53 1 Ambiguous Terminology Diagnosis TAMBIGTERM

Business rules

For Add and Update Tumour records
  • Ambiguous terminology diagnosis must be one of the Eligible Ambiguous terminology diagnosis codes.
Table
Edit logic (TVAL53)
Sub–edit  Conditions Outcome
TVAL53-1 T5 IN ['1', '2'] AND T53 IS NOT NULL AND NOT IN [Eligible Ambiguous terminology diagnosis codes] Record rejected
Table
Feedback report messages (TVAL53)
Sub–edit  Text Type
TVAL53-1 Ambiguous terminology diagnosis code is invalid. Core error
Table
Revision (TVAL53)
Year Description
2008 Edit added: New edit.

TVAL54

Purpose

This edit validates the Date of conclusive diagnosis.

Table
Referenced fields (TVAL54)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T54 8 Date of conclusive diagnosis TDATCONCLUSDIAG
T54.YEAR 4 First 4 digits of T54 (year of date of conclusive diagnosis) Not applicable
T54.MONTH 2 5th and 6th digits of T54 (month of date of conclusive diagnosis) Not applicable
T54.DAY 2 7th and 8th digits of T56 (day of date of conclusive diagnosis) Not applicable

Business rules

For Add and Update Tumour records, Date of conclusive diagnosis
  • Must be exclusively composed of numbers: 0 to 9.
  • Must be 8 digits long.
  • If Year or Month or Day is accessioned then the Date of conclusive diagnosis must be accessioned.
  • If Year or Month or Day is not applicable then the Date of conclusive diagnosis must be not applicable.
  • If Year is unknown then Month and Day must be unknown.
  • If Month is unknown then Day must be unknown.
  • If Year and Month are known and Day is unknown then Month must be a valid month.
  • If Year, Month and Day are known then it must be a valid calendar date.
  • Must be between January 1st, 2008 and December 31st of Reference year inclusively.
Table
Edit logic (TVAL54)
Sub–edit  Conditions Outcome
TVAL54-1 T5 IN ['1', '2'] AND LENGTH (T54) <> 8 OR NOT IS_COMPOSED_OF (T54, '0123456789') Record Rejected
TVAL54-2 T5 IN ['1', '2'] AND LENGTH (T54) = 8 AND IS_COMPOSED_OF (T54, '0123456789') AND (T54.YEAR = '0000' OR T54.MONTH='00' OR T54.DAY='00') AND (T54.YEAR <> '0000' OR T54.MONTH <> '00' OR T54.DAY <> '00') Record Rejected
TVAL54-3 T5 IN ['1', '2'] AND LENGTH (T54) = 8 AND IS_COMPOSED_OF (T54, '0123456789') AND (T54.YEAR = '8888' OR T54.MONTH='88' OR T54.DAY='88') AND (T54.YEAR <> '8888' OR T54.MONTH <> '88' OR T54.DAY <> '88') Record Rejected
TVAL54-4 T5 IN ['1', '2'] AND LENGTH (T54) = 8 AND IS_COMPOSED_OF (T54, '0123456789') AND T54.YEAR = '9999' AND (T54.MONTH <> '99' OR T54.DAY <> '99') Record Rejected
TVAL54-5 T5 IN ['1', '2'] AND LENGTH (T54) = 8 AND IS_COMPOSED_OF (T54, '0123456789') AND T54.MONTH = '99' AND T54.DAY <> '99' Record Rejected
TVAL54-6 T5 IN ['1', '2'] AND LENGTH (T54) = 8 AND IS_COMPOSED_OF (T54, '0123456789') AND T54.MONTH NOT IN ['01'-'12', '99'] AND T54.DAY = '99' Record Rejected
TVAL54-7 T5 IN ['1', '2'] AND LENGTH (T54) = 8 AND IS_COMPOSED_OF (T54, '0123456789') AND T54 NOT IN ['00000000', '88888888', '99999999'] AND T54.MONTH <> '99' AND T54.DAY <> '99' AND NOT IS_VALID_DATE Record Rejected
TVAL54-8 T5 IN ['1', '2'] AND T54 NOT IN ['00000000', '88888888', '99999999'] AND (T54.YEAR < 2008 OR T54.YEAR > CYCLE_YEAR) Record Rejected
Table
Feedback report messages (TVAL54)
Sub–edit  Text Type
TVAL54-1 Date of conclusive diagnosis is not composed of 8 numbers. Core Error
TVAL54-2 Year, month and day must be 'accessioned'. Core Error
TVAL54-3 Year, month and day must be 'not applicable'. Core Error
TVAL54-4 Year, month and day must be 'unknown'. Core Error
TVAL54-5 Date of conclusive diagnosis: month and day must be 'unknown'. Core Error
TVAL54-6 Date of conclusive diagnosis is not a valid partial date: month is invalid. Core Error
TVAL54-7 Date of conclusive diagnosis is not a valid calendar date. Core Error
TVAL54-8 Date of conclusive diagnosis is out of scope. Core Error
Table
Revision (TVAL54)
Year Description
2008 Edit added: New edit.

TVAL55

Purpose

This edit validates the Type of multiple tumours reported as one primary code.

Table
Referenced fields (TVAL55)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T55 2 Type of multiple tumours reported as one primary TMULTTUMONEPRIM

Business rules

For Add and Update Tumour records, Type of multiple tumours reported as one primary code
  • Must contain a valid code.
Table
Edit logic (TVAL55)
Sub–edit  Conditions Outcome
TVAL55-1 T5 IN ['1', '2'] AND T55 IS NOT NULL AND T55 NOT IN [Eligible Type of multiple tumours reported as one primary codes] Record rejected
Table
Feedback report messages (TVAL55)
Sub–edit  Text Type
TVAL55-1 Type of multiple tumours reported as one primary code is invalid. Core error
Table
Revision (TVAL55)
Year Description
2008 Edit added: New edit.

TVAL56

Purpose

This edit validates the Date of multiple tumours.

Table
Referenced fields (TVAL56)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T56 8 Date of multiple tumours TDATMULT
T56.YEAR 4 First 4 digits of T56 (year of date of multiple tumours) Not applicable
T56.MONTH 2 5th and 6th digits of T56 (month of date of multiple tumours) Not applicable
T56.DAY 2 7th and 8th digits of T56 (day of date of multiple tumours) Not applicable

Business rules

For Add and Update Tumour records, Date of multiple tumours
  • Must be exclusively composed of numbers: 0 to 9.
  • Must be 8 digits long.
  • If Year or Month or Day relates to a single tumour then the Date of multiple tumours must contain all zeros.
  • If Year or Month or Day is not applicable then the Date of multiple tumours must be not applicable.
  • If Year is unknown then Month and Day must be unknown.
  • If Month is unknown then Day must be unknown.
  • If Year and Month are known and Day is unknown then Month must be a valid month.
  • If Year, Month and Day are known then it must be a valid calendar date.
  • Must be between January 1st, 2008 and December 31st of Reference year inclusively.
Table
Edit logic (TVAL56)
Sub–edit  Conditions Outcome
TVAL56-1 T5 IN ['1', '2'] AND LENGTH (T56) <> 8 OR NOT IS_COMPOSED_OF (T56, '0123456789') Record Rejected
TVAL56-2 T5 IN ['1', '2'] AND LENGTH (T56) = 8 AND IS_COMPOSED_OF (T56, '0123456789') AND (T56.YEAR = '0000' OR T56.MONTH = '00' OR T56.DAY = '00') AND (T56.YEAR <> '0000' OR T56.MONTH <> '00' OR T56.DAY <> '00') Record Rejected
TVAL56-3 T5 IN ['1', '2'] AND LENGTH (T56) = 8 AND IS_COMPOSED_OF (T56, '0123456789') AND (T56.YEAR = '8888' OR T56.MONTH = '88' OR T56.DAY = '88') AND (T56.YEAR <> '8888' OR T56.MONTH <> '88' OR T56.DAY <> '88') Record Rejected
TVAL56-4 T5 IN ['1', '2'] AND LENGTH (T56) = 8 AND IS_COMPOSED_OF (T56, '0123456789') AND T56.YEAR = '9999' AND (T56.MONTH <> '99' OR T56.DAY <> '99') Record Rejected
TVAL56-5 T5 IN ['1', '2'] AND LENGTH (T56) = 8 AND IS_COMPOSED_OF (T56, '0123456789') AND T56.MONTH = '99' AND T56.DAY <> '99' Record Rejected
TVAL56-6 T5 IN ['1', '2'] AND LENGTH (T56) = 8 AND IS_COMPOSED_OF (T56, '0123456789') AND T56.MONTH NOT IN ['01'-'12', '99'] AND T56.DAY = '99' Record Rejected
TVAL56-7 T5 IN ['1', '2'] AND LENGTH (T56) = 8 AND IS_COMPOSED_OF (T56, '0123456789') AND T56 NOT IN ['00000000', '88888888', '99999999'] AND T56.MONTH <> '99' AND T56.DAY <> '99' AND NOT IS_VALID_DATE Record Rejected
TVAL56-8 T5 IN ['1', '2'] AND T56 NOT IN ['00000000', '88888888', '99999999'] AND (T56.YEAR < 2008 OR T56.YEAR > CYCLE_YEAR) Record Rejected
Table
Feedback report messages (TVAL56)
Sub–edit  Text Type
TVAL56-1 Date of multiple tumours is not composed of 8 numbers. Core Error
TVAL56-2 Year, month and day must relate to a single tumour (all zeros). Core Error
TVAL56-3 Year, month and day must be 'not applicable'. Core Error
TVAL56-4 Year, month and day must be 'unknown'. Core Error
TVAL56-5 Date of multiple tumours: month and day must be 'unknown'. Core Error
TVAL56-6 Date of multiple tumours is not a valid partial date: month is invalid. Core Error
TVAL56-7 Date of multiple tumours is not a valid calendar date. Core Error
TVAL56-8 Date of multiple tumours is out of scope. Core Error
Table
Revision (TVAL56)
Year Description
2008 Edit added: New edit.

TVAL57

Purpose

This edit validates the Multiplicity counter.

Table
Referenced fields (TVAL57)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T57 2 Multiplicity counter TMULTCOUNT

Business rules

For Add and Update Tumour records, Multiplicity counter
  • Must be a numeric value between '01' and '87', or '88' or '99'
Table
Edit logic (TVAL57)
Sub–edit  Conditions Outcome
TVAL57-1 T5 IN ['1', '2'] AND T57 IS NOT NULL AND T57 NOT IN [Eligible Multiplicity counter codes] Record Rejected
Table
Feedback report messages (TVAL57)
Sub–edit  Text Type
TVAL57-1 Multiplicity counter is invalid Core error
Table
Revision (TVAL57)
Year Description
2008 Edit added: New edit.

TVAL58

Purpose

This edit validates the date of diagnosis flag.

Table
Referenced fields (TVAL58)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T58 1 Date of diagnosis flag TDATDIAGFLAG

Business rules

For Add and Update Tumour records
  • Date of diagnosis flag must be one of the Eligible date of diagnosis flag codes.
Table
Edit logic (TVAL58)
Sub–edit  Conditions Outcome
TVAL58-1 T5 IN ['1', '2'] AND T58 NOT IN [Eligible date of diagnosis flag codes] Record Rejected
Table
Feedback report messages (TVAL58)
Sub–edit  Text Type
TVAL58-1 Date of diagnosis flag code is invalid. Core fatal error
Table
Revision (TVAL58)
Year Description
2010 New edit added.

TVAL59

Purpose

This edit validates the date of conclusive diagnosis flag.

Table
Referenced fields (TVAL59)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T59 1

Date of conclusive diagnosis flag

TDATCONCLUSDIAGFLAG

Business rules

For Add and Update Tumour records
  • Date of conclusive diagnosis flag must be one of the Eligible date of conclusive diagnosis flag codes.
Table
Edit logic (TVAL59)
Sub–edit  Conditions Outcome
TVAL59-1 T5 IN ['1', '2'] AND T59 NOT IN [Eligible date of conclusive diagnosis flag codes] Record Rejected
Table
Feedback report messages (TVAL59)
Sub–edit  Text Type
TVAL59-1 Date of conclusive diagnosis flag code is invalid. Core fatal error
Table
Revision (TVAL59)
Year Description
2010 New edit added

TVAL60

Purpose

This edit validates the date of multiple tumours flag.

Table
Referenced fields (TVAL60)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T60 1 Date of multiple tumours flag TDATMULTFLAG

Business rules

For Add and Update Tumour records
  • Date of multiple tumours flag must be one of the Eligible date of multiple tumours flag codes.
Table
Edit logic (TVAL60)
Sub–edit  Conditions Outcome
TVAL60-1 T5 IN ['1', '2'] AND T59 NOT IN [Eligible date of multiple tumours flag codes] Record Rejected
Table
Feedback report messages (TVAL60)
Sub–edit  Text Type
TVAL60-1 Date of multiple tumours flag code is invalid. Core fatal error
Table
Revision (TVAL60)
Year Description
2010 New edit added.

TVAL61

Purpose

This edit validates Grade path value.

Table
Referenced fields (TVAL61)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T61 1 Grade path value TGRADEPATHVAL

Business rules

For Add and Update Tumour records
  • Grade path value must be one of the Eligible Grade path value codes.
Table
Edit logic (TVAL61)
Sub–edit  Conditions Outcome
TVAL61-1 T5 IN ['1', '2'] AND T61 IS NOT NULL AND NOT IN [Eligible Grade path value codes] Record rejected
Table
Feedback report messages (TVAL61)
Sub–edit  Text Type
TVAL61-1 Grade path value code is invalid. Core error
Table
Revision (TVAL61)
Year Description
2010 Edit added: New edit

TVAL62

Purpose

This edit validates Grade path system.

Table
Referenced fields (TVAL62)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T62 1 Grade path system TGRADEPATHSYS

Business rules

For Add and Update Tumour records
  • Grade path system must be one of the Eligible Grade path system codes.
Table
Edit logic (TVAL62)
Sub–edit  Conditions Outcome
TVAL62-1 T5 IN ['1', '2'] AND T62 IS NOT NULL AND NOT IN [Eligible Grade path system codes]  
Table
Feedback report messages (TVAL62)
Sub–edit  Text Type
TVAL62-1 Grade path system code is invalid. Core error
Table
Revision (TVAL62)
Year Description
2010 Edit added: New edit

TVAL63

Purpose

This edit validates Lymph-vascular invasion.

Table
Referenced fields (TVAL62)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T64 6

CS version input current

TCSVERINCUR

T63 1

Lymph-vascular invasion

TLYMPHVASINV

Business rules

For Add and Update Tumour records
  • If CS version input current is blank (CSV2 not yet implemented) then Lymph-vascular invasion must be left blank.
  • If CS version input current indicates CSV2 has been implemented then Lymph-vascular invasion must be one of the Eligible Lymph-vascular invasion codes.
Table
Edit logic (TVAL63)
Sub–edit  Conditions Outcome
TVAL63-1 T5 IN ['1', '2'] AND T64 = NULL AND T63 <> NULL Record rejected
TVAL63-2

T5 IN ['1', '2'] AND (T64>= '020200' and T64 <> '999999') and T63 NOT IN [Eligible Lymph-vascular invasion codes]

Record rejected

Table
Feedback report messages (TVAL63)
Sub–edit  Text Type
TVAL63-1 Lymph-vascular invasion code must be blank if CSV2 is not implemented. Core error
TVAL63-2 Lymph-vascular invasion code is invalid. Core error
Table
Revision (TVAL63)
Year Description
2010 Edit added: New edit

TVAL64

Purpose

This edit validates CS Version input current.

Table
Referenced fields (TVAL64)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T27 3 CS tumour size TCSTSIZE
T28 3 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 3 CS lymph nodes TCSLNODE
T31 1 CS lymph nodes eval TCSLNEVAL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T63 1 Lymph-vascular invasion TLYMPHVASINV
T64 6 CS version input current TCSVERINCUR
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T65 3 CS site-specific factor 7 TCSSSF7
T66 3 CS site-specific factor 8 TCSSSF8
T67 3 CS site-specific factor 9 TCSSSF9
T68 3 CS site-specific factor 10 TCSSSF10
T69 3 CS site-specific factor 11 TCSSSF11
T70 3 CS site-specific factor 12 TCSSSF12
T71 3 CS site-specific factor 13 TCSSSF13
T72 3 CS site-specific factor 14 TCSSSF14
T73 3 CS site-specific factor 15 TCSSSF15
T74 3 CS site-specific factor 16 TCSSSF16
T75 3 CS site-specific factor 17 TCSSSF17
T76 3 CS site-specific factor 18 TCSSSF18
T77 3 CS site-specific factor 19 TCSSSF19
T78 3 CS site-specific factor 20 TCSSSF20
T79 3 CS site-specific factor 21 TCSSSF21
T80 3 CS site-specific factor 22 TCSSSF22
T81 3 CS site-specific factor 23 TCSSSF23
T82 3 CS site-specific factor 24 TCSSSF24
T83 3 CS site-specific factor 25 TCSSSF25

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope and with at least one known CS variable
  • CS version input current must be one of the Eligible CS version input current codes.
Table
Edit logic (TVAL64)
Sub–edit  Conditions Outcome
TVAL64-1 (T5 IN ['1', '2'] AND T12.YEAR >= '2004' AND (T27<>'999' OR 'T28<>'999' OR T29<>'9' OR T30<>'999' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T63 <> '9' OR T65 <> '999' OR T66 <> '999' OR T67 <> '999' OR T68 <> '999' OR T69 <> '999' OR T70 <> '999' OR T71 <> '999' OR T72 <> '999' OR T73 <> '999' OR T74 <> '999' OR T75 <> '999' OR T76 <> '999' OR T77 <> '999' OR T78 <> '999' OR T79 <> '999' OR T80 <> '999' OR T81 <> '999' OR T82 <> '999' OR T83 <> '999' OR T52 <> '999999') AND T64 NOT IN [Eligible CS version input current codes] CS data items filled with 'R' at posting.
Table
Feedback report messages (TVAL64)
Sub–edit  Text Type
TVAL64-1 CS version input current is not a valid version number. CS error
Table
Revision (TVAL64)
Year Description
2010 Edit added: New edit.

TVAL65 - TVAL83

Purpose

These edits validate the CS site-specific factors 7 - 25.

Table
Referenced fields (TVAL65-TVAL83)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T64 6 CS version input current TCSVERINCUR
T65-T83 3 CS site-specific factors 7 -25 N/A

Business rules

For Add and Update Tumour records CS site specific factors 7 – 25
  • must be either blank or composed of numbers 0 to 9
  • must be 3 digits long
Table
Edit logic (TVAL65 - TVAL83)
Sub–edit  Conditions Outcome
TVAL65-1 – TVAL83-1 T5 IN ['1', '2'] AND (T64 >= '020200' AND T64 <> '999999') AND T(65, T66, T67 …T83 NOT NULL) and (LENGTH (T66, T67 …T83) <> 3 OR NOT IS_COMPOSED_OF ((T66, T67 …T83), '0123456789')) CS data items filled with 'R' at posting.
Table
Feedback report messages (TVAL65-TVAL83)
Sub–edit  Text Type
TVAL65-1 -TVAL83-1 CS Site specific factor XX code is invalid. CS error
Table
Revision (TVAL65- TVAL83)
Year Description
2010 New edit added.

TVAL84

Purpose

This edit validates CS mets at dx bone.

Table
Referenced fields (TVAL84)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T84 1 CS mets at dx bone TCSMDXBONE

Business rules

For Add and Update Tumour records
  • CS mets at dx bone must be one of the Eligible CS mets at dx bone codes.
Table
Edit logic (TVAL84)
Sub–edit  Conditions Outcome
TVAL84-1 T5 IN ['1', '2'] AND T84 IS NOT NULL AND NOT IN [Eligible CS mets at dx bone codes] Record rejected
Table
Feedback report messages (TVAL84)
Sub–edit  Text Type
TVAL84-1 CS mets at dx bone code is invalid. Core error
Table
Revision (TVAL84)
Year Description
2010 Edit added: New edit

TVAL85

Purpose

This edit validates CS mets at dx brain.

Table
Referenced fields (TVAL85)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T85 1 CS mets at dx brain TCSMDXBRAIN

Business rules

For Add and Update Tumour records
  • CS mets at dx brain must be one of the Eligible CS mets at dx brain codes.
Table
Edit logic (TVAL85)
Sub–edit  Conditions Outcome
TVAL85-1 T5 IN ['1', '2'] AND T85 IS NOT NULL AND NOT IN [Eligible CS mets at dx brain codes] Record rejected
Table
Feedback report messages (TVAL85)
Sub–edit  Text Type
TVAL85-1 CS mets at dx brain code is invalid. Core error
Table
Revision (TVAL85)
Year Description
2010 Edit added: New edit

TVAL86

Purpose

This edit validates CS mets at dx liver.

Table
Referenced fields (TVAL86)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T86 1 CS mets at dx liver TCSMDXLIVER

Business rules

For Add and Update Tumour records
  • CS mets at dx liver must be one of the Eligible CS mets at dx liver codes.
Table
Edit logic (TVAL86)
Sub–edit  Conditions Outcome
TVAL86-1 T5 IN ['1', '2'] AND T86 IS NOT NULL AND NOT IN [Eligible CS mets at dx liver codes] Record rejected
Table
Feedback report messages (TVAL86)
Sub–edit  Text Type
TVAL86-1 CS mets at dx liver code is invalid. Core error
Table
Revision (TVAL86)
Year Description
2010 Edit added: New edit

TVAL87

Purpose

This edit validates CS mets at dx lung.

Table
Referenced fields (TVAL87)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T87 1 CS mets at dx lung TCSMDXLUNG

Business rules

For Add and Update Tumour records
  • CS mets at dx lung must be one of the Eligible CS mets at dx lung codes.
Table
Edit logic (TVAL87)
Sub–edit  Conditions Outcome
TVAL87-1 T5 IN [*'1', '2'] AND T87 IS NOT NULL AND NOT IN [Eligible CS mets at dx lung codes] Record rejected
Table
Feedback report messages (TVAL87)
Sub–edit  Text Type
TVAL87-1 CS mets at dx lung code is invalid. Core error
Table
Revision (TVAL87)
Year Description
2010 Edit added: New edit

3.5 Correlation edits

The purpose of the correlation edits is to enforce the business rules between fields on the same Input record. For ease of use, correlation edits have been divided into two groups:

  • Patient correlation edits: enforce business rules between valid patient fields;
  • Tumour correlation edits: enforce business rules between valid tumour fields.

Correlation edits are only performed on Input records where all referenced fields are valid.

3.5.1 Patient correlation edits

The following table summarizes the purpose of each individual edit of this category.

Table 26
Patient correlation edits summary
Edit name Purpose
PCOR1 Ensures that the content of the patient record is consistent with the action described in the Patient record type.
PCOR2 Verifies the likelihood of given names and gender.
PCOR3 Ensures that first given name, second given name and third given name are used coherently.
PCOR4 Ensures that type of current surname code accurately reflects the content of the current surname field.
PCOR5 Ensures that birth surname and current surname are consistent with type of current surname.
PCOR6 Ensures that at least one surname is reported, either the current surname or the birth surname.
PCOR7 Ensures that date of birth and date of death respect a chronological sequence and time frame.
PCOR8 Ensures that death-related variables present a consistent reporting of the patient's vital status.
PCOR9 Ensures that Death registration number and province/territory or country of death are consistent.
PCOR10 Ensures Death registration number and date of death are consistent.
PCOR11 Ensures Death registration number and Underlying cause of death are consistent.

PCOR1

Purpose

This edit ensures that the content of the patient record is consistent with the action described in the patient record type.

Table
Referenced fields (PCOR1)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P3 9 CCR identification number CCR_ID
P4 1 Patient record type PRECTYPE
P5 1 Type of current surname PTYP_CUR
P6 25 Current surname PCURSNAM
P7 15 First given name PGNAME_1
P8 15 Second given name PGNAME_2
P9 7 Third given name PGNAME_3
P10 1 Sex PSEX
P11 8 Date of birth PDATBIR
P12 3 Province/territory or country of birth PPROVBIR
P13 25 Birth surname PBIRNAM
P14 8 Date of death PDATDEA
P15 3 Province/territory or country of death PPROVDEA
P16 6 Death registration number PDEAREG
P17 4 Underlying cause of death PCAUSDEA
P18 1 Autopsy confirming cause of death PAUTOPSY
P20 1 Date of birth flag PAUTOPSY
P21 1 Date of death flag PAUTOPSY

Business rules

For Add Patient records
  • Patient reporting province/territory, Patient identification number, Type of Current surname, Sex, Date of birth,Province/territory or country of birth, Date of death, Province/territory or country of death, Death registration number, Underlying cause of death and Autopsy confirming cause of death must be provided.
  • CCR identification number must be blank.

For Update Patient records
  • Patient reporting province/territory, Patient identification number, CCR identification number, Type of Current surname, Sex, Date of birth, Province/territory or country of birth, Date of death, Province/territory or country of death, Death registration number, Underlying cause of death and Autopsy confirming cause of death must be provided.

For Delete Patient records

  • Patient reporting Province/territory, Patient identification number, CCR identification number must be provided.
  • Type of Current surname, Current surname, First given name, Second given name, Third given name, Sex, Date of birth, Province/territory or country of birth, Birth surname, Date of death, Province/territory or country of death, Death registration number, Underlying cause of death, Autopsy confirming cause of death, Date of birth and Date of death flag must be blank.
Table
Edit logic (PCOR1)
Sub–edit  Conditions Outcome
PCOR1-1 P4 = '1' AND (P1 IS NULL OR P2 IS NULL OR P3 IS NOT NULL OR P5 IS NULL OR P10 IS NULL OR P11 IS NULL OR P12 IS NULL OR P14 IS NULL OR P15 IS NULL OR P16 IS NULL OR P17 IS NULL OR P18 IS NULL) Record rejected
PCOR1-2 P4 = '2' AND (P1 IS NULL OR P2 IS NULL OR P3 IS NULL OR P5 IS NULL OR P10 IS NULL OR P11 IS NULL OR P12 IS NULL OR P14 IS NULL OR P15 IS NULL OR P16 IS NULL OR P17 IS NULL OR P18 IS NULL) Record rejected
PCOR1-3 P4 = '3' AND (P1 IS NULL OR P2 IS NULL OR P3 IS NULL OR P5 IS NOT NULL OR P6 IS NOT NULL OR P7 IS NOT NULL OR P8 IS NOT NULL OR P9 IS NOT NULL OR P10 IS NOT NULL OR P11 IS NOT NULL OR P12 IS NOT NULL OR P13 IS NOT NULL OR P14 IS NOT NULL OR P15 IS NOT NULL OR P16 IS NOT NULL OR P17 IS NOT NULL OR P18 IS NOT NULL OR P20 IS NOT NULL OR P21 IS NOT NULL ) Record rejected
Table
Feedback report messages (PCOR1)
Sub–edit  Text Type
PCOR1-1 Input record does not respect the Add Patient record format. There are missing or extra values. Core fatal error
PCOR1-2 Input record does not respect the Update Patient record format. There are missing values. Core fatal error
PCOR1-3 Input record does not respect the Delete Patient record format. There are missing or extra values. Core fatal error
Table
Revision (PCOR1)
Year Description
2010 Referenced Fields, Business rules and Edit logic: P20 – Date of birth flag and P21 – Date of death flag added.
2004 Edit renamed: Current edit was formerly known as Correlation Edit No.1.

PCOR2

Purpose

This edit verifies the likelihood of given names and sex.

Table
Referenced fields (PCOR2)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P7 15 First given name PGNAME_1
P8 15 Second given name PGNAME_2
P9 7 Third given name PGNAME_3
P10 1 Sex PSEX
Table
Other parameters (PCOR2)
Parameters Length Description
NAME_SEX_THRESHOLD 3 Tolerated average likelihood of First given name, Second given name and Third given name to be associated to the opposite gender according to given name and Sex registry2. Value must be between 0 and 100. Default value is 95.

Business rules

For Add and Update Patient records
  • If the average likelihood of First given name, Second given name and Third given name to be associated to the opposite gender according to given name and Sex registry is greater than NAME_SEX_THRESHOLD, then a warning must be sent.
Table
Edit logic (PCOR2)
Sub–edit  Conditions Outcome
PCOR2-1 P4 IN ['1', '2'] AND P10 IN ['1', '2'] AND AVERAGE ([Probability of P7 to be associated to opposite gender], [Probability of P8 to be associated to opposite gender], [Probability of P9 to be associated to opposite gender]) > NAME_SEX_THRESHOLD Warning
Table
Feedback report messages (PCOR2)
Sub–edit  Text Type
PCOR2-1 Reported given names are not likely for reported Sex. Warning
Table
Revision (PCOR2)
Year Description
2004 Edit removed: Edit formerly known as Correlation Edit No.2 has been removed.
Edit added: Current edit was not documented before.

PCOR3

Purpose

This edit ensures that first given name, second given name and third given name are used coherently.

Table
Referenced fields (PCOR3)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P7 15 First given name PGNAME_1
P8 15 Second given name PGNAME_2
P9 7 Third given name PGNAME_3

Business rules

For Add and Update Patient records
  • If First given name is blank then Second given name and Third given name must be blank.
  • If Second given name is blank then Third given name must be blank.
Table
Edit logic (PCOR3)
Sub–edit  Conditions Outcome
PCOR3-1 P4 IN ['1', '2'] AND P7 IS NULL AND (P8 IS NOT NULL OR P9 IS NOT NULL) Record rejected
PCOR3-2 P4 IN ['1', '2'] AND P8 IS NULL AND P9 IS NOT NULL Record rejected
Table
Feedback report messages (PCOR3)
Sub–edit  Text Type
PCOR3-1 First given name is missing. Core error
PCOR3-2 Second given name is missing. Core error
Table
Revision (PCOR3)
Year Description
2004 Edit renamed: Current edit was formerly known as Correlation Edit No.3.

PCOR4

Purpose

This edit ensures that type of current surname code accurately reflects the content of the current surname field.

Table
Referenced fields (PCOR4)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P5 1 Type of current surname PTYP_CUR
P6 25 Current surname PCURSNAM

Business rules

For Add and Update Patient records
  • If Type of Current surname is 'Current Surname unknown' (0) then Current surname must be blank.
  • If Current surname is blank then Type of Current surname must be 'Current surname unknown' (0).
Table
Edit logic (PCOR4)
Sub–edit  Conditions Outcome
PCOR4-1 P4 IN ['1', '2'] AND ((P5 = '0' AND P6 IS NOT NULL) OR (P6 IS NULL AND P5 <> '0')) Record rejected
Table
Feedback report messages (PCOR4)
Sub–edit  Text Type
PCOR4-1 Type of current surname and Current surname do not agree. Core error
Table
Revision (PCOR4)
Year Description
2004 Edit renamed: Current edit was formerly known as Correlation Edit No.4.

PCOR5

Purpose

This edit ensures that birth surname and current surname are consistent with type of current surname.

Table
Referenced fields (PCOR5)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P5 1 Type of Current surname PTYP_CUR
P6 25 Current surname PCURSNAM
P13 25 Birth surname PBIRNAM

Business rules

For Add and Update Patient records
  • If Type of Current surname is 'Birth surname' then Current surname and Birth surname must be the same.
Table
Edit logic (PCOR5)
Sub–edit  Conditions Outcome
PCOR5-1 P4 IN ['1', '2'] AND P5 = '1' AND P6 <> P13 Record rejected
Table
Feedback report messages (PCOR5)
Sub–edit  Text Type
PCOR5-1 Current surname and Birth surname are different while Type of current surname indicates that they should be the same. Core error
Table
Revision (PCOR5)
Year Description
2004 Edit renamed: Current edit was formerly known as Correlation Edit No.5.

PCOR6

Purpose

This edit ensures that at least one surname is reported, either the current surname or the birth surname.

Table
Referenced fields (PCOR6)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P6 25 Current surname PCURSNAM
P13 25 Birth surname PBIRNAM

Business rules

For Add and Update Patient records
  • Current surname and Birth surname cannot both be blank.
Table
Edit logic (PCOR6)
Sub–edit  Conditions Outcome
PCOR6-1 P4 IN ['1', '2'] AND P6 IS NULL AND P13 IS NULL Record rejected
Table
Feedback report messages (PCOR6)
Sub–edit  Text Type
PCOR6-1 Current surname and Birth surname cannot both be blank. Core error
Table
Revision (PCOR6)
Year Description
2004 Edit renamed: Current edit was formerly known as Correlation Edit No.6.

PCOR7

Purpose

This edit ensures that date of birth and date of death respect a chronological sequence and time frame.

Table
Referenced fields (PCOR7)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P11 8 Date of birth PDATBIR
P11.YEAR 4 First 4 characters of P11 (year of date of birth) Not applicable
P11.MONTH 2 5th and 6th characters of P11 (month of date of birth) Not applicable
P11.DAY 2 7th and 8th characters of P11 (day of date of birth) Not applicable
P14 8 Date of death PDATDEA
P14.YEAR 4 First 4 characters of P14 (year of date of death) Not applicable
P14.MONTH 2 5th and 6th characters of P14 (month of date of death) Not applicable
P14.DAY 2 7th and 8th characters of P14 (day of date of death) Not applicable
P19 8 Date of transmission PDATTRAN

Business rules

For Add and Update Patient records
  • If Date of birth and Date of death are at least partially known then
    • Date of death must be on or after Date of birth;
    • Year of Date of death and year of Date of birth should not be more than 110 years apart.
  • If Date of birth is at least partially known and the patient is not known to have died then
    • Year of Date of birth and year of Date of transmission should not be more than 110 years apart.
Table
Edit logic (PCOR7)
Sub–edit  Conditions Outcome
PCOR7-1 P4 IN ['1', '2'] AND P11 <> '99999999' AND P14 NOT IN ['00000000', '99999999'] AND ((P11.DAY <> '99' AND P14.DAY <> '99' AND P14 < P11) OR (P11.MONTH <> '99' AND P14.MONTH <> '99' AND P14.YEAR || P14.MONTH < P11.YEAR || P11.MONTH) OR (P14.YEAR < P11.YEAR)) Record rejected
PCOR7-2 P4 IN ['1', '2'] AND P11 <> '99999999' AND ((P14 NOT IN ['00000000', '99999999'] AND P14.YEAR – P11.YEAR > 110) OR (P14 = '00000000' AND P19.YEAR – P11.YEAR > 110)) Warning
Table
Feedback report messages (PCOR7)
Sub–edit  Text Type
PCOR7-1 Date of death is before Date of birth. Core error
PCOR7-2 The patient is more than 110 years old. Warning
Table
Revision (PCOR7)
Year Description
2004 Edit renamed: Current edit was formerly known as Correlation Edit No.7.
Business rules added: Special handling for patients over 110 years old.

PCOR8

Purpose

This edit ensures that death-related variables present a consistent reporting of the patient's vital status.

Table
Referenced fields (PCOR8)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P14 8 Date of death PDATDEA
P15 3 Province/territory or country of death PPROVDEA
P16 6 Death registration number PDEAREG
P17 4 Underlying cause of death PCAUSDEA
P18 1 Autopsy confirming cause of death PAUTOPSY

Business rules

For Add and Update Patient records
  • If any of the death-related variables (Date of death, Province/territory or country of death, Death registration number, Underlying cause of death and Autopsy confirming cause of death) indicate that the patient is deceased then no variables should indicate that the patient is not known to have died.
Table
Edit logic (PCOR8)
Sub–edit  Conditions Outcome
PCOR8-1 P4 IN ['1', '2'] AND (P14 <> '00000000' OR P15 <> '000' OR P16 <> '000000' OR P17 <> '0000' OR P18 <> '0') AND (P14 = '00000000' OR P15 = '000' OR P16 = '000000' OR P17 = '0000' OR P18 = '0') Record rejected
Table
Feedback report messages (PCOR8)
Sub–edit  Text Type
PCOR8-1 Some death-related variables indicate that the patient is deceased whereas at least another indicates that the patient is not known to have died. Core error
Table
Revision (PCOR8)
Year Description
2004 Edit removed: Edit formerly known as Correlation Edit No.8 was redundant with PVAL11.
Edit renamed: Current edit was formerly known as Correlation Edit No.10.

PCOR9

Purpose

This edit ensures that death registration number and province/territory or country of death are consistent.

Table
Referenced fields (PCOR9)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P15 3 Province/territory or country of death PPROVDEA
P16 6 Death registration number PDEAREG

Business rules

For Add and Update Patient records
  • If Death registration number is known then Province/territory or country of death must indicate a specific location in Canada or United States of America.
  • If Death registration number indicated that the Patient died outside Canada then Province/territory or country of death must indicate a foreign country or unknown place.
  • If Death registration number is unknown then Province/territory or country of death must be either a location in Canada or an unknown place.
Table
Edit logic (PCOR9)
Sub–edit  Conditions Outcome
PCOR9-1 P4 IN ['1', '2'] AND P16 IN [000001-999997] AND P15 NOT IN [840, 910, 911, 912, 913, 924, 935, 946, 947, 948, 959, 960, 961, 962] Record rejected
PCOR9-2 P4 IN ['1', '2'] AND P16 = '999998' AND P15 IN [909, 910, 911, 912, 913, 924, 935, 946, 947, 948, 959, 960, 961, 962] Record rejected
PCOR9-3 P4 IN ['1', '2'] AND P16 = '999999' AND P15 NOT IN [909, 910, 911, 912, 913, 924, 935, 946, 947, 948, 959, 960, 961, 962, 999] Record rejected
Table
Feedback report messages (PCOR9)
Sub–edit  Text Type
PCOR9-1 If Death registration number is known then province/territory or country of death must indicate a specific location in Canada or United States of America. Core error
PCOR9-2 If Death registration number indicated that the patient died outside Canada then province/territory or country of death must indicate a foreign country or unknown place. Core error
PCOR9-3 If Death registration number is unknown then province/territory or country of death must be either a location in Canada or an unknown place. Core error
Table
Revision (PCOR9)
Year Description
2004 Edit reorganized: Edit formerly known as Correlation Edit No.9 merged with PVAL14.
Edit renamed: Current edit was formerly known as Correlation Edit No.11.
Business rules changed: If Death registration number is known then province/territory or country of death must indicate a specific location in Canada or United States of America; If Death registration number is unknown then province/territory or country of death must be either a location in Canada or an unknown place.
Business rules added: If Death registration number indicated that the patient died outside Canada then province/territory or country of death must indicate a foreign country or unknown place.

PCOR10

Purpose

This edit ensures death registration number and date of death are consistent.

Table
Referenced fields (PCOR10)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P14 8 Date of death PDATDEA
P16 6 Death registration number PDEAREG

Business rules

For Add and Update Patient records
  • If Death registration number is known then Date of death must be at least partially known.
Table
Edit logic (PCOR10)
Sub–edit  Conditions Outcome
PCOR10-1 P4 IN ['1', '2'] AND P16 IN [000001-999997] AND P14.YEAR = '9999' Record rejected
Table
Feedback report messages (PCOR10)
Sub–edit  Text Type
PCOR10-1 Date of death cannot be unknown if Death registration number is known. Core error
Table
Revision (PCOR10)
Year Description
2004 Edit reorganized: Edit formerly known as Correlation Edit No.10 moved to PCOR8.
Edit added: New edit.

PCOR11

Purpose

This edit ensures death registration number and underlying cause of death are consistent.

Table
Referenced fields (PCOR11)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P16 6 Death registration number PDEAREG
P17 3 Underlying cause of death PCAUSDEA

Business rules

For Add and Update Patient records
  • If Death registration number is unknown then Underlying cause of death cannot be 'Officially unknown'.
Table
Edit logic (PCOR11)
Sub–edit  Conditions Outcome
PCOR11-1 P4 IN ['1', '2'] AND P16 = '999999' AND P17 IN = ['R99', '7999'] Record rejected
Table
Feedback report messages (PCOR11)
Sub–edit  Text Type
PCOR11-1 Underlying cause of death cannot be 'Officially unknown' when Death registration is unknown. Core error
Table
Revision (PCOR11)
Year Description
2004 Edit reorganized: Edit formerly known as Correlation Edit No.11 moved to PCOR9.
Edit added: New edit.

3.5.2 Tumour correlation edits

The following table summarizes the purpose of each individual edit of this category.

Table 27
Tumour correlation edits summary
Edit name Purpose
TCOR1 Ensures that the content of the core tumour fields is consistent with the operation described in the Tumour record type.
TCOR2 Ensures that Postal code and Standard geographic code are coherent.
TCOR3 Ensures that Census tract and Standard geographic code are coherent.
TCOR4 Rejects tumour data for patients living outside the reporting province/territory at time of diagnosis.
TCOR5 Ensures that expected topography, histology and behaviour values are reported based on the Source classification flag.
TCOR6 Ensures the consistency between ICD-9 Cancer code and related ICD-O-2 values.
TCOR7 Ensures the consistency between related ICD-O-2 and ICD-O-3 values.
TCOR8 Not applicable. (Placeholder for future requirement implementation.)
TCOR9 Rejects tumour records that are outside the CCR core scope.
TCOR10 Ensures that invalid combinations of topography and histology are rejected.
TCOR11 Ensures that invalid combinations of histology and behaviour codes are rejected.
TCOR12 Ensures the consistency between the topography and the laterality.
TCOR13 Ensures that invalid combinations of Method used to establish the date of diagnosis and Diagnostic confirmation codes are rejected.
TCOR14 Ensures that Method of diagnosis is only reported for tumours diagnosed prior to 2004.
TCOR15 Ensures that Method used to establish the date of diagnosis is only reported for tumours diagnosed in 2004 and onwards.
TCOR16 Ensures that Diagnostic confirmation is only reported for tumours diagnosed in 2004 and onwards.
TCOR17 Ensures that Grade, differentiation or cell indicator is only reported for tumours diagnosed in 2004 and onwards.
TCOR18 This edit ensures that Collaborative Staging variables are reported for tumours within the CCR collaborative staging scope.
TCOR19 This edit ensures that AJCC TNM staging variables are reported for tumours within the CCR AJCC TNM staging scope.
TCOR20 Ensures that TNM stage group is reported only when clinical and pathologic TNM stage group are not reported.
TCOR21 Ensures that the combination of AJCC clinical TNM stage group and individual clinical T, N, M values is acceptable.
TCOR22 Ensures that the combination of AJCC pathologic TNM stage group and the individual pathologic T, N, M values is acceptable.
TCOR23 Ensures that the combination of AJCC TNM stage group and the individual clinical/pathologic T, N, M values is acceptable.
TCOR24 Ensures that AJCC edition number is coherent with all remaining AJCC TNM staging variables.
TCOR26 Ensures the consistency between Ambiguous terminology diagnosis and Date of conclusive diagnosis.
TCOR27 Ensures the consistency between Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter.
TCOR29 Ensures the consistency between Ambiguous terminology diagnosis and Date of Conclusive Diagnosis.
TCOR30 Ensures that date of diagnosis and date of conclusive diagnosis respect a chronological sequence and time frame.
TCOR31 Ensures the consistency between ICD-O-2/3 Topography and Type of multiple tumours reported as one primary.
TCOR32 Ensures the consistency between ICD-O-3 Behaviour and Multiple tumours reported as one primary.
TCOR33 Ensures the consistency between Type of Multiple Tumours Reported as One Primary, ICD-O-2/3 Topography and ICD-O-3 Histology.
TCOR34 Ensures the consistency between Date of multiple tumours and Type of multiple tumours reported as one primary.
TCOR35 Ensures the consistency between Method Used to Establish the Date of Diagnosis, Type of Multiple Tumours Reported as One Primary, Date of Multiple Tumours and Multiplicity Counter.
TCOR36 Ensures the consistency between Date of diagnosis and Grade path value and Grade path system.
TCOR37 Ensures the consistency between Grade path value and Grade path system.
TCOR38 Ensures the consistency between CS mets at dx and CS mets at dx - bone, CS mets at dx and CS mets at dx - brain, CS mets at dx and CS mets at dx - liver, CS mets at dx and CS mets at dx - lung.

TCOR1

Purpose

This edit ensures that the content of the core tumour fields is consistent with the operation described in the tumour record type.

Table
Referenced fields (TCOR1)
Field Length Description Acronym
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Tumour patient identification number TPIN
T3 9 Tumour reference number TTRN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
T6 25 Name of place of residence TPLACRES
T7 6 Postal code TPOSTCOD
T8 7 Standard geographic code TCODPLAC
T9 9 Census tract TCENTRAC
T10 15 Health insurance number THIN
T11 1 Method of diagnosis TMETHDIAG
T12 8 Date of diagnosis TDATDIAG
T12.YEAR 4 First 4 digist of T12 (year of date of diagnosis Not applicable
T13 4 ICD–9 Cancer code TICD_9
T14 1 Source classification flag TSCF
T15 4 ICD–O–2/3 Topography TICD_O2T
T16 4 ICD–O–2 Histology TICD_O2H
T17 1 ICD–O–2 Behaviour TICD_O2B
T19 1 Laterality TLATERAL
T21 4 ICD–O–3 Histology TICD_O3H
T22 1 ICD–O–3 Behaviour TICD_03B
T23 1 Grade, differentiation or cell indicator TGRADE
T24 2 Method used to establish the date of diagnosis TMETHUSED
T25 2 Diagnostic confirmation TMETHCONF
T27 3 CS tumour size TCSTSIZE
T28 3 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 3 CS lymph nodes TCSLNODE
T31 1 CS lymph nodes eval TCSLNEVAL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at diagnosis TCSMDIAG
T35 1 CS mets evaluation TCSMEVAL
T36 3 CS site–specific factor 1 TCSSSF1
T37 3 CS site–specific factor 2 TCSSSF2
T38 3 CS site–specific factor 3 TCSSSF3
T39 3 CS site–specific factor 4 TCSSSF4
T40 3 CS site–specific factor 5 TCSSSF5
T41 3 CS site–specific factor 6 TCSSSF6
T42 9 AJCCclinical T TAJCCCLINT
T43 3 AJCC clinical N TAJCCCLINN
T44 3 AJCC clinical M TAJCCCLINM
T45 9 AJCC pathologic T TAJCCPATHT
T46 6 AJCC pathologic N TAJCCPATHN
T47 3 AJCC pathologic M TAJCCPATHM
T48 4 AJCC clinical TNM stage group TAJCCCLINSG
T49 4 AJCC pathologic TNM stage group TAJCCPATHSG
T50 4 AJCC TNM stage group TAJCCSG
T51 2 AJCC TNM edition number TAJCCEDNUM
T52 6 CS version input original TCSVERINORIG
T53 1 Ambiguous terminology diagnosis TAMBIGTERM
T54 8 Date of conclusive diagnosis TDATCONCLUSDIAG
T55 2 Type of multiple tumours reported as one primary TMULTTUMONEPRIM
T56 8 Date of multiple tumours TDATMULT
T57 2 Multiplicity counter TMULTCOUNT
T58 2 Date of diagnosis flag TDATDIAGFLAG
T59 2 Date of conclusive diagnosis flag TDATCONCLUSDIAGFLAG
T60 2 Date of multiple tumours flag TDATMULTFLAG
T61 1 Grade path value TGRADEPATHVAL
T62 1 Grade path system TGRADEPATHSYS
T63 1 Lymph-vascular invasion TLYMPHVASINV
T64 6 CS version input current TCSVERINCUR
T65 3 CS site-specific factor 7 TCSSSF7
T66 3 CS site-specific factor 8 TCSSSF8
T67 3 CS site-specific factor 9 TCSSSF9
T68 3 CS site-specific factor 10 TCSSSF10
T69 3 CS site-specific factor 11 TCSSSF11
T70 3 CS site-specific factor 12 TCSSSF12
T71 3 CS site-specific factor 13 TCSSSF13
T72 3 CS site-specific factor 14 TCSSSF14
T73 3 CS site-specific factor 15 TCSSSF15
T74 3 CS site-specific factor 16 TCSSSF16
T75 3 CS site-specific factor 17 TCSSSF17
T76 3 CS site-specific factor 18 TCSSSF18
T77 3 CS site-specific factor 19 TCSSSF19
T78 3 CS site-specific factor 20 TCSSSF20
T79 3 CS site-specific factor 21 TCSSSF21
T80 3 CS site-specific factor 22 TCSSSF22
T81 3 CS site-specific factor 23 TCSSSF23
T82 3 CS site-specific factor 24 TCSSSF24
T83 3 CS site-specific factor 25 TCSSSF25
T84 1 CS Mets at Dx - Bone TCSMDXBONE
T85 1 CS Mets at Dx - Brain TCSMDXBRAIN
T86 1 CS Mets at Dx - Liver TCSMDXLIVER
T87 1 CS Mets at Dx - Lung TCSMDXLUNG

Business rules

For Add Tumour records
  • Tumour reporting province/territory, Tumour patient identification number, Tumour reference number, Postal code, Standard geographic code, Method of diagnosis, Date of diagnosis, ICD-9 cancer code, Source classification flag, ICD-O-2/3 Topography, ICD-O-2 Histology, ICD-O-2 Behaviour, Laterality, ICD-O-3 Histology, ICD-O-3 Behaviour, Grade, differentiation or cell indicator, Method used to establish the date of diagnosis, Diagnostic confirmation must be provided39.
  • Fillers (T18 and T20) are ignored.
For Update Tumour records
  • Tumour reporting province/territory, Tumour patient identification number, Tumour reference number, CCR identification number, Postal code, Standard geographic code, Method of diagnosis, Date of diagnosis, ICD-9 cancer code, Source classification flag, ICD-O-2/3 Topography, ICD-O-2 Histology, ICD-O-2 Behaviour, Laterality, ICD-O-3 Histology, ICD-O-3 Behaviour, Grade, differentiation or cell indicator, Method used to establish the date of diagnosis, Diagnostic confirmation must be provided39.
  • Fillers (T18 and T20) are ignored.
For Delete Tumour records
  • Tumour reporting province/territory, Tumour patient identification number, Tumour reference number and CCR identification number must be provided.
  • Name of place of residence, Postal code, Standard geographic code, Census tract, Health insurance number, Method of diagnosis, Date of diagnosis, ICD-9 cancer code, Source classification flag, ICD-O-2/3 Topography, ICD-O-2 Histology, ICD-O-2 Behaviour, Laterality, ICD-O-3 Histology, ICD-O-3 Behaviour, Grade, differentiation or cell indicator, Method used to establish the date of diagnosis, Diagnostic confirmation, CS tumour size, CS extension, CS tumour size/ext eval, CS lymph nodes, CS lymph nodes eval, Regional nodes examined, Regional nodes positive, CS mets at dx, CS mets eval, CS site-specific factor 1, CS site-specific factor 2, CS site-specific factor 3, CS site-specific factor 4, CS site-specific factor 5, CS site-specific factor 6, AJCC clinical T, AJCC clinical N, AJCC clinical M, AJCC pathologic T, AJCC pathologic N, AJCC pathologic M, AJCC clinical TNM stage group, AJCC pathologic TNM stage group, AJCC TNM stage group, AJCC edition number, CS version input original, Ambiguous Terminology Diagnosis, Date of conclusive diagnosis, Type of multiple tumours reported as one primary, Date of multiple tumours, and Multiplicity Counter, Date of diagnosis flag, Date of conclusive diagnosis flag,  Date of multiple tumours flag, Grade path value, Grade path system, Lymph-vascular invasion, CS site-specific factors 7 – 25, CS Mets at Dx – Bone, CS Mets at Dx – Brain, CS Mets at Dx – Liver, CS Mets at Dx – Lung must be blank.
  • Fillers (T18 and T20) are ignored.
Table
Edit logic (TCOR1)
Sub–edit  Conditions Outcome
TCOR1-1 T5 = '1' AND (T1 IS NULL OR T2 IS NULL OR T3 IS NULL OR T7 IS NULL OR T8 IS NULL OR T11 IS NULL OR T12 IS NULL OR T13 IS NULL OR T14 IS NULL OR T15 IS NULL OR T16 IS NULL OR T17 IS NULL OR T19 IS NULL OR T21 IS NULL OR T22 IS NULL OR T23 IS NULL OR T24 IS NULL OR T25 IS NULL) OR (T12 IS NOT NULL AND T12.YEAR < 2006 AND T9 IS NULL)) Record rejected
TCOR1-2 T5 = '2' AND (T1 IS NULL OR T2 IS NULL OR T3 IS NULL OR T4 IS NULL OR T7 IS NULL OR T8 IS NULL OR T11 IS NULL OR T12 IS NULL OR T13 IS NULL OR T14 IS NULL OR T15 IS NULL OR T16 IS NULL OR T17 IS NULL OR T19 IS NULL OR T21 IS NULL OR T22 IS NULL OR T23 IS NULL OR T24 IS NULL OR T25 IS NULL) OR (T12 IS NOT NULL AND T12.YEAR < 2006 AND T9 IS NULL) Record rejected
TCOR1-3 T5 = '3' AND (T1 IS NULL OR T2 IS NULL OR T3 IS NULL OR T4 IS NULL OR T6 IS NOT NULL OR T7 IS NOT NULL OR T8 IS NOT NULL OR T9 IS NOT NULL OR T10 IS NOT NULL OR T11 IS NOT NULL OR T12 IS NOT NULL OR T13 IS NOT NULL OR T14 IS NOT NULL OR T15 IS NOT NULL OR T16 IS NOT NULL OR T17 IS NOT NULL OR T19 IS NOT NULL OR T21 IS NOT NULL OR T22 IS NOT NULL OR T23 IS NOT NULL OR T24 IS NOT NULL OR T25 IS NOT NULL OR T27 IS NOT NULL OR T28 IS NOT NULL OR T29 IS NOT NULL OR T30 IS NOT NULL OR T31 IS NOT NULL OR T32 IS NOT NULL OR T33 IS NOT NULL OR T34 IS NOT NULL OR T35 IS NOT NULL OR T36 IS NOT NULL OR T37 IS NOT NULL OR T38 IS NOT NULL OR T39 IS NOT NULL OR T40 IS NOT NULL OR T41 IS NOT NULL OR T42 IS NOT NULL OR T43 IS NOT NULL OR T44 IS NOT NULL OR T45 IS NOT NULL OR T46 IS NOT NULL OR T47 IS NOT NULL OR T48 IS NOT NULL OR T49 IS NOT NULL OR T50 IS NOT NULL OR T51 IS NOT NULL OR T52 IS NOT NULL OR T53 IS NOT NULL OR T54 IS NOT NULL OR T55 IS NOT NULL OR T56 IS NOT NULL OR T57 IS NOT NULLOR T58 IS NOT NULL OR T59 IS NOT NULL OR T60 IS NOT NULL OR T61 IS NOT NULL OR T62 IS NOT NULL OR T63 IS NOT NULL OR T64 IS NOT NULL OR T65 IS NOT NULL OR T66 IS NOT NULL OR T67 IS NOT NULL OR T68 IS NOT NULL OR T69 IS NOT NULL OR T70 IS NOT NULL OR T71 IS NOT NULL OR T72 IS NOT NULL OR T73 IS NOT NULL OR T74 IS NOT NULL OR T75 IS NOT NULL OR T76 IS NOT NULL OR T77 IS NOT NULL OR T78 IS NOT NULL OR T79 IS NOT NULL OR T80 IS NOT NULL OR T81 IS NOT NULL OR T82 IS NOT NULL OR T83 IS NOT NULL OR T84 IS NOT NULL OR T85 IS NOT NULL OR T86 IS NOT NULL OR T87 IS NOT NULL) Record rejected
Table
Feedback report messages (TCOR1)
Sub–edit  Text Type
TCOR1-1 Input record does not respect the Add Tumour record format. There are missing values. Core fatal error
TCOR1-2 Input record does not respect the Update Tumour record format. There are missing values. Core fatal error
TCOR1-3 Input record does not respect the Delete Tumour record format. There are missing or extra values. Core fatal error
Table
Revision (TCOR1)
Year Description
2010 Business rules and Edit logic changed: Fields T58 to T87 added. Variable name changes T31 - CS lymph nodes eval (CS reg nodes eval), and T52 - CS version input original (CS version 1st). The length of variables T24, T25, T28 and T30 has changed. The length of variables Method used to establish date of diagnosis, Diagnostic confirmation, CS extension and CS lymph nodes has changed.
2008 Business rules and Edit logic changed: Fields T53 to T57 have been added.
2007 Business rules and Edit logic changed: Field T52 has been added.
2006 Business rules and Edit logic changed: Census tract effective date range ended in 2005. For cases diagnosed in 2006 and onwards, T9 (Census tract) must not be reported.
2004 Edit renamed: Edit formerly known as Correlation Edit No.12.
Business rules changed: Handle new fields related to Collaborative staging and TNM data.

TCOR2

Purpose

This edit ensures that postal code and standard geographic code are coherent.

Table
Referenced fields (TCOR2)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T7 6 Postal code TPOSTCOD
T7.FIRST 1 First digit of Postal code Not applicable
T8.PROV 2 First 2 digits of T8 (province code of Standard geographic code) Not applicable

Business rules

For Add and Update Tumour records, if Postal code is known then
  • it must start with 'A' if in Newfoundland or Labrador;
  • it must start with 'B' if in Nova Scotia;
  • it must start with 'C' if in Prince Edward Island;
  • it must start with 'E' if in New Brunswick;
  • it must start with 'G', 'H', 'J' or 'K' if in Quebec;
  • it must start with 'K', 'L', 'M', 'N' or 'P' if in Ontario;
  • it must start with 'R' if in Manitoba;
  • it must start with 'R' or 'S' if in Saskatchewan;
  • it must start with 'S' or 'T' if in Alberta;
  • it must start with 'V' if in British Columbia;
  • it must start with 'Y' if in Yukon;
  • it must start with 'X' if in Northwest Territories;
  • it must start with 'X' if in Nunavut.
Table
Edit logic (TCOR2)
Sub–edit  Conditions Outcome
TCOR2-1 T5 IN ['1', '2'] AND T7 <> '999999' AND ((T8.PROV = '10' AND T7.FIRST <> 'A') OR (T8.PROV = '11' AND T7.FIRST <> 'C') OR (T8.PROV = '12' AND T7.FIRST <> 'B') OR (T8.PROV = '13' AND T7.FIRST <> 'E') OR (T8.PROV = '24' AND T7.FIRST NOT IN ['G', 'H', 'J', 'K']) OR (T8.PROV = '35' AND T7.FIRST NOT IN ['K', 'L', 'M', 'N', 'P']) OR (T8.PROV = '46' AND T7.FIRST <> 'R') OR (T8.PROV = '47' AND T7.FIRST NOT IN ['R', 'S']) OR (T8.PROV = '48' AND T7.FIRST NOT IN ['S', 'T']) OR (T8.PROV = '59' AND T7.FIRST <> 'V') OR (T8.PROV = '60' AND T7.FIRST <> 'Y') OR (T8.PROV = '61' AND T7.FIRST <> 'X') OR (T8.PROV = '62' AND T7.FIRST <> 'X')) Record rejected
Table
Feedback report messages (TCOR2)
Sub–edit  Text Type
TCOR2-1 Postal code and Standard geographic code indicate 2 different provinces/territories. Core error
Table
Revision (TCOR2)
Year Description
2004 Edit renamed: Edit formerly known as Correlation Edit No.14.

TCOR3

Purpose

This edit ensures that census tract and standard geographic code are coherent.

Table
Referenced fields (TCOR3)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T8 7 Standard geographic code TCODPLAC
T9 9 Census tract TCENTRAC
T12.YEAR 4 First 4 characters of T12 (year of the Date of diagnosis) Not applicable

Business rules

For Add and Update Tumour records
  • If Date of diagnosis is between year 1992 and 1995 inclusively, and both Census tract and Standard geographic code are fully known, then the reported Standard geographic code must match the Standard geographic code associated with the Census tract in Eligible Census tracts from 1992 to 199512 .
  • If Date of diagnosis is between year 1996 and 2000 inclusively, and both Census tract and Standard geographic code are fully known, then the reported Standard geographic code must match the Standard geographic code associated with the Census tract in Eligible Census tracts from 1996 to 200012.
  • If Date of diagnosis is between year 2001 and 2005 inclusively, and both Census tract and Standard geographic code are fully known, then the reported Standard geographic code must match the Standard geographic code associated with the Census tract in Eligible Census tracts from 2001 to 200512.
Table
Edit logic (TCOR3)
Sub–edit  Conditions Outcome
TCOR3-1 T5 IN ['1', '2'] AND T8 NOT LIKE '_ _ _ _ 999' AND T9 NOT LIKE '___999.99' AND T12.YEAR >= 1992 AND T12.YEAR < 1996 AND T8 NOT IN [SGC from Eligible Census tracts from 1992 to 1995 where Census tract = T9] Record rejected
TCOR3-2 T5 IN ['1', '2'] AND T8 NOT LIKE '_ _ _ _ 999' AND T9 NOT LIKE '___999.99' AND T12.YEAR >= 1996 AND T12.YEAR < 2001 AND T8 NOT IN [SGC from Eligible Census tracts from 1996 to 2000 where Census tract = T9] Record rejected
TCOR3-3 T5 IN ['1', '2'] AND T8 NOT LIKE '_ _ _ _ 999' AND T9 NOT LIKE '___999.99' AND T12.YEAR >= 2001 AND T12.YEAR < 2005 AND T8 NOT IN [SGC from Eligible Census tracts from 2001 to 2005 where Census tract = T9] Record rejected
Table
Feedback report messages (TCOR3)
Sub–edit  Text Type
TCOR3-1 Census tract and Standard geographic code combination not found in Census tract Data dictionary – 1991. Core error
TCOR3-2 Census tract and Standard geographic code combination not found in Census tract Data dictionary – 1996. Core error
TCOR3-3 Census tract and Standard geographic code combination not found in Census tract Data dictionary – 2001. Core error
Table
Revision (TCOR3)
Year Description
2006 Business rules and Edit logic changed: Edit modified to include combinations where Census tract indicate an area outside a Census Metropolitan Area.
2004 Edit renamed: Edit formerly known as Correlation Edit No.15

TCOR4

Purpose

This edit rejects tumour data for patients living outside the reporting province/territory at time of diagnosis.

Table
Referenced fields (TCOR4)
Field Length Description Acronym
T1 2 Tumour reporting province/territory TREPPROV
T5 1 Tumour record type TRECTYPE
T8.PROV 2 First 2 characters from T8 (province code of Standard geographic code) Not applicable

Business rules

For Add and Update Tumour records
  • Tumour reporting province/territory must be equal to province code found in Standard geographic code.
Table
Edit logic (TCOR4)
Sub–edit  Conditions Outcome
TCOR4-1 T5 IN ['1', '2'] AND T1 <> T8.PROV Record rejected
Table
Feedback report messages (TCOR4)
Sub–edit  Text Type
TCOR4-1 Reporting province/territory and Standard geographic code must indicate the same province/territory. Core error
Table
Revision (TCOR4)
Year Description
2004 Edit renamed: Edit formerly known as Correlation Edit No.16.

TCOR5

Purpose

This edit ensures that expected topography, histology and behaviour values are reported based on the Source classification flag.

Table
Referenced fields (TCOR5)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T13 4 ICD-9 cancer code TICD_9
T14 1 Source classification flag TSCF
T16 4 ICD-O-2 Histology TICD_O2H
T17 1 ICD-O-2 Behaviour TICD_O2B

Business rules

For Add and Update Tumour records
  • If Source classification Flag indicates that ICD-9 is the Source classification then ICD-9 cancer code, ICD-O-2/3 Topography40, ICD-O-2 Histology, ICD-O-2 Behaviour41, ICD-O-3 Histology42 and ICD-O-3 Behaviour41 must be reported.
  • If Source classification flag indicates that ICD-O-2 is the Source classification then ICD-O-2/3 Topography40, ICD–O–2 Histology, ICD-O-2 Behaviour41, ICD-O-3 Histology42 and ICD-O-3 Behaviour41 must be reported and ICD-9 Cancer code must not be reported.
  • If Source classification flag indicates that ICD-O-3 is the Source classification then ICD-O-2/3 Topography42, ICD-O-3 Histology40 and ICD-O-3 Behaviour41 must be reported and ICD-9 cancer code, ICD-O-2 Histology and ICD-O-2 Behaviour must not be reported.
Table
Edit logic (TCOR5)
Sub–edit  Conditions Outcome
TCOR5-1 T5 IN ['1', '2'] AND T14 = '1' AND (T13 = '0000' OR T16 = '0000') Record rejected
TCOR5-2 T5 IN ['1', '2'] AND T14 = '2' AND T16 = '0000' Record rejected
TCOR5-3 T5 IN ['1', '2'] AND T14 = '2' AND T13 <> '0000' Record rejected
TCOR5-4 T5 IN ['1', '2'] AND T14 = '4' AND (T13 <> '0000' OR T16 <> '0000' OR T17 <> '0') Record rejected
Table
Feedback report messages (TCOR5)
Sub–edit  Text Type
TCOR5-1 Based on the Source classification flag, ICD-9 Cancer code and ICD-O-2 Histology must be reported. Core Error
TCOR5-2 Based on the Source classification flag, ICD-O-2 Histology must be reported. Core Error
TCOR5-3 Based on the Source classification flag, ICD-9 Cancer code must not be reported. Core Error
TCOR5-4 Based on the Source classification flag, ICD-9 cancer code, ICD-O-2 Histology and ICD-O-2 Behaviour must not be reported. Core Error
Table
Revision (TCOR5)
Year Description
2004 Edit renamed: Edit formerly known as Correlation Edit No.18.
Business rules deleted: ICD-10 related rules dropped.
Business rules changed: Ensure that topography and histology are reported in accordance with the Source classification flag.
Business rules added: Prevent the reporting of data using a classification older than the one indicated by the Source classification flag.

TCOR6

Purpose

This edit ensures the consistency between ICD-9 Cancer code and related ICD-O-2 values.

Table
Referenced fields (TCOR6)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T13 4 ICD-9 cancer code TICD_9
T14 1 Source classification flag TSCF
T15 4 ICD-O-2/3 Topography TICD_O2T
T16 4 ICD-O-2 Histology TICD_O2H
T17 1 ICD-O-2 Behaviour TICD_O2B

Business rules

For Add and Update Tumour records where the source classification is ICD-9
  • ICD-9 Cancer code and ICD-O-2/3 Topography must match based on ICD-9 to ICD-O-2 conversion table43.
  • If ICD-9 Cancer code is related to a specific histology code (different than 8000) based on ICD-9 to ICD-O-2 conversion table then reported ICD-O-2 Histology should not be generic (equal to 8000).
  • ICD-9 Cancer code and ICD-O-2 Behaviour must be coherent based on ICD-9 to ICD-O-2 conversion table.
Table
Edit logic (TCOR6)
Sub–edit  Conditions Outcome
TCOR6-1 T5 IN ['1', '2'] AND T14 = '1' AND T13 <> '0000' AND (T13 and T15 NOT IN [ICD-9 to ICD-O-2 conversion table]) Record Rejected
TCOR6-2 T5 IN ['1', '2'] AND T14 = '1' AND T13 <> '0000' AND T16 = '8000' AND (ICD-O-2 Histology <> '8000' IN [ICD-9 to ICD-O-2 conversion table where ICD-9 = T13]) Warning
TCOR6-3 T5 IN ['1', '2'] AND T14 = '1' AND T13 <> '0000' AND (T13 and T17 NOT IN [ICD-9 to ICD-O-2 conversion table]) Record Rejected
Table
Feedback report messages (TCOR6)
Sub–edit  Text Type
TCOR6-1 ICD-9 Cancer code and ICD-O-2/3 Topography are not coherent. Core Error
TCOR6-2 ICD-O-2 Histology could have been more precise based on ICD-9 cancer code. Warning
TCOR6-3 ICD-9 Cancer code and ICD-O-2 Behaviour are not coherent. Core Error
Table
Revision (TCOR6)
Year Description
2004 Edit renamed: Edit formerly known as Correlation Edit No.20
Business rules deleted: ICD-10 related rules dropped.
Business rules added:
Coherence check between ICD-9 Cancer code and ICD-O2/3 Topography added.
Coherence check between ICD-9 Cancer code and ICD-O-2 Histology added.

TCOR7

Purpose

This edit ensures the consistency between related ICD-O-2 and ICD-O-3 values.

Table
Referenced fields (TCOR7)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T14 1 Source classification flag TSCF
T15 4 ICD-O-2/3 Topography TICD_O2T
T16 4 ICD-O-2 Histology TICD_O2H
T17 1 ICD-O-2 Behaviour TICD_O2B
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B

Business rules

For Add and Update Tumour records where the source classification is either ICD-9 or ICD-O-2
  • ICD-O-3 Histology and ICD-O-3 Behaviour combination must be consistent with ICD-O-2/3 Topography, ICD-O-2 Histology and ICD-O-2 Behaviour combination based on ICD-O-2 to ICD-O-3 conversion table44.
Table
Edit logic (TCOR7)
Sub–edit  Conditions Outcome
TCOR7-1 T5 IN ['1', '2'] AND T14 IN ['1', '2'] AND T16 <> '0000' AND (T21 and T22 combination NOT IN [ICD-O-2 to ICD-O-3 conversion table for T15, T16 and T17 combination]) Record rejected
Table
Feedback report messages (TCOR7)
Sub–edit  Text Type
TCOR7-1 ICD-O-3 Histology and ICD-O-3 Behaviour combination is not coherent with ICD-O-2/3 Topography, ICD-O-2 Histology and ICD-O-2 Behaviour combination. Core Error
Table
Revision (TCOR7)
Year Description
2004 Edit added: New edit.

TCOR8

Purpose

Not applicable. (This empty correlation is kept as a placeholder for future requirement implementation.)

Table
Referenced fields (TCOR8)
Field Length Description Acronym
Not applicable Not applicable Not applicable Not applicable

Business rules

Not applicable

Table
Edit logic (TCOR8)
Sub–edit  Conditions Outcome
Not applicable Not applicable Not applicable
Table
Feedback report messages (TCOR8)
Sub–edit  Text Type
Not applicable Not applicable Not applicable
Table
Revision (TCOR8)
Year Description
Not applicable Not applicable

TCOR9

Purpose

This edit rejects tumour records that are outside the CCR core scope.

Table
Referenced fields (TCOR9)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of Date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B

Business rules

For Add and Update Tumour records
  • ICD-O-2/3 Topography, ICD-O-3 Histology, ICD-O-3 Behaviour and year of Date of diagnosis combination must be within the CCR core scope45.
Table
Edit logic (TCOR9)
Sub–edit  Conditions Outcome
TCOR9-1 T5 IN ['1', '2'] AND (T12.YEAR, T15, T21 and T22 NOT IN [CCR core scope]) Record rejected
Table
Feedback report messages (TCOR9)
Sub–edit  Text Type
TCOR9-1 Based on ICD-O-2/3 Topography, ICD-O-3 Histology and Behaviour and Date of diagnosis, the tumour is outside the CCR core scope. Core Error
Table
Revision (TCOR9)
Year Description
2004 Edit consolidated: Edits formerly known as Correlation edit No.13 and Correlation edit No.21.
Business rules changed: Verification is now performed on ICD-O-3 values only, regardless of the source classification used.

TCOR10

Purpose

This edit ensures that invalid combinations of topography and histology are rejected.

Table
Referenced fields (TCOR10)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of Date of diagnosis (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H

Business rules

For Add and Update Tumour records
  • ICD-O-2/3 Topography and ICD-O-3 Histology and year of date of diagnosis combination must not be invalid based on Invalid site and Histology combinations table46.
Table
Edit logic (TCOR10)
Sub–edit  Conditions Outcome
TCOR10-1 T5 IN ['1', '2'] AND (T12.Year, T15 and T21 IN [Invalid site and Histology combinations]) Record rejected
Table
Feedback report messages (TCOR10)
Sub–edit  Text Type
TCOR10-1 ICD-O-2/3 Topography, ICD-O-3 Histology and Date of diagnosis combination is either invalid or not eligible for CCR. Core error
Table
Revision (TCOR10)
Year Description
2007 Referenced fields, Business rules, Edit logic and Feedback report messages changed: Verification now includes Date of diagnosis.
2004 Edit renamed: Edit formerly known as Correlation Edit No.23.
Business rules changed: Verification is now performed on ICD-O-3 values only, regardless of the source classification used.

TCOR11

Purpose

This edit ensures that invalid combinations of histology and behaviour codes are rejected.

Note: Invalid combinations are combinations that are invalid from a subject matter point of view. These are different from matrix combinations which are combinations not explicitly listed in ICD-O but possible from a subject matter point of view and allowed based on rules or coding guidelines for morphology, ICD-O-3, as outlined in the International Classification of Diseases for Oncology, third edition..

Table
Referenced fields (TCOR11)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of Date of diagnosis (year of date of diagnosis) Not applicable
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B

Business rules

For Add and Update Tumour records
  • ICD-O-3 Histology, ICD-O-3 Behaviour and year of date of diagnosis combination must not be invalid based on Invalid Histology and Behaviour combination table47.
Table
Edit logic (TCOR11)
Sub–edit  Conditions Outcome
TCOR11-1 T5 IN ['1', '2'] AND (T12.YEAR, T21 and T22 IN [Invalid Histology and Behaviour combination]) Record rejected
Table
Feedback report messages (TCOR11)
Sub–edit  Text Type
TCOR11-1 ICD-O-3 Histology, ICD-O-3 Behaviour and Date of diagnosis combination is invalid. Core error
Table
Revision (TCOR11)
Year Description
2007 Referenced fields, Business rules, Edit logic and Feedback report messages changed: Verification now includes Date of diagnosis.
2004 Edit renamed: Edit formerly known as Correlation Edit No.24.
Business rules changed: Verification is now performed on ICD-O-3 values only, regardless of the source classification used.

TCOR12

Purpose

This edit ensures the consistency between the topography and the laterality.

Table
Referenced fields (TCOR12)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of Date of diagnosis (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T19 1 Laterality TLATERAL

Business rules

For Add and Update Tumour records
  • ICD-O-2/3 Topography, Laterality and year of date of diagnosis combination must be valid based on Valid site and Laterality combinations table48.
Table
Edit logic (TCOR12)
Sub–edit  Conditions Outcome
TCOR12-1 T5 IN ['1', '2'] AND (T12.Year, T15 and T19 NOT IN [Valid site and Laterality combinations table]) Record rejected
Table
Feedback report messages (TCOR12)
Sub–edit  Text Type
TCOR12-1 ICD-O-2/3 Topography, Laterality and Date of diagnosis combination is invalid. Core error
Table
Revision (TCOR12)
Year Description
2004 Edit renamed: Edit formerly known as Correlation Edit No.22.
Business rules changed: Verification is now performed on ICD-O-3 values only, regardless of the source classification used.

TCOR13

Purpose

This edit ensures that invalid combinations of Method used to establish the date of diagnosis and Diagnostic confirmation codes are rejected.

Table
Referenced fields (TCOR13)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of Date of Diagnosis (year of Date of Diagnosis) N/A
T24 1 Method used to establish the date of diagnosis TMETHUSED
T25 1 Diagnostic confirmation TMETHCONF
T53 1 Ambiguous Terminology Diagnosis TAMBIGTERM

Business rules

For Add and Update Tumour records where the Date of Diagnosis is in 2004 or after
  • Diagnostic confirmation cannot be less definitive than Method used to establish the date of diagnosis. Example: Diagnostic confirmation cannot be "positive cytology" if the Method used to establish the Date of Diagnosis is "positive histology".
  • Method used to establish the date of diagnosis and Diagnostic confirmation must indicate the same value when either is "Autopsy Only" or "Death Certificate Only (DCO)" and the other one is reported.

For Add and Update Tumour records where the Date of Diagnosis is in 2008 or after

  • If Ambiguous Terminology Diagnosis is Ambiguous terminology only (1) then
    • Diagnostic Confirmation must be more definitive than Method used to establish date of diagnosis.
Table
Edit logic (TCOR13)
Sub–edit  Conditions Outcome
TCOR13-1

T5 IN ['1', '2'] AND (T12.YEAR>= '2008' AND T12.YEAR <= '2009') AND T53 = '1' AND T24 IN ['1','2','4','5','6','7', '9'] AND T25 IN ['1','2','4','5','6','7', '9'] AND ((T24='2' AND T25='2') OR (T24<T25))

Record rejected
TCOR13-2

T5 IN ['1', '2'] AND (T12.YEAR>= '2004' AND T12.YEAR <= '2009') AND T24 IN ['1','2','4','5','6','7', '9'] AND T25 IN ['1','2','4','5','6','7', '9'] AND ((T24='2' AND T25='2') OR (T24<T25 AND NOT (T24='1' and T25='2')))

Record rejected
TCOR13-3

T5 IN ['1', '2'] AND T12.YEAR>= '2004' AND ((T24 IN ['3', '8'] AND T25<>'0') OR (T25 IN ['3', '8'] AND T24<>'0')) AND T24 <> T25)

Record rejected
TCOR13-4

T5 IN ['1', '2'] AND (T12.YEAR>= '2010') AND T53 = '1' AND T24 IN ['1','2','4','5','6','7','9','10'] AND T25 IN ['1','2','4','5','6','7','9','10'] AND ((T24='2' AND T25='2') OR (T24 < '10' and T25 < '10' ANDT24<=T25) OR (T24 = '10' AND T25 > '1' AND T24 > T25))

Record rejected
TCOR13-5

T5 IN ['1', '2'] AND (T12.YEAR>= '2010' ) AND T24 IN ['1','2','4','5','6','7', '9','10'] AND T25 IN ['1','2','4','5','6','7', '9','10'] AND ((T24='2' AND T25='2') OR ((T24 < '10' AND T25 < '10') AND (T24 < T25) AND NOT (T24='1' and T25='2')) OR (T24= '10' AND T24 > T25 AND NOT (T24='10' and T25='1')))

Record rejected
Table
Feedback report messasges (TCOR13)
Sub–edit  Text Type
TCOR13-1

Diagnostic confirmation must be more definitive than Method used to establish the date of diagnosis when Ambiguous terminology is equal to 1 (Date of diagnosis 2008 to 2009).

Core error
TCOR13-2

Diagnostic confirmation cannot be less definitive than Method used to establish the date of diagnosis (Date of diagnosis 2004 to 2009).

Core error
TCOR13-3

Method used to establish the date of diagnosis and Diagnostic confirmation must indicate the same method when either is "Autopsy only" or "Death certificate only (DCO)".

Core error
TCOR13-4

Diagnostic confirmation must be more definitive than Method used to establish the date of diagnosis when Ambiguous terminology is equal to 1 (Date of diagnosis 2010 and onwards).

Core error
TCOR13-5

Diagnostic confirmation cannot be less definitive than Method used to establish the date of diagnosis (Date of diagnosis 2010 and onwards).

Core error
Table
Revision (TCOR13)
Year Description
2010 Edit Logic and Feedback report messages: New sub-edits added and existing edits modified to account for new code 10 - Positive histology plus added to Method used to establish date of diagnosis and Diagnostic confirmation. 
2008 New Sub-edit added: To make Diagnostic confirmation more definitive than Method used to establish the date of diagnosis.
2007 New edit added.

TCOR14

Purpose

This edit ensures that method of diagnosis is only reported for tumours diagnosed prior to 2004.

Table
Referenced fields (TCOR14)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T11 1 Method of diagnosis TMETHDIAG
T12.YEAR 4 First 4 digits of Date of diagnosis (year of date of diagnosis) Not applicable

Business rules

For Add and Update Tumour records
  • Method of diagnosis must only be reported when Date of diagnosis is prior 2004.
Table
Edit logic (TCOR14)
Sub–edit  Conditions Outcome
TCOR14-1 T5 IN ['1', '2'] AND T12.YEAR < 2004 AND T11 = '0' Record rejected
TCOR14-2 T5 IN ['1', '2'] AND T12.YEAR >= 2004 AND T11 <> '0' Record rejected
Table
Feedback report messages (TCOR14)
Sub–edit  Text Type
TCOR14-1 Method of diagnosis must be reported for tumours diagnosed before 2004. Core error
TCOR14-2 Method of diagnosis must be coded 'Not reported' for tumours diagnosed in 2004 and onwards. Core error
Table
Revision (TCOR14)
Year Description
2004 Edit Added: New edit.

TCOR15

Purpose

This edit ensures that method used to establish the date of diagnosis is only reported for tumours diagnosed in 2004 and onwards.

Table
Referenced fields (TCOR15)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of Date of diagnosis (year of date of diagnosis) Not applicable
T24 1 Method used to establish the date of diagnosis TMETHUSED

Business rules

For Add and Update Tumour records
  • Method used to establish the date of diagnosis must only be reported when Date of diagnosis is in 2004 or after.
Table
Edit logic (TCOR15)
Sub–edit  Conditions Outcome
TCOR15-1 T5 IN ['1', '2'] AND T12.YEAR < 2004 AND T24<> '0' Record rejected
TCOR15-2 T5 IN ['1', '2'] AND T12.YEAR >= 2004 AND T24 = '0' Record rejected
Table
Feedback report messages (TCOR15)
Sub–edit  Text Type
TCOR15-1 Method used to establish the date of diagnosis must be coded 'Not reported' for tumours diagnosed before 2004. Core error
TCOR15-2 Method used to establish the date of diagnosis must be reported for tumours diagnosed in 2004 and onwards. Core error
Table
Revision (TCOR15)
Year Description
2004 Edit Added: New edit.

TCOR16

Purpose

This edit ensures that diagnostic confirmation is only reported for tumours diagnosed in 2004 and onwards.

Table
Referenced fields (TCOR16)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of Date of diagnosis (year of date of diagnosis) Not applicable
T25 1 Diagnostic confirmation TMETHCONF

Business rules

For Add and Update Tumour records
  • Diagnostic confirmation must only be reported when Date of diagnosis is in 2004 or after.
Table
Edit logic (TCOR16)
Sub–edit  Conditions Outcome
TCOR16-1 T5 IN ['1', '2'] AND T12.YEAR < 2004 AND T25<> '0' Record rejected
TCOR16-2 T5 IN ['1', '2'] AND T12.YEAR >= 2004 AND T25 = '0' Record rejected
Table
Feddback report messages (TCOR16)
Sub–edit  Text Type
TCOR16-1 Diagnostic confirmation must be coded 'Not reported' for tumours diagnosed before 2004. Core error
TCOR16-2 Diagnostic confirmation must be reported for tumours diagnosed in 2004 and onwards. Core error
Table
Revision (TCOR16)
Year Description
2004 Edit Added: New edit.

TCOR17

Purpose

This edit ensures that grade, differentiation or cell indicator is only reported for tumours diagnosed in 2004 and onwards.

Table
Referenced fields (TCOR17)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of Date of diagnosis (year of date of diagnosis) Not applicable
T23 1 Grade, differentiation or cell indicator TGRADE

Business rules

For Add and Update Tumour records
  • Grade, differentiation or cell indicator must only be reported when Date of diagnosis is in 2004 or after.
Table
Edit logic (TCOR17)
Sub–edit  Conditions Outcome
TCOR17-1 T5 IN ['1', '2'] AND T12.YEAR < 2004 AND T23 <> '0' Record rejected
TCOR17-2 T5 IN ['1', '2'] AND T12.YEAR >= 2004 AND T23 = '0' Record rejected
Table
Feedback report messages (TCOR17)
Sub–edit  Text Type
TCOR17-1 Grade, differentiation or cell indicator must be coded 'Not reported' for tumours diagnosed before 2004. Core error
TCOR17-2 Grade, differentiation or cell indicator must be reported for tumours diagnosed in 2004 and onwards. Core error
Table
Revision (TCOR17)
Year Description
2004 Edit Added: New edit.

TCOR18

Purpose

This edit ensures that collaborative staging variables are reported for tumours within the CCR collaborative staging scope.

Table
Referenced fields (TCOR18)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T27 3 CS tumour size TCSTSIZE
T28 3 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS lymph nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version input original TCSVERINORIG
T63 1 Lymph-vascular invasion TLYMPHVASINV
T64 6 CS version input current TCSVERINCUR
T65-T83 3 CS site-specific factors 7 - 25 TCSSSF7 – TCSSSF25

Business rules

For Add and Update Tumour records outside the CCR collaborative staging scope48,
  • All Collaborative staging variables must be blank.
For Add and Update Tumour records within the CCR collaborative staging scope,
  • All Collaborative staging variables must be reported.
Table
Edit logic (TCOR18)
Sub–edit  Conditions Outcome
TCOR18-1

T5 IN ['1', '2'] AND T12.YEAR < 2004 AND (T27 IS NOT NULL OR T28 IS NOT NULL OR T29 IS NOT NULL OR T30 IS NOT NULL OR T31 IS NOT NULL OR T32 IS NOT NULL OR T33 IS NOT NULL OR T34 IS NOT NULL OR T35 IS NOT NULL OR T36 IS NOT NULL OR T37 IS NOT NULL OR T38 IS NOT NULL OR T39 IS NOT NULL OR T40 IS NOT NULL OR T41 IS NOT NULL OR T52 IS NOT NULL)

CS data items are not posted.

TCOR18-2

T5 IN ['1', '2'] AND T12.YEAR >= 2004 AND T64 IS NULL AND (T27 IS NULL OR T28 IS NULL OR T29 IS NULL OR T30 IS NULL OR T31 IS NULL OR T32 IS NULL OR T33 IS NULL OR T34 IS NULL OR T35 IS NULL OR T36 IS NULL OR T37 IS NULL OR T38 IS NULL OR T39 IS NULL OR T40 IS NULL OR T41 IS NULL OR T52 IS NULL)

CS data items filled with 'R' at posting.

TCOR18-3

T5 IN ['1', '2'] AND T12.YEAR >= 2004 AND T64 IS NOT NULL AND (T27 IS NULL OR T28 IS NULL OR T29 IS NULL OR T30 IS NULL OR T31 IS NULL OR T32 IS NULL OR T33 IS NULL OR T34 IS NULL OR T35 IS NULL OR T36 IS NULL OR T37 IS NULL OR T38 IS NULL OR T39 IS NULL OR T40 IS NULL OR T41 IS NULL OR T52 IS NULL OR T63 IS NULL OR T65 IS NULL OR T66 IS NULL OR T67 IS NULL OR T68 IS NULL OR T69 IS NULL OR T70 IS NULL OR T71 IS NULL OR T72 IS NULL OR T73 IS NULL OR T74 IS NULL OR T75 IS NULL OR T76 IS NULL OR T77 IS NULL OR T78 ISNULL OR T79 IS NULL OR T80 IS NULL OR T81 IS NULL OR T82 IS NULL OR T83 IS NULL)

CS data items filled with 'R' at posting.

Table
Feedback report messages (TCOR18)
Sub–edit  Text Type
TCOR18-1 Collaborative staging data must be left blank for tumours diagnosed prior to 2004. Reported data will not be loaded into CCR. CS fatal error
TCOR18-2 Eligible Collaborative staging site: all Collaborative staging variables must be reported (using CSV1).
 
CS fatal error
TCOR18-3 Eligible Collaborative staging site: all Collaborative staging variables must be reported (using CSV2) CS fatal error
Table
Revision (TCOR18)
Year Description
2010 Referenced Fields: Name and acronym of CS version 1st (TCSFVER) changed to CS version input original (TCSVERINORIG). Name and acronym of CS reg nodes eval (TCSRNEVAL) changed to CS lymph node eval (TCSLNEVAL). Length of CS Extension and CS Lymph nodes has changed from 2 to 3. TCOR18-2 revised to reflect use of CSV1. TCOR18-3 added to reflect use of CSV2.
2007 Referenced fields and Edit logic updated: T52 added as a new CS variable
2004 Edit Added: New edit.

TCOR19

Purpose

This edit ensures that AJCC TNM staging variables are reported for tumours within the CCR AJCC TNM staging scope.

Table
Referenced fields (TCOR19)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T42 9 AJCC clinical T TAJCCCLINT
T43 3 AJCC clinical N TAJCCCLINN
T44 3 AJCC clinical M TAJCCCLINM
T45 9 AJCC pathologic T TAJCCPATHT
T46 3 AJCC pathologic N TAJCCPATHN
T47 3 AJCC pathologic M TAJCCPATHM
T48 4 AJCC clinical TNM stage group TAJCCCLINSG
T49 4 AJCC pathologic TNM stage group TAJCCPATHSG
T50 4 AJCC TNM stage group TAJCCSG
T51 2 AJCC edition number TAJCCEDNUM

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • All AJCC TNM staging variables must be reported.
For Add and Update Tumour records outside the CCR AJCC TNM staging scope
  • All AJCC TNM staging variables must be blank.

Edit logic

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Table
Edit logic (TCOR19)
Sub–edit  Conditions Outcome
TCOR19-1 T5 IN ['1', '2'] AND (T12.YEAR < 2003 OR T12.YEAR > 2007) AND NOT (T42 IS NULL AND T43 IS NULL AND T44 IS NULL AND T45 IS NULL AND T46 IS NULL AND T47 IS NULL AND T48 IS NULL AND T49 IS NULL AND T50 IS NULL AND T51 IS NULL) AJCC TNM data items are not posted.
TCOR19-2 T5 IN ['1', '2'] AND (T12.YEAR >= 2003 OR T12.YEAR > 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND (T42 IS NULL OR T43 IS NULL OR T44 IS NULL OR T45 IS NULL OR T46 IS NULL OR T47 IS NULL OR T48 IS NULL OR T49 IS NULL OR T50 IS NULL OR T51 IS NULL) AJCC TNM data items filled with 'R' at posting.
TCOR19-3 T5 IN ['1', '2'] AND (T12.YEAR >= 2003 OR T12.YEAR > 2007) AND NOT (T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X]) AND NOT (T42 IS NULL AND T43 IS NULL AND T44 IS NULL AND T45 IS NULL AND T46 IS NULL AND T47 IS NULL AND T48 IS NULL AND T49 IS NULL AND T50 IS NULL AND T51 IS NULL) AJCC TNM data items are not posted.
Table
Feedback report messages (TCOR19)
Sub–edit  Text Type
TCOR19-1 All AJCC TNM staging data must be blank for tumours diagnosed prior to 2003 or after 2007. Reported data will not be loaded into CCR. AJCC TNM fatal error
TCOR19-2 Eligible AJCC TNM staging site: all AJCC TNM staging variables must be reported. AJCC TNM fatal error
TCOR19-3 Non-eligible AJCC TNM staging site: all AJCC TNM staging variables must be blank. Reported data will not be loaded into CCR AJCC TNM fatal error
Table
Revision (TCOR19)
Year Description
2009 Edit logic and Feedback report messages updated: AJCC variables T42 to T51 no longer reported after 2007.
2004 Edit Added: New edit.

TCOR20

Purpose

This edit ensures that TNM stage group is reported only when clinical and pathologic TNM stage group are not reported.

Table
Referenced fields (TCOR20)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T48 4 AJCC clinical TNM stage group TAJCCCLINSG
T49 4 AJCC pathologic TNM stage group TAJCCPATHSG
T50 4 AJCC TNM stage group TAJCCSG

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • AJCC TNM stage group can only be reported when both AJCC clinical TNM stage group and AJCC pathologic TNM stage group are either unknown or not assessed.

Edit logic

To simplify the edit logic, let Site X be a given site within the AJCC TNM Staging. Ex:Colorectal, breast or prostate.

Table
Edit logic (TCOR20)
Sub–edit  Conditions Outcome
TCOR20-1 T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T50 <> '99' AND (T48 NOT IN ['99', 'X'] OR T49 NOT IN ['99', 'X']) AJCC TNM data items filled with 'R' at posting.
Table
Feedback report messasges (TCOR20)
Sub–edit  Text Type
TCOR20-1 TNM stage group cannot be reported when clinical and/or pathologic TNM stage group is reported AJCC TNM error
Table
Revision (TCOR20)
Year Description
2009 Edit logic and Feedback report messages changed: AJCC variables T48, T49 and T50 no longer reported after 2007.
2004 Edit Added: New edit.

TCOR21

Purpose

This edit ensures that the combination of AJCC Clinical TNM stage group and the individual clinical T, N, M values combination is acceptable.

Table
Referenced fields (TCOR21)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T42 9 AJCC clinical T TAJCCCLINT
T43 3 AJCC clinical N TAJCCCLINN
T44 3 AJCC clinical M TAJCCCLINM
T48 4 AJCC clinical TNM stage group TAJCCCLINSG

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • If AJCC clinical TNM stage group is known and assessed then AJCC clinical T, N, M and AJCC clinical TNM stage group combination must be valid for the site49.
  • If AJCC clinical TNM stage group is not assessed then AJCC clinical T, N and M combination must not lead to a stage group for the site
  • If AJCC clinical TNM stage group is unknown then all AJCC clinical T, N and M values must also be unknown and conversely.

Edit logic

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Table
Edit logic (TCOR21)
Sub–edit  Conditions Outcome
TCOR21-1 T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND NOT (T42 = '99' AND T43 = '99' AND T44 = '99') AND T48 NOT IN ['99', 'X'] AND T42, T43, T44, T48 NOT IN [valid AJCC TNM and stage group combination for Site X] AJCC TNM data items filled with 'R' at posting.
TCOR21-2 T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T48 = 'X' AND T42, T43, T44 IN [valid AJCC TNM and stage group combination for Site X] AJCC TNM data items filled with 'R' at posting.
TCOR21-3 T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T48 = '99' AND (T42 <> '99' OR T43 <> '99' OR T44 <> '99') AJCC TNM data items filled with 'R' at posting.
TCOR21-4 T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T48 <> '99' AND T42 = '99' AND T43 = '99' AND T44 = '99' AJCC TNM data items filled with 'R' at posting.
Table
Feedback report messages (TCOR21)
Sub–edit  Text Type
TCOR21-1 AJCC clinical TNM stage group is invalid for reported AJCC clinical T, N and M values and site. AJCC TNM error
TCOR21-2 AJCC clinical TNM stage group must be assessed for reported clinical T, N and M values and site. AJCC TNM error
TCOR21-3 All AJCC clinical T, N and M values must be set to 'Unknown' when AJCC clinical TNM stage group is 'Unknown'. AJCC TNM error
TCOR21-4 AJCC clinical TNM stage group must be set to 'Unknown' when All AJCC clinical T, N and M values are set to 'Unknown'. AJCC TNM error
Table
Revision (TCOR21)
Year Description
2009 Edit logic and Feedback report messages changed: AJCC variables T42, T43, T44 and T48 no longer reported after 2007.
2004 Edit Added: New edit.

TCOR22

Purpose

This edit ensures that the combination of AJCC pathologic TNM stage group and the individualpathologic T, N, M values is acceptable.

Table
Referenced fields (TCOR22)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T45 9 AJCC pathologic T TAJCCPATHT
T46 3 AJCC pathologic N TAJCCPATHN
T47 3 AJCC pathologic M TAJCCPATHM
T49 4 AJCC pathologic TNM stage group TAJCCPATHSG

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29.
  • If AJCC pathologic TNM stage group is known and assessed then AJCC pathologic T, N, M and AJCC pathologic TNM stage group combination must be valid for the site49.
  • If AJCC pathologic TNM stage group is not assessed then AJCC pathologic T, N and M combination must not imply a stage group for the site49.
  • If AJCC pathologic TNM stage group is unknown then all AJCC pathologic T, N and M values must also be unknown and conversely.

Edit logic

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Table
Edit logic (TCOR22)
Sub–edit  Conditions Outcome
TCOR22-1 T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND NOT (T45 = '99' AND T46 = '99' AND T47 = '99') AND T49 NOT IN ['99', 'X'] AND T45, T46, T47, T49 NOT IN [valid AJCC TNM and stage group combination for Site X] AJCC TNM data items filled with 'R' at posting.
TCOR22-2 T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T49 = 'X' AND T45, T46, T47 IN [valid AJCC TNM and stage group combination for Site X] AJCC TNM data items filled with 'R' at posting.
TCOR22-3 T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T49 = '99' AND (T45 <> '99' OR T46 <> '99' OR T47 <> '99') AJCC TNM data items filled with 'R' at posting.
TCOR22-4 T5 IN ['1', '2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T49 <> '99' AND T45 = '99' AND T46 = '99' AND T47 = '99' AJCC TNM data items filled with 'R' at posting.
Table
Feedback report messages (TCOR22)
Sub–edit  Text Type
TCOR22-1 AJCC pathologic TNM stage group is invalid for reported AJCC pathologic T, N and M values and site. AJCC TNM error
TCOR22-2 AJCC pathologic TNM stage group must be assessed for reported pathologic T, N and M values and site. AJCC TNM error
TCOR22-3 All AJCC pathologic T, N and M values must be set to 'Unknown' when AJCC pathologic TNM stage group is 'Unknown'. AJCC TNM error
TCOR22-4 AJCC pathologic TNM stage group must be set to 'Unknown' when All AJCC pathologic T, N and M values are set to 'Unknown'. AJCC TNM error
Table
Revision (TCOR22)
Year Description
2009 Edit logic and Feedback report messages changed: AJCC variables T45, T46, T47 and T49 no longer reported after 2007.
2004 Edit Added: New edit.

TCOR23

Purpose

This edit ensures that the combination of AJCC TNM stage group and the individual clinical/pathologic T, N, M values is acceptable.

Table
Referenced fields(TCOR23)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T42 9 AJCC clinical T TAJCCCLINT
T43 3 AJCC clinical N TAJCCCLINN
T44 3 AJCC clinical M TAJCCCLINM
T45 9 AJCC pathologic T TAJCCPATHT
T46 3 AJCC pathologic N TAJCCPATHN
T47 3 AJCC pathologic M TAJCCPATHM
T50 4 AJCC TNM stage group TAJCCSG

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • If AJCC TNM stage group is known then the most "accurate" combination of known and assessed AJCC clinical/pathologic T, N, M values and AJCC TNM stage group must be valid49,50. For any staging element (T, N, M), pathologic values are always considered more "accurate" when both clinical and pathologic values are known and assessed.
  • Example If cT = 'T2' and pT = 'T1', the most accurate tumour stage is 'T1' (pathologic data take precedence over clinical).
  • Example If cM = 'M1' and pM = 'MX', the most accurate metastases stage is 'M1' (pathologic M is not assessed).

Edit logic

To simplify the edit logic, let:

  • BestT (clin, path), BestN (clin, path) and BestM (clin, path) be functions that return the most "accurate" tumour, node and metastases staging value based on the rules stated above. When both clinical and pathologic values are '99', 'TX', 'NX' or 'MX', these functions always return the pathologic value.
  • Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.
Table
Edit logic (TCOR23)
Sub–edit  Conditions Outcome
TCOR23-1 T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T50 <> '99' AND ((BestT (T42, T45) NOT IN ['99', 'X'] AND BestN (T43, T46) IN ['99', 'X'] AND BestM (T44, T47) IN ['99', 'X'] AND BestT(T42, T45), T50 NOT IN [valid AJCC TNM and stage group combination for Site X]) OR (BestT (T42, T45) IN ['99', 'X'] AND BestN (T43, T46) NOT IN ['99', 'X'] AND BestM (T44, T47) IN ['99', 'X'] AND BestN (T43, T46), T50 NOT IN [valid AJCC TNM and stage group combination for Site X]) OR (BestT (T42, T45) IN ['99', 'X'] AND BestN (T43, T46) IN ['99', 'X'] AND BestM (T44, T47) NOT IN ['99', 'X'] AND BestM (T44, T47), T50 NOT IN [valid AJCC TNM and stage group combination for Site X]) OR (BestT (T42, T45) NOT IN ['99', 'X'] AND BestN (T43, T46) NOT IN ['99', 'X'] AND BestM (T44, T47) IN ['99', 'X'] AND BestT (T42, T45), BestN (T43, T46), T50 NOT IN [valid AJCC TNM and stage group combination for Site X]) OR (BestT (T42, T45) IN ['99', 'X'] AND BestN (T43, T46) NOT IN ['99', 'X'] AND BestM (T44, T47) NOT IN ['99', 'X'] AND BestN (T43, T46), BestM (T44, T47), T50 NOT IN [valid AJCC TNM and stage group combination for Site X]) OR ((BestT (T42, T45) NOT IN ['99', 'X'] AND BestN (T43, T46) IN ['99', 'X'] AND BestM (T44, T47) NOT IN ['99', 'X'] AND BestT(T42, T45), BestM (T44, T47), T50 NOT IN [valid AJCC TNM and stage group combination for Site X]) OR (BestT (T42, T45) NOT IN ['99', 'X'] AND BestN (T43, T46) NOT IN ['99', 'X'] AND BestM (T44, T47) NOT IN ['99', 'X'] AND BestT(T42, T45), BestN (T43, T46), BestM (T44, T47), T50 NOT IN [valid AJCC TNM and stage group combination for Site X])) AJCC TNM data items filled with 'R' at posting.
Table
Feedback report messages (TCOR23)
Sub–edit  Text Type
TCOR23-1 AJCC TNM stage group is invalid for reported clinical/pathologic T, N and M values and site. AJCC TNM error
Table
Revision (TCOR23)
Year Description
2009 Edit logic and Feedback report messages changed: AJCC variables T42, T43, T44, T45, T46, T47 and T50 no longer reported after 2007.
2004 Edit Added: New edit.

TCOR24

Purpose

This edit ensures that AJCC edition number is coherent with all remaining AJCC TNM staging variables.

Table
Referenced fields (TCOR24)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T42 9 AJCC clinical T TAJCCCLINT
T43 3 AJCC clinical N TAJCCCLINN
T44 3 AJCC clinical M TAJCCCLINM
T45 9 AJCC pathologic T TAJCCPATHT
T46 3 AJCC pathologic N TAJCCPATHN
T47 3 AJCC pathologic M TAJCCPATHM
T48 4 AJCC clinical TNM stage group TAJCCCLINSG
T49 4 AJCC pathologic TNM stage group TAJCCPATHSG
T50 4 AJCC TNM stage group TAJCCSG
T51 2 AJCC edition number TAJCCEDNUM

Business rules

For Add and Update Tumour records with the CCR AJCC TNM staging scope29.
  • If AJCC edition number is set to 'Not staged' then all other AJCC TNM staging variables must be set to 'Unknown' and conversely.
Table
Edit logic (TCOR24)
Sub–edit  Conditions Outcome
TCOR24-1 T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND ((T15 IN [Eligible ICD-O-3 – Topography codes for AJCC TNM Staging Colorectal sites] AND T21 IN [Eligible ICD-O-3 – Histology codes for AJCC TNM Staging Colorectal sites] AND T22 IN [Eligible ICD-O-3 Behaviour codes for AJCC TNM Staging Colorectal sites]) OR (T15 IN [Eligible ICD-O-3 – Topography codes for AJCC TNM Staging Breast sites] AND T21 IN [Eligible ICD-O-3 – Histology codes for AJCC TNM Staging Breast sites] AND T22 IN [Eligible ICD-O-3 – Behaviour codes for AJCC TNM Staging Breast sites]) OR (T15 IN [Eligible ICD-O-3 – Topography codes for AJCC TNM Staging Prostate sites] AND T21 IN [Eligible ICD-O-3 – Histology codes for AJCC TNM Staging Prostate sites] AND T22 IN [Eligible ICD-O-3 – Behaviour codes for AJCC TNM Staging Prostate sites])) AND T42 = '99' AND T43 = '99' AND T44 = '99' AND T45 = '99' AND T46 = '99' AND T47 = '99' AND T48 = '99' AND T49 = '99' AND T50 = '99' AND T51 <> '00' AJCC TNM data items filled with 'R' at posting.
TCOR24-2 T5 IN ['1', '2'] AND (T12.YEAR >= 2003 AND T12.YEAR <= 2007) AND ((T15 IN [Eligible ICD-O-3 – Topography codes for AJCC TNM Staging Colorectal sites] AND T21 IN [Eligible ICD-O-3 – Histology codes for AJCC TNM Staging Colorectal sites] AND T22 IN [Eligible ICD-O-3 Behaviour codes for AJCC TNM Staging Colorectal sites]) OR (T15 IN [Eligible ICD-O-3 – Topography codes for AJCC TNM Staging Breast sites] AND T21 IN [Eligible ICD-O-3 – Histology codes for AJCC TNM Staging Breast sites] AND T22 IN [Eligible ICD-O-3 – Behaviour codes for AJCC TNM Staging Breast sites]) OR (T15 IN [Eligible ICD-O-3 – Topography codes for AJCC TNM Staging Prostate sites] AND T21 IN [Eligible ICD-O-3 – Histology codes for AJCC TNM Staging Prostate sites] AND T22 IN [Eligible ICD-O-3 – Behaviour codes for AJCC TNM Staging Prostate sites])) AND T51 = '00' AND (T42 <> '99' OR T43 <> '99' OR T44 <> '99' OR T45 <> '99' OR T46 <> '99' OR T47 <> '99' OR T48 <> '99' OR T49 <> '99' OR T50 <> '99') All AJCC TNM data items filled with 'R' at posting.
Table
Feedback report messages (TCOR24)
Sub–edit  Text Type
TCOR24-1 TNM edition number must be set to 'Not Staged' when all other AJCC TNM staging variables are 'Unknown'. AJCC TNM error
TCOR24-2 TNM edition number cannot be set to 'Not Staged' when some AJCC TNM staging variables are reported. AJCC TNM error
Table
Revision (TCOR24)
Year Description
2009 Edit logic and Feedback report messages changed: AJCC variables T42 - T51 no longer reported after 2007.
2004 Edit Added: New edit.

TCOR26

Purpose

This edit ensures the consistency between Ambiguous terminology diagnosis and Date of conclusive diagnosis.

Table
Referenced fields (TCOR26)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T53 1 Ambiguous terminology diagnosis TAMBIGTERM
T54 8 Date of conclusive diagnosis TDATCONCLUSDIAG

Business rules

For Add and Update Tumour records
  • If Date of Diagnosis is before 2008 then Ambiguous terminology diagnosis and Date of conclusive diagnosis must both be blank.
  • If Date of Diagnosis is 2008 and onwards then Ambiguous terminology diagnosis and Date of conclusive diagnosis must be either both blank or both reported.
Table
Edit logic (TCOR26)
Sub–edit  Conditions Outcome
TCOR26-1 T5 IN ['1','2'] AND T12.YEAR < 2008 AND (T53 IS NOT NULL OR T54 IS NOT NULL) Record rejected
TCOR26-2 T5 IN ['1','2'] AND T12.YEAR >= 2008 AND (T53 IS NOT NULL OR T54 IS NOT NULL) AND (T53 IS NULL OR T54 IS NULL) Record rejected
Table
Feedback report messages (TCOR26)
Sub–edit  Text Type
TCOR26-1 Ambiguous terminology diagnosis and Date of conclusive diagnosis must both be blank if Date of diagnosis is before 2008. Core error
TCOR26-2 Ambiguous terminology diagnosis and Date of conclusive diagnosis must either both be reported or both be left blank if Date of diagnosis is 2008 and onwards. Core error
Table
Revision (TCOR26)
Year Description
2008 Edit added: New edit.

TCOR27

Purpose

This edit ensures the consistency between Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter.

Table
Referenced fields (TCOR27)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 5 First 4 digits of T12 (year of date of diagnosis) Not applicable
T55 2 Type of multiple tumours reported as one primary TMULTTUMONEPRIM
T56 8 Date of multiple tumours DDATMULT
T57 2 Multiplicity counter TMULTCOUNT

Business rules

For Add and Update Tumour records
  • If Date of Diagnosis is before 2008 then Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter must all be blank.
  • If Date of Diagnosis is 2008 and onwards then Type of multiple tumours reported as one primary, Date of multiple tumours, and Multiplicity counter must be either all blank or all reported.
Table
Edit logic (TCOR27)
Sub–edit  Conditions Outcome
TCOR27-1 T5 IN ['1','2'] AND T12.YEAR < 2008 AND (T55 IS NOT NULL OR T56 IS NOT NULL OR T57 IS NOT NULL) Record rejected
TCOR27-2 T5 IN ['1','2'] AND T12.YEAR >= 2008 AND (T55 IS NOT NULL OR T56 IS NOT NULL OR T57 IS NOT NULL) AND (T55 IS NULL OR T56 IS NULL OR T57 IS NULL) Record rejected
Table
Feedback report messages (TCOR27)
Sub–edit  Text Type
TCOR27-1 Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter must all be blank if Date of diagnosis is before 2008. Core error
TCOR27-2 Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter must either all be blank or all be reported if Date of diagnosis is 2008 and onwards. Core error
Table
Revision (TCOR27)
Year Description
2008 Edit added: New edit.

TCOR29

Purpose

This edit ensures the consistency between Ambiguous terminology diagnosis and Date of conclusive diagnosis.

Table
Referenced fields (TCOR29)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T53 1 Ambiguous terminology diagnosis TAMBIGTERM
T54 8 Date conclusive diagnosis TDATCONCLUSDIAG

Business rules

For Add and Update Tumour records
  • If Ambiguous terminology diagnosis is "Conclusive terminology within 60 days of original diagnosis" (0) then Date of conclusive diagnosis must be "Not applicable" (88888888).
  • If Ambiguous terminology diagnosis is "Ambiguous terminology only" (1) then Date of conclusive diagnosis must be "Accessioned based on ambiguous terminology diagnosis only" (00000000).
  • If Ambiguous terminology diagnosis is "Ambiguous terminology followed by conclusive terminology" (2) then Date of conclusive diagnosis must NOT be "Not applicable" (88888888) or "Accessioned based on ambiguous terminology diagnosis only" (00000000).
  • If Ambiguous terminology diagnosis is "Unknown terminology" (9) then Date of conclusive diagnosis must indicate that date is unknown (99999999).
  • If Ambiguous terminology diagnosis is "Ambiguous terminology followed by conclusive terminology" (2) then Date of conclusive diagnosis should NOT be unknown (99999999).
Table
Edit logic (TCOR29)
Sub–edit  Conditions Outcome
TCOR29-1 T5 IN ['1','2'] AND (T53 = '0' AND T54 <> '88888888') OR (T53 = '1' AND T54 <> '00000000') OR (T53 = '2' AND T54 IN ['00000000', '88888888']) OR (T53 = '9' AND T54 <> '99999999') Record rejected
TCOR29-2 T5 IN ['1', '2'] AND T53 IN ['2'] AND T54 IN ['99999999'] Warning
Table
Feedback report messages (TCOR29)
Sub–edit  Text Type
TCOR29-1 Ambiguous terminology diagnosis and Date of conclusive diagnosis are inconsistent. Core error
TCOR29-2 Date of conclusive diagnosis should be a valid calendar date when case is identified as "Ambiguous terminology followed by conclusive terminology". Warning
Table
Revision (TCOR29)
Year Description
2008 Edit added: New edit.

TCOR30

Purpose

This edit ensures that date of diagnosis and date of conclusive diagnosis respect a chronological sequence and time frame.

Table
Referenced fields (TCOR30)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12 8 Date of diagnosis TDATDIAG
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T12.MONTH 2 5th and 6th digits of T12 (month of date of diagnosis) Not applicable
T12.DAY 2 Last 2 digits of T12 (day of date of diagnosis) Not applicable
T54 8 Date of Conclusive Diagnosis TDATCONCLUSDIAG
T54.YEAR 4 First 4 digits of T54 (year of date of conclusive diagnosis) Not applicable
T54.MONTH 2 5th and 6th digits of T54 (month of date of conclusive diagnosis) Not applicable
T54.DAY 2 7th and 8th of T54 (day of date of conclusive diagnosis) Not applicable

Business rules

For Add and Update Tumour records
  • Date of conclusive diagnosis must be greater than two months (60 days) after the Date of diagnosis.
Table
Edit logic (TCOR30)
Sub–edit  Conditions Outcome
TCOR30-1 T5 IN ['1', '2'] AND T54 NOT IN ['00000000','88888888', '99999999'] AND ((T12.DAY <> '99' AND T54.DAY <> '99' AND T54 < T12) OR (T12.MONTH <> '99' AND T54.MONTH <> '99' AND T54.YEAR || T54.MONTH < T12.YEAR || T12.MONTH) OR (T54.YEAR < T12.YEAR)) Record rejected
TCOR30-2 T5 IN ['1', '2'] AND T54 NOT IN ['00000000','88888888', '99999999'] and DIFF_DAYS (Date1,Date2) <= 60. See Appendix J – Interval between 2 dates (complete or partial). Record rejected
TCOR30-3 T5 IN ['1', '2'] AND T12.YEAR = T54.YEAR AND T12.MONTH = '99' AND T54.MONTH = '99' Record rejected
Table
Feedback report messages (TCOR30)
Sub–edit  Text Type
TCOR30-1 Date of conclusive diagnosis is before date of diagnosis. Core error
TCOR30-2 Date of conclusive diagnosis must be greater than 60 days after the date of diagnosis. Core error
TCOR30-3 If the year of Date of diagnosis is equal to the year of Date of conclusive diagnosis and both months are unknown, the Date of conclusive diagnosis must be unknown. Core error
Table
Revision (TCOR30)
Year Description
2008 Edit added: New edit.

TCOR31

Purpose

This edit ensures the consistency between ICD-O-2/3 Topography and Type of multiple tumours reported as one primary.

Table
Referenced fields (TCOR31)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T15 5 ICD-O-2/3 Topography TICD_02T
T55 2 Type of multiple tumours reported as one primary TMULTTUMONEPRIM

Business rules

For Add and Update Tumour records
  • If Type of multiple tumours reported as one primary is coded as "polyp and adenocarcinoma" (31) or "Familial Adenomatous Polyposis (FAP) with carcinoma" (32) Then ICD-O-2/3 Topography must be coded as "Colon" (C180-C189), "Rectosigmoid Junction" (C199) or "Rectum" (C209).
Table
Edit logic (TCOR31)
Sub–edit  Conditions Outcome
TCOR31-1 T5 IN ['1', '2'] AND T55 IN [31,32] and T15 NOT IN [C180-C189, C199 or C209] Record rejected
Table
Feedback report messages (TCOR31)
Sub–edit  Text Type
TCOR31-1 Type of multiple tumours reported as one primary and ICD-O-2/3 combination is invalid. Core error
Table
Revision (TCOR31)
Year Description
2008 Edit added: New edit.

TCOR32

Purpose

This edit ensures the consistency between ICD-O-3 Behaviour and Type of multiple tumours reported as one primary.

Table
Referenced fields (TCOR32)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T22 1 ICD-O-3 Behaviour TICD_03B
T55 2 Type of multiple tumours reported as one primary TMULTTUMONEPRIM

Business rules

For Add and Update Tumour records
  • If Type of multiple tumours reported as one primary is coded as either "Multiple benign (intracranial and CNS sites only)" (10), "Multiple borderline" (11), or "Benign (intracranial and CNS sites only) and borderline" (12), then ICD-O-3 Behaviour must be coded as either "benign" (0) or "borderline" (1).
Table
Edit logic (TCOR32)
Sub–edit  Conditions Outcome
TCOR32-1 T5 IN ['1', '2'] AND T55 IN ['10', '11', '12'] AND T22 NOT IN ['0','1'] Record rejected
Table
Feedback report messages (TCOR32)
Sub–edit  Text Type
TCOR32-1 Type of multiple tumours reported as one primary and ICD-O-3 behaviour combination is invalid. Core error
Table
Revision (TCOR32)
Year Description
2008 Edit added: New edit.

TCOR33

Purpose

This edit ensures the consistency between Type of multiple tumours reported as one primary, Date of multiple tumours, Multiplicity counter, ICD-O-2/3 Topography and ICD-O-3 Histology.

Table
Referenced fields (TCOR33)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T15 4 ICD–O–2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T24 1 Method used to establish the date of diagnosis TMETHUSED
T55 2 Type of multiple tumours reported as one primary TMULTTUMONEPRIM
T56 8 Date of multiple tumours TDATMULT
T57 2 Multiplicity counter TMULTCOUNT

Business rules

For Add and Update Tumour records where method used to establish the date of diagnosis is not 'death certificate only"
  • If ICD–O–2/3 topography is 'unknown primary' (C809) or ICD–O– 3 Histology refers to lymphoma, leukemia or immunoproliferative disease62 [9590-9989 except 9731, 9734, 9740, 9750, 9755, 9756, 9757, 9758, 9930] then Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter must be 'Information on multiple tumours not applicable for this site'.
  • If ICD-O-2/3 topography is known (not C809) and ICD–O–3 Histology does NOT refer to lymphoma, leukemia or immunoproliferative disease [9590-9989 except 9731, 9734, 9740, 9750, 9755, 9756, 9757, 9758, 9930] then Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter must not be 'Information on multiple tumours not applicable for this site'.
Table
Edit logic (TCOR33)
Sub–edit  Conditions Outcome
TCOR33-1 T5 IN ['1','2'] AND T24 <> 8 AND (T15 = 'C809' OR T21 IN [9590-9989]) AND T55 <> 88 OR T56 <> '88888888' OR T57 <> '88' Record rejected
TCOR33-2 T5 IN ['1','2'] AND T24 <> 8 AND (T15 <> 'C809' OR T21 NOT IN [9590-9989]) AND T55 = '88' OR T56 = '88888888' OR T57 = '88' Record rejected
Table
Feedback report messages (TCOR33)
Sub–edit  Text Type
TCOR33-1 Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter must be reported as 'Information on multiple tumours not applicable for this site'. Core error
TCOR33-2 Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter must NOT be reported as 'Information on multiple tumours not applicable for this site'. Core error
Table
Revision (TCOR33)
Year Description
2008 Edit added: New edit.

TCOR34

Purpose

This edit ensures the consistency between Date of multiple tumours and Type of multiple tumours reported as one primary.

Table
Referenced fields (TCOR34)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T55 2 Type of multiple tumours reported as one primary TMULTTUMONEPRIM
T56 8 Date of multiple tumours DDATMULT
T57 2 Multiplicity counter TMULTCOUNT

Business rules

For Add and Update Tumour records
  • If Type of multiple tumours reported as one primary is "single tumour" (00) then  Date of multiple tumours  must be "single tumour" (00000000) and Multiplicity counter must be '01'.
  • If Type of multiple tumours reported as one primary is "not applicable for this site" (88) then Date of multiple tumours must be "information on multiple tumours not applicable for this site" (88888888) and Multiplicity counter must be 'Information on multiple tumours not applicable for this site' (88).
  • If Type of multiple tumours reported as one primary indicates multiple tumours (codes 10 through 80) or unknown (99) then Date of multiple tumours must be the date the patient is diagnosed with multiple tumours or unknown (99999999) and Multiplicity counter must be values 02 through 87 or (99).
Table
Edit logic (TCOR34)
Sub–edit  Conditions Outcome
TCOR34-1 T5 IN ['1','2'] AND (T55 = '00' AND T56 <> '00000000' OR T57 <> '01') OR (T55 = '88' AND T56 <> '88888888' OR T57 <> 88' ) OR (T55 IN ['10','11','12','20','30','31','32','40','80' '99'] AND (T56 = '00000000' OR T56 = '88888888') OR (T57 = '01' OR T57 = '88') Record rejected
Table
Feedback report messages (TCOR34)
Sub–edit  Text Type
TCOR34-1 Type of multiple tumours reported as one primary, date of multiple tumours and multiplicity counter combination is invalid. Core error
Table
Revision (TCOR34)
Year Description
2009 Business rules and edit logic changed : Modified to accept additional combinations.
2008 Edit added: New edit.

TCOR35

Purpose

This edit ensures the consistency between Method used to establish the date of diagnosis, Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter..

Table
Referenced fields (TCOR35)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T24 1 Method used to establish the date of diagnosis TMETHUSED
T55 2 Type of multiple tumours reported as one primary TMULTTUMONEPRIM
T56 8 Date of multiple tumours TDATMULT
T57 2 Multiplicity counter TMULTCOUNT

Business rules

For Add and Update Tumour records
  • If Type of multiple tumours reported as one primary is "Unknown" (99) and Method used to establish date of diagnosis is "Death certificate only" (8), then Date of multiple tumours must be "Unknown" (99999999) and Multiplicity counter must be "Multiple tumours present, unknown how many/unknown if single or multiple tumours" (99).
Table
Edit logic (TCOR35)
Sub–edit  Conditions Outcome
TCOR35-1 T5 IN ['1','2'] AND (T55 = '99' AND T24 = '8') AND (T56 <> '99999999' OR T57 <> '99') Record rejected
Table
Feedback report messages (TCOR35)
Sub–edit  Text Type
TCOR35-1 Method used to establish the date of diagnosis, Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter combination is invalid. Core error
Table
Revision (TCOR35)
Year Description
2008 Edit added: New edit.

TCOR36

Purpose

This edit ensures the consistency between Date of diagnosis and Grade path value and Grade path system.

Table
Referenced fields (TCOR36)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T61 1 Grade path value TGRADEPATHVAL
T62 1 Grade path system TGRADEPATHSYS

Business rules

For Add and Update Tumour records
  • If Date of Diagnosis is before 2010 then Grade path value and Grade path system must both be blank.
  • If Date of Diagnosis is 2010 and onwards then Grade path value and Grade path system must be either both blank or both reported.
Table
Edit logic (TCOR36)
Sub–edit  Conditions Outcome
TCOR36-1 T5 IN ['1','2'] AND T12.YEAR < 2010 AND (T61 IS NOT NULL OR T62 IS NOT NULL) Record rejected
TCOR36-2 T5 IN ['1','2'] AND T12.YEAR >= 2010 AND (T61 IS NOT NULL OR T62 IS NOT NULL) AND (T61 IS NULL OR T62 IS NULL) Record rejected
Table
Feedback report messages (TCOR36)
Sub–edit  Text Type
TCOR36-1 Grade path value and Grade path system must both be blank if Date of diagnosis is before 2010. Core error
TCOR36-2 Grade path value and Grade path system must either both be reported or both be left blank if Date of diagnosis is 2010 and onwards. Core error
Table
Revision (TCOR36)
Year Description
2010 Edit added: New edit.

TCOR37

Purpose

This edit ensures the consistency between Grade path value and Grade path system.

Table
Referenced fields (TCOR37)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T61 1 Grade path value TGRADEPATHVAL
T62 1 Grade path system TGRADEPATHSYS

Business rules

For Add and Update Tumour records
  • If Grade Path System is reported as a two-grade system (2), then Grade Path Value must be reported as Grade 1 or as Grade 2.
  • If Grade Path System is reported as a three-grade system (3), then Grade Path Value must be reported as Grade 1, or as Grade 2, or as Grade 3.
  • If Grade Path System is reported as a Four-Grade System (4), then Grade Path Value must be reported as Grade 1, or as Grade 2, or as Grade 3, or as Grade 4.
Table
Edit logic (TCOR37)
Sub–edit  Conditions Outcome
TCOR37-1 T5 IN ['1', '2'] AND T12.YEAR >= 2010 AND (T62 = '2' AND (T61 <> '1' OR T61 <> '2')) Record rejected
TCOR37-2 T5 IN ['1', '2'] AND T12.YEAR >= 2010 AND (T62 = '3' AND (T61 <> '1' OR T61 <> '2' OR T61 <> '3')) Record rejected
TCOR37-3 T5 IN ['1', '2'] AND T12.YEAR >= 2010 AND (T62 = '4' AND (T61 <> '1' OR T61 <> '2' OR T61 <> '3' OR T61 <> '4')) Record rejected
Table
Feedback report messages (TCOR37)
Sub–edit  Text Type
TCOR37-1 Grade Path Value must be reported as Grade 1 or Grade 2 when Grade Path System is reported as a two-grade system. Core error
TCOR37-2 Grade Path Value must be reported as Grade 1, Grade 2 or Grade 3 when Grade Path System is reported as a three-grade system. Core error
TCOR37-3 Grade Path Value must be reported as Grade 1, Grade 2 or Grade 3, or Grade 4 when Grade Path System is reported as a four-grade system. Core error
Table
Revision (TCOR37)
Year Description
2010 Edit added: New edit.

TCOR38

Purpose

This edit ensures consistency between CS mets at dx and CS mets at dx bone, CS mets at dx and CS mets at dx brain, CS mets at dx and CS mets at dx liver, CS mets at dx and CS mets at dx lung.

Table
Referenced fields (TCOR38)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T34 2 CS mets at dx TCSMDIAG
T84 1 CS mets at dx bone TCSMDXBONE
T85 1 CS mets at dx brain TCSMDXBRAIN
T86 1 CS mets at dx liver TCSMDXLIVER
T87 1 CS mets at dx lung TCSMDXLUNG

Business rules

For Add and Update Tumour records where Date of diagnosis >= '2010'
  • If CS mets at dx bone indicates metastatic involvement, then CS mets at dx must also indicate metastatic involvement.
  • If CS mets at dx brain indicates metastatic involvement, then CS mets at dx must also indicate metastatic involvement.
  • If CS mets at dx liver indicates metastatic involvement, then CS mets at dx must also indicate metastatic involvement.
  • If CS mets at dx lung indicates metastatic involvement, then CS mets at dx must also indicate metastatic involvement.
Table
Edit logic (TCOR38)
Sub–edit  Conditions Outcome
TCOR38-1 T5 IN ['1', '2'] AND T12.YEAR >= 2010 AND (T84 = '1' AND T34 = '00') Record rejected
TCOR38-2 T5 IN ['1', '2'] AND T12.YEAR >= 2010 AND (T85 = '1' AND T34 = '00') Record rejected
TCOR38-3 T5 IN ['1', '2'] AND T12.YEAR >= 2010 AND (T86 = '1' AND T34 = '00') Record rejected
TCOR38-4 T5 IN ['1', '2'] AND T12.YEAR >= 2010 AND (T87 = '1' AND T34 = '00') Record rejected
Table
Feedback report messages (TCOR38)
Sub–edit  Text Type
TCOR38-1 CS mets dx must indicate metastatic involvement when CS mets at dx bone indicates metastatic involvement. Core error
TCOR38-2 CS mets dx must indicate metastatic involvement when CS mets at dx brain indicates metastatic involvement. Core error
TCOR38-3 CS mets dx must indicate metastatic involvement when CS mets at dx liver indicates metastatic involvement. Core error
TCOR38-4 CS mets dx must indicate metastatic involvement when CS mets at dx lung indicates metastatic involvement. Core error
Table
Revision (TCOR38)
Year Description
2010 Edit added: New edit.

3.6 Match edits

The purpose of the match edits is to enforce the business rules between fields on different records. For ease of use, match edits have been divided into four groups:

  • Key input match edits: Ensure that input patient and tumour records respect the submission rules in terms of matching keys.
  • Key base match edits: Ensure that input patient and tumour records respect the actual state of the CCR in terms of matching keys.
  • Data item match edits: Enforce the business rules between data items (other than keys) found on different records.
  • Pre-posting match edits: Identify core error-free input records that cannot be posted to the CCR4 because some other related Input records are either missing or have core errors.

3.6.1 Key input match edits

The purpose of the key input match edits is to ensure that input patient and tumour records respect the submission rules in terms of matching keys.

At this level, the following fields are used as key:

  • Patient record: Reporting province/territory and patient identification number.
  • Tumour record: Reporting province/territory, patient identification number and tumour reference number.

The following table summarizes the purpose of each individual edit of this category:

Table 28
Input match edits summary
Edit name Purpose
KIM1 Ensures that only one operation affecting a specific patient record is performed (that is, add, delete or update) within a data submission.
KIM2 Ensures that only one operation affecting a specific Tumour record is performed (that is, add, delete or update) within a data submission.
KIM3 Enforces the submission rules regarding the addition of a patient record.
KIM4 Enforces the submission rules regarding the deletion of a patient record.
KIM5 Enforces the submission rules regarding the addition of a Tumour record.

Important note:

When a key input match edit fails, all related Input records (all input patient and tumour records sharing the same reporting province/territory and patient identification number) are rejected. Related records are also called the family of records.

KIM1

Purpose

This edit ensures that only one operation affecting a specific patient record is performed
(add, delete or update) within a data submission.

Table
Referenced fields (KIM1)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN

Business rules

For Input Patient records
  • There cannot be another Input patient record with identical Reporting province/territory and Patient identification number within the same data submission.
Table
Edit logic (KIM1)
Sub–edit  Conditions Outcome
KIM1-1 Input patient record that matches another Input patient record where P1=P1 AND P2=P2. Family rejected51
Table
Feedback report messages (KIM1)
Sub–edit  Text Type
KIM1-1 Family rejected: more than one Input patient record with the same Patient reporting province/territory and Patient identification number. Core error
Table
Revision (KIM1)
Year Description
2004 Edit renamed: Formerly known as Input Match Edit No.1.

KIM2

Purpose

This edit ensures that only one operation affecting a specific tumour record is performed (add, delete or update) within a data submission.

Table
Referenced fields (KIM2)
Field Length Description Acronym
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Tumour patient identification number TPIN
T3 9 Tumour reference number TTRN

Business rules

For Input Tumour records
  • There cannot be another Input Tumour record with identical Reporting province/territory, Patient identification number and Tumour reference number within the same data submission.
Table
Edit logic (KIM2)
Sub–edit  Conditions Outcome
KIM2-1 Input tumour record that matches another Input tumour record where T1=T1 AND T2=T2 AND T3=T3. Family rejected52
Table
Feedback report messages (KIM2)
Sub–edit  Text Type
KIM2-1 Family rejected: more than one Input tumour record with the same Tumour reporting province/territory, Tumour patient identification number and Tumour reference number. Core error
Table
Revision (KIM2)
Year Description
2004 Edit renamed: Formerly known as Input Match Edit No.2.

KIM3

Purpose

This edit enforces the submission rules regarding the addition of a patient record.

Table
Referenced fields (KIM3)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P4 1 Patient record type PRECTYPE
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Tumour patient identification number TPIN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE

Business fields

For Add Patient records
  • There must be at least one Add Tumour record with identical Reporting province/territory and Patient identification number and a blank CCR identification number within the same data submission.
  • There cannot be any Add Tumour record with identical Reporting province/territory and Patient identification number and a reported CCR identification number within the same data submission.
  • There cannot be any Update or Delete Tumour record with identical Reporting province/territory and Patient identification number within the same data submission.
Table
Edit logic KIM3)
Sub–edit  Conditions Outcome
KIM3-1 Input patient record where P4='1' that matches no Input tumour record where T5='1' AND T1=P1 AND T2=P2. Family rejected53
KIM3-2 Input patient record where P4='1' that matches an Input tumour record where T5='1' AND T1=P1 AND T2=P2 AND T4 IS NOT NULL. Family rejected53
KIM3-3 Input patient record where P4='1' that matches an Input tumour record where T5 IN ['2','3'] AND T1=P1 AND T2=P2. Family rejected53
Table
Feedback report messages (KIM3)
Sub–edit  Text Type
KIM3-1 Family rejected: Add Patient record does not match any Add Tumour record. Core error
KIM3-2 Family rejected: Add Patient record matches an Add Tumour record with CCR identification number. Core error
KIM3-3 Family rejected: Add Patient record matches an Update or Delete Tumour record. Core error
Table
Revision (KIM3)
Year Description
2004 Edit renamed: Formerly known as Input Match Edit No.3.

KIM4

Purpose

This edit enforces the submission rules regarding the deletion of a patient record.

Table
referenced fields (KIM4)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPROV
P2 12 Patient identification number PPIN
P4 1 Patient record type PRECTYPE
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Tumour patient identification number TPIN
T5 1 Tumour record type TRECTYPE

Business rules

For Delete Patient records
  • There must be at least one Delete Tumour record with identical Reporting province/territory and Patient identification number within the same data submission.
  • There cannot be any Add or Update Tumour record with identical Reporting province/territory and Patient identification number within the same data submission.
Table
Edit logic (KIM4)
Sub–edit  Conditions Outcome
KIM4-1 Input patient record where P4='3' that matches no Input tumour record where T5='3' AND P1=T1 AND P2=T2. Family rejected53
KIM4-2 Input patient record where P4='3' that matches Input tumour record where T5 IN ['1','2'] AND P1=T1 AND P2=T2. Family rejected53
Table
Feedback report messages (KIM4)
Sub–edit  Text Type
KIM4-1 Delete Patient record does not match any Delete Tumour record. Core error
KIM4-2 Family rejected: Delete Patient record matches an Add or Update Tumour record. Core error
Table
Revision (KIM4)
Year Description
2004 Edit renamed: Formerly known as Input Match Edit No.4.
Business rules changed: CCR identification number has been removed from the edit since it is equivalent to Reporting province/territory – Patient identification number combination.

KIM5

Purpose

This edit enforces the submission rules regarding the addition of a tumour record.

Table
Referenced fields (KIM5)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P4 1 Patient record type PRECTYPE
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Tumour patient identification number TPIN
T4 9 CCR Identification number CCR_ID
T5 1 Tumour record type TRECTYPE

Business rules

For Add Tumour records without CCR identification number
  • There must be an Add Patient record with identical Reporting province/territory and Patient identification number within the same data submission.
  • There cannot be any Update54 Patient records with identical Reporting province/territory and Patient identification number within the same data submission.
Table
Edit logic (KIM5)
Sub–edit  Conditions Outcome
KIM5-1 Input tumour record where T5='1' AND T4 IS NULL that matches no Input patient record where P4='1' AND P1=T1 AND P2=T2. Family rejected55
KIM5-2 Input tumour record where T5='1' AND T4 IS NULL that matches Input patient record where P4='2' AND P1=T1 AND P2=T2. Family rejected55
Table
Feedback report messages (KIM5)
Sub–edit Text Type
KIM5-1 Family rejected: Add Tumour record without CCR_ID does not match an Add Patient record. Core error
KIM5-2 Family rejected: Add Tumour record without CCR_ID matches an Update Patient record. Core error
Table
Revision (KIM5)
Year Description
2004 Edit renamed: Formerly known as Input Match Edit No.6.

3.6.2 Key base match edits

The purpose of the key base match edits is to ensure that input patient and tumour records respect the actual state of the CCR in terms of matching keys.

At this level, the following fields are used as keys:

  • Patient record: CCR identification number, reporting province/territory and patient identification number.
  • Tumour record: CCR identification number, reporting province/territory, patient identification number and tumour reference number.

The following table summarizes the purpose of each individual edit of this category.

Table 29
Base match edits summary
Edit name Purpose
KBM1 Ensures that no duplicate Patient keys are posted to the CCR.
KBM2 Ensures that Update or Delete Patient record keys match a Base Patient record.
KBM3 Ensures that no duplicate Tumour keys are posted to the CCR.
KBM4 Ensures that an Add Tumour record with CCR identification number matches a Base patient record owned by the Reporting province/territory.
KBM5 Ensures that Update or Delete Tumour record keys match a Base tumour record.

Important note

When a key base match edit fails, the conflicting base record (if any), is included in the detailed feedback report for easier error correction.

Writing conventions throughout the following edit descriptions:

  • Expression "base patient/tumour record" means a patient/tumour record already in the CCR.
  • Expression "add/update/delete/input patient/tumour record" means a patient/tumour record within the data submission.
  • Unless specified otherwise, field numbers prefixed with "I" are input fields and field numbers prefixed with "B" are Base fields. 
    Example: IT5 is the Tumour record type field on an input tumour record.
    Example: IP1 is the Reporting province/territory field on an input patient record

KBM1

Purpose

This edit ensures that no duplicate patient keys are posted to the CCR.

Table
Referenced fields (KBM1)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P4 1 Patient record type PRECTYPE

Business rules

For Add Patient records
  • There must not be a Base patient record with identical Reporting province/territory and Patient identification number.
Table
Edit logic (KBM1)
Sub–edit  Conditions Outcome
KBM1-1 Input patient record where IP4='1' that matches a Base patient record where IP1=BP1 AND IP2=BP2. Record rejected
Table
Feedback report messages (KBM1)
Sub–edit  Text Type
KBM1-1 A Base patient record with identical reporting province/Territory and Patient identification number already exists. Core error
Table
Revision (KBM1)
Year Description
2004 Edit renamed: Formerly known as Correlation Edit No.25.

KBM2

Purpose

This edit ensures that update or delete patient record keys match a base patient record.

Table
Referenced fields (KBM2)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P3 9 CCR identification number CCR_ID
P4 1 Patient record type PRECTYPE

Business rules

For Update or Delete Patient records
  • There must be a Base patient record with identical Reporting province/territory, Patient identification number and CCR identification number.
Table
Edit logic (KBM2)
Sub–edit  Conditions Outcome
KBM2-1 Input patient record where IP4 IN ['2','3'] that matches a Base patient record where IP1=BP1 AND IP2<>BP2 AND IP3=BP3. Record rejected
KBM2-2 Input patient record where IP4 IN ['2','3'] that matches a Base patient record where IP1=BP1 AND IP2=BP2 AND IP3<>BP3. Record rejected
KBM2-3 Input patient record where IP4 IN ['2','3'] that matches a Base patient record where IP1<>BP1 AND IP3=BP3. Record rejected
KBM2-4 Input patient record where IP4 IN ['2','3'] that match no Base patient record where (IP1=BP1 AND IP2=BP2) OR IP3=BP3. Record rejected
Table
Feedback report messages (KBM2)
Sub–edit  Text Type
KBM2-1 Based on the CCR identification number, the Patient identification number is incorrect. Core error
KBM2-2 Based on the Reporting province/territory and the Patient identification number, the CCR identification number is incorrect. Core error
KBM2-3 Based on the CCR identification number, the Patient is owned by another province/territory. Core error
KBM2-4 No matching Patient record found in the CCR. Core error
Table
Revision (KBM2)
Year Description
2004 Edit renamed: Formerly known as Correlation Edit No.26.

KBM3

Purpose

This edit ensures that no duplicate tumour keys are posted to the CCR.

Table
Referenced fields (KBM3)
Field Length Description Acronym
T1 2 Tumour reporting province/Territory TREPPROV
T2 12 Tumour patient identification number TPIN
T3 9 Tumour reference number TTRN
T5 1 Tumour record type TRECTYPE

Business rules

For Add Tumour records
  • There must not be a Base tumour record with an identical Reporting province/territory, Patient identification number and Tumour reference number.
Table
Edit logic (KBM3)
Sub–edit  Conditions Outcome
KBM3-1 Input tumour record where IT5='1' that matches a Base tumour record where IT1=BT1 AND IT2=BT2 AND IT3=BT3. Record rejected
Table
Feedback report messages (KBM3)
Sub–edit  Text Type
KBM3-1 A Base tumour record with identical Reporting province/territory, Patient identification number and Tumour reference number already exists. Core error
Table
Revision (KBM3)
Year Description
2004 Edit renamed: Formerly known as Correlation Edit No.32 – Part 1.

KBM4

Purpose

This edit ensures that an add tumour record with CCR identification number matches a base patient record owned by the reporting province/territory.

Table
Referenced fields (KBM4)
Field Length Description Acronym
T1 2 Tumour reporting province/territory TREPPROV
T2 9 Tumour patient identification number TPIN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
P1 2 Patient reporting province/territory PREPPROV
P2 9 Patient identification number PPIN
P3 9 CCR identification number CCR_ID

Business rules

For Add Tumour records with CCR identification number
  • There must be a Base patient record with the same Reporting province/territory, Patient identification number and CCR identification number.
Table
Edit logic (KBM4)
Sub–edit  Conditions Outcome
KBM4-1 Input tumour record where IT5='1' AND IT4 IS NOT NULL that matches a Base patient record where IT1=BP1 AND IT2<>BP2 AND IT4=BP3. Record rejected
KBM4-2 Input tumour record where IT5='1' AND IT4 IS NOT NULL that matches a Base patient record where IT1=BP1 AND IT2=BP2 AND IT4<>BP3. Record rejected
KBM4-3 Input tumour record where IT5='1' AND IT4 IS NOT NULL that matches a Base patient record where IT1<>BP1 AND IT4=BP3. Record rejected
KBM4-4 Input tumour record where IT5='1' AND IT4 IS NOT NULL that matches no Base patient record where (IT1=BP1 AND IT2=BP2) OR IT4=BP3. Record rejected
Table
Feedback report messages (KBM4)
Sub–edit  Text Type
KBM4-1 Based on CCR identification number, Patient identification number is incorrect. Core error
KBM4-2 Based on Reporting province/territory and Patient identification number, CCR identification number is incorrect. Core error
KBM4-3 Based on CCR identification number, the Patient record belongs to another province/territory. Core error
KBM4-4 Matching Base patient record not found. Core error
Table
Revision (KBM4)
Year Description
2004 Edit renamed: Formerly known as Correlation Edit No.32 – Part 2 and Additional rules for updating the CCR #3.
Business rules changed: This aggregated edit is now using the Base Patient records.

KBM5

Purpose

This edit ensures that update or delete tumour record keys match a base tumour record.

Table
Referenced fields (KBM5)
Field Length Description Acronym
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Tumour patient identification number TPIN
T3 9 Tumour reference number TTRN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE

Business rules

For Update and Delete Tumour records
  • There must be a Base tumour record with identical Reporting province/territory, Patient identification number, Tumour reference number and CCR identification number.
Table
Edit logic (KBM5)
Sub–edit  Conditions Outcome
KBM5-1 Input tumour record where IT5 IN ['2','3'] that matches a Base tumour record where IT1=BT1 AND IT2=BT2 AND IT3=BT3 AND IT4<>BT4. Record rejected
KBM5-2 Input tumour record where IT5 IN ['2','3'] that matches a Base tumour record where IT1=BT1 AND IT2<>BT2 AND IT4=BT4. Record rejected
KBM5-3 Input tumour record where IT5 IN ['2','3'] that matches no Base tumour record where IT1=BT1 AND IT2=BT2 AND IT3=BT3 but matches a Base tumour record where IT1=BT1 AND IT2=BT2 AND IT3<>BT3 AND IT4=BT4. Record rejected
KBM5-4 Input tumour record where IT5 IN ['2','3'] that matches no Base tumour record where (IT1=BT1 AND IT2=BT2) OR (IT1=BT1 AND IT4=BT4). Record rejected
Table
Feedback report messages (KBM5)
Sub–edit  Text Type
KBM5-1 Based on Reporting province/territory, Patient identification number and Tumour reference number, CCR identification number is incorrect. Core error
KBM5-2 Based on CCR identification number and Reporting province/territory, Patient identification number is incorrect. Core error
KBM5-3 Matching Base tumour record not found. Tumour reference number may be incorrect. Core error
KBM5-4 Matching Base tumour record not found. Core error
Table
Revision (KBM5)
Year Description
2004 Edit renamed: Formerly known as Correlation Edit No.33.

3.6.3 Data item match edits

The purpose of the data item match edits is to enforce the business rules between data items (other than keys) found on different records.

The following table summarizes the purpose of each individual edit of this category.

Table 30
Data item match edits summary
Edit name Purpose
DIM1 Ensures that Date of diagnosis and Date of birth are coherent and within time frame.
DIM2 Ensures that Date of diagnosis and Date of death are coherent.
DIM3 Ensures that Method of diagnosis accurately reflects the relationship between Date of diagnosis and Date of death.
DIM4 Ensures that Method used to establish the date of diagnosis accurately reflects the relationship between Date of diagnosis and Date of death.
DIM5 Ensures that patient Sex and tumour Topography are coherent.
DIM6 Ensures that no "duplicate" tumour records are created for any given Patient record.

Important notes:

Writing conventions throughout the following edit descriptions:

  • Expression "base patient/tumour record" means a patient/tumour record already in the CCR.
  • Expression "add/update/delete/input patient/tumour record" means a patient/tumour record within the data submission.
  • Unless specified otherwise, field numbers prefixed with "I" are input fields and field numbers prefixed with "B" are Base fields.
    Example: IT5 is the Tumour record type field on an input tumour record.
    Example: IP1 is the Reporting province/territory field on an input patient record

These edits only consider input records that have neither core fatal errors nor core errors. (See section 3.1.7 Message types for information about different types of errors.) Since DIM edits find core errors, an input record that fails a given DIM edit will automatically be excluded from all subsequent DIM edits.

These edits must be performed in a specific order (see below).

When a data item match edit fails, the conflicting base record (patient or tumour, if any) is included in the detailed feedback report for easier error correction.

3.6.3.1 Special order of execution

Data item match edits must be performed horizontally. That is, all sub-edits with the same number must be processed together. Example: instead of processing all sub-edits from DIM1 before processing all sub-edits from DIM2 (vertically), all sub-edits DIMX-1 must be processed before processing sub-edits DIMX-2 (horizontally). Although the sub-edits within a horizontal group can be processed in any order, these groups of sub-edits must be processed in a very specific order.

Step 1: All sub-edits that consider only input records (Sub-edits number 1 and 4).

Step 2: All sub-edits that consider base patient records that are not updated by input patient records (Sub-edits number 2 and 5).

Step 3: All sub-edits that consider base tumour records that are not updated nor deleted by input tumour records must be processed (Sub-edit number 3 and 6).

The ordering is essential to guarantee the effectiveness of these edits since each step builds the necessary conditions for the next one. The following table summarizes the special order of execution.

Table 31
Data item match edits special order of execution
Edit DIM1 DIM2 DIM3 DIM4 DIM5 DIM6
Sub-edit 1 2 3 4 5 6 1 2 3 1 2 3 4 5 6 1 2 3 4 5 6 1 2 3 1 2 3 4 5 6
Step 1 x     x     x     x     x     x     x     x     x     x    
Step 2   x     x     x     x     x     x     x     x     -     -  
Step 3     x     x     x     x     x     x     x     x     x     x

DIM1

Purpose

This edit ensures that date of diagnosis and date of birth are coherent and within time frame.

Table
Referenced fields (DIM1)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P3 9 CCR identification number CCR_ID
P4 1 Patient record type PRECTYPE
P11 8 Date of birth PDATBIR
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Patient identification number TPIN
T3 9 Tumour reference number TTRN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
T12 8 Date of diagnosis TDATDIAG

Business rules

Date of diagnosis must be on or after the Date of birth.
  • Year of Date of diagnosis and year of the Date of birth must not be more than 117 years apart.

Edit logic

Important notes:

  • These sub-edits must be processed in a specific order. See Section - 3.6.3.1 Special order of execution for more details.
  • Partially known dates must be compared using the highest common level of precision.

    Example: If Date1 = YYYYMMDD and Date2 = YYYYMM99 then dates must be compared using the year and month only. Thus, for the purpose of the following sub-edits, '20031002' and '20031099' are equal.
Table
Edit logic (DIM1)
Sub–edit  Conditions Outcome
DIM1-1 Core error-free56 Input tumour record where IT5 IN ['1','2'] that matches a Core error-free Input patient record where IP4 IN ['1','2'] AND IP1=IT1 AND IP2=IT2 AND IP11<>'99999999' AND IT12<IP11 (see note above). Tumour record rejected
DIM1-2 Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4 IS NOT NULL that matches no Core error-free Input patient record where IP4='2' AND IP3=IT4 but matches a Base patient record where BP3=IT4 AND BP11<>'99999999' AND IT12<BP11 (see note above). Tumour record rejected
DIM1-3 Core error-free Input patient record where IP4='2' that matches a Base tumour record where IP3=BT4 AND IP11<>'99999999' AND BT12<IP11 (see note above) that matches no Core error-free Input Tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3. Patient record rejected
DIM1-4 Core error-free Input tumour record where IT5 IN ['1','2'] that matches a Core error-free Input patient record where IP4 IN ['1','2'] AND IP1=IT1 AND IP2=IT2 AND IP11<>'99999999' AND IT12.YEAR>(IP11.YEAR+117). Tumour record rejected
DIM1-5 Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4 IS NOT NULL that matches no Core error-free Input patient record where IP4='2' AND IP3=IT4 but matches a Base Patient record where BP3=IT4 AND BP11<>'99999999' AND IT12.YEAR>(BP11.YEAR+117). Tumour record rejected
DIM1-6 Core error-free Input patient record where IP4='2' that matches a Base tumour record where IP3=BT4 AND IP11<>'99999999' AND BT12.YEAR>(IP11.YEAR+117) that matches no Core error-free Input Tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3. Patient record rejected
Table
Feedback report messages (DIM1)
Sub–edit  Text Type
DIM1-1 Date of diagnosis is before Date of birth on matching Input patient record. Core error
DIM1-2 Date of diagnosis is before Date of birth on matching Base patient record. Core error
DIM1-3 Date of birth is after Date of diagnosis on matching Base tumour record. Core error
DIM1-4 Date of diagnosis is more than 117 years after Date of birth on matching Input patient record. Core error
DIM1-5 Date of diagnosis is more than 117 years after Date of birth on matching Base patient record. Core error
DIM1-6 Date of birth is more than 117 years before Date of diagnosis on matching Base tumour record. Core error
Table
Revision (DIM1)
Year Description
2004 Edit renamed: Formerly known as Correlation Edit No.28.

DIM2

Purpose

This edit ensures that date of diagnosis and date of death are coherent.

Table
Referenced fields (DIM2)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P3 9 CCR identification number CCR_ID
P4 1 Patient record type PRECTYPE
P14 8 Date of death PDATDEA
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Patient identification number TPIN
T3 9 Tumour reference number TTRN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
T12 8 Date of diagnosis TDATDIAG

Business rules

Tumour Date of diagnosis cannot be after the patient Date of death.

Edit logic

Important notes:

  • These sub-edits must be processed in a specific order. See Section 3.6.3.1 Special order of execution for more details.
  • Partially known dates must be compared using the highest common level of precision.

    Example: If Date1 = YYYYMMDD and Date2 = YYYYMM99 then dates must be compared using the year and month only. Thus, for the purpose of the following sub-edits, '20031002' and '20031099' are equal.
Table
Edit logic (DIM2)
Sub–edit  Conditions Outcome
DIM2-1 Core error-free56 Input tumour record where IT5 IN ['1','2'] that matches a Core error-free Input patient record where IP4 IN ['1','2'] AND IP1=IT1 AND IP2=IT2 AND IP14 NOT IN ['99999999','00000000'] AND IP14<IT12 (see note above). Tumour record rejected
DIM2-2 Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4 IS NOT NULL that matches no Core error-free Input patient record where IP4='2' AND IP3=IT4 but matches a Base Patient record where BP3=IT4 AND BP14 NOT IN ['99999999','00000000'] AND BP14<IT12 (see note above). Tumour record rejected
DIM2-3 Core error-free Input patient record where IP4='2' AND IP14 NOT IN ['99999999','00000000'] that matches a Base tumour record where IP3=BT4 AND BT12>IP14 (see note above) that matches no Core error-free Input tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3. Patient record rejected
Table
Feedback report messages (DIM2)
Sub–edit  Text Type
DIM2-1 Date of diagnosis is after Date of death on matching Input patient record. Core error
DIM2-2 Date of diagnosis is after Date of death on matching Base patient record. Core error
DIM2-3 Date of death is before Date of diagnosis on matching Base tumour record. Core error
Table
Revision (DIM2)
Year Description
2004 Edit renamed: Formerly known as Correlation Edit No.29.

DIM3

Purpose

This edit ensures that the method of diagnosis accurately reflects the relationship between the date of diagnosis and the date of death.

Table
Referenced fields (DIM3)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P3 9 CCR identification number CCR_ID
P4 1 Patient record type PRECTYPE
P14 8 Date of death PDATDEA
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Tumour patient identification number TPIN
T3 9 Tumour reference number TTRN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
T11 1 Method of diagnosis TMETDIAG
T12 8 Date of diagnosis TDATDIAG
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable

Business rules

For tumours diagnosed between 1992 and 2003
  • Method of diagnosis cannot be 'Death certificate only (DCO)' or 'Autopsy' when the Date of death indicates that the 'Patient is not known to have died'.
  • Method of diagnosis can be anything when Date of death is unknown or equal to Date of diagnosis.
  • Method of diagnosis cannot be 'Death certificate only (DCO)' when Date of diagnosis is before Date of death.57

Edit logic

Important notes:

  • These sub-edits must be processed in a specific order. See Section 3.6.3.1 Special order of execution for more details.
  • Partially known dates must be compared using the highest common level of precision.

    Example: If Date1 = YYYYMMDD and Date2 = YYYYMM99 then dates must be compared using the year and month only. Thus, for the purpose of the following sub-edits, '20031002' and '20031099' are equal.
Table
Edit logic (DIM3)
Sub–edit  Conditions Outcome
DIM3-1 Core error-free56 Input tumour record where IT5 IN ['1','2'] AND IT11 IN ['2','6'] AND IT12.YEAR>=1992 AND IT12.YEAR<=2003 that matches a Core error-free Input patient record where IP4 IN ['1','2'] AND IP1=IT1 AND IP2=IT2 AND IP14='00000000' Tumour record rejected
DIM3-2 Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4 IS NOT NULL AND IT11 IN ['2','6'] AND IT12.YEAR>=1992 AND IT12.YEAR<=2003 that matches no Core error-free Input patient record where IP4='2' AND IP3=IT4 but matches a Base patient record where BP3=IT4 AND BP14='00000000' Tumour record rejected
DIM3-3 Core error-free Input patient record where IP4='2' AND IP14='00000000' that matches a Base tumour record where IP3=BT4 AND BT11 IN ['2','6'] AND BT12.YEAR>=1992 AND BT12.YEAR<=2003 that matches no Core error-free Input tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3. Patient record rejected
DIM3-4 Core error-free Input tumour record where IT5 IN ['1','2'] AND IT11='6' AND IT12.YEAR>=1992 AND IT12.YEAR<=2003 that matches a Core error-free Input patient record where IP4 IN ['1','2'] AND IP1=IT1 AND IP2=IT2 AND IP14 NOT IN ['00000000', '99999999'] AND IP14>IT12 (see note above). Tumour record rejected
DIM3-5 Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4 IS NOT NULL AND IT11='6' AND IT12.YEAR>=1992 AND IT12.YEAR<=2003 that matches no Core error-free Input patient record where IP4='2' AND IP3=IT4 but matches a Base patient record where BP3=IT4 AND BP14 NOT IN ['00000000', '99999999'] AND BP14>IT12 (see note above). Tumour record rejected
DIM3-6 Core error-free Input patient record where IP4='2' AND IP14 NOT IN ['00000000', '99999999'] that matches a Base tumour record where IP3=BT4 AND BT11='6' AND BT12.YEAR>=1992 AND BT12.YEAR<=2003 AND BT12<IP14 (see note above) that matches no Core error-free Input tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3. Patient record Rejected
Table
Feedback report messages (DIM3)
Sub–edit  Text Type
DIM3-1 Method of diagnosis cannot be 'Death certificate only (DCO)' or 'Autopsy' when the Date of death indicates that the 'Patient is not known to have died' on matching Input patient record. Core error
DIM3-2 Method of diagnosis cannot be 'Death certificate only (DCO)' or 'Autopsy' when the Date of death indicates that the 'Patient is not known to have died' on matching Base patient record. Core error
DIM3-3 Date of death cannot indicate that patient is alive when Method of diagnosis is 'Death certificate only (DCO)' or 'Autopsy' on a matching Base tumour record. Core error
DIM3-4 Method of Diagnosis cannot be 'Death certificate only (DCO)' when Date of diagnosis is before Date of death on matching Input patient record. Core error
DIM3-5 Method of diagnosis cannot be 'Death certificate only (DCO)' when the Date of diagnosis is before Date of death on matching Base patient record. Core error
DIM3-6 Date of death cannot be after Date of diagnosis on a matching Base tumour record where Method of diagnosis is 'Death certificate only (DCO)'. Core error
Table
Revision (DIM3)
Year Description
2004 Edit renamed: Formerly known as Correlation Edit No.30 – Part 1.

DIM4

Purpose

This edit ensures that the method used to establish the date of diagnosis accurately reflects the relationship between date of diagnosis and date of death.

Table
Referenced fields (DIM4)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P3 9 CCR identification number CCR_ID
P4 1 Patient record type PRECTYPE
P14 8 Date of death PDATDEA
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Tumour patient identification number TPIN
T3 9 Tumour reference number TTRN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
T11 1 Method of diagnosis TMETDIAG
T12 8 Date of diagnosis TDATDIAG
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T24 1 Method used to establish the date of diagnosis TMETHUSED

Business rules

For tumours diagnosed in 2004 and onwards
  • Method used to establish the date of diagnosis cannot be 'Autopsy only' or 'Death certificate only (DCO)' when Date of death indicates that the 'Patient is not known to have died' or when Date of diagnosis is before Date of death.
  • Method used to establish the date of diagnosis can be anything when Date of death is unknown or equal to Date of diagnosis.

Edit logic

Important notes:

  • These sub-edits must be processed in a specific order. See Section 3.6.3.1 Special order of execution for more details.
  • Partially known dates must be compared using the highest common level of precision.

    Example: If Date1 = YYYYMMDD and Date2 = YYYYMM99 then dates must be compared using the year and month only. Thus, for the purpose of the following sub-edits, '20031002' and '20031099' are equal.
Table
Edit logic (DIM4)
Sub–edit  Conditions Outcome
DIM4-1 Core error-free56 Input tumour record where IT5 IN ['1','2'] AND IT12.YEAR>=2004 AND IT24 IN ['3','8'] that matches a Core error-free Input patient record where IP4 IN ['1','2'] AND IP1=IT1 AND IP2=IT2 AND IP14='00000000' Tumour record rejected
DIM4-2 Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4 IS NOT NULL AND IT12.YEAR>=2004 AND IT24 IN ['3','8'] that matches no Core error-free Input patient record where IP4='2' AND IP3=IT4 but matches a Base patient record where BP3=IT4 AND BP14='00000000'. Tumour record rejected
DIM4-3 Core error-free Input patient record where IP4='2' AND IP14='00000000' that matches a Base tumour record where IP3=BT4 AND BT12.YEAR>=2004 AND BT24 IN ['3','8'] that matches no Core error-free Input tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3. Patient record rejected
DIM4-4 Core error-free Input tumour record where IT5 IN ['1','2'] AND IT12.YEAR>=2004 AND IT24 IN ['3','8'] that matches a Core error-free Input patient record where IP4 IN ['1','2'] AND IP1=IT1 AND IP2=IT2 AND IP14 NOT IN ['00000000', '99999999'] AND IP14>IT12 (see note above). Tumour record rejected
DIM4-5 Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4 IS NOT NULL AND IT12.YEAR>=2004 AND IT24 IN ['3','8'] that matches no Core error-free Input patient record where IP4='2' AND IP3=IT4 but matches a Base patient record where BP3=IT4 AND BP14 NOT IN ['00000000', '99999999'] AND BP14>IT12 (see note above). Tumour record rejected
DIM4-6 Core error-free Input patient record where IP4='2' AND IP14 NOT IN ['00000000', '99999999'] that matches a Base tumour record where IP3=BT4 AND BT12.YEAR>=2004 AND BT12<IP14 (see note above) AND BT24 IN ['3','8'] that matches no Core error-free Input tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3. Patient record rejected
Table
Feedback report messages (DIM4)
Sub–edit  Text Type
DIM4-1 Method used to establish the date of diagnosis cannot be 'Autopsy Only' or 'Death certificate only (DCO)' when Date of death indicates that the 'Patient is not known to have died' on matching Input Patient record. Core error
DIM4-2 Method used to establish the date of diagnosis cannot be 'Autopsy Only' or 'Death certificate only (DCO)' when Date of death indicates that the 'Patient is not known to have died' on matching Base patient record. Core error
DIM4-3 Date of death cannot indicate that 'Patient is not known to have died' when Method used to establish the date of diagnosis is 'Autopsy Only' or 'Death certificate only (DCO)' on a matching Base tumour record. Core error
DIM4-4 Method used to establish the date of diagnosis cannot be 'Autopsy Only' or 'Death certificate only (DCO)' when Date of diagnosis is before Date of death on matching Input Patient record. Core error
DIM4-5 Method used to establish the date of diagnosis cannot be 'Autopsy Only' or 'Death certificate only (DCO)' when Date of diagnosis is before Date of death on matching Base patient record. Core error
DIM4-6 Date of death cannot be after Date of Diagnosis on matching Base tumour record where Method used to establish the date of diagnosis is 'Autopsy Only' or 'Death certificate only (DCO)' Core error
Table
Revision (DIM4)
Year Description
2004 Edit renamed: Formerly known as Correlation Edit No.30 – Part 2.

DIM5

Purpose

This edit ensures that patient sex and tumour topography are coherent.

Table
Referenced fields (DIM5)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P3 9 CCR identification number CCR_ID
P4 1 Patient record type PRECTYPE
P10 1 Sex PSEX
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Tumour patient identification number TPIN
T3 9 Tumour reference number TTRN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
T15 4 ICD-O-2/3 Topography TICD_O2T

Business rules

  • Tumours diagnosed in female organ must be associated with female patient. Female organs are: ICD-O-2/3 Topography: C510-C589.
  • Tumours diagnosed in male organ must be associated with male patient. Male organs are: ICD-O-2/3 Topography: C600-C639.

Edit logic

Important notes

These sub-edits must be processed in a specific order. See Section – 3.6.3.1 Special order of execution.

DIM5

Table
Edit logic (DIM5)
Sub–edit  Conditions Outcome
DIM5-1 (Core error-free56 Input tumour record where IT5 IN ['1','2'] AND IT15 IN [ICD-O-2/3 Topography codes associated to female organ] that matches a Core error-free Input patient record where IP4 IN ['1','2'] AND IP1=IT1 AND IP2=IT2 AND IP10 IN ['1','9'])
OR
(Core error-free Input tumour record where IT5 IN ['1','2'] AND IT15 IN [ICD-O-2/3 Topography codes associated to male organ] that matches a Core error-free Input patient record where IP4 IN ['1','2'] AND IP1=IT1 AND IP2=IT2 AND IP10 IN ['2','9'])
Tumour record rejected
DIM5-2 (Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4 IS NOT NULL AND IT15 IN [ICD-O-2/3 Topography codes associated to female organ] that matches no Core error-free Input patient record where IP4='2' AND IP3=IT4 but matches a Base patient record where BP3=IT4 AND BP10 IN ['1','9'])
OR
(Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4 IS NOT NULL AND IT15 IN [ICD-O-2/3 Topography codes associated to male organ] that matches no Core error-free Input patient record where IP4='2' AND IP3=IT4 but matches a Base patient record where BP3=IT4 AND BP10 IN ['2','9'])
Tumour record rejected
DIM5-3 (Core error-free Input patient record where IP4='2' AND IP10 IN ['1','9'] that matches a Base tumour record where IP3=BT4 AND BT15 IN [ICD-O-2/3 Topography codes associated to female organ] that matches no Core error-free Input tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3)
OR
(Core error-free Input patient record where IP4='2' AND IP10 IN ['2','9'] that matches a Base tumour record where IP3=BT4 AND BT15 IN [ICD-O-2/3 Topography codes associated to male organ] that matches no Core error-free Input tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3)
Patient record Rejected
Table
Feedback report messages (DIM5)
Sub–edit  Text Type
DIM5-1 ICD-O-2/3 Topography does not agree with Sex code on matching Input patient record. Core error
DIM5-2 ICD-O-2/3 Topography does not agree with Sex code on matching Base patient record. Core error
DIM5-3 Sex code does not agree with ICD-O-2/3 Topography on a matching Base tumour record. Core error
Table
Revision (DIM5)
Year Description
2004 Edit renamed: Formerly known as COR31.
Business rules changed: Verification is now performed on ICD-O-3 values only.

DIM6

Purpose

This edit ensures that no "duplicate" tumour records are created for any given patient record (1992-2006 data years only). As of 2007 the CCR has adopted SEER rules. New edits will be implemented to adhere to these new rules.

Table
Referenced fields (DIM6)
Field Length Description Acronym
T1 2 Tumour reporting province/territory TREPPROV
T12.YEAR 4 First 4 digits of Date of diagnosis (year of date of diagnosis) Not applicable
T2 12 Tumour patient identification number TPIN
T3 9 Tumour reference number TTRN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
T15 4 ICD-O-2/3 Topography TICD_O2T
T15.SITE 3 First 3 digits of T15 (ICD-O-2/3 Topography site) Not applicable
T15.SUBSITE 1 Last digit of T15 (ICD-O-2/3 Topography sub-site) Not applicable
T19 1 Laterality TLATERAL
T21 4 ICD-O-3 Histology TICD_O3H

Business rules

Definitions
  • Tumours with "equivalent topographies" are tumours that have:
    • The same ICD-O-3 sites56 and sub-sites59or
    • The same ICD-O-3 sites but at least one sub-site is 'Overlapping' (8) or 'NOS' (9) or
    • Overlapping topographies based on Equivalent Topographies for Overlapping and Unspecified Sites63 concordance table.
  • Tumours with "equivalent histologies" are tumours that have:
    • The same ICD-O-3 Histology code or
    • The same histological group based on Equivalent Histologies56 concordance table.
  • A Patient may have multiple Hematopoietic tumours (tumours with ICD-O-3 Histology codes in range 9590-9989) only if they have non-equivalent histologies. (Thus, a patient may not have more than one Hematopoietic tumour in each equivalent histology group, regardless of their respective topography and laterality.)
  • A Patient may have multiple non-Hematopoietic tumours with equivalent topographies and equivalent histologies only if they are found on paired organs with specific (right, left one side involved, origin not specified and bilateral) and different laterality.
See Appendix D – Multiple primary tumours rules for CCR for more detail.

Important notes

These sub-edits must be processed in a specific order. See Section - 3.6.3.1 Special order of execution

Table
Edit logic DIM6)
Sub–edit  Conditions Outcome
DIM6–1 Core error-free56 Input tumour record (say A) where A.T5 IN ['1','2'] AND A.T21 IN ['9590'-'9989'] that matches a Core error-free Input tumour record (say B) where B.T5 IN ['1','2'] AND A.T1=B.T1 AND A.T2=B.T2 AND A.T3<>B.T3 AND B.T21 IN ['9590'-'9989'] AND (A.T21=B.T21 OR (A.T21 and B.T21 are equivalent based on reference table Equivalent Histologies)). Tumour records A and B rejected
DIM6-2 Not applicable61 Not applicable
DIM6-3 Core error-free Input tumour record (say A) where A.T5 IN ['1','2'] AND A.T4 IS NOT NULL AND A.T21 IN ['9590'-'9989'] that matches a Base Tumour record (say B) where A.T4=B.T4 AND (A.T1<>B.T1 OR A.T3<>B.T3) AND B.T21 IN ['9590'-'9989'] AND (A.T21=B.T21 OR (A.T21 and B.T21 are equivalent based on reference table Equivalent Histologies)) that matches no Core error-free Input tumour record (say C) where C.T5 IN ['2','3'] AND C.T1=B.T1 AND C.T2=B.T2 AND C.T3=B.T3. Tumour record A rejected
DIM6-4 Core error-free Input tumour record (say A) where A.T5 IN ['1','2'] that matches a Core error-free Input tumour record (say B) where B.T5 IN ['1','2'] AND A.T1=B.T1 AND A.T2=B.T2 AND A.T3<>B.T3 AND NOT (A.T21 IN ['9590'-'9989'] AND B.T21 IN ['9590'-'9989']) AND (A.T15=B.T15 OR (A.T15.SITE=B.T15.SITE AND (A.T15.SUBSITE IN ['8','9'] OR B.T15.SUBSITE IN ['8','9'])) OR (A.T15 and B.T15 are equivalent based on Equivalent Topographies for Overlapping and Unspecified Sites)) AND (A.T21=B.T21 OR (A.T21 and B.T21 are equivalent based on Equivalent Histologies)) AND (A.T19 IN ['9','0'] OR B.T19 IN ['9','0'] OR A.T19=B.T19) Tumour records A and B rejected
DIM6-5 Not applicable59 Not applicable
DIM6-6 Core error-free Input tumour record (say A) where A.T5 IN ['1','2'] AND A.T4 IS NOT NULL that matches a Base tumour record (say B) where A.T4=B.T4 AND (A.T1<>B.T1 OR A.T3<>B.T3) AND NOT (A.T21 IN ['9590'-'9989'] AND NOT B.T21 IN ['9590'-'9989']) AND (A.T15=B.T15 OR (A.T15.SITE=B.T15.SITE AND (A.T15.SUBSITE IN ['8','9'] OR B.T15.SUBSITE IN ['8','9'])) OR (A.T15 and B.T15 are equivalent based on Equivalent Topographies for Overlapping and Unspecified Sites)) AND (A.T21=B.T21 OR (A.T21 and B.T21 are equivalent based on Equivalent Histologies)) AND (A.T19 IN ['9','0'] OR B.T19 IN ['9','0'] OR A.T19=B.T19) that matches no Core error-free Input Tumour record (say C) where C.T5 IN ['2','3'] AND C.T1=B.T1 AND C.T2=B.T2 AND C.T3=B.T3. Tumour record A rejected
Table
Feedback report messages (DIM6)
Sub–edit  Text Type
DIM6-1 Duplicate Input tumour records of the Hematopoietic system based on ICD-O-3 Histology. Core error
DIM6-2 Not applicable61 Not applicable
DIM6-3 Duplicates an existing Base tumour record of the Hematopoietic system based on ICD-O-3 Histology. Core error
DIM6-4 Duplicate Input tumour records based on ICD-O-3 Topography, ICD-O-3 Histology and Laterality. Core error
DIM6-5 Not applicable59 Not applicable
DIM6-6 Duplicates an existing Base tumour record based on ICD-O-3 Topography, ICD-O-3 Histology and Laterality. Core error
Table
Revision (DIM6)
Year Description
2006 Edit no longer used (only applied for data years 1992-2006). New multiple primary/histology rules adopted.
2004 Edit renamed: Formerly known as Correlation Edit No.34A-F.
Business rule changed: Potential duplicate tumours with unknown laterality are now rejected.
Edit logic changed to allow the addition of a Tumour record that duplicates a Base tumour record that is about to be updated or deleted.

3.6.4 Pre-posting match edits

The purpose of the pre-posting match edits is to identify core error-free4 input records that cannot be posted to the CCR because some other related input records are either missing or have core errors.

The following table summarizes the purpose of each individual edit of this category.

Table 32
Pre-posting edits summary
Edit name Purpose
PPM1 Ensures that no orphan Patient record is created in the CCR.
PPM2 Ensures that no orphan Tumour record is created in the CCR.

PPM1

Purpose

This edit ensures that no orphan patient record is created in the CCR.

Table
Referenced fields (PPM1)
Field Length Description Acronym
T1 2 Tumour reporting province/territory TREPPROV
T2 9 Tumour patient identification number TPIN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
P1 2 Patient reporting province/territory PREPPROV
P2 9 Patient identification number PPIN
P3 9 CCR identification number CCR_ID
P4 1 Patient record type PRECTYPE

Business rules

Every Base patient record must have at least one Base tumour record with the same Reporting province/territory and Patient identification number and CCR identification number.
Table
Edit logic (PPM1)
Sub–edit  Conditions Outcome
PPM1-1 Core error-free56 Input patient record where P4='1' that matches no Core error-free Input tumour record where T5='1' AND P1=T1 AND P2=T2. Patient record rejected
PPM1-2 One or more Core error-free Input tumour records with the same IT4 where IT5='3' that match no Core error-free Input patient record where IP4='3' AND IP3=IT4 and match no Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4=IT4 but match a Base Patient record where IT1=BP1 AND IT4=BP3 and match as many Base tumour records where BT1=IT1 AND BT4=IT4. Tumour records rejected
Table
Feedback report messages (PPM1)
Sub–edit  Text Type
PPM1-1 Patient record cannot be added because all associated Add Tumour records have been rejected. Core error
PPM1-2 Tumour records cannot be deleted because it would create an orphan Patient record. Core error
Table
Revision (PPM1)
Year Description
2004 Renamed: Formerly known as Additional rules for updating the CCR #2.
Business rules added: Prevent the addition of a new Patient record without Tumour record.

PPM2

Purpose

This edit ensures that no orphan tumour record is created in the CCR.

Table
Referenced fields (PPM2)
Field Length Description Acronym
T1 2 Tumour reporting province/territory TREPPROV
T2 9 Tumour patient identification number TPIN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
P1 2 Patient reporting province/territory PREPPROV
P2 9 Patient identification number PPIN
P3 9 CCR identification number CCR_ID
P4 1 Patient record type PRECTYPE

Business rules

Every Base tumour record must have one Base patient record with the same CCR identification number.
Table
Edit logic (PPM2)
Sub–edit  Conditions Outcome
PPM2-1 Core error-free56 Input tumour record where T5='1' AND T4 IS NULL that matches no Core error-free Input patient record where P4='1' AND P1=T1 AND P2=T2. Tumour record rejected
PPM2-2 Core error-free Input patient record where IP4='3' that matches less Core error-free Input tumour records where IT5='3' AND IT4=IP3 than Base tumour Record where BT1=IP1 AND BT4=IP3 Patient record rejected
Table
Feedback report messages (PPM2)
Sub–edit  Text Type
PPM2-1 Tumour record cannot be added because associated Add Patient record has been rejected. Core error
PPM2-2 Patient record cannot be deleted because not all related Base tumour records with the same Reporting province/territory have been deleted. Core error
Table
Revision (PPM2)
Year Description
2004 Edit renamed: Formerly known as Additional rules for updating the CCR #1.
Business rules added: Prevent the addition of a new Tumour record without a Patient record.

3.7 Data posting

Description

The data posting phase is the actual registration of validated data on the CCR database. During this phase, successfully validated input records are added, updated or deleted from the CCR database in accordance with the operation specified by the PTCR on each record. Depending on the operation, a CCR identification number is generated and some derived variables are computed.

In addition to the data registration, the data posting phase also updates auxiliary tables used by other processes such as internal record linkage and death clearance. These tables are:

  • Deleted CCR ID,
  • Alternate surnames,
  • Internal Record Linkage – Don't Link Cross Reference table,
  • Death Clearance – Don't Link Cross Reference.

The content and purpose of the above tables are described in Appendix F – Auxiliary tables

Organization

This section is organized as follow:

Table
Data posting
Sub–section Description
3.7.1 Add Patient record processing
How Input records are processed based on the operation and the record type.
3.7.2 Add Tumour record processing
3.7.3 Update Patient record processing
3.7.4 Update Tumour record processing
3.7.5 Delete Patient record processing
3.7.6 Delete Tumour record processing
3.7.7 Patient Derived variable calculations
How patient and tumour derived variables are computed.
3.7.8 Tumour Derived variable calculations

Writing Conventions

Throughout the following pages, the prefixes "I" and "B" preceding field numbers indicate input or base fields respectively. These prefixes are used to indicate the origin of the corresponding variable in expressions.

Example: IP6 stands for P6 variable on an input record.
Example: BTD2 stands for TD2 variable on a base record

3.7.1 Add patient record processing

For each successfully validated add patient record, the following actions are conducted:

A new base patient record is created using:

  • CCR identification number (P3): A new CCR identification number (see below);
  • Core data items (P1 to -P21 except P4 – input record type): corresponding input record variables values;
  • Derived variables (PD1 to PD8): applicable patient derived variables values (see 3.7.7 patient derived variable calculations).

3.7.1.1 CCR identification number creation

The logic to create a new CCR identification number is the following:

LET
  • Today _Year4 be the year of today's date (4 digits).
  • Today_Year2 be the last two digits of the year of today's date (2 digits).
  • Last_CCRID_Year4 be the year the last CCR identification number was created (4 digits).
  • CCR_sequence_number be the numeric sequence used to create the CCR identification number (6 digits).
  • Check_Digit be a placeholder for the new CCR ID check digit (1 digit)
  • New_CCR_ID be a placeholder for the new CCR identification number (9 digits).
  • Check_Digit() be a function that returns a check digit based on the logic described in Appendix X – CCR_ID Check Digit Routine.
  • || be a string operator that concatenates two text strings together.
BEGIN
  • IF Last_CCRID_Year4 < Today_Year4THEN
  • CCR_Sequence_Number = '000000';
  • Last_CCRID_Year4 =Today _Year4;
  • End IF;
  • Check_Digit = Check_Digit (Today _Year2 || CCR_Sequence_Number)
  • New_CCR_ID = Today _Year2 || CCR_Sequence_Number ||Check_Digit
  • CCR_Sequence_Number =CCR_Sequence_Number + 1;
  • RETURN New_CCR_ID;
END;

3.7.2 Add tumour record processing

For each add tumour record where the core data items (T1 to T26, T53 to T63 and T84 to T87) are valid, the following actions are conducted:

A new base tumour record is created using:

  • Core data items (T1 to T26 (except T5 – Input record type), T53 to T63, and T84 to T87): corresponding input core data items;
  • CCR identification number (T4): reported CCR identification number or, if missing, the CCR identification number assigned to the corresponding new patient record (Patient record with the same reporting province/territory and patient identification number);
  • CS data items (T27 to T41 and T52 and T64 to T83):
    • If the tumour is within the CCR collaborative staging scope and the input CS data items are valid then the input CS data items are loaded onto the database.
    • If the tumour is within the CCR collaborative staging scope and one or more of the input CS data items is invalid then the corresponding database fields are "R" filled.
    • If the tumour is outside the CCR collaborative staging scope then the corresponding database fields are filled with blanks.
  • AJCC TNM data items (T42 to T51 (reported 2003 to 2007)):
    • If the tumour is within the CCR AJCC TNM staging scope and the input AJCC TNM data items are valid then the input AJCC TNM data items are loaded onto the database.
    • If the tumour is within the CCR AJCC TNM staging scope and one or more of the input AJCC TNM data items is invalid then the corresponding database fields are "R" filled.
    • If the tumour is outside the CCR AJCC TNM staging scope then the corresponding database fields are "NULL" filled.
  • Derived data items (TD1 to TD20): applicable tumour derived variables values (see 3.7.8 Tumour derived variable calculations).

3.7.3 Update patient record processing

For each successfully validated Update patient record, the following actions are conducted:

  • Alternate surname table is updated (see below);
  • Death Clearance – Don't Link Cross Reference table is updated (see below);
  • Corresponding base patient record is updated using:
    • Core data items (P1 to P21 except P4 – Input record type): all input record variable values,
    • Derived variables (PD1-PD8): applicable patient derived variables values (see 3.7.7 Patient derived variable calculations).

3.7.3.1 Alternate surname table update

Alternate surname table is updated as following:


Let P3 be the CCR identification number
Let P6 be the patient Current Surname
IF BP6 IS NOT NULL AND (IP6 IS NULL OR IP6 <> BP6) AND (BP3, BP6 combination NOT IN [Alternate Surname table]) THEN
BP3, BP6 combination is added to Alternate Surname table.
END IF

See Appendix F – Auxiliary Tables – Alternate surname for more details.

3.7.3.2 Death Clearance – Don't Link Cross Reference Table Update

If a base Patient is Death-Cleared and the corresponding Input transaction resets all Death Information, the Death Confirmation is said to be Refused and the Death Clearance – Don't Link Cross Reference Table is updated as follows;

Let P3 be the CCR Identification Number
Let P14 be the patient Date of Death
Let P15 be the patient Province/Territory or Country of Death
Let P16 be the patient Death Registration Number
Let P17 be the patient Underlying Cause of Death
Let P18 be the patient Autopsy Confirming Cause of Death
Let PD5 be the Death Clearance Status
IF (BPD5='2' AND IP14='00000000' AND IP15='000' AND IP16='000000' AND IP17='0000' AND IP18='0') THEN
BP3, BP14, BP15, BP16 combination is added to Death Clearance – Don't Link Cross Reference table.
END IF

See Appendix F – Auxiliary Tables – Death Clearance – Don't Link Cross Reference Table for more details.

3.7.4 Update tumour record processing

For each update tumour record where the core data items (T1 to T26 and T53 to T63) are valid, the following actions are conducted:

  • Corresponding base tumour record is updated using:

Core data items (T1 to T26 except T5 and T53 to T63– Input record type): Corresponding input core data items;
CS data items (T27 to T41, and T52 and T63 to T83):

  • If the tumour is within the CCR collaborative staging scope and the input CS data items are valid then the input CS data items are used.
  • If the tumour is within the CCR collaborative staging scope but the input CS data items are invalid then the corresponding base data items are "R" filled.
  • If the tumour is outside the CCR collaborative staging scope then NULL values are used.

AJCC TNM data items (T42 to T51 (reported 2003 to 2007)):

  • If the tumour is within the CCR AJCC TNM stagingscope and the input AJCC TNM data items are valid then the input AJCC TNM data items are used.
  • If the tumour is within the CCR AJCC TNM staging scope but input AJCC TNM data items are invalid then the corresponding base data items are "R" filled.
  • If the tumour is outside the CCR AJCC TNM staging scope then NULL values are used.

Derived data items (TD1 to TD20): applicable tumour derived variables values (see 3.7.8 Tumour derived variable calculations)

3.7.5 Delete patient record processing

For each successfully validated delete patient record, the following actions are conducted:

  • Deletion or reversal of ownership of the corresponding base patient record (see below);
  • If reversal of ownership takes place, corresponding patient derived variables are updated (See3.7.7 Patient derived variable calculations).

If true patient record deletion takes place:

  • Deleted CCR_ID table is updated (see below);
  • Alternate surname table is updated (see below);
  • Internal Record Linkage – Don't Link Cross Reference table is updated (see below);
  • Death Clearance – Don't Link Cross Reference table is updated (see below).

3.7.5.1 Patient record deletion or reversal of ownership

A reversal of ownership is needed when a PTCR deletes a patient record but does not own all related tumours records (that is, at least one related tumour record is owned by another jurisdiction). In such case, the Patient record cannot be deleted from the database because it would otherwise create orphan tumour records. In lieu, the ownership (express by P1 – Patient Reporting Province/Territory and P2 – Patient Identification Number values) of the existing base patient record is changed to the jurisdiction that owns Patient's Last Diagnosed Tumour among remaining tumour records.

The Patient's Last Diagnosed Tumour is based on Date of Diagnosis (TDATDIAG) sorted in chronological order and the following additional rules:

When sorting in chronological order tumours based on the Date of Diagnosis, less precise dates must come before more precise dates. For example, if one tumour has a Date of Diagnosis of '19951099' and another tumour has a Date of Diagnosis of '19959999', then the tumour with the Date of Diagnosis of '19951099' is considered the Latest Tumour.
When two or more tumours share the same Date of Diagnosis, tumours are sorted in ascending order by Tumour Reference Number (TTRN), Health Insurance Number (THIN) and Reporting Province Code (TREPPROV) using an alphabetic comparison method63.
For example, if two tumours have the same Date of Diagnosis but one tumour has TTRN='2' and the other has a TTRN='12345', then the latest tumour will be the one with TTRN='2'.

The following box shows the conditions that need to be assessed and the action that must be performed when processing a delete patient record.


Let P1 be Patient reporting province/territory.
Let P2 be Patient Identification Number.
Let P3 be Patient CCR identification number.
Let T1 be Tumour reporting province/territory.
Let T2 be Tumour Patient Identification Number.
Let T4 be Tumour CCR identification number.
Let T12 be Tumour Date of diagnosis.
Let Patient Last Diagnosed Tumour () be a function that returns the latest diagnosed tumour based on the rules specified above.
IF [Base tumour records where BT4 = IP3 AND BT1 <> IP1] IS NOT NULL THEN
-- Reversal of Ownership: BP1 – Base patient reporting province/territory is updated.
BP1 and BP2 = BT1 and BT2 from Patient Last Diagnosed Tumour ([Base tumour record
where BT4 = IP3 AND BT1 <> IP1 AND MAX(BT12)])
ELSE
-- True Patient Deletion must take place
The corresponding Base record is deleted.
END IF

Since the corresponding base patient record is not really deleted from the CCR when a reversal of ownership occurs, the applicable patient derived variables must be updated.

3.7.5.2 Deleted CCR_ID Table update

When a true patient record deletion takes place (contrary to a reversal of ownership), a new entry in Deleted CCR_ID table must be created as following:

Table
Deleted CCR_ID Table update
Deleted CCR_ID table variable Values
CCR identification number IP3
Reporting province/territory IP1
Patient identification number IP2
Date of Deletion Today's date using YYYYMMDD format.
New CCR_ID [blank]
Process 1

See Appendix F – Auxiliary Tables – Deleted CCR_ID for more details.

3.7.5.3 Alternate surname table update

When a true patient record deletion takes place (contrary to a reversal of ownership), all corresponding entries in the alternate surname table (if any) must be deleted as well.

See Appendix F – Auxiliary tables – Alternate surname for more details.

3.7.5.4 Internal Record Linkage – Don't Link Cross Reference Table Update

When a true Patient record deletion takes place (contrary to a reversal of ownership), all corresponding entries in the Internal Record Linkage – Don't Link Cross Reference table (if any) must be deleted as well.

See Appendix F – Auxiliary tables – IRL DLCR for more details.

3.7.5.5 Death Clearance – Don't Link Cross Reference Table Update

When a true Patient record deletion takes place (contrary to a reversal of ownership), all corresponding entries in the Death Clearance - Don't Link Cross Reference table (if any) must be deleted as well.

See Appendix F – Auxiliary tables – DC DLCR for more details.

3.7.6 Delete tumour record processing

For each successfully validated delete tumour record, the following actions are conducted:

Deletion of the corresponding base Tumour record.

3.7.7 Patient derived variable calculations

The following table depicts how patient derived variables are calculated depending on the operation that takes place. See corresponding variable description pages in Chapter 2 for code meaning.

Table 33
Patient derived variable calculations
Operation variable Add patient Update patient Reversal of ownership (Deletepatient)
PD1 - Processing date – Patient record
Each time a Patient record is written (created or updated), the date of the transaction is saved.

PD1 = Today's date using YYYYMMDD format.
PD2 - Vital status
Not applicable: These variables are only derived for Tabulation master files. See Chapter 4 Tabulation master files for more detail.
PD3 – Number of tumours
PD4 - Death clearance cut Off date Patient never underwent Death clearance

PD4 = '00000000'
PD4 stays the same.
PD5 - Death clearance Status Patient never underwent Death clearance

PD5 = '0'
If the Patient is Death-Cleared and Patient date of death and/or province/territory/country of death and/or Death registration number is changed, then the Patient record is no longer Death-Cleared (Death Clearance Reversal)

Let P14 be the patient Date of death
Let P15 be the patient province/territory or country of death
Let P16 be the patient Death registration number
Let PD5 be the Death Clearance Status
Let PD6 be the Death Clearance Method
Let PD7 be the Death clearance underlying cause of death
Let PD8 be Date of death (Un) Confirmation
IF BPD5 = '2' AND (IP14<>BP14 OR IP15<>BP15 OR IP16<>BP16) THEN
PD5 = '3'
PD6='0'
PD7='0000'
PD8=Today's date using YYYMMDD format
ELSE
PD5 stays the same.
PD6 stays the same.
PD7 stays the same.
PD8 stays the same.
END IF
PD5 stays the same.

3.7.8 Tumour derived variable calculations

The following table depicts how tumour derived variables are calculated depending on the operation that takes place. See corresponding variable description pages in Chapter 2 for code meaning.

Table 34
Tumour derived variable calculations
Operation variable Add tumour Update tumour
TD1 – Processing date – Tumour record Each time a Tumour record is written (created or updated), the date of the transaction is saved.

TD1 = Today's date using YYYYMMDD format.
TD2 – Sequence number Not applicable: these variables are only derived for Tabulation master files. See Chapter 4 Tabulation master files for more detail.
TD3 – Age at diagnosis
TD4 – Age group at diagnosis
TD5 – Survival interval
TD6 – Survival censor
TD7 – Derived AJCC T
TD8 – Derived AJCC N
TD9 – Derived AJCC M
TD10 – Derived AJCC T descriptor
TD11 – Derived AJCC N descriptor
TD12 – Derived AJCC M descriptor
TD13 – Derived AJCC stage group
TD14 – Derived AJCC flag
TD15 – Derived SS1977
TD16 – Derived SS1977 flag
TD17 – Derived SS2000
TD18 – Derived SS2000 flag
TD19 – CS version derived

Chapter 4 – Tabulation master files

  • Description
  • Scope
  • Content and layout
  • Derived variables calculations
  • Confidentiality

4.1 Description

The Tabulation master file (TMF) produced from the Canadian Cancer Registry (CCR) serves as a snapshot of the entire CCR database. The resulting flat file merges the patient and tumour records from the CCR, using the unique patient record identifier (CCR identification number) to produce a composite record containing both patient and tumour information, with one record for each tumour.

The TMF is used by researchers, academics, regional health unit personnel, health policy/program planners and decision-makers, epidemiologists and public health professionals. It is provided to representatives from organizations such as Health Canada, the Public Health Agency of Canada, the Canadian Institute for Health Information, and other health-related non-government organizations in accordance with applicable legal agreements and Statistics Canada's guidelines pertaining to release of confidential information. It is created on a yearly basis or, in some instances, as warranted by operational requirements.

See http://www.statcan.ca/english/about/privact.htm section 4.5 Confidentiality

4.2 Scope

There are 2 versions of the tabulation master file, the Canadian Cancer Registry tabulation master file (CCRTMF) and the International Agency for Research on Cancer tabulation master file (IARCTMF). These two versions differ in scope as different rules for determining multiple primary neoplasms are applied.

In addition, each of the TMF can either be national (based on patients from all PTCRs) or provincial/territorial (based on patients from only one PTCR). Provincial/territorial TMFs are based on the ownership of Patient records, i.e. tumours are selected based on the reporting province or territory of its related patient record regardless of the province or territory that actually owns the tumour record itself.

4.2.1 CCRTMF – Canadian Cancer Registry tabulation master file.

Variations exist between provincial/territorial Cancer Registries in the coding practices for multiple primaries. Many registries adhere to CCR rules while others use IARC (Québec), IARC/Berg (Ontario) and SEER (Alberta from 1994) for recording tumours in their registries. Given that all cancer records submitted to the CCR are subjected to specific CCR rules for determining multiple primary tumours (see Appendix D – Multiple primary tumours rules for CCR for more details), the resulting CCRTMF consists of a mixture of IARC and CCR rules for determining multiple tumours. As of 2007 the CCR has adopted SEER rules.

4.2.2 IARCTMF – International agency for research on cancer (IARC) tabulation master file

Important note: IARCTMF implementation has changed in 2004. See Revision box at the end of this section for details.

Since not all registries follow the CCR standards, the annual release of cancer incidence and survival statistics are disseminated from STC using the IARC rules for determining multiple primary tumours for the purpose of comparability between registries over time.

All tumour records on IARCTMF have been selected from the CCR according to IARC coding rules for determining multiple primary tumours as specified by the IARC/IACR's Working Groups' Recommendations for coding Multiple Primaries. The International Classification of Diseases for Oncology – Third Edition outlines the rules as follows:

A working party of IARC recommended definitions of multiple neoplasms for the purpose of incidence reporting for international comparison. Their recommendations are:
  1. Recognition of the existence of two or more primary cancers does not depend on time.
  2. A primary cancer is one that originates in a primary site or tissue and is neither an extension, nor a recurrence, nor a metastasis.
  3. Only one tumour shall be recognized as arising in an organ or pair of organs or tissue. For tumours where site is coded by the first edition of ICD-O (or by ICD-9), an organ or tissue is defined by the three-character category of the topography code.

    ICD-1O and the Second and Third editions of ICD-O have a more detailed set of topography codes. The sites covered by some groups of codes are considered to be a single organ for the purposes of defining multiple tumours. These topography code groups are shown in Table 24*.

    Multifocal tumours – that is, discrete masses apparently not in continuity with other primary cancers originating in the same primary site or tissue, for example bladder – are counted as a single cancer.

    Skin cancer presents a special problem as the same individual may have many such neoplasms over a lifetime. The IARC/IACR rules imply that only the first tumour of a defined histological type, anywhere on the skin, is counted as an incident cancer unless, for example, one primary was a malignant melanoma and the other a basal cell carcinoma.
  4. Rule 3 does not apply in two circumstances:
    4.1. For systemic or multicentric cancers potentially involving many discrete organs, four histological groups – lymphomas, leukemias, Kaposi sarcoma, and mesothelioma (groups 7, 8, 9 and 10 in Table 25*) – are included. They are counted only once in any individual.

    4.2. Other specific histologies – groups 1, 2, 3, 4, 6, and 11 in Table 25 – are considered to be different for the purpose of defining multiple tumours. Thus, a tumour in the same organ with a 'different' histology is counted as a new tumour. Groups 5 and 12 include tumours that have not been satisfactorily typed histologically and cannot therefore be distinguished from the other groups.
- Source International Classification of Diseases for Oncology – Third Edition, page 35

"* "Table 24" and "Table 25" are reproduced on the following pages.

Table 24
Groups of topography codes from ICD-O-2 and ICD-O-3 considered a single site in the definition of multiple cancers
ICD–O–2/3 Topography codes Description
C01 Base of tongue
C02 Other and unspecified parts of tongue
C05 Palate
C06 Other and unspecified parts of mouth
C07 Parotid gland
C08 Other and unspecified major salivary glands
C09 Tonsil
C10 Oropharynx
C12 Pyriform sinus
C13 Hypopharynx
C23 Gallbladder
C24 Other and unspecified parts of biliary tract
C30 Nasal cavity and middle ear
C31 Accessory sinus
C33 Trachea
C34 Bronchus and lung
C37 Thymus
C38.0 Heart
C38.1-.3 Mediastinum
C38.8 Overlapping lesion of heart, mediastinum and pleura
C38.4 Pleura (visceral, parietal, NOS)
C51 Vulva
C52 Vagina
C57.7 Other specified female genital organs
C57.8-.9 Unspecified female genital organs
C56 Ovary
C57.0 Fallopian tube
C57.1 Broad ligaments
C57.2 Round ligament
C57.3 Parametrium
C57.4 Uterine adnexa
C60 Penis
C63 Other and unspecified male genital organs
C64 Kidney
C65 Renal pelvis
C66 Ureter
C68 Other and unspecified urinary organs
C74 Adrenal gland
C75 Other endocrine glands and related structures
Source: THE SEER PROGRAM CODING AND STAGING MANUAL 2004, Fourth Edition, January 2004, page 9, Surveillance Research Program Division Of Cancer Control And Population Sciences, National Cancer Institute, U.S. Department Of Health And Human Services.
Table 25
Groups of malignant neoplasms considered to be histologically "different" for the purpose of defining multiple tumours (adapted from Berg, 1994)
Group Description ICD-O-3 Histology codes
1 Squamous carcinomas 805 to 808, 812, 813
2 Basal cell carcinomas 809 to 811
3 Adenocarcinomas 814, 816, 819 to 822, 826to 833, 835 to 855, 857, 894
4 Other specific carcinomas 803, 804, 815, 817 to 818, 823 to 825, 834, 856, 858 to 867
(5) Unspecified carcinomas (NOS) 801, 802
6 Sarcomas and soft tissue tumours 868 to 871, 880 to 892, 899, 904, 912 to 913, 915 to 925, 937, 954 to 958
7 Lymphomas 959 to 972
8 Leukemia 980 to 994, 995, 996, 998
9 Kaposi sarcoma 914
10 Mesothelioma 905
11 Other specified types ofcancer 872 to 879, 893, 895 to 898, 900 to 903, 906 to 911, 926 to 936, 938 to 953, 973 to 975, 976
(12) Unspecified types of cancer 800, 997
Source: INTERNATIONAL CLASSIFICATION OF DISEASES FOR ONCOLOGY, Third Edition, 2000, page 37, World Health Organization.

Based on the above rules and tables, the following algorithm is used to eliminate duplicate tumours from the IARC tabulation master files.

Table 35
Algorithm used to eliminate duplicate tumours from IARC TMF

Definitions
Site: Identified by the 3 first digits of the ICD-O-2/3 Topography code.
Topography Group: See Table 24.
Histology Group: See Table 25.
Systemic and Multicentric groups: 7, 8, 9, 10
Non-Systemic and Non-Multicentric groups: 1, 2, 3, 4, 5, 6, 11, 12
Specific Histology groups: 1, 2, 3, 4, 6, 11
Non-Specific Histology groups: 5, 12
Rule 1: When there is more than one tumour in a subset keep the tumour with the highest behaviour/site rank (see Table 35b below), if more than one tumour has the same rank keep the tumour with the earliest Date of diagnosis. If more than one tumour has the same Date of diagnosis, then the tumour with the lowest TTRN, TPIN and TREPPROV is kept.
Logic
For a given patient with more than one tumour:
For Systemic and Multicentric Tumours:
Eliminate duplicate tumours in each Systemic and Multicentric Group using Rule1(regardless of the Site).
For Non-Systemic and Non-Multicentric Tumours:
Eliminate duplicate tumours within the same Site and same Specific Histology group using Rule1;
Eliminate duplicate tumours within the same Site and any Non-Specific Histology group using Rule1;
Eliminate all tumours within Non-Specific Histology groups when there is at least one tumour within Specific Histology groups for the same Site;
Eliminate duplicate tumours within the same Topography group and same Specific Histology group using Rule 1;
Eliminate duplicate tumours within the same Topography group and any Non-Specific Histology group using Rule 1;
Eliminate all tumours within Non-Specific Histology groups when there is at least one tumour within Specific Histology groups for the same Topography group.
Table 35b
Ranking of Behaviour to Identify most 'malignant' tumour:
Behaviour (T22) \ Site (T15) C0 – C66, C68-C80 C67
0 4 4
1 3 3
2 2 1
3 1 1

When a patient has only two tumours, it may be easier to use the following decision tree instead of the above algorithm to assess if tumours are duplicates. When a patient has more than two tumours, the above algorithm must always be used to eliminate duplicate tumours since the decision tree does not indicate the order in which to process tumours pairs which in turn may lead to incorrect results.

Figure 1 Decision tree to assess if two tumours are duplicates based on IARC rules

Figure 1 Decision tree to assess if two tumours are duplicates based on IARC rules
Table
Revision (Description)
Year Description
2008 Table 35 changed: Behaviour/site ranking to take precedence for duplicate tumours
Table 35b added: Ranking of Behaviour to Identify the most 'malignant' tumour:
2007 Table 24 changed:Topography group added: C38.4
2004 Table 24 changed: The latest SEER "Table 24" definition has been implemented.

Topography groups removed: C19, C20; C40, C41;

Topography groups added: C37, C38.0-3 and C38.8; C51, C52, C57.7 and C57.8-9; C56 and C57.0-4;

Algorithm changed:

Systemic and Multicentric tumours: IARC criteria are applied regardless of the CCR Multiple Primary rules.

Duplicate tumours within the same Histology group and with the same Date of Diagnosis: In this case, only the tumour with the lowest Tumour Reference Number, Patient identification number and Reporting Province/Territory Code is kept. This was needed to guarantee that the tumour selected is always the same when the Date of Diagnosis is the same for all tumours.

Histology group 5 vs 12: These two groups are now considered the same for the purpose of finding duplicate tumours.

Specific Histology groups vs Non-Specific Histology groups: A condition has been added to deal with duplicate tumours from different Histology groups where specific and non-specific histologies have been reported. In this case, only tumours with specific histology are kept, regardless of the Date of Diagnosis.

4.3 Content and layout

The TMF includes all variables on the patient and tumour records as provided by PTCRs (except for Fields P4 and T5, the patient and tumour record types) plus additional variables that are derived from the input variables or brought in from other sources by the CCR. (See Chapter 2 Data dictionary for more information about each variable.)

The record layout for both CCR and IARC tabulation master files is as follows.

Table 36
TMF record layout
Field Length Position Description Acronym
P1 2 1 - 2 Patient reporting province/territory PREPPROV
P2 12 3 - 14 Patient identification number PPIN
P3 9 15 - 23 CCR identification number CCR_ID
P5 1 24 - 24 Type of Current surname PTYP_CUR
P6 25 25 - 49 Current surname PCURSNAM
P7 15 50 - 64 First given name PGNAME_1
P8 15 65 - 79 Second given name PGNAME_2
P9 7 80 - 86 Third given name PGNAME_3
P10 1 87 - 87 Sex PSEX
P11 8 88 - 95 Date of birth PDATBIR
P12 3 96 - 98 Province/territory or country of birth PPROVBIR
P13 25 99 - 123 Birth surname PBIRNAM
P14 8 124 - 131 Date of death PDATDEA
P15 3 132 - 134 Province/territory or country of death PPROVDEA
P16 6 135 - 140 Death registration number PDEAREG
P17 4 141 - 144 Underlying cause of death PCAUSDEA
P18 1 145 - 145 Autopsy confirming cause of death PAUTOPSY
P19 8 146 - 153 Patient date of transmission PDATTRAN
P20 2 154 - 155 Date of birth flag (blank until 2010) PDATBIRFLAG
P21 2 156 - 157 Date of death flag (blank until 2010) PDATDEAFLAG
PD1 8 158 - 165 Processing date – patient record PDCCRDATPROC
PD2 1 166 - 166 Vital status PDCCRVITALST
PD3 2 167 - 168 Number of tumours PDCCRNBRTMRS
PD4 8 169 - 176 Death clearance cut off date PDDCDATCO
PD5 1 177 - 177 Death clearance status PDDCSTAT
PD6 1 178 - 178 Death clearance method PDDCMETH
PD7 4 179 - 182 Death clearance underlying cause of death PDDCUCD
PD8 8 183 - 190 Date of death (un) confirmation PDDCDATCN
T1 2 191 - 192 Tumour reporting province/territory TREPPROV
T2 12 193 - 204 Tumour patient identification number TPIN
T3 9 205 - 213 Tumour reference number TTRN
T6 25 214 - 238 Name of place of residence TPLACRES
T7 6 239 - 244 Postal code TPOSTCOD
T8 7 245 - 251 Standard geographic code TCODPLAC
T9 9 252 - 260 Census tract TCENTRAC
T10 15 261 - 275 Health insurance number THIN
T11 1 276 - 276 Method of diagnosis TMETHDIAG
T12 8 277 - 284 Date of diagnosis TDATDIAG
T13 4 285 - 288 ICD-9 cancer code TICD_9
T14 1 289 - 289 Source classification flag TSCF
T15 4 290 - 293 ICD-O-2/3 Topography TICD_O2T
T16 4 294 - 297 ICD-O-2 Histology TICD_O2H
T17 1 298 - 298 ICD-O-2 Behaviour TICD_O2B
T19 1 299 - 299 Laterality TLATERAL
T21 4 300 - 303 ICD-O-3 Histology TICD_O3H
T22 1 304 - 304 ICD-O-3 Behaviour TICD_O3B
T23 1 305 - 305 Grade, differentiation or cell indicator TGRADE
T24 2 306 - 307 Method used to establish date of diagnosis TMETHUSED
T25 2 308 - 309 Diagnostic confirmation TMETHCONF
T26 8 310 - 317 Tumour date of transmission TDATTRAN
T27 3 318 - 320 CS tumour size TCSTSIZE
T28 3 321 - 323 CS extension TCSEXTN
T29 1 324 - 324 CS tumour size/ext eval TCSEVAL
T30 3 325 - 327 CS lymph nodes TCSLNODE
T31 1 328 - 328 CS reg nodes eval TCSRNEVAL
T32 2 329 - 330 Regional nodes examined TCSRNEXAM
T33 2 331 - 332 Regional nodes positive TCSRNPOS
T34 2 333 - 334 CS mets at dx TCSMDIAG
T35 1 335 - 335 CS mets Eval TCSMEVAL
T36 3 336 - 338 CS site-specific factor 1 TCSSSF1
T37 3 339 - 341 CS site-specific factor 2 TCSSSF2
T38 3 342 - 344 CS site-specific factor 3 TCSSSF3
T39 3 345 - 347 CS site-specific factor 4 TCSSSF4
T40 3 348 - 350 CS site-specific factor 5 TCSSSF5
T41 3 351 - 353 CS site-specific factor 6 TCSSSF6
T42 9 354 - 362 AJCC clinical T TAJCCCLINT
T43 3 363 - 365 AJCC clinical N TAJCCCLINN
T44 3 366 - 368 AJCC clinical M TAJCCCLINM
T45 9 369 - 377 AJCC pathologic T TAJCCPATHT
T46 6 378 - 383 AJCC pathologic N TAJCCPATHN
T47 3 384 - 386 AJCC pathologic M TAJCCPATHM
T48 4 387 - 390 AJCC clinical TNM stage group TAJCCCLINSG
T49 4 391 - 394 AJCC pathologic TNM stage group TAJCCPATHSG
T50 4 395 - 398 AJCC TNM stage group TAJCCSG
T51 2 399 - 400 AJCC TNM edition number TAJCCEDNUM
T52 6 401 - 406 CS version input original TCSVERINORIG
T53 1 407 - 407 Ambiguous Terminology Diagnosis TAMBIGTERM
T54 8 408 - 415 Date of conclusive diagnosis TDATCONCLUSDIAG
T55 2 416 - 417 Type of multiple tumours reported as one primary TMULTTUMONEPRIM
T56 8 418 - 425 Date of multiple tumours TDATMULT
T57 2 426 - 427 Multiplicity counter TMULTCOUNT
T58 2 428 - 429 Date of diagnosis flag (blank until 2010) TDATDIAGFLAG
T59 2 430 - 431 Date of conclusive diagnosis flag (blank until 2010) TDATCONCLUSDIAGFLAG
T60 2 432 - 433 Date of multiple tumours flag (blank until 2010) TDATMULTFLAG
T61 1 434 - 434 Grade Path Value (blank until 2010) TGRADEPATHVAL
T62 1 435 - 435 Grade Path System (blank until 2010) TGRADEPATHSYS
T63 1 436 - 436 Lymph-vascular invasion TLYMPHVASINV
T64 6 437 - 442 CS Version input current TCSVERINCUR
T65 3 443 - 445 CS Site-Specific Factor 7 TCSSSF7
T66 3 446 - 448 CS Site-Specific Factor 8 TCSSSF8
T67 3 449 - 451 CS Site-Specific Factor 9 TCSSSF9
T68 3 452 - 454 CS Site-Specific Factor 10 TCSSSF10
T69 3 455 - 457 CS Site-Specific Factor 11 TCSSSF11
T70 3 458 - 460 CS Site-Specific Factor 12 TCSSSF12
T71 3 461 - 463 CS Site-Specific Factor 13 TCSSSF13
T72 3 464 - 466 CS Site-Specific Factor 14 TCSSSF14
T73 3 467 - 469 CS Site-Specific Factor 15 TCSSSF15
T74 3 470 - 472 CS Site-Specific Factor 16 TCSSSF16
T75 3 473 - 475 CS Site-Specific Factor 17 TCSSSF17
T76 3 476 - 478 CS Site-Specific Factor 18 TCSSSF18
T77 3 479 - 481 CS Site-Specific Factor 19 TCSSSF19
T78 3 482 - 484 CS Site-Specific Factor 20 TCSSSF20
T79 3 485 - 487 CS Site-Specific Factor 21 TCSSSF21
T80 3 488 - 490 CS Site-Specific Factor 22 TCSSSF22
T81 3 491 - 493 CS Site-Specific Factor 23 TCSSSF23
T82 3 494 - 496 CS Site-Specific Factor 24 TCSSSF24
T83 3 497 - 499 CS Site-Specific Factor 25 TCSSSF25
T84 1 500 - 500 CS Mets at Dx - Bone (blank until 2010) TCSMDXBONE
T85 1 501 - 501 CS Mets at Dx - Brain (blank until 2010) TCSMDXBRAIN
T86 1 502 - 502 CS Mets at Dx - Liver (blank until 2010) TCSMDXLIVER
T87 1 503 - 503 CS Mets at Dx - Lung (blank until 2010) TCSMDXLUNG
TD1 8 504 - 511 Processing date – tumour record TDCCRDATPROC
TD2 2 512 - 513 Sequence number TDCCRSEQNUM
TD3 3 514 - 516 Age at diagnosis TDCCRAGEDIAG
TD4 2 517 - 518 Age group at diagnosis TDCCRAGEGRP
TD5 5 519 - 523 Survival interval TDDCSURVINT
TD6 1 524 - 524 Survival censor TDDCCENSOR
TD7 2 525 - 526 Derived AJCC T TDCSAJCCT
TD8 2 527 - 528 Derived AJCC N TDCSAJCCN
TD9 2 529 - 530 Derived AJCC M TDCSAJCCM
TD10 1 531 - 531 Derived AJCC T descriptor TDCSAJCCTDESC
TD11 1 532 - 532 Derived AJCC N descriptor TDCSAJCCNDESC
TD12 1 533 - 533 Derived AJCC M descriptor TDCSAJCCMDESC
TD13 2 534 - 534 Derived AJCC stage group TDCSAJCCSG
TD14 1 536 - 536 Derived AJCC flag TDCSAJCCF
TD15 1 537 - 537 Derived SS1977 TDCSSS1977
TD16 1 538 - 538 Derived SS1977 flag TDCSSS1977F
TD17 1 539 - 539 Derived SS2000 TDCSSS2000
TD18 1 540 - 540 Derived SS2000 flag TDCSSS2000F
TD19 6 541 - 546 CS version derived TCSVERDER
Table
Revision (Content and layout)
Year Description
2010 Variable names changed: CS version 1st to CS version input original (acronym changed from TCSFVER to TCSVERINORIG), CS reg nodes eval to CS lymph nodes eval (acronym changed from TCSRNEVAL to TCSLNEVAL), CS version latest to CS version derived (acronym changed from TCSLVER to TCSVERDER) . The length of variables Method used to establish date of diagnosis, Diagnostic confirmation, CS extension and CS lymph nodes has changed.
Addition of P20, P21, T58 – T87
Re-positioning of many variables
2008 Addition of T53 to T57
2007 Addition of T52, deletion of TD20

4.4 Derived variable calculations

Most of the derived variables found on the tabulation master file are used and updated by the CCR System main processes (namely data loading, internal record linkage and death clearance process). Thus, these variables are already available at tabulation master file (TMF) creation time and do not need to be recalculated. Variables that are not used by the CCR System main processes must be derived at TMF creation time. The following table shows which variables are derived at TMF creation time and their respective calculation specification.

Table 37
Derived variable calculations at TMF time
Variable Value
PD2 – Vital status  Let P14 be the patient Date of death

IF P14 = '00000000' THEN
PD2 = '1'
ELSE
PD2 = '2'
End IF
PD3 – Number of tumours PD3 = Patient's total number of tumours within the applicable TMF scope.
TD2 – Sequence number For a given CCR identification number and TNM scope, tumours are numbered from 1 to N in chronologic order based on the Date of diagnosis. If two or more tumours share the same Date of diagnosis, then tumours are ordered by Reporting province/territory and Tumour reference number in ascending order.

TD2 = Sequence number based on the above definition.
TD3 – Age at diagnosis If the Patient date of birth is unknown, then Age at diagnosis cannot be calculated. Otherwise, Age at diagnosis is calculated using Patient date of birth and the tumour Date of diagnosis.

Let INTERVAL_YEARS (Date1, Date2) be a function that returns the number of complete years between Date1 and Date2 as described in Appendix E – Interval and Mean Time Between Dates.
Let P11 be the corresponding Patient date of birth.
Let T12 be the Tumour date of diagnosis.

IF P11 = '99999999' THEN
TD3 = 999
ELSE
TD3 = INTERVAL_YEARS (P11, T12)
END IF
TD4 – Age group at diagnosis TD4 = Corresponding age group based on TD3 value. (See TD4 – Specified values and meaning.)
TD5 – Survival interval
TD6 – Survival censor
If the Patient never underwent Death clearance process; or the Date of diagnosis is after Death clearance cut-off date; or the Method of diagnosis is Death certificate only; or the Method of diagnosis is Autopsy and there is no clear evidence of a positive survival; or the Method used to establish the date of diagnosis is Autopsy or Death certificate only, then the Survival interval is not applicable.
If Survival interval is applicable but Date of death is unknown, then the Survival interval cannot be calculated.
If Survival interval is applicable but the Patient is not known to have died or died after the Death clearance cut-off date, then the Survival interval is calculated using Death clearance cut off date.
If the Survival interval is applicable and the patient died before or on the Death clearance cut-off date, then the Survival interval is calculated using Date of death.

Let INTERVAL_DAYS (Date1, Date2) be a function that returns the number of days between Date1 and Date2 as described in Appendix E – Interval and Mean Time Between Dates.
Let T11 be the Tumour method of diagnosis.
Let T12 be the Tumour date of diagnosis.
Let T24 be the Tumour method used to establish the date of diagnosis.
Let PD4 be the corresponding Patient death clearance cut-off date.
Let P14 be the corresponding Patient Date of death.

IF PD4 = '00000000'
OR T12.YEAR > PD4.YEAR
OR T11 = '6'
OR (T11 = '2' AND P14 = '99999999')
OR (T11 = '2' AND T12.YEAR = P14.YEAR AND (T12.MONTH = '99' OR P14.MONTH = '99'))
OR (T11 = '2' AND T12.YEAR = P14.YEAR AND T12.MONTH = P14.MONTH AND (T12.DAY = '99' OR P14.DAY = '99'))
OR T24 IN ['3', '8'] THEN
TD5 = 99998
TD6 = '0'
ELSE IF P14 = '99999999' THEN
TD5 = 99999
TD6 = '0'
ELSE IF P14 = '00000000' OR P14.YEAR > PD4.YEAR THEN
TD5 = INTERVAL_DAYS (T12, PD4)
TD6 = '2'
ELSE
TD5 = INTERVAL_DAYS (T12, P14)
TD6 = '1'
END IF
TD7 – Derived AJCC T Values returned by the recommended version of the AJCC CS algorithm based on CS Input variables and tumour ICD-O-2/3 Topography and ICD-O-3 Histology.
TD8 – Derived AJCC N
TD9 – Derived AJCC M
TD10 – Derived AJCC T descriptor
TD11 – Derived AJCC N descriptor
TD12 – Derived AJCC M descriptor
TD13 – Derived AJCC stage group
TD14 – Derived AJCC flag
TD15 – Derived SS1977
TD16 – Derived SS1977 flag
TD17 – Derived SS2000
TD18 – Derived SS2000 flag
TD19 – CS version derived
Table
Revision (Derived variable calculations)
Year Description
2007 PD2 – Vital Status is now derived at TMF time

4.5 Confidentiality

In order to respect confidentiality agreements, three different filtering options may be applied to the tabulation master files.

  • No filtering: No fields are hidden. This TMF is used to return data to reporting PTCR and for authorized record linkage activities.
  • No name: All names and Health insurance number fields are hidden. This TMF is used for NAACCR submission.
  • No name, No key: All names, Health insurance number and patient identification number fields are hidden. This TMF is used for dissemination.

The following table explicitly lists which fields are hidden by the different confidentiality filters.

Table 38
Hidden fields on filtered tabulation master files
Sensitive Field Filtering Option
No Filtering No Name No Name, No Key
P2 – Patient Identification Number - - Hidden
P6 – Current Surname - Hidden Hidden
P7 – First Given Name - Hidden Hidden
P8 – Second Given Name - Hidden Hidden
P9 – Third Given Name - Hidden Hidden
P13 – Birth Surname - Hidden Hidden
T2 – Tumour Patient Identification Number - - Hidden
T10 – Health Insurance Number - Hidden Hidden

In order to keep the same record layout for all Tabulation Master Files, hidden fields are simply filled with 'X'.

Appendices

Appendix C – AJCC TNM reference tables
Appendix D – Multiple primary tumours rules for CCR
Appendix E – Interval and mean time between dates
Appendix F – Auxiliary tables
Appendix G – Grade, differentiation or cell indicator guidelines (for T23)
Appendix H – CCR Ambiguous Terms (for T12 and T53)
Appendix I – Guidelines for Abstracting and Determining Death Certificate Only (DCO) Cases for
Provincial/Territorial Cancer Registries (PTCRs) in Canada (for T12 and P18)
Appendix J – Internal between two dates (complete or partial)
Appendix K - Flavours of Null Table
Appendix T – Residency guidelines in Canada (for T1, T6, P1)
Appendix X – CCR_ID check digit routine
Appendix Z – References

Appendix C – AJCC TNM reference tables (2003 to 2007)

This appendix describes all AJCC TNM reference tables, namely:

  • Valid AJCC clinical T by site;
  • Valid AJCC clinical N by site;
  • Valid AJCC clinical M by site;
  • Valid AJCC pathologic T by site;
  • Valid AJCC pathologic N by site;
  • Valid AJCC pathologic M by site;
  • Valid AJCC clinical TNM stage group by site;
  • Valid AJCC pathologic TNM stage group by site;
  • Valid AJCC TNM stage group by site;
  • Valid AJCC T, N, M and stage group combination by site

Valid AJCC clinical T by site (2003 to 2007)

Table usage notes:

See Chapter 1 for a complete description of each eligible site in terms of topography, histology and behaviour.

Table 39
Valid AJCC clinical T by stageable site
Breast Prostate Colorectal
TX TX TX
T0 T0 T0
Tis -- Tis
TisDCIS -- --
TisLCIS -- --
TisPagets -- --
T1 T1 T1
T1mic -- --
T1a T1a --
T1b T1b --
T1c T1c --
T2 T2 T2
-- T2a --
-- T2b --
-- T2c --
T3 T3 T3
-- T3a --
-- T3b --
T4 T4 T4
T4a -- --
T4b -- --
T4c -- --
T4d -- --
99 99 99

Valid AJCC clinical N by site (2003 to 2007)

Table usage notes:

See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.

Table 40
Valid AJCC clinical N by stageable site
Breast Prostate Colorectal
NX NX NX
N0 N0 N0
N1 N1 N1
N2 -- N2
N2a -- --
N2b -- --
N3 -- --
N3a -- --
N3b -- --
N3c -- --
99 99 99

Valid AJCC clinical M by site (2003 to 2007)

Table usage notes:

See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.

Table 41
Valid AJCC clinical M by stageable site
Breast Prostate Colorectal
MX MX MX
M0 M0 M0
M1 M1 M1
-- M1a --
-- M1b --
-- M1c --
99 99 99

Valid AJCC pathologic T by site (2003 to 2007)

Table usage notes:

See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.

Table 42
Valid AJCC pathologic T by stageable site
Breast Prostate Colorectal
TX TX TX
T0 -- T0
Tis -- Tis
TisDCIS -- --
TisLCIS -- --
TisPagets -- --
T1 -- T1
T1mic -- --
T1a -- --
T1b -- --
T1c -- --
T2 T2 T2
-- T2a --
-- T2b --
-- T2c --
T3 T3 T3
-- T3a --
-- T3b --
T4 T4 T4
T4a -- --
T4b -- --
T4c -- --
T4d -- --
99 99 99

Valid AJCC pathologic N by site (2003 to 2007)

See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.

Table 43
Valid AJCC pathologic N by stageable site
Breast Prostate Colorectal
NX NX NX
N0 N0 N0
N0i- -- --
N0i+ -- --
N0mol- -- --
N0mol+ -- --
N1 N1 N1
N1mi -- --
N1a -- --
N1b -- --
N1c -- --
N2 -- N2
N2a -- --
N2b -- --
N3 -- --
N3a -- --
N3b -- --
N3c -- --
99 99 99

Valid AJCC pathologic M by site (2003 to 2007)

Table usage notes:

See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.

Table 44
Valid AJCC pathologic M by stageable site
Breast Prostate Colorectal
MX MX MX
M0 M0 M0
M1 M1 M1
-- M1a --
-- M1b --
-- M1c --
99 99 99

Valid AJCC clinical TNM stage group by site (2003 to 2007)

Table usage notes:

See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.

Table 45
Valid AJCC TNM clinical stage group by stageable site
Breast Prostate Colorectal
X X X
0 -- 0
I I I
-- II --
IIA -- IIA
IIB -- IIB
-- III --
IIIA -- IIIA
IIIB -- IIIB
IIIC -- IIIC
IV IV IV
99 99 99

Valid AJCC pathologic TNM stage group by site (2003 to 2007)

Table usage notes:

See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.

Table 46
Valid AJCC TNM pathologic stage group by stageable site
Breast Prostate Colorectal
X X X
0 -- 0
I I I
-- II --
IIA -- IIA
IIB -- IIB
-- III --
IIIA -- IIIA
IIIB -- IIIB
IIIC -- IIIC
IV IV IV
99 99 99

Valid AJCC TNM stage group by site (2003 to 2007)

Table usage notes:

See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.

Table 47
Valid AJCC TNM stage group by stageable site
Breast Prostate Colorectal
0 -- 0
I I I
II61 II II61
IIA -- IIA
IIB -- IIB
III61 III III61
IIIA -- IIIA
IIIB -- IIIB
IIIC -- IIIC
IV IV IV
99 99 99

Valid AJCC T, N, M and stage group combination by site (2003 to 2007)

Table usage notes

  • The following tables assess the validity of the T, N, M and stage group values combination. They can be used to assess either clinical or pathologicvalues.
  • TNM values in the tables include all their sub-values. Thus, the expression 'T1' includes {T1, T1a, T1b, T1is...}. The actual list of included values depends on the site.
  • In the context of the CCR System, the expression 'Any T' or 'Any N' include all their respective sub-values and the value '99'. Thus, the expression 'Any N' includes {99, NX, N0, N1, N1a...}
Table 48
Valid AJCC T, N, M and stage group combination for colorectal sites
Stage Group T N M
0 Tis N0 M0
I T1 N0 M0
I T2 N0 M0
IIA T3 N0 M0
IIB T4 N0 M0
IIIA T1 N1 M0
IIIA T2 N1 M0
IIIB T3 N1 M0
IIIB T4 N1 M0
IIIC Any T N2 M0
IV Any T Any N M1
Table 49
Valid AJCC T, N, M and stage group combination for breast sites
Stage group T N M
0 Tis N0 M0
I T1 N0 M0
IIA T0 N1 M0
IIA T1 N1 M0
IIA T2 N0 M0
IIB T2 N1 M0
IIB T3 N0 M0
IIIA T0 N2 M0
IIIA T1 N2 M0
IIIA T2 N2 M0
IIIA T3 N1 M0
IIIA T3 N2 M0
IIIB T4 N0 M0
IIIB T4 N1 M0
IIIB T4 N2 M0
IIIC Any T N3 M0
IV Any T Any N M1
Table 50
Valid AJCC T, N, M and stage group combination for prostate sites
Stage group T N M
I T1a N0 M0
II T1a N0 M0
II T1b N0 M0
II T1c N0 M0
II T2 N0 M0
III T3 N0 M0
IV T4 N0 M0
IV Any T N1 M0
IV Any T Any N M1

This table has been slightly modified from the AJCC cancer staging manual, 6,th Edition since the CCR system does not consider the grade when validating the stage group and T, N, M values combination

Table
Revision (Valid AJCC T, N, M and stage group combination by site)
Year Description
2008 Table 50: updated Stage group II with T1a, T1b and T1c

Appendix D – Multiple primary tumours rules for CCR

As of 2007 the CCR has adopted SEER rules. New edits will be implemented to adhere to these new rules.

Figure 2 Decision tree to assess CCR Multiple primary tumours

Figure 2 Decision tree to assess CCR Multiple primary tumours

Appendix E – Interval and mean time between dates

The following algorithm can be used to assess the number of days or complete years between two dates. When both dates are complete, the algorithm returns the exact number of days or complete years between the two dates. When one or both dates are partial, the mean number of days or complete years between the two dates is returned. This algorithm cannot be used if one or both dates are totally unknown, i.e. equal to '99999999'. The returned value is always a positive whole number (including zero).

Definitions

Let Date1 and Date2 be the two dates from which the interval must be calculated and where Date1 <= Date2.

Let Y1, M1 and D1 be the year, month and day of date1.
Let Y2, M2 and D2 be the year, month and day of date2.
Let MOD (X, Y) be a function that returns the remainder of X divided by Y.
Let MIDDLE_DAY (Month) be a function that returns the middle day of month using the following logic:

If Month='02' Then
Return '15'
Otherwise
Return '16'

Let LAST_DAY (Year, Month) be a function that returns the last day of the month for the specified year using the following logic:

If Month='02' Then
If (MOD(Y2,4)=0 AND MOD(Y2,100)<>0) OR (MOD(Y2,4)=0 AND MOD(Y2,400)=0) Then
Return '29'
Else
Return '28'
Else If Month in ('04','06','09','11') Then
Return '30'
Else
Return '31'

Let MONTH_BETWEEN (Date1, Date2) be a function that returns the number of months between date1 and date2. If date1 is later than date2, then the result is positive. If date1 is earlier than date2, then the result is negative. If date1 and date2 are either the same days of the month or both last days of months, then the result is always a whole number. Otherwise a fractional portion of the result based on a 31-day month is also added.

Table
Algorithm (Appendix E – Interval and mean time between dates)
Number of days between Date1 and Date2 Number of years between Date1 and Date2
Based on unknown date components and existing conditions between Date1 and Date2, found the right expression to compute the number of days between Date1 and Date2 using the following table.
Evaluate the expression.
Return rounded result.
Based on unknown date components and existing conditions between Date1 and Date2, found the right expression to compute the number complete years between Date1 and Date2 using the following table.
Evaluate the expression.
Return truncated result.
Table
Table 51
Interval and mean time between dates calculation
Unknown date components Conditions Number of days between Date1 and Date2 Number of years between Date1 and Date2
None None Y2/M2/D2 - Y1/M1/D1 MONTH_BETWEEN (Y2/M2/D2, Y1/M1/D1) / 12
D1 Y1=Y2 AND M1=M2 ½ * (Y2/M2/D2 - Y1/M1/01) 0
Otherwise Y2/M2/D2 - Y1/M1/MIDDLE_DAY(M1) MONTH_BETWEEN (Y2/M2/D2, Y1/M1/MIDDLE_DAY(M1)) / 12
D2 Y1=Y2 AND M1=M2 ½ * (Y2/M2/LAST_DAY(Y2,M2) - Y1/M1/D1) 0
Otherwise Y2/M2/MIDDLE_DAY(M2) - Y1/M1/D1 MONTH_BETWEEN (Y2/M2/MIDDLE_DAY(M2), Y1/M1/D1) / 12
D1, D2 Y1=Y2 AND M1=M2 ½ * (Y2/M2/LAST_DAY(Y2,M2) - Y1/M1/MIDDLE_DAY(M1)) [~ 7]
Note: Given the small difference between all possible cases, 7 can be used for all cases.
Case 1: there are 31 days in M1: (31-16)/2=7.5
Case 2: there are 30 days in M1: (30-16)/2=7
Case 3: there are 29 days in M1: (29-15)/2=7
Case 4: there are 28 days in M1: (28-15)/2=6.5
0
Otherwise Y2/M2/MIDDLE_DAY(M2) - Y1/M1/MIDDLE_DAY(M1) MONTH_BETWEEN (Y2/M2/MIDDLE_DAY(M2), Y1/M1/MIDDLE_DAY(M1)) / 12
M1, D1 Y1=Y2 ½ * (Y2/M2/D2 - Y1/01/01) 0
Y1<Y2 Y2/M2/D2 - Y1/07/02 MONTH_BETWEEN (Y2/M2/D2, Y1/07/02) / 12
M2, D2 Y1=Y2 ½ * (Y2/12/31 - Y1/M1/D1) 0
Y1<Y2 Y2/07/02 - Y1/M1/D1 MONTH_BETWEEN (Y2/07/02, Y1/M1/D1) / 12
D1, M2, D2 Y1=Y2 ½ * (Y2/12/31 - Y1/M1/MIDDLE_DAY(M1)) 0
Y1<Y2 Y2/07/02 - Y1/M1/MIDDLE_DAY(M1) MONTH_BETWEEN (Y2/07/02, Y1/M1/MIDDLE_DAY(M1)) / 12
M1, D1, D2 Y1=Y2 ½ * (Y2/M2/MIDDLE_DAY(M2) - Y1/01/01) 0
Y1<Y2 Y2/M2/MIDDLE_DAY(M2) - Y1/07/02 MONTH_BETWEEN (Y2/M2/MIDDLE_DAY(M2), Y1/07/02) / 12
M1, D1, M2, D2 Y1=Y2 ½ * (Y2/12/31 - Y1/07/02) [= 91]
Note: Since the outcome is constant, 91 can be used directly.
0
Y1<Y2 Y2/07/02 - Y1/07/02 MONTH_BETWEEN (Y2/07/02, Y1/07/02) / 12

Used by

  • Data loading – posting.
  • Tabulation master file

Appendix F – Auxiliary tables

This section describes all auxiliary tables used by several processes, namely:

  • Delete CCR ID;
  • Alternate surname;
  • Internal Record Linkage – Don't Link Cross Reference;
  • Death Clearance – Don't Link Cross Reference.

Delete CCR ID

Description

This table keeps a log of patient record deletions.

Content

  • CCR identification number: The CCR identification number of the deleted patient record.
  • Reporting province/territory: The reporting province/territory of the deleted patient record.
  • Patient identification number: The patient identification number of the deleted patient record.
  • Date of deletion: The date of the day the patient record was deleted or merged with another.
  • New CCR_ID: The CCR identification number of the remaining patient record when two patient records are merged through internal record linkage resolution.
  • Process: Code indicating which process has deleted the patient record. Possible values are:
    1. Data loading process through posting step.
    2. Internal record linkage through resolution step.

Usage

This table can be used to know how and when a patient record has been deleted. This is especially useful when providing feedback to PTCR about an input patient record that is rejected because the corresponding base patient record is not found on the CCR.

Used By

  • Data loading – posting
  • Internal record linkage
Table
Revision (Delete CCR ID)
Year Description
Not applicable Not applicable

Alternate surname

Description

This table keeps a copy of other patient surnames used since a patient enters the CCR.

Content

  • CCR identification number: The CCR identification number of the patient.
  • Surname: Former surname used by the patient.

Usage

This table is used during record linkage activities to augment the chances of a link between two records. This is useful when a patient surname changed overtime. Generally speaking, an additional patient record is created for every alternate patient surname. Doing so will allow a better link between a jurisdiction that uses the former patient surname and another jurisdiction that uses the latter patient surname.

Used By

  • Data loading – posting;
  • Internal record linkage – Record explosion;
  • Death clearance process – Record explosion.
Table
Revision (Alternate surname)
Year Description
Not applicable Not applicable

Internal Record Linkage – Don't Link Cross Reference

Description

This table keeps a log of potential duplicate patient record pairs that have been reviewed and rejected by PTCR through the Internal Record Linkage process.

Content

  • CCR Identification Number 1: The CCR Identification Number of the first patient.
  • CCR Identification Number 2: The CCR Identification Number of the second patient.
  • Resolution Date: The date when the Resolution step of the Internal Record Linkage process has run and has created the entry. (Format: YYYYMMDD)

Usage

This table is used during Internal Record Linkage process to avoid resending for review potential duplicate patient records that have been already reviewed and rejected by PTCR.

Used By

  • Data Loading – Posting;
Table
Internal Record Linkage – Don't Link Cross Reference
Year Description
Not applicable Not applicable

Death Clearance – Don't Link Cross Reference

Description

This table keeps a log of Death Confirmation refused by PTCR through the Death Confirmation Refusal Process.

Content

  • CCR Identification Number: The CCR Identification Number of the patient.
  • Date of Death: The Date of Death as specified on the rejected Death Event (format: YYYYMMDD);
  • Place of Death: The Place of Death as specified on the rejected Death Event;
  • Death Registration Number: The Death Registration Numner as specified on the rejected Death Event
  • Refusal Date: The date when the Death Confirmation Refusal has been processed (Format: YYYYMMDD)

The Year of Death, the Place of Death and the Death Registration Number altogether create a key that uniquely identifies a Death Event.

Usage

This table is used during Death Clearance process to avoid resending for review Death Clearance Confirmation that have been already reviewed and rejected by PTCR.

Used By

  • Data Loading – Posting (Death Confirmation Refusal);
  • Internal Record Linkage – Resolution;
  • Death Clearance – Probabilistic Linkage.
Table
Revision (Death Clearance – Don't Link Cross Reference)
Year Description
2004 Reporting Province and Patient Identification Number have been removed from this table since they are not part of the Patient Primary Key and were not maintained upon Patient Reversal of Ownership.

Appendix G – Guidelines for reporting grade, differentiation or cell indicator

Note: The CCR captures Grade for "invasive" tumours only beginning with January 1, 2004 data to accommodate grade collection in the CS Algorithm. These guidelines apply to January 1, 2006 data.

The CCR does not collect Grade for "in situ" tumours.

All CCR codes are based on the SEER codes as defined in the SEER Program Coding and Staging Manual 2004. The intent is to collect histopathologic grade however there are recognized anatomical site exceptions (for example, kidney) that apply other grading schemes.

Site Specific Grade Guidelines (page 4) take precedence over the General Coding RULES (page 2); use the General Coding Rules only when there are no Site Specific Grade Guidelines.

Grade, Differentiation (Codes 1, 2, 3, 4, 9)

Pathologic testing determines the grade, or degree of differentiation, of the tumour. For cancers, the grade is a measurement of how closely the tumour cells resemble the parent tissue (organ of origin). Well differentiated tumour cells closely resemble the tissue from the organ of origin. Poorly differentiated and undifferentiated tumour cells are disorganized and abnormal looking; they bear little or no resemblance to the tissue from the organ of origin.

Pathologists describe the tumour grade by levels of similarity. Pathologists may define the tumour by describing two levels of similarity (two-grade system); by describing three levels of similarity (three-grade system); or by describing four levels of similarity (four-grade system). The four-grade system describes the tumour as grade I, grade II, grade III, and grade IV (also called well differentiated, moderately differentiated, poorly differentiated, and undifferentiated/anaplastic). These similarities/differences may be based on pattern (architecture), cytology, or nuclear features or a combination of these elements depending upon the grading system that is used. The information from this data item is useful for determining prognosis.

Cell Indicator (Codes 5, 6, 7, 8, 9)

Describes the lineage or phenotype of the cell that became malignant. Cell indicator codes apply to hematopoietic malignancies (ICD-O-3 range 9590-9989) and for these diagnoses cell indicator takes precedence over grade/differentiation. Note: See the ICD-O-3 chapter Morphology (page 67)for further instructions on coding grade.

CCR Codes:

1 Grade I; grade i; grade 1; well differentiated; differentiated, NOS
2 Grade II; grade ii; grade 2; moderately differentiated; moderately well differentiated; intermediate differentiation
3 Grade III; grade iii, grade 3; poorly differentiated; dedifferentiated
4 Grade IV; grade iv; grade 4; undifferentiated; anaplastic
5 T-cell; T-precursor
6 B-Cell; Pre-B; B-precursor
7 Null cell; Non T-non B
8 NK cell (natural killer cell) (effective beginning with diagnosis 1/1/1995)
9 Grade/differentiations unknown, not stated, or not applicable

GENERAL CODING RULES

  1. If there is any confusion relating to grade, we strongly recommend consulting the pathologist for confirmation.

    Example: To determine grade when there are multiple pathology consults.
  2. The site-specific coding guidelines (pages 4-9) include rules for coding grade for the following primary sites: breast, kidney, prostate, CNS, lymphoma, leukemia and sarcoma.
  3. Code the grade from the final diagnosis in the pathology report. If there is more than one pathology report, and the grades in the final diagnoses differ, code the highest grade for the primary site from any pathology report.
  4. If grade is not stated in the final pathology diagnosis, use the information in the microscopic section, addendum, or comment to code grade.
  5. If there is no tissue diagnosis (pathology or cytology report), code the grade from the Magnetic Resonance Imaging (MRI) or Positron Emission Tomography (PET).
  6. If more than one grade is recorded for a single tumour, code the highest grade, even if it is a focus.

    Example: Pathology report reads: Grade II adenocarcinoma with a focus of undifferentiated adenocarcinoma. Code the tumour grade as grade 4, CCR Code 4.
  7. Code the grade information from the consultation or tumour board round if the specimen is sent to a specialty pathology department for a consult.
  8. Code the grade from the primary tumour only, never from a recurrence or metastatic site (distant and/or regional) even if this is the only reference to grade that you have.
  9. Code the grade for all unknown primaries to 9 (unknown grade) unless grade is implied by histology (i.e. anaplastic carcinoma (grade = 4).
  10. Some terms in ICD-O-3 carry an implied statement of grade. These histologies must be reported with the correct grade as stated below even if the primary site is unknown:
    8020/34 Carcinoma, undifferentiated
    8021/34 Carcinoma, anaplastic
    8331/31 Follicular adenocarcinoma, well differentiated
    9082/34 Malignant teratoma, undifferentiated
    9083/32 Malignant teratoma, intermediate type
    9401/34 Astrocytoma, anaplastic
    9451/34 Oligodendroglioma, anaplastic
    9511/31 Retinoblastoma, differentiated
    9512/34 Retinoblastoma, undifferentiated
  11. Code the grade of the invasive component when the tumour has both in situ and invasive portions. If the invasive component grade is unknown and in situ is graded, code the grade as unknown (9). Note: The CCR does not capture grade for in situ (high dysplasia) cases.
  12. If a patient receives pre-operative systemic treatment for example, chemotherapy, radiotherapy, hormonal etc), code grade:
    – from a pre-treatment pathology report, if available.
    –after pre-operative systemic treatment if this is the only grade information available.

SITE SPECIFIC GRADE GUIDELINES

If the site specific guidelines do not apply or only limited information is available, then refer to the Common Grading Systems tables (page 10) and the Terminology (Four Grade) Conversion Table (page 11).

Exception: Cell indicator takes precedence over grade/differentiation for lymphomas and leukemias.

Breast Cancer

Priority Order for Coding Breast Cancer Grade Code grade in the following priority order (See following table):

  1. Bloom-Richardson (BR) scores 3-9 converted to grade
  2. Bloom Richardson (BR) grade (low, intermediate, high)
  3. Terminology
    a. Differentiation (well differentiated, moderately differentiated, etc)
  4. Histologic grade (Breast Grade NOS, invasive cancer, histologic grade is implied).
    a. Grade 1/I/i, grade 2/II/ii, grade 3/III/iii, grade 4/IV/iv

Note: The conversion of low, intermediate, and high grade for breast is different from the conversion used for all other tumours. Do not use three-grade conversion for breast primaries (see page 10).

Table
Breast Grading Conversion Table
BR Scores BR Grade Terminology Histologic Grade CCR Code
3, 4, 5 Low Well differentiated I/III; 1/3 1
6, 7 Intermediate Moderately differentiated II/III; 2/3 2
8, 9 High Poorly differentiated III/III; 3/3 3

Bloom-Richardson (BR)

  1. BR may also be called: modified Bloom-Richardson, Scarff-Bloom-Richardson, SBR grading, BR grading, Elston-Ellis modification of Bloom Richardson score, the Nottingham modification of Bloom Richardson score, Nottingham-Tenovus, or Nottingham grade
  2. BR may be expressed in scores (range 3-9)The score is based on three morphologic features of "invasive no-special-type" breast cancers (degree of tubule formation/histologic grade, mitotic activity, nuclear pleomorphism of tumour cells)
  3. BR may be expressed as a grade (low, intermediate, high)
  4. BR grade is derived from the BR score
  5. Use the Breast Grading Conversion Table above to convert the score, grade or terminology into the CCR code

Kidney Cancer

Fuhrman grade describes the nucleus of the cell. If Fuhrman grade is not specified, nuclear grade has second priority.For kidney, nuclear grade is more important (priority) than looking at the overall histologic grade of the tumor.

Note: Use the general coding rules for coding grade for Wilms tumour (8960) as these prioritization rules do not apply.

Priority Order for Coding Kidney Cancer Grade

Code grade in the following priority order:

  1. Fuhrman grade (grade 1, 2 ,3 ,4)
  2. Nuclear grade (grade 1, 2, 3, 4)
  3. Terminology (well diff, mod diff)
  4. Histologic grade (grade 1, grade 2)
Table
Fuhrman Conversion Table
Grade Differentiation or Descriptor CCR Code
Grade i Well differentiated 1
Grade ii Moderately differentiated 2
Grade iii Poorly differentiated 3
Grade iv Undifferentiated 4

Prostate

Nuclear grade is not equivalent to any part of the Gleason grading process (cannot be converted from Gleason's Score or Pattern).

Priority Rules for Coding Prostate Cancer Grade

Code grade in the following priority order:

  1. Gleason's Grade (score or pattern)
  2. Terminology
    a. Differentiation (well differentiated, moderately differentiated, etc.)
  3. Histologic grade
    a. Grade 1/I/i, grade 2/II/ii, grade 3/III/iii, grade 4/IV/iv

Use the following table to convert Gleason's pattern or score into CCR codes:

Table
Gleason Conversion Table
Gleason's Score (Gleason's Grade) Gleason's Pattern Terminology Histologic Grade CCR Code
2, 3, 4 1, 2 Well differentiated I 1
5, 6 3 Moderately differentiated II 2
7, 8, 9, 10 4, 5 Poorly differentiated III 3

Note: if Gleason's score or pattern is not specified, see examples below:

Gleason's Pattern

Prostate cancers are commonly graded using Gleason's score or pattern. Gleason's grading is based on a 5-level system, meaning it is based on 5 histologic patterns. The pathologist will evaluate the primary (majority) and secondary patterns for the tumour. The pattern is usually written as a sum, with the majority pattern appearing first and the secondary pattern as the second number.

Example: A Gleason pattern of 2 + 4 means that the primary pattern is 2 and the secondary pattern is 4.

Gleason's Score

The patterns are added together to create a score.

Example: If the pattern is 2 + 4, the score is 6 (the sum of 2 and 4).

When reviewing prostate grading terminology and attempting to determine whether it represents a grade or a score, consider the following results:

  • less than or equal to 5 are coded as a pattern and
  • more than 5 are coded as a score.
  1. If the pathology report contains only one number, and that number is less than or equal to 5, it is a pattern. Please see General Coding Rule 1.
  2. If the pathology report contains only one number, and that number is greater than 5, it is a score. Please see General Coding Rule #1.
  3. If the pathology report specifies a specific number out of a total of 10, the first number given is the score.

    Example: The pathology report says "Gleason's 3/10". The Gleason's score would be 3.
  4. If there are two numbers less than 6, assume they refer to two patterns. The first number is the primary pattern and the second is the secondary pattern.

    Example: If the pathology report says "Gleason's 3 + 5," the Gleason's score would be 8, the sum of 3 and 5.

Central Nervous System

  1. WHO grading forbrain is used to estimate prognosis and can refer to both benign and malignant lesions. It is never coded in the 6th digit of the histology code.
    a. WHO grade is captured in Collaborative Stage Site Specific Factor 1.
  2. Pathologists do not always describe ICD-O-3 grade or differentiation of CNS tumors.a. If no grade is given, code the 6th digit histology code to '9' unknown.
    b. Some histologies include/imply grade in the terms; in these cases the grade can be coded (for example, anaplastic astrocytoma 9401/34). SeeGeneral Coding Rule 10.
  3. Do not automatically code glioblastoma multiforme as grade IV, if no grade is given, code to '9' unknown. (9440/39).
  4. All glioma's with histology 938-946 with the exception of those with an implied grade are '9' not applicable.
  5. Grade astrocytomas according to ICD-O-3 rules. Do not use the WHO grade to code this field.

Lymphoma and Leukemia 9590-9989

  1. The designation of T-cell, B-cell, null cell, or NK cell has precedence over any statement of differentiation.
    a. Code ANY statement of T-cell, B-cell, null cell, or NK cell including:
    T-cell (code 5)
    Cortical T
    Mature T
    Pre-T
    Pro-T
    T-cell phenotype
    T-precursor
    B-Cell (code 6)
    B-cell phenotype
    B-precursor
    Pre-B
    Pre-pre-B
    Pro-B
    Null-Cell; Non-T-non-B (code 7)
    Null-cell
    Non T-non-B
    Common cell
    NK (Natural Killer) cell (code 8)
    NK/T cell
    Cell type not determined, not stated or not applicable (code 9)
    Combined B cell and T cell

    Note: The 'code to the higher code' rule usually does not apply to phenotypes.

    b. Code information on cell type from any source, whether or not marker studies are documented in the patient record.

    Example: The history portion of the medical record documents that the patient has a T-cell lymphoma. There are no marker studies on the chart. Code the grade as T-cell.
  2. Do not use the terms "high grade," "low grade," and "intermediate grade" to code differentiation or Cell Indicator field. These terms refer to prognosis, not grade.
    a. In some instances, the term 'grade' does not imply differentiation and should not be used to code the 6th digit of the morphology code. It is important to recognize when the term "grade" refers to category and when it refers to biologic activity. When describing some diseases, pathologists use the term "grade" as a synonym for "type" or "category." Registrars recognize the term "grade" as an indicator of cell differentiation that is coded in the 6th digit of the ICD-O morphology code.
    i. The grade descriptors for nodular sclerosing Hodgkin lymphoma and follicular lymphoma are actually types or categories of these diseases. The 6th digit should not be coded as grade 1, 2 or 3 for these cases.
    ii. Poorly differentiated lymphocytic lymphoma or a B-cell or T-cell lymphoma should be coded in the 6th digit of the morphology code.
    iii. Other terms described as high grade or low grade as part of the diagnostic term may be used to code the 6th digit of the morphology code.
  3. Do not code the descriptions "Grade 1," "Grade 2," or "Grade 3" in the Grade, Differentiation or Cell Indicator field.
  4. Codes 9950-9989 rarely have a grade associated with them and are generally coded as a '9'.
  5. Grade codes 5-8 are T-cell, B-cell, or NK cell indicators used for leukemias and lymphomas only. Therefore, codes 5-8 may only be used with morphologies in the range of 9590-9989.

Sarcoma

Several grading systems exist and may be used to grade sarcomas. The following table incorporates two, three and four-tier grading systems. If a sarcoma is graded using terminology, refer to the Terminology Conversion Table on page 11.

Table
Gleason Conversion Table
Grade Differentiation or Descriptor CCR Code
Low Grade 1/2 1/3 1/4 2/4 2
Intermediate Grade 2/3 3
High Grade 2/2 3/3 3/4 4/4 4

Common Grading Systems

Two-Grade System

There are some cancers for which a two-grade system is used (i.e. colon cancer, papillary transitional cell carcinoma, bladder, endometrial stromal sarcoma). The patterns of cell growth are measured on a scale of 1 or 2 (also referred to as low and high grade). The expected outcome is more favorable for lower grades.

  • If the grade is listed as 1/2 or as low grade, assign code 2.
  • If the grade is listed as 2/2 or as high grade, assign code 4.
Table
Two-Grade Conversion Table
Grade Differentiation /
Description
CCR Code
1/2, I/II Low grade 2
2/2, II/II High grade 4

Three-Grade System

There are several cancers for which a three-grade system is used (for example peritoneum, endometrium, fallopian tube, prostate, bladder and soft tissue sarcoma). The patterns of cell growth are measured on a scale of 1, 2, and 3 (also referred to as low, medium/intermediate, and high grade). This system measures the proportion of cancer cells that are growing and making new cells and how closely they resemble the cells of the host tissue. Thus, it is similar to a four-grade system (see Terminology Conversion Table on page 10), but simply divides the spectrum into 3 rather than 4 categories (see Three-Grade Conversion Table below). The expected outcome is more favorable for lower grades.

  • If the grade is listed as1/3 or as low grade, assign code 2.
  • If the grade is listed as 2/3 or as medium/intermediate grade, assign code 3.
  • If the grade is listed as 3/3 or as high grade, assign code 4.

Use the following table to convert the grade to CCR codes:

Table
Three-Grade Conversion Table*
Grade Differentiation /
Description
CCR Code
1/3, I/III Low grade 2
2/3, II/III Medium/Intermediate grade 3
3/3, III/III High grade 4

*Do not use for breast primaries

Terminology Conversion Table
This system measures the proportion of cancer cells that are growing and making new cells and how closely they resemble the cells of the host tissue. The expected outcome is more favorable for lower grades.

Table
Terminology Conversion Table
Description Grade CCR Code
Differentiated, NOS I 1
Well differentiated I 1
Fairly well differentiated II 2
Intermediate differentiation II 2
Low grade I-II 2
Mid differentiated II 2
Moderately differentiated II 2
Moderately well differentiated II 2
Partially differentiated II 2
Partially well differentiated I-II 2
Relatively or generally well differentiated II 2
Medium grade, intermediate grade II-III 3
Moderately poorly differentiated III 3
Moderately undifferentiated III 3
Poorly differentiated III 3
Relatively poorly differentiated III 3
Relatively undifferentiated III 3
Slightly differentiated III 3
Dedifferentiated III 3
High grade III-IV 4
Undifferentiated, anaplastic, not differentiated IV 4
Non-high grade 9

References:

  1. SEER Program Coding and Staging Manual (2004) Published by the U. S. Department of Health & Human Services (Bethesda, MD), 2004. NIH Publication Number 04-5581.
  2. International Classification of Diseases for Oncology, Third Edition. WHO.
  3. NAACCR Edit Logic Report for Metafile NAACR10E.EMF
  4. Centers for Disease Control and Prevention. Data collection of primary central nervous system tumors. National Program of Cancer Registries Training Materials. Atlanta, Georgia: Department of Health and Human Services, Centers for Disease Control and Prevention, 2004.
Table
Revision (Terminology Conversion Table)
Year Description
2006 New appendix

Appendix H – CCR Ambiguous Terms

Effective for January 1, 2001 data and forward

The Data Quality Management Committee, with the approval of the CCR, recommends that the SEER Program list4 of ambiguous terms be adopted as the Canadian list when identifying cancer cases5. Where possible, it is best to obtain additional information or consult with a pathologist for clarification. If neither is possible, use the following list for determining whether to register/report a cancer case to the CCR.

Table
Appendix H – CCR Ambiguous Terms
Consider as diagnostic of cancer NOT considered diagnostic of cancer*
apparent(ly) cannot be ruled out
appears to equivocal
comparable with possible
compatible with potentially malignant
consistent with questionable
favor(s) rule out
malignant appearing suggests
most likely worrisome
presumed  
probable  
suspect(ed)  
suspicious (for)  
typical of * without additional information
Exception:
If cytology is reported as "suspicious", do not
interpret this as a diagnosis of cancer.
Abstract the case only if a positive biopsy
or a physician's clinical impression of cancer supports the cytology findings.
Do not include patients who have a diagnosis consisting only of these terms.
Table
Revision (Appendix H – CCR Ambiguous Terms)
Year Description
2006 New appendix

Appendix I – Guidelines for Abstracting and Determining Death Certificate Only (DCO) Cases for Provincial/Territorial Cancer Registries (PTCRs) in Canada (for T12 and P18)

Cancer registries have identified access to death information as a critical component for operating a high quality program. There are two main reasons for acquiring this particular data, including:

  1. Determination of Death Status for Currently Enrolled Cases: Once a registry has enrolled a case of cancer the addition of death information can provide a more complete picture of how cancer has impacted this individual. Death information on a specific case can remove it from active follow up routines and allow registries to perform more accurate and complete survival calculations.
  2. Case Completeness: To ensure a high level of case completeness a registry typically relies on a variety of methods to ascertain newly diagnosed cancers. One common method is to complete a linkage to vital statistics information regarding cause(s) of death. If an individual is reported with a cancer cause of death and is not found in the registry the case should be followed back to determine if it meets the criteria for cancer registration.

Therefore it is important that PTCRs enter into agreements with Vital Statistics registrars to receive at a minimum all cases for which cancer is listed on any part of the medical certificate of death. In Canada death registration is subject to provincial mandates and includes the completion of a Statement of Death and/or a Medical Certificate of Death. Cancer registries receive death notifications in various formats i.e., hardcopy, electronically, or computer files and at varying intervals for example, monthly, quarterly or annually.

The ideal is to receive notification of all deaths including all causes of death occurring within the province, enabling the registry to perform a comprehensive death clearance. When linked with the registry database this information will result in both matched and non-matched cancer incidence. A death certificate with a reportable tumour listed that does not link to other records in the cancer registry is called a Death Certificate Notification (DCN) and requires further investigation. DCNs include cases in which the underlying cause of death is cancer as well as cases in which cancer is simply mentioned on the death certificate. When additional information is obtained the case should be registered with that year's incidence data. If additional information cannot be obtained, the case is a true Death Certificate Only (DCO) and can be reported as such to the Canadian Cancer Registry (CCR).

Death certificate information is a critical component in the registry certification process operated by the North American Association of Central Cancer Registries (NAACCR). To be eligible for NAACCR certification a PTCR must participate in the NAACCR Call for Data. The data criteria reviewed during this process include: Completeness, passing EDITS, DCO, Interval for Criteria, Timeliness, Duplicate Reports and Missing Data Fields in Sex, Age, County and Race. The DCO certification requirement is less than 5% silver and less than 3% gold.

The CCR and NAACCR accepted formula for calculating the DCO rate is:

The CCR and NAACCR accepted formula for calculating the DCO rate is:

Differences exist in the denominator as CCR does not include in situ bladder cancers and NAACCR does.Where cancer cases = all unduplicated invasive cancers + in situ bladder cancers within the diagnosis year for state (provincial) residents. These include all cases identified and abstracted from the death clearance project and all true DCOs. This information is included in the NAACCR Call for Data.

(Source: NAACCR Series II: Calculating the DCO Rate)

1. Definitions

Cause of Death

The causes of death to be entered on the medical certificate of cause of death are all those diseases; morbid conditions or injuries which either resulted in or contributed to death and the circumstances of the accident or violence which produced any such injuries.

(Source: World Health Assembly, Article 23 of the Constitution of the World Health Organization. ICD-9 pg. 763)

Death Certificate Notification (DCN)

Death certificate notification is a cancer death identified from any source including a Vital Statistics Death Registration that could not be linked (electronically or manually) to an existing cancer record.

Death Certificate Only (DCO)

"Death certificate only" means that the only source of information about the case was a death certificate. This category includes deaths where either the Underlying Cause of Death is cancer, or there is any mention of cancer on the death certificate.
(Source: CCR – Report No. 3.2.2. – Input Data Dictionary, page 79. Revised on: 17/06/94.)As of January 1, 2000 mortality information in Canada was captured by Vital Statistics using the ICD-10 classification system.

Follow Back (FB)

Followback is the process of actively searching for additional information on DCNs at the patient and disease level and updating the cancer database as a complete abstract when possible. If additional information cannot be found the case is a true DCO.

Underlying Cause of Death

The underlying cause of death is (a) the disease or injury which initiated the train of events leading directly to death, or (b) the circumstances of the accident or violence which produced the fatal injury.

(Source: World Health Assembly, Article 23 of the Constitution of the World Health Organization. ICD-9 pg. 763)

2. Process

The process for determining a DCO case will vary and should be modified to meet the requirements of the individual PTCRs. PTCRs should match DCNs to their database; those cancer deaths that do not match require further investigation. Processing is required when the decedent was a resident of your province at the time of death, and a reportable cancer is mentioned on the DCN and no record is found in the PTCR database. No further processing is required when the only tumour mentioned on the DCN is a non-reportable tumour, the decedent was a non-resident of your province (forward to province of ownership if agreements are in place) or when a non-cancer death is identified.

The underlying cause of death field is intended to capture a patient's official cause of death. As this variable is important for record linkage purposes and has legal implications, the death information coded and provided to cancer registries from provincial and territorial Vital Statistics offices should not be altered even when cancer registries have more complete or detailed diagnostic information. The only PTCR reported data that may be changed on the CCR patient record because of a confirmation of death are: Date of Death, Province/Country of Death and Death Registration Number.
(Source, CCR – Report No. 3.2.1 – Coding and Reporting Guidelines – December 18, 1995)

A. DCN Match to Provincial/Territorial cancer registry database. (Example: positive match on four variables for example, HIN, Surname, Sex and DOB).

  • Determine same primary versus new primary.
  • Identify discrepancies between cancer on certificate of death and registry diagnosis codes.
  • Update missing or incomplete fields.

An inconclusive Match shows some discrepancies between identifiers in the incidence and death data but the records may belong to the same person. (Example: positive or close match on the four variables for example, HIN positive match, mismatch with surname, sex or DOB.

  • Visual verification to determine if it's "close enough" to be judged a match or non-match.
  • FB to make a valid determination.

Followback (FB) for new primaries or abstract for additional DCO primaries. Edit and review cases in registry database not microscopically confirmed.

B. DCO. DCN cancer death, Non-match to Provincial/Territorial cancer registry database.
Nonmatched cancer deaths are cleared in a variety of ways, depending on the PTCR's ability to staff a DCO clearance program. Each non-match cancer death must be manually reviewed for reportability and to ascertain where to follow back. Followback sources include facility (chronic care, hospital/nursing home), coroner and attending physician where the death occurred.

Based upon the information received from follow back, the case may be abstracted as:

  • FollowBack is recommended by form letter to the institution (Appendix A) where the patient expired and secondly to the informant (Appendix B) who signed the death certificate to obtain additional information.
  • Cases that are identified after followback should be added to the appropriate diagnosis year as actual incident records (not DCOs).
  • Cases where no additional information is obtained should be reported to the CCR as a DCO.

C. Standard conventions for abstracting DCO cases:

  1. If FB is not returned from facility/physician, the information from the DCN may be used and the case considered a DCO.
  2. If a date of diagnosis or an approximate date cannot be established, the case is a DCO and the date of death is used as the date of diagnosis.
  3. Follow standard coding conventions for site/histology.
  4. There may be more than one primary noted on the Death Certificate. More than one DCO abstract may be required.
  5. Code the histology from the Death Certificate, i.e., squamous cell carcinoma, adenocarcinoma, etc., if available. If "carcinoma" is recorded, code as 8010/3. If "cancer" is recorded, code as 8000/3.
  6. Code the Primary Site recorded on the Death Certificate, i.e., lung, prostate, breast.
  7. Melanoma, unknown primary site code to Malignant melanoma of skin, site unspecified (ICD-9 172.9, ICD-10 C43.9).
  8. Lymphoma, unknown primary site code to Lymph Nodes, NOS (ICD-9 202.8, ICD-10 C85.9).
  9. Leukemia is always coded to Bone Marrow (ICD-9 208.9, ICD-10 C95.9).
  10. Watch for primary sites where metastases are common (Lung, Liver, Brain and Bone).
  11. The death certificate may state "metastatic liver cancer" or "metastatic bone cancer". If it is unclear if the site recorded is the primary or a metastatic site, code to Unknown Primary Site (ICD-9 199.0, ICD-10 C80.9).
  12. Stage is always "unknown".
  13. Diagnostic confirmation is always "unknown".
  14. No treatment is recorded, even if noted on the DCN.
  15. Include DCO cases in edits.

(Cover letter to Institution)

PTCR

Inside address

To Whom It May Concern

The Registry Name is presently completing the Death Certificate Only (DCO) follow back process for year/s. DCO means that the only source of information about the case was a death certificate. The death certificate identified the decedent as having expired in your facility however the cancer registry has no prior information on this case through its routine data collection. Data collection is legislated by act/privacy act. Enclosed you will find a Registry Form letter for completion, it is important that we collect the initial date and address at time of diagnosis. If, your records do not identify this patient as having cancer please indicate and we will adjust our records accordingly.

By completing the enclosed Registry Form letter we can finalize the information on this patient. Complete information permits the calculation of survival rates on patients diagnosed with cancer, facilitates epidemiological studies and improves the completeness and quality of reported death and other demographic information. Your continued support in improving the quality of data allows us to participate in provincial and national studies and to provide accurate statistics on an ongoing basis to our stakeholders.

If there are any questions or concerns, please do not hesitate to contact me, contact name at facility name and phone number.

Sincerely yours,

Signature

Enclosure

(Cover letter to Informant)

PTCR

Inside address

Dear Insert name here,

The Registry Name is presently completing the Death Certificate Only (DCO) follow back process for year/s. DCO means that the only source of information about the case was a death certificate. The death certificate stated the decedent had cancer, however the cancer registry has no prior information on this case through its routine data collection. Data collection is legislated by act/privacy act. The death certificate identifies you as the last attending physician at time of death for patient name. Enclosed you will find a Registry Form letter for completion, it is important that we collect the initial date and address at time of diagnosis. If, your records do not identify this patient as having cancer please indicate and we will adjust our records accordingly.

By completing the enclosed Registry Form letter we can finalize the information on this patient. Complete information permits the calculation of survival rates on patients diagnosed with cancer, facilitates epidemiological studies and improves the completeness and quality of reported death and other demographic information. Your continued support in improving the quality of data allows us to participate in provincial and national studies and to provide accurate statistics on an ongoing basis to our stakeholders.

If there are any questions or concerns, please do not hesitate to contact me, contact name at facility name and phone number.

Sincerely yours,

Signature

Enclosure

Table
Death Certificate Notification (DCN)
Year Description
2007 New appendix

Appendix J – Interval between two dates (complete or partial)

The following algorithm can be used to assess the number of days between two dates. When both dates are complete, the algorithm returns the exact number of days. When one or both dates are partial, the missing parts of the dates are "derived" and the number of days returned, based on the derived dates. This algorithm cannot be used if one or more dates is totally unknown, i.e. equal to '99999999'. The returned value is always a positive whole number (including zero).

Definitions

Let Date1 and Date2 be the two dates for which the interval must be calculated and where Date1 <= Date2.

Let Y1, M1 and D1 be the year, month and day of date1.
Let Y2, M2 and D2 be the year, month and day of date2.

Let DIFF_DAYS (Date1, Date2) be a function that returns the number of days between date1 and date2.

Table
Assumptions if there are partial dates
Date1 is a partial date Date2 is a partial date
If MONTH is not reported then MONTH is assumed to be '01'.
If DAY is not reported then DAY is assumed to be '01'.
If MONTH is not reported then MONTH is assumed to be '12'.
If DAY is not reported then DAY is assumed to be the last day of the reported MONTH (28, 29, 30 or 31).

Examples

Date1 = 20060627.
Date2 = 20060930.

DIFF_DAYS (20060627, 20060930)

Date1 = 20060699
Date2 = 20070999.

DIFF_DAYS = (20060601, 20070930)

Date1 = 20069999
Date2 = 20079999

DIFF_DAYS = (200601, 20071231)

Table
Appendix J – Interval between two dates (complete or partial)
Year Description
2008 New appendix

Appendix K – HL7 Flavors of Null table

Definition: If a value is an exceptional value (NULL-value), this specifies in what way and why proper information is missing.

NAACCR
Code
HL7
Code
Name Definition
10 NI no information No information whatsoever can be inferred from this exceptional value. This is the most general exceptional value. It is also the default exceptional value. It is unknown whether this event occurred (for example, radiation treatment).
11 NA not applicable No proper value is applicable in this context (for example, last menstrual period for a male).
12 UNK unknown A proper value is applicable but not known. This event occurred, but the date is unknown (for example, birth date).
13 NASK not asked This information has not been sought (for example, patient was not asked).
14 ASKU asked but
unknown
Information was sought but not found (for example, patient was asked but did not know).
15 NAV temporarily
unavailable
Information is not available at this time, but it is expected that it will be available later.
16 OTH* other* The actual value is not an element in the value domain of a variable (for example, concept not provided by required code system).
17 PINF positive infinity Positive infinity of numbers.
18 NINF negative infinity Negative infinity of numbers.
19 MSK masked Information on this item is available, but it has not been provided by the sender due to security, privacy, or other reasons. An alternate mechanism for gaining access to this information may be available. Note: Using this null flavor does provide information that may be a breach of confidentiality. Its primary purpose is for those circumstances where it is necessary to inform the receiver that the information does exist.
20 NP not present Value is not present in a message. This is only defined in messages, never in application data! All values not present in the message must be replaced by the applicable default or No-Information (NI) as the default of all defaults.

The null flavors are a general domain extension of all normal data types. Note the distinction between value domain of any data type and the vocabulary domain of coded data types. A vocabulary domain is a value domain for coded values, but not all value domains are vocabulary domains.

* The null flavor Other is used whenever the actual value is not in the required value domain. This may be, for example, when the value exceeds some constraints that are defined too restrictively (for example, age < 100 years).

Note: Null flavors are applicable to any property of a data value or a higher-level object attribute. Where the difference of null flavors is not significant, ITs are not required to represent them. If nothing else is noted in this specification, ITs need not represent general NULL flavors for data-value property.

Appendix T – Residency guidelines in Canada

To ensure comparability of definitions of cases and the population at risk (numerator and denominator), the Canadian Cancer Registry (CCR) rules for determining residency at time of diagnosis are to be identical or comparable to rules used by the Canadian Census Bureau, whenever possible.

The residence at diagnosis is generally the place of usual residence, as stated by the patient or, as stated by the Census Bureau, 'the dwelling in Canada where a person lives most of the time'. Residency is their usual place of residence, regardless of where they are when diagnosed. For patients with multiple tumours, the address may be different for each primary tumour.

There are a number of situations for which the process of determining residency is not intuitive, and special guidelines have been created in order to define an individual's usual place of residence. The Data Quality Committee (DQC) for the Canadian Council of Cancer Registries (CCCR) recognizes that some Provincial/Territorial Cancer Registries (PTCRs) are removed from the direct patient contact relationship, and may not have access to the patient or the information to confirm residency. Using the provincial health insurance number (HIN) as a determining factor of residency during initial case abstraction is appropriate. When permanently relocating, the HIN from the previous province of residence is valid for three months. However, if the case is identified as a potential duplicate during a Record Linkage cycle, additional information should be obtained before confirming residency, as it may not be appropriate to default to using province of HIN, as the primary residence.

PTCRs are encouraged to use these guidelines to determine residency for categories of persons for whom residence is not immediately apparent.

  1. Residence (one residence). The dwelling in Canada where a person lives most of the time.
  2. Persons with more than one residence. Usual residence rule applies; however, if the time spent at each residence is equal or the abstractor is not sure which one to choose, the residence where the patient was staying on the day cancer was diagnosed should be considered the usual place of residence (see examples below).
    a) Exception: Consider the residence shared with their family as their usual place of residence, even if they spend most of the year elsewhere.
    Commuter workers living away part of the week while working: Consider the residence shared with their family as the usual place of residence, even if they spend most of the year elsewhere. (for example, parents, husbands, wives or common-law partners)
    b) Snowbirds: People who live at another residence (city, province or country) with a warmer climate. Residence should be documented as where they live most of the time.
    c) Children in joint custody: Residence should be documented as where they live most of the time. If time is equally divided, their residence is documented as where they were staying on the day cancer was diagnosed.
  3. Patients with rural addresses. If the information provides a rural address only, which may be the post office box, record the address as stated, but make every attempt, within your resources, to identify the actual physical place of residence at time of diagnosis.
  4. Patients with no usual place of residence (i.e. homeless, transient people). Residents who do not have a usual place of residence should be documented as where they were staying on the day cancer was diagnosed.
  5. Institutional collective dwellings (Collective dwellings that provide care or assistance services). Persons in institutions with no other usual place of residence elsewhere in Canada, or persons who have been in one or more institutions for a continuous period of six months or longer, are to be considered as usual residents of the institution.
    Institutional collective dwellings include:
    a) Residents of a long-term care facility, a hospital, or a home for the aged.
    b) In homes, schools, hospitals, or wards for the physically disabled, mentally challenged, or mentally ill or in drug/alcohol treatment facilities.
    c) Inmates of correctional institutions, including prisons, jails, detention centers, or halfway houses.
    d) Children in juvenile institutions, such as residential care facilities for neglected or abused children or orphanages.
    e) For abused women, or for runaway or neglected youth please see section 6 - Non-institutional collective dwellings.
  6. Non-institutional collective dwellings (Collective dwellings that do not provide care or assistance services). Residence should be documented as their usual residence, if they report one (the place where they live most of the time) or otherwise at the inn, hotel, etc.
    Non-institutional collective dwellings include:
    a) Inns, hotels, motels and hostels.
    b) YMCAs/YWCAs, or public or commercial campgrounds.
    c) Military bases.
    d) Migrant workers (lumber / mining camps & farms).
    e) Members of religious orders in monasteries or convents.
    f) Shelters with sleeping facilities for people without housing, for abused women, or for runaway or neglected youth. Residence should be documented as the shelter.
  7. Students. Students who live away from home while attending school, but who return to live with their parents part of the year should consider their place of residence as their parents' home, even if they spend most of the year elsewhere.
  8. Live-ins:
    a) Live-in nannies. Residence should be documented as where they live most of the week.
    b) Foster children, boarders or housemates. Residence should be documented as where they are living at time of diagnosis.
  9. Merchant and coast guard vessels. Merchant vessels, coast guard vessels and oil rigs at sea should be documented as their usual onshore residence, if they report one (the place where they live most of the time when they are onshore) or otherwise, at their vessel's homeport.
  10. Naval vessels. Canadian Forces Naval Vessel residence should be documented as their usual onshore residence, if they report one (the place where they live most of the time when they are onshore) or otherwise, at their vessel's homeport.
  11. Armed forces. Canadian Armed Forces residence should be documented as their usual place of residence, if they report one, or otherwise, where they are stationed at time of diagnosis.
  12. Non-permanent residents (foreign citizens). Persons who hold a student or employment authorization, Minister's permit or who were refugee claimants at time of diagnosis, for a continuous period of six months or more.
    a) Citizens of foreign countries who have established a household or are part of an established household in Canada while working or studying, including family members with them. Residence should be documented as their household in Canada.
    b) Citizens of foreign countries who are living in Canadian embassies, ministries, legations or consulates. Residence should be documented as the embassy.
    c) Citizens of foreign countries temporarily traveling or visiting Canada. These cases are not reportable to the Canadian Cancer Registry.

Appendix X – CCR_ID check digit routine

The last digit of the CCR_ID is a check digit, for example, digit calculated from the other CCR_ID digits. The purpose of using a check digit is twofold: it allows the detection of some data corruption and prevents one from creating new IDs too easily. The next routine returns a check digit for a given CCR_ID.

Pseudo code


Let N1 be the first digit of CCR_ID (starting from the left)
Let N2 be the second digit of CCR_ID (starting from the left)
Let N8 be the eighth digit of CCR_ID (starting from the left)

Change the values of N2, N4, N6, N8 according to the following pattern
Initial value 0 1 2 3 4 5 6 7 8 9
New value 0 2 4 6 8 1 3 5 7 9


Let REMAINDER be the remainder of ((N1 + N2 + N3 + N4 + N5 + N6 + N7 + N8) / 10)
If REMAINDER = 0 then
RETURN 0
Else
RETURN (10 – REMAINDER)

Used by

  • Data loading – Edit
  • Data loading – posting

Appendix Z – References

Collaborative Staging Task Force of the American Joint Committee on Cancer. Collaborative Staging Manual and Coding Instructions, Version 01.04.01. Jointly published by American Joint Committee on Cancer (Chicago, IL) and U.S. Department of Health and Human Services (Bethesda, MD), 2004. NIH Publication Number 04-5496.
http://www.cancerstaging.org/cstage/index.html

Fritz A, Percy C, Jack A, et al (eds): ICD-O: International Classification of Diseases for Oncology, Third Edition. Geneva, World Health Organization, 2000.

SEER Program Coding and Staging Manual 2004, Surveillance, Epidemiology and End Results (SEER) Program, National Cancer Institute, National Institutes of Health, Bethesda, MD. NIH Publication Number 04-5581.

SEER Program Coding and Staging Manual 2007, Surveillance, Epidemiology and End Results (SEER) Program, National Cancer Institute, National Institutes of Health, Bethesda, MD. NIH Publication Number 07-5581.

Johnson CH, Peace S, Adamo P, Fritz A, Percy-Laurry A, Edwards BK. The 2007 Multiple Primary and Histology Coding Rules. National Cancer Institute, Surveillance, Epidemiology and End Results Program. Bethesda, MD, 2007. Revised April 30, 2008

NAACCR Standards for Cancer Registries, Volume II Version 11.3 - Data Standards and Data Dictionary, Thirteenth Edition.

National Cancer Institute Surveillance Epidemiology and End Results training website, American Joint Committee on Cancer. http://www.training.seer.cancer.gov/
module_staging_cancer/unit03_sec03_part00_ajcc.html

CCR Committee on Data and Quality Management - Clinical Core Data Set - March 2001 version

AJCC Cancer Staging Manual, 6th Edition, American Joint Committee on Cancer (AJCC), 2002

Facility Oncology Registry Data Standards (FORDS), revised for 2007. Published by the American College of Surgeons (ACoS) and the Commission on Cancer (COC), 2007.

Facility Oncology Registry Data Standards (FORDS) manual, revised for 2009. Published by the American College of Surgeons (ACoS) and the Commission on Cancer (COC), 2009.

Footnotes

1.The original set of ISO codes has been expanded to include individual Canadian provinces and territories and other Statistics Canada specific codes.

2. Available upon request.

3.The only source of information about the case was a death certificate. This category includes deaths where either the underlying cause of death (patient record, Field No.17) is cancer, or there is any mention of cancer on the death certificate.

4. Input records that passed successfully through all validation edits, correlation edits and other match edits.

5. Because CS and AJCC TNM data items are fairly new to CCR, it has been temporarily decided that CS and AJCC TNM errors (including fatal errors)will not prevent valid core data items from being loaded on the CCR database

6. See Appendix A – Core reference tables - ICD-9 to ICD-O-2 conversion table for details.

7. See P1 Specific values & meaning.

8. See Appendix X - CCR_ID check digit routine.

9. See P4 Specific values & meaning.

10. See P5 Specific values & meaning.

11. See P10 Specific values & meaning.

12. See Appendix A (Part III - CCR System Guide) – Core reference tables.

13. See Appendix A (Part III - CCR System Guide) – Core reference tables.

14. See P18 Specific values & meaning.

15. See T1 Specific values & meaning.

16. See Appendix X – CCR_ID check digit routine.

17. See T5 Specific values & meaning.

18. See T11 Specific values & meaning.

19. See T13 Specific values & meaning.

20. See T14 Specific values & meaning.

21. See T17 Specific values & meaning.

22. See T19 Specific values & meaning.

23. Eligible ICD-O-3 histology codes do not include '0000' since this value should have been converted to a more meaningful value during the Pre-edit processing.

24. See T22 Specific values & meaning.

25. See T23 Specific values & meaning.

26. See T24 Specific values & meaning.

27.See T25 Specific values & meaning.

28. See section 1.1.2.2 – CCR collaborative staging scope.

29. See section 1.1.2.3 – CCR AJCC TNM staging scope.

30. See Appendix C – AJCC TNM concordance tables - Valid AJCC clinical T by site.

31. See Appendix C – AJCC TNM concordance tables - Valid AJCC clinical N by site.

32. See Appendix C – AJCC TNM concordance tables – Valid AJCC clinical M by site.

33. See Appendix C – AJCC TNM concordance tables – Valid AJCC pathologic T by site.

34. See Appendix C – AJCC TNM concordance tables – Valid AJCC pathologic N by site.

35. See Appendix C – AJCC TNM concordance tables – Valid AJCC pathologic M by site.

36. See Appendix C – AJCC TNM concordance tables – Valid AJCC TNM clinical stage group by site.

37. See Appendix C – AJCC TNM concordance tables – Valid AJCC TNM staging group by site.

38. See T51 Specific values & meaning.

39. Collaborative staging data items (T27-T41) and AJCC TNM staging data items (T42-T51) may or may not be reported. See TCOR-18 and TCOR-19 respectively for more details.

40. Already enforced by TVAL15.

41. Impossible to enforce since the code that stands for 'Not Reported' also stands for 'Benign behaviour'.

42. Already enforced by TVAL21.

43. See Appendix A (Part III - CCR System Guide) – Core reference tables – ICD-9 to ICD-O-2 conversion table.

44.See Appendix A (Part III - CCR System Guide) – Core reference tables – ICD-O-2 to ICD-O-3 conversion table.

45. See Appendix A (Part III - CCR System Guide) – Core reference tables – CCR core scope.

46. See Appendix A (Part III - CCR System Guide) – Core reference tables – Invalid site and histology combinations.

47. See Appendix A (Part III - CCR System Guide) – Core reference tables – Invalid histology and behaviour combinations.

48. See collaborative staging scope in Chapter 1.

49.See Appendix C – AJCC TNM concordance tables – Valid AJCC T, N, M and stage group combination bysite.

50. Thus, unknown or not assessed AJCC clinical/pathologic T, N, M values are excluded.

51. All related patient and tumour records are rejected, but corresponding message is only attached to each conflicting patient record of the family.

52. All related patient and tumour records are rejected, but corresponding message is only attached to each conflicting tumour record of the family.

53. All related patient and tumour records are rejected, but corresponding message is only attached to each erroneous or conflicting patient record of the family.

54. The match with a delete patient transaction is covered by KIM4.

55. All related patient and tumour records are rejected, but corresponding message is only attached to each erroneous or conflicting tumour record of the family.

56. Input record that has neither core fatal errors nor core errors from all previous edits.

57. Method of diagnosis can be 'Autopsy' even when date of diagnosis is before date of death. This is possible since method of diagnosis is not linked to date of diagnosis. See corresponding definitions for more detail.

58. According to cancer staging manual, 6th edition, this value is not a valid stage group for the site.

59. Place holder to keep sub-edit numbering in accordance with the required processing order. See Data Item match edits introduction for more information.

60. Based on the underlying cause of death coding rules, these 2 codes cannot be used.

61. According to cancer staging manual, 6th edition, this value is not a valid stage group for the site. On the other hand, since AJCC TNM stage group is likely to be assigned by a physician rather than derived from any T, N and M values, this value must be accepted.

62. Lymphoma, leukemia or immunoproliferative disease is identified by the following ICD-0-3 codes: 9590-9989 excluding 9731, 9734, 9740, 9750, 9755-9758, 9930.

63. Alphabetic comparison as opposed to numeric comparison is used because TTRN and Health Insurance Number may contain letters.

Canadian Cancer Registry System Guide – 2009 Edition

Part II – Data Loading and Tabulation Master Files

Introduction
0.1 Canadian Cancer Registry Overview
0.2 CCR System Guide Document Organization
0.3 Part II Document Organization – Data Loading and TMF
0.4 Changes to the CCR Data Loading and TMF for the 2007 and 2008 Reference Years
0.5 Contacts in Statistics Canada

Chapter 3 – Data Loading
3.1 Introduction
3.2 Data Importing
3.3 Data Conditioning
3.4 Validation Edits
3.5 Correlation Edits
3.6 Match Edits
3.7 Data Posting

Chapter 4 – Tabulation Master Files
4.1 Description
4.2 Scope
4.3 Content and layout
4.4 Derived variable calculations
4.5 Confidentiality

Appendices
Appendix C – AJCC TNM reference tables
Appendix D – Multiple primary tumour rules for CCR
Appendix E – Interval and mean times between dates
Appendix F – Auxiliary tables
Appendix G – Guidelines for reporting grade, differentiation or cell indicator
Appendix H – CCR ambiguous Terms
Appendix I – Guidelines for abstracting and determining Death Certificate Only (DCO) Cases for Provincial/Territorial Cancer Registries (PTCRS) in Canada (for T12 and P18)
Appendix J – Interval between two dates (complete or partial)
Appendix T – Residency guidelines in Canada
Appendix X – CCR_ID Check digit routine
Appendix Z – Reference
Footnotes

Introduction

  • Canadian Cancer Registry Overview
  • CCR System Guide Document Organization
  • Part II Document organization – Data Loading and TMF
  • Changes to the CCR Data Loading and TMF for the 2007 and 2008 Reference Years
  • Statistics Canada Contacts

0.1 Canadian Cancer Registry Overview

The patient-oriented Canadian Cancer Registry (CCR) evolved from the event-oriented National Cancer Incidence Reporting System (NCIRS). Beginning with cases diagnosed in 1992, incidence figures collected by Provincial and Territorial Cancer Registries (PTCRs) have been reported to the CCR, which is maintained by Statistics Canada. Established as a person-oriented database, the CCR includes mechanisms for updating and clearing death records and is linked to provincial and territorial databases to help track patients across Canada who have been diagnosed with tumours.

0.2 CCR System Guide Document Organization

The CCR System Guide has been separated into three parts to improve access and navigation. Although the three parts are separate, the three documents should be used in conjunction with each other. The different sections of the three-part CCR System Guide often refer to each other. The CCR System Guide is now composed of:

Part I: CCR Data Dictionary provides explanation on the reporting of data, including the scope and detailed information on the input and derived variables.

Part II: CCR Data Loading and Tabulation Master Files provides information on the data loading process, including in-depth descriptions of the various edits performed on the data. Part II also provides information on the Tabulation Master Files, including the scope, content and layout. Part II is followed by several appendices that contain supporting information such as explicit code set tables, guidelines to assist coders and other supportive information.

Part III: CCR Core Reference Tables provides detailed information on the CCR Core Reference Tables such as descriptions of the tables, their usage and any revisions made. Part III is an accompanying document to the Core Reference Tables 2009.xls.

0.3 Part II Document organization – Data Loading and TMF

Chapter 3 – Data loading describes in great detail all the verification performed against reported data prior to their loading into the CCR System. Related business rules, Edit logic and feedback report messages are described for all edits. It also describes the data conditioning and the data posting phase.

Chapter 4 – Tabulation master file describes the main output of the system.

Appendices contain supporting information such as explicit code set tables, guidelines to assist coders, lists of changes from previous versions of the system, etc.

0.4 Changes to the CCR Data Loading and TMF for the 2007 and 2008 Reference Years

Please refer to the relevant section in the System Guide – Data Loading and TMF for more details related to these changes.

Changes to the CCR Data Loading and TMF for the 2007 and 2008 Reference Years
Section Item(s) Description of change Effective (reference year)
3.1.5 Step 2: Core data items validation New validation edits added, TVAL53-57 2008
3.1.5 Step 7: CS data items validation New validation edit TVAL52 added in to step 2007
3.1.7 CS fatal error CS data item T52 added 2007
3.1.7 CS error CS data item T52 added 2007
3.3.1 Data formatting – Table 22 Impact of data formatting step on tumour data items New variables added: T53, T54, T55, T56, T57 2008
New variable added – T52 2007
3.4 Validation Edits –
PVAL6
PVAL7
PVAL8
PVAL9
PVAL13
Business rules changed – acceptable accented characters specified 2007
3.4.2 Tumour validation edits – Table 25 New Tumour validation edits – TVAL53, TVAL54, TVAL55, TVAL56, TVAL57 2008
New Tumour validation edit – TVAL52 2007
3.4.2 Tumour validation edits –
TVAL6
Business rules changed – acceptable accented characters and special characters specified
Edit logic – New edit logic added
Feedback report messages – New messages added
2007
3.4.2 Tumour validation edits –TVAL8 Business rules, Edit logic and Feedback report messages added – SGC 2006 2006
3.4.2 Tumour validation edits –
TVAL9
Business rules, Edit logic and Feedback report messages added – Census tract effective date range ended in 2005. For 2006 onwards T9 must be blank 2006
3.4.2 Tumour validation edits –
TVAL27
TVAL28
TVAL29
TVAL30
TVAL31
TVAL32
TVAL33
TVAL34
TVAL35
TVAL36
TVAL37
TVAL38
TVAL39
TVAL40
TVAL41
Referenced fields, Business rules, Edit logic and Feedback report messages updated: now using recommended version of AJCC CS algorithm 2007
3.4.2 Tumour validation edits –
TVAL52
New validation edit added 2007
3.4.2 Tumour validation edits –
TVAL53
TVAL54
TVAL55
TVAL56
TVAL57
New validation edits added 2008
3.5.2 Tumour correlation edits – Table 27 New correlation edits – TCOR26, TCOR27 2008
3.5.2 Tumour correlation edits – Table 27 New correlation edits – TCOR13 2007
3.5.2 Tumour correlation edits – TCOR1 Referenced fields, Business rules, edit logic changed – new data items added T53, T54, T55, T56, T57 2008
Referenced fields, Business rules, edit logic changed – new data items added T52 2007
3.5.2 Tumour correlation edits – TCOR3 Business rules and Edit logic changed: includes combinations where census tract indicates area outside CMA 2006
3.5.2 Tumour correlation edits – TCOR10
TCOR11
Referenced fields, Business rules, Edit logic and Feedback report messages changed: Verification now includes Date of diagnosis. 2007
3.5.2 Tumour correlation edits – TCOR13 New correlation edit added 2007
3.5.2 Tumour correlation edits – TCOR18 Referenced fields and Edit logic updated: T52 added as a new CS variable 2007
3.5.2 Tumour correlation edits – TCOR26, TCOR27, TCOR29 – TCOR35 New correlation edits 2008
3.6.3 Data item match edits –
DIM6
Revision – Edit no longer used after 2006 2006
3.7.2 Add tumour record processing – CS data items Added new data item T52 2007
3.7.7 Patient derived variable calculation PD7 – Name of variable changed 2007
4.2 Table 24 – Scope - topography codes from ICD-O-2 and ICD-O-3 considered a single site in the definition of multiple cancers Topography group added: C38.4 2007
4.3 Table 36 TMF record layout Addition/deletion of variable – T52 CS version 1st added TD20 deleted 2007
PD7 – Variable acronym changed
New variables added – T53 to T57
2008
4.3 Table 37 – Derived variable calculations at TMF time PD2 – Vital status now derived at TMF time 2007
Appendices Appendices – Appendix A moved to Part III of system guide. Appendix A now included in Part III of system guide 2008
Additions to Appendices Appendix H now includes T53
Appendix I now includes P18
2008
Table 50 – updated table Updated stage group II with T1a, T1b and T1c 2008
New Appendices added to system guide New Appendices
Appendix G – Grade, differentiation or cell indicator guidelines
Appendix H - CCR Ambiguous Terms
Appendix I – Guidelines for abstracting and determining death certificate only (DCO) cases for PTCRs in Canada
2007
Appendix J – Interval between two dates (complete or partial) 2008
Appendices deleted from system guide Appendix Y - Removed and replaced with Section 0.4 Changes to the CCR Data Loading and TMF for the 2007 and 2008 reference years 2008
Appendix Z - References Updates to several references 2007
  • Additional updates have been made; however, only the changes that require action on the part of the PTCRs have been included in this table.
  • Note that changes effective in the 2006 reference year have also been included here.

0.5 Statistics Canada Contacts

PTCRs employees are encouraged to bring forward any questions by contacting one of the following:

For additional information regarding the processing of CCR data, please contact:

Colette Brassard
Section Chief
Operations and Integration Division
Statistics Canada
Tel: (613) 951-7282
Fax: (613) 951-0709
For any subject matter related questions/queries, please contact:

Kim Boyuk
Chief, Cancer Statistics
Health Statistics Division
Statistics Canada
Tel: (613) 951-2510
Fax: (613) 951-0792

Hollie Anderson
Manager, Canadian Cancer Registry
Health Statistics Division
Statistics Canada
Tel: (613) 951-0757
Fax: (613) 951-0792

Chapter 3 – Data loading

  • Data importing
  • Data conditioning
  • Data editing
  • Data posting

3.1 Introduction

The data loading process is done in 4 distinct phases:

1. Data importing: Reads in input patient and tumour record files and breaks them down into separate data items using the proper record layout.
2. Data conditioning: Formats the data, filters the old classification data, computes some missing input variables and adjusts the laterality code. This phase alters the reported data.
3. Data editing: Identifies errors in input records and provides sufficient feedback to correct them. This phase does not alter the data. The documentation about this phase has been divided into 3 sections:

  • Validations edits,
  • Correlation edits,
  • Match edits.

4. Data posting: Computes some derived variables, transfers valid data in the CCR database and generates additional reports.

Since the data editing is the most complex phase of the overall process, the remaining pages of the introduction present its key components. An overview of the overall data loading process is also presented at the end of the introduction.

3.1.1 Business rules

The main purpose of the edit process is to enforce a given number of rules on the CCR Data items. Some rules are related to the subject matter (subject matter rules) whereas some others are related to the transmission of data between the PTCR and Statistics Canada (transactional rules). The expression "Business rules" has been retained to express both subject matter and transactional rules that apply to the CCR System.

3.1.2 Edits and sub-edits

Each individual edit in the CCR system enforces a set of related business rules. For the purpose of reporting, an edit may be divided into sub-edits in order to provide more detailed feedback. Thus, each Sub-edit has its own logic and message.

3.1.3 Edit logic

Edit logic are logical expressions that can be evaluated to true or false. They are built from data item names, operators and functions. The principal language elements are described in the following tables.

Table 14 Logical operators
Operator Syntax and meaning
AND expr1 AND expr2
The expression is true if and only if both expr1 and expr2 are true, otherwise the expression is false.
OR expr1 OR expr2
The expression is true whenever expr1 or expr2 is true, otherwise the expression is false.
NOT NOT expr1
The expression is true only if it does not equal expr1, otherwise the expression is false.
Table 15 Comparison operators
Operator Syntax and meaning
<> Expr1 <> expr2
Assesses whether expr1 is different from expr2.
= Expr1 = expr2
Assesses whether expr1 is equal to expr2.
> Expr1 > expr2
Assesses whether expr1 is greater than expr2.
>= Expr1 >= expr2
Assesses whether expr1 is greater than or equal to expr2.
< Expr1 < expr2
Assesses whether expr1 is less than expr2.
<= Expr1 <= expr2
Assesses whether expr1 is less than or equal to expr2.
BETWEEN Expr1 BETWEEN (expr2, expr3)
Assesses whether expr1 is greater than or equal to expr2 and less than or equal to expr3.
LIKE Expr1 LIKE expr2
Assesses whether expr1 complies with expr2 pattern. Expr2 may contain Underscore (_) and percent (%) characters which stand respectively for any single character and any number (including 0) of characters.
Ex: ‘951-5555' LIKE ‘951-_ _ _ _' is true.
EX: ‘951-5555' LIKE ‘653-_ _ _ _' is false.
Table 16 Functions
Function Syntax and meaning
AVERAGE AVERAGE (X1, X2, ..., Xn)
Returns the arithmetic mean of X: X1+X2+...+Xn / n. This function ignores NULL values.
BLANK BLANK(x1)
Returns x1 blank character(s).
CALCULATE_CCR_CHECK_DIGIT CALCULATE_CCR_CHECK_DIGIT (str1)
Returns a CCR_ID check digit based on str1.
CONTAINS_WORD CONTAINS_WORD (str1, str2, x1)
Assesses whether str1 contains a word of at least x1 character(s) from str2.
IS_COMPOSED_OF IS_COMPOSED_OF (str1, str2)
Assesses whether str1 is only composed of characters from str2.
IS_VALID_DATE IS_VALID_DATE (str1)
Assesses whether str1 is a calendar date.
LENGTH LENGTH (str1)
Returns the length of str1 including trailing blanks.
UPPER UPPER (str1)
Returns str1 where letters and accented characters are converted to their uppercase equivalent. Special characters and numbers remain the same.
Table 17 String operator
Operator Syntax and meaning
|| str1 || str2
Returns a unique string containing str1 and str2 concatenated (juxtaposed).
Table 18 Set operators and symbols
Operator and symbol Syntax and meaning
[] [Expr1,...]
[A-Z]
[A]
Indicates an explicit list of values, a range of values or set of values known as Set A.
IN expr1 IN [A]
Assesses whether expr1 is included in Set A.

3.1.4 Edit families and groups

For ease of use, edits have been grouped into families and groups depending on the scope of the business rules they enforce. There are 3 families:

  1. Validation edits: Enforce business rules on each individual field.
  2. Correlation edits: Enforce business rules between valid fields on the same input record.
  3. Match edits: Enforce business rules between valid fields on different records.

The following table describes the scope of each edit group.

Table 19 Edit scope by family and group
Family Group Scope
Validation Patient validation (PVAL)  Enforce business rules on Patient fields.
Tumour validation (TVAL)  Enforce business rules on Tumour fields.
Correlation Patient correlation (PCOR)  Enforce business rules between valid Patient fields.
Tumour correlation (TCOR)  Enforcebusiness rules between valid Tumour fields.
Match Key input match (KIM) Ensure that Input patient and Tumour records respect the submission rules in terms of matching keys.
Hey base match (KBM) Ensure that Input patient and Tumour records respect the actual state of the CCR in terms of matching keys.
Data item match (DIM) Enforce the business rules between data items (other than keys) found on different records.
Pre–posting match (PPM) Identify error–free4 Input records that cannot be posted to CCR because some other related Input records are either missing or in error.

3.1.5 Edits order of execution and edit control

Because of the dependencies between the edits, edit processing must respect a given order of execution. Since CS and AJCC TNM data item edits depend on core data items, core data item edits must be done first. For each of the following steps, the number of eligible input records will depend on the outcome of preceding steps.

Step 1: Core data items minimum requirements assessment

The core data items minimum requirements consist of an Input record with a valid record type and date of transmission and no missing core data items (P1-P19 or T1-T26). The following edits must be successful in order to respect the minimum requirements:

  • Patient records: PCOR1, PVAL4 and PVAL19.
  • Tumour records: TCOR1, TVAL5 and TVAL26.

Step 2: Core data items validation

Remaining core data items validation edits (PVAL1-19, TVAL1-26 and TVAL53-57) can be performed on the Input records that respect the core data items minimum requirements. The following order must be respected:

  • PVAL11 before PVAL12;
  • PVAL14 before PVAL15 and PVAL17;
  • TVAL12 before TVAL8 and TVAL9;

Step 3: Core data items correlation, key input match and key base match edits

These edits are run based on the outcome of the core data item validation edits. That is, for a given edit, only the Input records where all referenced fields have been successfully validated are eligible. (This implies that Input records that do not respect the minimum requirements or that fail a required field validation edit are not eligible.) These edits can be run in any order.

Step 4: Core data item match edits

Those edits can only be performed on Input records that have no core data items errors. A special processing order must be respected. See Section 3.6.3 Data Item Match Edits for details.

Step 5: Core data items pre-posting match edits

Those edits can only be performed on Input records that have no core data items errors. These edits can be run in any order.

Step 6: CS data items minimum requirements assessment

CS data items minimum requirements consist of an input tumour record with valid date of diagnosis and no missing CS data items. The following edit must be successful in order to respect the minimum requirements:

Tumour records: TCOR18.

Step 7: CS data items validation

CS Validation edits (TVAL27 to 41 and TVAL52) can be performed on the input tumour records that respect the CS minimum requirements and where all core referenced fields are valid. These edits can be run in any order.

Step 8: AJCC TNM data items minimum requirements assessment

AJCC TNM data items minimum requirements consist of an input tumour record with valid date of diagnosis, ICD-O-2/3 topography, ICD-O-3 histology and ICD-O-3 behaviour and no missing AJCC TNM data items. The following edit must be successful in order to respect the minimum requirements SITE-SPECIFIC MEANING: Tumour records: TCOR19.

Step 9: AJCC TNM data items validation

AJCC TNM validation edits (TVAL42 to 51) can be performed on the input tumour records that respect the AJCC TNM minimum requirements and where all core referenced fields are valid. These edits can be run in any order.

Step 10: AJCC TNM data items correlation

These edits are run based on the outcome of previous validation edits. That is, for a given edit, only the Input records where all referenced fields (core and AJCC TNM) have been successfully validated are eligible. These edits can be run in any order.

See section 3.1.9 flowchart of the data loading process for an illustration of the edits dependencies.

3.1.6 Sub-edits order of execution

Except for data item match Sub-edits; all sub-edits from a given edit may be performed in any order. See Section 3.6.3.1 Special order of execution for more details about data item match Sub-edits special order of execution.

3.1.7 Message types

The severity of an error is expressed by its corresponding message's type. The following list describes each possible message type and gives an indication of when they are issued and how they change the editing process flow.

Fatal error: When a group of data items does not respect the minimum requirements. Related editing is stopped.

Core fatal error: Core data items (P1 to P19 and T1 to T26) do not respect the minimum requirements. The input record will not undergo any other edits and will be rejected.

CS fatal error: CS data items (T27 to T41 and T52) do not respect the minimum requirements. CS data items will not undergo any other related edits and will not be loaded on the CCR database. CS Fatal error does not prevent valid core and AJCC TNM data items from being loaded on the CCR database.1

AJCC TNM Fatal error: AJCC TNM data items (T42 to T51) do not respect the minimum requirements. AJCC TNM data items will not undergo any other related edits and will not be loaded on the CCR database. AJCC TNM fatal error does not prevent valid core and CS data items from being loaded on the CCR database.5

Error: Normal edits failure. Editing is not stopped. Unless specified otherwise, the input record can be edited by other edits based on the validity of their corresponding referenced fields.

Core error: Error found in core patient (P1 to P19) or Tumour (T1 to T26) data items. Core error causes the Input record to be rejected.

CS error: Error found in CS data items (T27 to T41 and T52). CS data items will not be loaded on the CCR database.CS error does not prevent valid core and AJCC TNM data items from being loaded on the CCR database.5

AJCC TNM error: Error found in AJCC TNM data items (T42 to T51). AJCC TNM data items will not be loaded on the CCR database. AJCC TNM error does not prevent valid core and CS data items from being loaded on the CCR database.5

Warning: Informative message to PTCR. Warnings do not prevent Inputrecords from being loaded on the CCR.

3.1.8 Edit description pages

For ease of use, each edit is described using a standard format: name, purpose, referenced fields, business rules, edit logic and feedback report messages. When needed, other parameters, revisions and notes are also added to give more detail. The following table describes each possible section.

Table 20 Edit presentation breakdown
Section Description
Name A unique name for the edit.
Purpose Edit main purpose.
Referenced fields List of all input file fields (or part of fields) involved in the edit.
Other parameters List of additional parameters needed to perform the edit.
Business rules Rules that describe the eligible field value or relationship between many field values. These rules are written in plain English.
Edit logic Each Sub-edit condition that identifies invalid records. These conditions are usually written using logical expressions.
Feedback report messages List of all possible edit messages.
Revision List of all changes that have been applied to the edit over time.
Notes Any remarks.

3.1.9 Flowchart of the data loading process

3.1.9 Flowchart of the data loading process

Notes:
*See 3.1.5 Edits Order of Execution and Edit Control for exact sequencing.
**DIM Edits have a special processing order. See specific section for more details.

3.2 Data importing

During the data importing phase, the input patient record file and/or input tumour record file is read in by the system. Every record is then cut into separate data items using the proper record layout.

3.2 Data Importing

3.3 Data conditioning

The purpose of the data conditioning phase is threefold. Its intent is to:

  • Reduce PTCR response burden by automatically correcting small errors such as the use of lowercase characters in code fields or improper alignment of values.
  • Eliminate older classification data (ICD-9 and ICD-O-2) when not reported as the source classification data. This eliminates the risk of incoherence between the source classification and any former classification data.
  • Bring all reported data up to a uniform classification (ICD-O-3). This facilitates a comparison of all tumours reported to the CCR.

To achieve these objectives, the following steps are performed on the data:

  1. Data formatting;
  2. Old classification filtering;
  3. ICD-O-2/3 topography calculation;
  4. ICD-O-3 histology and behaviour calculation; and,
  5. Laterality adjustment.

The steps listed above must be executed in sequential order. Each step may alter the reported data. Refer to the corresponding section below for a description of how these reported data are altered.

3.3.1 Data formatting

Description

Data formatting is composed of three operations:

Left justified: Removes blank character preceding the data item value.

Uppercase: Converts all lower case alphabetic characters to uppercase letters.
Converts lower case French accents (é, è, ê, ë, ç…) to corresponding uppercase letters (é à É). Special characters and digits remain unchanged.

Removal of trailing blanks: Removes any blank characters trailing the data item value. Data items containing only blank characters will be converted to NULL. This is an important assumption used in the data editing phase.

Purpose

Data formatting reduces PTCR response burden by fixing small formatting errors that would otherwise cause an input record to be rejected. It also converts blank data items to NULL values in order to be compliant with the data editing specification.

Logic

  • Left justification is applied on any fields longer than 1 character.
  • Uppercase is applied on any fields that may contain letters.
  • Removal of trailing blanks is applied on all fields.

The following two tables summarize the impact of the data formatting step on patient and tumour data items. X and – indicate whether the corresponding transformation is applicable or not.

Table 21 Impact of data formatting step on patient data items
Variable Name Variable Left justify Uppercase Removal of trailing blanks
P1 Patient reporting province/territory X - X
P2 Patient identification number X X X
P3 CCR identification number X - X
P4 Patient record type - - X
P5 Type of current surname - - X
P6 Current surname X X X
P7 First given name X X X
P8 Second given name X X X
P9 Third given name X X X
P10 Sex - - X
P11 Date of birth X - X
P12 Province/territory or country of birth X - X
P13 Birth surname X X X
P14 Date of death X - X
P15 Province/territory or country of death X - X
P16 Death registration number X - X
P17 Underlying cause of death X X X
P18 Autopsy confirming cause of death - - X
P19 Patient date of transmission X - X
Table 22 Impact of data formatting step on tumour data items
Variable Name Variable Left justify Uppercase Remove trailing blank
T1 Tumour reporting province/territory X - X
T2 Tumour patient identification number X X X
T3 Tumour reference number X X X
T4 CCR identification number X - X
T5 Tumour record type - - X
T6 Name of place of residence X X X
T7 Postal code X X X
T8 Standard geographic code X - X
T9 Census tract X - X
T10 Health insurance number X X X
T11 Method of diagnosis - - X
T12 Date of diagnosis X - X
T13 ICD–9 cancer code X - X
T14 Source classification flag - - X
T15 ICD–O–2/3 Topography X X X
T16 ICD–O–2 Histology X - X
T17 ICD–O–2 Behaviour X - X
T18 Filler - - -
T19 Laterality - - X
T20 Filler - - -
T21 ICD–O–3 Histology X - X
T22 ICD–O–3 Behaviour - - X
T23 Grade, differentiation or cell indicator - - X
T24 Method used to establish the date of diagnosis - - X
T25 Diagnostic confirmation - - X
T26 Date of transmission X - X
T27 CS tumour size X - X
T28 CS extension X - X
T29 CS tumour size/ext eval - - X
T30 CS lymph nodes X - X
T31 CS reg nodes eval - - X
T32 Regional nodes examined X - X
T33 Regional nodes positive X - X
T34 CS mets at dx X - X
T35 CS mets eval - - X
T36 CS site-specific factor 1 X - X
T37 CS site-specific factor 2 X - X
T38 CS site-specific factor 3 X - X
T39 CS site-specific factor 4 X - X
T40 CS site-specific factor 5 X - X
T41 CS site-specific factor 6 X - X
T42 AJCC clinical T X X X
T43 AJCC clinical N X X X
T44 AJCC clinical M X X X
T45 AJCC pathologic T X X X
T46 AJCC pathologic N X X X
T47 AJCC pathologic M X X X
T48 AJCC clinical TNM stage group X X X
T49 AJCC pathologic TNM stage group X X X
T50 AJCC TNM stage group X X X
T51 AJCC TNM edition number X - X
T52 CS Version 1st X - X
T53 Ambiguous Terminology Diagnosis - - X
T54 Date of Conclusive Diagnosis X - X
T55 Type of Multiple Tumours Reported as One Primary X - X
T56 Date of Multiple Tumours X - X
T57 Multiplicity Counter X - X

Revision

Year Description
2008 Tumour input variables T53 to T57 have been added to the record layout. Different formatting processes are done to each new variable.
2007 T52 – CS Version 1st – tumour input variable added to record layout. It is left justified and trailing blanks are removed.
2004 In order to reduce response burden, some data items will automatically be uppercased, left justified and right truncated (removal of trailing blanks) by the CCR system.
T3 – Tumour reference number: Values will not be zero left filled anymore.

3.3.2 Old classification filtering

Description

This step deletes disease classification information reported by PTCRs older than that indicated by the source classification flag.

Purpose

This step eliminates the possibility of incoherence between source classification data (as identified by the source classification flag) and any former classification data.

Logic

  • If the Source classification flag indicates that ICD-9 is the source classification, then all reported data are kept as is.
  • If the Source classification flag indicates that ICD-O-2 is the source classification, then reported ICD-9 Cancer Code is replaced by '0000'.
  • If the Source classification flag indicates that ICD-O-3 is the source classification, then reported ICD-9 Cancer Code and ICD-O-2 Histology are replaced by '0000' and reported ICD-O-2 Behaviour is replaced by '0'.
  • In any other case, all reported data are kept as is.

This step will not create a feedback message. The following examples and table illustrate possible scenarios.

Example 1: If source classification flag indicates ICD-9, then no change.
Example 2: If source classification flag indicates ICD-O-2, then ICD-9 is not loaded.
Example 3: If source classification flag indicates ICD-O-3, then ICD-9 and ICD-O-2H/B are not loaded. ICD-O-2/3T is kept since it also belongs to ICD-O-3.

Table 23 Old classification filtering
Example TSCF ICD-9 ICD-O-2/3T ICD-O-2H ICD-O-2B ICD-O-3H ICD-O-3B
1 Before 1 175 C509 8521 3 8521 3
After 1 175 C509 8521 3 8521 3
2 Before 2 175 C509 8521 3 8521 3
After 2 0000 C509 8521 3 8521 3
3 Before 4 175 C509 8521 3 8521  
After 4 0000 C509 0000 0 8521 3

3.3.3 ICD-O-2/3 Topography calculation

Background

For cases diagnosed from 1992 to 2000, the Canadian Council of Cancer Registries adopted the International Classification of Diseases for Oncology, Second Edition (ICD-O-2) as the standard for reporting diagnostic information to the Canadian Cancer Registry (CCR). This classification was chosen because it provides detailed information on the site (topography), the histology and the behaviour of the neoplasm. The site codes are based on the malignant neoplasms section (C00-C80) of the International Statistical Classification of Diseases and Related Health Problems, Tenth revision (ICD-10). The morphology codes are revised and expanded from its predecessor, the ICD-O-1. The International Classification of Diseases is a classification system which covers the broad range of diseases and other health problems for which health care services may be rendered. The ICD has been in use in Canada for many decades for morbidity (hospitalization) and mortality (death) reporting. The Ninth revision (ICD-9), in use since 1979, has been replaced by the ICD-10 for morbidity and mortality. Chapter 2 of the ICD-9 (Neoplasms) provides a classification of tumours, primarily by site and includes behaviour. The ICD-O-2 supplements site information with tumour morphology detail. This greater level of specificity makes ICD-O more suitable for cancer registration purposes.

By 1992, the data year for which the CCR became operational, all provincial/territorial cancer registries except Ontario and Québec had implemented the ICD-O-2 for reporting tumour site and morphology. Ontario and Québec had adopted the ICD-O-2 for reporting tumour morphology information, but continued to report the site of tumours using the ICD-9, for administrative reasons. In order to bring all data to a common basis, the ICD-9 to ICD-O-2 conversion was created, cooperatively by Statistics Canada, the Ontario Cancer Treatment and Research Foundation and the Fichier des tumeurs du Québec.

Description

This step computes ICD-O-2/3 Topography code from the reported ICD-9 Cancer code when needed.

Purpose

This step ensures that, for each reported tumour, the site is described using the ICD-O-3 classification. This facilitates the comparison between all tumours reported to the CCR.

Logic

If ICD-O-2/3 Topography = '0000' and Source classification flag = '1' then
If ICD-9 Cancer code is found in ICD-9 to ICD-O-2 conversion table6 then
ICD-O-2/3 Topography = ICD-O-2/3 Topography code associated to ICD-9 Cancer code in ICD-9 to ICD-O-2 conversion table.
Else (ICD-9 Cancer code is NULL or NOT found in ICD-9 to ICD-O-2 conversion table)
Warning saying "ICD-O-2/3 Topography calculation: Conversion failed." is sent to the reporting PTCR.
End If
End If

Directions

The process of converting coded information from one disease classification system to another can result in a distortion or loss of original diagnostic detail. Whenever possible, it is recommended that the original descriptive diagnosis be coded directly, using the preferred, most recent classification system.

Registries using both the ICD-O-2/3 topography and the ICD-9 to code tumour sites are requested to report only ICD-O-2/3 topography codes to the CCR. ICD-9 codes should only be reported to the CCR if ICD-O-2/3 topography codes are not available.

3.3.4 ICD-O-3 Histology and behaviour calculation

Background

For cases diagnosed from 2001 onwards, the Canadian Council of Cancer Registries adopted the International Classification of Diseases for Oncology, Third edition (ICD-O-3) as the standard for reporting diagnostic information to the Canadian Cancer Registry (CCR). The topography section of the Third edition remains the same as the Second edition; however it includes revised morphologies and new classifications especially for lymphomas and leukemias. This classification was adopted because it represents the most current classification of diseases for oncology.

Description

This step computes the ICD-O-3 Histology and the ICD-O-3 behaviour from reported ICD-O-2 histology and ICD-O-2 behaviour when needed.

Purpose

This step ensures that, for each reported tumour, the histology and behaviour are described using the ICD-O-3 classification. This facilitates the comparison between all tumours reported to the CCR.

If ICD-O-3 Histology = '0000' and ICD-O-3 Behaviour = '0' and Source Classification Flag = '1' or '2' 'then
If ICD-O-2/3 Topography, ICD-O-2 Histology and ICD-O-2 Behaviour combination is found in ICD-O-2 to ICD-O-3 conversion table6 then
ICD-O-3 Histology = ICD-O-3 Histology code associated to ICD-O-2/3 Topography, ICD-O-2 Histology and ICD-O-2 Behaviour combination in ICD-O-2 to ICD-O-3 conversion table
ICD-O-3 Behaviour = ICD-O-3 Behaviour code associated to ICD-O-2/3 Topography, ICD-O-2 Histology and ICD-O-2 Behaviour combination in ICD-O-2 to ICD-O-3 conversion table
If the Review Flag associated to ICD-O-2/3 Topography, ICD-O-2 Histology and ICD-O-2 Behaviour combination in ICD-O-2 to ICD-O-3 conversion table = '1' then
Warning saying "ICD-O-3 Histology and Behaviour calculation: Values must be manually reviewed." is sent to the reporting PTCR.
Else (ICD-O-2/3 Topography is NULL or ICD-O-2 Histology is NULL or ICD-O-2 Behaviour is NULL or the combination is NOT found in ICD-O-2 to ICD-O-3 conversion table)
Warning saying "ICD-O-3 Histology and Behaviour calculation: Conversion failed." is sent to the reporting PTCR.
End If
End If

This step ensures that, for each reported tumour, the histology and behaviour are described using the ICD-O-3 classification. This facilitates the comparison between all tumours reported to the CCR

3.3.5 Laterality adjustment

Background

Although the ICD-9 and the ICD-O-3 may be used for similar purposes, they are not totally compatible. Since the ICD-9 and the ICD-O-3 use different topographic groupings, there are cases where the laterality code may be coherent with a given ICD-9 Cancer code but may be incoherent with the closest corresponding ICD-O-2/3 topography code. Thus, for these exceptional cases, the laterality code must be altered to be compliant with the ICD-O-3 classification.

Description

This step alters the laterality code when specific ICD-9 Cancer codes are reported as source classification data and corresponding ICD-O-2/3 topography codes conflict with the reported laterality code due to classification incompatibility.

Purpose

This step reduces PTCR response burden by fixing classification incompatibility issues that would otherwise cause an input record to be rejected.

Logic

If Source Classification Flag = '1' and ICD-9 Cancer Code in ['1460','2021','2022','2382'] and Laterality = '0' then
Laterality = '9'
Warning saying "Laterality Adjustment: Laterality code has been changed from '0' to '9' in order to be compliant with ICD-O-3 classification." is sent to the reporting PTCR.
End if

3.4 Validation Edits

The purpose of the Validation edits is to enforce the business rules on each individual field. For ease of use, validation edits have been divided into two groups:

  • Patient validation edits: enforce business rules on patient fields;
  • Tumour validation edits: enforce business rules on tumour fields.

3.4.1 Patient validation edits

The following table summarizes the purpose of each individual edit of this category.

Table 24 Patient validation edits summary
Edit name Purpose
PVAL1 Validates the Patient reporting province/territory code.
PVAL2 Validates the Patient identification number.
PVAL3 Validates the CCR identification number.
PVAL4 Validates the Patient record type code.
PVAL5 Validates the Type of current surname code.
PVAL6 Validates the Current surname.
PVAL7 Validates the First given name.
PVAL8 Validates the Second given name.
PVAL9 Validates the Third given name.
PVAL10 Validates the Sex code.
PVAL11 Validates the Date of birth.
PVAL12 Validates the Province/territory or country of birth code.
PVAL13 Validates Birth surname.
PVAL14 Validates Date of death.
PVAL15 Validates the Province/territory or country of death code.
PVAL16 Validates Death registration number.
PVAL17 Validates the Underlying cause of death code.
PVAL18 Validates Autopsy confirming cause of death code.
PVAL19 Validates Patient record date of transmission.

PVAL1

This edit validates the patient reporting province/territory code.

Referenced fields (PVAL1)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
Other parameters (PVAL1)
Parameters Length Description
PTCR_CODE 2 Province/territory code of the PTCR that is submitting the data.

Business rules

For Input patient records
  • Patient reporting province/territory must be equal to province/territory code of the PTCR submitting the data7.
Edit logic (PVAL1)
Sub–edit Conditions Outcome
PVAL1-1 P1 <> PTCR_CODE Record rejected
Feedback report messages (PVAL1)
Sub–edit Text Type
PVAL1-1 Patient reporting province/territory code does not match PTCR province/territory code. Core error
Revision (PVAL1)
Year Description
Not applicable Not applicable

PVAL2

Purpose

This edit validates the patient identification number.

Referenced fields (PVAL2)
Field Length Description Acronym
P2 12 Patient identification number PPIN

Business rules

On any type of Input patient record, Patient identification number
  • Must be exclusively composed of any of the following:
    • Uppercase letters: A to Z
    • Numbers: 0 to 9
  • Cannot be exclusively composed of zeros.
Edit logic (PVAL2)
Sub–edit Conditions Outcome
PVAL2-1 IS_COMPOSED_OF (P2, ‘0') Record rejected
PVAL2-2 NOT IS_COMPOSED_OF (P2, ‘ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789') Record rejected
Feedback report messages (PVAL2)
Sub–edit Text Type
PVAL2-1 Patient identification number cannot be exclusively composed of zeros. Core error
PVAL2-2 Patient identification number is not exclusively composed of uppercase letters and/or numbers. Core error
Revision (PVAL2)
Year Description
2004 Business rule changed: Apostrophes, hyphens, periods and inner spaces are not accepted anymore.

PVAL3

Purpose

This edit validates the CCR identification number.

Referenced fields (PVAL3)
Field Length Description Acronym
P3 9 CCR identification number CCR_ID
P3.ID 8 First 8 digits of P3 (CCR ID sequence number) Not applicable
P3.CHECK_DIGIT 1 9th digit of P3 (CCR ID check digit) Not applicable
P4 1 Patient record type PRECTYPE

Business rules

For Update and Delete Patient records, CCR identification number
  • Must be exclusively composed of numbers: 0 to 9
  • Must be 9 digits long.
  • Cannot be all zeros.
  • Must have a valid check digit8.
Edit logic (PVAL3)
Sub–edit Conditions Outcome
PVAL3-1 P4 IN [‘2', ‘3'] AND (LENGTH (P3) <> 9 OR NOT IS_COMPOSED_OF (P3, ‘0123456789')) Record rejected
PVAL3-2 P4 IN [‘2', ‘3'] AND P3 = ‘000000000' Record rejected
PVAL3-3 P4 IN [‘2', ‘3'] AND P3 <> ‘000000000' AND LENGTH (P3) = 9 AND IS_COMPOSED_OF (P3, ‘0123456789') AND P3.CHECK_DIGIT <> CALCULATE_CCR_CHECK_DIGIT (P3.ID) Record rejected
Feedback report messages (PVAL3)
Sub–edit Text Type
PVAL3-1 CCR identification number is not 9 digits long. Core error
PVAL3-2 CCR identification number cannot be all zeros. Core error
PVAL3-3 CCR identification number is invalid. Core error
Revision (PVAL3)
Year Description
Not applicable Not applicable

PVAL4

Purpose

This edit validates the patient record type code.

Referenced fields (PVAL4)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE

Business rules

For Input Patient records, Patient record type
  • Cannot be blank.
  • Must be one of the Eligible patient record type codes9.
Edit logic (PVAL4)
Sub–edit Conditions Outcome
PVAL4-1 P4 IS NULL OR P4 NOT IN [Eligible Patient record type codes] Record rejected
Feedback report messages(PVAL4)
Sub–edit Text Type
PVAL4-1 Patient record type code is missing or invalid. Core fatal error
Revision (PVAL4)
Year Description
Not applicable Not applicable

PVAL5

Purpose

This edit validates the type of current surname code.

Referenced fieldds (PVAL5)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P5 1 Type of current surname PTYP_CUR

Business rules

For Add and Update Patient records
  • Type of Current Surname must be one of the Eligible type of current surname codes10.
Edit logic (PVAL5)
Sub–edit Conditions Outcome
PVAL5-1 P4 IN [‘1', ‘2'] AND P5 NOT IN [Eligible type of current surname codes] Record rejected
Feedback report messages (PVAL5)
Sub–edit Text Type
PVAL5-1 Type of current surname code is invalid. Core error
Revision (PVAL5)
Year Description
Not applicable Not applicable

PVAL6

Purpose

This edit validates the current surname.

Referenced fields (PVAL6)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P6 25 Current surname PCURSNAM

Business rules

For Add and Update Patient records
  • Current surname can be blank.
  • If Current surname is not blank then
    • It must be exclusively composed of any of the following:
      • Letters: A to Z (upper or lowercase)
      • Accented characters: Â À Ç É Ê Ë È Î Ï Ô Û Ü (upper or lowercase)
      • Special characters: space ( ), period (.), apostrophe ('), hyphen (-)
    • It must contain at least one letter.
Edit logic (PVAL6)
Sub–edit Conditions Outcome
PVAL6-1 P4 IN [‘1', ‘2'] AND P6 IS NOT NULL AND NOT IS_COMPOSED_OF (UPPER (P6), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') Record rejected
PVAL6-2 P4 IN [‘1', ‘2'] AND P6 IS NOT NULL AND IS_COMPOSED_OF (UPPER (P6), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') AND NOT CONTAINS_WORD (UPPER (P6), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ', 1) Record rejected
Feedback report messages (PVAL6)
Sub–edit Text Type
PVAL6-1 Current surname is not exclusively composed of acceptable letters, accented characters or special characters. Core error
PVAL6-2 Current surname does not contain at least one letter. Core error
Revision (PVAL6)
Year Description
2007 Business rules changed: Acceptable accented characters are specified.
2004 Business rules changed: Titles are now allowed in current surname.

PVAL7

Purpose

This edit validates the first given name.

Referenced fields (PVAL7)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P7 15 First given name PGNAME_1

Business rules

For Add and Update Patient records
  • First given name can be blank.
  • If First given name is not blank then
    • It must be exclusively composed of any of the following:
      • Letters: A to Z (upper or lowercase)
      • Accented characters: Â À Ç É Ê Ë È Î Ï Ô Û Ü (upper or lowercase)
      • Special characters: space ( ), period (.), apostrophe ('), hyphen (-)
    • It must contain at least one letter.
Edit logic (PVAL7)
Sub–edit Conditions Outcome
PVAL7-1 P4 IN [‘1', ‘2'] AND P7 IS NOT NULL AND NOT IS_COMPOSED_OF (UPPER (P7), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') Record rejected
PVAL7-2 P4 IN [‘1', ‘2'] AND P7 IS NOT NULL AND IS_COMPOSED_OF (UPPER (P7), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') AND NOT CONTAINS_WORD (UPPER (P7), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ', 1) Record rejected
Feedback report messages (PVAL7)
Sub–edit Text Type
PVAL7-1 First given name is not exclusively composed of acceptable letters, accented characters or special characters. Core error
PVAL7-2 First given name does not contain at least one letter. Core error
Revision (PVAL7)
Year Description
2007 Business rules changed: Acceptable accented characters are specified.

PVAL8

Purpose

This edit validates the second given name.

Referenced fields (PVAL8)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P8 15 Second given name PGNAME_2

Business rules

For Add and Update Patient records
  • Second given name can be blank.
  • If Second given name is not blank then
    • It must be exclusively composed of any of the following:
      • Letters: A to Z (upper or lowercase)
      • Accented characters: Â À Ç É Ê Ë È Î Ï Ô Û Ü (upper or lowercase)
      • Special characters: space ( ), period (.), apostrophe ('), hyphen (-)
    • It must contain at least one letter
Edit logic(PVAL8)
Sub–edit Conditions Outcome
PVAL8-1 P4 IN [‘1', ‘2'] AND P8 IS NOT NULL AND NOT IS_COMPOSED_OF (UPPER (P8), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') Record rejected
PVAL8-2 P4 IN [‘1', ‘2'] AND P8 IS NOT NULL AND IS_COMPOSED_OF (UPPER (P8), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') AND NOT CONTAINS_WORD (UPPER (P8), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ', 1) Record rejected
Feedback report messages (PVAL8)
Sub–edit Text Type
PVAL8-1 Second given name is not exclusively composed of acceptable letters, accented characters or special characters. Core error
PVAL8-2 Second given name does not contain at least one letter. Core error
Revision (PVAL8)
Year Description
2007 Business rules changed: Acceptable accented characters are specified.

PVAL9

Purpose

This edit validates the third given name.

Referenced fields (PVAL9)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P9 7 Third given name PGNAME_3

Business rules

For Add and Update Patient records
  • Third given name can be blank.
  • If Third given name is not blank then
    • It must be exclusively composed of any of the following:
      • Letters: A to Z (upper or lowercase)
      • Accented characters: Â À Ç É Ê Ë È Î Ï Ô Û Ü (upper or lowercase)
      • Special characters: space ( ), period (.), apostrophe ('), hyphen (-)
    • It must contain at least one letter.
Edit logic (PVAL9)
Sub–edit Conditions Outcome
PVAL9-1 P4 IN [‘1', ‘2'] AND P9 IS NOT NULL AND NOT IS_COMPOSED_OF (UPPER (P9), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') Record rejected
PVAL9-2 P4 IN [‘1', ‘2'] AND P9 IS NOT NULL AND IS_COMPOSED_OF (UPPER (P9), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') AND NOT CONTAINS_WORD (UPPER (P9), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ', 1) Record rejected
Feedback report messages (PVAL9)
Sub edit Text Type
PVAL9-1 Third given name is not exclusively composed of acceptable letters, accented characters or special characters. Core error
PVAL9-2 Third given name does not contain at least one letter. Core error
Revision (PVAL9)
Year Description
2007 Business rules changed: Acceptable accented characters are specified.

PVAL10

Purpose

This edit validates the sex code.

Referenced fields (PVAL10)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P10 1 Sex PSEX

Business rules

For Add and Update Patient records
  • Sex must be one of the Eligible sex codes11.
Edit logic (PVAL10)
Sub–edit Conditions Outcome
PVAL10-1 P4 IN [‘1', ‘2'] AND P10 NOT IN [Eligible sex codes] Record rejected
Feedback report messages (PVAL10)
Sub–edit Text Type
PVAL10-1 Sex code is invalid. Core error
Revision (PVAL10)
Year Description
Not applicable Not applicable

PVAL11

Purpose

This edit validates the date of birth.

Referenced fields (PVAL11)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P11 8 Date of birth PDATBIR
P11.YEAR 4 First 4 digits of P11 (year of date of birth) Not applicable
P11.MONTH 2 5th and 6th digits of P11 (month of date of birth) Not applicable
P11.DAY 2 7th and 8th digits of P11 (day of date of birth) Not applicable
Other parameters (PVAL11)
Parameters Length Description
CYCLE_YEAR 2 Reference year

Business rules

For Add and Update Patient records, Date of birth
  • Must be 8 digits long.
  • Must be between January 1st, 1875 and December 31st of Reference year inclusively.
  • If Year is unknown then Month must be unknown.
  • If Month is unknown then Day must be unknown.
  • If Year, Month and Day are known then it must be a valid calendar date.
  • If Year and Month are known and Day is unknown then month must be a valid month.
Edit logic (PVAL11)
Sub–edit Conditions Outcome
PVAL11-1 P4 IN [‘1', ‘2'] AND (LENGTH (P11) <> 8 OR NOT IS_COMPOSED_OF (P11, ‘0123456789')) Record rejected
PVAL11-2 P4 IN [‘1', ‘2'] AND LENGTH (P11) = 8 AND IS_COMPOSED_OF (P11, ‘0123456789') AND ((P11.YEAR = ‘9999' AND P11.MONTH <> ‘99') OR (P11.MONTH = ‘99' AND P11.DAY <> ‘99')) Record rejected
PVAL11-3 P4 IN [‘1', ‘2'] AND LENGTH (P11) = 8 AND IS_COMPOSED_OF (P11, ‘0123456789') AND P11.YEAR <> ‘9999' AND (P11.YEAR < 1875 OR P11.YEAR > CYCLE_YEAR) Record rejected
PVAL11-4 P4 IN [‘1', ‘2'] AND LENGTH (P11) = 8 AND IS_COMPOSED_OF (P11, ‘0123456789') AND P11.YEAR <> ‘9999' AND P11.MONTH <> ‘99' AND P11.DAY <> ‘99' AND IS_VALID_DATE (P11) Record rejected
PVAL11-5 P4 IN [‘1', ‘2'] AND LENGTH (P11) = 8 AND IS_COMPOSED_OF (P11, ‘0123456789') AND P11.YEAR <> ‘9999' AND P11.MONTH NOT IN [‘01'-'12', ‘99'] AND P11.DAY = ‘99' Record rejected
Feedback report messages (PVAL11)
Sub–edit Text Type
PVAL11-1 Date of birth is not 8 digits long. Core error
PVAL11-2 Date of birth: Improper use of the ‘Unknown' code. Core error
PVAL11-3 Date of birth must be between the year 1875 and the current reference year inclusively. Core error
PVAL11-4 Date of birth is not a valid calendar date. Core error
PVAL11-5 Date of birth is not a valid partial date: month is invalid. Core error
Revision (PVAL11)
Year Description
Not applicable Not applicable

PVAL12

Purpose

This edit validates the province/territory or country of birth code.

Referenced fields (PVAL12)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P11.YEAR 4 First 4 characters of P11 (year of date of birth) Not applicable
P12 3 Province/territory or country of birth PPROVBIR

Business rules

For Add and Update Patient records
  • If Date of birth is before 1996 then Province/territory or country of birth must be one of the Eligible Province/territory and country codes prior to 199612.
  • If Date of birth is on or after 1996 then Province/territory or country of birth must be one of the Eligible Province/territory and country codes in and after 199612
  • If Date of birth is unknown then Province/territory or country of birth must be either one of the Eligible Province/territory and country codes prior to 199612 or Eligible Province/territory and country codes in and after 199612.
Edit logic (PVAL12)
Sub–edit Conditions Outcome
PVAL12-1 P4 IN [‘1', ‘2'] AND P11.YEAR <> ‘9999' AND P11.YEAR < 1996 AND P12 NOT IN [Eligible Province/territory and country code prior to 1996] Record rejected
PVAL12-2 P4 IN [‘1', ‘2'] AND P11.YEAR <> ‘9999' AND P11.YEAR >= 1996 AND P12 NOT IN [Eligible Province/territory and country code in and after 1996] Record rejected
PVAL12-3 P4 IN [‘1', ‘2'] AND P11.YEAR = ‘9999' AND P12 NOT IN [Eligible Province/territory and country code prior to 1996] AND P12 NOT IN [Eligible Province/territory and country code in and after 1996] Record rejected
Feedback report messages (PVAL12)
Sub–edit Text Type
PVAL12-1 Province/territory or country of birth code is invalid for Date of birth prior to 1996. Core error
PVAL12-2 Province/territory or country of birth code is invalid for Date of birth in and after 1996. Core error
PVAL12-3 Province/territory or country of birth code is invalid. Core error
Revision PVAL12)
Year Description
2004 Business rules changed: Province/territory or country of birth code is now validated against Province/territory or country codes valid at time of birth.

PVAL13

Purpose

This edit validates birth surname.

Referenced fields (PVAL13)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P13 25 Birth surname PBIRNAM

Business rules

For Add and Update Patient records
  • Birth surname can be blank.
  • If Birth surname is not blank then
    • It must be exclusively composed of any of the following:
      • Letters: A to Z (upper or lowercase)
      • Accented characters: Â À Ç É Ê Ë È Î Ï Ô Û Ü (upper or lowercase)
      • Special characters: space ( ), period (.), apostrophe ('), hyphen (-)
    • It must contain at least one letter.
Edit logic (PVAL13)
Sub–edit Conditions Outcome
PVAL13-1 P4 IN [‘1', ‘2'] AND P13 IS NOT NULL AND NOT IS_COMPOSED_OF (UPPER (P13), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') Record rejected
PVAL13-2 P4 IN [‘1', ‘2'] AND P13 IS NOT NULL AND IS_COMPOSED_OF (UPPER (P13), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') AND NOT CONTAINS_WORD (UPPER (P13), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ', 1) Record rejected
Feedback report messages (PVAL13)
Sub edit Text Type
PVAL13-1 Birth surname is not exclusively composed of acceptable letters, accented characters or special characters. Core error
PVAL13-2 Birth surname does not contain at least one letter. Core error
Revision Feedback report messages (PVAL13)
Year Description
2007 Business rules changed: Acceptable accented characters are specified.

PVAL14

Purpose

This edit validates date of death.

Referenced fields (PVAL14)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P14 8 Date of death PDATDEA
P14.YEAR 4 First 4 digits of P14 (year of date of death) Not applicable
P14.MONTH 2 5th and 6th digits of P14 (month of date of death) Not applicable
P14.DAY 2 7th and 8th digits of P14 (day of date of death) Not applicable
P19.YEAR 4 First 4 digits of P19 (year of date of transmission) Not applicable
P19.MONTH 2 5th and 6th digits of P19 (Month of date of transmission) Not applicable
P19.DAY 2 7th and 8th digits of P19 (Day of date of transmission) Not applicable

Business rules

For Add and Update Patient records, Date of death
  • Must be 8 digits long.
  • Can be all zeros (when patient is not known to have died).
  • Must be between January 1st, 1992 and Date of transmission inclusively.
  • If Year is unknown then Month must be unknown.
  • If Month is unknown then Day must be unknown.
  • If Year, Month and Day are known then it must be a valid calendar date.
  • If Year and Month are known and Day is unknown then Month must be a valid month.
Edit logic (PVAL14)
Sub–edit Conditions Outcome
PVAL14-1 P4 IN [‘1', ‘2'] AND (LENGTH (P14) <> 8 OR NOT IS_COMPOSED_OF (P14, ‘0123456789')) Record rejected
PVAL14-2 P4 IN [‘1', ‘2'] AND (P14.YEAR = ‘0000' OR P14.MONTH = ‘00' OR P14.DAY = ‘00') AND NOT (P14.YEAR = ‘0000' AND P14.MONTH = ‘00' AND P14.DAY = ‘00') Record rejected
PVAL14-3 P4 IN [‘1', ‘2'] AND LENGTH (P14) = 8 AND IS_COMPOSED_OF (P14, ‘0123456789') AND P14.YEAR NOT IN [‘0000', ‘9999'] AND ((P14.MONTH = ‘99' AND P14.DAY = ‘99' AND (P14.YEAR < 1992 OR P14.YEAR > P19.YEAR)) OR (P14.MONTH IN [‘01'-'12'] AND P14.DAY = ‘99' AND (P14.YEAR < 1992 OR P14.YEAR||P14.MONTH > P19.YEAR||P19.MONTH)) OR (P14.MONTH IN [‘01'-'12'] AND P14.DAY IN [‘01', ‘31'] AND IS_VALID_DATE (P14) AND (P14.YEAR < 1992 OR P14 > P19)) Record rejected
PVAL14-4 P4 IN [‘1', ‘2'] AND LENGTH (P14) = 8 AND IS_COMPOSED_OF (P14, ‘0123456789') AND ((P14.YEAR = ‘9999' AND P14.MONTH <> ‘99') or (P14.MONTH = ‘99' AND P14.DAY <> ‘99')) Record rejected
PVAL14-5 P4 IN [‘1', ‘2'] AND LENGTH (P14) = 8 AND IS_COMPOSED_OF (P14, ‘0123456789') AND P14.YEAR NOT IN [‘0000', ‘9999'] AND P14.MONTH NOT IN [‘00', ‘99'] AND P14.DAY NOT IN [‘00', ‘99'] AND NOT IS_VALID_DATE (P14) Record rejected
PVAL14-6 P4 IN [‘1', ‘2'] AND LENGTH (P14) = 8 AND IS_COMPOSED_OF (P14, ‘0123456789') AND P14.YEAR NOT IN [‘0000', ‘9999'] AND P14.MONTH NOT IN [‘00', ‘01'-'12', ‘99'] AND P14.DAY = ‘99' Record rejected
Feedback report messages (PVAL14)
Sub–edit Text Type
PVAL14-1 Date of death is not 8 digits long. Core error
PVAL14-2 Date of death: Improper use of ‘Patient is not known to have died' code. Core error
PVAL14-3 Date of death must be between January 1st, 1992 and the Date of Transmission inclusively. Core error
PVAL14-4 Date of death: Improper use of ‘Unknown' code. Core error
PVAL14-5 Date of death is not a valid calendar date. Core error
PVAL14-6 Date of death is not a valid partial date: month is invalid. Core error
Revision (PVAL14)
Year Description
2004 Business rules changed: Date of death cannot be beyond Date of transmission.

PVAL15

Purpose

This edit validates the province/territory or country of death code.

Referenced fields (PVAL15)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P14.YEAR 4 First 4 characters of P14 (year of date of death) Not applicable
P15 3 Province/territory or country of death PPROVDEA

Business rules

For Add and Update Patient records
  • If Date of death is before 1996 then Province/territory or country of death must be one of the Eligible province/territory and country codes prior to 199612.
  • If Date of death is on or after 1996 then Province/territory or country of death must be one of the Eligible province/territory and country codes in and after 199612.
  • If Date of death is unknown then Province/territory or country of death must be either one of the Eligible province/territory and country codes prior to 199612 or Eligible province/territory and country codes in and after 199612.
Edit Logic (PVAL15)
Sub–edit Conditions Outcome
PVAL15-1 P4 IN [‘1', ‘2'] AND P14.YEAR NOT IN [‘0000', ‘9999'] AND P14.YEAR < 1996 AND P15 NOT IN [Eligible province/territory or country codes prior to 1996] Record rejected
PVAL15-2 P4 IN [‘1', ‘2'] AND P14.YEAR NOT IN [‘0000', ‘9999'] AND P14.YEAR >= 1996 AND P15 NOT IN [Eligible province/territory or country codes in and after 1996] Record rejected
PVAL15-3 P4 IN [‘1', ‘2'] AND P14.YEAR = ‘9999' AND P15 NOT IN [Eligible Province/Territory or Country of Death codes in and after 1996] AND P15 NOT IN [Eligible province/territory or country codes prior to 1996] Record rejected
Feedback report messages (PVAL15)
Sub–edit Text Type
PVAL15-1 Province/territory or country of death code is invalid for Date of death prior to 1996. Core error
PVAL15-2 Province/territory or country of death code is invalid for Date of death in and after 1996. Core error
PVAL15-3 Province/territory or country of death code is invalid. Core error
Revision (PVAL15)
Year Description
2004 Business rules changed: Province/territory or country of death code is now validated against Province/territory or country codes valid at time of death.

PVAL16

Purpose

This edit validates the death registration number.

Referenced fields (PVAL16)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P16 6 Death registration number PDEAREG

Business rules

For Add and Update Patient records, Death registration number
  • Must be exclusively composed of numbers: 0 to 9
  • Must be 6 digits long
Edit logic (PVAL16)
Sub–edit Conditions Outcome
PVAL16-1 P4 IN [‘1', ‘2'] AND (LENGTH (P16) <> 6 OR NOT IS_COMPOSED_OF (P16, ‘0123456789')) Record rejected
Feedback report messages (PVAL16
Sub–edit Text Type
PVAL16-1 Death registration number is not 6 digits long. Core error
Revision (PVAL16)
Year Description
Not applicable Not applicable

PVAL17

Purpose

This edit validates the underlying cause of death code.

Referenced fields (PVAL17)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P14.YEAR 4 First 4 characters of P14 (year of date of death) Not applicable
P17 3 Underlying cause of death PCAUSDEA

Business rules

For Add and Update Patient records
  • IF Date of death is unknown then Underlying cause of death must be coded as ‘Unknown/unavailable Underlying cause of death'.
  • IF Date of death is before 2000 then Underlying cause of death must be one of the Eligible ICD-9 underlying cause of death codes12.
  • IF Date of death is between 2000 and 2002 inclusively then Underlying cause of death must be one of the Eligible ICD-10 underlying cause of death codes in 2000-200212
  • IF Date of death is in or after 2003 then Underlying cause of death must be one of the Eligible ICD-10 underlying cause of death codes in 2003 and after13.
Edit logic (PVAL17)
Sub–edit Conditions Outcome
PVAL17-1 P4 IN [‘1', ‘2'] AND P14.YEAR = ‘9999' AND P17 <> ‘0009' Record rejected
PVAL17-2 P4 IN [‘1', ‘2'] AND P14.YEAR NOT IN [‘0000', ‘9999'] AND P14.YEAR < 2000 AND P17 NOT IN [ICD-9 – Cause of death] Record rejected
PVAL17-3 P4 IN [‘1', ‘2'] AND P14.YEAR NOT IN [‘0000', ‘9999'] AND P14.YEAR >= 2000 AND P14.YEAR <= 2002 AND P17 NOT IN [ICD-10 – Cause of death in 2000-2002] Record rejected
PVAL17-4 P4 IN [‘1', ‘2'] AND P14.YEAR NOT IN [‘0000', ‘9999'] AND P14.YEAR >= 2003 AND P17 NOT IN [ICD-10 – Cause of death in 2003 and after] Record rejected
Feedback report messages (PVAL17)
Sub–edit Text Type
PVAL17-1 Underlying cause of death must be set to unknown when the Date of death is unknown. Core error
PVAL17-2 Underlying cause of death code is either invalid or not eligible for Date of death prior to 2000. Core error
PVAL17-3 Underlying cause of death code is either invalid or not eligible for Date of death between 2000 and 2002 inclusively. Core error
PVAL17-4 Underlying cause of death code is either invalid or not eligible for Date of death in or after 2003. Core error
Revision (PVAL17)
Year Description
2004 Business rules added:
If Date of death is unknown then Underlying cause of death must be coded as ‘Unknown/unavailable Underlying cause of death'.
If Date of death is in 2003 or after then Underlying cause of death must be coded using the latest revision of ICD-10 Underlying cause of death (2003 and after).

PVAL18

Purpose

This edit validates autopsy confirming cause of death code.

Referenced fields (PVAL18)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P18 1 Autopsy confirming cause of death PAUTOPSY

Business rules

For Add and Update Patient records
  • Autopsy confirming cause of death must be one of the eligible autopsy confirming cause of death codes14.
Edit logic (PVAL18)
Sub–edit Conditions Outcome
PVAL18-1 P4 IN [‘1', ‘2'] AND P18 NOT IN [Eligible Autopsy confirming cause of death codes] Record rejected
Feedback report messages (PVAL18)
Sub–edit Text Type
PVAL18-1 Autopsy confirming cause of death code is invalid. Core error
Revision (PVAL18)
Year Description
Not applicable Not applicable

PVAL19

Purpose

This edit validates the patient record date of transmission.

Referenced fields (PVAL19)
Field Length Description Acronym
P19 8 Patient Date of transmission PDATTRAN
P19.YEAR 4 First 4 digits of P19 (year of date of transmission) Not applicable
P19.MONTH 2 5th and 6th digits of P19 (month of date of transmission) Not applicable
P19.DAY 2 7th and 8th digits of P19 (day of date of transmission) Not applicable
Other parameters (PVAL19)
Parameters Length Description
LOAD_DATE 8 Statistics Canada loading date: date on the Statistics Canada computer clock when the data are loaded on the CCR database.

Business rules

For Input Patient records, Patient Date of transmission
  • Cannot be blank
  • Must be exclusively composed of numbers: 0 to 9
  • Must be 8 digits long
  • Must be a valid calendar date
  • Must be within the previous 10 months from Statistics Canada loading date
Edit logic (PVAL19)
Sub–edit Conditions Outcome
PVAL19-1 P19 IS NULL Record rejected
PVAL19-2 P19 IS NOT NULL AND (LENGTH (P19) <> 8 OR NOT IS_COMPOSED_OF (P19, ‘0123456789')) Record rejected
PVAL19-3 P19 IS NOT NULL AND LENGTH (P19) = 8 AND IS_COMPOSED_OF (P19, ‘0123456789') AND NOT IS_VALID_DATE (P19) Record rejected
PVAL19-4 P19 IS NOT NULL AND LENGTH (P19) = 8 AND IS_COMPOSED_OF (P19, ‘0123456789') AND IS_VALID_DATE (P19) AND P19 > LOAD_DATE () Record rejected
PVAL19-5 P19 IS NOT NULL AND LENGTH (P19) = 8 AND IS_COMPOSED_OF (P19, ‘0123456789') AND IS_VALID_DATE (P19) AND P19 < (LOAD_DATE – 10 months) Record rejected
Feedback report messages (PVAL19)
Sub–edit Text Type
PVAL19-1 Patient Date of transmission is missing. Core fatal error
PVAL19-2 Patient Date of transmission is not 8 digits long. Core fatal error
PVAL19-3 Patient Date of transmission is not a valid calendar date. Core fatal error
PVAL19-4 Patient Date of transmission is after Statistics Canada loading date. Core fatal error
PVAL19-5 Patient Date of transmission is more than 10 months before Statistics Canada loading date. Core fatal error
Revision (PVAL19)
Year Description
Not applicable Not applicable

3.4.2 Tumour validation edits

The following table summarizes the purpose of each individual edit of this category.

Table 25 Tumour validation edits summary

Table 25 Tumour validation edits summary
Edit name Purpose
TVAL1 Validates the Tumour reporting province/territory code.
TVAL2 Validates the Tumour patient identification number.
TVAL3 Validates the Tumour reference number.
TVAL4 Validates the CCR identification number.
TVAL5 Validates the Tumour record type code.
TVAL6 Validates the Name of place of residence.
TVAL7 Validates the Postal code.
TVAL8 Validates the Standard geographic code.
TVAL9 Validates the Census tract.
TVAL10 Validates the Health insurance number (HIN).
TVAL11 Validates the Method of diagnosis code.
TVAL12 Validates the Date of diagnosis.
TVAL13 Validates the ICD-9 cancer code.
TVAL14 Validates the Source classification flag.
TVAL15 Validates the ICD-O-2/3 Topography code.
TVAL16 Validates the ICD-O-2 Histology code.
TVAL17 Validates the ICD-O-2 Behaviour code.
TVAL18 Not applicable
TVAL19 Validates the Laterality code.
TVAL20 Not applicable
TVAL21 Validates the ICD-O-3 Histology code.
TVAL22 Validates the ICD-O-3 Behaviour code.
TVAL23 Validates the grade, differentiation or cell indicator code.
TVAL24 Validates the Method used to establish the date of diagnosis code.
TVAL25 Validates the Diagnostic confirmation code.
TVAL26 Validates the Date of transmission.
TVAL27 Validates CS tumour size.
TVAL28 Validates CS extension.
TVAL29 Validates CS tumour size/ext eval.
TVAL30 Validates CS lymph nodes.
TVAL31 Validates CS reg nodes eval.
TVAL32 Validates Regional nodes examined.
TVAL33 Validates Regional nodes positive.
TVAL34 Validates CS mets at dx.
TVAL35 Validates CS mets eval.
TVAL36 Validates CS site-specific factor 1.
TVAL37 Validates CS site-specific factor 2.
TVAL38 Validates CS site-specific factor 3.
TVAL39 Validates CS site-specific factor 4.
TVAL40 Validates CS site-specific factor 5.
TVAL41 Validates CS site-specific factor 6.
TVAL42 Validates AJCC clinical T.
TVAL43 Validates AJCC clinical N.
TVAL44 Validates AJCC clinical M.
TVAL45 Validates AJCC pathologic T.
TVAL46 Validates AJCC pathologic N.
TVAL47 Validates AJCC pathologic M.
TVAL48 Validates AJCC clinical TNM stage group.
TVAL49 Validates AJCC pathologic TNM stage group.
TVAL50 Validates AJCC TNM stage group.
TVAL51 Validates AJCC edition number code.
TVAL52 Validates CS Version 1st.
TVAL53 Validates Ambiguous Terminology Diagnosis.
TVAL54 Validates Date of Conclusive Diagnosis.
TVAL55 Validates Type of Multiple Tumours Reported as One Primary.
TVAL56 Validates Date of Multiple Tumours.
TVAL57 Validates Multiplicity Counter.

TVAL1

Purpose

This edit validates the Tumour reporting province/territory code.

Referenced Fields (TVAL1)
Field Length Description Acronym
T1 2 Tumour reporting province/territory TREPPROV
Other parameters (TVAL1)
Parameters Length Description
PTCR_CODE 2 Province/territory code of the PTCR that is submitting the data.

Business rules

For Input Tumour records
  • Tumour reporting province/territory must be equal to province/territory code of the PTCR that is submitting the data15.
Edit logic (TVAL1)
Sub–edit Conditions Outcome
TVAL1-1 T1 <> PTCR_CODE Record rejected
Feedback report messages (TVAL1)
Sub–edit Text Type
TVAL1-1 Tumour reporting province/territory code does not match PTCR province/territory code. Core error
Revision (TVAL1)
Year Description
Not applicable Not applicable

TVAL2

Purpose

This edit validates the tumour patient identification number.

Referenced fields (TVAL2)
Field Length Description Acronym
T2 12 Tumour patient identification number TPIN

Business rules

For Input Tumour records, Patient identification number
  • Must be exclusively composed of any of the following:
    • Uppercase letters: A to Z
    • Numbers: 0 to 9
  • Cannot be exclusively composed of zeros.
Edit logic (TVAL2)
Sub–edit Conditions Outcome
TVAL2-1 IS_COMPOSED_OF (T2, ‘0') Record rejected
TVAL2-2 NOT IS_COMPOSED_OF (T2, ‘ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789') Record rejected
Feedback report messages (TVAL2)
Sub–edit Text Type
TVAL2-1 Patient identification number cannot be exclusively composed of zeros. Core error
TVAL2-2 Patient identification number is not exclusively composed of uppercase letters and/or numbers. Core error
Revision (TVAL2)
Year Description
2004 Business rule changed: Apostrophes, hyphens, periods and inner spaces are not accepted anymore.

TVAL3

Purpose

This edit validates the tumour reference number.

Referenced fields (TVAL3)
Field Length Description Acronym
T3 9 Tumour reference number TTRN

Business rules

For Input Tumour records, Tumour reference number
  • Must be exclusively composed of any of the following:
    • Numbers: 0 to 9
    • Uppercase letters: A to Z
    • Special characters: space ( ), period (.), apostrophe (‘), hyphens (-)
  • Cannot be exclusively composed of zeros.
Edit logic (TVAL3)
Sub–edit Conditions Outcome
TVAL3-1 IS_COMPOSED_OF (T3, ‘0') Record rejected
TVAL3-2 NOT IS_COMPOSED_OF (T3, ‘ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789 -‘.') Record rejected
Feedback report messages (TVAL3)
Sub–edit Text Type
TVAL3-1 Tumour reference number cannot be exclusively composed of zeros. Core error
TVAL3-2 Tumour reference number is not exclusively composed of acceptable letters, numbers or special characters. Core error
Revision (TVAL3)
Year Description
2004 Business rule added: Tumour reference number cannot be exclusively composed of zeros.

TVAL4

Purpose

This edit validates the CCR identification number.

Referenced fields (TVAL4)
Field Length Description Acronym
T4 9 CCR identification number CCR_ID
T4.ID 8 First 8 digits of T4 (CCR ID sequence number) Not applicable
T4.CHECK_DIGIT 1 9th digit of T4 (CCR ID check digit) Not applicable

Business rules

For Input Tumour records
  • If CCR identification number is reported then
    • Must be exclusively composed of numbers: 0 to 9
    • Must be 9 digits long;
    • Cannot be all zeros;
    • Must have a valid check digit16.
Edit logic (TVAL4)
Sub–edit Conditions Outcome
TVAL4-1 T4 IS NOT NULL AND (LENGTH (T4) <> 9 OR NOT IS_COMPOSED_OF (T4, ‘0123456789')) Record rejected
TVAL4-2 T4 = ‘000000000' Record rejected
TVAL4-3 T4 IS NOT NULL AND T4 <> ‘000000000' AND LENGTH (T4) = 9 AND IS_COMPOSED_OF (T4, ‘0123456789') AND T4.CHECK_DIGIT <> CALCULATE_CCR_CHECK_DIGIT (T4.ID) Record rejected
Feedback report messages (TVAL4)
Sub–edit Text Type
TVAL4-1 CCR identification number is not 9 digits long. Core error
TVAL4-2 CCR identification number cannot be all zeros. Core error
TVAL4-3 CCR identification number is invalid. Core error
Revision (TVAL4)
Year Description
Not applicable Not applicable

TVAL5

Purpose

This edit validates the tumour record type code.

Referenced fields (TVAL5)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE

Business rules

For Input Tumour records, Tumour record type
  • Cannot be blank.
  • Must be one of the Eligible tumour record type codes17 .
Edit logic (TVAL5)
Sub–edit Conditions Outcome
TVAL5-1 T5 IS NULL OR T5 NOT IN [Eligible tumour record type codes] Record rejected
Feedback report messages (TVAL5)
Sub–edit Text Type
TVAL5-1 Tumour record type code is missing or invalid. Core fatal error
Revision (TVAL5)
Year Description
Not applicable Not applicable

TVAL6

Purpose

This edit validates the name of place of residence.

Referenced fileds (TVAL6)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T6 25 Name of place of residence TPLACRES

Business rules

For Add and Update Tumour records
  • Name of place of residence can be blank.
  • If Name of place of residence is not blank then it can be any combination of the following:
    • Letters: A to Z (upper or lowercase)
      • Accented characters: Â À Ç É Ê Ë È Î Ï Ô Û Ü (upper or lowercase)
      • Special characters: space ( ), period (.), apostrophe ('), hyphen (-), exclamation mark (!), ampersand (&), forward slash (/), parenthese [“(“and”)”], number sign (#), comma (,)
  • It must contain a word of at least 2 letters.
Edit logic TVAL6)
Sub–edit Conditions Outcome
TVAL6-1 T5 IN [‘1', ‘2'] AND T6 IS NOT NULL AND IS NOT COMPOSED OF (UPPER (T6), ‘ABCDEFGHILKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ.'-!&/()#,') Record rejected
TVAL6-2 T5 IN [‘1', ‘2'] AND T6 IS NOT NULL AND IS_COMPOSED_OF (UPPER (T6), ‘ABCDEFGHILKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-!&/()#,') AND NOT CONTAINS_WORD (UPPER (T6), ‘ABCDEFGHILKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ', 2) Record rejected
Feedback report messages (TVAL6)
Sub–edit Text Type
TVAL6-1 Name of place of residence is not exclusively composed of acceptable letters, accented characters or special characters. Core error
TVAL6-2 Name of place of residence does not contain a word of at least 2 letters. Core error
Revision (TVAL6)
Year Description
2007 Business rules changed: Acceptable accented characters and special characters are specified.
Edit logic: New edit logic added.
Feedback report messages: New message added.

TVAL7

Purpose

This edit validates the postal code.

Referenced fields (TVAL7)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T7 6 Postal code TPOSTCOD
T7.FIRST 1 1st character of T7 Not applicable
T7.SECOND 1 2nd character of T7 Not applicable
T7.THIRD 1 3rd character of T7 Not applicable
T7.FOURTH 1 4th character of T7 Not applicable
T7.FIFTH 1 5th character of T7 Not applicable
T7.SIXTH 1 6th character of T7 Not applicable

Business rules

For Add and Update Tumour records, Postal code
  • Must be 6 characters long.
  • Can be unknown.
  • If not unknown then
    • 1st, 3rd and 5th characters must be uppercase letters: A-Z
    • 2nd, 4th and 6th characters must be numbers: 0-9
Edit logic (TVAL7)
Sub–edit Conditions Outcome
TVAL7-1 T5 IN [‘1', ‘2'] AND (LENGTH(T7) <> 6 OR (T7 <> ‘999999' AND (T7.FIRST NOT IN [A-Z] OR T7.SECOND NOT IN [0-9] OR T7.THIRD NOT IN [A-Z] OR T7.FOURTH NOT IN [0-9] OR T7.FIFTH NOT IN [A-Z] OR T7.SIXTH NOT IN [0-9]))) Record rejected
Feedback report messages (TVAL7)
Sub–edit Text Type
TVAL7-1 Postal code has an invalid format. Core error
Revision (TVAL7)
Year Description
Not applicable Not applicable

TVAL8

Purpose

This edit validates the Standard geographic code.

Referenced fields (TVAL8)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T8 7 Standard geographic code TCODPLAC
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable

Business rules

For Add and Update Tumour records
  • If Date of diagnosis is between 1992 and 1995 then Standard geographic code must be one of the Eligible Standard geographic classification codes from 1992 to 199512.
  • If Date of diagnosis is between 1996 and 2000 then Standard geographic code must be one of the Eligible Standard geographic classification codes from 1996 to 200012.
  • If Date of diagnosis is between 2001 and 2005 then Standard geographic code must be one of the Eligible Standard geographic classification codes from 2001 to 200512.
  • If Date of Diagnosis is between 2006 and 2010 then Standard geographic code must be one of the Eligible Standard geographic classification codes from 2006 and 2010.
Edit logic (TVAL8)
Sub–edit Conditions Outcome
TVAL8-1 T5 IN [‘1', ‘2'] AND T12.YEAR BETWEEN (‘1992', ‘1995') AND T8 NOT IN [Eligible Standard geographic classification codes from 1992 to 1995] Record rejected
TVAL8-2 T5 IN [‘1', ‘2'] AND T12.YEAR BETWEEN (‘1996', ‘2000') AND T8 NOT IN [Eligible Standard geographic classification codes from 1996 to 2000] Record rejected
TVAL8-3 T5 IN [‘1', ‘2'] AND T12.YEAR BETWEEN (‘2001', ‘2005') AND T8 NOT IN [Eligible Standard geographic classification codes from 2001 to 2005] Record rejected
TVAL8-4 T5 IN [‘1', ‘2'] AND T12.YEAR BETWEEN (‘2006', ‘2010') AND T8 NOT IN [Eligible Standard Geographic Classification codes from 2006 to 2010] Record rejected
Feedback report messages (TVAL8)
Sub–edit Text Type
TVAL8-1 Standard geographic code is invalid according to the Standard geographic classification – 1991. Core error
TVAL8-2 Standard geographic code is invalid according to the Standard geographic classification – 1996. Core error
TVAL8-3 Standard geographic code is invalid according to the Standard geographic classification – 2001. Core error
TVAL8-4 Standard geographic code is invalid according to the Standard geographic classification – 2006. Core error
Revision (TVAL8)
Year Description
2006 Business rules, Edit logic and Feedback report messages added: SGC – 2006 added
2001 Business rules, Edit logic and Feedback report messages added: SGC – 2001 added
1996 Business rules, Edit logic and Feedback report messages added: SGC – 1996 added

TVAL9

Purpose

This edit validates the census tract.

Referenced fields (TVAL9)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T9 9 Census tract TCENTRAC
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable

Business rules

For Add and Update Tumour records
  • If Date of diagnosis is between 1992 and 1995 then Census tract must be reported and must be one of the Eligible Census tracts from 1992 to 199512.
  • If Date of diagnosis is between 1996 and 2000 then Census tract must be reported and must be one of the Eligible Census tracts from 1996 to 200012.
  • If Date of diagnosis is between 2001 and 2005 then Census tract must be reported and must be one of the Eligible Census tracts from 2001 to 200512
  • If Date of Diagnosis is 2006 and onwards then Census Tract must not be reported (field should be left blank).
Edit logic (TVAL9)
Sub–edit Conditions Outcome
TVAL9-1 T5 IN [‘1', ‘2'] AND T12.YEAR BETWEEN (‘1992', ‘1995') AND (T9 IS NULL OR T9 NOT IN [Eligible Census tracts from 1992 to 1995]) Record rejected
TVAL9-2 T5 IN [‘1', ‘2'] AND T12.YEAR BETWEEN (‘1996', ‘2000') AND (T9 IS NULL OR T9 NOT IN [Eligible Census tracts from 1996 to 2000]) Record rejected
TVAL9-3 T5 IN [‘1', ‘2'] AND T12.YEAR BETWEEN (‘2001', ‘2005') AND (T9 IS NULL OR T9 NOT IN [Eligible Census tracts from 2001 to 2005]) Record rejected
TVAL9-4 T5 IN [‘1', ‘2'] AND T12.YEAR >= (‘2006') AND T9 <> NULL Record rejected
Feedback report messages (TVAL9)
Sub–edit Text Type
TVAL9-1 Census tract is invalid according to the Census tract Data Dictionary – 1991. Core error
TVAL9-2 Census tract is invalid according to the Census tract Data Dictionary – 1996. Core error
TVAL9-3 Census tract is invalid according to the Census tract Data Dictionary – 2001. Core error
TVAL9-4 Census tract must not be reported for cases diagnosed in 2006 and onwards. Core error
Revision (TVAL9)
Year Description
2006 Business rules, Edit logic and Feedback report messages added: Census tract effective date range ended in 2005. For cases diagnosed in 2006 and onwards, T9 (Census Tract) must be reported as blank (null)
2001 Business rules, Edit logic and Feedback report messages added: Eligible Census tracts – 2001 added
1996 Business rules, Edit logic and Feedback report messages added: Eligible Census tracts – 1996 added

TVAL10

Purpose

This edit validates the health insurance number (HIN).

Referenced fields (TVAL10)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T10 15 Health insurance number THIN

Business rules

For Add and Update Tumour records,
  • If Health insurance number is reported then
  • It must be at least 6 characters long.
  • It must be exclusively composed of any of the following:
    • Uppercase letters: A to Z
    • Numbers: 0 to 9
Edit logic (TVAL10)
Sub–edit Conditions Outcome
TVAL10-1 T5 IN [‘1', ‘2'] AND T10 IS NOT NULL AND LENGTH (T10) < 6 Record rejected
TVAL10-2 T5 IN [‘1', ‘2'] AND T10 IS NOT NULL AND NOT IS_COMPOSED_OF (T10, ‘ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789') Record rejected
Feddback report messages (TVAL10)
Sub–edit Text Type
TVAL10-1 Health insurance number is less than 6 characters long. Core error
TVAL10-2 Health insurance number is not exclusively composed of uppercase letters and/or numbers. Core error
Revision (TVAL10)
Year Description
Not applicable Not applicable

TVAL11

Purpose

This edit validates the method of diagnosis code.

Referenced fields (TVAL11)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T11 1 Method of diagnosis TMETHDIAG

Business rules

For Add and Update Tumour records
  • Method of diagnosis must be one of the Eligible method of diagnosis codes18.
Edit logic (TVAL11)
Sub–edit Conditions Outcome
TVAL11-1 T5 IN [‘1', ‘2'] AND T11 NOT IN [Eligible method of diagnosis codes] Record rejected
Feedback report messages (TVAL11)
Sub–edit Text Type
TVAL11-1 Method of diagnosis code is invalid. Core error
Revision (TVAL11)
Year Description
Not applicable Not applicable

TVAL12

Purpose

This edit validates the date of diagnosis.

Referenced fields (TVAL12)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12 8 Date of diagnosis TDATDIAG
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T12.MONTH 2 5th and 6th digits of T12 (month of date of diagnosis) Not applicable
T12.DAY 2 Last 2 digits of T12 (day of date of diagnosis) Not applicable
Other parameters (TVAL12)
Parameters Length Description
CYCLE_YEAR 4 Reference year

Business rules

For Add and Update Tumour records, Date of Diagnosis
  • Must be exclusively composed of numbers: 0 to 9.
  • Must be 8 digits long.
  • Must be between January 1st, 1992 and December 31st of Reference year inclusively.
  • Year cannot be unknown.
  • If Month is unknown then Day must be unknown.
  • If Year, Month and Day are known then it must be a valid calendar date.
  • If Year and Month are known and Day is unknown then Month must be a valid month.
Edit logic (TVAL12)
Sub–edit Conditions Outcome
TVAL12-1 T5 IN [‘1', ‘2'] AND (LENGTH (T12) <> 8 OR NOT IS_COMPOSED_OF (T12, ‘0123456789')) Record rejected
TVAL12-2 T5 IN [‘1', ‘2'] AND LENGTH (T12) = 8 AND IS_COMPOSED_OF (T12, ‘0123456789') AND T12.MONTH = ‘99' AND T12.DAY <> ‘99' Record rejected
TVAL12-3 T5 IN [‘1', ‘2'] AND LENGTH (T12) = 8 AND IS_COMPOSED_OF (T12, ‘0123456789'' AND (T12.YEAR < 1992 OR T12.YEAR > CYCLE_YEAR) Record rejected
TVAL12-4 T5 IN [‘1', ‘2'] AND LENGTH (T12) = 8 AND IS_COMPOSED_OF (T12, ‘0123456789') AND T12.MONTH <> ‘99' AND T12.DAY <> ‘99' AND NOT IS_VALID_DATE (T12) Record rejected
TVAL12-5 T5 IN [‘1', ‘2'] AND LENGTH (T12) = 8 AND IS_COMPOSED_OF (T12, ‘0123456789') AND T12.MONTH NOT IN [‘01'-'12', ‘99'] AND T12.DAY = ‘99' Record rejected
Feedback report messages (TVAL12)
Sub–edit Text Type
TVAL12-1 Date of diagnosis is not composed of 8 numbers. Core error
TVAL12-2 Date of diagnosis: Improper use of ‘Unknown' code. Core error
TVAL12-3 Date of diagnosis must be between January 1st, 1992 and December 31st of Reference year inclusively. Core error
TVAL12-4 Date of diagnosis is not a valid calendar date. Core error
TVAL12-5 Date of diagnosis is not a valid partial date: month is invalid. Core error
Revision (TVAL12)
Year Description
Not applicable Not applicable

TVAL13

Purpose

This edit validates the ICD-9 cancer code.

Referenced fields (TVAL13)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T13 4 ICD-9 cancer code TICD_9

Business rules

For Add and Update Tumour records
  • If ICD-9 Cancer code is reported then it must be one of the Eligible ICD-9 Cancer codes19.
Edit logic (TVAL13)
Sub–edit Conditions Outcome
TVAL13-1 T5 IN [‘1', ‘2'] AND T13 <> ‘0000' AND T13 NOT IN [Eligible ICD-9 Cancer codes] Record rejected
Feedback report messages (TVAL13)
Sub–edit Text Type
TVAL13-1 ICD-9 Cancer code is either invalid or not eligible for the CCR system. Core error
Revision (TVAL13)
Year Description
Not applicable Not applicable

TVAL14

Purpose

This edit validates the source classification flag.

Referenced fields (TVAL14)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T14 1 Source classification flag TSCF

Business rules

For Add and Update Tumour records
  • Source classification flag must be one of the Eligible source classification flags20.
Edit logic (TVAL14)
Sub–edit Conditions Outcome
TVAL14-1 T5 IN [‘1', ‘2'] AND T14 NOT IN [Eligible source classification flags] Record rejected
Feedback report messages (TVAL14)
Sub–edit Text Type
TVAL14-1 Source classification flag is invalid. Core error
Revision (TVAL14)
Year Description
Not applicable Not applicable

TVAL15

Purpose

This edit validates the ICD-O-2/3 topography code.

Referenced fields (TVAL15)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T15 4 ICD-O-2/3 Topography TICD_O2T

Business rules

For Add and Update Tumour records
  • ICD-O-2/3 Topography must be one of the Eligible ICD-O-2/3 Topography codes12.
Edit logic (TVAL15)
Sub–edit Conditions Outcome
TVAL15-1 T5 IN [‘1', ‘2'] AND T15 NOT IN [Eligible ICD-O-2/3 Topography codes] Record rejected
Feedback report messages (TVAL15)
Sub–edit Text Type
TVAL15-1 ICD-O-2/3 Topography code is either invalid or not eligible for the CCR System. Core error
Revision (TVAL15)
Year Description
Not applicable Not applicable

TVAL16

Purpose

This edit validates the ICD-O-2 histology code.

Referenced fields (TVAL16)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T15 4 ICD-O-2/3 Topography TICD_O2T
T16 4 ICD-O-2 Histology TICD_O2H

Business rules

For Add and Update Tumour records
  • If ICD-O-2 Histology is reported then it must be one of the Eligible ICD–O–2 Histology codes12.
Edit logic (TVAL16)
Sub–edit Conditions Outcome
TVAL16-1 T5 IN [‘1', ‘2'] AND T15 <> ‘0000' AND T16 NOT IN [Eligible ICD-O-2 Histology codes] Record rejected
Feedback report messages (TVAL16)
Sub–edit Text Type
TVAL16-1 ICD-O-2 Histology code is either invalid or not eligible for the CCR System. Core error
Revision (TVAL16)
Year Description
Not applicable Not applicable

TVAL17

Purpose

This edit validates the ICD-O-2 Behaviour code.

Referenced fields (TVAL17)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T17 1 ICD-O-2 Behaviour TICD_O2B

Business rules

For Add and Update Tumour records
  • If ICD-O-2 Behaviour is reported then it must be one of the Eligible ICD–O–2 Behaviour codes21.
Edit logic (TVAL17)
Sub–edit Conditions Outcome
TVAL17-1 T5 IN [‘1', ‘2'] AND T17 NOT IN [Eligible ICD–O–;2 Behaviour codes] Record rejected
Feedback report messages (TVAL17)
Sub–edit Text Type
TVAL17-1 ICD-O-2 Behaviour code is either invalid or not eligible for the CCR system. Core error
Revision (TVAL17)
Year Description
Not applicable Not applicable

TVAL18

Purpose

Not applicable

Referenced fields (TVAL18)
Field Length Description Acronym
T18 4 Filler Not applicable

Business rules

For Input Tumour records
  • Filler can be anything, including blank.
Edit logic (TVAL18)
Sub–edit Conditions Outcome
Not applicable Not applicable Not applicable
Feedback report messages (TVAL18)
Sub–edit Text Type
Not applicable Not applicable Not applicable
Revision (TVAL18)
Year Description
2004 Edit removed: Filler can be anything, including blank.

Note
This empty validation is kept as a placeholder for future requirement implementation.

TVAL19

Purpose

This edit validates the laterality code.

Referenced fields (TVAL19)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T19 1 Laterality TLATERAL

Business rules

For Add and Update Tumour records
  • Laterality must be one of the Eligible laterality codes22.
Edit logic (TVAL19)
Sub–edit Conditions Outcome
TVAL19-1 T5 IN [‘1', ‘2'] AND T19 NOT IN [Eligible laterality codes] Record rejected
Feedback report messages (TVAL19)
Sub–edit Text Type
TVAL19-1 Laterality code is invalid. Core error
Revision (TVAL19)
Year Description
Not applicable Not applicable

TVAL20

Purpose

Not applicable

Referenced fields (TVAL20)
Field Length Description Acronym
T20 1 Filler Not applicable

Business rules

For Input Tumour records
  • Filler can be anything, including blank.
Edit logic TVAL20)
Sub–edit Conditions Outcome
Not applicable Not applicable Not applicable
Feedback report messages (TVAL20)
Sub–edit Text Type
Not applicable Not applicable Not applicable
Revision (TVAL20)
Year Description
2004 Edit removed: Filler can be anything, including blank.

Note:
This empty validation is kept as a placeholder for future requirement implementation.

TVAL21

Purpose

This edit validates the ICD-O-3 Histology code.

Referenced fields (TVAL21)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T21 4 ICD-O-3 Histology TICD_O3H

Business rules

For Add and Update Tumour records
  • ICD-O-3 Histology must be one of the Eligible ICD–O–3 Histology codes12,23.
Edit logic (TVAL21)
Sub–edit Conditions Outcome
TVAL21-1 T5 IN [‘1', ‘2'] AND T21 NOT IN [Eligible ICD-O-3 Histology codes] Record rejected
Feedback report messages (TVAL21)
Sub–edit Text Type
TVAL21-1 ICD-O-3 Histology code is either invalid or not eligible for the CCR System. Core error
Revision (TVAL21)
Year Description
2004 Edit renamed: Current edit was formerly known as Validation edit No.21M.

TVAL22

Purpose

This edit validates the ICD-O-3 Behaviour code.

Referenced fields TVAL22)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T22 1 ICD-O-3 Behaviour TICD_O3B

Business rules

For Add and Update Tumour records
  • ICD-O-3 Behaviour must be one of the Eligible ICD–O–3 Behaviour codes24.
Edit logic (TVAL22)
Sub–edit Conditions Outcome
TVAL22-1 T5 IN [‘1', ‘2'] AND T22 NOT IN [Eligible ICD–O–3 Behaviour codes] Record rejected
Feedback report messages TVAL22)
Sub–edit Text Type
TVAL22-1 ICD-O-3 Behaviour code is either invalid or not eligible for the CCR system. Core error
Revision (TVAL22)
Year Description
2004 Edit reorganized: Edit formerly known as Validation edit No.22 moved to TVAL26.
Edit renamed: Current edit was formerly known as Validation edit No.21B.

TVAL23

Purpose

This edit validates the grade, differentiation or cell indicator code.

Referenced fields (TVAL23)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T23 1 Grade, differentiation or cell indicator TGRADE

Business rules

For Add and Update Tumour records
  • Grade, differentiation or cell indicator must be one of the Eligible grade, differentiation or cell indicator codes25.
Edit logic (TVAL23)
Sub–edit Conditions Outcome
TVAL23-1 T5 IN [‘1', ‘2'] AND T23 NOT IN [Eligible grade, differentiation or cell indicator codes] Record rejected
Feedback report messages (TVAL23)
Sub–edit Text Type
TVAL23-1 Grade, differentiation or cell indicator code is invalid. Core error
Revision (TVAL23)
Year Description
2004 Edit reorganized: Edit formerly known as Validation edit No.23 moved to TVAL24.
Edit added: New edit.

TVAL24

Purpose

This edit validates the method used to establish the date of diagnosis code.

Referenced fields (TVAL24)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T24 1 Method used to establish the date of diagnosis TMETHUSED

Business rules

For Add and Update Tumour records
  • Method used to establish the date of diagnosis must be one of the Eligible method used to establish the date of diagnosis codes26.
Edit logic (TVAL24)
Sub–edit Conditions Outcome
TVAL24-1 T5 IN [‘1', ‘2'] AND T24 NOT IN [Eligible method used to establish the date of diagnosis codes] Record rejected
Feedback report messages (TVAL24)
Sub–edit Text Type
TVAL24-1 Method used to establish the date of diagnosis code is invalid. Core error
Revision(TVAL24)
Year Description
2004 Edit reorganized: Edit formerly known as Validation edit No.24 moved to TVAL25.
Edit renamed: Current edit formerly known as Validation edit No.23.

TVAL25

Purpose

This edit validates the diagnostic confirmation code.

Referenced fields (TVAL25)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T25 1 Diagnostic Confirmation TMETHCONF

Business rules

For Add and Update Tumour records
  • Diagnostic confirmation must be one of the Eligible diagnostic confirmation codes27.
Edit logic (TVAL25)
Sub–edit Conditions Outcome
TVAL25-1 T5 IN [‘1', ‘2'] AND T25 NOT IN [Eligible diagnostic confirmation codes] Record rejected
Feedback report messages (TVAL25)
Sub–edit Text Type
TVAL25-1 Diagnostic confirmation code is invalid. Core error
Revision (TVAL25)
Year Description
2004 Edit renamed: Current edit formerly known as Validation edit No.24.

TVAL26

Purpose

This edit validates the tumour date of transmission.

Referenced fields (TVAL26)
Field Length Description Acronym
T26 8 Tumour date of transmission TDATTRAN
T26.YEAR 4 First 4 digits of T26 (year of date of transmission) Not applicable
T26.MONTH 2 5th and 6th digits of T26 (month of date of transmission) Not applicable
T26.DAY 2 7th and 8th digits of T26 (day of date of transmission) Not applicable
Other parameters (TVAL26)
Parameters Length Description
LOAD_DATE 8 Statistics Canada loading date: Date on the Statistics Canada computer clock when the data are loaded on the CCR database.

Business rules

For Input Tumour records, Tumour date of transmission
  • Cannot be blank.
  • Must be exclusively composed of numbers: 0 to 9.
  • Must be 8 digits long.
  • Must be a valid calendar date.
  • Must be within the previous 10 months from Statistics Canada loading date.
Edit logic (TVAL26)
Sub–edit Conditions Outcome
TVAL26-1 T26 IS NULL Record rejected
TVAL26-2 T26 IS NOT NULL AND (LENGTH (T26) <> 8 OR NOT IS_COMPOSED_OF (T26, ‘0123456789')) Record rejected
TVAL26-3 T26 IS NOT NULL AND LENGTH (T26) = 8 AND IS_COMPOSED_OF (T26, ‘0123456789') AND NOT IS_VALID_DATE (T26) Record rejected
TVAL26-4 T26 IS NOT NULL AND LENGTH (T26) = 8 AND IS_COMPOSED_OF (P26, ‘0123456789') AND IS_VALID_DATE (T26) AND T26 > LOAD_DATE Record rejected
TVAL26-5 T26 IS NOT NULL AND LENGTH (T26) = 8 AND IS_COMPOSED_OF (T26, ‘0123456789') AND IS_VALID_DATE (T26) AND T26 < (LOAD_DATE – 10 months) Record rejected
Feedback report messages (TVAL26)
Sub–edit Text Type
TVAL26-1 Tumour date of transmission is missing. Core fatal error
TVAL26-2 Tumour date of transmission is not 8 digits long. Core fatal error
TVAL26-3 Tumour date of transmission is not a valid calendar date. Core fatal error
TVAL26-4 Tumour date of transmission is after Statistics Canada loading date. Core fatal error
TVAL26-5 Tumour date of transmission is more than 10 months before Statistics Canada loading date. Core fatal error
Revision (TVAL26)
Year Description
2004 Edit renamed: Current edit formerly known as Validation edit No.22.

TVAL27

Purpose

This edit validates CS tumour size.

Referenced fields (TVAL27)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS tumour size must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL27)
Sub–edit Conditions Outcome
TVAL27-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <>'999999') AND NOT VALID_CS_TUMOUR_SIZE(T15, T21, T27) CS data items filled with 'R' at posting.
Feedback report messages (TVAL27)
Sub–edit Text Type
TVAL27-1 CS tumour size is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL27)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL28

Purpose

This edit validates CS extension.

Referenced fields (TVAL28)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD—O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR Collaborative staging scope28 and with at least one known CS variable,
  • CS extension must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL28)
Sub–edit Conditions Outcome
TVAL28-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> ‘999999') AND NOT VALID_CS_EXTENSION(T15, T21, T28) CS data items filled with 'R' at posting.
Feedback report messages (TVAL28)
Sub–edit Text Type
TVAL28-1 CS extension is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL28)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL29

Purpose

This edit validates CS tumour size/ext eval.

Referenced fields (TVAL29)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS tumour size/ext eval must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL29)
Sub–edit Conditions Outcome
TVAL29-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> ‘999999') AND NOT VALID _CS_TUMOUR_SIZE/EXT_EVAL(T15, T21, T29) CS data items filled with 'R' at posting.
Feedback report messages (TVAL29)
Sub–edit Text Type
TVAL29-1 CS tumour size/ext eval is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL29)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL30

Purpose

This edit validates CS lymph nodes.

Referenced fields (TVAL30)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS lymph nodes must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL30)
Sub–edit Conditions Outcome
TVAL30-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> ‘999999') AND NOT VALID CS_LYMPH_NODES(T15, T21, T30) CS data items filled with 'R' at posting.
Feedback report messages (TVAL30)
Sub–edit Text Type
TVAL30-1 CS lymph nodes is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL30)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL31

Purpose

This edit validates CS reg nodes eval.

Referenced fields (TVAL31)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS reg nodes eval must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL31)
Sub–edit Conditions Outcome
TVAL31-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> ‘999999') AND NOT VALID_CS_REG_NODES_EVAL(T15, T21, T31) CS data items filled with 'R' at posting.
Feedback report messages (TVAL31)
Sub–edit Text Type
TVAL31-1 CS reg nodes eval is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL31)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL32

Purpose

This edit validates regional nodes examined.

Referenced fields (TVAL32)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • Regional nodes examined must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL32)
Sub–edit Conditions Outcome
TVAL32-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> ‘999999') AND NOT VALID_REGIONAL_NODES_EXAMINED(T15, T21, T32) CS data items filled with 'R' at posting.
Feedback report messages (TVAL32)
Sub–edit Text Type
TVAL32-1 Regional nodes examined is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL32)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL33

Purpose

This edit validates regional nodes positive.

Referenced fields (TVAL33)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • Regional nodes positive must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL33)
Sub–edit Conditions Outcome
TVAL33-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> ‘999999') AND NOT VALID_REGIONAL_NODES_POSITIVE(T15, T21, T33) CS data items filled with 'R' at posting.
Feedback report messages TVAL33)
Sub–edit Text Type
TVAL33-1 Regional nodes positive is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL33)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL34

Purpose

This edit validates CS mets at dx.

Referenced fields (TVAL34)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS mets at dx must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL34)
Sub–edit Conditions Outcome
TVAL34-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38 <>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> ‘999999') AND NOT VALID_CS_METS_AT_DX(T15, T21, T34) CS data items filled with 'R' at posting.
Feedback report messages (TVAL34)
Sub–edit Text Type
TVAL34-1 CS mets at dx is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL34)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL35

Purpose

This edit validates CS mets eval.

Referenced fields (TVAL35)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS mets eval must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL35)
Sub–edit Conditions Outcome
TVAL35-1 T5 IN [‘1', ‘2']AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> ‘999999') AND NOT VALID_CS_METS_EVAL(T15, T21, T35) CS data items filled with 'R' at posting.
Feedback report messages (TVAL35)
Sub–edit Text Type
TVAL35-1 CS mets eval is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL35)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL36

Purpose

This edit validates CS site-specific factor 1.

Referenced fields (TVAL36)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS site-specific factor 1 must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL36)
Sub–edit Conditions Outcome
TVAL36-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> ‘999999') AND NOT VALID_CS_SITE-SPECIFIC_FACTOR_1(T15, T21, T36) CS data items filled with 'R' at posting.
Feedback report messages (TVAL36)
Sub–edit Text Type
TVAL36-1 CS site-specific factor 1 is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL36)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm.
2004 Edit added: New edit.

TVAL37

Purpose

This edit validates CS site-specific factor 2.

Referenced fields (TVAL37)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS site-specific factor 2 must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL37)
Sub–edit Conditions Outcome
TVAL37-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> ‘999999') AND NOT VALID_CS_SITE-SPECIFIC_FACTOR_2(T15, T21, T37) CS data items filled with 'R' at posting.
Feedback report messages (TVAL37)
Sub–edit Text Type
TVAL37-1 CS site-specific factor 2 is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL37)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm.
2004 Edit added: New edit.

TVAL38

Purpose

This edit validates CS site-specific factor 3.

Referenced fields (TVAL38)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS site-specific factor 3 must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL38)
Sub–edit Conditions Outcome
TVAL38-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> ‘999999') AND NOT VALID_CS_SITE-SPECIFIC_FACTOR_3(T15, T21, T38) CS data items filled with 'R' at posting.
Feedback report messages (TVAL38)
Sub–edit Text Type
TVAL38-1 CS site-specific factor 3 is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL38)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm.
2004 Edit added: New edit.

TVAL39

Purpose

This edit validates CS site-specific factor 4.

Referenced fields (TVAL39)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS site-specific factor 4 must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL39)
Sub–edit Conditions Outcome
TVAL39-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> ‘999999') AND NOT VALID_CS_SITE-SPECIFIC_FACTOR_4(T15, T21, T39) CS data items filled with 'R' at posting.
Feedback report messages (TVAL39)
Sub–edit Text Type
TVAL39-1 CS site-specific factor 4 is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL39)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm.
2004 Edit added: New edit.

TVAL40

Purpose

This edit validates CS site-specific factor 5.

Referenced fields (TVAL40)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28and with at least one known CS variable
  • CS site-specific factor 5 must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL40)
Sub–edit Conditions Outcome
TVAL40-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> ‘999999') AND NOT VALID_CS_SITE-SPECIFIC_FACTOR_5(T15, T21, T40) CS data items filled with 'R' at posting.
Feedback report messages (TVAL40)
Sub–edit Text Type
TVAL40-1 CS site-specific factor 5 is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL40)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL41

Purpose

This edit validates CS site-specific factor 6.

Referenced fields (TVAL41)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD–O–2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS site-specific factor 6 must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL41)
Sub–edit Conditions Outcome
TVAL41-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> ‘999999') AND NOT VALID_CS_SITE-SPECIFIC_FACTOR_6(T15, T21, T41) CS data items filled with 'R' at posting.
Feedback report messages (TVAL41)
Sub–edit Text Type
TVAL41-1 CS site-specific factor 6 is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL41)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL42

Purpose

This edit validates AJCC clinical T

Referenced fields (TVAL42)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T42 9 AJCC clinical T TAJCCCLINT

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • AJCC clinical T must be one of the Eligible AJCC clinical T values for the corresponding site30.

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Edit logic (TVAL42)
Sub–edit Conditions Outcome
TVAL42-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T42 NOT IN [Eligible AJCC clinical T for Site X] AJCC TNM data items filled with 'R' at posting.
Feedback report messages (TVAL42)
Sub–edit Text Type
TVAL42-1 AJCC clinical T is invalid for reported site. AJCC TNM error
Revision (TVAL42)
Year Description
2004 Edit added: New edit.

TVAL43

Purpose

This edit validates AJCC clinical N.

Referenced fields (TVAL43)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T43 3 AJCC clinical N TAJCCCLINN

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • AJCC clinical N must be one of the Eligible AJCC clinical N values for the corresponding site31.

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example : Colorectal, breast or prostate.

Edit logic (TVAL43)
Sub–edit Conditions Outcome
TVAL43-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T43 NOT IN [Eligible AJCC clinical N for Site X] AJCC TNM data items filled with 'R' at posting.
Feedback report messages (TVAL43)
Sub–edit Text Type
TVAL43-1 AJCC clinical N is invalid for reported site. AJCC TNM error
Revision (TVAL43)
Year Description
2004 Edit added: New edit.

TVAL44

Purpose

This edit validates AJCC clinical M.

Referenced fields (TVAL44)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T44 3 AJCC clinical M TAJCCCLINM

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • AJCC clinical M must be one of the Eligible AJCC clinical M values for the corresponding site32.

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Ex: Colorectal, breast or prostate.

Edit logic (TVAL44)
Sub–edit Conditions Outcome
TVAL44-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T44 NOT IN [Eligible AJCC clinical M for Site X] AJCC TNM data items filled with 'R' at posting.
Feedback report messages (TVAL44)
Sub–edit Text Type
TVAL44-1 AJCC clinical M is invalid for reported site. AJCC TNM error
Revision (TVAL44)
Year Description
2004 Edit added: New edit.

TVAL45

Purpose

This edit validates AJCC pathologic T.

Referenced fields (TVAL45)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T45 9 AJCC pathologic T TAJCCPATHT

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • AJCC pathologic T must be one of the Eligible AJCC pathologic T values for the corresponding site33.

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Edit logic (TVAL45)
Sub–edit Conditions Outcome
TVAL45-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T45 NOT IN [Eligible AJCC pathologic T for Site X] AJCC TNM data items filled with 'R' at posting.
Feedback report messages (TVAL45)
Sub–edit Text Type
TVAL45-1 AJCC pathologic T is invalid for reported site. AJCC TNM error
Revision (TVAL45)
Year Description
2004 Edit added: New edit.

TVAL46

Purpose

This edit validates AJCC pathologic N.

Referenced fields (TVAL46)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T46 3 AJCC pathologic N TAJCCPATHN

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • AJCC pathologic N must be one of the Eligible AJCC pathologic N values for the corresponding site34.

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Edit logic (TVAL46)
Sub–edit Conditions Outcome
TVAL46-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T46 NOT IN [Eligible AJCC pathologic N for Site X] AJCC TNM data items filled with 'R' at posting.
Feedback report messages (TVAL46)
Sub–edit Text Type
TVAL46-1 AJCC pathologic N is invalid for reported site. AJCC TNM error
Revision (TVAL46)
Year Description
2004 Edit added: New edit.

TVAL47

Purpose

This edit validates AJCC pathologic M.

Referenced fields (TVAL47)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T47 3 AJCC pathologic M TAJCCPATHM

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • AJCC pathologic M must be one of the Eligible pathologic M values for the corresponding site35.

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Edit logic (TVAL47)
Sub–edit Conditions Outcome
TVAL47-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T47 NOT IN [Eligible AJCC pathologic M for Site X] AJCC TNM data items filled with 'R' at posting.
Feedback report messages (TVAL47)
Sub–edit Text Type
TVAL47-1 AJCC pathologic M is invalid for reported site. AJCC TNM error
Revision (TVAL47)
Year Description
2004 Edit added: New edit.

TVAL48

Purpose

This edit validates AJCC clinical TNM stage group.

Referenced fields (TVAL48)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T48 4 AJCC clinical TNM stage group TAJCCCLINSG

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • AJCC clinical TNM stage group must be one of the Eligible AJCC clinical TNM stage group values for the corresponding site38.

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Edit logic (TVAL48)
Sub–edit Conditions Outcome
TVAL48-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T48 NOT IN [Eligible AJCC clinical TNM stage group for Site X] AJCC TNM data items filled with 'R' at posting.
Feedback report messages (TVAL48)
Sub–edit Text Type
TVAL48-1 AJCC clinical TNM stage group is invalid for reported site. AJCC TNM error
Revision (TVAL48)
Year Description
2004 Edit added: New edit.

TVAL49

Purpose

This edit validates AJCC pathologic TNM stage group.

Referenced fields (TVAL49)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T49 4 AJCC pathologic TNM stage group TAJCCPATHSG

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • AJCC pathologic TNM stage group must be one of the Eligible AJCC pathologic TNM stage group values for the corresponding site37.

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast orprostate.

Edit logic (TVAL49)
Sub–edit Conditions Outcome
TVAL49-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T49 NOT IN [Eligible AJCC pathologic TNM stage group for Site X] AJCC TNM data items filled with 'R' at posting.
Feedback report messages (TVAL49)
Sub–edit Text Type
TVAL49-1 AJCC pathologic TNM stage group is invalid for reported site. AJCC TNM error
Revision (TVAL49)
Year Description
2004 Edit added: New edit.

TVAL50

Purpose

This edit validates AJCC TNM stage group.

Referenced fields (TVAL50)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T50 4 AJCC TNM stage group TAJCCSG

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • AJCC TNM stage group must be one of the Eligible AJCC TNM stage group values for the corresponding site37.

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Edit logic (TVAL50)
Sub–edit Conditions Outcome
TVAL50-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T50 NOT IN [Eligible AJCC TNM stage group for Site X] AJCC TNM data items filled with 'R' at posting.
Feedback report messages (TVAL50)
Sub–edit Text Type
TVAL50-1 AJCC TNM stage group is invalid for reported site. AJCC TNM error
Revision (TVAL50)
Year Description
2004 Edit added: New edit.

TVAL51

Purpose

This edit validates AJCC edition number code.

Referenced fields (TVAL51)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T51 2 AJCC edition number TAJCCEDNUM

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • AJCC edition number must be one of the Eligible AJCC edition number codes38.

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Edit logic (TVAL51)
Sub–edit Conditions Outcome
TVAL51-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T51 NOT IN [Eligible AJCC edition number codes] AJCC TNM data items filled with 'R' at posting.
Feedback report messages (TVAL51)
Sub–edit Text Type
TVAL51-1 AJCC edition number code is either invalid or not eligible for the CCR system. AJCC TNM error
Revision (TVAL51)
Year Description
2004 Edit added: New edit.

TVAL52

Purpose

This edit validates CS Version 1st.

Referenced fields (TVAL52)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope and with at least one known CS variable
  • CS version 1st must be one of the Eligible CS Version 1st codes.
Edit logic (TVAL52)
Sub–edit Conditions Outcome
TVAL52-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2006' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' or T52 <> ‘999999') AND T52 NOT IN [Eligible CS Version 1st codes] CS data items filled with 'R' at posting.
Feedback report messages (TVAL52)
Sub–edit Text Type
TVAL52-1 CS Version 1st is not a valid version number CS error
Revision (TVAL52)
Year Description
2007 Edit added: New edit.

TVAL53

Purpose

This edit validates the Ambiguous terminology diagnosis code.

Referenced fields (TVAL53)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T53 1 Ambiguous Terminology Diagnosis TAMBIGTERM

Business rules

For Add and Update Tumour records
  • Ambiguous terminology diagnosis must be one of the Eligible Ambiguous terminology diagnosis codes.
Edit logic (TVAL53)
Sub–edit Conditions Outcome
TVAL53-1 T5 IN [‘1', ‘2'] AND T53 IS NOT NULL AND NOT IN [Eligible Ambiguous terminology diagnosis codes] Record rejected
Feedback report messages (TVAL53)
Sub–edit Text Type
TVAL53-1 Ambiguous terminology diagnosis code is invalid. Core error
Revision (TVAL53)
Year Description
2008 Edit added: New edit.

TVAL54

Purpose

This edit validates the Date of conclusive diagnosis.

Referenced fields (TVAL54)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T54 8 Date of conclusive diagnosis TDATCONCLUSDIAG
T54.YEAR 4 First 4 digits of T54 (year of date of conclusive diagnosis) Not applicable
T54.MONTH 2 5th and 6th digits of T54 (month of date of conclusive diagnosis) Not applicable
T54.DAY 2 Last 2 digits of T56 (day of date of conclusive diagnosis) Not applicable

Business rules

For Add and Update Tumour records, Date of conclusive diagnosis
  • Must be exclusively composed of numbers: 0 to 9.
  • Must be 8 digits long.
  • If Year or Month or Day is accessioned then the Date of conclusive diagnosis must be accessioned.
  • If Year or Month or Day is not applicable then the Date of conclusive diagnosis must be not applicable.
  • If Year is unknown then Month and Day must be unknown.
  • If Month is unknown then Day must be unknown.
  • If Year and Month are known and Day is unknown then Month must be a valid month.
  • If Year, Month and Day are known then it must be a valid calendar date.
  • Must be between January 1st, 2008 and December 31st of Reference year inclusively.
Edit logic (TVAL54)
Sub–edit Conditions Outcome
TVAL54-1 T5 IN [‘1', ‘2'] AND LENGTH (T54) <> 8 OR NOT IS_COMPOSED_OF (T54, ‘0123456789') Record Rejected
TVAL54-2 T5 IN [‘1', ‘2'] AND LENGTH (T54) = 8 AND IS_COMPOSED_OF (T54, ‘0123456789') AND (T54.YEAR = ‘0000' OR T54.MONTH='00' OR T54.DAY='00') AND (T54.YEAR <> ‘0000' OR T54.MONTH <> ‘00' OR T54.DAY <> ‘00') Record Rejected
TVAL54-3 T5 IN [‘1', ‘2'] AND LENGTH (T54) = 8 AND IS_COMPOSED_OF (T54, ‘0123456789') AND (T54.YEAR = ‘8888' OR T54.MONTH='88' OR T54.DAY='88')  AND (T54.YEAR <> ‘8888' OR T54.MONTH <> ‘88' OR T54.DAY <> ‘88') Record Rejected
TVAL54-4 T5 IN [‘1', ‘2'] AND LENGTH (T54) = 8 AND IS_COMPOSED_OF (T54, ‘0123456789') AND T54.YEAR = ‘9999' AND (T54.MONTH <> ‘99' OR T54.DAY <> ‘99') Record Rejected
TVAL54-5 T5 IN [‘1', ‘2'] AND LENGTH (T54) = 8 AND IS_COMPOSED_OF (T54, ‘0123456789') AND T54.MONTH = ‘99' AND T54.DAY <> ‘99' Record Rejected
TVAL54-6 T5 IN [‘1', ‘2'] AND LENGTH (T54) = 8 AND IS_COMPOSED_OF (T54, ‘0123456789') AND T54.MONTH NOT IN [‘01'-'12', ‘99'] AND T54.DAY = ‘99' Record Rejected
TVAL54-7 T5 IN [‘1', ‘2'] AND LENGTH (T54) = 8 AND IS_COMPOSED_OF (T54, ‘0123456789') AND T54 NOT IN [‘00000000', ‘88888888', ‘99999999'] AND T54.MONTH <> ‘99' AND T54.DAY <> ‘99' AND NOT IS_VALID_DATE Record Rejected
TVAL54-8 T5 IN [‘1', ‘2'] AND T54 NOT IN [‘00000000', ‘88888888', ‘99999999'] AND (T54.YEAR < 2008 OR T54.YEAR > CYCLE_YEAR) Record Rejected
Feedback report messages (TVAL54)
Sub–edit Text Type
TVAL54-1 Date of conclusive diagnosis is not composed of 8 numbers. Core Error
TVAL54-2 Year, month and day must be ‘accessioned'. Core Error
TVAL54-3 Year, month and day must be ‘not applicable'. Core Error
TVAL54-4 Year, month and day must be ‘unknown'. Core Error
TVAL54-5 Date of conclusive diagnosis: month and day must be ‘unknown'. Core Error
TVAL54-6 Date of conclusive diagnosis is not a valid partial date: month is invalid. Core Error
TVAL54-7 Date of conclusive diagnosis is not a valid calendar date. Core Error
TVAL54-8 Date of conclusive diagnosis is out of scope. Core Error
Revision (TVAL54)
Year Description
2008 Edit added: New edit.

TVAL55

Purpose

This edit validates the Type of multiple tumours reported as one primary code.

Referenced fields (TVAL55)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T55 2 Type of multiple tumours reported as one primary TMULTTUMONEPRIM

Business rules

For Add and Update Tumour records, Type of multiple tumours reported as one primary code
  • Must contain a valid code.
Edit logic (TVAL55)
Sub–edit Conditions Outcome
TVAL55-1 T5 IN [‘1', ‘2'] AND T55 IS NOT NULL AND T55 NOT IN [Eligible Type of multiple tumours reported as one primary codes] Record rejected
Feedback report messages (TVAL55)
Sub–edit Text Type
TVAL55-1 Type of multiple tumours reported as one primary code is invalid. Core error
Revision (TVAL55)
Year Description
2008 Edit added: New edit.

TVAL56

Purpose

This edit validates the Date of multiple tumours.

Referenced fields (TVAL56)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T56 8 Date of multiple tumours TDATMULT
T56.YEAR 4 First 4 digits of T56 (year of date of multiple tumours) Not applicable
T56.MONTH 2 5th and 6th digits of T56 (month of date of multiple tumours) Not applicable
T56.DAY 2 Last 2 digits of T56 (day of date of multiple tumours) Not applicable

Business rules

For Add and Update Tumour records, Date of multiple tumours
  • Must be exclusively composed of numbers: 0 to 9.
  • Must be 8 digits long.
  • If Year or Month or Day relates to a single tumour then the Date of multiple tumours must contain all zeros.
  • If Year or Month or Day is not applicable then the Date of multiple tumours must be not applicable.
  • If Year is unknown then Month and Day must be unknown.
  • If Month is unknown then Day must be unknown.
  • If Year and Month are known and Day is unknown then Month must be a valid month.
  • If Year, Month and Day are known then it must be a valid calendar date.
  • Must be between January 1st, 2008 and December 31st of Reference year inclusively.
Edit logic (TVAL56)
Sub–edit Conditions Outcome
TVAL56-1 T5 IN [‘1', ‘2'] AND LENGTH (T56) <> 8 OR NOT IS_COMPOSED_OF (T56, ‘0123456789') Record Rejected
TVAL56-2 T5 IN [‘1', ‘2'] AND LENGTH (T56) = 8 AND IS_COMPOSED_OF (T56, ‘0123456789') AND (T56.YEAR = ‘0000' OR T56.MONTH = ‘00' OR T56.DAY = ‘00') AND (T56.YEAR <> ‘0000' OR T56.MONTH <> ‘00' OR T56.DAY <> ‘00') Record Rejected
TVAL56-3 T5 IN [‘1', ‘2'] AND LENGTH (T56) = 8 AND IS_COMPOSED_OF (T56, ‘0123456789') AND (T56.YEAR = ‘8888' OR T56.MONTH = ‘88' OR T56.DAY = ‘88') AND (T56.YEAR <> ‘8888' OR T56.MONTH <> ‘88' OR T56.DAY <> ‘88') Record Rejected
TVAL56-4 T5 IN [‘1', ‘2'] AND LENGTH (T56) = 8 AND IS_COMPOSED_OF (T56, ‘0123456789') AND T56.YEAR = ‘9999' AND (T56.MONTH <> ‘99' OR T56.DAY <> ‘99') Record Rejected
TVAL56-5 T5 IN [‘1', ‘2'] AND LENGTH (T56) = 8 AND IS_COMPOSED_OF (T56, ‘0123456789') AND T56.MONTH = ‘99' AND T56.DAY <> ‘99' Record Rejected
TVAL56-6 T5 IN [‘1', ‘2'] AND LENGTH (T56) = 8 AND IS_COMPOSED_OF (T56, ‘0123456789') AND T56.MONTH NOT IN [‘01'-'12', ‘99'] AND T56.DAY = ‘99' Record Rejected
TVAL56-7 T5 IN [‘1', ‘2'] AND LENGTH (T56) = 8 AND IS_COMPOSED_OF (T56, ‘0123456789') AND T56 NOT IN [‘00000000', ‘88888888', ‘99999999'] AND T56.MONTH <> ‘99' AND T56.DAY <> ‘99' AND NOT IS_VALID_DATE Record Rejected
TVAL56-8 T5 IN [‘1', ‘2'] AND T56 NOT IN [‘00000000', ‘88888888', ‘99999999'] AND (T56.YEAR < 2008 OR T56.YEAR > CYCLE_YEAR) Record Rejected
Feedback report messages (TVAL56)
Sub–edit Text Type
TVAL56-1 Date of multiple tumours is not composed of 8 numbers. Core Error
TVAL56-2 Year, month and day must relate to a single tumour (all zeros). Core Error
TVAL56-3 Year, month and day must be ‘not applicable'. Core Error
TVAL56-4 Year, month and day must be ‘unknown'. Core Error
TVAL56-5 Date of multiple tumours: month and day must be ‘unknown'. Core Error
TVAL56-6 Date of multiple tumours is not a valid partial date: month is invalid. Core Error
TVAL56-7 Date of multiple tumours is not a valid calendar date. Core Error
TVAL56-8 Date of multiple tumours is out of scope. Core Error
Revision (TVAL56)
Year Description
2008 Edit added: New edit.

TVAL57

Purpose

This edit validates the Multiplicity counter.

Referenced fields (TVAL57)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T57 2 Multiplicity counter TMULTCOUNT

Business rules

For Add and Update Tumour records, Multiplicity counter
  • Must be a numeric value between ‘01' and ‘87', or ‘88' or ‘99'
Edit logic (TVAL57)
Sub–edit Conditions Outcome
TVAL57-1 T5 IN [‘1', ‘2'] AND T57 IS NOT NULL AND T57 NOT IN [Eligible Multiplicity counter codes] Record Rejected
Feedback report messages (TVAL57)
Sub–edit Text Type
TVAL57-1 Multiplicity counter is invalid Core error
Revision (TVAL57)
Year Description
2008 Edit added: New edit.

3.5 Correlation edits

The purpose of the correlation edits is to enforce the business rules between fields on the same Input record. For ease of use, correlation edits have been divided into two groups:

  • Patient correlation edits: enforce business rules between valid patient fields;
  • Tumour correlation edits: enforce business rules between valid tumour fields.

Correlation edits are only performed on Input records where all referenced fields are valid.

3.5.1 Patient correlation edits

The following table summarizes the purpose of each individual edit of this category.

Table 26 Patient correlation edits summary
Edit name Purpose
PCOR1 Ensures that the content of the patient record is consistent with the action described in the Patient record type.
PCOR2 Verifies the likelihood of given names and gender.
PCOR3 Ensures that first given name, second given name and third given name are used coherently.
PCOR4 Ensures that type of current surname code accurately reflects the content of the current surname field.
PCOR5 Ensures that birth surname and current surname are consistent with type of current surname.
PCOR6 Ensures that at least one surname is reported, either the current surname or the birth surname.
PCOR7 Ensures that date of birth and date of death respect a chronological sequence and time frame.
PCOR8 Ensures that death-related variables present a consistent reporting of the patient's vital status.
PCOR9 Ensures that Death registration number and province/territory or country of death are consistent.
PCOR10 Ensures Death registration number and date of death are consistent.
PCOR11 Ensures Death registration number and Underlying cause of death are consistent.

PCOR1

Purpose

This edit ensures that the content of the patient record is consistent with the action described in the patient record type.

Referenced fields (PCOR1)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P3 9 CCR identification number CCR_ID
P4 1 Patient record type PRECTYPE
P5 1 Type of current surname PTYP_CUR
P6 25 Current surname PCURSNAM
P7 15 First given name PGNAME_1
P8 15 Second given name PGNAME_2
P9 7 Third given name PGNAME_3
P10 1 Sex PSEX
P11 8 Date of birth PDATBIR
P12 3 Province/territory or country of birth PPROVBIR
P13 25 Birth surname PBIRNAM
P14 8 Date of death PDATDEA
P15 3 Province/territory or country of death PPROVDEA
P16 6 Death registration number PDEAREG
P17 4 Underlying cause of death PCAUSDEA
P18 1 Autopsy confirming cause of death PAUTOPSY

Business rules

For Add Patient records
  • Patient reporting province/territory, Patient identification number, Type of Current surname, Sex, Date of birth,Province/territory or country of birth, Date of death, Province/territory or country of death, Death registration number, Underlying cause of death and Autopsy confirming cause of death must be provided.
  • CCR identification number must be blank.

For Update Patient records
  • Patient reporting province/territory, Patient identification number, CCR identification number, Type of Current surname, Sex, Date of birth, Province/territory or country of birth, Date of death, Province/territory or country of death, Death registration number, Underlying cause of death and Autopsy confirming cause of death must be provided.

For Delete Patient records

  • Patient reporting Province/territory, Patient identification number, CCR identification number must be provided.
  • Type of Current surname, Current surname, First given name, Second given name, Third given name, Sex, Date of birth, Province/territory or country of birth, Birth surname, Date of death, Province/territory or country of death, Death registration number, Underlying cause of death and Autopsy confirming cause of death must be blank.
Edit logic (PCOR1)
Sub–edit Conditions Outcome
PCOR1-1 P4 = ‘1' AND (P1 IS NULL OR P2 IS NULL OR P3 IS NOT NULL OR P5 IS NULL OR P10 IS NULL OR P11 IS NULL OR P12 IS NULL OR P14 IS NULL OR P15 IS NULL OR P16 IS NULL OR P17 IS NULL OR P18 IS NULL) Record rejected
PCOR1-2 P4 = ‘2' AND (P1 IS NULL OR P2 IS NULL OR P3 IS NULL OR P5 IS NULL OR P10 IS NULL OR P11 IS NULL OR P12 IS NULL OR P14 IS NULL OR P15 IS NULL OR P16 IS NULL OR P17 IS NULL OR P18 IS NULL) Record rejected
PCOR1-3 P4 = ‘3' AND (P1 IS NULL OR P2 IS NULL OR P3 IS NULL OR P5 IS NOT NULL OR P6 IS NOT NULL OR P7 IS NOT NULL OR P8 IS NOT NULL OR P9 IS NOT NULL OR P10 IS NOT NULL OR P11 IS NOT NULL OR P12 IS NOT NULL OR P13 IS NOT NULL OR P14 IS NOT NULL OR P15 IS NOT NULL OR P16 IS NOT NULL OR P17 IS NOT NULL OR P18 IS NOT NULL) Record rejected
Feedback report messages (PCOR1)
Sub–edit Text Type
PCOR1-1 Input record does not respect the Add Patient record format. There are missing or extra values. Core fatal error
PCOR1-2 Input record does not respect the Update Patient record format. There are missing values. Core fatal error
PCOR1-3 Input record does not respect the Delete Patient record format. There are missing or extra values. Core fatal error
Revision (PCOR1)
Year Description
2004 Edit renamed: Current edit was formerly known as Correlation Edit No.1.

PCOR2

Purpose

This edit verifies the likelihood of given names and sex.

Referenced fields (PCOR2)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P7 15 First given name PGNAME_1
P8 15 Second given name PGNAME_2
P9 7 Third given name PGNAME_3
P10 1 Sex PSEX
Other parameters (PCOR2)
Parameters Length Description
NAME_SEX_THRESHOLD 3 Tolerated average likelihood of First given name, Second given name and Third given name to be associated to the opposite gender according to given name and Sex registry2. Value must be between 0 and 100. Default value is 95.

Business rules

For Add and Update Patient records
  • If the average likelihood of First given name, Second given name and Third given name to be associated to the opposite gender according to given name and Sex registry is greater than NAME_SEX_THRESHOLD, then a warning must be sent.
Edit logic (PCOR2)
Sub–edit Conditions Outcome
PCOR2-1 P4 IN [‘1', ‘2'] AND P10 IN ['1', '2'] AND AVERAGE ([Probability of P7 to be associated to opposite gender], [Probability of P8 to be associated to opposite gender], [Probability of P9 to be associated to opposite gender]) > NAME_SEX_THRESHOLD Warning
Feedback report messages (PCOR2)
Sub–edit Text Type
PCOR2-1 Reported given names are not likely for reported Sex. Warning
Revision (PCOR2)
Year Description
2004 Edit removed: Edit formerly known as Correlation Edit No.2 has been removed.
Edit added: Current edit was not documented before.

PCOR3

Purpose

This edit ensures that first given name, second given name and third given name are used coherently.

Referenced fields (PCOR3)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P7 15 First given name PGNAME_1
P8 15 Second given name PGNAME_2
P9 7 Third given name PGNAME_3

Business rules

For Add and Update Patient records
  • If First given name is blank then Second given name and Third given name must be blank.
  • If Second given name is blank then Third given name must be blank.
Edit logic (PCOR3)
Sub–edit Conditions Outcome
PCOR3-1 P4 IN [‘1', ‘2'] AND P7 IS NULL AND (P8 IS NOT NULL OR P9 IS NOT NULL) Record rejected
PCOR3-2 P4 IN [‘1', ‘2'] AND P8 IS NULL AND P9 IS NOT NULL Record rejected
Feedback report messages (PCOR3)
Sub–edit Text Type
PCOR3-1 First given name is missing. Core error
PCOR3-2 Second given name is missing. Core error
Revision (PCOR3)
Year Description
2004 Edit renamed: Current edit was formerly known as Correlation Edit No.3.

PCOR4

Purpose

This edit ensures that type of current surname code accurately reflects the content of the current surname field.

Referenced fields (PCOR4)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P5 1 Type of current surname PTYP_CUR
P6 25 Current surname PCURSNAM

Business rules

For Add and Update Patient records
  • If Type of Current surname is ‘Current Surname unknown' (0) then Current surname must be blank.
  • If Current surname is blank then Type of Current surname must be ‘Current surname unknown' (0).
Edit logic (PCOR4)
Sub–edit Conditions Outcome
PCOR4-1 P4 IN [‘1', ‘2'] AND ((P5 = ‘0' AND P6 IS NOT NULL) OR (P6 IS NULL AND P5 <> ‘0')) Record rejected
Feedback report messages (PCOR4)
Sub–edit Text Type
PCOR4-1 Type of current surname and Current surname do not agree. Core error
Revision (PCOR4)
Year Description
2004 Edit renamed: Current edit was formerly known as Correlation Edit No.4.

PCOR5

Purpose

This edit ensures that birth surname and current surname are consistent with type of current surname.

Referenced fields (PCOR5)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P5 1 Type of Current surname PTYP_CUR
P6 25 Current surname PCURSNAM
P13 25 Birth surname PBIRNAM

Business rules

For Add and Update Patient records
  • If Type of Current surname is ‘Birth surname' then Current surname and Birth surname must be the same.
Edit logic (PCOR5)
Sub–edit Conditions Outcome
PCOR5-1 P4 IN [‘1', ‘2'] AND P5 = ‘1' AND P6 <> P13 Record rejected
Feedback report messages (PCOR5)
Sub–edit Text Type
PCOR5-1 Current surname and Birth surname are different while Type of current surname indicates that they should be the same. Core error
Revision (PCOR5)
Year Description
2004 Edit renamed: Current edit was formerly known as Correlation Edit No.5.

PCOR6

Purpose

This edit ensures that at least one surname is reported, either the current surname or the birth surname.

Referenced fields (PCOR6)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P6 25 Current surname PCURSNAM
P13 25 Birth surname PBIRNAM

Business rules

For Add and Update Patient records
  • Current surname and Birth surname cannot both be blank.
Edit logic (PCOR6)
Sub–edit Conditions Outcome
PCOR6-1 P4 IN [‘1', ‘2'] AND P6 IS NULL AND P13 IS NULL Record rejected
Feedback report messages (PCOR6)
Sub–edit Text Type
PCOR6-1 Current surname and Birth surname cannot both be blank. Core error
Revision (PCOR6)
Year Description
2004 Edit renamed: Current edit was formerly known as Correlation Edit No.6.

PCOR7

Purpose

This edit ensures that date of birth and date of death respect a chronological sequence and time frame.

Referenced fields (PCOR7)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P11 8 Date of birth PDATBIR
P11.YEAR 4 First 4 characters of P11 (year of date of birth) Not applicable
P11.MONTH 2 5th and 6th characters of P11 (month of date of birth) Not applicable
P11.DAY 2 7th and 8th characters of P11 (day of date of birth) Not applicable
P14 8 Date of death PDATDEA
P14.YEAR 4 First 4 characters of P14 (year of date of death) Not applicable
P14.MONTH 2 5th and 6th characters of P14 (month of date of death) Not applicable
P14.DAY 2 7th and 8th characters of P14 (day of date of death) Not applicable
P19 8 Date of transmission PDATTRAN

Business rules

For Add and Update Patient records
  • If Date of birth and Date of death are at least partially known then
    • Date of death must be on or after Date of birth;
    • Year of Date of death and year of Date of birth should not be more than 110 years apart.
  • If Date of birth is at least partially known and the patient is not known to have died then
    • Year of Date of birth and year of Date of transmission should not be more than 110 years apart.
Edit logic (PCOR7)
Sub–edit Conditions Outcome
PCOR7-1 P4 IN [‘1', ‘2'] AND P11 <> ‘99999999' AND P14 NOT IN [‘00000000', ‘99999999'] AND ((P11.DAY <> ‘99' AND P14.DAY <> ‘99' AND P14 < P11) OR (P11.MONTH <> ‘99' AND P14.MONTH <> ‘99' AND P14.YEAR || P14.MONTH < P11.YEAR || P11.MONTH) OR (P14.YEAR < P11.YEAR)) Record rejected
PCOR7-2 P4 IN [‘1', ‘2'] AND P11 <> ‘99999999' AND ((P14 NOT IN [‘00000000', ‘99999999'] AND P14.YEAR – P11.YEAR > 110) OR (P14 = ‘00000000' AND P19.YEAR – P11.YEAR > 110)) Warning
Feedback report messages (PCOR7)
Sub–edit Text Type
PCOR7-1 Date of death is before Date of birth. Core error
PCOR7-2 The patient is more than 110 years old. Warning
Revision (PCOR7)
Year Description
2004 Edit renamed: Current edit was formerly known as Correlation Edit No.7.
Business rules added: Special handling for patients over 110 years old.

PCOR8

Purpose

This edit ensures that death-related variables present a consistent reporting of the patient's vital status.

Referenced fields (PCOR8)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P14 8 Date of death PDATDEA
P15 3 Province/territory or country of death PPROVDEA
P16 6 Death registration number PDEAREG
P17 4 Underlying cause of death PCAUSDEA
P18 1 Autopsy confirming cause of death PAUTOPSY

Business rules

For Add and Update Patient records
  • If any of the death-related variables (Date of death, Province/territory or country of death, Death registration number, Underlying cause of death and Autopsy confirming cause of death) indicate that the patient is deceased then no variables should indicate that the patient is not known to have died.
Edit logic (PCOR8)
Sub–edit Conditions Outcome
PCOR8-1 P4 IN [‘1', ‘2'] AND (P14 <> ‘00000000' OR P15 <> ‘000' OR P16 <> ‘000000' OR P17 <> ‘0000' OR P18 <> ‘0') AND (P14 = ‘00000000' OR P15 = ‘000' OR P16 = ‘000000' OR P17 = ‘0000' OR P18 = ‘0') Record rejected
Feedback report messages (PCOR8)
Sub–edit Text Type
PCOR8-1 Some death-related variables indicate that the patient is deceased whereas at least another indicates that the patient is not known to have died. Core error
Revision (PCOR8)
Year Description
2004 Edit removed: Edit formerly known as Correlation Edit No.8 was redundant with PVAL11.
Edit renamed: Current edit was formerly known as Correlation Edit No.10.

PCOR9

Purpose

This edit ensures that death registration number and province/territory or country of death are consistent.

Referenced fields (PCOR9)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P15 3 Province/territory or country of death PPROVDEA
P16 6 Death registration number PDEAREG

Business rules

For Add and Update Patient records
  • If Death registration number is known then Province/territory or country of death must indicate a specific location in Canada or United States of America.
  • If Death registration number indicated that the Patient died outside Canada then Province/territory or country of death must indicate a foreign country or unknown place.
  • If Death registration number is unknown then Province/territory or country of death must be either a location in Canada or an unknown place.
Edit logic (PCOR9)
Sub–edit Conditions Outcome
PCOR9-1 P4 IN [‘1', ‘2'] AND P16 IN [000001-999997] AND P15 NOT IN [840, 910, 911, 912, 913, 924, 935, 946, 947, 948, 959, 960, 961, 962] Record rejected
PCOR9-2 P4 IN [‘1', ‘2'] AND P16 = ‘999998' AND P15 IN [909, 910, 911, 912, 913, 924, 935, 946, 947, 948, 959, 960, 961, 962] Record rejected
PCOR9-3 P4 IN [‘1', ‘2'] AND P16 = ‘999999' AND P15 NOT IN [909, 910, 911, 912, 913, 924, 935, 946, 947, 948, 959, 960, 961, 962, 999] Record rejected
Feedback report messages (PCOR9)
Sub–edit Text Type
PCOR9-1 If Death registration number is known then province/territory or country of death must indicate a specific location in Canada or United States of America. Core error
PCOR9-2 If Death registration number indicated that the patient died outside Canada then province/territory or country of death must indicate a foreign country or unknown place. Core error
PCOR9-3 If Death registration number is unknown then province/territory or country of death must be either a location in Canada or an unknown place. Core error
Revision (PCOR9)
Year Description
2004 Edit reorganized: Edit formerly known as Correlation Edit No.9 merged with PVAL14.
Edit renamed: Current edit was formerly known as Correlation Edit No.11.
Business rules changed: If Death registration number is known then province/territory or country of death must indicate a specific location in Canada or United States of America; If Death registration number is unknown then province/territory or country of death must be either a location in Canada or an unknown place.
Business rules added: If Death registration number indicated that the patient died outside Canada then province/territory or country of death must indicate a foreign country or unknown place.

PCOR10

Purpose

This edit ensures death registration number and date of death are consistent.

Referenced fields (PCOR10)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P14 8 Date of death PDATDEA
P16 6 Death registration number PDEAREG

Business rules

For Add and Update Patient records
  • If Death registration number is known then Date of death must be at least partially known.
Edit logic (PCOR10)
Sub–edit Conditions Outcome
PCOR10-1 P4 IN [‘1', ‘2'] AND P16 IN [000001-999997] AND P14.YEAR = ‘9999' Record rejected
Feedback report messages (PCOR10)
Sub–edit Text Type
PCOR10-1 Date of death cannot be unknown if Death registration number is known. Core error
Revision (PCOR10)
Year Description
2004 Edit reorganized: Edit formerly known as Correlation Edit No.10 moved to PCOR8.
Edit added: New edit.

PCOR11

Purpose

This edit ensures death registration number and underlying cause of death are consistent.

Referenced fields (PCOR11)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P16 6 Death registration number PDEAREG
P17 3 Underlying cause of death PCAUSDEA

Business rules

For Add and Update Patient records
  • If Death registration number is unknown then Underlying cause of death cannot be ‘Officially unknown'.
Edit logic (PCOR11)
Sub–edit Conditions Outcome
PCOR11-1 P4 IN [‘1', ‘2'] AND P16 = ‘999999' AND P17 IN = [‘R99', ‘7999'] Record rejected
Feedback report messages (PCOR11)
Sub–edit Text Type
PCOR11-1 Underlying cause of death cannot be ‘Officially unknown' when Death registration is unknown. Core error
Revision (PCOR11)
Year Description
2004 Edit reorganized: Edit formerly known as Correlation Edit No.11 moved to PCOR9.
Edit added: New edit.

3.5.2 Tumour correlation edits

The following table summarizes the purpose of each individual edit of this category.

Table 27 Tumour correlation edits summary
Edit name Purpose
TCOR1 Ensures that the content of the core tumour fields is consistent with the operation described in the Tumour record type.
TCOR2 Ensures that Postal code and Standard geographic code are coherent.
TCOR3 Ensures that Census tract and Standard geographic code are coherent.
TCOR4 Rejects tumour data for patients living outside the reporting province/territory at time of diagnosis.
TCOR5 Ensures that expected topography, histology and behaviour values are reported based on the Source classification flag.
TCOR6 Ensures the consistency between ICD-9 Cancer code and related ICD-O-2 values.
TCOR7 Ensures the consistency between related ICD-O-2 and ICD-O-3 values.
TCOR8 Not applicable. (Placeholder for future requirement implementation.)
TCOR9 Rejects tumour records that are outside the CCR core scope.
TCOR10 Ensures that invalid combinations of topography and histology are rejected.
TCOR11 Ensures that invalid combinations of histology and behaviour codes are rejected.
TCOR12 Ensures the consistency between the topography and the laterality.
TCOR13 Ensures that invalid combinations of Method used to establish the date of diagnosis and Diagnostic confirmation codes are rejected.
TCOR14 Ensures that Method of diagnosis is only reported for tumours diagnosed prior to 2004.
TCOR15 Ensures that Method used to establish the date of diagnosis is only reported for tumours diagnosed in 2004 and onwards.
TCOR16 Ensures that Diagnostic confirmation is only reported for tumours diagnosed in 2004 and onwards.
TCOR17 Ensures that Grade, differentiation or cell indicator is only reported for tumours diagnosed in 2004 and onwards.
TCOR18 This edit ensures that Collaborative Staging variables are reported for tumours within the CCR collaborative staging scope.
TCOR19 This edit ensures that AJCC TNM staging variables are reported for tumours within the CCR AJCC TNM staging scope.
TCOR20 Ensures that TNM stage group is reported only when clinical and pathologic TNM stage group are not reported.
TCOR21 Ensures that the combination of AJCC clinical TNM stage group and individual clinical T, N, M values is acceptable.
TCOR22 Ensures that the combination of AJCC pathologic TNM stage group and the individual pathologic T, N, M values is acceptable.
TCOR23 Ensures that the combination of AJCC TNM stage group and the individual clinical/pathologic T, N, M values is acceptable.
TCOR24 Ensures that AJCC edition number is coherent with all remaining AJCC TNM staging variables.
TCOR26 Ensures the consistency between Ambiguous terminology diagnosis and Date of conclusive diagnosis.
TCOR27 Ensures the consistency between Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter.
TCOR29 Ensures the consistency between Ambiguous terminology diagnosis and Date of Conclusive Diagnosis.
TCOR30 Ensures that date of diagnosis and date of conclusive diagnosis respect a chronological sequence and time frame.
TCOR31 Ensures the consistency between ICD-O-2/3 Topography and Type of multiple tumours reported as one primary.
TCOR32 Ensures the consistency between ICD-O-3 Behaviour and Multiple tumours reported as one primary.
TCOR33 Ensures the consistency between Type of Multiple Tumours Reported as One Primary,  ICD-O-2/3 Topography and ICD-O-3 Histology.
TCOR34 Ensures the consistency between Date of multiple tumours and Type of multiple tumours reported as one primary.
TCOR35 Ensures the consistency between Method Used to Establish the Date of Diagnosis, Type of Multiple Tumours Reported as One Primary, Date of Multiple Tumours and Multiplicity Counter.

TCOR1

Purpose

This edit ensures that the content of the core tumour fields is consistent with the operation described in the tumour record type.

Referenced fields (TCOR1)
Field Length Description Acronym
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Tumour patient identification number TPIN
T3 9 Tumour reference number TTRN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
T6 25 Name of place of residence TPLACRES
T7 6 Postal code TPOSTCOD
T8 7 Standard geographic code TCODPLAC
T9 9 Census tract TCENTRAC
T10 15 Health insurance number THIN
T11 1 Method of diagnosis TMETHDIAG
T12 8 Date of diagnosis TDATDIAG
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T13 4 ICD-9 cancer code TICD_9
T14 1 Source classification flag TSCF
T15 4 ICD-O-2/3 Topography TICD_O2T
T16 4 ICD-O-2 Histology TICD_O2H
T17 1 ICD-O-2 Behaviour TICD_O2B
T19 1 Laterality TLATERAL
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T23 1 Grade, differentiation or cell indicator TGRADE
T24 1 Method used to establish the date of diagnosis TMETHUSED
T25 1 Diagnostic confirmation TMETHCONF
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T42 9 AJCC clinical T TAJCCCLINT
T43 3 AJCC clinical N TAJCCCLINN
T44 3 AJCC clinical M TAJCCCLINM
T45 9 AJCC pathologic T TAJCCPATHT
T46 3 AJCC pathologic N TAJCCPATHN
T47 3 AJCC pathologic M TAJCCPATHM
T48 4 AJCC clinical TNM stage group TAJCCCLINSG
T49 4 AJCC pathologic TNM stage group TAJCCPATHSG
T50 4 AJCC TNM stage group TAJCCSG
T51 2 AJCC edition number TAJCCEDNUM
T52 6 CS Version 1st TCSFVER
T53 1 Ambiguous Terminology Diagnosis TAMBIGTERM
T54 8 Date of Conclusive Diagnosis TDATCONCLUSDIAG
T55 2 Type of Multiple Tumours Reported as One Primary TMULTTUMONEPRIM
T56 8 Date of Multiple Tumours TDATMULT
T57 2 Multiplicity Counter TMULTCOUNT

Business rules

For Add Tumour records
  • Tumour reporting province/territory, Tumour patient identification number, Tumour reference number, Postal code, Standard geographic code, Method of diagnosis, Date of diagnosis, ICD-9 cancer code, Source classification flag, ICD-O-2/3 Topography, ICD-O-2 Histology, ICD-O-2 Behaviour, Laterality, ICD-O-3 Histology, ICD-O-3 Behaviour, Grade, differentiation or cell indicator, Method used to establish the date of diagnosis, Diagnostic confirmation must be provided39.
  • Fillers (T18 and T20) are ignored.
For Update Tumour records
  • Tumour reporting province/territory, Tumour patient identification number, Tumour reference number, CCR identification number, Postal code, Standard geographic code, Method of diagnosis, Date of diagnosis, ICD-9 cancer code, Source classification flag, ICD-O-2/3 Topography, ICD-O-2 Histology, ICD-O-2 Behaviour, Laterality, ICD-O-3 Histology, ICD-O-3 Behaviour, Grade, differentiation or cell indicator, Method used to establish the date of diagnosis, Diagnostic confirmation must be provided39.
  • Fillers (T18 and T20) are ignored.
For Delete Tumour records
  • Tumour reporting province/territory, Tumour patient identification number, Tumour reference number and CCR identification number must be provided.
  • Name of place of residence, Postal code, Standard geographic code, Census tract, Health insurance number, Method of diagnosis, Date of diagnosis, ICD-9 cancer code, Source classification flag, ICD-O-2/3 Topography, ICD-O-2 Histology, ICD-O-2 Behaviour, Laterality, ICD-O-3 Histology, ICD-O-3 Behaviour, Grade, differentiation or cell indicator, Method used to establish the date of diagnosis, Diagnostic confirmation, CS tumour size, CS extension, CS tumour size/ext eval, CS lymph nodes, CS reg nodes eval, Regional nodes examined, Regional nodes positive, CS mets at dx, CS mets eval, CS site-specific factor 1, CS site-specific factor 2, CS site-specific factor 3, CS site-specific factor 4, CS site-specific factor 5, CS site-specific factor 6, AJCC clinical T, AJCC clinical N, AJCC clinical M, AJCC pathologic T, AJCC pathologic N, AJCC pathologic M, AJCC clinical TNM stage group, AJCC pathologic TNM stage group, AJCC TNM stage group, AJCC edition number, CS Version 1st, Ambiguous Terminology Diagnosis, Date of conclusive diagnosis, Type of multiple tumours reported as one primary, Date of multiple tumours, and Multiplicity Counter must be blank.
  • Fillers (T18 and T20) are ignored.
Edit logic (TCOR1)
Sub–edit Conditions Outcome
TCOR1-1 T5 = ‘1' AND (T1 IS NULL OR T2 IS NULL OR T3 IS NULL OR T7 IS NULL OR T8 IS NULL OR T11 IS NULL OR T12 IS NULL OR T13 IS NULL OR T14 IS NULL OR T15 IS NULL OR T16 IS NULL OR T17 IS NULL OR T19 IS NULL OR T21 IS NULL OR T22 IS NULL OR T23 IS NULL OR T24 IS NULL OR T25 IS NULL) OR (T12 IS NOT NULL AND T12.YEAR < 2006 AND T9 IS NULL)) Record rejected
TCOR1-2 T5 = ‘2' AND (T1 IS NULL OR T2 IS NULL OR T3 IS NULL OR T4 IS NULL OR T7 IS NULL OR T8 IS NULL OR T11 IS NULL OR T12 IS NULL OR T13 IS NULL OR T14 IS NULL OR T15 IS NULL OR T16 IS NULL OR T17 IS NULL OR T19 IS NULL OR T21 IS NULL OR T22 IS NULL OR T23 IS NULL OR T24 IS NULL OR T25 IS NULL) OR (T12 IS NOT NULL AND T12.YEAR < 2006 AND T9 IS NULL) Record rejected
TCOR1-3 T5 = ‘3' AND (T1 IS NULL OR T2 IS NULL OR T3 IS NULL OR T4 IS NULL OR T6 IS NOT NULL OR T7 IS NOT NULL OR T8 IS NOT NULL OR T9 IS NOT NULL OR T10 IS NOT NULL OR T11 IS NOT NULL OR T12 IS NOT NULL OR T13 IS NOT NULL OR T14 IS NOT NULL OR T15 IS NOT NULL OR T16 IS NOT NULL OR T17 IS NOT NULL OR T19 IS NOT NULL OR T21 IS NOT NULL OR T22 IS NOT NULL OR T23 IS NOT NULL OR T24 IS NOT NULL OR T25 IS NOT NULL OR T27 IS NOT NULL OR T28 IS NOT NULL OR T29 IS NOT NULL OR T30 IS NOT NULL OR T31 IS NOT NULL OR T32 IS NOT NULL OR T33 IS NOT NULL OR T34 IS NOT NULL OR T35 IS NOT NULL OR T36 IS NOT NULL OR T37 IS NOT NULL OR T38 IS NOT NULL OR T39 IS NOT NULL OR T40 IS NOT NULL OR T41 IS NOT NULL OR T42 IS NOT NULL OR T43 IS NOT NULL OR T44 IS NOT NULL OR T45 IS NOT NULL OR T46 IS NOT NULL OR T47 IS NOT NULL OR T48 IS NOT NULL OR T49 IS NOT NULL OR T50 IS NOT NULL OR T51 IS NOT NULL OR T52 IS NOT NULL OR T53 IS NOT NULL OR T54 IS NOT NULL OR T55 IS NOT NULL OR T56 IS NOT NULL OR T57 IS NOT NULL) Record rejected
Feedback report messages (TCOR1)
Sub–edit Text Type
TCOR1-1 Input record does not respect the Add Tumour record format. There are missing values. Core fatal error
TCOR1-2 Input record does not respect the Update Tumour record format. There are missing values. Core fatal error
TCOR1-3 Input record does not respect the Delete Tumour record format. There are missing or extra values. Core fatal error
Revision (TCOR1)
Year Description
2008 Business rules and Edit logic changed: Fields T53 to T57 have been added.
2007 Business rules and Edit logic changed: Field T52 has been added.
2006 Business rules and Edit logic changed: Census tract effective date range ended in 2005. For cases diagnosed in 2006 and onwards, T9 (Census tract) must not be reported.
2004 Edit renamed: Edit formerly known as Correlation Edit No.12.
Business rules changed: Handle new fields related to Collaborative staging and TNM data.

TCOR2

Purpose

This edit ensures that postal code and standard geographic code are coherent.

Referenced fields (TCOR2)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T7 6 Postal code TPOSTCOD
T7.FIRST 1 First digit of Postal code Not applicable
T8.PROV 2 First 2 digits of T8 (province code of Standard geographic code) Not applicable

Business rules

For Add and Update Tumour records, if Postal code is known then
  • it must start with ‘A' if in Newfoundland or Labrador;
  • it must start with ‘B' if in Nova Scotia;
  • it must start with ‘C' if in Prince Edward Island;
  • it must start with ‘E' if in New Brunswick;
  • it must start with ‘G', ‘H', ‘J' or ‘K' if in Quebec;
  • it must start with ‘K', ‘L', 'M', ‘N' or ‘P' if in Ontario;
  • it must start with ‘R' if in Manitoba;
  • it must start with ‘R' or ‘S' if in Saskatchewan;
  • it must start with ‘S' or ‘T' if in Alberta;
  • it must start with ‘V' if in British Columbia;
  • it must start with ‘Y' if in Yukon;
  • it must start with ‘X' if in Northwest Territories;
  • it must start with ‘X' if in Nunavut.
Edit logic (TCOR2)
Sub–edit Conditions Outcome
TCOR2-1 T5 IN [‘1', ‘2'] AND T7 <> ‘999999' AND ((T8.PROV = ‘10' AND T7.FIRST <> ‘A') OR (T8.PROV = ‘11' AND T7.FIRST <> ‘C') OR (T8.PROV = ‘12' AND T7.FIRST <> ‘B') OR (T8.PROV = ‘13' AND T7.FIRST <> ‘E') OR (T8.PROV = ‘24' AND T7.FIRST NOT IN [‘G', ‘H', ‘J', ‘K']) OR (T8.PROV = ‘35' AND T7.FIRST NOT IN [‘K', ‘L', ‘M', ‘N', ‘P']) OR (T8.PROV = ‘46' AND T7.FIRST <> ‘R') OR (T8.PROV = ‘47' AND T7.FIRST NOT IN [‘R', ‘S']) OR (T8.PROV = ‘48' AND T7.FIRST NOT IN [‘S', ‘T']) OR (T8.PROV = ‘59' AND T7.FIRST <> ‘V') OR (T8.PROV = ‘60' AND T7.FIRST <> ‘Y') OR (T8.PROV = ‘61' AND T7.FIRST <> ‘X') OR (T8.PROV = ‘62' AND T7.FIRST <> ‘X')) Record rejected
Feedback report messages (TCOR2)
Sub–edit Text Type
TCOR2-1 Postal code and Standard geographic code indicate 2 different provinces/territories. Core error
Revision (TCOR2)
Year Description
2004 Edit renamed: Edit formerly known as Correlation Edit No.14.

TCOR3

Purpose

This edit ensures that census tract and standard geographic code are coherent.

Referenced fields (TCOR3)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T8 7 Standard geographic code TCODPLAC
T9 9 Census tract TCENTRAC
T12.YEAR 4 First 4 characters of T12 (year of the Date of diagnosis) Not applicable

Business rules

For Add and Update Tumour records
  • If Date of diagnosis is between year 1992 and 1995 inclusively, and both Census tract and Standard geographic code are fully known, then the reported Standard geographic code must match the Standard geographic code associated with the Census tract in Eligible Census tracts from 1992 to 199512 .
  • If Date of diagnosis is between year 1996 and 2000 inclusively, and both Census tract and Standard geographic code are fully known, then the reported Standard geographic code must match the Standard geographic code associated with the Census tract in Eligible Census tracts from 1996 to 200012.
  • If Date of diagnosis is between year 2001 and 2005 inclusively, and both Census tract and Standard geographic code are fully known, then the reported Standard geographic code must match the Standard geographic code associated with the Census tract in Eligible Census tracts from 2001 to 200512.
Edit logic (TCOR3)
Sub–edit Conditions Outcome
TCOR3-1 T5 IN [‘1', ‘2'] AND T8 NOT LIKE ‘_ _ _ _ 999' AND T9 NOT LIKE ‘___999.99' AND T12.YEAR >= 1992 AND T12.YEAR < 1996 AND T8 NOT IN [SGC from Eligible Census tracts from 1992 to 1995 where Census tract = T9] Record rejected
TCOR3-2 T5 IN [‘1', ‘2'] AND T8 NOT LIKE ‘_ _ _ _ 999' AND T9 NOT LIKE ‘___999.99' AND T12.YEAR >= 1996 AND T12.YEAR < 2001 AND T8 NOT IN [SGC from Eligible Census tracts from 1996 to 2000 where Census tract = T9] Record rejected
TCOR3-3 T5 IN [‘1', ‘2'] AND T8 NOT LIKE ‘_ _ _ _ 999' AND T9 NOT LIKE ‘___999.99' AND T12.YEAR >= 2001 AND T12.YEAR < 2005 AND T8 NOT IN [SGC from Eligible Census tracts from 2001 to 2005 where Census tract = T9] Record rejected
Feedback report messages (TCOR3)
Sub–edit Text Type
TCOR3-1 Census tract and Standard geographic code combination not found in Census tract Data dictionary – 1991. Core error
TCOR3-2 Census tract and Standard geographic code combination not found in Census tract Data dictionary – 1996. Core error
TCOR3-3 Census tract and Standard geographic code combination not found in Census tract Data dictionary – 2001. Core error
Revision (TCOR3)
Year Description
2006 Business rules and Edit logic changed: Edit modified to include combinations where Census tract indicate an area outside a Census Metropolitan Area.
2004 Edit renamed: Edit formerly known as Correlation Edit No.15

TCOR4

Purpose

This edit rejects tumour data for patients living outside the reporting province/territory at time of diagnosis.

Referenced fields (TCOR4)
Field Length Description Acronym
T1 2 Tumour reporting province/territory TREPPROV
T5 1 Tumour record type TRECTYPE
T8.PROV 2 First 2 characters from T8 (province code of Standard geographic code) Not applicable

Business rules

For Add and Update Tumour records
  • Tumour reporting province/territory must be equal to province code found in Standard geographic code.
Edit logic (TCOR4)
Sub–edit Conditions Outcome
TCOR4-1 T5 IN [‘1', ‘2'] AND T1 <> T8.PROV Record rejected
Feedback report messages (TCOR4)
Sub–edit Text Type
TCOR4-1 Reporting province/territory and Standard geographic code must indicate the same province/territory. Core error
Revision (TCOR4)
Year Description
2004 Edit renamed: Edit formerly known as Correlation Edit No.16.

TCOR5

Purpose

This edit ensures that expected topography, histology and behaviour values are reported based on the Source classification flag.

Referenced fields (TCOR5)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T13 4 ICD-9 cancer code TICD_9
T14 1 Source classification flag TSCF
T16 4 ICD-O-2 Histology TICD_O2H
T17 1 ICD-O-2 Behaviour TICD_O2B

Business rules

For Add and Update Tumour records
  • If Source classification Flag indicates that ICD-9 is the Source classification then ICD-9 cancer code, ICD-O-2/3 Topography40, ICD-O-2 Histology, ICD-O-2 Behaviour41, ICD-O-3 Histology42 and ICD-O-3 Behaviour41 must be reported.
  • If Source classification flag indicates that ICD-O-2 is the Source classification then ICD-O-2/3 Topography40, ICD–O–2 Histology, ICD-O-2 Behaviour41, ICD-O-3 Histology42 and ICD-O-3 Behaviour41 must be reported and ICD-9 Cancer code must not be reported.
  • If Source classification flag indicates that ICD-O-3 is the Source classification then ICD-O-2/3 Topography42, ICD-O-3 Histology40 and ICD-O-3 Behaviour41 must be reported and ICD-9 cancer code, ICD-O-2 Histology and ICD-O-2 Behaviour must not be reported.
Edit logic (TCOR5)
Sub–edit Conditions Outcome
TCOR5-1 T5 IN [‘1', ‘2'] AND T14 = ‘1' AND (T13 = ‘0000' OR T16 = ‘0000') Record rejected
TCOR5-2 T5 IN [‘1', ‘2'] AND T14 = ‘2' AND T16 = ‘0000' Record rejected
TCOR5-3 T5 IN [‘1', ‘2'] AND T14 = ‘2' AND T13 <> ‘0000' Record rejected
TCOR5-4 T5 IN [‘1', ‘2'] AND T14 = ‘4' AND (T13 <> '0000' OR T16 <> ‘0000' OR T17 <> ‘0') Record rejected
Feedback report messages (TCOR5)
Sub–edit Text Type
TCOR5-1 Based on the Source classification flag, ICD-9 Cancer code and ICD-O-2 Histology must be reported. Core Error
TCOR5-2 Based on the Source classification flag, ICD-O-2 Histology must be reported. Core Error
TCOR5-3 Based on the Source classification flag, ICD-9 Cancer code must not be reported. Core Error
TCOR5-4 Based on the Source classification flag, ICD-9 cancer code, ICD-O-2 Histology and ICD-O-2 Behaviour must not be reported. Core Error
Revision (TCOR5)
Year Description
2004 Edit renamed: Edit formerly known as Correlation Edit No.18.
Business rules deleted: ICD-10 related rules dropped.
Business rules changed: Ensure that topography and histology are reported in accordance with the Source classification flag.
Business rules added: Prevent the reporting of data using a classification older than the one indicated by the Source classification flag.

TCOR6

Purpose

This edit ensures the consistency between ICD-9 Cancer code and related ICD-O-2 values.

Referenced fields (TCOR6)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T13 4 ICD-9 cancer code TICD_9
T14 1 Source classification flag TSCF
T15 4 ICD-O-2/3 Topography TICD_O2T
T16 4 ICD-O-2 Histology TICD_O2H
T17 1 ICD-O-2 Behaviour TICD_O2B

Business rules

For Add and Update Tumour records where the source classification is ICD-9
  • ICD-9 Cancer code and ICD-O-2/3 Topography must match based on ICD-9 to ICD-O-2 conversion table43.
  • If ICD-9 Cancer code is related to a specific histology code (different than 8000) based on ICD-9 to ICD-O-2 conversion table then reported ICD-O-2 Histology should not be generic (equal to 8000).
  • ICD-9 Cancer code and ICD-O-2 Behaviour must be coherent based on ICD-9 to ICD-O-2 conversion table.
Edit logic (TCOR6)
Sub–edit Conditions Outcome
TCOR6-1 T5 IN [‘1', ‘2'] AND T14 = '1' AND T13 <> '0000' AND (T13 and T15 NOT IN [ICD-9 to ICD-O-2 conversion table]) Record Rejected
TCOR6-2 T5 IN [‘1', ‘2'] AND T14 = '1' AND T13 <> '0000' AND T16 = '8000' AND (ICD-O-2 Histology <> '8000' IN [ICD-9 to ICD-O-2 conversion table where ICD-9 = T13]) Warning
TCOR6-3 T5 IN [‘1', ‘2'] AND T14 = '1' AND T13 <> '0000' AND (T13 and T17 NOT IN [ICD-9 to ICD-O-2 conversion table]) Record Rejected
Feedback report messages (TCOR6)
Sub–edit Text Type
TCOR6-1 ICD-9 Cancer code and ICD-O-2/3 Topography are not coherent. Core Error
TCOR6-2 ICD-O-2 Histology could have been more precise based on ICD-9 cancer code. Warning
TCOR6-3 ICD-9 Cancer code and ICD-O-2 Behaviour are not coherent. Core Error
Revision (TCOR6)
Year Description
2004 Edit renamed: Edit formerly known as Correlation Edit No.20
Business rules deleted: ICD-10 related rules dropped.
Business rules added:
Coherence check between ICD-9 Cancer code and ICD-O2/3 Topography added.
Coherence check between ICD-9 Cancer code and ICD-O-2 Histology added.

TCOR7

Purpose

This edit ensures the consistency between related ICD-O-2 and ICD-O-3 values.

Referenced fields (TCOR7)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T14 1 Source classification flag TSCF
T15 4 ICD-O-2/3 Topography TICD_O2T
T16 4 ICD-O-2 Histology TICD_O2H
T17 1 ICD-O-2 Behaviour TICD_O2B
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B

Business rules

For Add and Update Tumour records where the source classification is either ICD-9 or ICD-O-2
  • ICD-O-3 Histology and ICD-O-3 Behaviour combination must be consistent with ICD-O-2/3 Topography, ICD-O-2 Histology and ICD-O-2 Behaviour combination based on ICD-O-2 to ICD-O-3 conversion table44.
Edit logic (TCOR7)
Sub–edit Conditions Outcome
TCOR7-1 T5 IN [‘1', ‘2'] AND T14 IN [‘1', '2'] AND T16 <> '0000' AND (T21 and T22 combination NOT IN [ICD-O-2 to ICD-O-3 conversion table for T15, T16 and T17 combination]) Record rejected
Feedback report messages (TCOR7)
Sub–edit Text Type
TCOR7-1 ICD-O-3 Histology and ICD-O-3 Behaviour combination is not coherent with ICD-O-2/3 Topography, ICD-O-2 Histology and ICD-O-2 Behaviour combination. Core Error
Revision (TCOR7)
Year Description
2004 Edit added: New edit.

TCOR8

Purpose

Not applicable. (This empty correlation is kept as a placeholder for future requirement implementation.)

Referenced fields (TCOR8)
Field Length Description Acronym
Not applicable Not applicable Not applicable Not applicable

Business rules

Not applicable

Edit logic (TCOR8)
Sub–edit Conditions Outcome
Not applicable Not applicable Not applicable
Feedback report messages (TCOR8)
Sub–edit Text Type
Not applicable Not applicable Not applicable
Revision (TCOR8)
Year Description
Not applicable Not applicable

TCOR9

Purpose

This edit rejects tumour records that are outside the CCR core scope.

Referenced fields (TCOR9)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of Date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B

Business rules

For Add and Update Tumour records
  • ICD-O-2/3 Topography, ICD-O-3 Histology, ICD-O-3 Behaviour and year of Date of diagnosis combination must be within the CCR core scope45.
Edit logic (TCOR9)
Sub–edit Conditions Outcome
TCOR9-1 T5 IN [‘1', ‘2'] AND (T12.YEAR, T15, T21 and T22 NOT IN [CCR core scope]) Record rejected
Feedback report messages (TCOR9)
Sub–edit Text Type
TCOR9-1 Based on ICD-O-2/3 Topography, ICD-O-3 Histology and Behaviour and Date of diagnosis, the tumour is outside the CCR core scope. Core Error
Revision (TCOR9)
Year Description
2004 Edit consolidated: Edits formerly known as Correlation edit No.13 and Correlation edit No.21.
Business rules changed: Verification is now performed on ICD-O-3 values only, regardless of the source classification used.

TCOR10

Purpose

This edit ensures that invalid combinations of topography and histology are rejected.

Referenced fields (TCOR10)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of Date of diagnosis (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H

Business rules

For Add and Update Tumour records
  • ICD-O-2/3 Topography and ICD-O-3 Histology and year of date of diagnosis combination must not be invalid based on Invalid site and Histology combinations table46.
Edit logic (TCOR10)
Sub–edit Conditions Outcome
TCOR10-1 T5 IN [‘1', ‘2'] AND (T12.Year, T15 and T21 IN [Invalid site and Histology combinations]) Record rejected
Feedback report messages (TCOR10)
Sub–edit Text Type
TCOR10-1 ICD-O-2/3 Topography, ICD-O-3 Histology and Date of diagnosis combination is either invalid or not eligible for CCR. Core error
Revision (TCOR10)
Year Description
2007 Referenced fields, Business rules, Edit logic and Feedback report messages changed: Verification now includes Date of diagnosis.
2004 Edit renamed: Edit formerly known as Correlation Edit No.23.
Business rules changed: Verification is now performed on ICD-O-3 values only, regardless of the source classification used.

TCOR11

Purpose

This edit ensures that invalid combinations of histology and behaviour codes are rejected.

Note: Invalid combinations are combinations that are invalid from a subject matter point of view. These are different from matrix combinations which are combinations not explicitly listed in ICD-O but possible from a subject matter point of view and allowed based on rules or coding guidelines for morphology, ICD-O-3 (page 29).

Referenced fields (TCOR11)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of Date of diagnosis (year of date of diagnosis) Not applicable
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B

Business rules

For Add and Update Tumour records
  • ICD-O-3 Histology, ICD-O-3 Behaviour and year of date of diagnosis combination must not be invalid based on Invalid Histology and Behaviour combination table47.
Edit logic (TCOR11)
Sub–edit Conditions Outcome
TCOR11-1 T5 IN [‘1', ‘2'] AND (T12.YEAR, T21 and T22 IN [Invalid Histology and Behaviour combination]) Record rejected
Feedback report messages (TCOR11)
Sub–edit Text Type
TCOR11-1 ICD-O-3 Histology, ICD-O-3 Behaviour and Date of diagnosis combination is invalid. Core error
Revision (TCOR11)
Year Description
2007 Referenced fields, Business rules, Edit logic and Feedback report messages changed: Verification now includes Date of diagnosis.
2004 Edit renamed: Edit formerly known as Correlation Edit No.24.
Business rules changed: Verification is now performed on ICD-O-3 values only, regardless of the source classification used.

TCOR12

Purpose

This edit ensures the consistency between the topography and the laterality.

Referenced fields (TCOR12)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of Date of diagnosis (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T19 1 Laterality TLATERAL

Business rules

For Add and Update Tumour records
  • ICD-O-2/3 Topography, Laterality and year of date of diagnosis combination must be valid based on Valid site and Laterality combinations table48.
Edit logic (TCOR12)
Sub–edit Conditions Outcome
TCOR12-1 T5 IN [‘1', ‘2'] AND (T12.Year, T15 and T19 NOT IN [Valid site and Laterality combinations table]) Record rejected
Feedback report messages (TCOR12)
Sub–edit Text Type
TCOR12-1 ICD-O-2/3 Topography, Laterality and Date of diagnosis combination is invalid. Core error
Revision (TCOR12)
Year Description
2004 Edit renamed: Edit formerly known as Correlation Edit No.22.
Business rules changed: Verification is now performed on ICD-O-3 values only, regardless of the source classification used.

TCOR13

Purpose

This edit ensures that invalid combinations of Method used to establish the date of diagnosis and Diagnostic confirmation codes are rejected.

Referenced fields (TCOR13)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of Date of Diagnosis (year of Date of Diagnosis) N/A
T24 1 Method used to establish the date of diagnosis TMETHUSED
T25 1 Diagnostic confirmation TMETHCONF
T53 1 Ambiguous Terminology Diagnosis TAMBIGTERM

Business rules

For Add and Update Tumour records where the Date of Diagnosis is in 2004 or after
  • Diagnostic confirmation cannot be less definitive than Method used to establish the date of diagnosis. Example: Diagnostic confirmation cannot be “positive cytology” if the Method used to establish the Date of Diagnosis is “positive histology”.
  • Method used to establish the date of diagnosis and Diagnostic confirmation must indicate the same value when either is "Autopsy Only" or "Death Certificate Only (DCO)" and the other one is reported.

For Add and Update Tumour records where the Date of Diagnosis is in 2008 or after

  • If Ambiguous Terminology Diagnosis is Ambiguous terminology only (1) then
    • Diagnostic Confirmation must be more definitive than Method used to establish date of diagnosis.
Edit logic (TCOR13)
Sub–edit Conditions Outcome
TCOR13-1 T5 IN ['1', '2'] AND (T12.YEAR>= '2008') AND T53 = ‘1' AND T24 IN ['1','2','4','5','6','7', ‘9'] AND T25 IN ['1','2','4','5','6','7', ‘9'] AND ((T24='2' AND T25='2') OR (T24<T25)) Record rejected
TCOR13-2 T5 IN ['1', '2'] AND (T12.YEAR>= '2004' ) AND T24 IN ['1','2','4','5','6','7', ‘9'] AND T25 IN ['1','2','4','5','6','7', ‘9'] AND ((T24='2' AND T25='2') OR (T24<T25 AND NOT (T24='1' and T25='2'))) Record rejected
TCOR13-3 T5 IN [‘1', ‘2'] AND T12.YEAR>= '2004' AND ((T24 IN ['3', '8'] AND T25<>'0') OR (T25 IN ['3', '8'] AND T24<>'0')) AND T24 <> T25) Record rejected
Feedback report messasges (TCOR13)
Sub–edit Text Type
TCOR13-1 Diagnostic confirmation must be more definitive than Method used to establish the date of diagnosis when Ambiguous terminology is equal to 1. Core error
TCOR13-2 Diagnostic confirmation cannot be less definitive than Method used to establish the date of diagnosis. Core error
TCOR13-3 Method Used to Establish the Date of Diagnosis and Diagnostic Confirmation must indicate the same method when either is "Autopsy Only" or "Death Certificate Only (DCO)". Core error
Revision (TCOR13)
Year Description
2008 New Sub-edit added: To make Diagnostic confirmation more definitive than Method used to establish the date of diagnosis.
2007 New edit added.

TCOR14

Purpose

This edit ensures that method of diagnosis is only reported for tumours diagnosed prior to 2004.

Referenced fields (TCOR14)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T11 1 Method of diagnosis TMETHDIAG
T12.YEAR 4 First 4 digits of Date of diagnosis (year of date of diagnosis) Not applicable

Business rules

For Add and Update Tumour records
  • Method of diagnosis must only be reported when Date of diagnosis is prior 2004.
Edit logic (TCOR14)
Sub–edit Conditions Outcome
TCOR14-1 T5 IN [‘1', ‘2'] AND T12.YEAR < 2004 AND T11 = ‘0' Record rejected
TCOR14-2 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2004 AND T11 <> ‘0' Record rejected
Feedback report messages (TCOR14)
Sub–edit Text Type
TCOR14-1 Method of diagnosis must be reported for tumours diagnosed before 2004. Core error
TCOR14-2 Method of diagnosis must be coded ‘Not reported' for tumours diagnosed in 2004 and onwards. Core error
Revision (TCOR14)
Year Description
2004 Edit Added: New edit.

TCOR15

Purpose

This edit ensures that method used to establish the date of diagnosis is only reported for tumours diagnosed in 2004 and onwards.

Referenced fields (TCOR15)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of Date of diagnosis (year of date of diagnosis) Not applicable
T24 1 Method used to establish the date of diagnosis TMETHUSED

Business rules

For Add and Update Tumour records
  • Method used to establish the date of diagnosis must only be reported when Date of diagnosis is in 2004 or after.
Edit logic (TCOR15)
Sub–edit Conditions Outcome
TCOR15-1 T5 IN [‘1', ‘2'] AND T12.YEAR < 2004 AND T24<> ‘0' Record rejected
TCOR15-2 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2004 AND T24 = ‘0' Record rejected
Feedback report messages (TCOR15)
Sub–edit Text Type
TCOR15-1 Method used to establish the date of diagnosis must be coded 'Not reported' for tumours diagnosed before 2004. Core error
TCOR15-2 Method used to establish the date of diagnosis must be reported for tumours diagnosed in 2004 and onwards. Core error
Revision (TCOR15)
Year Description
2004 Edit Added: New edit.

TCOR16

Purpose

This edit ensures that diagnostic confirmation is only reported for tumours diagnosed in 2004 and onwards.

Referenced fields (TCOR16)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of Date of diagnosis (year of date of diagnosis) Not applicable
T25 1 Diagnostic confirmation TMETHCONF

Business rules

For Add and Update Tumour records
  • Diagnostic confirmation must only be reported when Date of diagnosis is in 2004 or after.
Edit logic (TCOR16)
Sub–edit Conditions Outcome
TCOR16-1 T5 IN [‘1', ‘2'] AND T12.YEAR < 2004 AND T25<> ‘0' Record rejected
TCOR16-2 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2004 AND T25 = ‘0' Record rejected
Feddback report messages (TCOR16)
Sub–edit Text Type
TCOR16-1 Diagnostic confirmation must be coded ‘Not reported' for tumours diagnosed before 2004. Core error
TCOR16-2 Diagnostic confirmation must be reported for tumours diagnosed in 2004 and onwards. Core error
Revision (TCOR16)
Year Description
2004 Edit Added: New edit.

TCOR17

Purpose

This edit ensures that grade, differentiation or cell indicator is only reported for tumours diagnosed in 2004 and onwards.

Referenced fields (TCOR17)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of Date of diagnosis (year of date of diagnosis) Not applicable
T23 1 Grade, differentiation or cell indicator TGRADE

Business rules

For Add and Update Tumour records
  • Grade, differentiation or cell indicator must only be reported when Date of diagnosis is in 2004 or after.
Edit logic (TCOR17)
Sub–edit Conditions Outcome
TCOR17-1 T5 IN [‘1', ‘2'] AND T12.YEAR < 2004 AND T23 <> ‘0' Record rejected
TCOR17-2 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2004 AND T23 = ‘0' Record rejected
Feedback report messages (TCOR17)
Sub–edit Text Type
TCOR17-1 Grade, differentiation or cell indicator must be coded ‘Not reported' for tumours diagnosed before 2004. Core error
TCOR17-2 Grade, differentiation or cell indicator must be reported for tumours diagnosed in 2004 and onwards. Core error
Revision (TCOR17)
Year Description
2004 Edit Added: New edit.

TCOR18

Purpose

This edit ensures that collaborative staging variables are reported for tumours within the CCR collaborative staging scope.

Referenced fields (TCOR18)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records outside the CCR collaborative staging scope48,
  • All Collaborative staging variables must be blank.
For Add and Update Tumour records within the CCR collaborative staging scope,
  • All Collaborative staging variables must be reported.
Edit logic (TCOR18)
Sub–edit Conditions Outcome
TCOR18-1 T5 IN [‘1', ‘2'] AND T12.YEAR < 2004 AND (T27 IS NOT NULL OR T28 IS NOT NULL OR T29 IS NOT NULL OR T30 IS NOT NULL OR T31 IS NOT NULL OR T32 IS NOT NULL OR T33 IS NOT NULL OR T34 IS NOT NULL OR T35 IS NOT NULL OR T36 IS NOT NULL OR T37 IS NOT NULL OR T38 IS NOT NULL OR T39 IS NOT NULL OR T40 IS NOT NULL OR T41 IS NOT NULL OR T52 IS NOT NULL) CS data items are not posted.
TCOR18-2 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2004 AND (T27 IS NULL OR T28 IS NULL OR T29 IS NULL OR T30 IS NULL OR T31 IS NULL OR T32 IS NULL OR T33 IS NULL OR T34 IS NULL OR T35 IS NULL OR T36 IS NULL OR T37 IS NULL OR T38 IS NULL OR T39 IS NULL OR T40 IS NULL OR T41 IS NULL OR T52 IS NULL) CS data items filled with 'R' at posting.
Feedback report messages (TCOR18)
Sub–edit Text Type
TCOR18-1 Collaborative staging data must be left blank for tumours diagnosed prior to 2004. Reported data will not be loaded into CCR. CS fatal error
TCOR18-2 Eligible Collaborative staging site: all Collaborative staging variables must be reported. CS fatal error
Revision (TCOR18)
Year Description
2007 Referenced fields and Edit logic updated: T52 added as a new CS variable
2004 Edit Added: New edit.

TCOR19

Purpose

This edit ensures that AJCC TNM staging variables are reported for tumours within the CCR AJCC TNM staging scope.

Referenced fields (TCOR19)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T42 9 AJCC clinical T TAJCCCLINT
T43 3 AJCC clinical N TAJCCCLINN
T44 3 AJCC clinical M TAJCCCLINM
T45 9 AJCC pathologic T TAJCCPATHT
T46 3 AJCC pathologic N TAJCCPATHN
T47 3 AJCC pathologic M TAJCCPATHM
T48 4 AJCC clinical TNM stage group TAJCCCLINSG
T49 4 AJCC pathologic TNM stage group TAJCCPATHSG
T50 4 AJCC TNM stage group TAJCCSG
T51 2 AJCC edition number TAJCCEDNUM

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • All AJCC TNM staging variables must be reported.
For Add and Update Tumour records outside the CCR AJCC TNM staging scope
  • All AJCC TNM staging variables must be blank.

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Edit logic (TCOR19)
Sub–edit Conditions Outcome
TCOR19-1 T5 IN [‘1', ‘2'] AND T12.YEAR < 2003 AND NOT (T42 IS NULL AND T43 IS NULL AND T44 IS NULL AND T45 IS NULL AND T46 IS NULL AND T47 IS NULL AND T48 IS NULL AND T49 IS NULL AND T50 IS NULL AND T51 IS NULL) AJCC TNM data items are not posted.
TCOR19-2 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND (T42 IS NULL OR T43 IS NULL OR T44 IS NULL OR T45 IS NULL OR T46 IS NULL OR T47 IS NULL OR T48 IS NULL OR T49 IS NULL OR T50 IS NULL OR T51 IS NULL) AJCC TNM data items filled with 'R' at posting.
TCOR19-3 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND NOT (T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X]) AND NOT (T42 IS NULL AND T43 IS NULL AND T44 IS NULL AND T45 IS NULL AND T46 IS NULL AND T47 IS NULL AND T48 IS NULL AND T49 IS NULL AND T50 IS NULL AND T51 IS NULL) AJCC TNM data items are not posted.
Feedback report messages (TCOR19)
Sub–edit Text Type
TCOR19-1 All AJCC TNM staging data must be blank for tumours diagnosed prior to 2003. Reported data will not be loaded into CCR. AJCC TNM fatal error
TCOR19-2 Eligible AJCC TNM staging site: all AJCC TNM staging variables must be reported. AJCC TNM fatal error
TCOR19-3 Non-eligible AJCC TNM staging site: all AJCC TNM staging variables must be blank. Reported data will not be loaded into CCR. AJCC TNM fatal error
Revision (TCOR19)
Year Description
2004 Edit Added: New edit.

TCOR20

Purpose

This edit ensures that TNM stage group is reported only when clinical and pathologic TNM stage group are not reported.

Referenced fields (TCOR20)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T48 4 AJCC clinical TNM stage group TAJCCCLINSG
T49 4 AJCC pathologic TNM stage group TAJCCPATHSG
T50 4 AJCC TNM stage group TAJCCSG

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • AJCC TNM stage group can only be reported when both AJCC clinical TNM stage group and AJCC pathologic TNM stage group are either unknown or not assessed.

To simplify the edit logic, let Site X be a given site within the AJCC TNM Staging. Ex:Colorectal, breast or prostate.

Edit logic (TCOR20)
Sub–edit Conditions Outcome
TCOR20-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T50 <> ‘99' AND (T48 NOT IN [‘99', ‘X'] OR T49 NOT IN [‘99', ‘X']) AJCC TNM data items filled with 'R' at posting.
Feedback report messasges (TCOR20)
Sub–edit Text Type
TCOR20-1 TNM stage group cannot be reported when clinical and/or pathologic TNM stage group is reported. AJCC TNM error
Revision (TCOR20)
Year Description
2004 Edit Added: New edit.

TCOR21

Purpose

This edit ensures that the combination of AJCC Clinical TNM stage group and the individual clinical T, N, M values combination is acceptable.

Referenced fields (TCOR21)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T42 9 AJCC clinical T TAJCCCLINT
T43 3 AJCC clinical N TAJCCCLINN
T44 3 AJCC clinical M TAJCCCLINM
T48 4 AJCC clinical TNM stage group TAJCCCLINSG

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • If AJCC clinical TNM stage group is known and assessed then AJCC clinical T, N, M and AJCC clinical TNM stage group combination must be valid for the site49.
  • If AJCC clinical TNM stage group is not assessed then AJCC clinical T, N and M combination must not lead to a stage group for the site
  • If AJCC clinical TNM stage group is unknown then all AJCC clinical T, N and M values must also be unknown and conversely.

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Edit logic (TCOR21)
Sub–edit Conditions Outcome
TCOR21-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND NOT (T42 = ‘99' AND T43 = ‘99' AND T44 = ‘99') AND T48 NOT IN [‘99', ‘X'] AND T42, T43, T44, T48 NOT IN [valid AJCC TNM and stage group combination for Site X] AJCC TNM data items filled with 'R' at posting.
TCOR21-2 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T48 = ‘X' AND T42, T43, T44 IN [valid AJCC TNM and stage group combination for Site X] AJCC TNM data items filled with 'R' at posting.
TCOR21-3 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T48 = ‘99' AND (T42 <> ‘99' OR T43 <> ‘99' OR T44 <> ‘99') AJCC TNM data items filled with 'R' at posting.
TCOR21-4 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T48 <> ‘99' AND T42 = ‘99' AND T43 = ‘99' AND T44 = ‘99' AJCC TNM data items filled with 'R' at posting.
Feedback report messages (TCOR21)
Sub–edit Text Type
TCOR21-1 AJCC clinical TNM stage group is invalid for reported AJCC clinical T, N and M values and site. AJCC TNM error
TCOR21-2 AJCC clinical TNM stage group must be assessed for reported clinical T, N and M values and site. AJCC TNM error
TCOR21-3 All AJCC clinical T, N and M values must be set to ‘Unknown' when AJCC clinical TNM stage group is ‘Unknown'. AJCC TNM error
TCOR21-4 AJCC clinical TNM stage group must be set to ‘Unknown' when All AJCC clinical T, N and M values are set to ‘Unknown'. AJCC TNM error
Revision (TCOR21)
Year Description
2004 Edit Added: New edit.

TCOR22

Purpose

This edit ensures that the combination of AJCC pathologic TNM stage group and the individualpathologic T, N, M values is acceptable.

Referenced fields (TCOR22)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T45 9 AJCC pathologic T TAJCCPATHT
T46 3 AJCC pathologic N TAJCCPATHN
T47 3 AJCC pathologic M TAJCCPATHM
T49 4 AJCC pathologic TNM stage group TAJCCPATHSG

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29.
  • If AJCC pathologic TNM stage group is known and assessed then AJCC pathologic T, N, M and AJCC pathologic TNM stage group combination must be valid for the site49.
  • If AJCC pathologic TNM stage group is not assessed then AJCC pathologic T, N and M combination must not imply a stage group for the site49.
  • If AJCC pathologic TNM stage group is unknown then all AJCC pathologic T, N and M values must also be unknown and conversely.

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Edit logic (TCOR22)
Sub–edit Conditions Outcome
TCOR22-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for SiteX] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND NOT (T45 = ‘99' AND T46 = ‘99' AND T47 = ‘99') AND T49 NOT IN [‘99', ‘X'] AND T45, T46, T47, T49 NOT IN [valid AJCC TNM and stage group combination for Site X] AJCC TNM data items filled with 'R' at posting.
TCOR22-2 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T49 = ‘X' AND T45, T46, T47 IN [valid AJCC TNM and stage group combination for Site X] AJCC TNM data items filled with 'R' at posting.
TCOR22-3 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T49 = ‘99' AND (T45 <> ‘99' OR T46 <> ‘99' OR T47 <> ‘99') AJCC TNM data items filled with 'R' at posting.
TCOR22-4 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T49 <> ‘99' AND T45 = ‘99' AND T46 = ‘99' AND T47 = ‘99' AJCC TNM data items filled with 'R' at posting.
Feedback report messages (TCOR22)
Sub–edit Text Type
TCOR22-1 AJCC pathologic TNM stage group is invalid for reported AJCC pathologic T, N and M values and site. AJCC TNM error
TCOR22-2 AJCC pathologic TNM stage group must be assessed for reported pathologic T, N and M values and site. AJCC TNM error
TCOR22-3 All AJCC pathologic T, N and M values must be set to ‘Unknown' when AJCC pathologic TNM stage group is ‘Unknown'. AJCC TNM error
TCOR22-4 AJCC pathologic TNM stage group must be set to ‘Unknown' when All AJCC pathologic T, N and M values are set to ‘Unknown'. AJCC TNM error
Revision (TCOR22)
Year Description
2004 Edit Added: New edit.

TCOR23

Purpose

This edit ensures that the combination of AJCC TNM stage group and the individual clinical/pathologic T, N, M values is acceptable.

Referenced fields(TCOR23)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T42 9 AJCC clinical T TAJCCCLINT
T43 3 AJCC clinical N TAJCCCLINN
T44 3 AJCC clinical M TAJCCCLINM
T45 9 AJCC pathologic T TAJCCPATHT
T46 3 AJCC pathologic N TAJCCPATHN
T47 3 AJCC pathologic M TAJCCPATHM
T50 4 AJCC TNM stage group TAJCCSG

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • If AJCC TNM stage group is known then the most “accurate” combination of known and assessed AJCC clinical/pathologic T, N, M values and AJCC TNM stage group must be valid49,50. For any staging element (T, N, M), pathologic values are always considered more “accurate” when both clinical and pathologic values are known and assessed.
  • Example If cT = ‘T2' and pT = ‘T1', the most accurate tumour stage is ‘T1' (pathologic data take precedence over clinical).
  • Example If cM = ‘M1' and pM = ‘MX', the most accurate metastases stage is ‘M1' (pathologic M is not assessed).

To simplify the edit logic, let:

  • BestT (clin, path), BestN (clin, path) and BestM (clin, path) be functions that return the most “accurate” tumour, node and metastases staging value based on the rules stated above. When both clinical and pathologic values are '99', 'TX', 'NX' or 'MX', these functions always return the pathologic value.
  • Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.
Edit logic (TCOR23)
Sub–edit Conditions Outcome
TCOR23-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T50 <> '99' AND ((BestT (T42, T45) NOT IN [‘99', ‘X'] AND BestN (T43, T46) IN [‘99', ‘X'] AND BestM (T44, T47) IN [‘99', ‘X'] AND BestT(T42, T45), T50 NOT IN [valid AJCC TNM and stage group combination for Site X]) OR (BestT (T42, T45) IN [‘99', ‘X'] AND BestN (T43, T46) NOT IN [‘99', ‘X'] AND BestM (T44, T47) IN [‘99', ‘X'] AND BestN (T43, T46), T50 NOT IN [valid AJCC TNM and stage group combination for Site X]) OR (BestT (T42, T45) IN [‘99', ‘X'] AND BestN (T43, T46) IN [‘99', ‘X'] AND BestM (T44, T47) NOT IN [‘99', ‘X'] AND BestM (T44, T47), T50 NOT IN [valid AJCC TNM and stage group combination for Site X]) OR (BestT (T42, T45) NOT IN [‘99', ‘X'] AND BestN (T43, T46) NOT IN [‘99', ‘X'] AND BestM (T44, T47) IN [‘99', ‘X'] AND BestT (T42, T45), BestN (T43, T46), T50 NOT IN [valid AJCC TNM and stage group combination for Site X]) OR (BestT (T42, T45) IN [‘99', ‘X'] AND BestN (T43, T46) NOT IN [‘99', ‘X'] AND BestM (T44, T47) NOT IN [‘99', ‘X'] AND BestN (T43, T46), BestM (T44, T47), T50 NOT IN [valid AJCC TNM and stage group combination for Site X]) OR ((BestT (T42, T45) NOT IN [‘99', ‘X'] AND BestN (T43, T46) IN [‘99', ‘X'] AND BestM (T44, T47) NOT IN [‘99', ‘X'] AND BestT(T42, T45), BestM (T44, T47), T50 NOT IN [valid AJCC TNM and stage group combination for Site X]) OR (BestT (T42, T45) NOT IN [‘99', ‘X'] AND BestN (T43, T46) NOT IN [‘99', ‘X'] AND BestM (T44, T47) NOT IN [‘99', ‘X'] AND BestT(T42, T45), BestN (T43, T46), BestM (T44, T47), T50 NOT IN [valid AJCC TNM and stage group combination for Site X])) AJCC TNM data items filled with 'R' at posting.
Feedback report messages (TCOR23)
Sub–edit Text Type
TCOR23-1 AJCC TNM stage group is invalid for reported clinical/pathologic T, N and M values and site. AJCC TNM error
Revision (TCOR23)
Year Description
2004 Edit Added: New edit.

TCOR24

Purpose

This edit ensures that AJCC edition number is coherent with all remaining AJCC TNM staging variables.

Referenced fields (TCOR24)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T42 9 AJCC clinical T TAJCCCLINT
T43 3 AJCC clinical N TAJCCCLINN
T44 3 AJCC clinical M TAJCCCLINM
T45 9 AJCC pathologic T TAJCCPATHT
T46 3 AJCC pathologic N TAJCCPATHN
T47 3 AJCC pathologic M TAJCCPATHM
T48 4 AJCC clinical TNM stage group TAJCCCLINSG
T49 4 AJCC pathologic TNM stage group TAJCCPATHSG
T50 4 AJCC TNM stage group TAJCCSG
T51 2 AJCC edition number TAJCCEDNUM

Business rules

For Add and Update Tumour records with the CCR AJCC TNM staging scope29.
  • If AJCC edition number is set to ‘Not staged' then all other AJCC TNM staging variables must be set to ‘Unknown' and conversely.
Edit logic (TCOR24)
Sub–edit Conditions Outcome
TCOR24-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND ((T15 IN [Eligible ICD-O-3 – Topography codes for AJCC TNM Staging Colorectal sites] AND T21 IN [Eligible ICD-O-3 – Histology codes for AJCC TNM Staging Colorectal sites] AND T22 IN [Eligible ICD-O-3 Behaviour codes for AJCC TNM Staging Colorectal sites]) OR (T15 IN [Eligible ICD-O-3 – Topography codes for AJCC TNM Staging Breast sites] AND T21 IN [Eligible ICD-O-3 – Histology codes for AJCC TNM Staging Breast sites] AND T22 IN [Eligible ICD-O-3 – Behaviour codes for AJCC TNM Staging Breast sites]) OR (T15 IN [Eligible ICD-O-3 – Topography codes for AJCC TNM Staging Prostate sites] AND T21 IN [Eligible ICD-O-3 – Histology codes for AJCC TNM Staging Prostate sites] AND T22 IN [Eligible ICD-O-3 – Behaviour codes for AJCC TNM Staging Prostate sites])) AND T42 = ‘99' AND T43 = ‘99' AND T44 = ‘99' AND T45 = ‘99' AND T46 = ‘99' AND T47 = ‘99' AND T48 = ‘99' AND T49 = ‘99' AND T50 = ‘99' AND T51 <> ‘00' AJCC TNM data items filled with 'R' at posting.
TCOR24-2 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND ((T15 IN [Eligible ICD-O-3 – Topography codes for AJCC TNM Staging Colorectal sites] AND T21 IN [Eligible ICD-O-3 – Histology codes for AJCC TNM Staging Colorectal sites] AND T22 IN [Eligible ICD-O-3 Behaviour codes for AJCC TNM Staging Colorectal sites]) OR (T15 IN [Eligible ICD-O-3 – Topography codes for AJCC TNM Staging Breast sites] AND T21 IN [Eligible ICD-O-3 – Histology codes for AJCC TNM Staging Breast sites] AND T22 IN [Eligible ICD-O-3 – Behaviour codes for AJCC TNM Staging Breast sites]) OR (T15 IN [Eligible ICD-O-3 – Topography codes for AJCC TNM Staging Prostate sites] AND T21 IN [Eligible ICD-O-3 – Histology codes for AJCC TNM Staging Prostate sites] AND T22 IN [Eligible ICD-O-3 – Behaviour codes for AJCC TNM Staging Prostate sites])) AND T51 = ‘00' AND (T42 <> ‘99' OR T43 <> ‘99' OR T44 <> ‘99' OR T45 <> ‘99' OR T46 <> ‘99' OR T47 <> ‘99' OR T48 <> ‘99' OR T49 <> ‘99' OR T50 <> ‘99') All AJCC TNM data items filled with 'R' at posting.
Feedback report messages (TCOR24)
Sub–edit Text Type
TCOR24-1 TNM edition number must be set to ‘Not Staged' when all other AJCC TNM staging variables are ‘Unknown'. AJCC TNM error
TCOR24-2 TNM edition number cannot be set to ‘Not Staged' when some AJCC TNM staging variables are reported. AJCC TNM error
Revision (TCOR24)
Year Description
2004 Edit Added: New edit.

TCOR26

Purpose

This edit ensures the consistency between Ambiguous terminology diagnosis and Date of conclusive diagnosis.

Referenced fields (TCOR26)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T53 1 Ambiguous terminology diagnosis TDATCONCLUSDIAG
T54 8 Date of conclusive diagnosis TMULTCOUNT

Business rules

For Add and Update Tumour records
  • If Date of Diagnosis is before 2008 then Ambiguous terminology diagnosis and Date of conclusive diagnosis must both be blank.
  • If Date of Diagnosis is 2008 and onwards then Ambiguous terminology diagnosis and Date of conclusive diagnosis must be either both blank or both reported.
Edit logic (TCOR26)
Sub–edit Conditions Outcome
TCOR26-1 T5 IN [‘1','2'] AND T12.YEAR < 2008 AND (T53 IS NOT NULL OR T54 IS NOT NULL) Record rejected
TCOR26-2 T5 IN [‘1','2'] AND T12.YEAR >= 2008 AND (T53 IS NOT NULL OR T54 IS NOT NULL) AND (T53 IS NULL OR T54 IS NULL) Record rejected
Feedback report messages (TCOR26)
Sub–edit Text Type
TCOR26-1 Ambiguous terminology diagnosis and Date of conclusive diagnosis must both be blank if Date of diagnosis is before 2008. Core error
TCOR26-2 If Date of diagnosis is 2008 and onwards, Ambiguous terminology diagnosis and Date of conclusive diagnosis must either both be reported or both be left blank. Core error
Revision (TCOR26)
Year Description
2008 Edit added: New edit.

TCOR27

Purpose

This edit ensures the consistency between Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter.

Referenced fields (TCOR27)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 5 First 4 digits of T12 (year of date of diagnosis) Not applicable
T55 2 Type of multiple tumours reported as one primary TMULTTUMONEPRIM
T56 8 Date of multiple tumours DDATMULT
T57 2 Multiplicity counter TMULTCOUNT

Business rules

For Add and Update Tumour records
  • If Date of Diagnosis is before 2008 then Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter must all be blank.
  • If Date of Diagnosis is 2008 and onwards then Type of multiple tumours reported as one primary, Date of multiple tumours, and Multiplicity counter must be either all blank or all reported.
Edit logic (TCOR27)
Sub–edit Conditions Outcome
TCOR27-1 T5 IN [‘1','2'] AND T12.YEAR < 2008 AND (T55 IS NOT NULL OR T56 IS NOT NULL OR T57 IS NOT NULL) Record rejected
TCOR27-2 T5 IN [‘1','2'] AND T12.YEAR >= 2008 AND (T55 IS NOT NULL OR T56 IS NOT NULL OR T57 IS NOT NULL) AND (T55 IS NULL OR T56 IS NULL OR T57 IS NULL) Record rejected
Feedback report messages (TCOR27)
Sub–edit Text Type
TCOR27-1 Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter must all be blank if Date of diagnosis is before 2008. Core error
TCOR27-2 Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter must either all be blank or all be reported if Date of diagnosis is 2008 and onwards. Core error
Revision (TCOR27)
Year Description
2008 Edit added: New edit.

TCOR29

Purpose

This edit ensures the consistency between Ambiguous terminology diagnosis and Date of conclusive diagnosis.

Referenced fields (TCOR29)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T53 1 Ambiguous terminology diagnosis TAMBIGTERM
T54 8 Date of multiple tumours DDATMULT

Business rules

For Add and Update Tumour records
  • If Ambiguous terminology diagnosis is “Conclusive terminology within 60 days of original diagnosis” (0) then Date of conclusive diagnosis must be “Not applicable” (88888888).
  • If Ambiguous terminology diagnosis is “Ambiguous terminology only” (1) then Date of conclusive diagnosis must be ”Accessioned based on ambiguous terminology diagnosis only” (00000000).
  • If Ambiguous terminology diagnosis is “Ambiguous terminology followed by conclusive terminology” (2) then Date of conclusive diagnosis must NOT be “Not applicable” (88888888) or  “Accessioned based on ambiguous terminology diagnosis only” (00000000).
  • If Ambiguous terminology diagnosis is “Unknown terminology” (9) then Date of conclusive diagnosis must indicate that date is unknown (99999999).
  • If Ambiguous terminology diagnosis is “Ambiguous terminology followed by conclusive terminology” (2) then Date of conclusive diagnosis should NOT be unknown (99999999).
Edit logic (TCOR29)
Sub–edit Conditions Outcome
TCOR29-1 T5 IN [‘1','2'] AND (T53 = ‘0' AND T54 <> ‘88888888') OR (T53 = ‘1' AND T54 <> ‘00000000') OR (T53 = ‘2' AND T54 IN [‘00000000', ‘88888888']) OR (T53 = ‘9' AND T54 <> ‘99999999') Record rejected
TCOR29-2 T5 IN [‘1', '2'] AND T53 IN [‘2'] AND T54 IN [‘99999999'] Warning
Feedback report messages (TCOR29)
Sub–edit Text Type
TCOR29-1 Ambiguous terminology diagnosis and Date of conclusive diagnosis are inconsistent. Core error
TCOR29-2 Date of conclusive diagnosis should be a valid calendar date when case is identified as "Ambiguous terminology followed by conclusive terminology”. Warning
Revision (TCOR29)
Year Description
2008 Edit added: New edit.

TCOR30

Purpose

This edit ensures that date of diagnosis and date of conclusive diagnosis respect a chronological sequence and time frame.

Referenced fields (TCOR30)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12 8 Date of diagnosis TDATDIAG
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T12.MONTH 2 5th and 6th digits of T12 (month of date of diagnosis) Not applicable
T12.DAY 2 Last 2 digits of T12 (day of date of diagnosis) Not applicable
T54 8 Date of Conclusive Diagnosis TDATCONCLUSDIAG
T54.YEAR 4 First 4 digits of T54 (year of date of conclusive diagnosis) Not applicable
T54.MONTH 2 5th and 6th digits of T54 (month of date of conclusive diagnosis) Not applicable
T54.DAY 2 Last 2 digits of T54 (day of date of conclusive diagnosis) Not applicable

Business rules

For Add and Update Tumour records
  • Date of conclusive diagnosis must be greater than two months (60 days) after the Date of diagnosis.
Edit logic (TCOR30)
Sub–edit Conditions Outcome
TCOR30-1 T5 IN [‘1', ‘2'] AND T54 NOT IN [‘00000000','88888888', ‘99999999'] AND ((T12.DAY <> ‘99' AND T54.DAY <> ‘99' AND T54 < T12) OR (T12.MONTH <> ‘99' AND T54.MONTH <> ‘99' AND T54.YEAR || T54.MONTH < T12.YEAR || T12.MONTH) OR (T54.YEAR < T12.YEAR)) Record rejected
TCOR30-2 T5 IN [‘1', ‘2'] AND T54 NOT IN [‘00000000','88888888', ‘99999999'] and DIFF_DAYS (Date1,Date2) <= 60. See Appendix J – Interval between 2 dates (complete or partial). Record rejected
TCOR30-3 T5 IN [‘1', ‘2'] AND T12.YEAR = T54.YEAR AND T12.MONTH = ‘99' AND T54.MONTH = ‘99' Record rejected
Feedback report messages (TCOR30)
Sub–edit Text Type
TCOR30-1 Date of conclusive diagnosis is before date of diagnosis. Core error
TCOR30-2 Date of conclusive diagnosis must be greater than 60 days after the date of diagnosis. Core error
TCOR30-3 If the year of Date of diagnosis is equal to the year of Date of conclusive diagnosis and both months are unknown, the Date of conclusive diagnosis must be unknown. Core error
Revision (TCOR30)
Year Description
2008 Edit added: New edit.

TCOR31

Purpose

This edit ensures the consistency between ICD-O-2/3 Topography and Type of multiple tumours reported as one primary.

Referenced fields (TCOR31)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T15 5 ICD-O-2/3 Topography TICD_02T
T55 2 Type of multiple tumours reported as one primary TMULTTUMONEPRIM

Business rules

For Add and Update Tumour records
  • If Type of multiple tumours reported as one primary is coded as “polyp and adenocarcinoma” (31) or “Familial Adenomatous Polyposis (FAP) with carcinoma” (32) Then ICD-O-2/3 Topography must be coded as “Colon” (C180-C189), “Rectosigmoid Junction” (C199) or “Rectum” (C209).
Edit logic (TCOR31)
Sub–edit Conditions Outcome
TCOR31-1 T5 IN [‘1', ‘2'] AND T55 IN [31,32] and T15 NOT IN [C180-C189, C199 or C209] Record rejected
Feedback report messages (TCOR31)
Sub–edit Text Type
TCOR31-1 Type of multiple tumours reported as one primary and ICD-O-2/3 combination is invalid. Core error
Revision (TCOR31)
Year Description
2008 Edit added: New edit.

TCOR32

Purpose

This edit ensures the consistency between ICD-O-3 Behaviour and Type of multiple tumours reported as one primary.

Referenced fields (TCOR32)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T22 1 ICD-O-3 Behaviour TICD_03B
T55 2 Type of multiple tumours reported as one primary TMULTTUMONEPRIM

Business rules

For Add and Update Tumour records
  • If Type of multiple tumours reported as one primary is coded as either “Multiple benign (intracranial and CNS sites only)” (10), “Multiple borderline” (11), or “Benign (intracranial and CNS sites only) and borderline” (12), then ICD-O-3 Behaviour must be coded as either “benign” (0) or “borderline” (1).
Edit logic (TCOR32)
Sub–edit Conditions Outcome
TCOR32-1 T5 IN [‘1', ‘2'] AND T55 IN [‘10', '11', '12'] AND T22 NOT IN [‘0','1'] Record rejected
Feedback report messages (TCOR32)
Sub–edit Text Type
TCOR32-1 Type of multiple tumours reported as one primary and ICD-O-3 behaviour combination is invalid. Core error
Revision (TCOR32)
Year Description
2008 Edit added: New edit.

TCOR33

Purpose

This edit ensures the consistency between Type of multiple tumours reported as one primary, Date of multiple tumours, Multiplicity counter, ICD-O-2/3 Topography and ICD-O-3 Histology.

Referenced fields (TCOR33)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T15 4 ICD–O–2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T24 1 Method used to establish the date of diagnosis TMETHUSED
T55 2 Type of multiple tumours reported as one primary TMULTTUMONEPRIM
T56 8 Date of multiple tumours DDATMULT
T57 2 Multiplicity counter TMULTCOUNT

Business rules

For Add and Update Tumour records where method used to establish the date of diagnosis is not ‘death certificate only”
  • If ICD–O–2/3 topography is ‘unknown primary' (C809) or ICD–O– 3 Histology refers to lymphoma, leukemia or immunoproliferative disease62 [9590-9989] then Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter must be ‘Information on multiple tumours not applicable for this site'.
  • If ICD-O-2/3 topography is known (not C809) and ICD–O–3 Histology does NOT refer to lymphoma, leukemia or immunoproliferative disease [9590-9989] then Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter must not be ‘Information on multiple tumours not applicable for this site'.
Edit logic (TCOR33)
Sub–edit Conditions Outcome
TCOR33-1 T5 IN [‘1','2'] AND T24 <> 8 AND (T15 = ‘C809' OR T21 IN [9590-9989]) AND T55 <> 88 OR T56 <> ‘88888888'  OR T57 <> ‘88' Record rejected
TCOR33-2 T5 IN [‘1','2'] AND T24 <> 8 AND (T15 <>  ‘C809' OR T21 NOT IN [9590-9989]) AND T55 = ‘88' OR T56 = ‘88888888' OR T57 = ‘88' Record rejected
Feedback report messages (TCOR33)
Sub–edit Text Type
TCOR33-1 Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter must be reported as ‘Information on multiple tumours not applicable for this site'. Core error
TCOR33-2 Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter must NOT be reported as ‘Information on multiple tumours not applicable for this site'. Core error
Revision (TCOR33)
Year Description
2008 Edit added: New edit.

TCOR34

Purpose

This edit ensures the consistency between Date of multiple tumours and Type of multiple tumours reported as one primary.

Referenced fields (TCOR34)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T55 2 Type of multiple tumours reported as one primary TMULTTUMONEPRIM
T56 8 Date of multiple tumours DDATMULT
T57 2 Multiplicity counter TMULTCOUNT

Business rules

For Add and Update Tumour records
  • If Type of multiple tumours reported as one primary is “single tumour” (00) then  Date of multiple tumours  must be “single tumour” (00000000) and Multiplicity counter must be ‘01'.
  • If Type of multiple tumours reported as one primary is “not applicable for this site” (88) then Date of multiple tumours  must be “information on multiple tumours not applicable for this site” (88888888) and Multiplicity counter must be ‘Information on multiple tumours not applicable for this site' (88).
  • If Type of multiple tumours reported as one primary indicates multiple tumours (codes 10 through 80) then Date of multiple tumours must be the date the patient is diagnosed with multiple tumours or unknown (99999999) and Multiplicity counter must be values 02 through 87.
  • If Type of multiple tumours reported as one primary is “Unknown” (99) then Date of multiple tumours must be unknown (99999999) and Multiplicity counter must be “Multiple tumours present, unknown how many; unknown if single or multiple tumours” (99).
Edit logic (TCOR34)
Sub–edit Conditions Outcome
TCOR34-1 T5 IN [‘1','2'] AND (T55 = ‘00' AND T56 <> ‘00000000' OR T57 <> ‘01') OR (T55 = ‘88' AND T56 <> ‘88888888' OR T57 <> 88' ) OR (T55 = ‘99' AND T56 <> ‘99999999' OR T57 <> ‘99') OR (T55 IN [‘10','11','12','20','30','31','32','40','80'] AND (T56 = ‘00000000' OR T56 = ‘88888888') OR (T57 = ‘01' OR T57 = ‘88'  OR T57 = ‘99') Record rejected
Feedback report messages (TCOR34)
Sub–edit Text Type
TCOR34-1 Type of multiple tumours reported as one primary, date of multiple tumours and multiplicity counter combination is invalid. Core error
Revision (TCOR34)
Year Description
2008 Edit added: New edit.

TCOR35

Purpose

This edit ensures the consistency between Method used to establish the date of diagnosis, Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter..

Referenced fields (TCOR35)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T24 1 Method used to establish the date of diagnosis TMETHUSED
T55 2 Type of multiple tumours reported as one primary TMULTTUMONEPRIM
T56 8 Date of multiple tumours DDATMULT
T57 2 Multiplicity counter TMULTCOUNT

Business rules

For Add and Update Tumour records
  • If Type of multiple tumours reported as one primary is “Unknown” (99) and Method used to establish date of diagnosis is “Death certificate only” (8), then Date of multiple tumours must be “Unknown” (99999999) and Multiplicity counter must be “Multiple tumours present, unknown how many/unknown if single or multiple tumours” (99).
Edit logic (TCOR35)
Sub–edit Conditions Outcome
TCOR35-1 T5 IN [‘1','2'] AND (T55 = ‘99' AND T24 = ‘8') AND (T56 <> ‘99999999' OR T57 <> ‘99') Record rejected
Feedback report messages (TCOR35)
Sub–edit Text Type
TCOR35-1 Method used to establish the date of diagnosis, Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter combination is invalid. Core error
Revision (TCOR35)
Year Description
2008 Edit added: New edit.

3.6 Match edits

The purpose of the match edits is to enforce the business rules between fields on different records. For ease of use, match edits have been divided into four groups:

  • Key input match edits: Ensure that input patient and tumour records respect the submission rules in terms of matching keys.
  • Key base match edits: Ensure that input patient and tumour records respect the actual state of the CCR in terms of matching keys.
  • Data item match edits: Enforce the business rules between data items (other than keys) found on different records.
  • Pre-posting match edits: Identify core error-free input records that cannot be posted to the CCR4 because some other related Input records are either missing or have core errors.

3.6.1 Key input match edits

The purpose of the key input match edits is to ensure that input patient and tumour records respect the submission rules in terms of matching keys.

At this level, the following fields are used as key:

  • Patient record: Reporting province/territory and patient identification number.
  • Tumour record: Reporting province/territory, patient identification number and tumour reference number.

The following table summarizes the purpose of each individual edit of this category:

Table 28 Input match edits summary
Edit name Purpose
KIM1 Ensures that only one operation affecting a specific patient record is performed (that is, add, delete or update) within a data submission.
KIM2 Ensures that only one operation affecting a specific Tumour record is performed (that is, add, delete or update) within a data submission.
KIM3 Enforces the submission rules regarding the addition of a patient record.
KIM4 Enforces the submission rules regarding the deletion of a patient record.
KIM5 Enforces the submission rules regarding the addition of a Tumour record.

Important note:

When a key input match edit fails, all related Input records (all input patient and tumour records sharing the same reporting province/territory and patient identification number) are rejected. Related records are also called the family of records.

KIM1

Purpose

This edit ensures that only one operation affecting a specific patient record is performed
(add, delete or update) within a data submission.

Referenced fields (KIM1)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN

Business rules

For Input Patient records
  • There cannot be another Input patient record with identical Reporting province/territory and Patient identification number within the same data submission.
Edit logic (KIM1)
Sub–edit Conditions Outcome
KIM1-1 Input patient record that matches another Input patient record where P1=P1 AND P2=P2. Family rejected51
Feedback report messages (KIM1)
Sub–edit Text Type
KIM1-1 Family rejected: more than one Input patient record with the same Patient reporting province/territory and Patient identification number. Core error
Revision (KIM1)
Year Description
2004 Edit renamed: Formerly known as Input Match Edit No.1.

KIM2

Purpose

This edit ensures that only on

Referenced fields (KIM2)
Field Length Description Acronym
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Tumour patient identification number TPIN
T3 9 Tumour reference number TTRN

Business rules

For Input Tumour records
  • There cannot be another Input Tumour record with identical Reporting province/territory, Patient identification number and Tumour reference number within the same data submission.
Edit logic (KIM2)
Sub–edit Conditions Outcome
KIM2-1 Input tumour record that matches another Input tumour record where T1=T1 AND T2=T2 AND T3=T3. Family rejected52
Feedback report messages (KIM2)
Sub–edit Text Type
KIM2-1 Family rejected: more than one Input tumour record with the same Tumour reporting province/territory, Tumour patient identification number and Tumour reference number. Core error
Revision (KIM2)
Year Description
2004 Edit renamed: Formerly known as Input Match Edit No.2.

KIM3

Purpose

This edit enforces the submission rules regarding the addition of a patient record.

Referenced fields (KIM3)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P4 1 Patient record type PRECTYPE
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Tumour patient identification number TPIN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE

Business fields

For Add Patient records
  • There must be at least one Add Tumour record with identical Reporting province/territory and Patient identification number and a blank CCR identification number within the same data submission.
  • There cannot be any Add Tumour record with identical Reporting province/territory and Patient identification number and a reported CCR identification number within the same data submission.
  • There cannot be any Update or Delete Tumour record with identical Reporting province/territory and Patient identification number within the same data submission.
Edit logic KIM3)
Sub–edit Conditions Outcome
KIM3-1 Input patient record where P4='1' that matches no Input tumour record where T5='1' AND T1=P1 AND T2=P2. Family rejected53
KIM3-2 Input patient record where P4='1' that matches an Input tumour record where T5='1' AND T1=P1 AND T2=P2 AND T4 IS NOT NULL. Family rejected53
KIM3-3 Input patient record where P4='1' that matches an Input tumour record where T5 IN ['2','3'] AND T1=P1 AND T2=P2. Family rejected53
Feedback report messages (KIM3)
Sub–edit Text Type
KIM3-1 Family rejected: Add Patient record does not match any Add Tumour record. Core error
KIM3-2 Family rejected: Add Patient record matches an Add Tumour record with CCR identification number. Core error
KIM3-3 Family rejected: Add Patient record matches an Update or Delete Tumour record. Core error
Revision (KIM3)
Year Description
2004 Edit renamed: Formerly known as Input Match Edit No.3.

KIM4

Purpose

This edit enforces the submission rules regarding the deletion of a patient record.

referenced fields (KIM4)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPROV
P2 12 Patient identification number PPIN
P4 1 Patient record type PRECTYPE
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Tumour patient identification number TPIN
T5 1 Tumour record type TRECTYPE

Business rules

For Delete Patient records
  • There must be at least one Delete Tumour record with identical Reporting province/territory and Patient identification number within the same data submission.
  • There cannot be any Add or Update Tumour record with identical Reporting province/territory and Patient identification number within the same data submission.
Edit logic (KIM4)
Sub–edit Conditions Outcome
KIM4-1 Input patient record where P4='3' that matches no Input tumour record where T5='3' AND P1=T1 AND P2=T2. Family rejected53
KIM4-2 Input patient record where P4='3' that matches Input tumour record where T5 IN ['1','2'] AND P1=T1 AND P2=T2. Family rejected53
Feedback report messages (KIM4)
Sub–edit Text Type
KIM4-1 Delete Patient record does not match any Delete Tumour record. Core error
KIM4-2 Family rejected: Delete Patient record matches an Add or Update Tumour record. Core error
Revision (KIM4)
Year Description
2004 Edit renamed: Formerly known as Input Match Edit No.4.
Business rules changed: CCR identification number has been removed from the edit since it is equivalent to Reporting province/territory – Patient identification number combination.

KIM5

Purpose

This edit enforces the submission rules regarding the addition of a tumour record.

Referenced fields (KIM5)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P4 1 Patient record type PRECTYPE
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Tumour patient identification number TPIN
T4 9 CCR Identification number CCR_ID
T5 1 Tumour record type TRECTYPE

Business rules

For Add Tumour records without CCR identification number
  • There must be an Add Patient record with identical Reporting province/territory and Patient identification number within the same data submission.
  • There cannot be any Update54 Patient records with identical Reporting province/territory and Patient identification number within the same data submission.
Edit logic (KIM5)
Sub–edit Conditions Outcome
KIM5-1 Input tumour record where T5='1' AND T4 IS NULL that matches no Input patient record where P4='1' AND P1=T1 AND P2=T2. Family rejected55
KIM5-2 Input tumour record where T5='1' AND T4 IS NULL that matches Input patient record where P4='2' AND P1=T1 AND P2=T2. Family rejected55
Feedback report messages (KIM5)
Sub–edit Text Type
KIM5-1 Family rejected: Add Tumour record without CCR_ID does not match an Add Patient record. Core error
KIM5-2 Family rejected: Add Tumour record without CCR_ID matches an Update Patient record. Core error
Revision (KIM5)
Year Description
2004 Edit renamed: Formerly known as Input Match Edit No.6.

3.6.2 Key base match edits

The purpose of the key base match edits is to ensure that input patient and tumour records respect the actual state of the CCR in terms of matching keys.

At this level, the following fields are used as keys:

  • Patient record: CCR identification number, reporting province/territory and patient identification number.
  • Tumour record: CCR identification number, reporting province/territory, patient identification number and tumour reference number.

The following table summarizes the purpose of each individual edit of this category.

Table 29 Base match edits summary
Edit name Purpose
KBM1 Ensures that no duplicate Patient keys are posted to the CCR.
KBM2 Ensures that Update or Delete Patient record keys match a Base Patient record.
KBM3 Ensures that no duplicate Tumour keys are posted to the CCR.
KBM4 Ensures that an Add Tumour record with CCR identification number matches a Base patient record owned by the Reporting province/territory.
KBM5 Ensures that Update or Delete Tumour record keys match a Base tumour record.

Important note

When a key base match edit fails, the conflicting base record (if any), is included in the detailed feedback report for easier error correction.

Writing conventions throughout the following edit descriptions:

  • Expression "base patient/tumour record" means a patient/tumour record already in the CCR.
  • Expression "add/update/delete/input patient/tumour record" means a patient/tumour record within the data submission.
  • Unless specified otherwise, field numbers prefixed with "I" are input fields and field numbers prefixed with "B" are Base fields. 
    Example: IT5 is the Tumour record type field on an input tumour record.
    Example: IP1 is the Reporting province/territory field on an input patient record

KBM1

Purpose

This edit ensures that no duplicate patient keys are posted to the CCR.

Referenced fields (KBM1)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P4 1 Patient record type PRECTYPE

Business rules

For Add Patient records
  • There must not be a Base patient record with identical Reporting province/territory and Patient identification number.
Edit logic (KBM1)
Sub–edit Conditions Outcome
KBM1-1 Input patient record where IP4='1' that matches a Base patient record where IP1=BP1 AND IP2=BP2. Record rejected
Feedback report messages (KBM1)
Sub–edit Text Type
KBM1-1 A Base patient record with identical reporting province/Territory and Patient identification number already exists. Core error
Revision (KBM1)
Year Description
2004 Edit renamed: Formerly known as Correlation Edit No.25.

KBM2

Purpose

This edit ensures that update or delete patient record keys match a base patient record.

Referenced fields (KBM2)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P3 9 CCR identification number CCR_ID
P4 1 Patient record type PRECTYPE

Business rules

For Update or Delete Patient records
  • There must be a Base patient record with identical Reporting province/territory, Patient identification number and CCR identification number.
Edit logic (KBM2)
Sub–edit Conditions Outcome
KBM2-1 Input patient record where IP4 IN ['2','3'] that matches a Base patient record where IP1=BP1 AND IP2<>BP2 AND IP3=BP3. Record rejected
KBM2-2 Input patient record where IP4 IN ['2','3'] that matches a Base patient record where IP1=BP1 AND IP2=BP2 AND IP3<>BP3. Record rejected
KBM2-3 Input patient record where IP4 IN ['2','3'] that matches a Base patient record where IP1<>BP1 AND IP3=BP3. Record rejected
KBM2-4 Input patient record where IP4 IN ['2','3'] that match no Base patient record where (IP1=BP1 AND IP2=BP2) OR IP3=BP3. Record rejected
Feedback report messages (KBM2)
Sub–edit Text Type
KBM2-1 Based on the CCR identification number, the Patient identification number is incorrect. Core error
KBM2-2 Based on the Reporting province/territory and the Patient identification number, the CCR identification number is incorrect. Core error
KBM2-3 Based on the CCR identification number, the Patient is owned by another province/territory. Core error
KBM2-4 No matching Patient record found in the CCR. Core error
Revision (KBM2)
Year Description
2004 Edit renamed: Formerly known as Correlation Edit No.26.

KBM3

Purpose

This edit ensures that no duplicate tumour keys are posted to the CCR.

Referenced fields (KBM3)
Field Length Description Acronym
T1 2 Tumour reporting province/Territory TREPPROV
T2 12 Tumour patient identification number TPIN
T3 9 Tumour reference number TTRN
T5 1 Tumour record type TRECTYPE

Business rules

For Add Tumour records
  • There must not be a Base tumour record with an identical Reporting province/territory, Patient identification number and Tumour reference number.
Edit logic (KBM3)
Sub–edit Conditions Outcome
KBM3-1 Input tumour record where IT5='1' that matches a Base tumour record where IT1=BT1 AND IT2=BT2 AND IT3=BT3. Record rejected
Feedback report messages (KBM3)
Sub–edit Text Type
KBM3-1 A Base tumour record with identical Reporting province/territory, Patient identification number and Tumour reference number already exists. Core error
Revision (KBM3)
Year Description
2004 Edit renamed: Formerly known as Correlation Edit No.32 – Part 1.

KBM4

Purpose

This edit ensures that an add tumour record with CCR identification number matches a base patient record owned by the reporting province/territory.

Referenced fields (KBM4)
Field Length Description Acronym
T1 2 Tumour reporting province/territory TREPPROV
T2 9 Tumour patient identification number TPIN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
P1 2 Patient reporting province/territory PREPPROV
P2 9 Patient identification number PPIN
P3 9 CCR identification number CCR_ID

Business rules

For Add Tumour records with CCR identification number
  • There must be a Base patient record with the same Reporting province/territory, Patient identification number and CCR identification number.
Edit logic (KBM4)
Sub–edit Conditions Outcome
KBM4-1 Input tumour record where IT5='1' AND IT4 IS NOT NULL that matches a Base patient record where IT1=BP1 AND IT2<>BP2 AND IT4=BP3. Record rejected
KBM4-2 Input tumour record where IT5='1' AND IT4 IS NOT NULL that matches a Base patient record where IT1=BP1 AND IT2=BP2 AND IT4<>BP3. Record rejected
KBM4-3 Input tumour record where IT5='1' AND IT4 IS NOT NULL that matches a Base patient record where IT1<>BP1 AND IT4=BP3. Record rejected
KBM4-4 Input tumour record where IT5='1' AND IT4 IS NOT NULL that matches no Base patient record where (IT1=BP1 AND IT2=BP2) OR IT4=BP3. Record rejected
Feedback report messages (KBM4)
Sub–edit Text Type
KBM4-1 Based on CCR identification number, Patient identification number is incorrect. Core error
KBM4-2 Based on Reporting province/territory and Patient identification number, CCR identification number is incorrect. Core error
KBM4-3 Based on CCR identification number, the Patient record belongs to another province/territory. Core error
KBM4-4 Matching Base patient record not found. Core error
Revision (KBM4)
Year Description
2004 Edit renamed: Formerly known as Correlation Edit No.32 – Part 2 and Additional rules for updating the CCR #3.
Business rules changed: This aggregated edit is now using the Base Patient records.

KBM5

Purpose

This edit ensures that update or delete tumour record keys match a base tumour record.

Referenced fields (KBM5)
Field Length Description Acronym
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Tumour patient identification number TPIN
T3 9 Tumour reference number TTRN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE

Business rules

For Update and Delete Tumour records
  • There must be a Base tumour record with identical Reporting province/territory, Patient identification number, Tumour reference number and CCR identification number.
Edit logic (KBM5)
Sub–edit Conditions Outcome
KBM5-1 Input tumour record where IT5 IN ['2','3'] that matches a Base tumour record where IT1=BT1 AND IT2=BT2 AND IT3=BT3 AND IT4<>BT4. Record rejected
KBM5-2 Input tumour record where IT5 IN ['2','3'] that matches a Base tumour record where IT1=BT1 AND IT2<>BT2 AND IT4=BT4. Record rejected
KBM5-3 Input tumour record where IT5 IN ['2','3'] that matches no Base tumour record where IT1=BT1 AND IT2=BT2 AND IT3=BT3 but matches a Base tumour record where IT1=BT1 AND IT2=BT2 AND IT3<>BT3 AND IT4=BT4. Record rejected
KBM5-4 Input tumour record where IT5 IN ['2','3'] that matches no Base tumour record where (IT1=BT1 AND IT2=BT2) OR (IT1=BT1 AND IT4=BT4). Record rejected
Feedback report messages (KBM5)
Sub–edit Text Type
KBM5-1 Based on Reporting province/territory, Patient identification number and Tumour reference number, CCR identification number is incorrect. Core error
KBM5-2 Based on CCR identification number and Reporting province/territory, Patient identification number is incorrect. Core error
KBM5-3 Matching Base tumour record not found. Tumour reference number may be incorrect. Core error
KBM5-4 Matching Base tumour record not found. Core error
Revision (KBM5)
Year Description
2004 Edit renamed: Formerly known as Correlation Edit No.33.

3.6.3 Data item match edits

The purpose of the data item match edits is to enforce the business rules between data items (other than keys) found on different records.

The following table summarizes the purpose of each individual edit of this category.

Table 30 Data item match edits summary
Edit name Purpose
DIM1 Ensures that Date of diagnosis and Date of birth are coherent and within time frame.
DIM2 Ensures that Date of diagnosis and Date of death are coherent.
DIM3 Ensures that Method of diagnosis accurately reflects the relationship between Date of diagnosis and Date of death.
DIM4 Ensures that Method used to establish the date of diagnosis accurately reflects the relationship between Date of diagnosis and Date of death.
DIM5 Ensures that patient Sex and tumour Topography are coherent.
DIM6 Ensures that no "duplicate" tumour records are created for any given Patient record.

Important notes:

Writing conventions throughout the following edit descriptions:

  • Expression "base patient/tumour record" means a patient/tumour record already in the CCR.
  • Expression "add/update/delete/input patient/tumour record" means a patient/tumour record within the data submission.
  • Unless specified otherwise, field numbers prefixed with "I" are input fields and field numbers prefixed with "B" are Base fields.
    Example: IT5 is the Tumour record type field on an input tumour record.
    Example: IP1 is the Reporting province/territory field on an input patient record

These edits only consider input records that have neither core fatal errors nor core errors. (See section 3.1.7 Message types for information about different types of errors.) Since DIM edits find core errors, an input record that fails a given DIM edit will automatically be excluded from all subsequent DIM edits.

These edits must be performed in a specific order (see below).

When a data item match edit fails, the conflicting base record (patient or tumour, if any) is included in the detailed feedback report for easier error correction.

3.6.3.1 Special order of execution

Data item match edits must be performed horizontally. That is, all sub-edits with the same number must be processed together. Example: instead of processing all sub-edits from DIM1 before processing all sub-edits from DIM2 (vertically), all sub-edits DIMX-1 must be processed before processing sub-edits DIMX-2 (horizontally). Although the sub-edits within a horizontal group can be processed in any order, these groups of sub-edits must be processed in a very specific order.

Step 1: All sub-edits that consider only input records (Sub-edits number 1 and 4).

Step 2: All sub-edits that consider base patient records that are not updated by input patient records (Sub-edits number 2 and 5).

Step 3: All sub-edits that consider base tumour records that are not updated nor deleted by input tumour records must be processed (Sub-edit number 3 and 6).

The ordering is essential to guarantee the effectiveness of these edits since each step builds the necessary conditions for the next one. The following table summarizes the special order of execution.

Table 31 Data item match edits special order of execution
Edit DIM1 DIM2 DIM3 DIM4 DIM5 DIM6
Sub-edit 1 2 3 4 5 6 1 2 3 1 2 3 4 5 6 1 2 3 4 5 6 1 2 3 1 2 3 4 5 6
Step 1 x     x     x     x     x     x     x     x     x     x    
Step 2   x     x     x     x     x     x     x     x     -     -  
Step 3     x     x     x     x     x     x     x     x     x     x

DIM1

Purpose

This edit ensures that date of diagnosis and date of birth are coherent and within time frame.

Referenced fields (DIM1)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P3 9 CCR identification number CCR_ID
P4 1 Patient record type PRECTYPE
P11 8 Date of birth PDATBIR
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Patient identification number TPIN
T3 9 Tumour reference number TTRN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
T12 8 Date of diagnosis TDATDIAG

Business rules

Date of diagnosis must be on or after the Date of birth.
  • Year of Date of diagnosis and year of the Date of birth must not be more than 117 yearsapart.

Important notes:

  • These sub-edits must be processed in a specific order. See Section - 3.6.3.1 Special order of execution for more details.
  • Partially known dates must be compared using the highest common level of precision.

    Example: If Date1 = YYYYMMDD and Date2 = YYYYMM99 then dates must be compared using the year and month only. Thus, for the purpose of the following sub-edits, '20031002' and '20031099' are equal.
Edit logic (DIM1)
Sub–edit Conditions Outcome
DIM1-1 Core error-free56 Input tumour record where IT5 IN ['1','2'] that matches a Core error-free Input patient record where IP4 IN ['1','2'] AND IP1=IT1 AND IP2=IT2 AND IP11<>'99999999' AND IT12<IP11 (see note above). Tumour record rejected
DIM1-2 Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4 IS NOT NULL that matches no Core error-free Input patient record where IP4='2' AND IP3=IT4 but matches a Base patient record where BP3=IT4 AND BP11<>'99999999' AND IT12<BP11 (see note above). Tumour record rejected
DIM1-3 Core error-free Input patient record where IP4='2' that matches a Base tumour record where IP3=BT4 AND IP11<>'99999999' AND BT12<IP11 (see note above) that matches no Core error-free Input Tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3. Patient record rejected
DIM1-4 Core error-free Input tumour record where IT5 IN ['1','2'] that matches a Core error-free Input patient record where IP4 IN ['1','2'] AND IP1=IT1 AND IP2=IT2 AND IP11<>'99999999' AND IT12.YEAR>(IP11.YEAR+117). Tumour record rejected
DIM1-5 Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4 IS NOT NULL that matches no Core error-free Input patient record where IP4='2' AND IP3=IT4 but matches a Base Patient record where BP3=IT4 AND BP11<>'99999999' AND IT12.YEAR>(BP11.YEAR+117). Tumour record rejected
DIM1-6 Core error-free Input patient record where IP4='2' that matches a Base tumour record where IP3=BT4 AND IP11<>'99999999' AND BT12.YEAR>(IP11.YEAR+117) that matches no Core error-free Input Tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3. Patient record rejected
Feedback report messages (DIM1)
Sub–edit Text Type
DIM1-1 Date of diagnosis is before Date of birth on matching Input patient record. Core error
DIM1-2 Date of diagnosis is before Date of birth on matching Base patient record. Core error
DIM1-3 Date of birth is after Date of diagnosis on matching Base tumour record. Core error
DIM1-4 Date of diagnosis is more than 117 years after Date of birth on matching Input patient record. Core error
DIM1-5 Date of diagnosis is more than 117 years after Date of birth on matching Base patient record. Core error
DIM1-6 Date of birth is more than 117 years before Date of diagnosis on matching Base tumour record. Core error
Revision (DIM1)
Year Description
2004 Edit renamed: Formerly known as Correlation Edit No.28.

DIM2

Purpose

This edit ensures that date of diagnosis and date of death are coherent.

Referenced fields (DIM2)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P3 9 CCR identification number CCR_ID
P4 1 Patient record type PRECTYPE
P14 8 Date of death PDATDEA
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Patient identification number TPIN
T3 9 Tumour reference number TTRN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
T12 8 Date of diagnosis TDATDIAG

Business rules

Tumour Date of diagnosis cannot be after the patient Date of death.

Important notes:

  • These sub-edits must be processed in a specific order. See Section 3.6.3.1 Special order of execution for more details.
  • Partially known dates must be compared using the highest common level of precision.

    Example: If Date1 = YYYYMMDD and Date2 = YYYYMM99 then dates must be compared using the year and month only. Thus, for the purpose of the following sub-edits, '20031002' and '20031099' are equal.
Edit logic (DIM2)
Sub–edit Conditions Outcome
DIM2-1 Core error-free56 Input tumour record where IT5 IN ['1','2'] that matches a Core error-free Input patient record where IP4 IN ['1','2'] AND IP1=IT1 AND IP2=IT2 AND IP14 NOT IN ['99999999','00000000'] AND IP14<IT12 (see note above). Tumour record rejected
DIM2-2 Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4 IS NOT NULL that matches no Core error-free Input patient record where IP4='2' AND IP3=IT4 but matches a Base Patient record where BP3=IT4 AND BP14 NOT IN ['99999999','00000000'] AND BP14<IT12 (see note above). Tumour record rejected
DIM2-3 Core error-free Input patient record where IP4='2' AND IP14 NOT IN ['99999999','00000000'] that matches a Base tumour record where IP3=BT4 AND BT12>IP14 (see note above) that matches no Core error-free Input tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3. Patient record rejected
Feedback report messages (DIM2)
Sub–edit Text Type
DIM2-1 Date of diagnosis is after Date of death on matching Input patient record. Core error
DIM2-2 Date of diagnosis is after Date of death on matching Base patient record. Core error
DIM2-3 Date of death is before Date of diagnosis on matching Base tumour record. Core error
Revision (DIM2)
Year Description
2004 Edit renamed: Formerly known as Correlation Edit No.29.

DIM3

Purpose

This edit ensures that the method of diagnosis accurately reflects the relationship between the date of diagnosis and the date of death.

Referenced fields (DIM3)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P3 9 CCR identification number CCR_ID
P4 1 Patient record type PRECTYPE
P14 8 Date of death PDATDEA
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Tumour patient identification number TPIN
T3 9 Tumour reference number TTRN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
T11 1 Method of diagnosis TMETDIAG
T12 8 Date of diagnosis TDATDIAG
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable

Business rules

For tumours diagnosed between 1992 and 2003
  • Method of diagnosis cannot be 'Death certificate only (DCO)' or 'Autopsy' when the Date of death indicates that the 'Patient is not known to have died'.
  • Method of diagnosis can be anything when Date of death is unknown or equal to Date of diagnosis.
  • Method of diagnosis cannot be 'Death certificate only (DCO)' when Date of diagnosis is before Date of death.57

Important notes:

  • These sub-edits must be processed in a specific order. See Section 3.6.3.1 Special order of execution for more details.
  • Partially known dates must be compared using the highest common level of precision.

    Example: If Date1 = YYYYMMDD and Date2 = YYYYMM99 then dates must be compared using the year and month only. Thus, for the purpose of the following sub-edits, '20031002' and '20031099' are equal.
Edit logic (DIM3)
Sub–edit Conditions Outcome
DIM3-1 Core error-free56 Input tumour record where IT5 IN ['1','2'] AND IT11 IN ['2','6'] AND IT12.YEAR>=1992 AND IT12.YEAR<=2003 that matches a Core error-free Input patient record where IP4 IN ['1','2'] AND IP1=IT1 AND IP2=IT2 AND IP14='00000000' Tumour record rejected
DIM3-2 Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4 IS NOT NULL AND IT11 IN ['2','6'] AND IT12.YEAR>=1992 AND IT12.YEAR<=2003 that matches no Core error-free Input patient record where IP4='2' AND IP3=IT4 but matches a Base patient record where BP3=IT4 AND BP14='00000000' Tumour record rejected
DIM3-3 Core error-free Input patient record where IP4='2' AND IP14='00000000' that matches a Base tumour record where IP3=BT4 AND BT11 IN ['2','6'] AND BT12.YEAR>=1992 AND BT12.YEAR<=2003 that matches no Core error-free Input tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3. Patient record rejected
DIM3-4 Core error-free Input tumour record where IT5 IN ['1','2'] AND IT11='6' AND IT12.YEAR>=1992 AND IT12.YEAR<=2003 that matches a Core error-free Input patient record where IP4 IN ['1','2'] AND IP1=IT1 AND IP2=IT2 AND IP14 NOT IN ['00000000', '99999999'] AND IP14>IT12 (see note above). Tumour record rejected
DIM3-5 Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4 IS NOT NULL AND IT11='6' AND IT12.YEAR>=1992 AND IT12.YEAR<=2003 that matches no Core error-free Input patient record where IP4='2' AND IP3=IT4 but matches a Base patient record where BP3=IT4 AND BP14 NOT IN ['00000000', '99999999'] AND BP14>IT12 (see note above). Tumour record rejected
DIM3-6 Core error-free Input patient record where IP4='2' AND IP14 NOT IN ['00000000', '99999999'] that matches a Base tumour record where IP3=BT4 AND BT11='6' AND BT12.YEAR>=1992 AND BT12.YEAR<=2003 AND BT12<IP14 (see note above) that matches no Core error-free Input tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3. Patient record Rejected
Feedback report messages (DIM3)
Sub–edit Text Type
DIM3-1 Method of diagnosis cannot be 'Death certificate only (DCO)' or 'Autopsy' when the Date of death indicates that the 'Patient is not known to have died' on matching Input patient record. Core error
DIM3-2 Method of diagnosis cannot be 'Death certificate only (DCO)' or 'Autopsy' when the Date of death indicates that the 'Patient is not known to have died' on matching Base patient record. Core error
DIM3-3 Date of death cannot indicate that patient is alive when Method of diagnosis is 'Death certificate only (DCO)' or 'Autopsy' on a matching Base tumour record. Core error
DIM3-4 Method of Diagnosis cannot be 'Death certificate only (DCO)' when Date of diagnosis is before Date of death on matching Input patient record. Core error
DIM3-5 Method of diagnosis cannot be 'Death certificate only (DCO)' when the Date of diagnosis is before Date of death on matching Base patient record. Core error
DIM3-6 Date of death cannot be after Date of diagnosis on a matching Base tumour record where Method of diagnosis is 'Death certificate only (DCO)'. Core error
Revision (DIM3)
Year Description
2004 Edit renamed: Formerly known as Correlation Edit No.30 – Part 1.

DIM4

Purpose

This edit ensures that the method used to establish the date of diagnosis accurately reflects the relationship between date of diagnosis and date of death.

Referenced fields (DIM4)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P3 9 CCR identification number CCR_ID
P4 1 Patient record type PRECTYPE
P14 8 Date of death PDATDEA
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Tumour patient identification number TPIN
T3 9 Tumour reference number TTRN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
T11 1 Method of diagnosis TMETDIAG
T12 8 Date of diagnosis TDATDIAG
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T24 1 Method used to establish the date of diagnosis TMETHUSED

Business rules

For tumours diagnosed between 1992 and 2003
  • Method used to establish the date of diagnosis cannot be ‘Autopsy only' or ‘Death certificate only (DCO)' when Date of death indicates that the 'Patient is not known to have died' or when Date of diagnosis is before Date of death.
  • Method used to establish the date of diagnosis can be anything when Date of death is unknown or equal to Date of diagnosis.

Important notes:

  • These sub-edits must be processed in a specific order. See Section 3.6.3.1 Special order of execution for more details.
  • Partially known dates must be compared using the highest common level of precision.

    Example: If Date1 = YYYYMMDD and Date2 = YYYYMM99 then dates must be compared using the year and month only. Thus, for the purpose of the following sub-edits, '20031002' and '20031099' are equal.
Edit logic (DIM4)
Sub–edit Conditions Outcome
DIM4-1 Core error-free56 Input tumour record where IT5 IN ['1','2'] AND IT12.YEAR>=2004 AND IT24 IN ['3','8'] that matches a Core error-free Input patient record where IP4 IN ['1','2'] AND IP1=IT1 AND IP2=IT2 AND IP14='00000000' Tumour record rejected
DIM4-2 Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4 IS NOT NULL AND IT12.YEAR>=2004 AND IT24 IN ['3','8'] that matches no Core error-free Input patient record where IP4='2' AND IP3=IT4 but matches a Base patient record where BP3=IT4 AND BP14='00000000'. Tumour record rejected
DIM4-3 Core error-free Input patient record where IP4='2' AND IP14='00000000' that matches a Base tumour record where IP3=BT4 AND BT12.YEAR>=2004 AND BT24 IN ['3','8'] that matches no Core error-free Input tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3. Patient record rejected
DIM4-4 Core error-free Input tumour record where IT5 IN ['1','2'] AND IT12.YEAR>=2004 AND IT24 IN ['3','8'] that matches a Core error-free Input patient record where IP4 IN ['1','2'] AND IP1=IT1 AND IP2=IT2 AND IP14 NOT IN ['00000000', '99999999'] AND IP14>IT12 (see note above). Tumour record rejected
DIM4-5 Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4 IS NOT NULL AND IT12.YEAR>=2004 AND IT24 IN ['3','8'] that matches no Core error-free Input patient record where IP4='2' AND IP3=IT4 but matches a Base patient record where BP3=IT4 AND BP14 NOT IN ['00000000', '99999999'] AND BP14>IT12 (see note above). Tumour record rejected
DIM4-6 Core error-free Input patient record where IP4='2' AND IP14 NOT IN ['00000000', '99999999'] that matches a Base tumour record where IP3=BT4 AND BT12.YEAR>=2004 AND BT12<IP14 (see note above) AND BT24 IN ['3','8'] that matches no Core error-free Input tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3. Patient record rejected
Feedback report messages (DIM4)
Sub–edit Text Type
DIM4-1 Method used to establish the date of diagnosis cannot be 'Autopsy Only' or 'Death certificate only (DCO)' when Date of death indicates that the 'Patient is not known to have died' on matching Input Patient record. Core error
DIM4-2 Method used to establish the date of diagnosis cannot be 'Autopsy Only' or 'Death certificate only (DCO)' when Date of death indicates that the 'Patient is not known to have died' on matching Base patient record. Core error
DIM4-3 Date of death cannot indicate that 'Patient is not known to have died' when Method used to establish the date of diagnosis is 'Autopsy Only' or 'Death certificate only (DCO)' on a matching Base tumour record. Core error
DIM4-4 Method used to establish the date of diagnosis cannot be 'Autopsy Only' or 'Death certificate only (DCO)' when Date of diagnosis is before Date of death on matching Input Patient record. Core error
DIM4-5 Method used to establish the date of diagnosis cannot be 'Autopsy Only' or 'Death certificate only (DCO)' when Date of diagnosis is before Date of death on matching Base patient record. Core error
DIM4-6 Date of death cannot be after Date of Diagnosis on matching Base tumour record where Method used to establish the date of diagnosis is 'Autopsy Only' or 'Death certificate only (DCO)' Core error
Revision (DIM4)
Year Description
2004 Edit renamed: Formerly known as Correlation Edit No.30 – Part 2.

DIM5

Purpose

This edit ensures that patient sex and tumour topography are coherent.

Referenced fields (DIM5)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P3 9 CCR identification number CCR_ID
P4 1 Patient record type PRECTYPE
P10 1 Sex PSEX
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Tumour patient identification number TPIN
T3 9 Tumour reference number TTRN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
T15 4 ICD-O-2/3 Topography TICD_O2T

Business rules

  • Tumours diagnosed in female organ must be associated with female patient. Female organs are: ICD-O-2/3 Topography: C510-C589.
  • Tumours diagnosed in male organ must be associated with male patient. Male organs are: ICD-O-2/3 Topography: C600-C639.

Important notes

These sub-edits must be processed in a specific order. See Section – 3.6.3.1 Special order of execution.

DIM5

Edit logic (DIM5)
Sub–edit Conditions Outcome
DIM5-1 (Core error-free56 Input tumour record where IT5 IN ['1','2'] AND IT15 IN [ICD-O-2/3 Topography codes associated to female organ] that matches a Core error-free Input patient record where IP4 IN ['1','2'] AND IP1=IT1 AND IP2=IT2 AND IP10 IN ['1','9'])
OR
(Core error-free Input tumour record where IT5 IN ['1','2'] AND IT15 IN [ICD-O-2/3 Topography codes associated to male organ] that matches a Core error-free Input patient record where IP4 IN ['1','2'] AND IP1=IT1 AND IP2=IT2 AND IP10 IN ['2','9'])
Tumour record rejected
DIM5-2 (Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4 IS NOT NULL AND IT15 IN [ICD-O-2/3 Topography codes associated to female organ] that matches no Core error-free Input patient record where IP4='2' AND IP3=IT4 but matches a Base patient record where BP3=IT4 AND BP10 IN ['1','9'])
OR
(Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4 IS NOT NULL AND IT15 IN [ICD-O-2/3 Topography codes associated to male organ] that matches no Core error-free Input patient record where IP4='2' AND IP3=IT4 but matches a Base patient record where BP3=IT4 AND BP10 IN ['2','9'])
Tumour record rejected
DIM5-3 (Core error-free Input patient record where IP4='2' AND IP10 IN ['1','9'] that matches a Base tumour record where IP3=BT4 AND BT15 IN [ICD-O-2/3 Topography codes associated to female organ] that matches no Core error-free Input tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3)
OR
(Core error-free Input patient record where IP4='2' AND IP10 IN ['2','9'] that matches a Base tumour record where IP3=BT4 AND BT15 IN [ICD-O-2/3 Topography codes associated to male organ] that matches no Core error-free Input tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3)
Patient record Rejected
Feedback report messages (DIM5)
Sub–edit Text Type
DIM5-1 ICD-O-2/3 Topography does not agree with Sex code on matching Input patient record. Core error
DIM5-2 ICD-O-2/3 Topography does not agree with Sex code on matching Base patient record. Core error
DIM5-3 Sex code does not agree with ICD-O-2/3 Topography on a matching Base tumour record. Core error
Revision (DIM5)
Year Description
2004 Edit renamed: Formerly known as COR31.
Business rules changed: Verification is now performed on ICD-O-3 values only.

DIM6

Purpose

This edit ensures that no "duplicate" tumour records are created for any given patient record (1992-2006 data years only). As of 2007 the CCR has adopted SEER rules. New edits will be implemented to adhere to these new rules.

Referenced fields (DIM6)
Field Length Description Acronym
T1 2 Tumour reporting province/territory TREPPROV
T12.YEAR 4 First 4 digits of Date of diagnosis (year of date of diagnosis) Not applicable
T2 12 Tumour patient identification number TPIN
T3 9 Tumour reference number TTRN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
T15 4 ICD-O-2/3 Topography TICD_O2T
T15.SITE 3 First 3 digits of T15 (ICD-O-2/3 Topography site) Not applicable
T15.SUBSITE 1 Last digit of T15 (ICD-O-2/3 Topography sub-site) Not applicable
T19 1 Laterality TLATERAL
T21 4 ICD-O-3 Histology TICD_O3H

Business rules

Definitions
  • Tumours with "equivalent topographies" are tumours that have:
    • The same ICD-O-3 sites56 and sub-sites59or
    • The same ICD-O-3 sites but at least one sub-site is 'Overlapping' (8) or 'NOS' (9) or
    • Overlapping topographies based on Equivalent Topographies for Overlapping and Unspecified Sites63 concordance table.
  • Tumours with "equivalent histologies" are tumours that have:
    • The same ICD-O-3 Histology code or
    • The same histological group based on Equivalent Histologies56 concordance table.
  • A Patient may have multiple Hematopoietic tumours (tumours with ICD-O-3 Histology codes in range 9590-9989) only if they have non-equivalent histologies. (Thus, a patient may not have more than one Hematopoietic tumour in each equivalent histology group, regardless of their respective topography and laterality.)
  • A Patient may have multiple non-Hematopoietic tumours with equivalent topographies and equivalent histologies only if they are found on paired organs with specific (right, left one side involved, origin not specified and bilateral) and different laterality.
See Appendix D – Multiple primary tumours rules for CCR for more detail.

Important notes

These sub-edits must be processed in a specific order. See Section - 3.6.3.1 Special order of execution

Edit logic DIM6)
Sub–edit Conditions Outcome
DIM6–1 Core error-free56 Input tumour record (say A) where A.T5 IN ['1','2'] AND A.T21 IN ['9590'-'9989'] that matches a Core error-free Input tumour record (say B) where B.T5 IN ['1','2'] AND A.T1=B.T1 AND A.T2=B.T2 AND A.T3<>B.T3 AND B.T21 IN ['9590'-'9989'] AND (A.T21=B.T21 OR (A.T21 and B.T21 are equivalent based on reference table Equivalent Histologies)). Tumour records A and B rejected
DIM6-2 Not applicable61 Not applicable
DIM6-3 Core error-free Input tumour record (say A) where A.T5 IN ['1','2'] AND A.T4 IS NOT NULL AND A.T21 IN ['9590'-'9989'] that matches a Base Tumour record (say B) where A.T4=B.T4 AND (A.T1<>B.T1 OR A.T3<>B.T3) AND B.T21 IN ['9590'-'9989'] AND (A.T21=B.T21 OR (A.T21 and B.T21 are equivalent based on reference table Equivalent Histologies)) that matches no Core error-free Input tumour record (say C) where C.T5 IN ['2','3'] AND C.T1=B.T1 AND C.T2=B.T2 AND C.T3=B.T3. Tumour record A rejected
DIM6-4 Core error-free Input tumour record (say A) where A.T5 IN ['1','2'] that matches a Core error-free Input tumour record (say B) where B.T5 IN ['1','2'] AND A.T1=B.T1 AND A.T2=B.T2 AND A.T3<>B.T3 AND NOT (A.T21 IN ['9590'-'9989'] AND B.T21 IN ['9590'-'9989']) AND (A.T15=B.T15 OR (A.T15.SITE=B.T15.SITE AND (A.T15.SUBSITE IN ['8','9'] OR B.T15.SUBSITE IN ['8','9'])) OR (A.T15 and B.T15 are equivalent based on Equivalent Topographies for Overlapping and Unspecified Sites)) AND (A.T21=B.T21 OR (A.T21 and B.T21 are equivalent based on Equivalent Histologies)) AND (A.T19 IN ['9','0'] OR B.T19 IN ['9','0'] OR A.T19=B.T19) Tumour records A and B rejected
DIM6-5 Not applicable59 Not applicable
DIM6-6 Core error-free Input tumour record (say A) where A.T5 IN ['1','2'] AND A.T4 IS NOT NULL that matches a Base tumour record (say B) where A.T4=B.T4 AND (A.T1<>B.T1 OR A.T3<>B.T3) AND NOT (A.T21 IN ['9590'-'9989'] AND NOT B.T21 IN ['9590'-'9989']) AND (A.T15=B.T15 OR (A.T15.SITE=B.T15.SITE AND (A.T15.SUBSITE IN ['8','9'] OR B.T15.SUBSITE IN ['8','9'])) OR (A.T15 and B.T15 are equivalent based on Equivalent Topographies for Overlapping and Unspecified Sites)) AND (A.T21=B.T21 OR (A.T21 and B.T21 are equivalent based on Equivalent Histologies)) AND (A.T19 IN ['9','0'] OR B.T19 IN ['9','0'] OR A.T19=B.T19) that matches no Core error-free Input Tumour record (say C) where C.T5 IN ['2','3'] AND C.T1=B.T1 AND C.T2=B.T2 AND C.T3=B.T3. Tumour record A rejected
Feedback report messages (DIM6)
Sub–edit Text Type
DIM6-1 Duplicate Input tumour records of the Hematopoietic system based on ICD-O-3 Histology. Core error
DIM6-2 Not applicable61 Not applicable
DIM6-3 Duplicates an existing Base tumour record of the Hematopoietic system based on ICD-O-3 Histology. Core error
DIM6-4 Duplicate Input tumour records based on ICD-O-3 Topography, ICD-O-3 Histology and Laterality. Core error
DIM6-5 Not applicable59 Not applicable
DIM6-6 Duplicates an existing Base tumour record based on ICD-O-3 Topography, ICD-O-3 Histology and Laterality. Core error
Revision (DIM6)
Year Description
2006 Edit no longer used (only applied for data years 1992-2006). New multiple primary/histology rules adopted.
2004 Edit renamed: Formerly known as Correlation Edit No.34A-F.
Business rule changed: Potential duplicate tumours with unknown laterality are now rejected.
Edit logic changed to allow the addition of a Tumour record that duplicates a Base tumour record that is about to be updated or deleted.

3.6.4 Pre-posting match edits

The purpose of the pre-posting match edits is to identify core error-free4 input records that cannot be posted to the CCR because some other related input records are either missing or have core errors.

The following table summarizes the purpose of each individual edit of this category.

Table 32 Pre-posting edits summary
Edit name Purpose
PPM1 Ensures that no orphan Patient record is created in the CCR.
PPM2 Ensures that no orphan Tumour record is created in the CCR.

PPM1

Purpose

This edit ensures that no orphan patient record is created in the CCR.

Referenced fields (PPM1)
Field Length Description Acronym
T1 2 Tumour reporting province/territory TREPPROV
T2 9 Tumour patient identification number TPIN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
P1 2 Patient reporting province/territory PREPPROV
P2 9 Patient identification number PPIN
P3 9 CCR identification number CCR_ID
P4 1 Patient record type PRECTYPE

Business rules

Every Base patient record must have at least one Base tumour record with the same Reporting province/territory and Patient identification number and CCR identification number.
Edit logic (PPM1)
Sub–edit Conditions Outcome
PPM1-1 Core error-free56 Input patient record where P4='1' that matches no Core error-free Input tumour record where T5='1' AND P1=T1 AND P2=T2. Patient record rejected
PPM1-2 One or more Core error-free Input tumour records with the same IT4 where IT5='3' that match no Core error-free Input patient record where IP4='3' AND IP3=IT4 and match no Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4=IT4 but match a Base Patient record where IT1=BP1 AND IT4=BP3 and match as many Base tumour records where BT1=IT1 AND BT4=IT4. Tumour records rejected
Feedback report messages (PPM1)
Sub–edit Text Type
PPM1-1 Patient record cannot be added because all associated Add Tumour records have been rejected. Core error
PPM1-2 Tumour records cannot be deleted because it would create an orphan Patient record. Core error
Revision (PPM1)
Year Description
2004 Renamed: Formerly known as Additional rules for updating the CCR #2.
Business rules added: Prevent the addition of a new Patient record without Tumour record.

PPM2

Purpose

This edit ensures that no orphan tumour record is created in the CCR.

Referenced fields (PPM2)
Field Length Description Acronym
T1 2 Tumour reporting province/territory TREPPROV
T2 9 Tumour patient identification number TPIN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
P1 2 Patient reporting province/territory PREPPROV
P2 9 Patient identification number PPIN
P3 9 CCR identification number CCR_ID
P4 1 Patient record type PRECTYPE

Business rules

Every Base tumour record must have one Base patient record with the same CCR identification number.
Edit logic (PPM2)
Sub–edit Conditions Outcome
PPM2-1 Core error-free56 Input tumour record where T5='1' AND T4 IS NULL that matches no Core error-free Input patient record where P4='1' AND P1=T1 AND P2=T2. Tumour record rejected
PPM2-2 Core error-free Input patient record where IP4='3' that matches less Core error-free Input tumour records where IT5='3' AND IT4=IP3 than Base tumour Record where BT1=IP1 AND BT4=IP3 Patient record rejected
Feedback report messages (PPM2)
Sub–edit Text Type
PPM2-1 Tumour record cannot be added because associated Add Patient record has been rejected. Core error
PPM2-2 Patient record cannot be deleted because not all related Base tumour records with the same Reporting province/territory have been deleted. Core error
Revision (PPM2)
Year Description
2004 Edit renamed: Formerly known as Additional rules for updating the CCR #1.
Business rules added: Prevent the addition of a new Tumour record without a Patient record.

3.7 Data posting

Description

The data posting phase is the actual registration of validated data on the CCR database. During this phase, successfully validated input records are added, updated or deleted from the CCR database in accordance with the operation specified by the PTCR on each record. Depending on the operation, a CCR identification number is generated and some derived variables are computed.

In addition to the data registration, the data posting phase also updates auxiliary tables used by other processes such as internal record linkage and death clearance. These tables are:

  • Deleted CCR ID,
  • Alternate surnames,
  • Internal Record Linkage – Don't Link Cross Reference table,
  • Death Clearance – Don't Link Cross Reference.

The content and purpose of the above tables are described in Appendix F – Auxiliary tables

Organization

This section is organized as follow:

Data posting
Sub–section Description
3.7.1 Add Patient record processing
How Input records are processed based on the operation and the record type.
3.7.2 Add Tumour record processing
3.7.3 Update Patient record processing
3.7.4 Update Tumour record processing
3.7.5 Delete Patient record processing
3.7.6 Delete Tumour record processing
3.7.7 Patient Derived variable calculations
How patient and tumour derived variables are computed.
3.7.8 Tumour Derived variable calculations

Writing Conventions

Throughout the following pages, the prefixes "I" and "B" preceding field numbers indicate input or base fields respectively. These prefixes are used to indicate the origin of the corresponding variable in expressions.

Example: IP6 stands for P6 variable on an input record.
Example: BTD2 stands for TD2 variable on a base record

3.7.1 Add patient record processing

For each successfully validated add patient record, the following actions are conducted:

A new base patient record is created using:

  • CCR identification number (P3): A new CCR identification number (see below);
  • Core data items (P1 to -P19 except P4 – input record type): corresponding input record variables values;
  • Derived variables (PD1 to PD8): applicable patient derived variables values (see 3.7.7 patient derived variable calculations).

3.7.1.1 CCR identification number creation

The logic to create a new CCR identification number is the following:

LET
  • Today _Year4 be the year of today's date (4 digits).
  • Today_Year2 be the last two digits of the year of today's date (2 digits).
  • Last_CCRID_Year4 be the year the last CCR identification number was created (4 digits).
  • CCR_sequence_number be the numeric sequence used to create the CCR identification number (6 digits).
  • Check_Digit be a placeholder for the new CCR ID check digit (1 digit)
  • New_CCR_ID be a placeholder for the new CCR identification number (9 digits).
  • Check_Digit() be a function that returns a check digit based on the logic described in Appendix X – CCR_ID Check Digit Routine.
  • || be a string operator that concatenates two text strings together.
BEGIN
  • IF Last_CCRID_Year4 < Today_Year4THEN
  • CCR_Sequence_Number = '000000';
  • Last_CCRID_Year4 =Today _Year4;
  • End IF;
  • Check_Digit = Check_Digit (Today _Year2 || CCR_Sequence_Number)
  • New_CCR_ID = Today _Year2 || CCR_Sequence_Number ||Check_Digit
  • CCR_Sequence_Number =CCR_Sequence_Number + 1;/
  • RETURN New_CCR_ID;
END;

3.7.2 Add tumour record processing

For each add tumour record where the core data items (T1 to T26) are valid, the following actions are conducted:

A new base tumour record is created using:

  • Core data items (T1 to T26 except T5 – Input record type): corresponding input core data items;
  • CCR identification number (T4): reported CCR identification number or, if missing, the CCR identification number assigned to the corresponding new patient record (Patient record with the same reporting province/territory and patient identification number);
  • CS data items (T27 to T41 and T52):
    • If the tumour is within the CCR collaborative staging scope and the input CS data items are valid then the input CS data items are used.
    • If the tumour is within the CCR collaborative staging scope but the input CS data items are invalid then the corresponding base data items are "R" filled.
    • If the tumour is outside the CCR collaborative staging scope then NULL values are used.
  • AJCC TNM data items (T42 to T51):
    • If the tumour is within the CCR AJCC TNM staging scope and the input AJCC TNM data items are valid then the input AJCC TNM data items are used.
    • If the tumour is within the CCR AJCC TNM staging scope but input AJCC TNM data items are invalid then the corresponding base data items are "R" filled.
    • If the tumour is outside the CCR AJCC TNM staging scope then NULL values are used.
  • Derived data items (TD1 to TD20): applicable tumour derived variables values (see 3.7.8 Tumour derived variable calculations).

3.7.3 Update patient record processing

For each successfully validated Update patient record, the following actions are conducted:

  • Alternate surname table is updated (see below);
  • Death Clearance – Don't Link Cross Reference table is updated (see below);
  • Corresponding base patient record is updated using:
    • Core data items (P1 to P19 except P4 – Input record type): all input record variable values,
    • Derived variables (PD1-PD8): applicable patient derived variables values (see 3.7.7 Patient derived variable calculations).

3.7.3.1 Alternate surname table update

Alternate surname table is updated as following:


Let P3 be the CCR identification number
Let P6 be the patient Current Surname
IF BP6 IS NOT NULL AND (IP6 IS NULL OR IP6 <> BP6) AND (BP3, BP6 combination NOT IN [Alternate Surname table]) THEN
BP3, BP6 combination is added to Alternate Surname table.
END IF

See Appendix F – Auxiliary Tables – Alternate surname for more details.

3.7.3.2 Death Clearance – Don't Link Cross Reference Table Update

If a base Patient is Death-Cleared and the corresponding Input transaction resets all Death Information, the Death Confirmation is said to be Refused and the Death Clearance – Don't Link Cross Reference Table is updated as follows;

Let P3 be the CCR Identification Number
Let P14 be the patient Date of Death
Let P15 be the patient Province/Territory or Country of Death
Let P16 be the patient Death Registration Number
Let P17 be the patient Underlying Cause of Death
Let P18 be the patient Autopsy Confirming Cause of Death
Let PD5 be the Death Clearance Status
IF (BPD5='2' AND IP14='00000000' AND IP15='000' AND IP16='000000' AND IP17='0000' AND IP18='0') THEN
BP3, BP14, BP15, BP16 combination is added to Death Clearance – Don't Link Cross Reference table.
END IF

See Appendix F – Auxiliary Tables – Death Clearance – Don't Link Cross Reference Table for more details.

3.7.4 Update tumour record processing

For each update tumour record where the core data items (T1 to T26) are valid, the following actions are conducted:

  • Corresponding base tumour record is updated using:

Core data items (T1 to T26 except T5 – Input record type): Corresponding input core data items;
CS data items (T27 to T41, and T52):

  • If the tumour is within the CCR collaborative staging scope and the input CS data items are valid then the input CS data items are used.
  • If the tumour is within the CCR collaborative staging scope but the input CS data items are invalid then the corresponding base data items are "R" filled.
  • If the tumour is outside the CCR collaborative staging scope then NULL values are used.

AJCC TNM data items (T42 to T51):

  • If the tumour is within the CCR AJCC TNM stagingscope and the input AJCC TNM data items are valid then the input AJCC TNM data items are used.
  • If the tumour is within the CCR AJCC TNM staging scope but input AJCC TNM data items are invalid then the corresponding base data items are "R" filled.
  • If the tumour is outside the CCR AJCC TNM staging scope then NULL values are used.

Derived data items (TD1 to TD20): applicable tumour derived variables values (see 3.7.8 Tumour derived variable calculations)

3.7.5 Delete patient record processing

For each successfully validated delete patient record, the following actions are conducted:

  • Deletion or reversal of ownership of the corresponding base patient record (see below);
  • If reversal of ownership takes place, corresponding patient derived variables are updated (See3.7.7 Patient derived variable calculations).

If true patient record deletion takes place:

  • Deleted CCR_ID table is updated (see below);
  • Alternate surname table is updated (see below);
  • Internal Record Linkage – Don't Link Cross Reference table is updated (see below);
  • Death Clearance – Don't Link Cross Reference table is updated (see below).

3.7.5.1 Patient record deletion or reversal of ownership

A reversal of ownership is needed when a PTCR deletes a patient record but does not own all related tumours records (that is, at least one related tumour record is owned by another jurisdiction). In such case, the Patient record cannot be deleted from the database because it would otherwise create orphan tumour records. In lieu, the ownership (express by P1 – Patient Reporting Province/Territory and P2 – Patient Identification Number values) of the existing base patient record is changed to the jurisdiction that owns Patient's Last Diagnosed Tumour among remaining tumour records.

The Patient's Last Diagnosed Tumour is based on Date of Diagnosis (TDATDIAG) sorted in chronological order and the following additional rules:

When sorting in chronological order tumours based on the Date of Diagnosis, less precise dates must come before more precise dates. For example, if one tumour has a Date of Diagnosis of ‘19951099' and another tumour has a Date of Diagnosis of ‘19959999', then the tumour with the Date of Diagnosis of ‘19951099' is considered the Latest Tumour.
When two or more tumours share the same Date of Diagnosis, tumours are sorted in ascending order by Tumour Reference Number (TTRN), Health Insurance Number (THIN) and Reporting Province Code (TREPPROV) using an alphabetic comparison method63.
For example, if two tumours have the same Date of Diagnosis but one tumour has TTRN='2' and the other has a TTRN='12345', then the latest tumour will be the one with TTRN='2'.

The following box shows the conditions that need to be assessed and the action that must be performed when processing a delete patient record.


Let P1 be Patient reporting province/territory.
Let P2 be Patient Identification Number.
Let P3 be Patient CCR identification number.
Let T1 be Tumour reporting province/territory.
Let T2 be Tumour Patient Identification Number.
Let T4 be Tumour CCR identification number.
Let T12 be Tumour Date of diagnosis.
Let Patient Last Diagnosed Tumour () be a function that returns the latest diagnosed tumour based on the rules specified above.
IF [Base tumour records where BT4 = IP3 AND BT1 <> IP1] IS NOT NULL THEN
-- Reversal of Ownership: BP1 – Base patient reporting province/territory is updated.
BP1 and BP2 = BT1 and BT2 from Patient Last Diagnosed Tumour ([Base tumour record
where BT4 = IP3 AND BT1 <> IP1 AND MAX(BT12)])
ELSE
-- True Patient Deletion must take place
The corresponding Base record is deleted.
END IF

Since the corresponding base patient record is not really deleted from the CCR when a reversal of ownership occurs, the applicable patient derived variables must be updated.

3.7.5.2 Deleted CCR_ID Table update

When a true patient record deletion takes place (contrary to a reversal of ownership), a new entry in Deleted CCR_ID table must be created as following:

Deleted CCR_ID Table update
Deleted CCR_ID table variable Values
CCR identification number IP3
Reporting province/territory IP1
Patient identification number IP2
Date of Deletion Today's date using YYYYMMDD format.
New CCR_ID [blank]
Process 1

See Appendix F – Auxiliary Tables – Deleted CCR_ID for more details.

3.7.5.3 Alternate surname table update

When a true patient record deletion takes place (contrary to a reversal of ownership), all corresponding entries in the alternate surname table (if any) must be deleted as well.

See Appendix F – Auxiliary tables – Alternate surname for more details.

3.7.5.4 Internal Record Linkage – Don't Link Cross Reference Table Update

When a true Patient record deletion takes place (contrary to a reversal of ownership), all corresponding entries in the Internal Record Linkage – Don't Link Cross Reference table (if any) must be deleted as well.

See Appendix F – Auxiliary tables – IRL DLCR for more details.

3.7.5.5 Death Clearance – Don't Link Cross Reference Table Update

When a true Patient record deletion takes place (contrary to a reversal of ownership), all corresponding entries in the Death Clearance - Don't Link Cross Reference table (if any) must be deleted as well.

See Appendix F – Auxiliary tables – DC DLCR for more details.

3.7.6 Delete tumour record processing

For each successfully validated delete tumour record, the following actions are conducted:

Deletion of the corresponding base Tumour record.

3.7.7 Patient derived variable calculations

The following table depicts how patient derived variables are calculated depending on the operation that takes place. See corresponding variable description pages in Chapter 2 for code meaning.

Table 33 Patient derived variable calculations
Operation variable Add patient Update patient Reversal of ownership (Deletepatient)
PD1 - Processing date – Patient record
Each time a Patient record is written (created or updated), the date of the transaction is saved.

PD1 = Today's date using YYYYMMDD format.
PD2 - Vital status
Not applicable: These variables are only derived for Tabulation master files. See Chapter 4 Tabulation master files for more detail.
PD3 – Number of tumours
PD4 - Death clearance cut Off date Patient never underwent Death clearance

PD4 = '00000000'
PD4 stays the same.
PD5 - Death clearance Status Patient never underwent Death clearance

PD5 = '0'
If the Patient is Death-Cleared and Patient date of death and/or province/territory/country of death and/or Death registration number is changed, then the Patient record is no longer Death-Cleared (Death Clearance Reversal)

Let P14 be the patient Date of death
Let P15 be the patient province/territory or country of death
Let P16 be the patient Death registration number
Let PD5 be the Death Clearance Status
Let PD6 be the Death Clearance Method
Let PD7 be the Death clearance underlying cause of death
Let PD8 be Date of death (Un) Confirmation
IF BPD5 = '2' AND (IP14<>BP14 OR IP15<>BP15 OR IP16<>BP16) THEN
PD5 = '3'
PD6=‘0'
PD7='0000'
PD8=Today's date using YYYMMDD format
ELSE
PD5 stays the same.
PD6 stays the same.
PD7 stays the same.
PD8 stays the same.
END IF
PD5 stays the same.

3.7.8 Tumour derived variable calculations

The following table depicts how tumour derived variables are calculated depending on the operation that takes place. See corresponding variable description pages in Chapter 2 for code meaning.

Table 34 Tumour derived variable calculations
Operation variable Add tumour Update tumour
TD1 – Processing date – Tumour record Each time a Tumour record is written (created or updated), the date of the transaction is saved.

TD1 = Today's date using YYYYMMDD format.
TD2 – Sequence number Not applicable: these variables are only derived for Tabulation master files. See Chapter 4 Tabulation master files for more detail.
TD3 – Age at diagnosis
TD4 – Age group at diagnosis
TD5 – Survival interval
TD6 – Survival censor
TD7 – Derived AJCC T
TD8 – Derived AJCC N
TD9 – Derived AJCC M
TD10 – Derived AJCC T descriptor
TD11 – Derived AJCC N descriptor
TD12 – Derived AJCC M descriptor
TD13 – Derived AJCC stage group
TD14 – Derived AJCC flag
TD15 – Derived SS1977
TD16 – Derived SS1977 flag
TD17 – Derived SS2000
TD18 – Derived SS2000 flag
TD19 – CS version latest

Chapter 4 – Tabulation master files

  • Description
  • Scope
  • Content and layout
  • Derived variables calculations
  • Confidentiality

4.1 Description

The Tabulation master file (TMF) produced from the Canadian Cancer Registry (CCR) serves as a snapshot of the entire CCR database. The resulting flat file merges the patient and tumour records from the CCR, using the unique patient record identifier (CCR identification number) to produce a composite record containing both patient and tumour information, with one record for each tumour.

The TMF is used by researchers, academics, regional health unit personnel, health policy/program planners and decision-makers, epidemiologists and public health professionals. It is provided to representatives from organizations such as Health Canada, the Public Health Agency of Canada, the Canadian Institute for Health Information, and other health-related non-government organizations in accordance with applicable legal agreements and Statistics Canada's guidelines pertaining to release of confidential information. It is created on a yearly basis or, in some instances, as warranted by operational requirements.

See http://www.statcan.ca/english/about/privact.htm section 4.5 Confidentiality

4.2 Scope

There are 2 versions of the tabulation master file, the Canadian Cancer Registry tabulation master file (CCRTMF) and the International Agency for Research on Cancer tabulation master file (IARCTMF). These two versions differ in scope as different rules for determining multiple primary neoplasms are applied.

In addition, each of the TMF can either be national (based on patients from all PTCRs) or provincial/territorial (based on patients from only one PTCR). Provincial/territorial TMFs are based on the ownership of Patient records, i.e. tumours are selected based on the reporting province or territory of its related patient record regardless of the province or territory that actually owns the tumour record itself.

4.2.1 CCRTMF – Canadian Cancer Registry tabulation master file.

Variations exist between provincial/territorial Cancer Registries in the coding practices for multiple primaries. Many registries adhere to CCR rules while others use IARC (Québec), IARC/Berg (Ontario) and SEER (Alberta from 1994) for recording tumours in their registries. Given that all cancer records submitted to the CCR are subjected to specific CCR rules for determining multiple primary tumours (see Appendix D – Multiple primary tumours rules for CCR for more details), the resulting CCRTMF consists of a mixture of IARC and CCR rules for determining multiple tumours. As of 2007 the CCR has adopted SEER rules.

4.2.2 IARCTMF – International agency for research on cancer (IARC) tabulation master file

Important note: IARCTMF implementation has changed in 2004. See Revision box at the end of this section for details.

Since not all registries follow the CCR standards, the annual release of cancer incidence and survival statistics are disseminated from STC using the IARC rules for determining multiple primary tumours for the purpose of comparability between registries over time.

All tumour records on IARCTMF have been selected from the CCR according to IARC coding rules for determining multiple primary tumours as specified by the IARC/IACR's Working Groups' Recommendations for coding Multiple Primaries. The International Classification of Diseases for Oncology – Third Edition outlines the rules as follows:

A working party of IARC recommended definitions of multiple neoplasms for the purpose of incidence reporting for international comparison. Their recommendations are:
  1. Recognition of the existence of two or more primary cancers does not depend on time.
  2. A primary cancer is one that originates in a primary site or tissue and is neither an extension, nor a recurrence, nor a metastasis.
  3. Only one tumour shall be recognized as arising in an organ or pair of organs or tissue. For tumours where site is coded by the first edition of ICD-O (or by ICD-9), an organ or tissue is defined by the three-character category of the topography code.

    ICD-1O and the Second and Third editions of ICD-O have a more detailed set of topography codes. The sites covered by some groups of codes are considered to be a single organ for the purposes of defining multiple tumours. These topography code groups are shown in Table 24*.

    Multifocal tumours – that is, discrete masses apparently not in continuity with other primary cancers originating in the same primary site or tissue, for example bladder – are counted as a single cancer.

    Skin cancer presents a special problem as the same individual may have many such neoplasms over a lifetime. The IARC/IACR rules imply that only the first tumour of a defined histological type, anywhere on the skin, is counted as an incident cancer unless, for example, one primary was a malignant melanoma and the other a basal cell carcinoma.
  4. Rule 3 does not apply in two circumstances: 4.1. For systemic or multicentric cancers potentially involving many discrete organs, four histological groups – lymphomas, leukemias, Kaposi sarcoma, and mesothelioma (groups 7, 8, 9 and 10 in Table 25*) – are included. They are counted only once in any individual.
    4.2. Other specific histologies – groups 1, 2, 3, 4, 6, and 11 in Table 25 – are considered to be different for the purpose of defining multiple tumours. Thus, a tumour in the same organ with a ‘different' histology is counted as a new tumour. Groups 5 and 12 include tumours that have not been satisfactorily typed histologically and cannot therefore be distinguished from the other groups.
- Source International Classification of Diseases for Oncology – Third Edition, page 35

"* "Table 24" and "Table 25" are reproduced on the following pages.

Table 24 Groups of topography codes from ICD-O-2 and ICD-O-3 considered a single site in the definition of multiple cancers
ICD–O–2/3 Topography codes Description
C01 Base of tongue
C02 Other and unspecified parts of tongue
C05 Palate
C06 Other and unspecified parts of mouth
C07 Parotid gland
C08 Other and unspecified major salivary glands
C09 Tonsil
C10 Oropharynx
C12 Pyriform sinus
C13 Hypopharynx
C23 Gallbladder
C24 Other and unspecified parts of biliary tract
C30 Nasal cavity and middle ear
C31 Accessory sinus
C33 Trachea
C34 Bronchus and lung
C37 Thymus
C38.0 Heart
C38.1-.3 Mediastinum
C38.8 Overlapping lesion of heart, mediastinum and pleura
C38.4 Pleura (visceral, parietal, NOS)
C51 Vulva
C52 Vagina
C57.7 Other specified female genital organs
C57.8-.9 Unspecified female genital organs
C56 Ovary
C57.0 Fallopian tube
C57.1 Broad ligaments
C57.2 Round ligament
C57.3 Parametrium
C57.4 Uterine adnexa
C60 Penis
C63 Other and unspecified male genital organs
C64 Kidney
C65 Renal pelvis
C66 Ureter
C68 Other and unspecified urinary organs
C74 Adrenal gland
C75 Other endocrine glands and related structures
Source: THE SEER PROGRAM CODING AND STAGING MANUAL 2004, Fourth Edition, January 2004, page 9, Surveillance Research Program Division Of Cancer Control And Population Sciences, National Cancer Institute, U.S. Department Of Health And Human Services.
Table 25 Groups of malignant neoplasms considered to be histologically "different" for the purpose of defining multiple tumours (adapted from Berg, 1994)
Group Description ICD-O-3 Histology codes
1 Squamous carcinomas 805 to 808, 812, 813
2 Basal cell carcinomas 809 to 811
3 Adenocarcinomas 814, 816, 819 to 822, 826to 833, 835 to 855, 857, 894
4 Other specific carcinomas 803, 804, 815, 817 to 818, 823 to 825, 834, 856, 858 to 867
(5) Unspecified carcinomas (NOS) 801, 802
6 Sarcomas and soft tissue tumours 868 to 871, 880 to 892, 899, 904, 912 to 913, 915 to 925, 937, 954 to 958
7 Lymphomas 959 to 972
8 Leukemia 980 to 994, 995, 996, 998
9 Kaposi sarcoma 914
10 Mesothelioma 905
11 Other specified types ofcancer 872 to 879, 893, 895 to 898, 900 to 903, 906 to 911, 926 to 936, 938 to 953, 973 to 975, 976
(12) Unspecified types of cancer 800, 997
Source: INTERNATIONAL CLASSIFICATION OF DISEASES FOR ONCOLOGY, Third Edition, 2000, page 37, World Health Organization.

Based on the above rules and tables, the following algorithm is used to eliminate duplicate tumours from the IARC tabulation master files.

Table 35 Algorithm used to eliminate duplicate tumours from IARC TMF

Definitions
Site: Identified by the 3 first digits of the ICD-O-2 Topography code.
Topography Group: See Table 24.
Histology Group: See Table 25.
Systemic and Multicentric groups: 7, 8, 9, 10
Non-Systemic and Non-Multicentric groups: 1, 2, 3, 4, 5, 6, 11, 12
Specific Histology groups: 1, 2, 3, 4, 6, 11
Non-Specific Histology groups: 5, 12
Rule 1: When there is more than one tumour in a subset, keep the tumour with the earliest Date of Diagnosis. If more than one tumour has the same Date of Diagnosis, then the tumour with the lowest TTRN, TPIN and TREPPROV is kept.
Logic
For a given patient with more than one tumour:
For Systemic and Multicentric Tumours:
Eliminate duplicate tumours in each Systemic and Multicentric Group using Rule1(regardless of the Site).
For Non-Systemic and Non-Multicentric Tumours:
Eliminate duplicate tumours within the same Site and same Specific Histology group using Rule1;
Eliminate duplicate tumours within the same Site and any Non-Specific Histology group using Rule1;
Eliminate all tumours within Non-Specific Histology groups when there is at least one tumour within Specific Histology groups for the same Site;
Eliminate duplicate tumours within the same Topography group and same Specific Histology group using Rule 1;
Eliminate duplicate tumours within the same Topography group and any Non-Specific Histology group using Rule 1;
Eliminate all tumours within Non-Specific Histology groups when there is at least one tumour within Specific Histology groups for the same Topography group

When a patient has only two tumours, it may be easier to use the following decision tree instead of the above algorithm to assess if tumours are duplicates. When a patient has more than two tumours, the above algorithm must always be used to eliminate duplicate tumours since the decision tree does not indicate the order in which to process tumours pairs which in turn may lead to incorrect results.

Figure 1 Decision tree to assess if two tumours are duplicates based on IARC rules

Figure 1 Decision tree to assess if two tumours are duplicates based on IARC rules
Revision (Description)
Year Description
2007 Table 24 changed:Topography group added: C38.4
2004 Table 24 changed: The latest SEER "Table 24" definition has been implemented.

Topography groups removed: C19, C20; C40, C41;

Topography groups added: C37, C38.0-3 and C38.8; C51, C52, C57.7 and C57.8-9; C56 and C57.0-4;

Algorithm changed:

Systemic and Multicentric tumours: IARC criteria are applied regardless of the CCR Multiple Primary rules.

Duplicate tumours within the same Histology group and with the same Date of Diagnosis: In this case, only the tumour with the lowest Tumour Reference Number, Patient identification number and Reporting Province/Territory Code is kept. This was needed to guarantee that the tumour selected is always the same when the Date of Diagnosis is the same for all tumours.

Histology group 5 vs 12: These two groups are now considered the same for the purpose of finding duplicate tumours.

Specific Histology groups vs Non-Specific Histology groups: A condition has been added to deal with duplicate tumours from different Histology groups where specific and non-specific histologies have been reported. In this case, only tumours with specific histology are kept, regardless of the Date of Diagnosis.

4.3 Content and layout

The TMF includes all variables on the patient and tumour records as provided by PTCRs (except for Fields P4 and T5, the patient and tumour record types) plus additional variables that are derived from the input variables or brought in from other sources by the CCR. (See Chapter 2 Data dictionary for more information about each variable.)

The record layout for both CCR and IARC tabulation master files is as follows.

Table 36 TMF record layout
Field Length Position Description Acronym
P1 2 1 - 2 Patient reporting province/territory PREPPROV
P2 12 3 - 14 Patient identification number PPIN
P3 9 15 - 23 CCR identification number CCR_ID
P5 1 24 - 24 Type of Current surname PTYP_CUR
P6 25 25 - 49 Current surname PCURSNAM
P7 15 50 - 64 First given name PGNAME_1
P8 15 65 - 79 Second given name PGNAME_2
P9 7 80 - 86 Third given name PGNAME_3
P10 1 87 - 87 Sex PSEX
P11 8 88 - 95 Date of birth PDATBIR
P12 3 96 - 98 Province/territory or country of birth PPROVBIR
P13 25 99 - 123 Birth surname PBIRNAM
P14 8 124 - 131 Date of death PDATDEA
P15 3 132 - 134 Province/territory or country of death PPROVDEA
P16 6 135 - 140 Death registration number PDEAREG
P17 4 141 - 144 Underlying cause of death PCAUSDEA
P18 1 145 - 145 Autopsy confirming cause of death PAUTOPSY
P19 8 146 - 153 Patient date of transmission PDATTRAN
PD1 8 154 - 161 Processing date – patient record PDCCRDATPROC
PD2 1 162 - 162 Vital status PDCCRVITALST
PD3 2 163 - 164 Number of tumours PDCCRNBRTMRS
PD4 8 165 - 172 Death clearance cut off date PDDCDATCO
PD5 1 173 - 173 Death clearance status PDDCSTAT
PD6 1 174 - 174 Death clearance method PDDCMETH
PD7 4 175 - 178 Death clearance underlying cause of death PDDCUCD
PD8 8 179 - 186 Date of death (Un) confirmation PDDCDATCN
T1 2 187 - 188 Tumour reporting province/territory TREPPROV
T2 12 189 - 200 Tumour patient identification number TPIN
T3 9 201 - 209 Tumour reference number TTRN
T6 25 210 - 234 Name of place of residence TPLACRES
T7 6 235 - 240 Postal code TPOSTCOD
T8 7 241 - 247 Standard geographic code TCODPLAC
T9 9 248 - 256 Census tract TCENTRAC
T10 15 257 - 271 Health insurance number THIN
T11 1 272 - 272 Method of diagnosis TMETHDIAG
T12 8 273 - 280 Date of diagnosis TDATDIAG
T13 4 281 - 284 ICD-9 cancer code TICD_9
T14 1 285 - 285 Source classification flag TSCF
T15 4 286 - 289 ICD-O-2/3 Topography TICD_O2T
T16 4 290 - 293 ICD-O-2 Histology TICD_O2H
T17 1 294 - 294 ICD-O-2 Behaviour TICD_O2B
T19 1 295 - 295 Laterality TLATERAL
T21 4 296 - 299 ICD-O-3 Histology TICD_O3H
T22 1 300 - 300 ICD-O-3 Behaviour TICD_O3B
T23 1 301 - 301 Grade, differentiation or cell indicator TGRADE
T24 1 302 - 302 Method used to establish date of diagnosis TMETHUSED
T25 1 303 - 303 Diagnostic confirmation TMETHCONF
T26 8 304 - 311 Tumour date of transmission TDATTRAN
T27 3 312 - 314 CS tumour size TCSTSIZE
T28 2 315 - 316 CS extension TCSEXTN
T29 1 317 - 317 CS tumour size/ext eval TCSEVAL
T30 2 318 - 319 CS lymph nodes TCSLNODE
T31 1 320 - 320 CS reg nodes eval TCSRNEVAL
T32 2 321 - 322 Regional nodes examined TCSRNEXAM
T33 2 323 - 324 Regional nodes positive TCSRNPOS
T34 2 325 - 326 CS mets at dx TCSMDIAG
T35 1 327 - 327 CS mets Eval TCSMEVAL
T36 3 328 - 330 CS site-specific factor 1 TCSSSF1
T37 3 331 - 333 CS site-specific factor 2 TCSSSF2
T38 3 334 - 336 CS site-specific factor 3 TCSSSF3
T39 3 337 - 339 CS site-specific factor 4 TCSSSF4
T40 3 340 - 342 CS site-specific factor 5 TCSSSF5
T41 3 343 - 345 CS site-specific factor 6 TCSSSF6
T42 9 346 - 354 AJCC clinical T TAJCCCLINT
T43 3 355 - 357 AJCC clinical N TAJCCCLINN
T44 3 358 - 360 AJCC clinical M TAJCCCLINM
T45 9 361 - 369 AJCC pathologic T TAJCCPATHT
T46 6 370 - 375 AJCC pathologic N TAJCCPATHN
T47 3 376 - 378 AJCC pathologic M TAJCCPATHM
T48 4 379 - 382 AJCC clinical TNM stage group TAJCCCLINSG
T49 4 383 - 386 AJCC pathologic TNM stage group TAJCCPATHSG
T50 4 387 - 390 AJCC TNM stage group TAJCCSG
T51 2 391 - 392 AJCC TNM edition number TAJCCEDNUM
TD1 8 393 - 400 Processing date – tumour record TDCCRDATPROC
TD2 2 401 - 402 Sequence number TDCCRSEQNUM
TD3 3 403 - 405 Age at diagnosis TDCCRAGEDIAG
TD4 2 406 - 407 Age group at diagnosis TDCCRAGEGRP
TD5 5 408 - 412 Survival interval TDDCSURVINT
TD6 1 413 - 413 Survival censor TDDCCENSOR
TD7 2 414 - 415 Derived AJCC T TDCSAJCCT
TD8 2 416 - 417 Derived AJCC N TDCSAJCCN
TD9 2 418 - 419 Derived AJCC M TDCSAJCCM
TD10 1 420 - 420 Derived AJCC T descriptor TDCSAJCCTDESC
TD11 1 421 - 421 Derived AJCC N descriptor TDCSAJCCNDESC
TD12 1 422 - 422 Derived AJCC M descriptor TDCSAJCCMDESC
TD13 2 423 - 424 Derived AJCC stage group TDCSAJCCSG
TD14 1 425 - 425 Derived AJCC flag TDCSAJCCF
TD15 1 426 - 426 Derived SS1977 TDCSSS1977
TD16 1 427 - 427 Derived SS1977 flag TDCSSS1977F
TD17 1 428 - 428 Derived SS2000 TDCSSS2000
TD18 1 429 - 429 Derived SS2000 flag TDCSSS2000F
T52 6 430 - 435 CS version 1st TCSFVER
TD19 6 436 - 441 CS version latest TDCSLVER
T53 1 442 - 442 Ambiguous Terminology Diagnosis TAMBIGTERM
T54 8 443 - 450 Date of conclusive diagnosis TDATCONCLUSDIAG
T55 2 451 - 452 Type of multiple tumours reported as one primary TMULTTUMONEPRIM
T56 8 453 - 460 Date of multiple tumours TDATMULT
T57 2 461 - 462 Multiplicity counter TMULTCOUNT
Revision (Content and layout)
Year Description
2008 Addition of T53 to T57
2007 Addition of T52, deletion of TD20

4.4 Derived variable calculations

Most of the derived variables found on the tabulation master file are used and updated by the CCR System main processes (namely data loading, internal record linkage and death clearance process). Thus, these variables are already available at tabulation master file (TMF) creation time and do not need to be recalculated. Variables that are not used by the CCR System main processes must be derived at TMF creation time. The following table shows which variables are derived at TMF creation time and their respective calculation specification.

Table 37 Derived variable calculations at TMF time
Variable Value
PD2 – Vital status  Let P14 be the patient Date of death

IF P14 = ‘00000000' THEN
PD2 = ‘1'
ELSE
PD2 = ‘2'
End IF
PD3 – Number of tumours PD3 = Patient's total number of tumours within the applicable TMF scope.
TD2 – Sequence number For a given CCR identification number and TNM scope, tumours are numbered from 1 to N in chronologic order based on the Date of diagnosis. If two or more tumours share the same Date of diagnosis, then tumours are ordered by Reporting province/territory and Tumour reference number in ascending order.

TD2 = Sequence number based on the above definition.
TD3 – Age at diagnosis If the Patient date of birth is unknown, then Age at diagnosis cannot be calculated. Otherwise, Age at diagnosis is calculated using Patient date of birth and the tumour Date of diagnosis.

Let INTERVAL_YEARS (Date1, Date2) be a function that returns the number of complete years between Date1 and Date2 as described in Appendix E – Interval and Mean Time Between Dates.
Let P11 be the corresponding Patient date of birth.
Let T12 be the Tumour date of diagnosis.

IF P11 = '99999999' THEN
TD3 = 999
ELSE
TD3 = INTERVAL_YEARS (P11, T12)
END IF
TD4 – Age group at diagnosis TD4 = Corresponding age group based on TD3 value. (See TD4 – Specified values and meaning.)
TD5 – Survival interval
TD6 – Survival censor
If the Patient never underwent Death clearance process; or the Date of diagnosis is after Death clearance cut-off date; or the Method of diagnosis is Death certificate only; or the Method of diagnosis is Autopsy and there is no clear evidence of a positive survival; or the Method used to establish the date of diagnosis is Autopsy or Death certificate only, then the Survival interval is not applicable.
If Survival interval is applicable but Date of death is unknown, then the Survival interval cannot be calculated.
If Survival interval is applicable but the Patient is not known to have died or died after the Death clearance cut-off date, then the Survival interval is calculated using Death clearance cut off date.
If the Survival interval is applicable and the patient died before or on the Death clearance cut-off date, then the Survival interval is calculated using Date of death.

Let INTERVAL_DAYS (Date1, Date2) be a function that returns the number of days between Date1 and Date2 as described in Appendix E – Interval and Mean Time Between Dates.
Let T11 be the Tumour method of diagnosis.
Let T12 be the Tumour date of diagnosis.
Let T24 be the Tumour method used to establish the date of diagnosis.
Let PD4 be the corresponding Patient death clearance cut-off date.
Let P14 be the corresponding Patient Date of death.

IF PD4 = '00000000'
OR T12.YEAR > PD4.YEAR
OR T11 = '6'
OR (T11 = '2' AND P14 = '99999999')
OR (T11 = '2' AND T12.YEAR = P14.YEAR AND (T12.MONTH = '99' OR P14.MONTH = '99'))
OR (T11 = '2' AND T12.YEAR = P14.YEAR AND T12.MONTH = P14.MONTH AND (T12.DAY = '99' OR P14.DAY = '99'))
OR T24 IN ['3', '8'] THEN
TD5 = 99998
TD6 = '0'
ELSE IF P14 = '99999999' THEN
TD5 = 99999
TD6 = '0'
ELSE IF P14 = '00000000' OR P14.YEAR > PD4.YEAR THEN
TD5 = INTERVAL_DAYS (T12, PD4)
TD6 = '2'
ELSE
TD5 = INTERVAL_DAYS (T12, P14)
TD6 = '1'
END IF
TD7 – Derived AJCC T Values returned by the recommended version of the AJCC CS algorithm based on CS Input variables and tumour ICD-O-2/3 Topography and ICD-O-3 Histology.
TD8 – Derived AJCC N
TD9 – Derived AJCC M
TD10 – Derived AJCC T descriptor
TD11 – Derived AJCC N descriptor
TD12 – Derived AJCC M descriptor
TD13 – Derived AJCC stage group
TD14 – Derived AJCC flag
TD15 – Derived SS1977
TD16 – Derived SS1977 flag
TD17 – Derived SS2000
TD18 – Derived SS2000 flag
TD19 – CS version latest
Revision (Derived variable calculations)
Year Description
2007 PD2 – Vital Status is now derived at TMF time

4.5 Confidentiality

In order to respect confidentiality agreements, three different filtering options may be applied to the tabulation master files.

  • No filtering: No fields are hidden. This TMF is used to return data to reporting PTCR and for authorized record linkage activities.
  • No name: All names and Health insurance number fields are hidden. This TMF is used for NAACCR submission.
  • No name, No key: All names, Health insurance number and patient identification number fields are hidden. This TMF is used for dissemination.

The following table explicitly lists which fields are hidden by the different confidentiality filters.

Table 38 Hidden fields on filtered tabulation master files
Sensitive Field Filtering Option
No Filtering No Name No Name, No Key
P2 – Patient Identification Number - - Hidden
P6 – Current Surname - Hidden Hidden
P7 – First Given Name - Hidden Hidden
P8 – Second Given Name - Hidden Hidden
P9 – Third Given Name - Hidden Hidden
P13 – Birth Surname - Hidden Hidden
T2 – Tumour Patient Identification Number - - Hidden
T10 – Health Insurance Number - Hidden Hidden

In order to keep the same record layout for all Tabulation Master Files, hidden fields are simply filled with 'X'.

Appendices

Appendix C – AJCC TNM reference tables
Appendix D – Multiple primary tumours rules for CCR
Appendix E – Interval and mean time between dates
Appendix F – Auxiliary tables
Appendix G – Grade, differentiation or cell indicator guidelines (for T23)
Appendix H – CCR Ambiguous Terms (for T12 and T53)
Appendix I – Guidelines for Abstracting and Determining Death Certificate Only (DCO) Cases for
Provincial/Territorial Cancer Registries (PTCRs) in Canada (for T12 and P18)
Appendix J – Internal between two dates (complete or partial)
Appendix T – Residency guidelines in Canada (for T1, T6, P1)
Appendix X – CCR_ID check digit routine
Appendix Z – References

Appendix C – AJCC TNM reference tables

This appendix describes all AJCC TNM reference tables, namely:

  • Valid AJCC clinical T by site;
  • Valid AJCC clinical N by site;
  • Valid AJCC clinical M by site;
  • Valid AJCC pathologic T by site;
  • Valid AJCC pathologic N by site;
  • Valid AJCC pathologic M by site;
  • Valid AJCC clinical TNM stage group by site;
  • Valid AJCC pathologic TNM stage group by site;
  • Valid AJCC TNM stage group by site;
  • Valid AJCC T, N, M and stage group combination by site

Valid AJCC clinical T by site

Table usage notes:

See Chapter 1 for a complete description of each eligible site in terms of topography, histology and behaviour.

Table 39 Valid AJCC clinical T by stageable site
Breast Prostate Colorectal
TX TX TX
T0 T0 T0
Tis -- Tis
TisDCIS -- --
TisLCIS -- --
TisPagets -- --
T1 T1 T1
T1mic -- --
T1a T1a --
T1b T1b --
T1c T1c --
T2 T2 T2
-- T2a --
-- T2b --
-- T2c --
T3 T3 T3
-- T3a --
-- T3b --
T4 T4 T4
T4a -- --
T4b -- --
T4c -- --
T4d -- --
99 99 99

Valid AJCC clinical N by site

Table usage notes:

See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.

Table 40 Valid AJCC clinical N by stageable site
Breast Prostate Colorectal
NX NX NX
N0 N0 N0
N1 N1 N1
N2 -- N2
N2a -- --
N2b -- --
N3 -- --
N3a -- --
N3b -- --
N3c -- --
99 99 99

Valid AJCC clinical M by site

Table usage notes:

See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.

Table 41 Valid AJCC clinical M by stageable site
Breast Prostate Colorectal
MX MX MX
M0 M0 M0
M1 M1 M1
-- M1a --
-- M1b --
-- M1c --
99 99 99

Valid AJCC pathologic T by site

Table usage notes:

See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.

Table 42 Valid AJCC pathologic T by stageable site
Breast Prostate Colorectal
TX TX TX
T0 -- T0
Tis -- Tis
TisDCIS -- --
TisLCIS -- --
TisPagets -- --
T1 -- T1
T1mic -- --
T1a -- --
T1b -- --
T1c -- --
T2 T2 T2
-- T2a --
-- T2b --
-- T2c --
T3 T3 T3
-- T3a --
-- T3b --
T4 T4 T4
T4a -- --
T4b -- --
T4c -- --
T4d -- --
99 99 99

Valid AJCC pathologic N by site

See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.

Table 43 Valid AJCC pathologic N by stageable site
Breast Prostate Colorectal
NX NX NX
N0 N0 N0
N0i- -- --
N0i+ -- --
N0mol- -- --
N0mol+ -- --
N1 N1 N1
N1mi -- --
N1a -- --
N1b -- --
N1c -- --
N2 -- N2
N2a -- --
N2b -- --
N3 -- --
N3a -- --
N3b -- --
N3c -- --
99 99 99

Valid AJCC pathologic M by site

Table usage notes:

See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.

Table 44 Valid AJCC pathologic M by stageable site
Breast Prostate Colorectal
MX MX MX
M0 M0 M0
M1 M1 M1
-- M1a --
-- M1b --
-- M1c --
99 99 99

Valid AJCC clinical TNM stage group by site

Table usage notes:

See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.

Table 45 Valid AJCC TNM clinical stage group by stageable site
Breast Prostate Colorectal
X X X
0 -- 0
I I I
-- II --
IIA -- IIA
IIB -- IIB
-- III --
IIIA -- IIIA
IIIB -- IIIB
IIIC -- IIIC
IV IV IV
99 99 99

Valid AJCC pathologic TNM stage group by site

Table usage notes:

See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.

Table 46 Valid AJCC TNM pathologic stage group by stageable site
Breast Prostate Colorectal
X X X
0 -- 0
I I I
-- II --
IIA -- IIA
IIB -- IIB
-- III --
IIIA -- IIIA
IIIB -- IIIB
IIIC -- IIIC
IV IV IV
99 99 99

Valid AJCC TNM stage group by site

Table usage notes:

See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.

Table 47 Valid AJCC TNM stage group by stageable site
Breast Prostate Colorectal
0 -- 0
I I I
II61 II II61
IIA -- IIA
IIB -- IIB
III61 III III61
IIIA -- IIIA
IIIB -- IIIB
IIIC -- IIIC
IV IV IV
99 99 99

Valid AJCC T, N, M and stage group combination by site

Table usage notes

  • The following tables assess the validity of the T, N, M and stage group values combination. They can be used to assess either clinical or pathologicvalues.
  • TNM values in the tables include all their sub-values. Thus, the expression ‘T1' includes {T1, T1a, T1b, T1is...}. The actual list of included values depends on the site.
  • In the context of the CCR System, the expression ‘Any T' or ‘Any N' include all their respective sub-values and the value ‘99'. Thus, the expression ‘Any N' includes {99, NX, N0, N1, N1a...}
Table 48 Valid AJCC T, N, M and stage group combination for colorectal sites
Stage Group T N M
0 Tis N0 M0
I T1 N0 M0
I T2 N0 M0
IIA T3 N0 M0
IIB T4 N0 M0
IIIA T1 N1 M0
IIIA T2 N1 M0
IIIB T3 N1 M0
IIIB T4 N1 M0
IIIC Any T N2 M0
IV Any T Any N M1
Table 49 Valid AJCC T, N, M and stage group combination for breast sites
Stage group T N M
0 Tis N0 M0
I T1 N0 M0
IIA T0 N1 M0
IIA T1 N1 M0
IIA T2 N0 M0
IIB T2 N1 M0
IIB T3 N0 M0
IIIA T0 N2 M0
IIIA T1 N2 M0
IIIA T2 N2 M0
IIIA T3 N1 M0
IIIA T3 N2 M0
IIIB T4 N0 M0
IIIB T4 N1 M0
IIIB T4 N2 M0
IIIC Any T N3 M0
IV Any T Any N M1
Table 50 Valid AJCC T, N, M and stage group combination for prostate sites
Stage group T N M
I T1a N0 M0
II T1a N0 M0
II T1b N0 M0
II T1c N0 M0
II T2 N0 M0
III T3 N0 M0
IV T4 N0 M0
IV Any T N1 M0
IV Any T Any N M1

This table has been slightly modified from the AJCC cancer staging manual, 6,th Edition since the CCR system does not consider the grade when validating the stage group and T, N, M values combination

Revision (Valid AJCC T, N, M and stage group combination by site)
Year Description
2008 Table 50: updated Stage group II with T1a, T1b and T1c

Appendix D – Multiple primary tumours rules for CCR

As of 2007 the CCR has adopted SEER rules. New edits will be implemented to adhere to these new rules.

Figure 2 Decision tree to assess CCR Multiple primary tumours

Figure 2 Decision tree to assess CCR Multiple primary tumours

Appendix E – Interval and mean time between dates

The following algorithm can be used to assess the number of days or complete years between two dates. When both dates are complete, the algorithm returns the exact number of days or complete years between the two dates. When one or both dates are partial, the mean number of days or complete years between the two dates is returned. This algorithm cannot be used if one or both dates are totally unknown, i.e. equal to '99999999'. The returned value is always a positive whole number (including zero).

Definitions

Let Date1 and Date2 be the two dates from which the interval must be calculated and where Date1 <= Date2.

Let Y1, M1 and D1 be the year, month and day of date1.
Let Y2, M2 and D2 be the year, month and day of date2.
Let MOD (X, Y) be a function that returns the remainder of X divided by Y.
Let MIDDLE_DAY (Month) be a function that returns the middle day of month using the following logic:

If Month='02' Then
Return '15'
Otherwise
Return '16'

Let LAST_DAY (Year, Month) be a function that returns the last day of the month for the specified year using the following logic:

If Month='02' Then
If (MOD(Y2,4)=0 AND MOD(Y2,100)<>0) OR (MOD(Y2,4)=0 AND MOD(Y2,400)=0) Then
Return '29'
Else
Return '28'
Else If Month in ('04','06','09','11') Then
Return '30'
Else
Return '31'

Let MONTH_BETWEEN (Date1, Date2) be a function that returns the number of months between date1 and date2. If date1 is later than date2, then the result is positive. If date1 is earlier than date2, then the result is negative. If date1 and date2 are either the same days of the month or both last days of months, then the result is always a whole number. Otherwise a fractional portion of the result based on a 31-day month is also added.

Algorithm (Appendix E – Interval and mean time between dates)
Number of days between Date1 and Date2 Number of years between Date1 and Date2
Based on unknown date components and existing conditions between Date1 and Date2, found the right expression to compute the number of days between Date1 and Date2 using the following table.
Evaluate the expression.
Return rounded result.
Based on unknown date components and existing conditions between Date1 and Date2, found the right expression to compute the number complete years between Date1 and Date2 using the following table.
Evaluate the expression.
Return truncated result.
Table 51 Interval and mean time between dates calculation
Unknown date components Conditions Number of days between Date1 and Date2 Number of years between Date1 and Date2
None None Y2/M2/D2 - Y1/M1/D1 MONTH_BETWEEN (Y2/M2/D2, Y1/M1/D1) / 12
D1 Y1=Y2 AND M1=M2 ½ * (Y2/M2/D2 - Y1/M1/01) 0
Otherwise Y2/M2/D2 - Y1/M1/MIDDLE_DAY(M1) MONTH_BETWEEN (Y2/M2/D2, Y1/M1/MIDDLE_DAY(M1)) / 12
D2 Y1=Y2 AND M1=M2 ½ * (Y2/M2/LAST_DAY(Y2,M2) - Y1/M1/D1) 0
Otherwise Y2/M2/MIDDLE_DAY(M2) - Y1/M1/D1 MONTH_BETWEEN (Y2/M2/MIDDLE_DAY(M2), Y1/M1/D1) / 12
D1, D2 Y1=Y2 AND M1=M2 ½ * (Y2/M2/LAST_DAY(Y2,M2) - Y1/M1/MIDDLE_DAY(M1)) [~ 7]
Note: Given the small difference between all possible cases, 7 can be used for all cases.
Case 1: there are 31 days in M1: (31-16)/2=7,5
Case 2: there are 30 days in M1: (30-16)/2=7
Case 3: there are 29 days in M1: (29-15)/2=7
Case 4: there are 28 days in M1: (28-15)/2=6,5
0
Otherwise Y2/M2/MIDDLE_DAY(M2) - Y1/M1/MIDDLE_DAY(M1) MONTH_BETWEEN (Y2/M2/MIDDLE_DAY(M2), Y1/M1/MIDDLE_DAY(M1)) / 12
M1, D1 Y1=Y2 ½ * (Y2/M2/D2 - Y1/01/01) 0
Y1<Y2 Y2/M2/D2 - Y1/07/02 MONTH_BETWEEN (Y2/M2/D2, Y1/07/02) / 12
M2, D2 Y1=Y2 ½ * (Y2/12/31 - Y1/M1/D1) 0
Y1<Y2 Y2/07/02 - Y1/M1/D1 MONTH_BETWEEN (Y2/07/02, Y1/M1/D1) / 12
D1, M2, D2 Y1=Y2 ½ * (Y2/12/31 - Y1/M1/MIDDLE_DAY(M1)) 0
Y1<Y2 Y2/07/02 - Y1/M1/MIDDLE_DAY(M1) MONTH_BETWEEN (Y2/07/02, Y1/M1/MIDDLE_DAY(M1)) / 12
M1, D1, D2 Y1=Y2 ½ * (Y2/M2/MIDDLE_DAY(M2) - Y1/01/01) 0
Y1<Y2 Y2/M2/MIDDLE_DAY(M2) - Y1/07/02 MONTH_BETWEEN (Y2/M2/MIDDLE_DAY(M2), Y1/07/02) / 12
M1, D1, M2, D2 Y1=Y2 ½ * (Y2/12/31 - Y1/07/02) [= 91]
Note: Since the outcome is constant, 91 can be used directly.
0
Y1<Y2 Y2/07/02 - Y1/07/02 MONTH_BETWEEN (Y2/07/02, Y1/07/02) / 12

Used by

  • Data loading – posting.
  • Tabulation master file

Appendix F – Auxiliary tables

This section describes all auxiliary tables used by several processes, namely:

  • Delete CCR ID;
  • Alternate surname;
  • Internal Record Linkage – Don't Link Cross Reference;
  • Death Clearance – Don't Link Cross Reference.

Appendix E – Interval and mean time between dates

Description

This table keeps a log of patient record deletions.

Content

  • CCR identification number: The CCR identification number of the deleted patient record.
  • Reporting province/territory: The reporting province/territory of the deleted patient record.
  • Patient identification number: The patient identification number of the deleted patient record.
  • Date of deletion: The date of the day the patient record was deleted or merged with another.
  • New CCR_ID: The CCR identification number of the remaining patient record when two patient records are merged through internal record linkage resolution.
  • Process: Code indicating which process has deleted the patient record. Possible values are:
    1. Data loading process through posting step.
    2. Internal record linkage through resolution step.

Usage

This table can be used to know how and when a patient record has been deleted. This is especially useful when providing feedback to PTCR about an input patient record that is rejected because the corresponding base patient record is not found on the CCR.

Used By

  • Data loading – posting
  • Internal record linkage
Revision (Appendix E – Interval and mean time between dates)
Year Description
Not applicable Not applicable

Alternate surname

Description

This table keeps a copy of other patient surnames used since a patient enters the CCR.

Content

  • CCR identification number: The CCR identification number of the patient.
  • Surname: Former surname used by the patient.

Usage

This table is used during record linkage activities to augment the chances of a link between two records. This is useful when a patient surname changed overtime. Generally speaking, an additional patient record is created for every alternate patient surname. Doing so will allow a better link between a jurisdiction that uses the former patient surname and another jurisdiction that uses the latter patient surname.

Used By

  • Data loading – posting;
  • Internal record linkage – Record explosion;
  • Death clearance process – Record explosion.
Revision (Alternate surname)
Year Description
Not applicable Not applicable

Internal Record Linkage – Don't Link Cross Reference

Description

This table keeps a log of potential duplicate patient record pairs that have been reviewed and rejected by PTCR through the Internal Record Linkage process.

Content

  • CCR Identification Number 1: The CCR Identification Number of the first patient.
  • CCR Identification Number 2: The CCR Identification Number of the second patient.
  • Resolution Date: The date when the Resolution step of the Internal Record Linkage process has run and has created the entry. (Format: YYYYMMDD)

Usage

This table is used during Internal Record Linkage process to avoid resending for review potential duplicate patient records that have been already reviewed and rejected by PTCR.

Used By

  • Data Loading – Posting;
Internal Record Linkage – Don't Link Cross Reference
Year Description
Not applicable Not applicable

Death Clearance – Don't Link Cross Reference

Description

This table keeps a log of Death Confirmation refused by PTCR through the Death Confirmation Refusal Process.

Content

  • CCR Identification Number: The CCR Identification Number of the patient.
  • Date of Death: The Date of Death as specified on the rejected Death Event (format: YYYYMMDD);
  • Place of Death: The Place of Death as specified on the rejected Death Event;
  • Death Registration Number: The Death Registration Numner as specified on the rejected Death Event
  • Refusal Date: The date when the Death Confirmation Refusal has been processed (Format: YYYYMMDD)

The Year of Death, the Place of Death and the Death Registration Number altogether create a key that uniquely identifies a Death Event.

Usage

This table is used during Death Clearance process to avoid resending for review Death Clearance Confirmation that have been already reviewed and rejected by PTCR.

Used By

  • Data Loading – Posting (Death Confirmation Refusal);
  • Internal Record Linkage – Resolution;
  • Death Clearance – Probabilistic Linkage.
Revision (Death Clearance – Don't Link Cross Reference)
Year Description
2004 Reporting Province and Patient Identification Number have been removed from this table since they are not part of the Patient Primary Key and were not maintained upon Patient Reversal of Ownership.

Appendix G – Guidelines for reporting grade, differentiation or cell indicator

Note: The CCR captures Grade for “invasive” tumours only beginning with January 1, 2004 data to accommodate grade collection in the CS Algorithm. These guidelines apply to January 1, 2006 data.

The CCR does not collect Grade for “in situ” tumours.

All CCR codes are based on the SEER codes as defined in the SEER Program Coding and Staging Manual 2004. The intent is to collect histopathologic grade however there are recognized anatomical site exceptions (for example, kidney) that apply other grading schemes.

Site Specific Grade Guidelines (page 4) take precedence over the General Coding RULES (page 2); use the General Coding Rules only when there are no Site Specific Grade Guidelines.

Grade, Differentiation (Codes 1, 2, 3, 4, 9)

Pathologic testing determines the grade, or degree of differentiation, of the tumour. For cancers, the grade is a measurement of how closely the tumour cells resemble the parent tissue (organ of origin). Well differentiated tumour cells closely resemble the tissue from the organ of origin. Poorly differentiated and undifferentiated tumour cells are disorganized and abnormal looking; they bear little or no resemblance to the tissue from the organ of origin.

Pathologists describe the tumour grade by levels of similarity. Pathologists may define the tumour by describing two levels of similarity (two-grade system); by describing three levels of similarity (three-grade system); or by describing four levels of similarity (four-grade system). The four-grade system describes the tumour as grade I, grade II, grade III, and grade IV (also called well differentiated, moderately differentiated, poorly differentiated, and undifferentiated/anaplastic). These similarities/differences may be based on pattern (architecture), cytology, or nuclear features or a combination of these elements depending upon the grading system that is used. The information from this data item is useful for determining prognosis.

Cell Indicator (Codes 5, 6, 7, 8, 9)

Describes the lineage or phenotype of the cell that became malignant. Cell indicator codes apply to hematopoietic malignancies (ICD-O-3 range 9590-9989) and for these diagnoses cell indicator takes precedence over grade/differentiation. Note: See the ICD-O-3 chapter Morphology (page 67)for further instructions on coding grade.

CCR Codes:

1 Grade I; grade i; grade 1; well differentiated; differentiated, NOS
2 Grade II; grade ii; grade 2; moderately differentiated; moderately well differentiated; intermediate differentiation
3 Grade III; grade iii, grade 3; poorly differentiated; dedifferentiated
4 Grade IV; grade iv; grade 4; undifferentiated; anaplastic
5 T-cell; T-precursor
6 B-Cell; Pre-B; B-precursor
7 Null cell; Non T-non B
8 NK cell (natural killer cell) (effective beginning with diagnosis 1/1/1995)
9 Grade/differentiations unknown, not stated, or not applicable

GENERAL CODING RULES

  1. If there is any confusion relating to grade, we strongly recommend consulting the pathologist for confirmation.

    Example: To determine grade when there are multiple pathology consults.
  2. The site-specific coding guidelines (pages 4-9) include rules for coding grade for the following primary sites: breast, kidney, prostate, CNS, lymphoma, leukemia and sarcoma.
  3. Code the grade from the final diagnosis in the pathology report. If there is more than one pathology report, and the grades in the final diagnoses differ, code the highest grade for the primary site from any pathology report.
  4. If grade is not stated in the final pathology diagnosis, use the information in the microscopic section, addendum, or comment to code grade.
  5. If there is no tissue diagnosis (pathology or cytology report), code the grade from the Magnetic Resonance Imaging (MRI) or Positron Emission Tomography (PET).
  6. If more than one grade is recorded for a single tumour, code the highest grade, even if it is a focus.

    Example: Pathology report reads: Grade II adenocarcinoma with a focus of undifferentiated adenocarcinoma. Code the tumour grade as grade 4, CCR Code 4.
  7. Code the grade information from the consultation or tumour board round if the specimen is sent to a specialty pathology department for a consult.
  8. Code the grade from the primary tumour only, never from a recurrence or metastatic site (distant and/or regional) even if this is theonly reference to grade that you have.
  9. Code the grade for all unknown primaries to 9 (unknown grade) unless grade is implied by histology (i.e. anaplastic carcinoma (grade = 4).
  10. Some terms in ICD-O-3 carry an implied statement of grade. These histologies must be reported with the correct grade as stated below even if the primary site is unknown:
    8020/34 Carcinoma, undifferentiated
    8021/34 Carcinoma, anaplastic
    8331/31 Follicular adenocarcinoma, well differentiated
    9082/34 Malignant teratoma, undifferentiated
    9083/32 Malignant teratoma, intermediate type
    9401/34 Astrocytoma, anaplastic
    9451/34 Oligodendroglioma, anaplastic
    9511/31 Retinoblastoma, differentiated
    9512/34 Retinoblastoma, undifferentiated
  11. Code the grade of the invasive component when the tumour has both in situ and invasive portions. If the invasive component grade is unknown and in situ is graded, code the grade as unknown (9). Note: The CCR does not capture grade for in situ (high dysplasia) cases.
  12. If a patient receives pre-operative systemic treatment for example, chemotherapy, radiotherapy, hormonal etc), code grade:
    – from a pre-treatment pathology report, if available.
    –after pre-operative systemic treatment if this is the only grade information available.

SITE SPECIFIC GRADE GUIDELINES

If the site specific guidelines do not apply or only limited information is available, then refer to the Common Grading Systems tables (page 10) and the Terminology (Four Grade) Conversion Table (page 11).

Exception: Cell indicator takes precedence over grade/differentiation for lymphomas and leukemias.

Breast Cancer

Priority Order for Coding Breast Cancer Grade Code grade in the following priority order (See following table):

  1. Bloom-Richardson (BR) scores 3-9 converted to grade
  2. Bloom Richardson (BR) grade (low, intermediate, high)
  3. Terminology
    a. Differentiation (well differentiated, moderately differentiated, etc)
  4. Histologic grade (Breast Grade NOS, invasive cancer, histologic grade is implied).
    a. Grade 1/I/i, grade 2/II/ii, grade 3/III/iii, grade 4/IV/iv

Note: The conversion of low, intermediate, and high grade for breast is different from the conversion used for all other tumours. Do not use three-grade conversion for breast primaries (see page 10).

Breast Grading Conversion Table
BR Scores BR Grade Terminology Histologic Grade CCR Code
3, 4, 5 Low Well differentiated I/III; 1/3 1
6, 7 Intermediate Moderately differentiated II/III; 2/3 2
8, 9 High Poorly differentiated III/III; 3/3 3

Bloom-Richardson (BR)

  1. BR may also be called: modified Bloom-Richardson, Scarff-Bloom-Richardson, SBR grading, BR grading, Elston-Ellis modification of Bloom Richardson score, the Nottingham modification of Bloom Richardson score, Nottingham-Tenovus, or Nottingham grade
  2. BR may be expressed in scores (range 3-9)The score is based on three morphologic features of “invasive no-special-type” breast cancers (degree of tubule formation/histologic grade, mitotic activity, nuclear pleomorphism of tumour cells)
  3. BR may be expressed as a grade (low, intermediate, high)
  4. BR grade is derived from the BR score
  5. Use the Breast Grading Conversion Table above to convert the score, grade or terminology into the CCR code

Kidney Cancer

Fuhrman grade describes the nucleus of the cell. If Fuhrman grade is not specified, nuclear grade has second priority.For kidney, nuclear grade is more important (priority) than looking at the overall histologic grade of the tumor.

Note: Use the general coding rules for coding grade for Wilms tumour (8960) as these prioritization rules do not apply.

Priority Order for Coding Kidney Cancer Grade

Code grade in the following priority order:

  1. Fuhrman grade (grade 1, 2 ,3 ,4)
  2. Nuclear grade (grade 1, 2, 3, 4)
  3. Terminology (well diff, mod diff)
  4. Histologic grade (grade 1, grade 2)
Fuhrman Conversion Table
Grade Differentiation or Descriptor CCR Code
Grade i Well differentiated 1
Grade ii Moderately differentiated 2
Grade iii Poorly differentiated 3
Grade iv Undifferentiated 4

Prostate

Nuclear grade is not equivalent to any part of the Gleason grading process (cannot be converted from Gleason's Score or Pattern).

Priority Rules for Coding Prostate Cancer Grade

Code grade in the following priority order:

  1. Gleason's Grade (score or pattern)
  2. Terminology
    a. Differentiation (well differentiated, moderately differentiated, etc.)
  3. Histologic grade
    a. Grade 1/I/i, grade 2/II/ii, grade 3/III/iii, grade 4/IV/iv

Use the following table to convert Gleason's pattern or score into CCR codes:

Gleason Conversion Table
Gleason's Score (Gleason's Grade) Gleason's Pattern Terminology Histologic Grade CCR Code
2, 3, 4 1, 2 Well differentiated I 1
5, 6 3 Moderately differentiated II 2
7, 8, 9, 10 4, 5 Poorly differentiated III 3

Note: if Gleason's score or pattern is not specified, see examples below:

Gleason's Pattern

Prostate cancers are commonly graded using Gleason's score or pattern. Gleason's grading is based on a 5-level system, meaning it is based on 5 histologic patterns. The pathologist will evaluate the primary (majority) and secondary patterns for the tumour. The pattern is usually written as a sum, with the majority pattern appearing first and the secondary pattern as the second number.

Example: A Gleason pattern of 2 + 4 means that the primary pattern is 2 and the secondary pattern is 4.

Gleason's Score

The patterns are added together to create a score.

Example: If the pattern is 2 + 4, the score is 6 (the sum of 2 and 4).

When reviewing prostate grading terminology and attempting to determine whether it represents a grade or a score, consider the following results:

  • less than or equal to 5 are coded as a pattern and
  • more than 5 are coded as a score.
  1. If the pathology report contains only one number, and that number is less than or equal to 5, it is a pattern. Please see General Coding Rule 1.
  2. If the pathology report contains only one number, and that number is greater than 5, it is a score. Please see General Coding Rule #1.
  3. If the pathology report specifies a specific number out of a total of 10, the first number given is the score.

    Example: The pathology report says “Gleason's 3/10”. The Gleason's score would be 3.
  4. If there are two numbers less than 6, assume they refer to two patterns. The first number is the primary pattern and the second is the secondary pattern.

    Example: If the pathology report says “Gleason's 3 + 5,” the Gleason's score would be 8, the sum of 3 and 5.

Central Nervous System

  1. WHO grading forbrain is used to estimate prognosis and can refer to both benign and malignant lesions. It is never coded in the 6th digit of the histology code.
    a. WHO grade is captured in Collaborative Stage Site Specific Factor 1.
  2. Pathologists do not always describe ICD-O-3 grade or differentiation of CNS tumors.a. If no grade is given, code the 6th digit histology code to ‘9' unknown.
    b. Some histologies include/imply grade in the terms; in these cases the grade can be coded (for example, anaplastic astrocytoma 9401/34). SeeGeneral Coding Rule 10.
  3. Do not automatically code glioblastoma multiforme as grade IV, if no grade is given, code to ‘9' unknown. (9440/39).
  4. All glioma's with histology 938-946 with the exception of those with an implied grade are ‘9' not applicable.
  5. Grade astrocytomas according to ICD-O-3 rules. Do not use the WHO grade to code this field.

Lymphoma and Leukemia 9590-9989

  1. The designation of T-cell, B-cell, null cell, or NK cell has precedence over any statement of differentiation.
    a. Code ANY statement of T-cell, B-cell, null cell, or NK cell including:
    T-cell (code 5)
    Cortical T
    Mature T
    Pre-T
    Pro-T
    T-cell phenotype
    T-precursor
    B-Cell (code 6)
    B-cell phenotype
    B-precursor
    Pre-B
    Pre-pre-B
    Pro-B
    Null-Cell; Non-T-non-B (code 7)
    Null-cell
    Non T-non-B
    Common cell
    NK (Natural Killer) cell (code 8)
    NK/T cell
    Cell type not determined, not stated or not applicable (code 9)
    Combined B cell and T cell

    Note: The ‘code to the higher code' rule usually does not apply to phenotypes.

    b. Code information on cell type from any source, whether or not marker studies are documented in the patient record.

    Example: The history portion of the medical record documents that the patient has a T-cell lymphoma. There are no marker studies on the chart. Code the grade as T-cell.
  2. Do not use the terms “high grade,” “low grade,” and “intermediate grade” to code differentiation or Cell Indicator field. These terms refer to prognosis, not grade.
    a. In some instances, the term ‘grade' does not imply differentiation and should not be used to code the 6th digit of the morphology code. It is important to recognize when the term “grade” refers to category and when it refers to biologic activity. When describing some diseases, pathologists use the term “grade” as a synonym for “type” or “category.” Registrars recognize the term “grade” as an indicator of cell differentiation that is coded in the 6th digit of the ICD-O morphology code.
    i. The grade descriptors for nodular sclerosing Hodgkin lymphoma and follicular lymphoma are actually types or categories of these diseases. The 6th digit should not be coded as grade 1, 2 or 3 for these cases.
    ii. Poorly differentiated lymphocytic lymphoma or a B-cell or T-cell lymphoma should be coded in the 6th digit of the morphology code.
    iii. Other terms described as high grade or low grade as part of the diagnostic term may be used to code the 6th digit of the morphology code.
  3. Do not code the descriptions “Grade 1,” “Grade 2,” or “Grade 3” in the Grade, Differentiation or Cell Indicator field.
  4. Codes 9950-9989 rarely have a grade associated with them and are generally coded as a ‘9'.
  5. Grade codes 5-8 are T-cell, B-cell, or NK cell indicators used for leukemias and lymphomas only. Therefore, codes 5-8 may only be used with morphologies in the range of 9590-9989.

Sarcoma

Several grading systems exist and may be used to grade sarcomas. The following table incorporates two, three and four-tier grading systems. If a sarcoma is graded using terminology, refer to the Terminology Conversion Table on page 11.

Gleason Conversion Table
Grade Differentiation or Descriptor CCR Code
Low Grade 1/2 1/3 1/4 2/4 2
Intermediate Grade 2/3 3
High Grade 2/2 3/3 3/4 4/4 4

Common Grading Systems

Two-Grade System

There are some cancers for which a two-grade system is used (i.e. colon cancer, papillary transitional cell carcinoma, bladder, endometrial stromal sarcoma). The patterns of cell growth are measured on a scale of 1 or 2 (also referred to as low and high grade). The expected outcome is more favorable for lower grades.

  • If the grade is listed as 1/2 or as low grade, assign code 2.
  • If the grade is listed as 2/2 or as high grade, assign code 4.
Two-Grade Conversion Table
Grade Differentiation /
Description
CCR Code
1/2, I/II Low grade 2
2/2, II/II High grade 4

Three-Grade System

There are several cancers for which a three-grade system is used (for example peritoneum, endometrium, fallopian tube, prostate, bladder and soft tissue sarcoma). The patterns of cell growth are measured on a scale of 1, 2, and 3 (also referred to as low, medium/intermediate, and high grade). This system measures the proportion of cancer cells that are growing and making new cells and how closely they resemble the cells of the host tissue. Thus, it is similar to a four-grade system (see Terminology Conversion Table on page 10), but simply divides the spectrum into 3 rather than 4 categories (see Three-Grade Conversion Table below). The expected outcome is more favorable for lower grades.

  • If the grade is listed as1/3 or as low grade, assign code 2.
  • If the grade is listed as 2/3 or as medium/intermediate grade, assign code 3.
  • If the grade is listed as 3/3 or as high grade, assign code 4.

Use the following table to convert the grade to CCR codes:

Three-Grade Conversion Table*
Grade Differentiation /
Description
CCR Code
1/3, I/III Low grade 2
2/3, II/III Medium/Intermediate grade 3
3/3, III/III High grade 4

*Do not use for breast primaries

Terminology Conversion Table
This system measures the proportion of cancer cells that are growing and making new cells and how closely they resemble the cells of the host tissue. The expected outcome is more favorable for lower grades.

Terminology Conversion Table
Description Grade CCR Code
Differentiated, NOS I 1
Well differentiated I 1
Fairly well differentiated II 2
Intermediate differentiation II 2
Low grade I-II 2
Mid differentiated II 2
Moderately differentiated II 2
Moderately well differentiated II 2
Partially differentiated II 2
Partially well differentiated I-II 2
Relatively or generally well differentiated II 2
Medium grade, intermediate grade II-III 3
Moderately poorly differentiated III 3
Moderately undifferentiated III 3
Poorly differentiated III 3
Relatively poorly differentiated III 3
Relatively undifferentiated III 3
Slightly differentiated III 3
Dedifferentiated III 3
High grade III-IV 4
Undifferentiated, anaplastic, not differentiated IV 4
Non-high grade 9

References:

  1. SEER Program Coding and Staging Manual (2004) Published by the U. S. Department of Health & Human Services (Bethesda, MD), 2004. NIH Publication Number 04-5581.
  2. International Classification of Diseases for Oncology, Third Edition. WHO.
  3. NAACCR Edit Logic Report for Metafile NAACR10E.EMF
  4. Centers for Disease Control and Prevention. Data collection of primary central nervous system tumors. National Program of Cancer Registries Training Materials. Atlanta, Georgia: Department of Health and Human Services, Centers for Disease Control and Prevention, 2004.
Revision (Terminology Conversion Table)
Year Description
2006 New appendix

Appendix H – CCR Ambiguous Terms

Effective for January 1, 2001 data and forward

The Data Quality Management Committee, with the approval of the CCCR, recommends that the SEER Program list4 of ambiguous terms be adopted as the Canadian list when identifying cancer cases5. Where possible, it is best to obtain additional information or consult with a pathologist for clarification. If neither is possible, use the following list for determining whether to register/report a cancer case to the CCR.

Appendix H – CCR Ambiguous Terms
Consider as diagnostic of cancer NOT considered diagnostic of cancer*
apparent(ly) cannot be ruled out
appears to equivocal
comparable with possible
compatible with potentially malignant
consistent with questionable
favor(s) rule out
malignant appearing suggests
most likely worrisome
presumed
probable
suspect(ed)
suspicious (for)
typical of * without additional information
Exception:
If cytology is reported as “suspicious”, do not
interpret this as a diagnosis of cancer.
Abstract the case only if a positive biopsy
or a physician's clinical impression of cancer supports the cytology findings.
Do not include patients who have a diagnosis consisting only of these terms.
Revision (Appendix H – CCR Ambiguous Terms)
Year Description
2006 New appendix

Appendix I – Guidelines for Abstracting and Determining Death Certificate Only (DCO) Cases for Provincial/Territorial Cancer Registries (PTCRs) in Canada (for T12 and P18)

Cancer registries have identified access to death information as a critical component for operating a high quality program. There are two main reasons for acquiring this particular data, including:

  1. Determination of Death Status for Currently Enrolled Cases: Once a registry has enrolled a case of cancer the addition of death information can provide a more complete picture of how cancer has impacted this individual. Death information on a specific case can remove it from active follow up routines and allow registries to perform more accurate and complete survival calculations.
  2. Case Completeness: To ensure a high level of case completeness a registry typically relies on a variety of methods to ascertain newly diagnosed cancers. One common method is to complete a linkage to vital statistics information regarding cause(s) of death. If an individual is reported with a cancer cause of death and is not found in the registry the case should be followed back to determine if it meets the criteria for cancer registration.

Therefore it is important that PTCRs enter into agreements with Vital Statistics registrars to receive at a minimum all cases for which cancer is listed on any part of the medical certificate of death. In Canada death registration is subject to provincial mandates and includes the completion of a Statement of Death and/or a Medical Certificate of Death. Cancer registries receive death notifications in various formats i.e., hardcopy, electronically, or computer files and at varying intervals for example, monthly, quarterly or annually.

The ideal is to receive notification of all deaths including all causes of death occurring within the province, enabling the registry to perform a comprehensive death clearance. When linked with the registry database this information will result in both matched and non-matched cancer incidence. A death certificate with a reportable tumour listed that does not link to other records in the cancer registry is called a Death Certificate Notification (DCN) and requires further investigation. DCNs include cases in which the underlying cause of death is cancer as well as cases in which cancer is simply mentioned on the death certificate. When additional information is obtained the case should be registered with that year's incidence data. If additional information cannot be obtained, the case is a true Death Certificate Only (DCO) and can be reported as such to the Canadian Cancer Registry (CCR).

Death certificate information is a critical component in the registry certification process operated by the North American Association of Central Cancer Registries (NAACCR). To be eligible for NAACCR certification a PTCR must participate in the NAACCR Call for Data. The data criteria reviewed during this process include: Completeness, passing EDITS, DCO, Interval for Criteria, Timeliness, Duplicate Reports and Missing Data Fields in Sex, Age, County and Race. The DCO certification requirement is less than 5% silver and less than 3% gold.

The CCR and NAACCR accepted formula for calculating the DCO rate is:

The CCR and NAACCR accepted formula for calculating the DCO rate is:

Differences exist in the denominator as CCR does not include in situ bladder cancers and NAACCR does.Where cancer cases = all unduplicated invasive cancers + in situ bladder cancers within the diagnosis year for state (provincial) residents. These include all cases identified and abstracted from the death clearance project and all true DCOs. This information is included in the NAACCR Call for Data.

(Source: NAACCR Series II: Calculating the DCO Rate)

1. Definitions

Cause of Death

The causes of death to be entered on the medical certificate of cause of death are all those diseases; morbid conditions or injuries which either resulted in or contributed to death and the circumstances of the accident or violence which produced any such injuries.

(Source: World Health Assembly, Article 23 of the Constitution of the World Health Organization. ICD-9 pg. 763)

Death Certificate Notification (DCN)

Death certificate notification is a cancer death identified from any source including a Vital Statistics Death Registration that could not be linked (electronically or manually) to an existing cancer record.

Death Certificate Only (DCO)

“Death certificate only” means that the only source of information about the case was a death certificate. This category includes deaths where either the Underlying Cause of Death is cancer, or there is any mention of cancer on the death certificate.
(Source: CCR – Report No. 3.2.2. – Input Data Dictionary, page 79. Revised on: 17/06/94.)As of January 1, 2000 mortality information in Canada was captured by Vital Statistics using the ICD-10 classification system.

Follow Back (FB)

Followback is the process of actively searching for additional information on DCNs at the patient and disease level and updating the cancer database as a complete abstract when possible. If additional information cannot be found the case is a true DCO.

Underlying Cause of Death

The underlying cause of death is (a) the disease or injury which initiated the train of events leading directly to death, or (b) the circumstances of the accident or violence which produced the fatal injury.

(Source: World Health Assembly, Article 23 of the Constitution of the World Health Organization. ICD-9 pg. 763)

2. Process

The process for determining a DCO case will vary and should be modified to meet the requirements of the individual PTCRs. PTCRs should match DCNs to their database; those cancer deaths that do not match require further investigation. Processing is required when the decedent was a resident of your province at the time of death, and a reportable cancer is mentioned on the DCN and no record is found in the PTCR database. No further processing is required when the only tumour mentioned on the DCN is a non-reportable tumour, the decedent was a non-resident of your province (forward to province of ownership if agreements are in place) or when a non-cancer death is identified.

The underlying cause of death field is intended to capture a patient's official cause of death. As this variable is important for record linkage purposes and has legal implications, the death information coded and provided to cancer registries from provincial and territorial Vital Statistics offices should not be altered even when cancer registries have more complete or detailed diagnostic information. The only PTCR reported data that may be changed on the CCR patient record because of a confirmation of death are: Date of Death, Province/Country of Death and Death Registration Number.
(Source, CCR – Report No. 3.2.1 – Coding and Reporting Guidelines – December 18, 1995)

A. DCN Match to Provincial/Territorial cancer registry database. (Example: positive match on four variables for example, HIN, Surname, Sex and DOB).

  • Determine same primary versus new primary.
  • Identify discrepancies between cancer on certificate of death and registry diagnosis codes.
  • Update missing or incomplete fields.

An inconclusive Match shows some discrepancies between identifiers in the incidence and death data but the records may belong to the same person. (Example: positive or close match on the four variables for example, HIN positive match, mismatch with surname, sex or DOB.

  • Visual verification to determine if it's “close enough” to be judged a match or non-match.
  • FB to make a valid determination.

Followback (FB) for new primaries or abstract for additional DCO primaries. Edit and review cases in registry database not microscopically confirmed.

B. DCO. DCN cancer death, Non-match to Provincial/Territorial cancer registry database.
Nonmatched cancer deaths are cleared in a variety of ways, depending on the PTCR's ability to staff a DCO clearance program. Each non-match cancer death must be manually reviewed for reportability and to ascertain where to follow back. Followback sources include facility (chronic care, hospital/nursing home), coroner and attending physician where the death occurred.

Based upon the information received from follow back, the case may be abstracted as:

  • FollowBack is recommended by form letter to the institution (Appendix A) where the patient expired and secondly to the informant (Appendix B) who signed the death certificate to obtain additional information.
  • Cases that are identified after followback should be added to the appropriate diagnosis year as actual incident records (not DCOs).
  • Cases where no additional information is obtained should be reported to the CCR as a DCO.

C. Standard conventions for abstracting DCO cases:

  1. If FB is not returned from facility/physician, the information from the DCN may be used and the case considered a DCO.
  2. If a date of diagnosis or an approximate date cannot be established, the case is a DCO and the date of death is used as the date of diagnosis.
  3. Follow standard coding conventions for site/histology.
  4. There may be more than one primary noted on the Death Certificate. More than one DCO abstract may be required.
  5. Code the histology from the Death Certificate, i.e., squamous cell carcinoma, adenocarcinoma, etc., if available. If “carcinoma” is recorded, code as 8010/3. If “cancer” is recorded, code as 8000/3.
  6. Code the Primary Site recorded on the Death Certificate, i.e., lung, prostate, breast.
  7. Melanoma, unknown primary site code to Malignant melanoma of skin, site unspecified (ICD-9 172.9, ICD-10 C43.9).
  8. Lymphoma, unknown primary site code to Lymph Nodes, NOS (ICD-9 202.8, ICD-10 C85.9).
  9. Leukemia is always coded to Bone Marrow (1CD-9 208.9, ICD-10 C95.9).
  10. Watch for primary sites where metastases are common (Lung, Liver, Brain and Bone).
  11. The death certificate may state “metastatic liver cancer” or “metastatic bone cancer”. If it is unclear if the site recorded is the primary or a metastatic site, code to Unknown Primary Site (ICD-9 199.0, ICD-10 C80.9).
  12. Stage is always “unknown”.
  13. Diagnostic confirmation is always “unknown”.
  14. No treatment is recorded, even if noted on the DCN.
  15. Include DCO cases in edits.

(Cover letter to Institution)

PTCR

Inside address

To Whom It May Concern

The Registry Name is presently completing the Death Certificate Only (DCO) follow back process for year/s. DCO means that the only source of information about the case was a death certificate. The death certificate identified the decedent as having expired in your facility however the cancer registry has no prior information on this case through its routine data collection. Data collection is legislated by act/privacy act. Enclosed you will find a Registry Form letter for completion, it is important that we collect the initial date and address at time of diagnosis. If, your records do not identify this patient as having cancer please indicate and we will adjust our records accordingly.

By completing the enclosed Registry Form letter we can finalize the information on this patient. Complete information permits the calculation of survival rates on patients diagnosed with cancer, facilitates epidemiological studies and improves the completeness and quality of reported death and other demographic information. Your continued support in improving the quality of data allows us to participate in provincial and national studies and to provide accurate statistics on an ongoing basis to our stakeholders.

If there are any questions or concerns, please do not hesitate to contact me, contact name at facility name and phone number.

Sincerely yours,

Signature

Enclosure

(Cover letter to Informant)

PTCR

Inside address

Dear Insert name here,

The Registry Name is presently completing the Death Certificate Only (DCO) follow back process for year/s. DCO means that the only source of information about the case was a death certificate. The death certificate stated the decedent had cancer, however the cancer registry has no prior information on this case through its routine data collection. Data collection is legislated by act/privacy act. The death certificate identifies you as the last attending physician at time of death for patient name. Enclosed you will find a Registry Form letter for completion, it is important that we collect the initial date and address at time of diagnosis. If, your records do not identify this patient as having cancer please indicate and we will adjust our records accordingly.

By completing the enclosed Registry Form letter we can finalize the information on this patient. Complete information permits the calculation of survival rates on patients diagnosed with cancer, facilitates epidemiological studies and improves the completeness and quality of reported death and other demographic information. Your continued support in improving the quality of data allows us to participate in provincial and national studies and to provide accurate statistics on an ongoing basis to our stakeholders.

If there are any questions or concerns, please do not hesitate to contact me, contact name at facility name and phone number.

Sincerely yours,

Signature

Enclosure

Death Certificate Notification (DCN)
Year Description
2007 New appendix

Appendix J – Interval between two dates (complete or partial)

The following algorithm can be used to assess the number of days between two dates. When both dates are complete, the algorithm returns the exact number of days. When one or both dates are partial, the missing parts of the dates are “derived” and the number of days returned, based on the derived dates.  This algorithm cannot be used if one or more dates is totally unknown, i.e. equal to '99999999'. The returned value is always a positive whole number (including zero).

Definitions

Let Date1 and Date2 be the two dates for which the interval must be calculated and where Date1 <= Date2.

Let Y1, M1 and D1 be the year, month and day of date1.
Let Y2, M2 and D2 be the year, month and day of date2.

Let DIFF_DAYS (Date1, Date2) be a function that returns the number of days between date1 and date2.

Assumptions if there are partial dates
Date1 is a partial date Date2 is a partial date
If MONTH is not reported then MONTH is assumed to be '01'.
If DAY is not reported then DAY is assumed to be '01'.
If MONTH is not reported then MONTH is assumed to be '12'.
If DAY is not reported then DAY is assumed to be the last day of the reported MONTH (28, 29, 30 or 31).

Examples

Date1 = 20060627.
Date2 = 20060930.

DIFF_DAYS (20060627, 20060930)

Date1 = 20060699
Date2 = 20070999.

DIFF_DAYS = (20060601, 20070930)

Date1 = 20069999
Date2 = 20079999

DIFF_DAYS = (200601, 20071231)

Appendix J – Interval between two dates (complete or partial)
Year Description
2008 New appendix

Appendix T – Residency guidelines in Canada

To ensure comparability of definitions of cases and the population at risk (numerator and denominator), the Canadian Cancer Registry (CCR) rules for determining residency at time of diagnosis are to be identical or comparable to rules used by the Canadian Census Bureau, whenever possible.

The residence at diagnosis is generally the place of usual residence, as stated by the patient or, as stated by the Census Bureau, ‘the dwelling in Canada where a person lives most of the time'. Residency is their usual place of residence, regardless of where they are when diagnosed. For patients with multiple tumours, the address may be different for each primary tumour.

There are a number of situations for which the process of determining residency is not intuitive, and special guidelines have been created in order to define an individual's usual place of residence. The Data Quality Committee (DQC) for the Canadian Council of Cancer Registries (CCCR) recognizes that some Provincial/Territorial Cancer Registries (PTCRs) are removed from the direct patient contact relationship, and may not have access to the patient or the information to confirm residency. Using the provincial health insurance number (HIN) as a determining factor of residency during initial case abstraction is appropriate. When permanently relocating, the HIN from the previous province of residence is valid for three months. However, if the case is identified as a potential duplicate during a Record Linkage cycle, additional information should be obtained before confirming residency, as it may not be appropriate to default to using province of HIN, as the primary residence.

PTCRs are encouraged to use these guidelines to determine residency for categories of persons for whom residence is not immediately apparent.

  1. Residence (one residence). The dwelling in Canada where a person lives most of the time.
  2. Persons with more than one residence. Usual residence rule applies; however, if the time spent at each residence is equal or the abstractor is not sure which one to choose, the residence where the patient was staying on the day cancer was diagnosed should be considered the usual place of residence (see examples below). a) Exception: Consider the residence shared with their family as their usual place of residence, even if they spend most of the year elsewhere.
    Commuter workers living away part of the week while working: Consider the residence shared with their family as the usual place of residence, even if they spend most of the year elsewhere. (for example, parents, husbands, wives or common-law partners)
    b) Snowbirds: People who live at another residence (city, province or country) with a warmer climate. Residence should be documented as where they live most of the time.
    c) Children in joint custody: Residence should be documented as where they live most of the time. If time is equally divided, their residence is documented as where they were staying on the day cancer was diagnosed.
  3. Patients with rural addresses. If the information provides a rural address only, which may be the post office box, record the address as stated, but make every attempt, within your resources, to identify the actual physical place of residence at time of diagnosis.
  4. Patients with no usual place of residence (i.e. homeless, transient people). Residents who do not have a usual place of residence should be documented as where they were staying on the day cancer was diagnosed.
  5. Institutional collective dwellings (Collective dwellings that provide care or assistance services). Persons in institutions with no other usual place of residence elsewhere in Canada, or persons who have been in one or more institutions for a continuous period of six months or longer, are to be considered as usual residents of the institution.
    Institutional collective dwellings include:
    a) Residents of a long-term care facility, a hospital, or a home for the aged.
    b) In homes, schools, hospitals, or wards for the physically disabled, mentally challenged, or mentally ill or in drug/alcohol treatment facilities.
    c) Inmates of correctional institutions, including prisons, jails, detention centers, or halfway houses.
    d) Children in juvenile institutions, such as residential care facilities for neglected or abused children or orphanages.
    e) For abused women, or for runaway or neglected youth please see section 6 - Non-institutional collective dwellings.
  6. Non-institutional collective dwellings (Collective dwellings that do not provide care or assistance services). Residence should be documented as their usual residence, if they report one (the place where they live most of the time) or otherwise at the inn, hotel, etc.
    Non-institutional collective dwellings include:
    a) Inns, hotels, motels and hostels.
    b) YMCAs/YWCAs, or public or commercial campgrounds.
    c) Military bases.
    d) Migrant workers (lumber / mining camps & farms).
    e) Members of religious orders in monasteries or convents.
    f) Shelters with sleeping facilities for people without housing, for abused women, or for runaway or neglected youth. Residence should be documented as the shelter.
  7. Students. Students who live away from home while attending school, but who return to live with their parents part of the year should consider their place of residence as their parents' home, even if they spend most of the year elsewhere.
  8. Live-ins:
    a) Live-in nannies. Residence should be documented as where they live most of the week.
    b) Foster children, boarders or housemates. Residence should be documented as where they are living at time of diagnosis.
  9. Merchant and coast guard vessels. Merchant vessels, coast guard vessels and oil rigs at sea should be documented as their usual onshore residence, if they report one (the place where they live most of the time when they are onshore) or otherwise, at their vessel's homeport.
  10. Naval vessels. Canadian Forces Naval Vessel residence should be documented as their usual onshore residence, if they report one (the place where they live most of the time when they are onshore) or otherwise, at their vessel's homeport.
  11. Armed forces. Canadian Armed Forces residence should be documented as their usual place of residence, if they report one, or otherwise, where they are stationed at time of diagnosis.
  12. Non-permanent residents (foreign citizens). Persons who hold a student or employment authorization, Minister's permit or who were refugee claimants at time of diagnosis, for a continuous period of six months or more.
    a) Citizens of foreign countries who have established a household or are part of an established household in Canada while working or studying, including family members with them. Residence should be documented as their household in Canada.
    b) Citizens of foreign countries who are living in Canadian embassies, ministries, legations or consulates. Residence should be documented as the embassy.
    c) Citizens of foreign countries temporarily traveling or visiting Canada. These cases are not reportable to the Canadian Cancer Registry.

Appendix X – CCR_ID check digit routine

The last digit of the CCR_ID is a check digit, for example, digit calculated from the other CCR_ID digits. The purpose of using a check digit is twofold: it allows the detection of some data corruption and prevents one from creating new IDs too easily. The next routine returns a check digit for a given CCR_ID.

Pseudo code


Let N1 be the first digit of CCR_ID (starting from the left)
Let N2 be the second digit of CCR_ID (starting from the left)
Let N8 be the eighth digit of CCR_ID (starting from the left)

Change the values of N2, N4, N6, N8 according to the following pattern
 
Initial value 0 1 2 3 4 5 6 7 8 9
New value 0 2 4 6 8 1 3 5 7 9


Let REMAINDER be the remainder of ((N1 + N2 + N3 + N4 + N5 + N6 + N7 + N8) / 10)
If REMAINDER = 0 then
RETURN 0
Else
RETURN (10 – REMAINDER)

Used by

  • Data loading – Edit
  • Data loading – posting

Appendix Z – References

Collaborative Staging Task Force of the American Joint Committee on Cancer. Collaborative Staging Manual and Coding Instructions, Version 01.04.01. Jointly published by American Joint Committee on Cancer (Chicago, IL) and U.S. Department of Health and Human Services (Bethesda, MD), 2004. NIH Publication Number 04-5496.
http://www.cancerstaging.org/cstage/index.html

Fritz A, Percy C, Jack A, et al (eds): ICD-O: International Classification of Diseases for Oncology, Third Edition. Geneva, World Health Organization, 2000.

SEER Program Coding and Staging Manual 2004, Surveillance, Epidemiology and End Results (SEER) Program, National Cancer Institute, National Institutes of Health, Bethesda, MD. NIH Publication Number 04-5581.

SEER Program Coding and Staging Manual 2007, Surveillance, Epidemiology and End Results (SEER) Program, National Cancer Institute, National Institutes of Health, Bethesda, MD. NIH Publication Number 07-5581.

Johnson CH, Peace S, Adamo P, Fritz A, Percy-Laurry A, Edwards BK. The 2007 Multiple Primary and Histology Coding Rules. National Cancer Institute, Surveillance, Epidemiology and End Results Program. Bethesda, MD, 2007. Revised April 30, 2008

NAACCR Standards for Cancer Registries, Volume II Version 11.3 - Data Standards and Data Dictionary, Thirteenth Edition.

National Cancer Institute Surveillance Epidemiology and End Results training website, American Joint Committee on Cancer. http://www.training.seer.cancer.gov/
module_staging_cancer/unit03_sec03_part00_ajcc.html

CCCR Committee on Data and Quality Management - Clinical Core Data Set - March 2001 version

AJCC Cancer Staging Manual, 6th Edition, American Joint Committee on Cancer (AJCC), 2002

Facility Oncology Registry Data Standards (FORDS), revised for 2007. Published by the American College of Surgeons (ACoS) and the Commission on Cancer (COC), 2007.

Facility Oncology Registry Data Standards (FORDS) manual, revised for 2009. Published by the American College of Surgeons (ACoS) and the Commission on Cancer (COC), 2009.

Footnotes

1.The original set of ISO codes has been expanded to include individual Canadian provinces and territories and other Statistics Canada specific codes.

2. Available upon request.

3.The only source of information about the case was a death certificate. This category includes deaths where either the underlying cause of death (patient record, Field No.17) is cancer, or there is any mention of cancer on the death certificate.

4. Input records that passed successfully through all validation edits, correlation edits and other match edits.

5. Because CS and AJCC TNM data items are fairly new to CCR, it has been temporarily decided that CS and AJCC TNM errors (including fatal errors)will not prevent valid core data items from being loaded on the CCR database

6. See Appendix A – Core reference tables - ICD-9 to ICD-O-2 conversion table for details.

7. See P1 Specific values & meaning.

8. See Appendix X - CCR_ID check digit routine.

9. See P4 Specific values & meaning.

10. See P5 Specific values & meaning.

11. See P10 Specific values & meaning.

12. See Appendix A – Core reference tables.

13. See Appendix – Core reference tables.

14. See P18 Specific values & meaning.

15. See T1 Specific values & meaning.

16. See Appendix X – CCR_ID check digit routine.

17. See T5 Specific values & meaning.

18. See T11 Specific values & meaning.

19. See T13 Specific values & meaning.

20. See T14 Specific values & meaning.

21. See T17 Specific values & meaning.

22. See T19 Specific values & meaning.

23. Eligible ICD-O-3 histology codes do not include ‘0000' since this value should have been converted to a more meaningful value during the Pre-edit processing.

24. See T22 Specific values & meaning.

25. See T23 Specific values & meaning.

26. See T24 Specific values & meaning.

27.See T25 Specific values & meaning.

28. See section 1.1.2.2 – CCR collaborative staging scope.

29. See section 1.1.2.3 – CCR AJCC TNM staging scope.

30. See Appendix C – AJCC TNM concordance tables - Valid AJCC clinical T by site.

31. See Appendix C – AJCC TNM concordance tables - Valid AJCC clinical N by site.

32. See Appendix C – AJCC TNM concordance tables – Valid AJCC clinical M by site.

33. See Appendix C – AJCC TNM concordance tables – Valid AJCC pathologic T by site.

34. See Appendix C – AJCC TNM concordance tables – Valid AJCC pathologic N by site.

35. See Appendix C – AJCC TNM concordance tables – Valid AJCC pathologic M by site.

36. See Appendix C – AJCC TNM concordance tables – Valid AJCC TNM clinical stage group by site.

37. See Appendix C – AJCC TNM concordance tables – Valid AJCC TNM staging group by site.

38. See T51 Specific values & meaning.

39. Collaborative staging data items (T27-T41) and AJCC TNM staging data items (T42-T51) may or may not be reported. See TCOR-18 and TCOR-19 respectively for more details.

40. Already enforced by TVAL15.

41. Impossible to enforce since the code that stands for 'Not Reported' also stands for 'Benign behaviour'.

42. Already enforced by TVAL21.

43. See Appendix A – Core reference tables – ICD-9 to ICD-O-2 conversion table.

44.See Appendix A – Core reference tables – ICD-O-2 to ICD-O-3 conversion table.

45. See Appendix A – Core reference tables – CCR core scope.

46. See Appendix A – Core reference tables – Invalid site and histology combinations.

47. See Appendix A – Core reference tables – Invalid histology and behaviour combinations.

48. See collaborative staging scope in Chapter 1.

49.See Appendix C – AJCC TNM concordance tables – Valid AJCC T, N, M and stage group combination bysite.

50. Thus, unknown or not assessed AJCC clinical/pathologic T, N, M values are excluded.

51. All related patient and tumour records are rejected, but corresponding message is only attached to each conflicting patient record of the family.

52. All related patient and tumour records are rejected, but corresponding message is only attached to each conflicting tumour record of the family.

53. All related patient and tumour records are rejected, but corresponding message is only attached to each erroneous or conflicting patient record of the family.

54. The match with a delete patient transaction is covered by KIM4.

55. All related patient and tumour records are rejected, but corresponding message is only attached to each erroneous or conflicting tumour record of the family.

56. Input record that has neither core fatal errors nor core errors from all previous edits.

57. Method of diagnosis can be 'Autopsy' even when date of diagnosis is before date of death. This is possible since method of diagnosis is not linked to date of diagnosis. See corresponding definitions for more detail.

58. According to cancer staging manual, 6th edition, this value is not a valid stage group for the site.

59. Place holder to keep sub-edit numbering in accordance with the required processing order. See Data Item match edits introduction for more information.

60. Based on the underlying cause of death coding rules, these 2 codes cannot be used.

61. According to cancer staging manual, 6th edition, this value is not a valid stage group for the site. On the other hand, since AJCC TNM stage group is likely to be assigned by a physician rather than derived from any T, N and M values, this value must be accepted.

62. Lymphoma, leukemia or immunoproliferative disease is identified by the following ICD-0-3 codes: 9590-9989 excluding 9731, 9734, 9740, 9750, 9755-9758, 9930.

63. Alphabetic comparison as opposed to numeric comparison is used because TTRN and Health Insurance Number may contain letters.

Canadian Cancer Registry System Guide – 2009 Edition

Part II – Data Loading and Tabulation Master Files

Introduction
0.1 Canadian Cancer Registry Overview
0.2 CCR System Guide Document Organization
0.3 Part II Document Organization – Data Loading and TMF
0.4 Changes to the CCR Data Loading and TMF for the 2007 and 2008 Reference Years
0.5 Contacts in Statistics Canada

Chapter 3 – Data Loading
3.1 Introduction
3.2 Data Importing
3.3 Data Conditioning
3.4 Validation Edits
3.5 Correlation Edits
3.6 Match Edits
3.7 Data Posting

Chapter 4 – Tabulation Master Files
4.1 Description
4.2 Scope
4.3 Content and layout
4.4 Derived variable calculations
4.5 Confidentiality

Appendices
Appendix C – AJCC TNM reference tables
Appendix D – Multiple primary tumour rules for CCR
Appendix E – Interval and mean times between dates
Appendix F – Auxiliary tables
Appendix G – Guidelines for reporting grade, differentiation or cell indicator
Appendix H – CCR ambiguous Terms
Appendix I – Guidelines for abstracting and determining Death Certificate Only (DCO) Cases for Provincial/Territorial Cancer Registries (PTCRS) in Canada (for T12 and P18)
Appendix J – Interval between two dates (complete or partial)
Appendix T – Residency guidelines in Canada
Appendix X – CCR_ID Check digit routine
Appendix Z – Reference
Footnotes

Introduction

  • Canadian Cancer Registry Overview
  • CCR System Guide Document Organization
  • Part II Document organization – Data Loading and TMF
  • Changes to the CCR Data Loading and TMF for the 2007 and 2008 Reference Years
  • Statistics Canada Contacts

0.1 Canadian Cancer Registry Overview

The patient-oriented Canadian Cancer Registry (CCR) evolved from the event-oriented National Cancer Incidence Reporting System (NCIRS). Beginning with cases diagnosed in 1992, incidence figures collected by Provincial and Territorial Cancer Registries (PTCRs) have been reported to the CCR, which is maintained by Statistics Canada. Established as a person-oriented database, the CCR includes mechanisms for updating and clearing death records and is linked to provincial and territorial databases to help track patients across Canada who have been diagnosed with tumours.

0.2 CCR System Guide Document Organization

The CCR System Guide has been separated into three parts to improve access and navigation. Although the three parts are separate, the three documents should be used in conjunction with each other. The different sections of the three-part CCR System Guide often refer to each other. The CCR System Guide is now composed of:

Part I: CCR Data Dictionary provides explanation on the reporting of data, including the scope and detailed information on the input and derived variables.

Part II: CCR Data Loading and Tabulation Master Files provides information on the data loading process, including in-depth descriptions of the various edits performed on the data. Part II also provides information on the Tabulation Master Files, including the scope, content and layout. Part II is followed by several appendices that contain supporting information such as explicit code set tables, guidelines to assist coders and other supportive information.

Part III: CCR Core Reference Tables provides detailed information on the CCR Core Reference Tables such as descriptions of the tables, their usage and any revisions made. Part III is an accompanying document to the Core Reference Tables 2009.xls.

0.3 Part II Document organization – Data Loading and TMF

Chapter 3 – Data loading describes in great detail all the verification performed against reported data prior to their loading into the CCR System. Related business rules, Edit logic and feedback report messages are described for all edits. It also describes the data conditioning and the data posting phase.

Chapter 4 – Tabulation master file describes the main output of the system.

Appendices contain supporting information such as explicit code set tables, guidelines to assist coders, lists of changes from previous versions of the system, etc.

0.4 Changes to the CCR Data Loading and TMF for the 2007 and 2008 Reference Years

Please refer to the relevant section in the System Guide – Data Loading and TMF for more details related to these changes.

Changes to the CCR Data Loading and TMF for the 2007 and 2008 Reference Years
Section Item(s) Description of change Effective (reference year)
3.1.5 Step 2: Core data items validation New validation edits added, TVAL53-57 2008
3.1.5 Step 7: CS data items validation New validation edit TVAL52 added in to step 2007
3.1.7 CS fatal error CS data item T52 added 2007
3.1.7 CS error CS data item T52 added 2007
3.3.1 Data formatting – Table 22 Impact of data formatting step on tumour data items New variables added: T53, T54, T55, T56, T57 2008
New variable added – T52 2007
3.4 Validation Edits –
PVAL6
PVAL7
PVAL8
PVAL9
PVAL13
Business rules changed – acceptable accented characters specified 2007
3.4.2 Tumour validation edits – Table 25 New Tumour validation edits – TVAL53, TVAL54, TVAL55, TVAL56, TVAL57 2008
New Tumour validation edit – TVAL52 2007
3.4.2 Tumour validation edits –
TVAL6
Business rules changed – acceptable accented characters and special characters specified
Edit logic – New edit logic added
Feedback report messages – New messages added
2007
3.4.2 Tumour validation edits –TVAL8 Business rules, Edit logic and Feedback report messages added – SGC 2006 2006
3.4.2 Tumour validation edits –
TVAL9
Business rules, Edit logic and Feedback report messages added – Census tract effective date range ended in 2005. For 2006 onwards T9 must be blank 2006
3.4.2 Tumour validation edits –
TVAL27
TVAL28
TVAL29
TVAL30
TVAL31
TVAL32
TVAL33
TVAL34
TVAL35
TVAL36
TVAL37
TVAL38
TVAL39
TVAL40
TVAL41
Referenced fields, Business rules, Edit logic and Feedback report messages updated: now using recommended version of AJCC CS algorithm 2007
3.4.2 Tumour validation edits –
TVAL52
New validation edit added 2007
3.4.2 Tumour validation edits –
TVAL53
TVAL54
TVAL55
TVAL56
TVAL57
New validation edits added 2008
3.5.2 Tumour correlation edits – Table 27 New correlation edits – TCOR26, TCOR27 2008
3.5.2 Tumour correlation edits – Table 27 New correlation edits – TCOR13 2007
3.5.2 Tumour correlation edits – TCOR1 Referenced fields, Business rules, edit logic changed – new data items added T53, T54, T55, T56, T57 2008
Referenced fields, Business rules, edit logic changed – new data items added T52 2007
3.5.2 Tumour correlation edits – TCOR3 Business rules and Edit logic changed: includes combinations where census tract indicates area outside CMA 2006
3.5.2 Tumour correlation edits – TCOR10
TCOR11
Referenced fields, Business rules, Edit logic and Feedback report messages changed: Verification now includes Date of diagnosis. 2007
3.5.2 Tumour correlation edits – TCOR13 New correlation edit added 2007
3.5.2 Tumour correlation edits – TCOR18 Referenced fields and Edit logic updated: T52 added as a new CS variable 2007
3.5.2 Tumour correlation edits – TCOR26, TCOR27, TCOR29 – TCOR35 New correlation edits 2008
3.6.3 Data item match edits –
DIM6
Revision – Edit no longer used after 2006 2006
3.7.2 Add tumour record processing – CS data items Added new data item T52 2007
3.7.7 Patient derived variable calculation PD7 – Name of variable changed 2007
4.2 Table 24 – Scope - topography codes from ICD-O-2 and ICD-O-3 considered a single site in the definition of multiple cancers Topography group added: C38.4 2007
4.3 Table 36 TMF record layout Addition/deletion of variable – T52 CS version 1st added TD20 deleted 2007
PD7 – Variable acronym changed
New variables added – T53 to T57
2008
4.3 Table 37 – Derived variable calculations at TMF time PD2 – Vital status now derived at TMF time 2007
Appendices Appendices – Appendix A moved to Part III of system guide. Appendix A now included in Part III of system guide 2008
Additions to Appendices Appendix H now includes T53
Appendix I now includes P18
2008
Table 50 – updated table Updated stage group II with T1a, T1b and T1c 2008
New Appendices added to system guide New Appendices
Appendix G – Grade, differentiation or cell indicator guidelines
Appendix H - CCR Ambiguous Terms
Appendix I – Guidelines for abstracting and determining death certificate only (DCO) cases for PTCRs in Canada
2007
Appendix J – Interval between two dates (complete or partial) 2008
Appendices deleted from system guide Appendix Y - Removed and replaced with Section 0.4 Changes to the CCR Data Loading and TMF for the 2007 and 2008 reference years 2008
Appendix Z - References Updates to several references 2007
  • Additional updates have been made; however, only the changes that require action on the part of the PTCRs have been included in this table.
  • Note that changes effective in the 2006 reference year have also been included here.

0.5 Statistics Canada Contacts

PTCRs employees are encouraged to bring forward any questions by contacting one of the following:

For additional information regarding the processing of CCR data, please contact:

Colette Brassard
Section Chief
Operations and Integration Division
Statistics Canada
Tel: (613) 951-7282
Fax: (613) 951-0709
For any subject matter related questions/queries, please contact:

Kim Boyuk
Chief, Cancer Statistics
Health Statistics Division
Statistics Canada
Tel: (613) 951-2510
Fax: (613) 951-0792

Hollie Anderson
Manager, Canadian Cancer Registry
Health Statistics Division
Statistics Canada
Tel: (613) 951-0757
Fax: (613) 951-0792

Chapter 3 – Data loading

  • Data importing
  • Data conditioning
  • Data editing
  • Data posting

3.1 Introduction

The data loading process is done in 4 distinct phases:

1. Data importing: Reads in input patient and tumour record files and breaks them down into separate data items using the proper record layout.
2. Data conditioning: Formats the data, filters the old classification data, computes some missing input variables and adjusts the laterality code. This phase alters the reported data.
3. Data editing: Identifies errors in input records and provides sufficient feedback to correct them. This phase does not alter the data. The documentation about this phase has been divided into 3 sections:

  • Validations edits,
  • Correlation edits,
  • Match edits.

4. Data posting: Computes some derived variables, transfers valid data in the CCR database and generates additional reports.

Since the data editing is the most complex phase of the overall process, the remaining pages of the introduction present its key components. An overview of the overall data loading process is also presented at the end of the introduction.

3.1.1 Business rules

The main purpose of the edit process is to enforce a given number of rules on the CCR Data items. Some rules are related to the subject matter (subject matter rules) whereas some others are related to the transmission of data between the PTCR and Statistics Canada (transactional rules). The expression "Business rules" has been retained to express both subject matter and transactional rules that apply to the CCR System.

3.1.2 Edits and sub-edits

Each individual edit in the CCR system enforces a set of related business rules. For the purpose of reporting, an edit may be divided into sub-edits in order to provide more detailed feedback. Thus, each Sub-edit has its own logic and message.

3.1.3 Edit logic

Edit logic are logical expressions that can be evaluated to true or false. They are built from data item names, operators and functions. The principal language elements are described in the following tables.

Table 14 Logical operators
Operator Syntax and meaning
AND expr1 AND expr2
The expression is true if and only if both expr1 and expr2 are true, otherwise the expression is false.
OR expr1 OR expr2
The expression is true whenever expr1 or expr2 is true, otherwise the expression is false.
NOT NOT expr1
The expression is true only if it does not equal expr1, otherwise the expression is false.
Table 15 Comparison operators
Operator Syntax and meaning
<> Expr1 <> expr2
Assesses whether expr1 is different from expr2.
= Expr1 = expr2
Assesses whether expr1 is equal to expr2.
> Expr1 > expr2
Assesses whether expr1 is greater than expr2.
>= Expr1 >= expr2
Assesses whether expr1 is greater than or equal to expr2.
< Expr1 < expr2
Assesses whether expr1 is less than expr2.
<= Expr1 <= expr2
Assesses whether expr1 is less than or equal to expr2.
BETWEEN Expr1 BETWEEN (expr2, expr3)
Assesses whether expr1 is greater than or equal to expr2 and less than or equal to expr3.
LIKE Expr1 LIKE expr2
Assesses whether expr1 complies with expr2 pattern. Expr2 may contain Underscore (_) and percent (%) characters which stand respectively for any single character and any number (including 0) of characters.
Ex: ‘951-5555' LIKE ‘951-_ _ _ _' is true.
EX: ‘951-5555' LIKE ‘653-_ _ _ _' is false.
Table 16 Functions
Function Syntax and meaning
AVERAGE AVERAGE (X1, X2, ..., Xn)
Returns the arithmetic mean of X: X1+X2+...+Xn / n. This function ignores NULL values.
BLANK BLANK(x1)
Returns x1 blank character(s).
CALCULATE_CCR_CHECK_DIGIT CALCULATE_CCR_CHECK_DIGIT (str1)
Returns a CCR_ID check digit based on str1.
CONTAINS_WORD CONTAINS_WORD (str1, str2, x1)
Assesses whether str1 contains a word of at least x1 character(s) from str2.
IS_COMPOSED_OF IS_COMPOSED_OF (str1, str2)
Assesses whether str1 is only composed of characters from str2.
IS_VALID_DATE IS_VALID_DATE (str1)
Assesses whether str1 is a calendar date.
LENGTH LENGTH (str1)
Returns the length of str1 including trailing blanks.
UPPER UPPER (str1)
Returns str1 where letters and accented characters are converted to their uppercase equivalent. Special characters and numbers remain the same.
Table 17 String operator
Operator Syntax and meaning
|| str1 || str2
Returns a unique string containing str1 and str2 concatenated (juxtaposed).
Table 18 Set operators and symbols
Operator and symbol Syntax and meaning
[] [Expr1,...]
[A-Z]
[A]
Indicates an explicit list of values, a range of values or set of values known as Set A.
IN expr1 IN [A]
Assesses whether expr1 is included in Set A.

3.1.4 Edit families and groups

For ease of use, edits have been grouped into families and groups depending on the scope of the business rules they enforce. There are 3 families:

  1. Validation edits: Enforce business rules on each individual field.
  2. Correlation edits: Enforce business rules between valid fields on the same input record.
  3. Match edits: Enforce business rules between valid fields on different records.

The following table describes the scope of each edit group.

Table 19 Edit scope by family and group
Family Group Scope
Validation Patient validation (PVAL)  Enforce business rules on Patient fields.
Tumour validation (TVAL)  Enforce business rules on Tumour fields.
Correlation Patient correlation (PCOR)  Enforce business rules between valid Patient fields.
Tumour correlation (TCOR)  Enforcebusiness rules between valid Tumour fields.
Match Key input match (KIM) Ensure that Input patient and Tumour records respect the submission rules in terms of matching keys.
Hey base match (KBM) Ensure that Input patient and Tumour records respect the actual state of the CCR in terms of matching keys.
Data item match (DIM) Enforce the business rules between data items (other than keys) found on different records.
Pre–posting match (PPM) Identify error–free4 Input records that cannot be posted to CCR because some other related Input records are either missing or in error.

3.1.5 Edits order of execution and edit control

Because of the dependencies between the edits, edit processing must respect a given order of execution. Since CS and AJCC TNM data item edits depend on core data items, core data item edits must be done first. For each of the following steps, the number of eligible input records will depend on the outcome of preceding steps.

Step 1: Core data items minimum requirements assessment

The core data items minimum requirements consist of an Input record with a valid record type and date of transmission and no missing core data items (P1-P19 or T1-T26). The following edits must be successful in order to respect the minimum requirements:

  • Patient records: PCOR1, PVAL4 and PVAL19.
  • Tumour records: TCOR1, TVAL5 and TVAL26.

Step 2: Core data items validation

Remaining core data items validation edits (PVAL1-19, TVAL1-26 and TVAL53-57) can be performed on the Input records that respect the core data items minimum requirements. The following order must be respected:

  • PVAL11 before PVAL12;
  • PVAL14 before PVAL15 and PVAL17;
  • TVAL12 before TVAL8 and TVAL9;

Step 3: Core data items correlation, key input match and key base match edits

These edits are run based on the outcome of the core data item validation edits. That is, for a given edit, only the Input records where all referenced fields have been successfully validated are eligible. (This implies that Input records that do not respect the minimum requirements or that fail a required field validation edit are not eligible.) These edits can be run in any order.

Step 4: Core data item match edits

Those edits can only be performed on Input records that have no core data items errors. A special processing order must be respected. See Section 3.6.3 Data Item Match Edits for details.

Step 5: Core data items pre-posting match edits

Those edits can only be performed on Input records that have no core data items errors. These edits can be run in any order.

Step 6: CS data items minimum requirements assessment

CS data items minimum requirements consist of an input tumour record with valid date of diagnosis and no missing CS data items. The following edit must be successful in order to respect the minimum requirements:

Tumour records: TCOR18.

Step 7: CS data items validation

CS Validation edits (TVAL27 to 41 and TVAL52) can be performed on the input tumour records that respect the CS minimum requirements and where all core referenced fields are valid. These edits can be run in any order.

Step 8: AJCC TNM data items minimum requirements assessment

AJCC TNM data items minimum requirements consist of an input tumour record with valid date of diagnosis, ICD-O-2/3 topography, ICD-O-3 histology and ICD-O-3 behaviour and no missing AJCC TNM data items. The following edit must be successful in order to respect the minimum requirements SITE-SPECIFIC MEANING: Tumour records: TCOR19.

Step 9: AJCC TNM data items validation

AJCC TNM validation edits (TVAL42 to 51) can be performed on the input tumour records that respect the AJCC TNM minimum requirements and where all core referenced fields are valid. These edits can be run in any order.

Step 10: AJCC TNM data items correlation

These edits are run based on the outcome of previous validation edits. That is, for a given edit, only the Input records where all referenced fields (core and AJCC TNM) have been successfully validated are eligible. These edits can be run in any order.

See section 3.1.9 flowchart of the data loading process for an illustration of the edits dependencies.

3.1.6 Sub-edits order of execution

Except for data item match Sub-edits; all sub-edits from a given edit may be performed in any order. See Section 3.6.3.1 Special order of execution for more details about data item match Sub-edits special order of execution.

3.1.7 Message types

The severity of an error is expressed by its corresponding message's type. The following list describes each possible message type and gives an indication of when they are issued and how they change the editing process flow.

Fatal error: When a group of data items does not respect the minimum requirements. Related editing is stopped.

Core fatal error: Core data items (P1 to P19 and T1 to T26) do not respect the minimum requirements. The input record will not undergo any other edits and will be rejected.

CS fatal error: CS data items (T27 to T41 and T52) do not respect the minimum requirements. CS data items will not undergo any other related edits and will not be loaded on the CCR database. CS Fatal error does not prevent valid core and AJCC TNM data items from being loaded on the CCR database.1

AJCC TNM Fatal error: AJCC TNM data items (T42 to T51) do not respect the minimum requirements. AJCC TNM data items will not undergo any other related edits and will not be loaded on the CCR database. AJCC TNM fatal error does not prevent valid core and CS data items from being loaded on the CCR database.5

Error: Normal edits failure. Editing is not stopped. Unless specified otherwise, the input record can be edited by other edits based on the validity of their corresponding referenced fields.

Core error: Error found in core patient (P1 to P19) or Tumour (T1 to T26) data items. Core error causes the Input record to be rejected.

CS error: Error found in CS data items (T27 to T41 and T52). CS data items will not be loaded on the CCR database.CS error does not prevent valid core and AJCC TNM data items from being loaded on the CCR database.5

AJCC TNM error: Error found in AJCC TNM data items (T42 to T51). AJCC TNM data items will not be loaded on the CCR database. AJCC TNM error does not prevent valid core and CS data items from being loaded on the CCR database.5

Warning: Informative message to PTCR. Warnings do not prevent Inputrecords from being loaded on the CCR.

3.1.8 Edit description pages

For ease of use, each edit is described using a standard format: name, purpose, referenced fields, business rules, edit logic and feedback report messages. When needed, other parameters, revisions and notes are also added to give more detail. The following table describes each possible section.

Table 20 Edit presentation breakdown
Section Description
Name A unique name for the edit.
Purpose Edit main purpose.
Referenced fields List of all input file fields (or part of fields) involved in the edit.
Other parameters List of additional parameters needed to perform the edit.
Business rules Rules that describe the eligible field value or relationship between many field values. These rules are written in plain English.
Edit logic Each Sub-edit condition that identifies invalid records. These conditions are usually written using logical expressions.
Feedback report messages List of all possible edit messages.
Revision List of all changes that have been applied to the edit over time.
Notes Any remarks.

3.1.9 Flowchart of the data loading process

3.1.9 Flowchart of the data loading process

Notes:
*See 3.1.5 Edits Order of Execution and Edit Control for exact sequencing.
**DIM Edits have a special processing order. See specific section for more details.

3.2 Data importing

During the data importing phase, the input patient record file and/or input tumour record file is read in by the system. Every record is then cut into separate data items using the proper record layout.

3.2 Data Importing

3.3 Data conditioning

The purpose of the data conditioning phase is threefold. Its intent is to:

  • Reduce PTCR response burden by automatically correcting small errors such as the use of lowercase characters in code fields or improper alignment of values.
  • Eliminate older classification data (ICD-9 and ICD-O-2) when not reported as the source classification data. This eliminates the risk of incoherence between the source classification and any former classification data.
  • Bring all reported data up to a uniform classification (ICD-O-3). This facilitates a comparison of all tumours reported to the CCR.

To achieve these objectives, the following steps are performed on the data:

  1. Data formatting;
  2. Old classification filtering;
  3. ICD-O-2/3 topography calculation;
  4. ICD-O-3 histology and behaviour calculation; and,
  5. Laterality adjustment.

The steps listed above must be executed in sequential order. Each step may alter the reported data. Refer to the corresponding section below for a description of how these reported data are altered.

3.3.1 Data formatting

Description

Data formatting is composed of three operations:

Left justified: Removes blank character preceding the data item value.

Uppercase: Converts all lower case alphabetic characters to uppercase letters.
Converts lower case French accents (é, è, ê, ë, ç…) to corresponding uppercase letters (é à É). Special characters and digits remain unchanged.

Removal of trailing blanks: Removes any blank characters trailing the data item value. Data items containing only blank characters will be converted to NULL. This is an important assumption used in the data editing phase.

Purpose

Data formatting reduces PTCR response burden by fixing small formatting errors that would otherwise cause an input record to be rejected. It also converts blank data items to NULL values in order to be compliant with the data editing specification.

Logic

  • Left justification is applied on any fields longer than 1 character.
  • Uppercase is applied on any fields that may contain letters.
  • Removal of trailing blanks is applied on all fields.

The following two tables summarize the impact of the data formatting step on patient and tumour data items. X and – indicate whether the corresponding transformation is applicable or not.

Table 21 Impact of data formatting step on patient data items
Variable Name Variable Left justify Uppercase Removal of trailing blanks
P1 Patient reporting province/territory X - X
P2 Patient identification number X X X
P3 CCR identification number X - X
P4 Patient record type - - X
P5 Type of current surname - - X
P6 Current surname X X X
P7 First given name X X X
P8 Second given name X X X
P9 Third given name X X X
P10 Sex - - X
P11 Date of birth X - X
P12 Province/territory or country of birth X - X
P13 Birth surname X X X
P14 Date of death X - X
P15 Province/territory or country of death X - X
P16 Death registration number X - X
P17 Underlying cause of death X X X
P18 Autopsy confirming cause of death - - X
P19 Patient date of transmission X - X
Table 22 Impact of data formatting step on tumour data items
Variable Name Variable Left justify Uppercase Remove trailing blank
T1 Tumour reporting province/territory X - X
T2 Tumour patient identification number X X X
T3 Tumour reference number X X X
T4 CCR identification number X - X
T5 Tumour record type - - X
T6 Name of place of residence X X X
T7 Postal code X X X
T8 Standard geographic code X - X
T9 Census tract X - X
T10 Health insurance number X X X
T11 Method of diagnosis - - X
T12 Date of diagnosis X - X
T13 ICD–9 cancer code X - X
T14 Source classification flag - - X
T15 ICD–O–2/3 Topography X X X
T16 ICD–O–2 Histology X - X
T17 ICD–O–2 Behaviour X - X
T18 Filler - - -
T19 Laterality - - X
T20 Filler - - -
T21 ICD–O–3 Histology X - X
T22 ICD–O–3 Behaviour - - X
T23 Grade, differentiation or cell indicator - - X
T24 Method used to establish the date of diagnosis - - X
T25 Diagnostic confirmation - - X
T26 Date of transmission X - X
T27 CS tumour size X - X
T28 CS extension X - X
T29 CS tumour size/ext eval - - X
T30 CS lymph nodes X - X
T31 CS reg nodes eval - - X
T32 Regional nodes examined X - X
T33 Regional nodes positive X - X
T34 CS mets at dx X - X
T35 CS mets eval - - X
T36 CS site-specific factor 1 X - X
T37 CS site-specific factor 2 X - X
T38 CS site-specific factor 3 X - X
T39 CS site-specific factor 4 X - X
T40 CS site-specific factor 5 X - X
T41 CS site-specific factor 6 X - X
T42 AJCC clinical T X X X
T43 AJCC clinical N X X X
T44 AJCC clinical M X X X
T45 AJCC pathologic T X X X
T46 AJCC pathologic N X X X
T47 AJCC pathologic M X X X
T48 AJCC clinical TNM stage group X X X
T49 AJCC pathologic TNM stage group X X X
T50 AJCC TNM stage group X X X
T51 AJCC TNM edition number X - X
T52 CS Version 1st X - X
T53 Ambiguous Terminology Diagnosis - - X
T54 Date of Conclusive Diagnosis X - X
T55 Type of Multiple Tumours Reported as One Primary X - X
T56 Date of Multiple Tumours X - X
T57 Multiplicity Counter X - X

Revision

Year Description
2008 Tumour input variables T53 to T57 have been added to the record layout. Different formatting processes are done to each new variable.
2007 T52 – CS Version 1st – tumour input variable added to record layout. It is left justified and trailing blanks are removed.
2004 In order to reduce response burden, some data items will automatically be uppercased, left justified and right truncated (removal of trailing blanks) by the CCR system.
T3 – Tumour reference number: Values will not be zero left filled anymore.

3.3.2 Old classification filtering

Description

This step deletes disease classification information reported by PTCRs older than that indicated by the source classification flag.

Purpose

This step eliminates the possibility of incoherence between source classification data (as identified by the source classification flag) and any former classification data.

Logic

  • If the Source classification flag indicates that ICD-9 is the source classification, then all reported data are kept as is.
  • If the Source classification flag indicates that ICD-O-2 is the source classification, then reported ICD-9 Cancer Code is replaced by '0000'.
  • If the Source classification flag indicates that ICD-O-3 is the source classification, then reported ICD-9 Cancer Code and ICD-O-2 Histology are replaced by '0000' and reported ICD-O-2 Behaviour is replaced by '0'.
  • In any other case, all reported data are kept as is.

This step will not create a feedback message. The following examples and table illustrate possible scenarios.

Example 1: If source classification flag indicates ICD-9, then no change.
Example 2: If source classification flag indicates ICD-O-2, then ICD-9 is not loaded.
Example 3: If source classification flag indicates ICD-O-3, then ICD-9 and ICD-O-2H/B are not loaded. ICD-O-2/3T is kept since it also belongs to ICD-O-3.

Table 23 Old classification filtering
Example TSCF ICD-9 ICD-O-2/3T ICD-O-2H ICD-O-2B ICD-O-3H ICD-O-3B
1 Before 1 175 C509 8521 3 8521 3
After 1 175 C509 8521 3 8521 3
2 Before 2 175 C509 8521 3 8521 3
After 2 0000 C509 8521 3 8521 3
3 Before 4 175 C509 8521 3 8521  
After 4 0000 C509 0000 0 8521 3

3.3.3 ICD-O-2/3 Topography calculation

Background

For cases diagnosed from 1992 to 2000, the Canadian Council of Cancer Registries adopted the International Classification of Diseases for Oncology, Second Edition (ICD-O-2) as the standard for reporting diagnostic information to the Canadian Cancer Registry (CCR). This classification was chosen because it provides detailed information on the site (topography), the histology and the behaviour of the neoplasm. The site codes are based on the malignant neoplasms section (C00-C80) of the International Statistical Classification of Diseases and Related Health Problems, Tenth revision (ICD-10). The morphology codes are revised and expanded from its predecessor, the ICD-O-1. The International Classification of Diseases is a classification system which covers the broad range of diseases and other health problems for which health care services may be rendered. The ICD has been in use in Canada for many decades for morbidity (hospitalization) and mortality (death) reporting. The Ninth revision (ICD-9), in use since 1979, has been replaced by the ICD-10 for morbidity and mortality. Chapter 2 of the ICD-9 (Neoplasms) provides a classification of tumours, primarily by site and includes behaviour. The ICD-O-2 supplements site information with tumour morphology detail. This greater level of specificity makes ICD-O more suitable for cancer registration purposes.

By 1992, the data year for which the CCR became operational, all provincial/territorial cancer registries except Ontario and Québec had implemented the ICD-O-2 for reporting tumour site and morphology. Ontario and Québec had adopted the ICD-O-2 for reporting tumour morphology information, but continued to report the site of tumours using the ICD-9, for administrative reasons. In order to bring all data to a common basis, the ICD-9 to ICD-O-2 conversion was created, cooperatively by Statistics Canada, the Ontario Cancer Treatment and Research Foundation and the Fichier des tumeurs du Québec.

Description

This step computes ICD-O-2/3 Topography code from the reported ICD-9 Cancer code when needed.

Purpose

This step ensures that, for each reported tumour, the site is described using the ICD-O-3 classification. This facilitates the comparison between all tumours reported to the CCR.

Logic

If ICD-O-2/3 Topography = '0000' and Source classification flag = '1' then
If ICD-9 Cancer code is found in ICD-9 to ICD-O-2 conversion table6 then
ICD-O-2/3 Topography = ICD-O-2/3 Topography code associated to ICD-9 Cancer code in ICD-9 to ICD-O-2 conversion table.
Else (ICD-9 Cancer code is NULL or NOT found in ICD-9 to ICD-O-2 conversion table)
Warning saying "ICD-O-2/3 Topography calculation: Conversion failed." is sent to the reporting PTCR.
End If
End If

Directions

The process of converting coded information from one disease classification system to another can result in a distortion or loss of original diagnostic detail. Whenever possible, it is recommended that the original descriptive diagnosis be coded directly, using the preferred, most recent classification system.

Registries using both the ICD-O-2/3 topography and the ICD-9 to code tumour sites are requested to report only ICD-O-2/3 topography codes to the CCR. ICD-9 codes should only be reported to the CCR if ICD-O-2/3 topography codes are not available.

3.3.4 ICD-O-3 Histology and behaviour calculation

Background

For cases diagnosed from 2001 onwards, the Canadian Council of Cancer Registries adopted the International Classification of Diseases for Oncology, Third edition (ICD-O-3) as the standard for reporting diagnostic information to the Canadian Cancer Registry (CCR). The topography section of the Third edition remains the same as the Second edition; however it includes revised morphologies and new classifications especially for lymphomas and leukemias. This classification was adopted because it represents the most current classification of diseases for oncology.

Description

This step computes the ICD-O-3 Histology and the ICD-O-3 behaviour from reported ICD-O-2 histology and ICD-O-2 behaviour when needed.

Purpose

This step ensures that, for each reported tumour, the histology and behaviour are described using the ICD-O-3 classification. This facilitates the comparison between all tumours reported to the CCR.

If ICD-O-3 Histology = '0000' and ICD-O-3 Behaviour = '0' and Source Classification Flag = '1' or '2' 'then
If ICD-O-2/3 Topography, ICD-O-2 Histology and ICD-O-2 Behaviour combination is found in ICD-O-2 to ICD-O-3 conversion table6 then
ICD-O-3 Histology = ICD-O-3 Histology code associated to ICD-O-2/3 Topography, ICD-O-2 Histology and ICD-O-2 Behaviour combination in ICD-O-2 to ICD-O-3 conversion table
ICD-O-3 Behaviour = ICD-O-3 Behaviour code associated to ICD-O-2/3 Topography, ICD-O-2 Histology and ICD-O-2 Behaviour combination in ICD-O-2 to ICD-O-3 conversion table
If the Review Flag associated to ICD-O-2/3 Topography, ICD-O-2 Histology and ICD-O-2 Behaviour combination in ICD-O-2 to ICD-O-3 conversion table = '1' then
Warning saying "ICD-O-3 Histology and Behaviour calculation: Values must be manually reviewed." is sent to the reporting PTCR.
Else (ICD-O-2/3 Topography is NULL or ICD-O-2 Histology is NULL or ICD-O-2 Behaviour is NULL or the combination is NOT found in ICD-O-2 to ICD-O-3 conversion table)
Warning saying "ICD-O-3 Histology and Behaviour calculation: Conversion failed." is sent to the reporting PTCR.
End If
End If

This step ensures that, for each reported tumour, the histology and behaviour are described using the ICD-O-3 classification. This facilitates the comparison between all tumours reported to the CCR

3.3.5 Laterality adjustment

Background

Although the ICD-9 and the ICD-O-3 may be used for similar purposes, they are not totally compatible. Since the ICD-9 and the ICD-O-3 use different topographic groupings, there are cases where the laterality code may be coherent with a given ICD-9 Cancer code but may be incoherent with the closest corresponding ICD-O-2/3 topography code. Thus, for these exceptional cases, the laterality code must be altered to be compliant with the ICD-O-3 classification.

Description

This step alters the laterality code when specific ICD-9 Cancer codes are reported as source classification data and corresponding ICD-O-2/3 topography codes conflict with the reported laterality code due to classification incompatibility.

Purpose

This step reduces PTCR response burden by fixing classification incompatibility issues that would otherwise cause an input record to be rejected.

Logic

If Source Classification Flag = '1' and ICD-9 Cancer Code in ['1460','2021','2022','2382'] and Laterality = '0' then
Laterality = '9'
Warning saying "Laterality Adjustment: Laterality code has been changed from '0' to '9' in order to be compliant with ICD-O-3 classification." is sent to the reporting PTCR.
End if

3.4 Validation Edits

The purpose of the Validation edits is to enforce the business rules on each individual field. For ease of use, validation edits have been divided into two groups:

  • Patient validation edits: enforce business rules on patient fields;
  • Tumour validation edits: enforce business rules on tumour fields.

3.4.1 Patient validation edits

The following table summarizes the purpose of each individual edit of this category.

Table 24 Patient validation edits summary
Edit name Purpose
PVAL1 Validates the Patient reporting province/territory code.
PVAL2 Validates the Patient identification number.
PVAL3 Validates the CCR identification number.
PVAL4 Validates the Patient record type code.
PVAL5 Validates the Type of current surname code.
PVAL6 Validates the Current surname.
PVAL7 Validates the First given name.
PVAL8 Validates the Second given name.
PVAL9 Validates the Third given name.
PVAL10 Validates the Sex code.
PVAL11 Validates the Date of birth.
PVAL12 Validates the Province/territory or country of birth code.
PVAL13 Validates Birth surname.
PVAL14 Validates Date of death.
PVAL15 Validates the Province/territory or country of death code.
PVAL16 Validates Death registration number.
PVAL17 Validates the Underlying cause of death code.
PVAL18 Validates Autopsy confirming cause of death code.
PVAL19 Validates Patient record date of transmission.

PVAL1

This edit validates the patient reporting province/territory code.

Referenced fields (PVAL1)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
Other parameters (PVAL1)
Parameters Length Description
PTCR_CODE 2 Province/territory code of the PTCR that is submitting the data.

Business rules

For Input patient records
  • Patient reporting province/territory must be equal to province/territory code of the PTCR submitting the data7.
Edit logic (PVAL1)
Sub–edit Conditions Outcome
PVAL1-1 P1 <> PTCR_CODE Record rejected
Feedback report messages (PVAL1)
Sub–edit Text Type
PVAL1-1 Patient reporting province/territory code does not match PTCR province/territory code. Core error
Revision (PVAL1)
Year Description
Not applicable Not applicable

PVAL2

Purpose

This edit validates the patient identification number.

Referenced fields (PVAL2)
Field Length Description Acronym
P2 12 Patient identification number PPIN

Business rules

On any type of Input patient record, Patient identification number
  • Must be exclusively composed of any of the following:
    • Uppercase letters: A to Z
    • Numbers: 0 to 9
  • Cannot be exclusively composed of zeros.
Edit logic (PVAL2)
Sub–edit Conditions Outcome
PVAL2-1 IS_COMPOSED_OF (P2, ‘0') Record rejected
PVAL2-2 NOT IS_COMPOSED_OF (P2, ‘ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789') Record rejected
Feedback report messages (PVAL2)
Sub–edit Text Type
PVAL2-1 Patient identification number cannot be exclusively composed of zeros. Core error
PVAL2-2 Patient identification number is not exclusively composed of uppercase letters and/or numbers. Core error
Revision (PVAL2)
Year Description
2004 Business rule changed: Apostrophes, hyphens, periods and inner spaces are not accepted anymore.

PVAL3

Purpose

This edit validates the CCR identification number.

Referenced fields (PVAL3)
Field Length Description Acronym
P3 9 CCR identification number CCR_ID
P3.ID 8 First 8 digits of P3 (CCR ID sequence number) Not applicable
P3.CHECK_DIGIT 1 9th digit of P3 (CCR ID check digit) Not applicable
P4 1 Patient record type PRECTYPE

Business rules

For Update and Delete Patient records, CCR identification number
  • Must be exclusively composed of numbers: 0 to 9
  • Must be 9 digits long.
  • Cannot be all zeros.
  • Must have a valid check digit8.
Edit logic (PVAL3)
Sub–edit Conditions Outcome
PVAL3-1 P4 IN [‘2', ‘3'] AND (LENGTH (P3) <> 9 OR NOT IS_COMPOSED_OF (P3, ‘0123456789')) Record rejected
PVAL3-2 P4 IN [‘2', ‘3'] AND P3 = ‘000000000' Record rejected
PVAL3-3 P4 IN [‘2', ‘3'] AND P3 <> ‘000000000' AND LENGTH (P3) = 9 AND IS_COMPOSED_OF (P3, ‘0123456789') AND P3.CHECK_DIGIT <> CALCULATE_CCR_CHECK_DIGIT (P3.ID) Record rejected
Feedback report messages (PVAL3)
Sub–edit Text Type
PVAL3-1 CCR identification number is not 9 digits long. Core error
PVAL3-2 CCR identification number cannot be all zeros. Core error
PVAL3-3 CCR identification number is invalid. Core error
Revision (PVAL3)
Year Description
Not applicable Not applicable

PVAL4

Purpose

This edit validates the patient record type code.

Referenced fields (PVAL4)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE

Business rules

For Input Patient records, Patient record type
  • Cannot be blank.
  • Must be one of the Eligible patient record type codes9.
Edit logic (PVAL4)
Sub–edit Conditions Outcome
PVAL4-1 P4 IS NULL OR P4 NOT IN [Eligible Patient record type codes] Record rejected
Feedback report messages(PVAL4)
Sub–edit Text Type
PVAL4-1 Patient record type code is missing or invalid. Core fatal error
Revision (PVAL4)
Year Description
Not applicable Not applicable

PVAL5

Purpose

This edit validates the type of current surname code.

Referenced fieldds (PVAL5)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P5 1 Type of current surname PTYP_CUR

Business rules

For Add and Update Patient records
  • Type of Current Surname must be one of the Eligible type of current surname codes10.
Edit logic (PVAL5)
Sub–edit Conditions Outcome
PVAL5-1 P4 IN [‘1', ‘2'] AND P5 NOT IN [Eligible type of current surname codes] Record rejected
Feedback report messages (PVAL5)
Sub–edit Text Type
PVAL5-1 Type of current surname code is invalid. Core error
Revision (PVAL5)
Year Description
Not applicable Not applicable

PVAL6

Purpose

This edit validates the current surname.

Referenced fields (PVAL6)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P6 25 Current surname PCURSNAM

Business rules

For Add and Update Patient records
  • Current surname can be blank.
  • If Current surname is not blank then
    • It must be exclusively composed of any of the following:
      • Letters: A to Z (upper or lowercase)
      • Accented characters: Â À Ç É Ê Ë È Î Ï Ô Û Ü (upper or lowercase)
      • Special characters: space ( ), period (.), apostrophe ('), hyphen (-)
    • It must contain at least one letter.
Edit logic (PVAL6)
Sub–edit Conditions Outcome
PVAL6-1 P4 IN [‘1', ‘2'] AND P6 IS NOT NULL AND NOT IS_COMPOSED_OF (UPPER (P6), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') Record rejected
PVAL6-2 P4 IN [‘1', ‘2'] AND P6 IS NOT NULL AND IS_COMPOSED_OF (UPPER (P6), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') AND NOT CONTAINS_WORD (UPPER (P6), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ', 1) Record rejected
Feedback report messages (PVAL6)
Sub–edit Text Type
PVAL6-1 Current surname is not exclusively composed of acceptable letters, accented characters or special characters. Core error
PVAL6-2 Current surname does not contain at least one letter. Core error
Revision (PVAL6)
Year Description
2007 Business rules changed: Acceptable accented characters are specified.
2004 Business rules changed: Titles are now allowed in current surname.

PVAL7

Purpose

This edit validates the first given name.

Referenced fields (PVAL7)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P7 15 First given name PGNAME_1

Business rules

For Add and Update Patient records
  • First given name can be blank.
  • If First given name is not blank then
    • It must be exclusively composed of any of the following:
      • Letters: A to Z (upper or lowercase)
      • Accented characters: Â À Ç É Ê Ë È Î Ï Ô Û Ü (upper or lowercase)
      • Special characters: space ( ), period (.), apostrophe ('), hyphen (-)
    • It must contain at least one letter.
Edit logic (PVAL7)
Sub–edit Conditions Outcome
PVAL7-1 P4 IN [‘1', ‘2'] AND P7 IS NOT NULL AND NOT IS_COMPOSED_OF (UPPER (P7), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') Record rejected
PVAL7-2 P4 IN [‘1', ‘2'] AND P7 IS NOT NULL AND IS_COMPOSED_OF (UPPER (P7), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') AND NOT CONTAINS_WORD (UPPER (P7), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ', 1) Record rejected
Feedback report messages (PVAL7)
Sub–edit Text Type
PVAL7-1 First given name is not exclusively composed of acceptable letters, accented characters or special characters. Core error
PVAL7-2 First given name does not contain at least one letter. Core error
Revision (PVAL7)
Year Description
2007 Business rules changed: Acceptable accented characters are specified.

PVAL8

Purpose

This edit validates the second given name.

Referenced fields (PVAL8)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P8 15 Second given name PGNAME_2

Business rules

For Add and Update Patient records
  • Second given name can be blank.
  • If Second given name is not blank then
    • It must be exclusively composed of any of the following:
      • Letters: A to Z (upper or lowercase)
      • Accented characters: Â À Ç É Ê Ë È Î Ï Ô Û Ü (upper or lowercase)
      • Special characters: space ( ), period (.), apostrophe ('), hyphen (-)
    • It must contain at least one letter
Edit logic(PVAL8)
Sub–edit Conditions Outcome
PVAL8-1 P4 IN [‘1', ‘2'] AND P8 IS NOT NULL AND NOT IS_COMPOSED_OF (UPPER (P8), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') Record rejected
PVAL8-2 P4 IN [‘1', ‘2'] AND P8 IS NOT NULL AND IS_COMPOSED_OF (UPPER (P8), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') AND NOT CONTAINS_WORD (UPPER (P8), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ', 1) Record rejected
Feedback report messages (PVAL8)
Sub–edit Text Type
PVAL8-1 Second given name is not exclusively composed of acceptable letters, accented characters or special characters. Core error
PVAL8-2 Second given name does not contain at least one letter. Core error
Revision (PVAL8)
Year Description
2007 Business rules changed: Acceptable accented characters are specified.

PVAL9

Purpose

This edit validates the third given name.

Referenced fields (PVAL9)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P9 7 Third given name PGNAME_3

Business rules

For Add and Update Patient records
  • Third given name can be blank.
  • If Third given name is not blank then
    • It must be exclusively composed of any of the following:
      • Letters: A to Z (upper or lowercase)
      • Accented characters: Â À Ç É Ê Ë È Î Ï Ô Û Ü (upper or lowercase)
      • Special characters: space ( ), period (.), apostrophe ('), hyphen (-)
    • It must contain at least one letter.
Edit logic (PVAL9)
Sub–edit Conditions Outcome
PVAL9-1 P4 IN [‘1', ‘2'] AND P9 IS NOT NULL AND NOT IS_COMPOSED_OF (UPPER (P9), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') Record rejected
PVAL9-2 P4 IN [‘1', ‘2'] AND P9 IS NOT NULL AND IS_COMPOSED_OF (UPPER (P9), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') AND NOT CONTAINS_WORD (UPPER (P9), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ', 1) Record rejected
Feedback report messages (PVAL9)
Sub edit Text Type
PVAL9-1 Third given name is not exclusively composed of acceptable letters, accented characters or special characters. Core error
PVAL9-2 Third given name does not contain at least one letter. Core error
Revision (PVAL9)
Year Description
2007 Business rules changed: Acceptable accented characters are specified.

PVAL10

Purpose

This edit validates the sex code.

Referenced fields (PVAL10)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P10 1 Sex PSEX

Business rules

For Add and Update Patient records
  • Sex must be one of the Eligible sex codes11.
Edit logic (PVAL10)
Sub–edit Conditions Outcome
PVAL10-1 P4 IN [‘1', ‘2'] AND P10 NOT IN [Eligible sex codes] Record rejected
Feedback report messages (PVAL10)
Sub–edit Text Type
PVAL10-1 Sex code is invalid. Core error
Revision (PVAL10)
Year Description
Not applicable Not applicable

PVAL11

Purpose

This edit validates the date of birth.

Referenced fields (PVAL11)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P11 8 Date of birth PDATBIR
P11.YEAR 4 First 4 digits of P11 (year of date of birth) Not applicable
P11.MONTH 2 5th and 6th digits of P11 (month of date of birth) Not applicable
P11.DAY 2 7th and 8th digits of P11 (day of date of birth) Not applicable
Other parameters (PVAL11)
Parameters Length Description
CYCLE_YEAR 2 Reference year

Business rules

For Add and Update Patient records, Date of birth
  • Must be 8 digits long.
  • Must be between January 1st, 1875 and December 31st of Reference year inclusively.
  • If Year is unknown then Month must be unknown.
  • If Month is unknown then Day must be unknown.
  • If Year, Month and Day are known then it must be a valid calendar date.
  • If Year and Month are known and Day is unknown then month must be a valid month.
Edit logic (PVAL11)
Sub–edit Conditions Outcome
PVAL11-1 P4 IN [‘1', ‘2'] AND (LENGTH (P11) <> 8 OR NOT IS_COMPOSED_OF (P11, ‘0123456789')) Record rejected
PVAL11-2 P4 IN [‘1', ‘2'] AND LENGTH (P11) = 8 AND IS_COMPOSED_OF (P11, ‘0123456789') AND ((P11.YEAR = ‘9999' AND P11.MONTH <> ‘99') OR (P11.MONTH = ‘99' AND P11.DAY <> ‘99')) Record rejected
PVAL11-3 P4 IN [‘1', ‘2'] AND LENGTH (P11) = 8 AND IS_COMPOSED_OF (P11, ‘0123456789') AND P11.YEAR <> ‘9999' AND (P11.YEAR < 1875 OR P11.YEAR > CYCLE_YEAR) Record rejected
PVAL11-4 P4 IN [‘1', ‘2'] AND LENGTH (P11) = 8 AND IS_COMPOSED_OF (P11, ‘0123456789') AND P11.YEAR <> ‘9999' AND P11.MONTH <> ‘99' AND P11.DAY <> ‘99' AND IS_VALID_DATE (P11) Record rejected
PVAL11-5 P4 IN [‘1', ‘2'] AND LENGTH (P11) = 8 AND IS_COMPOSED_OF (P11, ‘0123456789') AND P11.YEAR <> ‘9999' AND P11.MONTH NOT IN [‘01'-'12', ‘99'] AND P11.DAY = ‘99' Record rejected
Feedback report messages (PVAL11)
Sub–edit Text Type
PVAL11-1 Date of birth is not 8 digits long. Core error
PVAL11-2 Date of birth: Improper use of the ‘Unknown' code. Core error
PVAL11-3 Date of birth must be between the year 1875 and the current reference year inclusively. Core error
PVAL11-4 Date of birth is not a valid calendar date. Core error
PVAL11-5 Date of birth is not a valid partial date: month is invalid. Core error
Revision (PVAL11)
Year Description
Not applicable Not applicable

PVAL12

Purpose

This edit validates the province/territory or country of birth code.

Referenced fields (PVAL12)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P11.YEAR 4 First 4 characters of P11 (year of date of birth) Not applicable
P12 3 Province/territory or country of birth PPROVBIR

Business rules

For Add and Update Patient records
  • If Date of birth is before 1996 then Province/territory or country of birth must be one of the Eligible Province/territory and country codes prior to 199612.
  • If Date of birth is on or after 1996 then Province/territory or country of birth must be one of the Eligible Province/territory and country codes in and after 199612
  • If Date of birth is unknown then Province/territory or country of birth must be either one of the Eligible Province/territory and country codes prior to 199612 or Eligible Province/territory and country codes in and after 199612.
Edit logic (PVAL12)
Sub–edit Conditions Outcome
PVAL12-1 P4 IN [‘1', ‘2'] AND P11.YEAR <> ‘9999' AND P11.YEAR < 1996 AND P12 NOT IN [Eligible Province/territory and country code prior to 1996] Record rejected
PVAL12-2 P4 IN [‘1', ‘2'] AND P11.YEAR <> ‘9999' AND P11.YEAR >= 1996 AND P12 NOT IN [Eligible Province/territory and country code in and after 1996] Record rejected
PVAL12-3 P4 IN [‘1', ‘2'] AND P11.YEAR = ‘9999' AND P12 NOT IN [Eligible Province/territory and country code prior to 1996] AND P12 NOT IN [Eligible Province/territory and country code in and after 1996] Record rejected
Feedback report messages (PVAL12)
Sub–edit Text Type
PVAL12-1 Province/territory or country of birth code is invalid for Date of birth prior to 1996. Core error
PVAL12-2 Province/territory or country of birth code is invalid for Date of birth in and after 1996. Core error
PVAL12-3 Province/territory or country of birth code is invalid. Core error
Revision PVAL12)
Year Description
2004 Business rules changed: Province/territory or country of birth code is now validated against Province/territory or country codes valid at time of birth.

PVAL13

Purpose

This edit validates birth surname.

Referenced fields (PVAL13)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P13 25 Birth surname PBIRNAM

Business rules

For Add and Update Patient records
  • Birth surname can be blank.
  • If Birth surname is not blank then
    • It must be exclusively composed of any of the following:
      • Letters: A to Z (upper or lowercase)
      • Accented characters: Â À Ç É Ê Ë È Î Ï Ô Û Ü (upper or lowercase)
      • Special characters: space ( ), period (.), apostrophe ('), hyphen (-)
    • It must contain at least one letter.
Edit logic (PVAL13)
Sub–edit Conditions Outcome
PVAL13-1 P4 IN [‘1', ‘2'] AND P13 IS NOT NULL AND NOT IS_COMPOSED_OF (UPPER (P13), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') Record rejected
PVAL13-2 P4 IN [‘1', ‘2'] AND P13 IS NOT NULL AND IS_COMPOSED_OF (UPPER (P13), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-') AND NOT CONTAINS_WORD (UPPER (P13), ‘ABCDEFGHIJKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ', 1) Record rejected
Feedback report messages (PVAL13)
Sub edit Text Type
PVAL13-1 Birth surname is not exclusively composed of acceptable letters, accented characters or special characters. Core error
PVAL13-2 Birth surname does not contain at least one letter. Core error
Revision Feedback report messages (PVAL13)
Year Description
2007 Business rules changed: Acceptable accented characters are specified.

PVAL14

Purpose

This edit validates date of death.

Referenced fields (PVAL14)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P14 8 Date of death PDATDEA
P14.YEAR 4 First 4 digits of P14 (year of date of death) Not applicable
P14.MONTH 2 5th and 6th digits of P14 (month of date of death) Not applicable
P14.DAY 2 7th and 8th digits of P14 (day of date of death) Not applicable
P19.YEAR 4 First 4 digits of P19 (year of date of transmission) Not applicable
P19.MONTH 2 5th and 6th digits of P19 (Month of date of transmission) Not applicable
P19.DAY 2 7th and 8th digits of P19 (Day of date of transmission) Not applicable

Business rules

For Add and Update Patient records, Date of death
  • Must be 8 digits long.
  • Can be all zeros (when patient is not known to have died).
  • Must be between January 1st, 1992 and Date of transmission inclusively.
  • If Year is unknown then Month must be unknown.
  • If Month is unknown then Day must be unknown.
  • If Year, Month and Day are known then it must be a valid calendar date.
  • If Year and Month are known and Day is unknown then Month must be a valid month.
Edit logic (PVAL14)
Sub–edit Conditions Outcome
PVAL14-1 P4 IN [‘1', ‘2'] AND (LENGTH (P14) <> 8 OR NOT IS_COMPOSED_OF (P14, ‘0123456789')) Record rejected
PVAL14-2 P4 IN [‘1', ‘2'] AND (P14.YEAR = ‘0000' OR P14.MONTH = ‘00' OR P14.DAY = ‘00') AND NOT (P14.YEAR = ‘0000' AND P14.MONTH = ‘00' AND P14.DAY = ‘00') Record rejected
PVAL14-3 P4 IN [‘1', ‘2'] AND LENGTH (P14) = 8 AND IS_COMPOSED_OF (P14, ‘0123456789') AND P14.YEAR NOT IN [‘0000', ‘9999'] AND ((P14.MONTH = ‘99' AND P14.DAY = ‘99' AND (P14.YEAR < 1992 OR P14.YEAR > P19.YEAR)) OR (P14.MONTH IN [‘01'-'12'] AND P14.DAY = ‘99' AND (P14.YEAR < 1992 OR P14.YEAR||P14.MONTH > P19.YEAR||P19.MONTH)) OR (P14.MONTH IN [‘01'-'12'] AND P14.DAY IN [‘01', ‘31'] AND IS_VALID_DATE (P14) AND (P14.YEAR < 1992 OR P14 > P19)) Record rejected
PVAL14-4 P4 IN [‘1', ‘2'] AND LENGTH (P14) = 8 AND IS_COMPOSED_OF (P14, ‘0123456789') AND ((P14.YEAR = ‘9999' AND P14.MONTH <> ‘99') or (P14.MONTH = ‘99' AND P14.DAY <> ‘99')) Record rejected
PVAL14-5 P4 IN [‘1', ‘2'] AND LENGTH (P14) = 8 AND IS_COMPOSED_OF (P14, ‘0123456789') AND P14.YEAR NOT IN [‘0000', ‘9999'] AND P14.MONTH NOT IN [‘00', ‘99'] AND P14.DAY NOT IN [‘00', ‘99'] AND NOT IS_VALID_DATE (P14) Record rejected
PVAL14-6 P4 IN [‘1', ‘2'] AND LENGTH (P14) = 8 AND IS_COMPOSED_OF (P14, ‘0123456789') AND P14.YEAR NOT IN [‘0000', ‘9999'] AND P14.MONTH NOT IN [‘00', ‘01'-'12', ‘99'] AND P14.DAY = ‘99' Record rejected
Feedback report messages (PVAL14)
Sub–edit Text Type
PVAL14-1 Date of death is not 8 digits long. Core error
PVAL14-2 Date of death: Improper use of ‘Patient is not known to have died' code. Core error
PVAL14-3 Date of death must be between January 1st, 1992 and the Date of Transmission inclusively. Core error
PVAL14-4 Date of death: Improper use of ‘Unknown' code. Core error
PVAL14-5 Date of death is not a valid calendar date. Core error
PVAL14-6 Date of death is not a valid partial date: month is invalid. Core error
Revision (PVAL14)
Year Description
2004 Business rules changed: Date of death cannot be beyond Date of transmission.

PVAL15

Purpose

This edit validates the province/territory or country of death code.

Referenced fields (PVAL15)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P14.YEAR 4 First 4 characters of P14 (year of date of death) Not applicable
P15 3 Province/territory or country of death PPROVDEA

Business rules

For Add and Update Patient records
  • If Date of death is before 1996 then Province/territory or country of death must be one of the Eligible province/territory and country codes prior to 199612.
  • If Date of death is on or after 1996 then Province/territory or country of death must be one of the Eligible province/territory and country codes in and after 199612.
  • If Date of death is unknown then Province/territory or country of death must be either one of the Eligible province/territory and country codes prior to 199612 or Eligible province/territory and country codes in and after 199612.
Edit Logic (PVAL15)
Sub–edit Conditions Outcome
PVAL15-1 P4 IN [‘1', ‘2'] AND P14.YEAR NOT IN [‘0000', ‘9999'] AND P14.YEAR < 1996 AND P15 NOT IN [Eligible province/territory or country codes prior to 1996] Record rejected
PVAL15-2 P4 IN [‘1', ‘2'] AND P14.YEAR NOT IN [‘0000', ‘9999'] AND P14.YEAR >= 1996 AND P15 NOT IN [Eligible province/territory or country codes in and after 1996] Record rejected
PVAL15-3 P4 IN [‘1', ‘2'] AND P14.YEAR = ‘9999' AND P15 NOT IN [Eligible Province/Territory or Country of Death codes in and after 1996] AND P15 NOT IN [Eligible province/territory or country codes prior to 1996] Record rejected
Feedback report messages (PVAL15)
Sub–edit Text Type
PVAL15-1 Province/territory or country of death code is invalid for Date of death prior to 1996. Core error
PVAL15-2 Province/territory or country of death code is invalid for Date of death in and after 1996. Core error
PVAL15-3 Province/territory or country of death code is invalid. Core error
Revision (PVAL15)
Year Description
2004 Business rules changed: Province/territory or country of death code is now validated against Province/territory or country codes valid at time of death.

PVAL16

Purpose

This edit validates the death registration number.

Referenced fields (PVAL16)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P16 6 Death registration number PDEAREG

Business rules

For Add and Update Patient records, Death registration number
  • Must be exclusively composed of numbers: 0 to 9
  • Must be 6 digits long
Edit logic (PVAL16)
Sub–edit Conditions Outcome
PVAL16-1 P4 IN [‘1', ‘2'] AND (LENGTH (P16) <> 6 OR NOT IS_COMPOSED_OF (P16, ‘0123456789')) Record rejected
Feedback report messages (PVAL16
Sub–edit Text Type
PVAL16-1 Death registration number is not 6 digits long. Core error
Revision (PVAL16)
Year Description
Not applicable Not applicable

PVAL17

Purpose

This edit validates the underlying cause of death code.

Referenced fields (PVAL17)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P14.YEAR 4 First 4 characters of P14 (year of date of death) Not applicable
P17 3 Underlying cause of death PCAUSDEA

Business rules

For Add and Update Patient records
  • IF Date of death is unknown then Underlying cause of death must be coded as ‘Unknown/unavailable Underlying cause of death'.
  • IF Date of death is before 2000 then Underlying cause of death must be one of the Eligible ICD-9 underlying cause of death codes12.
  • IF Date of death is between 2000 and 2002 inclusively then Underlying cause of death must be one of the Eligible ICD-10 underlying cause of death codes in 2000-200212
  • IF Date of death is in or after 2003 then Underlying cause of death must be one of the Eligible ICD-10 underlying cause of death codes in 2003 and after13.
Edit logic (PVAL17)
Sub–edit Conditions Outcome
PVAL17-1 P4 IN [‘1', ‘2'] AND P14.YEAR = ‘9999' AND P17 <> ‘0009' Record rejected
PVAL17-2 P4 IN [‘1', ‘2'] AND P14.YEAR NOT IN [‘0000', ‘9999'] AND P14.YEAR < 2000 AND P17 NOT IN [ICD-9 – Cause of death] Record rejected
PVAL17-3 P4 IN [‘1', ‘2'] AND P14.YEAR NOT IN [‘0000', ‘9999'] AND P14.YEAR >= 2000 AND P14.YEAR <= 2002 AND P17 NOT IN [ICD-10 – Cause of death in 2000-2002] Record rejected
PVAL17-4 P4 IN [‘1', ‘2'] AND P14.YEAR NOT IN [‘0000', ‘9999'] AND P14.YEAR >= 2003 AND P17 NOT IN [ICD-10 – Cause of death in 2003 and after] Record rejected
Feedback report messages (PVAL17)
Sub–edit Text Type
PVAL17-1 Underlying cause of death must be set to unknown when the Date of death is unknown. Core error
PVAL17-2 Underlying cause of death code is either invalid or not eligible for Date of death prior to 2000. Core error
PVAL17-3 Underlying cause of death code is either invalid or not eligible for Date of death between 2000 and 2002 inclusively. Core error
PVAL17-4 Underlying cause of death code is either invalid or not eligible for Date of death in or after 2003. Core error
Revision (PVAL17)
Year Description
2004 Business rules added:
If Date of death is unknown then Underlying cause of death must be coded as ‘Unknown/unavailable Underlying cause of death'.
If Date of death is in 2003 or after then Underlying cause of death must be coded using the latest revision of ICD-10 Underlying cause of death (2003 and after).

PVAL18

Purpose

This edit validates autopsy confirming cause of death code.

Referenced fields (PVAL18)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P18 1 Autopsy confirming cause of death PAUTOPSY

Business rules

For Add and Update Patient records
  • Autopsy confirming cause of death must be one of the eligible autopsy confirming cause of death codes14.
Edit logic (PVAL18)
Sub–edit Conditions Outcome
PVAL18-1 P4 IN [‘1', ‘2'] AND P18 NOT IN [Eligible Autopsy confirming cause of death codes] Record rejected
Feedback report messages (PVAL18)
Sub–edit Text Type
PVAL18-1 Autopsy confirming cause of death code is invalid. Core error
Revision (PVAL18)
Year Description
Not applicable Not applicable

PVAL19

Purpose

This edit validates the patient record date of transmission.

Referenced fields (PVAL19)
Field Length Description Acronym
P19 8 Patient Date of transmission PDATTRAN
P19.YEAR 4 First 4 digits of P19 (year of date of transmission) Not applicable
P19.MONTH 2 5th and 6th digits of P19 (month of date of transmission) Not applicable
P19.DAY 2 7th and 8th digits of P19 (day of date of transmission) Not applicable
Other parameters (PVAL19)
Parameters Length Description
LOAD_DATE 8 Statistics Canada loading date: date on the Statistics Canada computer clock when the data are loaded on the CCR database.

Business rules

For Input Patient records, Patient Date of transmission
  • Cannot be blank
  • Must be exclusively composed of numbers: 0 to 9
  • Must be 8 digits long
  • Must be a valid calendar date
  • Must be within the previous 10 months from Statistics Canada loading date
Edit logic (PVAL19)
Sub–edit Conditions Outcome
PVAL19-1 P19 IS NULL Record rejected
PVAL19-2 P19 IS NOT NULL AND (LENGTH (P19) <> 8 OR NOT IS_COMPOSED_OF (P19, ‘0123456789')) Record rejected
PVAL19-3 P19 IS NOT NULL AND LENGTH (P19) = 8 AND IS_COMPOSED_OF (P19, ‘0123456789') AND NOT IS_VALID_DATE (P19) Record rejected
PVAL19-4 P19 IS NOT NULL AND LENGTH (P19) = 8 AND IS_COMPOSED_OF (P19, ‘0123456789') AND IS_VALID_DATE (P19) AND P19 > LOAD_DATE () Record rejected
PVAL19-5 P19 IS NOT NULL AND LENGTH (P19) = 8 AND IS_COMPOSED_OF (P19, ‘0123456789') AND IS_VALID_DATE (P19) AND P19 < (LOAD_DATE – 10 months) Record rejected
Feedback report messages (PVAL19)
Sub–edit Text Type
PVAL19-1 Patient Date of transmission is missing. Core fatal error
PVAL19-2 Patient Date of transmission is not 8 digits long. Core fatal error
PVAL19-3 Patient Date of transmission is not a valid calendar date. Core fatal error
PVAL19-4 Patient Date of transmission is after Statistics Canada loading date. Core fatal error
PVAL19-5 Patient Date of transmission is more than 10 months before Statistics Canada loading date. Core fatal error
Revision (PVAL19)
Year Description
Not applicable Not applicable

3.4.2 Tumour validation edits

The following table summarizes the purpose of each individual edit of this category.

Table 25 Tumour validation edits summary

Table 25 Tumour validation edits summary
Edit name Purpose
TVAL1 Validates the Tumour reporting province/territory code.
TVAL2 Validates the Tumour patient identification number.
TVAL3 Validates the Tumour reference number.
TVAL4 Validates the CCR identification number.
TVAL5 Validates the Tumour record type code.
TVAL6 Validates the Name of place of residence.
TVAL7 Validates the Postal code.
TVAL8 Validates the Standard geographic code.
TVAL9 Validates the Census tract.
TVAL10 Validates the Health insurance number (HIN).
TVAL11 Validates the Method of diagnosis code.
TVAL12 Validates the Date of diagnosis.
TVAL13 Validates the ICD-9 cancer code.
TVAL14 Validates the Source classification flag.
TVAL15 Validates the ICD-O-2/3 Topography code.
TVAL16 Validates the ICD-O-2 Histology code.
TVAL17 Validates the ICD-O-2 Behaviour code.
TVAL18 Not applicable
TVAL19 Validates the Laterality code.
TVAL20 Not applicable
TVAL21 Validates the ICD-O-3 Histology code.
TVAL22 Validates the ICD-O-3 Behaviour code.
TVAL23 Validates the grade, differentiation or cell indicator code.
TVAL24 Validates the Method used to establish the date of diagnosis code.
TVAL25 Validates the Diagnostic confirmation code.
TVAL26 Validates the Date of transmission.
TVAL27 Validates CS tumour size.
TVAL28 Validates CS extension.
TVAL29 Validates CS tumour size/ext eval.
TVAL30 Validates CS lymph nodes.
TVAL31 Validates CS reg nodes eval.
TVAL32 Validates Regional nodes examined.
TVAL33 Validates Regional nodes positive.
TVAL34 Validates CS mets at dx.
TVAL35 Validates CS mets eval.
TVAL36 Validates CS site-specific factor 1.
TVAL37 Validates CS site-specific factor 2.
TVAL38 Validates CS site-specific factor 3.
TVAL39 Validates CS site-specific factor 4.
TVAL40 Validates CS site-specific factor 5.
TVAL41 Validates CS site-specific factor 6.
TVAL42 Validates AJCC clinical T.
TVAL43 Validates AJCC clinical N.
TVAL44 Validates AJCC clinical M.
TVAL45 Validates AJCC pathologic T.
TVAL46 Validates AJCC pathologic N.
TVAL47 Validates AJCC pathologic M.
TVAL48 Validates AJCC clinical TNM stage group.
TVAL49 Validates AJCC pathologic TNM stage group.
TVAL50 Validates AJCC TNM stage group.
TVAL51 Validates AJCC edition number code.
TVAL52 Validates CS Version 1st.
TVAL53 Validates Ambiguous Terminology Diagnosis.
TVAL54 Validates Date of Conclusive Diagnosis.
TVAL55 Validates Type of Multiple Tumours Reported as One Primary.
TVAL56 Validates Date of Multiple Tumours.
TVAL57 Validates Multiplicity Counter.

TVAL1

Purpose

This edit validates the Tumour reporting province/territory code.

Referenced Fields (TVAL1)
Field Length Description Acronym
T1 2 Tumour reporting province/territory TREPPROV
Other parameters (TVAL1)
Parameters Length Description
PTCR_CODE 2 Province/territory code of the PTCR that is submitting the data.

Business rules

For Input Tumour records
  • Tumour reporting province/territory must be equal to province/territory code of the PTCR that is submitting the data15.
Edit logic (TVAL1)
Sub–edit Conditions Outcome
TVAL1-1 T1 <> PTCR_CODE Record rejected
Feedback report messages (TVAL1)
Sub–edit Text Type
TVAL1-1 Tumour reporting province/territory code does not match PTCR province/territory code. Core error
Revision (TVAL1)
Year Description
Not applicable Not applicable

TVAL2

Purpose

This edit validates the tumour patient identification number.

Referenced fields (TVAL2)
Field Length Description Acronym
T2 12 Tumour patient identification number TPIN

Business rules

For Input Tumour records, Patient identification number
  • Must be exclusively composed of any of the following:
    • Uppercase letters: A to Z
    • Numbers: 0 to 9
  • Cannot be exclusively composed of zeros.
Edit logic (TVAL2)
Sub–edit Conditions Outcome
TVAL2-1 IS_COMPOSED_OF (T2, ‘0') Record rejected
TVAL2-2 NOT IS_COMPOSED_OF (T2, ‘ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789') Record rejected
Feedback report messages (TVAL2)
Sub–edit Text Type
TVAL2-1 Patient identification number cannot be exclusively composed of zeros. Core error
TVAL2-2 Patient identification number is not exclusively composed of uppercase letters and/or numbers. Core error
Revision (TVAL2)
Year Description
2004 Business rule changed: Apostrophes, hyphens, periods and inner spaces are not accepted anymore.

TVAL3

Purpose

This edit validates the tumour reference number.

Referenced fields (TVAL3)
Field Length Description Acronym
T3 9 Tumour reference number TTRN

Business rules

For Input Tumour records, Tumour reference number
  • Must be exclusively composed of any of the following:
    • Numbers: 0 to 9
    • Uppercase letters: A to Z
    • Special characters: space ( ), period (.), apostrophe (‘), hyphens (-)
  • Cannot be exclusively composed of zeros.
Edit logic (TVAL3)
Sub–edit Conditions Outcome
TVAL3-1 IS_COMPOSED_OF (T3, ‘0') Record rejected
TVAL3-2 NOT IS_COMPOSED_OF (T3, ‘ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789 -‘.') Record rejected
Feedback report messages (TVAL3)
Sub–edit Text Type
TVAL3-1 Tumour reference number cannot be exclusively composed of zeros. Core error
TVAL3-2 Tumour reference number is not exclusively composed of acceptable letters, numbers or special characters. Core error
Revision (TVAL3)
Year Description
2004 Business rule added: Tumour reference number cannot be exclusively composed of zeros.

TVAL4

Purpose

This edit validates the CCR identification number.

Referenced fields (TVAL4)
Field Length Description Acronym
T4 9 CCR identification number CCR_ID
T4.ID 8 First 8 digits of T4 (CCR ID sequence number) Not applicable
T4.CHECK_DIGIT 1 9th digit of T4 (CCR ID check digit) Not applicable

Business rules

For Input Tumour records
  • If CCR identification number is reported then
    • Must be exclusively composed of numbers: 0 to 9
    • Must be 9 digits long;
    • Cannot be all zeros;
    • Must have a valid check digit16.
Edit logic (TVAL4)
Sub–edit Conditions Outcome
TVAL4-1 T4 IS NOT NULL AND (LENGTH (T4) <> 9 OR NOT IS_COMPOSED_OF (T4, ‘0123456789')) Record rejected
TVAL4-2 T4 = ‘000000000' Record rejected
TVAL4-3 T4 IS NOT NULL AND T4 <> ‘000000000' AND LENGTH (T4) = 9 AND IS_COMPOSED_OF (T4, ‘0123456789') AND T4.CHECK_DIGIT <> CALCULATE_CCR_CHECK_DIGIT (T4.ID) Record rejected
Feedback report messages (TVAL4)
Sub–edit Text Type
TVAL4-1 CCR identification number is not 9 digits long. Core error
TVAL4-2 CCR identification number cannot be all zeros. Core error
TVAL4-3 CCR identification number is invalid. Core error
Revision (TVAL4)
Year Description
Not applicable Not applicable

TVAL5

Purpose

This edit validates the tumour record type code.

Referenced fields (TVAL5)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE

Business rules

For Input Tumour records, Tumour record type
  • Cannot be blank.
  • Must be one of the Eligible tumour record type codes17 .
Edit logic (TVAL5)
Sub–edit Conditions Outcome
TVAL5-1 T5 IS NULL OR T5 NOT IN [Eligible tumour record type codes] Record rejected
Feedback report messages (TVAL5)
Sub–edit Text Type
TVAL5-1 Tumour record type code is missing or invalid. Core fatal error
Revision (TVAL5)
Year Description
Not applicable Not applicable

TVAL6

Purpose

This edit validates the name of place of residence.

Referenced fileds (TVAL6)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T6 25 Name of place of residence TPLACRES

Business rules

For Add and Update Tumour records
  • Name of place of residence can be blank.
  • If Name of place of residence is not blank then it can be any combination of the following:
    • Letters: A to Z (upper or lowercase)
      • Accented characters: Â À Ç É Ê Ë È Î Ï Ô Û Ü (upper or lowercase)
      • Special characters: space ( ), period (.), apostrophe ('), hyphen (-), exclamation mark (!), ampersand (&), forward slash (/), parenthese ["("and")"], number sign (#), comma (,)
  • It must contain a word of at least 2 letters.
Edit logic TVAL6)
Sub–edit Conditions Outcome
TVAL6-1 T5 IN [‘1', ‘2'] AND T6 IS NOT NULL AND IS NOT COMPOSED OF (UPPER (T6), ‘ABCDEFGHILKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ.'-!&/()#,') Record rejected
TVAL6-2 T5 IN [‘1', ‘2'] AND T6 IS NOT NULL AND IS_COMPOSED_OF (UPPER (T6), ‘ABCDEFGHILKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ .'-!&/()#,') AND NOT CONTAINS_WORD (UPPER (T6), ‘ABCDEFGHILKLMNOPQRSTUVWXYZÂÀÇÉÊËÈÎÏÔÛÜ', 2) Record rejected
Feedback report messages (TVAL6)
Sub–edit Text Type
TVAL6-1 Name of place of residence is not exclusively composed of acceptable letters, accented characters or special characters. Core error
TVAL6-2 Name of place of residence does not contain a word of at least 2 letters. Core error
Revision (TVAL6)
Year Description
2007 Business rules changed: Acceptable accented characters and special characters are specified.
Edit logic: New edit logic added.
Feedback report messages: New message added.

TVAL7

Purpose

This edit validates the postal code.

Referenced fields (TVAL7)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T7 6 Postal code TPOSTCOD
T7.FIRST 1 1st character of T7 Not applicable
T7.SECOND 1 2nd character of T7 Not applicable
T7.THIRD 1 3rd character of T7 Not applicable
T7.FOURTH 1 4th character of T7 Not applicable
T7.FIFTH 1 5th character of T7 Not applicable
T7.SIXTH 1 6th character of T7 Not applicable

Business rules

For Add and Update Tumour records, Postal code
  • Must be 6 characters long.
  • Can be unknown.
  • If not unknown then
    • 1st, 3rd and 5th characters must be uppercase letters: A-Z
    • 2nd, 4th and 6th characters must be numbers: 0-9
Edit logic (TVAL7)
Sub–edit Conditions Outcome
TVAL7-1 T5 IN [‘1', ‘2'] AND (LENGTH(T7) <> 6 OR (T7 <> ‘999999' AND (T7.FIRST NOT IN [A-Z] OR T7.SECOND NOT IN [0-9] OR T7.THIRD NOT IN [A-Z] OR T7.FOURTH NOT IN [0-9] OR T7.FIFTH NOT IN [A-Z] OR T7.SIXTH NOT IN [0-9]))) Record rejected
Feedback report messages (TVAL7)
Sub–edit Text Type
TVAL7-1 Postal code has an invalid format. Core error
Revision (TVAL7)
Year Description
Not applicable Not applicable

TVAL8

Purpose

This edit validates the Standard geographic code.

Referenced fields (TVAL8)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T8 7 Standard geographic code TCODPLAC
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable

Business rules

For Add and Update Tumour records
  • If Date of diagnosis is between 1992 and 1995 then Standard geographic code must be one of the Eligible Standard geographic classification codes from 1992 to 199512.
  • If Date of diagnosis is between 1996 and 2000 then Standard geographic code must be one of the Eligible Standard geographic classification codes from 1996 to 200012.
  • If Date of diagnosis is between 2001 and 2005 then Standard geographic code must be one of the Eligible Standard geographic classification codes from 2001 to 200512.
  • If Date of Diagnosis is between 2006 and 2010 then Standard geographic code must be one of the Eligible Standard geographic classification codes from 2006 and 2010.
Edit logic (TVAL8)
Sub–edit Conditions Outcome
TVAL8-1 T5 IN [‘1', ‘2'] AND T12.YEAR BETWEEN (‘1992', ‘1995') AND T8 NOT IN [Eligible Standard geographic classification codes from 1992 to 1995] Record rejected
TVAL8-2 T5 IN [‘1', ‘2'] AND T12.YEAR BETWEEN (‘1996', ‘2000') AND T8 NOT IN [Eligible Standard geographic classification codes from 1996 to 2000] Record rejected
TVAL8-3 T5 IN [‘1', ‘2'] AND T12.YEAR BETWEEN (‘2001', ‘2005') AND T8 NOT IN [Eligible Standard geographic classification codes from 2001 to 2005] Record rejected
TVAL8-4 T5 IN [‘1', ‘2'] AND T12.YEAR BETWEEN (‘2006', ‘2010') AND T8 NOT IN [Eligible Standard Geographic Classification codes from 2006 to 2010] Record rejected
Feedback report messages (TVAL8)
Sub–edit Text Type
TVAL8-1 Standard geographic code is invalid according to the Standard geographic classification – 1991. Core error
TVAL8-2 Standard geographic code is invalid according to the Standard geographic classification – 1996. Core error
TVAL8-3 Standard geographic code is invalid according to the Standard geographic classification – 2001. Core error
TVAL8-4 Standard geographic code is invalid according to the Standard geographic classification – 2006. Core error
Revision (TVAL8)
Year Description
2006 Business rules, Edit logic and Feedback report messages added: SGC – 2006 added
2001 Business rules, Edit logic and Feedback report messages added: SGC – 2001 added
1996 Business rules, Edit logic and Feedback report messages added: SGC – 1996 added

TVAL9

Purpose

This edit validates the census tract.

Referenced fields (TVAL9)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T9 9 Census tract TCENTRAC
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable

Business rules

For Add and Update Tumour records
  • If Date of diagnosis is between 1992 and 1995 then Census tract must be reported and must be one of the Eligible Census tracts from 1992 to 199512.
  • If Date of diagnosis is between 1996 and 2000 then Census tract must be reported and must be one of the Eligible Census tracts from 1996 to 200012.
  • If Date of diagnosis is between 2001 and 2005 then Census tract must be reported and must be one of the Eligible Census tracts from 2001 to 200512
  • If Date of Diagnosis is 2006 and onwards then Census Tract must not be reported (field should be left blank).
Edit logic (TVAL9)
Sub–edit Conditions Outcome
TVAL9-1 T5 IN [‘1', ‘2'] AND T12.YEAR BETWEEN (‘1992', ‘1995') AND (T9 IS NULL OR T9 NOT IN [Eligible Census tracts from 1992 to 1995]) Record rejected
TVAL9-2 T5 IN [‘1', ‘2'] AND T12.YEAR BETWEEN (‘1996', ‘2000') AND (T9 IS NULL OR T9 NOT IN [Eligible Census tracts from 1996 to 2000]) Record rejected
TVAL9-3 T5 IN [‘1', ‘2'] AND T12.YEAR BETWEEN (‘2001', ‘2005') AND (T9 IS NULL OR T9 NOT IN [Eligible Census tracts from 2001 to 2005]) Record rejected
TVAL9-4 T5 IN [‘1', ‘2'] AND T12.YEAR >= (‘2006') AND T9 <> NULL Record rejected
Feedback report messages (TVAL9)
Sub–edit Text Type
TVAL9-1 Census tract is invalid according to the Census tract Data Dictionary – 1991. Core error
TVAL9-2 Census tract is invalid according to the Census tract Data Dictionary – 1996. Core error
TVAL9-3 Census tract is invalid according to the Census tract Data Dictionary – 2001. Core error
TVAL9-4 Census tract must not be reported for cases diagnosed in 2006 and onwards. Core error
Revision (TVAL9)
Year Description
2006 Business rules, Edit logic and Feedback report messages added: Census tract effective date range ended in 2005. For cases diagnosed in 2006 and onwards, T9 (Census Tract) must be reported as blank (null)
2001 Business rules, Edit logic and Feedback report messages added: Eligible Census tracts – 2001 added
1996 Business rules, Edit logic and Feedback report messages added: Eligible Census tracts – 1996 added

TVAL10

Purpose

This edit validates the health insurance number (HIN).

Referenced fields (TVAL10)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T10 15 Health insurance number THIN

Business rules

For Add and Update Tumour records,
  • If Health insurance number is reported then
  • It must be at least 6 characters long.
  • It must be exclusively composed of any of the following:
    • Uppercase letters: A to Z
    • Numbers: 0 to 9
Edit logic (TVAL10)
Sub–edit Conditions Outcome
TVAL10-1 T5 IN [‘1', ‘2'] AND T10 IS NOT NULL AND LENGTH (T10) < 6 Record rejected
TVAL10-2 T5 IN [‘1', ‘2'] AND T10 IS NOT NULL AND NOT IS_COMPOSED_OF (T10, ‘ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789') Record rejected
Feddback report messages (TVAL10)
Sub–edit Text Type
TVAL10-1 Health insurance number is less than 6 characters long. Core error
TVAL10-2 Health insurance number is not exclusively composed of uppercase letters and/or numbers. Core error
Revision (TVAL10)
Year Description
Not applicable Not applicable

TVAL11

Purpose

This edit validates the method of diagnosis code.

Referenced fields (TVAL11)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T11 1 Method of diagnosis TMETHDIAG

Business rules

For Add and Update Tumour records
  • Method of diagnosis must be one of the Eligible method of diagnosis codes18.
Edit logic (TVAL11)
Sub–edit Conditions Outcome
TVAL11-1 T5 IN [‘1', ‘2'] AND T11 NOT IN [Eligible method of diagnosis codes] Record rejected
Feedback report messages (TVAL11)
Sub–edit Text Type
TVAL11-1 Method of diagnosis code is invalid. Core error
Revision (TVAL11)
Year Description
Not applicable Not applicable

TVAL12

Purpose

This edit validates the date of diagnosis.

Referenced fields (TVAL12)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12 8 Date of diagnosis TDATDIAG
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T12.MONTH 2 5th and 6th digits of T12 (month of date of diagnosis) Not applicable
T12.DAY 2 Last 2 digits of T12 (day of date of diagnosis) Not applicable
Other parameters (TVAL12)
Parameters Length Description
CYCLE_YEAR 4 Reference year

Business rules

For Add and Update Tumour records, Date of Diagnosis
  • Must be exclusively composed of numbers: 0 to 9.
  • Must be 8 digits long.
  • Must be between January 1st, 1992 and December 31st of Reference year inclusively.
  • Year cannot be unknown.
  • If Month is unknown then Day must be unknown.
  • If Year, Month and Day are known then it must be a valid calendar date.
  • If Year and Month are known and Day is unknown then Month must be a valid month.
Edit logic (TVAL12)
Sub–edit Conditions Outcome
TVAL12-1 T5 IN [‘1', ‘2'] AND (LENGTH (T12) <> 8 OR NOT IS_COMPOSED_OF (T12, ‘0123456789')) Record rejected
TVAL12-2 T5 IN [‘1', ‘2'] AND LENGTH (T12) = 8 AND IS_COMPOSED_OF (T12, ‘0123456789') AND T12.MONTH = ‘99' AND T12.DAY <> ‘99' Record rejected
TVAL12-3 T5 IN [‘1', ‘2'] AND LENGTH (T12) = 8 AND IS_COMPOSED_OF (T12, ‘0123456789'' AND (T12.YEAR < 1992 OR T12.YEAR > CYCLE_YEAR) Record rejected
TVAL12-4 T5 IN [‘1', ‘2'] AND LENGTH (T12) = 8 AND IS_COMPOSED_OF (T12, ‘0123456789') AND T12.MONTH <> ‘99' AND T12.DAY <> ‘99' AND NOT IS_VALID_DATE (T12) Record rejected
TVAL12-5 T5 IN [‘1', ‘2'] AND LENGTH (T12) = 8 AND IS_COMPOSED_OF (T12, ‘0123456789') AND T12.MONTH NOT IN [‘01'-'12', ‘99'] AND T12.DAY = ‘99' Record rejected
Feedback report messages (TVAL12)
Sub–edit Text Type
TVAL12-1 Date of diagnosis is not composed of 8 numbers. Core error
TVAL12-2 Date of diagnosis: Improper use of ‘Unknown' code. Core error
TVAL12-3 Date of diagnosis must be between January 1st, 1992 and December 31st of Reference year inclusively. Core error
TVAL12-4 Date of diagnosis is not a valid calendar date. Core error
TVAL12-5 Date of diagnosis is not a valid partial date: month is invalid. Core error
Revision (TVAL12)
Year Description
Not applicable Not applicable

TVAL13

Purpose

This edit validates the ICD-9 cancer code.

Referenced fields (TVAL13)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T13 4 ICD-9 cancer code TICD_9

Business rules

For Add and Update Tumour records
  • If ICD-9 Cancer code is reported then it must be one of the Eligible ICD-9 Cancer codes19.
Edit logic (TVAL13)
Sub–edit Conditions Outcome
TVAL13-1 T5 IN [‘1', ‘2'] AND T13 <> ‘0000' AND T13 NOT IN [Eligible ICD-9 Cancer codes] Record rejected
Feedback report messages (TVAL13)
Sub–edit Text Type
TVAL13-1 ICD-9 Cancer code is either invalid or not eligible for the CCR system. Core error
Revision (TVAL13)
Year Description
Not applicable Not applicable

TVAL14

Purpose

This edit validates the source classification flag.

Referenced fields (TVAL14)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T14 1 Source classification flag TSCF

Business rules

For Add and Update Tumour records
  • Source classification flag must be one of the Eligible source classification flags20.
Edit logic (TVAL14)
Sub–edit Conditions Outcome
TVAL14-1 T5 IN [‘1', ‘2'] AND T14 NOT IN [Eligible source classification flags] Record rejected
Feedback report messages (TVAL14)
Sub–edit Text Type
TVAL14-1 Source classification flag is invalid. Core error
Revision (TVAL14)
Year Description
Not applicable Not applicable

TVAL15

Purpose

This edit validates the ICD-O-2/3 topography code.

Referenced fields (TVAL15)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T15 4 ICD-O-2/3 Topography TICD_O2T

Business rules

For Add and Update Tumour records
  • ICD-O-2/3 Topography must be one of the Eligible ICD-O-2/3 Topography codes12.
Edit logic (TVAL15)
Sub–edit Conditions Outcome
TVAL15-1 T5 IN [‘1', ‘2'] AND T15 NOT IN [Eligible ICD-O-2/3 Topography codes] Record rejected
Feedback report messages (TVAL15)
Sub–edit Text Type
TVAL15-1 ICD-O-2/3 Topography code is either invalid or not eligible for the CCR System. Core error
Revision (TVAL15)
Year Description
Not applicable Not applicable

TVAL16

Purpose

This edit validates the ICD-O-2 histology code.

Referenced fields (TVAL16)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T15 4 ICD-O-2/3 Topography TICD_O2T
T16 4 ICD-O-2 Histology TICD_O2H

Business rules

For Add and Update Tumour records
  • If ICD-O-2 Histology is reported then it must be one of the Eligible ICD–O–2 Histology codes12.
Edit logic (TVAL16)
Sub–edit Conditions Outcome
TVAL16-1 T5 IN [‘1', ‘2'] AND T15 <> ‘0000' AND T16 NOT IN [Eligible ICD-O-2 Histology codes] Record rejected
Feedback report messages (TVAL16)
Sub–edit Text Type
TVAL16-1 ICD-O-2 Histology code is either invalid or not eligible for the CCR System. Core error
Revision (TVAL16)
Year Description
Not applicable Not applicable

TVAL17

Purpose

This edit validates the ICD-O-2 Behaviour code.

Referenced fields (TVAL17)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T17 1 ICD-O-2 Behaviour TICD_O2B

Business rules

For Add and Update Tumour records
  • If ICD-O-2 Behaviour is reported then it must be one of the Eligible ICD–O–2 Behaviour codes21.
Edit logic (TVAL17)
Sub–edit Conditions Outcome
TVAL17-1 T5 IN [‘1', ‘2'] AND T17 NOT IN [Eligible ICD–O–;2 Behaviour codes] Record rejected
Feedback report messages (TVAL17)
Sub–edit Text Type
TVAL17-1 ICD-O-2 Behaviour code is either invalid or not eligible for the CCR system. Core error
Revision (TVAL17)
Year Description
Not applicable Not applicable

TVAL18

Purpose

Not applicable

Referenced fields (TVAL18)
Field Length Description Acronym
T18 4 Filler Not applicable

Business rules

For Input Tumour records
  • Filler can be anything, including blank.
Edit logic (TVAL18)
Sub–edit Conditions Outcome
Not applicable Not applicable Not applicable
Feedback report messages (TVAL18)
Sub–edit Text Type
Not applicable Not applicable Not applicable
Revision (TVAL18)
Year Description
2004 Edit removed: Filler can be anything, including blank.

Note
This empty validation is kept as a placeholder for future requirement implementation.

TVAL19

Purpose

This edit validates the laterality code.

Referenced fields (TVAL19)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T19 1 Laterality TLATERAL

Business rules

For Add and Update Tumour records
  • Laterality must be one of the Eligible laterality codes22.
Edit logic (TVAL19)
Sub–edit Conditions Outcome
TVAL19-1 T5 IN [‘1', ‘2'] AND T19 NOT IN [Eligible laterality codes] Record rejected
Feedback report messages (TVAL19)
Sub–edit Text Type
TVAL19-1 Laterality code is invalid. Core error
Revision (TVAL19)
Year Description
Not applicable Not applicable

TVAL20

Purpose

Not applicable

Referenced fields (TVAL20)
Field Length Description Acronym
T20 1 Filler Not applicable

Business rules

For Input Tumour records
  • Filler can be anything, including blank.
Edit logic TVAL20)
Sub–edit Conditions Outcome
Not applicable Not applicable Not applicable
Feedback report messages (TVAL20)
Sub–edit Text Type
Not applicable Not applicable Not applicable
Revision (TVAL20)
Year Description
2004 Edit removed: Filler can be anything, including blank.

Note:
This empty validation is kept as a placeholder for future requirement implementation.

TVAL21

Purpose

This edit validates the ICD-O-3 Histology code.

Referenced fields (TVAL21)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T21 4 ICD-O-3 Histology TICD_O3H

Business rules

For Add and Update Tumour records
  • ICD-O-3 Histology must be one of the Eligible ICD–O–3 Histology codes12,23.
Edit logic (TVAL21)
Sub–edit Conditions Outcome
TVAL21-1 T5 IN [‘1', ‘2'] AND T21 NOT IN [Eligible ICD-O-3 Histology codes] Record rejected
Feedback report messages (TVAL21)
Sub–edit Text Type
TVAL21-1 ICD-O-3 Histology code is either invalid or not eligible for the CCR System. Core error
Revision (TVAL21)
Year Description
2004 Edit renamed: Current edit was formerly known as Validation edit No.21M.

TVAL22

Purpose

This edit validates the ICD-O-3 Behaviour code.

Referenced fields TVAL22)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T22 1 ICD-O-3 Behaviour TICD_O3B

Business rules

For Add and Update Tumour records
  • ICD-O-3 Behaviour must be one of the Eligible ICD–O–3 Behaviour codes24.
Edit logic (TVAL22)
Sub–edit Conditions Outcome
TVAL22-1 T5 IN [‘1', ‘2'] AND T22 NOT IN [Eligible ICD–O–3 Behaviour codes] Record rejected
Feedback report messages TVAL22)
Sub–edit Text Type
TVAL22-1 ICD-O-3 Behaviour code is either invalid or not eligible for the CCR system. Core error
Revision (TVAL22)
Year Description
2004 Edit reorganized: Edit formerly known as Validation edit No.22 moved to TVAL26.
Edit renamed: Current edit was formerly known as Validation edit No.21B.

TVAL23

Purpose

This edit validates the grade, differentiation or cell indicator code.

Referenced fields (TVAL23)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T23 1 Grade, differentiation or cell indicator TGRADE

Business rules

For Add and Update Tumour records
  • Grade, differentiation or cell indicator must be one of the Eligible grade, differentiation or cell indicator codes25.
Edit logic (TVAL23)
Sub–edit Conditions Outcome
TVAL23-1 T5 IN [‘1', ‘2'] AND T23 NOT IN [Eligible grade, differentiation or cell indicator codes] Record rejected
Feedback report messages (TVAL23)
Sub–edit Text Type
TVAL23-1 Grade, differentiation or cell indicator code is invalid. Core error
Revision (TVAL23)
Year Description
2004 Edit reorganized: Edit formerly known as Validation edit No.23 moved to TVAL24.
Edit added: New edit.

TVAL24

Purpose

This edit validates the method used to establish the date of diagnosis code.

Referenced fields (TVAL24)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T24 1 Method used to establish the date of diagnosis TMETHUSED

Business rules

For Add and Update Tumour records
  • Method used to establish the date of diagnosis must be one of the Eligible method used to establish the date of diagnosis codes26.
Edit logic (TVAL24)
Sub–edit Conditions Outcome
TVAL24-1 T5 IN [‘1', ‘2'] AND T24 NOT IN [Eligible method used to establish the date of diagnosis codes] Record rejected
Feedback report messages (TVAL24)
Sub–edit Text Type
TVAL24-1 Method used to establish the date of diagnosis code is invalid. Core error
Revision(TVAL24)
Year Description
2004 Edit reorganized: Edit formerly known as Validation edit No.24 moved to TVAL25.
Edit renamed: Current edit formerly known as Validation edit No.23.

TVAL25

Purpose

This edit validates the diagnostic confirmation code.

Referenced fields (TVAL25)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T25 1 Diagnostic Confirmation TMETHCONF

Business rules

For Add and Update Tumour records
  • Diagnostic confirmation must be one of the Eligible diagnostic confirmation codes27.
Edit logic (TVAL25)
Sub–edit Conditions Outcome
TVAL25-1 T5 IN [‘1', ‘2'] AND T25 NOT IN [Eligible diagnostic confirmation codes] Record rejected
Feedback report messages (TVAL25)
Sub–edit Text Type
TVAL25-1 Diagnostic confirmation code is invalid. Core error
Revision (TVAL25)
Year Description
2004 Edit renamed: Current edit formerly known as Validation edit No.24.

TVAL26

Purpose

This edit validates the tumour date of transmission.

Referenced fields (TVAL26)
Field Length Description Acronym
T26 8 Tumour date of transmission TDATTRAN
T26.YEAR 4 First 4 digits of T26 (year of date of transmission) Not applicable
T26.MONTH 2 5th and 6th digits of T26 (month of date of transmission) Not applicable
T26.DAY 2 7th and 8th digits of T26 (day of date of transmission) Not applicable
Other parameters (TVAL26)
Parameters Length Description
LOAD_DATE 8 Statistics Canada loading date: Date on the Statistics Canada computer clock when the data are loaded on the CCR database.

Business rules

For Input Tumour records, Tumour date of transmission
  • Cannot be blank.
  • Must be exclusively composed of numbers: 0 to 9.
  • Must be 8 digits long.
  • Must be a valid calendar date.
  • Must be within the previous 10 months from Statistics Canada loading date.
Edit logic (TVAL26)
Sub–edit Conditions Outcome
TVAL26-1 T26 IS NULL Record rejected
TVAL26-2 T26 IS NOT NULL AND (LENGTH (T26) <> 8 OR NOT IS_COMPOSED_OF (T26, ‘0123456789')) Record rejected
TVAL26-3 T26 IS NOT NULL AND LENGTH (T26) = 8 AND IS_COMPOSED_OF (T26, ‘0123456789') AND NOT IS_VALID_DATE (T26) Record rejected
TVAL26-4 T26 IS NOT NULL AND LENGTH (T26) = 8 AND IS_COMPOSED_OF (P26, ‘0123456789') AND IS_VALID_DATE (T26) AND T26 > LOAD_DATE Record rejected
TVAL26-5 T26 IS NOT NULL AND LENGTH (T26) = 8 AND IS_COMPOSED_OF (T26, ‘0123456789') AND IS_VALID_DATE (T26) AND T26 < (LOAD_DATE – 10 months) Record rejected
Feedback report messages (TVAL26)
Sub–edit Text Type
TVAL26-1 Tumour date of transmission is missing. Core fatal error
TVAL26-2 Tumour date of transmission is not 8 digits long. Core fatal error
TVAL26-3 Tumour date of transmission is not a valid calendar date. Core fatal error
TVAL26-4 Tumour date of transmission is after Statistics Canada loading date. Core fatal error
TVAL26-5 Tumour date of transmission is more than 10 months before Statistics Canada loading date. Core fatal error
Revision (TVAL26)
Year Description
2004 Edit renamed: Current edit formerly known as Validation edit No.22.

TVAL27

Purpose

This edit validates CS tumour size.

Referenced fields (TVAL27)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS tumour size must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL27)
Sub–edit Conditions Outcome
TVAL27-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <>'999999') AND NOT VALID_CS_TUMOUR_SIZE(T15, T21, T27) CS data items filled with 'R' at posting.
Feedback report messages (TVAL27)
Sub–edit Text Type
TVAL27-1 CS tumour size is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL27)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL28

Purpose

This edit validates CS extension.

Referenced fields (TVAL28)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD—O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR Collaborative staging scope28 and with at least one known CS variable,
  • CS extension must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL28)
Sub–edit Conditions Outcome
TVAL28-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> ‘999999') AND NOT VALID_CS_EXTENSION(T15, T21, T28) CS data items filled with 'R' at posting.
Feedback report messages (TVAL28)
Sub–edit Text Type
TVAL28-1 CS extension is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL28)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL29

Purpose

This edit validates CS tumour size/ext eval.

Referenced fields (TVAL29)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS tumour size/ext eval must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL29)
Sub–edit Conditions Outcome
TVAL29-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> ‘999999') AND NOT VALID _CS_TUMOUR_SIZE/EXT_EVAL(T15, T21, T29) CS data items filled with 'R' at posting.
Feedback report messages (TVAL29)
Sub–edit Text Type
TVAL29-1 CS tumour size/ext eval is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL29)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL30

Purpose

This edit validates CS lymph nodes.

Referenced fields (TVAL30)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS lymph nodes must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL30)
Sub–edit Conditions Outcome
TVAL30-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> ‘999999') AND NOT VALID CS_LYMPH_NODES(T15, T21, T30) CS data items filled with 'R' at posting.
Feedback report messages (TVAL30)
Sub–edit Text Type
TVAL30-1 CS lymph nodes is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL30)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL31

Purpose

This edit validates CS reg nodes eval.

Referenced fields (TVAL31)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS reg nodes eval must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL31)
Sub–edit Conditions Outcome
TVAL31-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> ‘999999') AND NOT VALID_CS_REG_NODES_EVAL(T15, T21, T31) CS data items filled with 'R' at posting.
Feedback report messages (TVAL31)
Sub–edit Text Type
TVAL31-1 CS reg nodes eval is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL31)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL32

Purpose

This edit validates regional nodes examined.

Referenced fields (TVAL32)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • Regional nodes examined must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL32)
Sub–edit Conditions Outcome
TVAL32-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> ‘999999') AND NOT VALID_REGIONAL_NODES_EXAMINED(T15, T21, T32) CS data items filled with 'R' at posting.
Feedback report messages (TVAL32)
Sub–edit Text Type
TVAL32-1 Regional nodes examined is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL32)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL33

Purpose

This edit validates regional nodes positive.

Referenced fields (TVAL33)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • Regional nodes positive must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL33)
Sub–edit Conditions Outcome
TVAL33-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> ‘999999') AND NOT VALID_REGIONAL_NODES_POSITIVE(T15, T21, T33) CS data items filled with 'R' at posting.
Feedback report messages TVAL33)
Sub–edit Text Type
TVAL33-1 Regional nodes positive is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL33)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL34

Purpose

This edit validates CS mets at dx.

Referenced fields (TVAL34)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS mets at dx must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL34)
Sub–edit Conditions Outcome
TVAL34-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38 <>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> ‘999999') AND NOT VALID_CS_METS_AT_DX(T15, T21, T34) CS data items filled with 'R' at posting.
Feedback report messages (TVAL34)
Sub–edit Text Type
TVAL34-1 CS mets at dx is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL34)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL35

Purpose

This edit validates CS mets eval.

Referenced fields (TVAL35)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS mets eval must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL35)
Sub–edit Conditions Outcome
TVAL35-1 T5 IN [‘1', ‘2']AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> ‘999999') AND NOT VALID_CS_METS_EVAL(T15, T21, T35) CS data items filled with 'R' at posting.
Feedback report messages (TVAL35)
Sub–edit Text Type
TVAL35-1 CS mets eval is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL35)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL36

Purpose

This edit validates CS site-specific factor 1.

Referenced fields (TVAL36)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS site-specific factor 1 must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL36)
Sub–edit Conditions Outcome
TVAL36-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> ‘999999') AND NOT VALID_CS_SITE-SPECIFIC_FACTOR_1(T15, T21, T36) CS data items filled with 'R' at posting.
Feedback report messages (TVAL36)
Sub–edit Text Type
TVAL36-1 CS site-specific factor 1 is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL36)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm.
2004 Edit added: New edit.

TVAL37

Purpose

This edit validates CS site-specific factor 2.

Referenced fields (TVAL37)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS site-specific factor 2 must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL37)
Sub–edit Conditions Outcome
TVAL37-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> ‘999999') AND NOT VALID_CS_SITE-SPECIFIC_FACTOR_2(T15, T21, T37) CS data items filled with 'R' at posting.
Feedback report messages (TVAL37)
Sub–edit Text Type
TVAL37-1 CS site-specific factor 2 is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL37)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm.
2004 Edit added: New edit.

TVAL38

Purpose

This edit validates CS site-specific factor 3.

Referenced fields (TVAL38)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS site-specific factor 3 must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL38)
Sub–edit Conditions Outcome
TVAL38-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> ‘999999') AND NOT VALID_CS_SITE-SPECIFIC_FACTOR_3(T15, T21, T38) CS data items filled with 'R' at posting.
Feedback report messages (TVAL38)
Sub–edit Text Type
TVAL38-1 CS site-specific factor 3 is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL38)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm.
2004 Edit added: New edit.

TVAL39

Purpose

This edit validates CS site-specific factor 4.

Referenced fields (TVAL39)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS site-specific factor 4 must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL39)
Sub–edit Conditions Outcome
TVAL39-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> ‘999999') AND NOT VALID_CS_SITE-SPECIFIC_FACTOR_4(T15, T21, T39) CS data items filled with 'R' at posting.
Feedback report messages (TVAL39)
Sub–edit Text Type
TVAL39-1 CS site-specific factor 4 is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL39)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm.
2004 Edit added: New edit.

TVAL40

Purpose

This edit validates CS site-specific factor 5.

Referenced fields (TVAL40)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28and with at least one known CS variable
  • CS site-specific factor 5 must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL40)
Sub–edit Conditions Outcome
TVAL40-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> ‘999999') AND NOT VALID_CS_SITE-SPECIFIC_FACTOR_5(T15, T21, T40) CS data items filled with 'R' at posting.
Feedback report messages (TVAL40)
Sub–edit Text Type
TVAL40-1 CS site-specific factor 5 is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL40)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL41

Purpose

This edit validates CS site-specific factor 6.

Referenced fields (TVAL41)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD–O–2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope28 and with at least one known CS variable
  • CS site-specific factor 6 must be valid according to the recommended version of the AJCC CS Algorithm with respect to the CS schema (derived from ICD-O-2/3 Topography and ICD-O-3 Histology).
Edit logic (TVAL41)
Sub–edit Conditions Outcome
TVAL41-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2004' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' OR T52 <> ‘999999') AND NOT VALID_CS_SITE-SPECIFIC_FACTOR_6(T15, T21, T41) CS data items filled with 'R' at posting.
Feedback report messages (TVAL41)
Sub–edit Text Type
TVAL41-1 CS site-specific factor 6 is invalid for the corresponding CS Schema, based on the recommended version of the AJCC CS Algorithm. CS error
Revision (TVAL41)
Year Description
2007 Referenced fields, Business Rules, Edit logic and Feedback report messages updated: Validation is now done using the recommended version of the AJCC CS algorithm
2004 Edit added: New edit.

TVAL42

Purpose

This edit validates AJCC clinical T

Referenced fields (TVAL42)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T42 9 AJCC clinical T TAJCCCLINT

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • AJCC clinical T must be one of the Eligible AJCC clinical T values for the corresponding site30.

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Edit logic (TVAL42)
Sub–edit Conditions Outcome
TVAL42-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T42 NOT IN [Eligible AJCC clinical T for Site X] AJCC TNM data items filled with 'R' at posting.
Feedback report messages (TVAL42)
Sub–edit Text Type
TVAL42-1 AJCC clinical T is invalid for reported site. AJCC TNM error
Revision (TVAL42)
Year Description
2004 Edit added: New edit.

TVAL43

Purpose

This edit validates AJCC clinical N.

Referenced fields (TVAL43)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T43 3 AJCC clinical N TAJCCCLINN

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • AJCC clinical N must be one of the Eligible AJCC clinical N values for the corresponding site31.

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example : Colorectal, breast or prostate.

Edit logic (TVAL43)
Sub–edit Conditions Outcome
TVAL43-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T43 NOT IN [Eligible AJCC clinical N for Site X] AJCC TNM data items filled with 'R' at posting.
Feedback report messages (TVAL43)
Sub–edit Text Type
TVAL43-1 AJCC clinical N is invalid for reported site. AJCC TNM error
Revision (TVAL43)
Year Description
2004 Edit added: New edit.

TVAL44

Purpose

This edit validates AJCC clinical M.

Referenced fields (TVAL44)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T44 3 AJCC clinical M TAJCCCLINM

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • AJCC clinical M must be one of the Eligible AJCC clinical M values for the corresponding site32.

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Ex: Colorectal, breast or prostate.

Edit logic (TVAL44)
Sub–edit Conditions Outcome
TVAL44-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T44 NOT IN [Eligible AJCC clinical M for Site X] AJCC TNM data items filled with 'R' at posting.
Feedback report messages (TVAL44)
Sub–edit Text Type
TVAL44-1 AJCC clinical M is invalid for reported site. AJCC TNM error
Revision (TVAL44)
Year Description
2004 Edit added: New edit.

TVAL45

Purpose

This edit validates AJCC pathologic T.

Referenced fields (TVAL45)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T45 9 AJCC pathologic T TAJCCPATHT

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • AJCC pathologic T must be one of the Eligible AJCC pathologic T values for the corresponding site33.

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Edit logic (TVAL45)
Sub–edit Conditions Outcome
TVAL45-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T45 NOT IN [Eligible AJCC pathologic T for Site X] AJCC TNM data items filled with 'R' at posting.
Feedback report messages (TVAL45)
Sub–edit Text Type
TVAL45-1 AJCC pathologic T is invalid for reported site. AJCC TNM error
Revision (TVAL45)
Year Description
2004 Edit added: New edit.

TVAL46

Purpose

This edit validates AJCC pathologic N.

Referenced fields (TVAL46)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T46 3 AJCC pathologic N TAJCCPATHN

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • AJCC pathologic N must be one of the Eligible AJCC pathologic N values for the corresponding site34.

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Edit logic (TVAL46)
Sub–edit Conditions Outcome
TVAL46-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T46 NOT IN [Eligible AJCC pathologic N for Site X] AJCC TNM data items filled with 'R' at posting.
Feedback report messages (TVAL46)
Sub–edit Text Type
TVAL46-1 AJCC pathologic N is invalid for reported site. AJCC TNM error
Revision (TVAL46)
Year Description
2004 Edit added: New edit.

TVAL47

Purpose

This edit validates AJCC pathologic M.

Referenced fields (TVAL47)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T47 3 AJCC pathologic M TAJCCPATHM

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • AJCC pathologic M must be one of the Eligible pathologic M values for the corresponding site35.

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Edit logic (TVAL47)
Sub–edit Conditions Outcome
TVAL47-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T47 NOT IN [Eligible AJCC pathologic M for Site X] AJCC TNM data items filled with 'R' at posting.
Feedback report messages (TVAL47)
Sub–edit Text Type
TVAL47-1 AJCC pathologic M is invalid for reported site. AJCC TNM error
Revision (TVAL47)
Year Description
2004 Edit added: New edit.

TVAL48

Purpose

This edit validates AJCC clinical TNM stage group.

Referenced fields (TVAL48)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T48 4 AJCC clinical TNM stage group TAJCCCLINSG

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • AJCC clinical TNM stage group must be one of the Eligible AJCC clinical TNM stage group values for the corresponding site38.

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Edit logic (TVAL48)
Sub–edit Conditions Outcome
TVAL48-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T48 NOT IN [Eligible AJCC clinical TNM stage group for Site X] AJCC TNM data items filled with 'R' at posting.
Feedback report messages (TVAL48)
Sub–edit Text Type
TVAL48-1 AJCC clinical TNM stage group is invalid for reported site. AJCC TNM error
Revision (TVAL48)
Year Description
2004 Edit added: New edit.

TVAL49

Purpose

This edit validates AJCC pathologic TNM stage group.

Referenced fields (TVAL49)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T49 4 AJCC pathologic TNM stage group TAJCCPATHSG

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • AJCC pathologic TNM stage group must be one of the Eligible AJCC pathologic TNM stage group values for the corresponding site37.

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast orprostate.

Edit logic (TVAL49)
Sub–edit Conditions Outcome
TVAL49-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T49 NOT IN [Eligible AJCC pathologic TNM stage group for Site X] AJCC TNM data items filled with 'R' at posting.
Feedback report messages (TVAL49)
Sub–edit Text Type
TVAL49-1 AJCC pathologic TNM stage group is invalid for reported site. AJCC TNM error
Revision (TVAL49)
Year Description
2004 Edit added: New edit.

TVAL50

Purpose

This edit validates AJCC TNM stage group.

Referenced fields (TVAL50)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T50 4 AJCC TNM stage group TAJCCSG

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • AJCC TNM stage group must be one of the Eligible AJCC TNM stage group values for the corresponding site37.

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Edit logic (TVAL50)
Sub–edit Conditions Outcome
TVAL50-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T50 NOT IN [Eligible AJCC TNM stage group for Site X] AJCC TNM data items filled with 'R' at posting.
Feedback report messages (TVAL50)
Sub–edit Text Type
TVAL50-1 AJCC TNM stage group is invalid for reported site. AJCC TNM error
Revision (TVAL50)
Year Description
2004 Edit added: New edit.

TVAL51

Purpose

This edit validates AJCC edition number code.

Referenced fields (TVAL51)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T51 2 AJCC edition number TAJCCEDNUM

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • AJCC edition number must be one of the Eligible AJCC edition number codes38.

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Edit logic (TVAL51)
Sub–edit Conditions Outcome
TVAL51-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T51 NOT IN [Eligible AJCC edition number codes] AJCC TNM data items filled with 'R' at posting.
Feedback report messages (TVAL51)
Sub–edit Text Type
TVAL51-1 AJCC edition number code is either invalid or not eligible for the CCR system. AJCC TNM error
Revision (TVAL51)
Year Description
2004 Edit added: New edit.

TVAL52

Purpose

This edit validates CS Version 1st.

Referenced fields (TVAL52)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records within the CCR collaborative staging scope and with at least one known CS variable
  • CS version 1st must be one of the Eligible CS Version 1st codes.
Edit logic (TVAL52)
Sub–edit Conditions Outcome
TVAL52-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= ‘2006' AND (T27<>'999' OR T28<>'99' OR T29<>'9' OR T30<>'99' OR T31<>'9' OR T32<>'99' OR T33<>'99' OR T34<>'99' OR T35<>'9' OR T36<>'999' OR T37<>'999' OR T38<>'999' OR T39<>'999' OR T40<>'999' OR T41<>'999' or T52 <> ‘999999') AND T52 NOT IN [Eligible CS Version 1st codes] CS data items filled with 'R' at posting.
Feedback report messages (TVAL52)
Sub–edit Text Type
TVAL52-1 CS Version 1st is not a valid version number CS error
Revision (TVAL52)
Year Description
2007 Edit added: New edit.

TVAL53

Purpose

This edit validates the Ambiguous terminology diagnosis code.

Referenced fields (TVAL53)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T53 1 Ambiguous Terminology Diagnosis TAMBIGTERM

Business rules

For Add and Update Tumour records
  • Ambiguous terminology diagnosis must be one of the Eligible Ambiguous terminology diagnosis codes.
Edit logic (TVAL53)
Sub–edit Conditions Outcome
TVAL53-1 T5 IN [‘1', ‘2'] AND T53 IS NOT NULL AND NOT IN [Eligible Ambiguous terminology diagnosis codes] Record rejected
Feedback report messages (TVAL53)
Sub–edit Text Type
TVAL53-1 Ambiguous terminology diagnosis code is invalid. Core error
Revision (TVAL53)
Year Description
2008 Edit added: New edit.

TVAL54

Purpose

This edit validates the Date of conclusive diagnosis.

Referenced fields (TVAL54)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T54 8 Date of conclusive diagnosis TDATCONCLUSDIAG
T54.YEAR 4 First 4 digits of T54 (year of date of conclusive diagnosis) Not applicable
T54.MONTH 2 5th and 6th digits of T54 (month of date of conclusive diagnosis) Not applicable
T54.DAY 2 Last 2 digits of T56 (day of date of conclusive diagnosis) Not applicable

Business rules

For Add and Update Tumour records, Date of conclusive diagnosis
  • Must be exclusively composed of numbers: 0 to 9.
  • Must be 8 digits long.
  • If Year or Month or Day is accessioned then the Date of conclusive diagnosis must be accessioned.
  • If Year or Month or Day is not applicable then the Date of conclusive diagnosis must be not applicable.
  • If Year is unknown then Month and Day must be unknown.
  • If Month is unknown then Day must be unknown.
  • If Year and Month are known and Day is unknown then Month must be a valid month.
  • If Year, Month and Day are known then it must be a valid calendar date.
  • Must be between January 1st, 2008 and December 31st of Reference year inclusively.
Edit logic (TVAL54)
Sub–edit Conditions Outcome
TVAL54-1 T5 IN [‘1', ‘2'] AND LENGTH (T54) <> 8 OR NOT IS_COMPOSED_OF (T54, ‘0123456789') Record Rejected
TVAL54-2 T5 IN [‘1', ‘2'] AND LENGTH (T54) = 8 AND IS_COMPOSED_OF (T54, ‘0123456789') AND (T54.YEAR = ‘0000' OR T54.MONTH='00' OR T54.DAY='00') AND (T54.YEAR <> ‘0000' OR T54.MONTH <> ‘00' OR T54.DAY <> ‘00') Record Rejected
TVAL54-3 T5 IN [‘1', ‘2'] AND LENGTH (T54) = 8 AND IS_COMPOSED_OF (T54, ‘0123456789') AND (T54.YEAR = ‘8888' OR T54.MONTH='88' OR T54.DAY='88') AND (T54.YEAR <> ‘8888' OR T54.MONTH <> ‘88' OR T54.DAY <> ‘88') Record Rejected
TVAL54-4 T5 IN [‘1', ‘2'] AND LENGTH (T54) = 8 AND IS_COMPOSED_OF (T54, ‘0123456789') AND T54.YEAR = ‘9999' AND (T54.MONTH <> ‘99' OR T54.DAY <> ‘99') Record Rejected
TVAL54-5 T5 IN [‘1', ‘2'] AND LENGTH (T54) = 8 AND IS_COMPOSED_OF (T54, ‘0123456789') AND T54.MONTH = ‘99' AND T54.DAY <> ‘99' Record Rejected
TVAL54-6 T5 IN [‘1', ‘2'] AND LENGTH (T54) = 8 AND IS_COMPOSED_OF (T54, ‘0123456789') AND T54.MONTH NOT IN [‘01'-'12', ‘99'] AND T54.DAY = ‘99' Record Rejected
TVAL54-7 T5 IN [‘1', ‘2'] AND LENGTH (T54) = 8 AND IS_COMPOSED_OF (T54, ‘0123456789') AND T54 NOT IN [‘00000000', ‘88888888', ‘99999999'] AND T54.MONTH <> ‘99' AND T54.DAY <> ‘99' AND NOT IS_VALID_DATE Record Rejected
TVAL54-8 T5 IN [‘1', ‘2'] AND T54 NOT IN [‘00000000', ‘88888888', ‘99999999'] AND (T54.YEAR < 2008 OR T54.YEAR > CYCLE_YEAR) Record Rejected
Feedback report messages (TVAL54)
Sub–edit Text Type
TVAL54-1 Date of conclusive diagnosis is not composed of 8 numbers. Core Error
TVAL54-2 Year, month and day must be ‘accessioned'. Core Error
TVAL54-3 Year, month and day must be ‘not applicable'. Core Error
TVAL54-4 Year, month and day must be ‘unknown'. Core Error
TVAL54-5 Date of conclusive diagnosis: month and day must be ‘unknown'. Core Error
TVAL54-6 Date of conclusive diagnosis is not a valid partial date: month is invalid. Core Error
TVAL54-7 Date of conclusive diagnosis is not a valid calendar date. Core Error
TVAL54-8 Date of conclusive diagnosis is out of scope. Core Error
Revision (TVAL54)
Year Description
2008 Edit added: New edit.

TVAL55

Purpose

This edit validates the Type of multiple tumours reported as one primary code.

Referenced fields (TVAL55)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T55 2 Type of multiple tumours reported as one primary TMULTTUMONEPRIM

Business rules

For Add and Update Tumour records, Type of multiple tumours reported as one primary code
  • Must contain a valid code.
Edit logic (TVAL55)
Sub–edit Conditions Outcome
TVAL55-1 T5 IN [‘1', ‘2'] AND T55 IS NOT NULL AND T55 NOT IN [Eligible Type of multiple tumours reported as one primary codes] Record rejected
Feedback report messages (TVAL55)
Sub–edit Text Type
TVAL55-1 Type of multiple tumours reported as one primary code is invalid. Core error
Revision (TVAL55)
Year Description
2008 Edit added: New edit.

TVAL56

Purpose

This edit validates the Date of multiple tumours.

Referenced fields (TVAL56)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T56 8 Date of multiple tumours TDATMULT
T56.YEAR 4 First 4 digits of T56 (year of date of multiple tumours) Not applicable
T56.MONTH 2 5th and 6th digits of T56 (month of date of multiple tumours) Not applicable
T56.DAY 2 Last 2 digits of T56 (day of date of multiple tumours) Not applicable

Business rules

For Add and Update Tumour records, Date of multiple tumours
  • Must be exclusively composed of numbers: 0 to 9.
  • Must be 8 digits long.
  • If Year or Month or Day relates to a single tumour then the Date of multiple tumours must contain all zeros.
  • If Year or Month or Day is not applicable then the Date of multiple tumours must be not applicable.
  • If Year is unknown then Month and Day must be unknown.
  • If Month is unknown then Day must be unknown.
  • If Year and Month are known and Day is unknown then Month must be a valid month.
  • If Year, Month and Day are known then it must be a valid calendar date.
  • Must be between January 1st, 2008 and December 31st of Reference year inclusively.
Edit logic (TVAL56)
Sub–edit Conditions Outcome
TVAL56-1 T5 IN [‘1', ‘2'] AND LENGTH (T56) <> 8 OR NOT IS_COMPOSED_OF (T56, ‘0123456789') Record Rejected
TVAL56-2 T5 IN [‘1', ‘2'] AND LENGTH (T56) = 8 AND IS_COMPOSED_OF (T56, ‘0123456789') AND (T56.YEAR = ‘0000' OR T56.MONTH = ‘00' OR T56.DAY = ‘00') AND (T56.YEAR <> ‘0000' OR T56.MONTH <> ‘00' OR T56.DAY <> ‘00') Record Rejected
TVAL56-3 T5 IN [‘1', ‘2'] AND LENGTH (T56) = 8 AND IS_COMPOSED_OF (T56, ‘0123456789') AND (T56.YEAR = ‘8888' OR T56.MONTH = ‘88' OR T56.DAY = ‘88') AND (T56.YEAR <> ‘8888' OR T56.MONTH <> ‘88' OR T56.DAY <> ‘88') Record Rejected
TVAL56-4 T5 IN [‘1', ‘2'] AND LENGTH (T56) = 8 AND IS_COMPOSED_OF (T56, ‘0123456789') AND T56.YEAR = ‘9999' AND (T56.MONTH <> ‘99' OR T56.DAY <> ‘99') Record Rejected
TVAL56-5 T5 IN [‘1', ‘2'] AND LENGTH (T56) = 8 AND IS_COMPOSED_OF (T56, ‘0123456789') AND T56.MONTH = ‘99' AND T56.DAY <> ‘99' Record Rejected
TVAL56-6 T5 IN [‘1', ‘2'] AND LENGTH (T56) = 8 AND IS_COMPOSED_OF (T56, ‘0123456789') AND T56.MONTH NOT IN [‘01'-'12', ‘99'] AND T56.DAY = ‘99' Record Rejected
TVAL56-7 T5 IN [‘1', ‘2'] AND LENGTH (T56) = 8 AND IS_COMPOSED_OF (T56, ‘0123456789') AND T56 NOT IN [‘00000000', ‘88888888', ‘99999999'] AND T56.MONTH <> ‘99' AND T56.DAY <> ‘99' AND NOT IS_VALID_DATE Record Rejected
TVAL56-8 T5 IN [‘1', ‘2'] AND T56 NOT IN [‘00000000', ‘88888888', ‘99999999'] AND (T56.YEAR < 2008 OR T56.YEAR > CYCLE_YEAR) Record Rejected
Feedback report messages (TVAL56)
Sub–edit Text Type
TVAL56-1 Date of multiple tumours is not composed of 8 numbers. Core Error
TVAL56-2 Year, month and day must relate to a single tumour (all zeros). Core Error
TVAL56-3 Year, month and day must be ‘not applicable'. Core Error
TVAL56-4 Year, month and day must be ‘unknown'. Core Error
TVAL56-5 Date of multiple tumours: month and day must be ‘unknown'. Core Error
TVAL56-6 Date of multiple tumours is not a valid partial date: month is invalid. Core Error
TVAL56-7 Date of multiple tumours is not a valid calendar date. Core Error
TVAL56-8 Date of multiple tumours is out of scope. Core Error
Revision (TVAL56)
Year Description
2008 Edit added: New edit.

TVAL57

Purpose

This edit validates the Multiplicity counter.

Referenced fields (TVAL57)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T57 2 Multiplicity counter TMULTCOUNT

Business rules

For Add and Update Tumour records, Multiplicity counter
  • Must be a numeric value between ‘01' and ‘87', or ‘88' or ‘99'
Edit logic (TVAL57)
Sub–edit Conditions Outcome
TVAL57-1 T5 IN [‘1', ‘2'] AND T57 IS NOT NULL AND T57 NOT IN [Eligible Multiplicity counter codes] Record Rejected
Feedback report messages (TVAL57)
Sub–edit Text Type
TVAL57-1 Multiplicity counter is invalid Core error
Revision (TVAL57)
Year Description
2008 Edit added: New edit.

3.5 Correlation edits

The purpose of the correlation edits is to enforce the business rules between fields on the same Input record. For ease of use, correlation edits have been divided into two groups:

  • Patient correlation edits: enforce business rules between valid patient fields;
  • Tumour correlation edits: enforce business rules between valid tumour fields.

Correlation edits are only performed on Input records where all referenced fields are valid.

3.5.1 Patient correlation edits

The following table summarizes the purpose of each individual edit of this category.

Table 26 Patient correlation edits summary
Edit name Purpose
PCOR1 Ensures that the content of the patient record is consistent with the action described in the Patient record type.
PCOR2 Verifies the likelihood of given names and gender.
PCOR3 Ensures that first given name, second given name and third given name are used coherently.
PCOR4 Ensures that type of current surname code accurately reflects the content of the current surname field.
PCOR5 Ensures that birth surname and current surname are consistent with type of current surname.
PCOR6 Ensures that at least one surname is reported, either the current surname or the birth surname.
PCOR7 Ensures that date of birth and date of death respect a chronological sequence and time frame.
PCOR8 Ensures that death-related variables present a consistent reporting of the patient's vital status.
PCOR9 Ensures that Death registration number and province/territory or country of death are consistent.
PCOR10 Ensures Death registration number and date of death are consistent.
PCOR11 Ensures Death registration number and Underlying cause of death are consistent.

PCOR1

Purpose

This edit ensures that the content of the patient record is consistent with the action described in the patient record type.

Referenced fields (PCOR1)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P3 9 CCR identification number CCR_ID
P4 1 Patient record type PRECTYPE
P5 1 Type of current surname PTYP_CUR
P6 25 Current surname PCURSNAM
P7 15 First given name PGNAME_1
P8 15 Second given name PGNAME_2
P9 7 Third given name PGNAME_3
P10 1 Sex PSEX
P11 8 Date of birth PDATBIR
P12 3 Province/territory or country of birth PPROVBIR
P13 25 Birth surname PBIRNAM
P14 8 Date of death PDATDEA
P15 3 Province/territory or country of death PPROVDEA
P16 6 Death registration number PDEAREG
P17 4 Underlying cause of death PCAUSDEA
P18 1 Autopsy confirming cause of death PAUTOPSY

Business rules

For Add Patient records
  • Patient reporting province/territory, Patient identification number, Type of Current surname, Sex, Date of birth,Province/territory or country of birth, Date of death, Province/territory or country of death, Death registration number, Underlying cause of death and Autopsy confirming cause of death must be provided.
  • CCR identification number must be blank.

For Update Patient records
  • Patient reporting province/territory, Patient identification number, CCR identification number, Type of Current surname, Sex, Date of birth, Province/territory or country of birth, Date of death, Province/territory or country of death, Death registration number, Underlying cause of death and Autopsy confirming cause of death must be provided.

For Delete Patient records

  • Patient reporting Province/territory, Patient identification number, CCR identification number must be provided.
  • Type of Current surname, Current surname, First given name, Second given name, Third given name, Sex, Date of birth, Province/territory or country of birth, Birth surname, Date of death, Province/territory or country of death, Death registration number, Underlying cause of death and Autopsy confirming cause of death must be blank.
Edit logic (PCOR1)
Sub–edit Conditions Outcome
PCOR1-1 P4 = ‘1' AND (P1 IS NULL OR P2 IS NULL OR P3 IS NOT NULL OR P5 IS NULL OR P10 IS NULL OR P11 IS NULL OR P12 IS NULL OR P14 IS NULL OR P15 IS NULL OR P16 IS NULL OR P17 IS NULL OR P18 IS NULL) Record rejected
PCOR1-2 P4 = ‘2' AND (P1 IS NULL OR P2 IS NULL OR P3 IS NULL OR P5 IS NULL OR P10 IS NULL OR P11 IS NULL OR P12 IS NULL OR P14 IS NULL OR P15 IS NULL OR P16 IS NULL OR P17 IS NULL OR P18 IS NULL) Record rejected
PCOR1-3 P4 = ‘3' AND (P1 IS NULL OR P2 IS NULL OR P3 IS NULL OR P5 IS NOT NULL OR P6 IS NOT NULL OR P7 IS NOT NULL OR P8 IS NOT NULL OR P9 IS NOT NULL OR P10 IS NOT NULL OR P11 IS NOT NULL OR P12 IS NOT NULL OR P13 IS NOT NULL OR P14 IS NOT NULL OR P15 IS NOT NULL OR P16 IS NOT NULL OR P17 IS NOT NULL OR P18 IS NOT NULL) Record rejected
Feedback report messages (PCOR1)
Sub–edit Text Type
PCOR1-1 Input record does not respect the Add Patient record format. There are missing or extra values. Core fatal error
PCOR1-2 Input record does not respect the Update Patient record format. There are missing values. Core fatal error
PCOR1-3 Input record does not respect the Delete Patient record format. There are missing or extra values. Core fatal error
Revision (PCOR1)
Year Description
2004 Edit renamed: Current edit was formerly known as Correlation Edit No.1.

PCOR2

Purpose

This edit verifies the likelihood of given names and sex.

Referenced fields (PCOR2)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P7 15 First given name PGNAME_1
P8 15 Second given name PGNAME_2
P9 7 Third given name PGNAME_3
P10 1 Sex PSEX
Other parameters (PCOR2)
Parameters Length Description
NAME_SEX_THRESHOLD 3 Tolerated average likelihood of First given name, Second given name and Third given name to be associated to the opposite gender according to given name and Sex registry2. Value must be between 0 and 100. Default value is 95.

Business rules

For Add and Update Patient records
  • If the average likelihood of First given name, Second given name and Third given name to be associated to the opposite gender according to given name and Sex registry is greater than NAME_SEX_THRESHOLD, then a warning must be sent.
Edit logic (PCOR2)
Sub–edit Conditions Outcome
PCOR2-1 P4 IN [‘1', ‘2'] AND P10 IN ['1', '2'] AND AVERAGE ([Probability of P7 to be associated to opposite gender], [Probability of P8 to be associated to opposite gender], [Probability of P9 to be associated to opposite gender]) > NAME_SEX_THRESHOLD Warning
Feedback report messages (PCOR2)
Sub–edit Text Type
PCOR2-1 Reported given names are not likely for reported Sex. Warning
Revision (PCOR2)
Year Description
2004 Edit removed: Edit formerly known as Correlation Edit No.2 has been removed.
Edit added: Current edit was not documented before.

PCOR3

Purpose

This edit ensures that first given name, second given name and third given name are used coherently.

Referenced fields (PCOR3)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P7 15 First given name PGNAME_1
P8 15 Second given name PGNAME_2
P9 7 Third given name PGNAME_3

Business rules

For Add and Update Patient records
  • If First given name is blank then Second given name and Third given name must be blank.
  • If Second given name is blank then Third given name must be blank.
Edit logic (PCOR3)
Sub–edit Conditions Outcome
PCOR3-1 P4 IN [‘1', ‘2'] AND P7 IS NULL AND (P8 IS NOT NULL OR P9 IS NOT NULL) Record rejected
PCOR3-2 P4 IN [‘1', ‘2'] AND P8 IS NULL AND P9 IS NOT NULL Record rejected
Feedback report messages (PCOR3)
Sub–edit Text Type
PCOR3-1 First given name is missing. Core error
PCOR3-2 Second given name is missing. Core error
Revision (PCOR3)
Year Description
2004 Edit renamed: Current edit was formerly known as Correlation Edit No.3.

PCOR4

Purpose

This edit ensures that type of current surname code accurately reflects the content of the current surname field.

Referenced fields (PCOR4)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P5 1 Type of current surname PTYP_CUR
P6 25 Current surname PCURSNAM

Business rules

For Add and Update Patient records
  • If Type of Current surname is ‘Current Surname unknown' (0) then Current surname must be blank.
  • If Current surname is blank then Type of Current surname must be ‘Current surname unknown' (0).
Edit logic (PCOR4)
Sub–edit Conditions Outcome
PCOR4-1 P4 IN [‘1', ‘2'] AND ((P5 = ‘0' AND P6 IS NOT NULL) OR (P6 IS NULL AND P5 <> ‘0')) Record rejected
Feedback report messages (PCOR4)
Sub–edit Text Type
PCOR4-1 Type of current surname and Current surname do not agree. Core error
Revision (PCOR4)
Year Description
2004 Edit renamed: Current edit was formerly known as Correlation Edit No.4.

PCOR5

Purpose

This edit ensures that birth surname and current surname are consistent with type of current surname.

Referenced fields (PCOR5)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P5 1 Type of Current surname PTYP_CUR
P6 25 Current surname PCURSNAM
P13 25 Birth surname PBIRNAM

Business rules

For Add and Update Patient records
  • If Type of Current surname is ‘Birth surname' then Current surname and Birth surname must be the same.
Edit logic (PCOR5)
Sub–edit Conditions Outcome
PCOR5-1 P4 IN [‘1', ‘2'] AND P5 = ‘1' AND P6 <> P13 Record rejected
Feedback report messages (PCOR5)
Sub–edit Text Type
PCOR5-1 Current surname and Birth surname are different while Type of current surname indicates that they should be the same. Core error
Revision (PCOR5)
Year Description
2004 Edit renamed: Current edit was formerly known as Correlation Edit No.5.

PCOR6

Purpose

This edit ensures that at least one surname is reported, either the current surname or the birth surname.

Referenced fields (PCOR6)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P6 25 Current surname PCURSNAM
P13 25 Birth surname PBIRNAM

Business rules

For Add and Update Patient records
  • Current surname and Birth surname cannot both be blank.
Edit logic (PCOR6)
Sub–edit Conditions Outcome
PCOR6-1 P4 IN [‘1', ‘2'] AND P6 IS NULL AND P13 IS NULL Record rejected
Feedback report messages (PCOR6)
Sub–edit Text Type
PCOR6-1 Current surname and Birth surname cannot both be blank. Core error
Revision (PCOR6)
Year Description
2004 Edit renamed: Current edit was formerly known as Correlation Edit No.6.

PCOR7

Purpose

This edit ensures that date of birth and date of death respect a chronological sequence and time frame.

Referenced fields (PCOR7)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P11 8 Date of birth PDATBIR
P11.YEAR 4 First 4 characters of P11 (year of date of birth) Not applicable
P11.MONTH 2 5th and 6th characters of P11 (month of date of birth) Not applicable
P11.DAY 2 7th and 8th characters of P11 (day of date of birth) Not applicable
P14 8 Date of death PDATDEA
P14.YEAR 4 First 4 characters of P14 (year of date of death) Not applicable
P14.MONTH 2 5th and 6th characters of P14 (month of date of death) Not applicable
P14.DAY 2 7th and 8th characters of P14 (day of date of death) Not applicable
P19 8 Date of transmission PDATTRAN

Business rules

For Add and Update Patient records
  • If Date of birth and Date of death are at least partially known then
    • Date of death must be on or after Date of birth;
    • Year of Date of death and year of Date of birth should not be more than 110 years apart.
  • If Date of birth is at least partially known and the patient is not known to have died then
    • Year of Date of birth and year of Date of transmission should not be more than 110 years apart.
Edit logic (PCOR7)
Sub–edit Conditions Outcome
PCOR7-1 P4 IN [‘1', ‘2'] AND P11 <> ‘99999999' AND P14 NOT IN [‘00000000', ‘99999999'] AND ((P11.DAY <> ‘99' AND P14.DAY <> ‘99' AND P14 < P11) OR (P11.MONTH <> ‘99' AND P14.MONTH <> ‘99' AND P14.YEAR || P14.MONTH < P11.YEAR || P11.MONTH) OR (P14.YEAR < P11.YEAR)) Record rejected
PCOR7-2 P4 IN [‘1', ‘2'] AND P11 <> ‘99999999' AND ((P14 NOT IN [‘00000000', ‘99999999'] AND P14.YEAR – P11.YEAR > 110) OR (P14 = ‘00000000' AND P19.YEAR – P11.YEAR > 110)) Warning
Feedback report messages (PCOR7)
Sub–edit Text Type
PCOR7-1 Date of death is before Date of birth. Core error
PCOR7-2 The patient is more than 110 years old. Warning
Revision (PCOR7)
Year Description
2004 Edit renamed: Current edit was formerly known as Correlation Edit No.7.
Business rules added: Special handling for patients over 110 years old.

PCOR8

Purpose

This edit ensures that death-related variables present a consistent reporting of the patient's vital status.

Referenced fields (PCOR8)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P14 8 Date of death PDATDEA
P15 3 Province/territory or country of death PPROVDEA
P16 6 Death registration number PDEAREG
P17 4 Underlying cause of death PCAUSDEA
P18 1 Autopsy confirming cause of death PAUTOPSY

Business rules

For Add and Update Patient records
  • If any of the death-related variables (Date of death, Province/territory or country of death, Death registration number, Underlying cause of death and Autopsy confirming cause of death) indicate that the patient is deceased then no variables should indicate that the patient is not known to have died.
Edit logic (PCOR8)
Sub–edit Conditions Outcome
PCOR8-1 P4 IN [‘1', ‘2'] AND (P14 <> ‘00000000' OR P15 <> ‘000' OR P16 <> ‘000000' OR P17 <> ‘0000' OR P18 <> ‘0') AND (P14 = ‘00000000' OR P15 = ‘000' OR P16 = ‘000000' OR P17 = ‘0000' OR P18 = ‘0') Record rejected
Feedback report messages (PCOR8)
Sub–edit Text Type
PCOR8-1 Some death-related variables indicate that the patient is deceased whereas at least another indicates that the patient is not known to have died. Core error
Revision (PCOR8)
Year Description
2004 Edit removed: Edit formerly known as Correlation Edit No.8 was redundant with PVAL11.
Edit renamed: Current edit was formerly known as Correlation Edit No.10.

PCOR9

Purpose

This edit ensures that death registration number and province/territory or country of death are consistent.

Referenced fields (PCOR9)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P15 3 Province/territory or country of death PPROVDEA
P16 6 Death registration number PDEAREG

Business rules

For Add and Update Patient records
  • If Death registration number is known then Province/territory or country of death must indicate a specific location in Canada or United States of America.
  • If Death registration number indicated that the Patient died outside Canada then Province/territory or country of death must indicate a foreign country or unknown place.
  • If Death registration number is unknown then Province/territory or country of death must be either a location in Canada or an unknown place.
Edit logic (PCOR9)
Sub–edit Conditions Outcome
PCOR9-1 P4 IN [‘1', ‘2'] AND P16 IN [000001-999997] AND P15 NOT IN [840, 910, 911, 912, 913, 924, 935, 946, 947, 948, 959, 960, 961, 962] Record rejected
PCOR9-2 P4 IN [‘1', ‘2'] AND P16 = ‘999998' AND P15 IN [909, 910, 911, 912, 913, 924, 935, 946, 947, 948, 959, 960, 961, 962] Record rejected
PCOR9-3 P4 IN [‘1', ‘2'] AND P16 = ‘999999' AND P15 NOT IN [909, 910, 911, 912, 913, 924, 935, 946, 947, 948, 959, 960, 961, 962, 999] Record rejected
Feedback report messages (PCOR9)
Sub–edit Text Type
PCOR9-1 If Death registration number is known then province/territory or country of death must indicate a specific location in Canada or United States of America. Core error
PCOR9-2 If Death registration number indicated that the patient died outside Canada then province/territory or country of death must indicate a foreign country or unknown place. Core error
PCOR9-3 If Death registration number is unknown then province/territory or country of death must be either a location in Canada or an unknown place. Core error
Revision (PCOR9)
Year Description
2004 Edit reorganized: Edit formerly known as Correlation Edit No.9 merged with PVAL14.
Edit renamed: Current edit was formerly known as Correlation Edit No.11.
Business rules changed: If Death registration number is known then province/territory or country of death must indicate a specific location in Canada or United States of America; If Death registration number is unknown then province/territory or country of death must be either a location in Canada or an unknown place.
Business rules added: If Death registration number indicated that the patient died outside Canada then province/territory or country of death must indicate a foreign country or unknown place.

PCOR10

Purpose

This edit ensures death registration number and date of death are consistent.

Referenced fields (PCOR10)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P14 8 Date of death PDATDEA
P16 6 Death registration number PDEAREG

Business rules

For Add and Update Patient records
  • If Death registration number is known then Date of death must be at least partially known.
Edit logic (PCOR10)
Sub–edit Conditions Outcome
PCOR10-1 P4 IN [‘1', ‘2'] AND P16 IN [000001-999997] AND P14.YEAR = ‘9999' Record rejected
Feedback report messages (PCOR10)
Sub–edit Text Type
PCOR10-1 Date of death cannot be unknown if Death registration number is known. Core error
Revision (PCOR10)
Year Description
2004 Edit reorganized: Edit formerly known as Correlation Edit No.10 moved to PCOR8.
Edit added: New edit.

PCOR11

Purpose

This edit ensures death registration number and underlying cause of death are consistent.

Referenced fields (PCOR11)
Field Length Description Acronym
P4 1 Patient record type PRECTYPE
P16 6 Death registration number PDEAREG
P17 3 Underlying cause of death PCAUSDEA

Business rules

For Add and Update Patient records
  • If Death registration number is unknown then Underlying cause of death cannot be ‘Officially unknown'.
Edit logic (PCOR11)
Sub–edit Conditions Outcome
PCOR11-1 P4 IN [‘1', ‘2'] AND P16 = ‘999999' AND P17 IN = [‘R99', ‘7999'] Record rejected
Feedback report messages (PCOR11)
Sub–edit Text Type
PCOR11-1 Underlying cause of death cannot be ‘Officially unknown' when Death registration is unknown. Core error
Revision (PCOR11)
Year Description
2004 Edit reorganized: Edit formerly known as Correlation Edit No.11 moved to PCOR9.
Edit added: New edit.

3.5.2 Tumour correlation edits

The following table summarizes the purpose of each individual edit of this category.

Table 27 Tumour correlation edits summary
Edit name Purpose
TCOR1 Ensures that the content of the core tumour fields is consistent with the operation described in the Tumour record type.
TCOR2 Ensures that Postal code and Standard geographic code are coherent.
TCOR3 Ensures that Census tract and Standard geographic code are coherent.
TCOR4 Rejects tumour data for patients living outside the reporting province/territory at time of diagnosis.
TCOR5 Ensures that expected topography, histology and behaviour values are reported based on the Source classification flag.
TCOR6 Ensures the consistency between ICD-9 Cancer code and related ICD-O-2 values.
TCOR7 Ensures the consistency between related ICD-O-2 and ICD-O-3 values.
TCOR8 Not applicable. (Placeholder for future requirement implementation.)
TCOR9 Rejects tumour records that are outside the CCR core scope.
TCOR10 Ensures that invalid combinations of topography and histology are rejected.
TCOR11 Ensures that invalid combinations of histology and behaviour codes are rejected.
TCOR12 Ensures the consistency between the topography and the laterality.
TCOR13 Ensures that invalid combinations of Method used to establish the date of diagnosis and Diagnostic confirmation codes are rejected.
TCOR14 Ensures that Method of diagnosis is only reported for tumours diagnosed prior to 2004.
TCOR15 Ensures that Method used to establish the date of diagnosis is only reported for tumours diagnosed in 2004 and onwards.
TCOR16 Ensures that Diagnostic confirmation is only reported for tumours diagnosed in 2004 and onwards.
TCOR17 Ensures that Grade, differentiation or cell indicator is only reported for tumours diagnosed in 2004 and onwards.
TCOR18 This edit ensures that Collaborative Staging variables are reported for tumours within the CCR collaborative staging scope.
TCOR19 This edit ensures that AJCC TNM staging variables are reported for tumours within the CCR AJCC TNM staging scope.
TCOR20 Ensures that TNM stage group is reported only when clinical and pathologic TNM stage group are not reported.
TCOR21 Ensures that the combination of AJCC clinical TNM stage group and individual clinical T, N, M values is acceptable.
TCOR22 Ensures that the combination of AJCC pathologic TNM stage group and the individual pathologic T, N, M values is acceptable.
TCOR23 Ensures that the combination of AJCC TNM stage group and the individual clinical/pathologic T, N, M values is acceptable.
TCOR24 Ensures that AJCC edition number is coherent with all remaining AJCC TNM staging variables.
TCOR26 Ensures the consistency between Ambiguous terminology diagnosis and Date of conclusive diagnosis.
TCOR27 Ensures the consistency between Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter.
TCOR29 Ensures the consistency between Ambiguous terminology diagnosis and Date of Conclusive Diagnosis.
TCOR30 Ensures that date of diagnosis and date of conclusive diagnosis respect a chronological sequence and time frame.
TCOR31 Ensures the consistency between ICD-O-2/3 Topography and Type of multiple tumours reported as one primary.
TCOR32 Ensures the consistency between ICD-O-3 Behaviour and Multiple tumours reported as one primary.
TCOR33 Ensures the consistency between Type of Multiple Tumours Reported as One Primary, ICD-O-2/3 Topography and ICD-O-3 Histology.
TCOR34 Ensures the consistency between Date of multiple tumours and Type of multiple tumours reported as one primary.
TCOR35 Ensures the consistency between Method Used to Establish the Date of Diagnosis, Type of Multiple Tumours Reported as One Primary, Date of Multiple Tumours and Multiplicity Counter.

TCOR1

Purpose

This edit ensures that the content of the core tumour fields is consistent with the operation described in the tumour record type.

Referenced fields (TCOR1)
Field Length Description Acronym
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Tumour patient identification number TPIN
T3 9 Tumour reference number TTRN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
T6 25 Name of place of residence TPLACRES
T7 6 Postal code TPOSTCOD
T8 7 Standard geographic code TCODPLAC
T9 9 Census tract TCENTRAC
T10 15 Health insurance number THIN
T11 1 Method of diagnosis TMETHDIAG
T12 8 Date of diagnosis TDATDIAG
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T13 4 ICD-9 cancer code TICD_9
T14 1 Source classification flag TSCF
T15 4 ICD-O-2/3 Topography TICD_O2T
T16 4 ICD-O-2 Histology TICD_O2H
T17 1 ICD-O-2 Behaviour TICD_O2B
T19 1 Laterality TLATERAL
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T23 1 Grade, differentiation or cell indicator TGRADE
T24 1 Method used to establish the date of diagnosis TMETHUSED
T25 1 Diagnostic confirmation TMETHCONF
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T42 9 AJCC clinical T TAJCCCLINT
T43 3 AJCC clinical N TAJCCCLINN
T44 3 AJCC clinical M TAJCCCLINM
T45 9 AJCC pathologic T TAJCCPATHT
T46 3 AJCC pathologic N TAJCCPATHN
T47 3 AJCC pathologic M TAJCCPATHM
T48 4 AJCC clinical TNM stage group TAJCCCLINSG
T49 4 AJCC pathologic TNM stage group TAJCCPATHSG
T50 4 AJCC TNM stage group TAJCCSG
T51 2 AJCC edition number TAJCCEDNUM
T52 6 CS Version 1st TCSFVER
T53 1 Ambiguous Terminology Diagnosis TAMBIGTERM
T54 8 Date of Conclusive Diagnosis TDATCONCLUSDIAG
T55 2 Type of Multiple Tumours Reported as One Primary TMULTTUMONEPRIM
T56 8 Date of Multiple Tumours TDATMULT
T57 2 Multiplicity Counter TMULTCOUNT

Business rules

For Add Tumour records
  • Tumour reporting province/territory, Tumour patient identification number, Tumour reference number, Postal code, Standard geographic code, Method of diagnosis, Date of diagnosis, ICD-9 cancer code, Source classification flag, ICD-O-2/3 Topography, ICD-O-2 Histology, ICD-O-2 Behaviour, Laterality, ICD-O-3 Histology, ICD-O-3 Behaviour, Grade, differentiation or cell indicator, Method used to establish the date of diagnosis, Diagnostic confirmation must be provided39.
  • Fillers (T18 and T20) are ignored.
For Update Tumour records
  • Tumour reporting province/territory, Tumour patient identification number, Tumour reference number, CCR identification number, Postal code, Standard geographic code, Method of diagnosis, Date of diagnosis, ICD-9 cancer code, Source classification flag, ICD-O-2/3 Topography, ICD-O-2 Histology, ICD-O-2 Behaviour, Laterality, ICD-O-3 Histology, ICD-O-3 Behaviour, Grade, differentiation or cell indicator, Method used to establish the date of diagnosis, Diagnostic confirmation must be provided39.
  • Fillers (T18 and T20) are ignored.
For Delete Tumour records
  • Tumour reporting province/territory, Tumour patient identification number, Tumour reference number and CCR identification number must be provided.
  • Name of place of residence, Postal code, Standard geographic code, Census tract, Health insurance number, Method of diagnosis, Date of diagnosis, ICD-9 cancer code, Source classification flag, ICD-O-2/3 Topography, ICD-O-2 Histology, ICD-O-2 Behaviour, Laterality, ICD-O-3 Histology, ICD-O-3 Behaviour, Grade, differentiation or cell indicator, Method used to establish the date of diagnosis, Diagnostic confirmation, CS tumour size, CS extension, CS tumour size/ext eval, CS lymph nodes, CS reg nodes eval, Regional nodes examined, Regional nodes positive, CS mets at dx, CS mets eval, CS site-specific factor 1, CS site-specific factor 2, CS site-specific factor 3, CS site-specific factor 4, CS site-specific factor 5, CS site-specific factor 6, AJCC clinical T, AJCC clinical N, AJCC clinical M, AJCC pathologic T, AJCC pathologic N, AJCC pathologic M, AJCC clinical TNM stage group, AJCC pathologic TNM stage group, AJCC TNM stage group, AJCC edition number, CS Version 1st, Ambiguous Terminology Diagnosis, Date of conclusive diagnosis, Type of multiple tumours reported as one primary, Date of multiple tumours, and Multiplicity Counter must be blank.
  • Fillers (T18 and T20) are ignored.
Edit logic (TCOR1)
Sub–edit Conditions Outcome
TCOR1-1 T5 = ‘1' AND (T1 IS NULL OR T2 IS NULL OR T3 IS NULL OR T7 IS NULL OR T8 IS NULL OR T11 IS NULL OR T12 IS NULL OR T13 IS NULL OR T14 IS NULL OR T15 IS NULL OR T16 IS NULL OR T17 IS NULL OR T19 IS NULL OR T21 IS NULL OR T22 IS NULL OR T23 IS NULL OR T24 IS NULL OR T25 IS NULL) OR (T12 IS NOT NULL AND T12.YEAR < 2006 AND T9 IS NULL)) Record rejected
TCOR1-2 T5 = ‘2' AND (T1 IS NULL OR T2 IS NULL OR T3 IS NULL OR T4 IS NULL OR T7 IS NULL OR T8 IS NULL OR T11 IS NULL OR T12 IS NULL OR T13 IS NULL OR T14 IS NULL OR T15 IS NULL OR T16 IS NULL OR T17 IS NULL OR T19 IS NULL OR T21 IS NULL OR T22 IS NULL OR T23 IS NULL OR T24 IS NULL OR T25 IS NULL) OR (T12 IS NOT NULL AND T12.YEAR < 2006 AND T9 IS NULL) Record rejected
TCOR1-3 T5 = ‘3' AND (T1 IS NULL OR T2 IS NULL OR T3 IS NULL OR T4 IS NULL OR T6 IS NOT NULL OR T7 IS NOT NULL OR T8 IS NOT NULL OR T9 IS NOT NULL OR T10 IS NOT NULL OR T11 IS NOT NULL OR T12 IS NOT NULL OR T13 IS NOT NULL OR T14 IS NOT NULL OR T15 IS NOT NULL OR T16 IS NOT NULL OR T17 IS NOT NULL OR T19 IS NOT NULL OR T21 IS NOT NULL OR T22 IS NOT NULL OR T23 IS NOT NULL OR T24 IS NOT NULL OR T25 IS NOT NULL OR T27 IS NOT NULL OR T28 IS NOT NULL OR T29 IS NOT NULL OR T30 IS NOT NULL OR T31 IS NOT NULL OR T32 IS NOT NULL OR T33 IS NOT NULL OR T34 IS NOT NULL OR T35 IS NOT NULL OR T36 IS NOT NULL OR T37 IS NOT NULL OR T38 IS NOT NULL OR T39 IS NOT NULL OR T40 IS NOT NULL OR T41 IS NOT NULL OR T42 IS NOT NULL OR T43 IS NOT NULL OR T44 IS NOT NULL OR T45 IS NOT NULL OR T46 IS NOT NULL OR T47 IS NOT NULL OR T48 IS NOT NULL OR T49 IS NOT NULL OR T50 IS NOT NULL OR T51 IS NOT NULL OR T52 IS NOT NULL OR T53 IS NOT NULL OR T54 IS NOT NULL OR T55 IS NOT NULL OR T56 IS NOT NULL OR T57 IS NOT NULL) Record rejected
Feedback report messages (TCOR1)
Sub–edit Text Type
TCOR1-1 Input record does not respect the Add Tumour record format. There are missing values. Core fatal error
TCOR1-2 Input record does not respect the Update Tumour record format. There are missing values. Core fatal error
TCOR1-3 Input record does not respect the Delete Tumour record format. There are missing or extra values. Core fatal error
Revision (TCOR1)
Year Description
2008 Business rules and Edit logic changed: Fields T53 to T57 have been added.
2007 Business rules and Edit logic changed: Field T52 has been added.
2006 Business rules and Edit logic changed: Census tract effective date range ended in 2005. For cases diagnosed in 2006 and onwards, T9 (Census tract) must not be reported.
2004 Edit renamed: Edit formerly known as Correlation Edit No.12.
Business rules changed: Handle new fields related to Collaborative staging and TNM data.

TCOR2

Purpose

This edit ensures that postal code and standard geographic code are coherent.

Referenced fields (TCOR2)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T7 6 Postal code TPOSTCOD
T7.FIRST 1 First digit of Postal code Not applicable
T8.PROV 2 First 2 digits of T8 (province code of Standard geographic code) Not applicable

Business rules

For Add and Update Tumour records, if Postal code is known then
  • it must start with ‘A' if in Newfoundland or Labrador;
  • it must start with ‘B' if in Nova Scotia;
  • it must start with ‘C' if in Prince Edward Island;
  • it must start with ‘E' if in New Brunswick;
  • it must start with ‘G', ‘H', ‘J' or ‘K' if in Quebec;
  • it must start with ‘K', ‘L', 'M', ‘N' or ‘P' if in Ontario;
  • it must start with ‘R' if in Manitoba;
  • it must start with ‘R' or ‘S' if in Saskatchewan;
  • it must start with ‘S' or ‘T' if in Alberta;
  • it must start with ‘V' if in British Columbia;
  • it must start with ‘Y' if in Yukon;
  • it must start with ‘X' if in Northwest Territories;
  • it must start with ‘X' if in Nunavut.
Edit logic (TCOR2)
Sub–edit Conditions Outcome
TCOR2-1 T5 IN [‘1', ‘2'] AND T7 <> ‘999999' AND ((T8.PROV = ‘10' AND T7.FIRST <> ‘A') OR (T8.PROV = ‘11' AND T7.FIRST <> ‘C') OR (T8.PROV = ‘12' AND T7.FIRST <> ‘B') OR (T8.PROV = ‘13' AND T7.FIRST <> ‘E') OR (T8.PROV = ‘24' AND T7.FIRST NOT IN [‘G', ‘H', ‘J', ‘K']) OR (T8.PROV = ‘35' AND T7.FIRST NOT IN [‘K', ‘L', ‘M', ‘N', ‘P']) OR (T8.PROV = ‘46' AND T7.FIRST <> ‘R') OR (T8.PROV = ‘47' AND T7.FIRST NOT IN [‘R', ‘S']) OR (T8.PROV = ‘48' AND T7.FIRST NOT IN [‘S', ‘T']) OR (T8.PROV = ‘59' AND T7.FIRST <> ‘V') OR (T8.PROV = ‘60' AND T7.FIRST <> ‘Y') OR (T8.PROV = ‘61' AND T7.FIRST <> ‘X') OR (T8.PROV = ‘62' AND T7.FIRST <> ‘X')) Record rejected
Feedback report messages (TCOR2)
Sub–edit Text Type
TCOR2-1 Postal code and Standard geographic code indicate 2 different provinces/territories. Core error
Revision (TCOR2)
Year Description
2004 Edit renamed: Edit formerly known as Correlation Edit No.14.

TCOR3

Purpose

This edit ensures that census tract and standard geographic code are coherent.

Referenced fields (TCOR3)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T8 7 Standard geographic code TCODPLAC
T9 9 Census tract TCENTRAC
T12.YEAR 4 First 4 characters of T12 (year of the Date of diagnosis) Not applicable

Business rules

For Add and Update Tumour records
  • If Date of diagnosis is between year 1992 and 1995 inclusively, and both Census tract and Standard geographic code are fully known, then the reported Standard geographic code must match the Standard geographic code associated with the Census tract in Eligible Census tracts from 1992 to 199512 .
  • If Date of diagnosis is between year 1996 and 2000 inclusively, and both Census tract and Standard geographic code are fully known, then the reported Standard geographic code must match the Standard geographic code associated with the Census tract in Eligible Census tracts from 1996 to 200012.
  • If Date of diagnosis is between year 2001 and 2005 inclusively, and both Census tract and Standard geographic code are fully known, then the reported Standard geographic code must match the Standard geographic code associated with the Census tract in Eligible Census tracts from 2001 to 200512.
Edit logic (TCOR3)
Sub–edit Conditions Outcome
TCOR3-1 T5 IN [‘1', ‘2'] AND T8 NOT LIKE ‘_ _ _ _ 999' AND T9 NOT LIKE ‘___999.99' AND T12.YEAR >= 1992 AND T12.YEAR < 1996 AND T8 NOT IN [SGC from Eligible Census tracts from 1992 to 1995 where Census tract = T9] Record rejected
TCOR3-2 T5 IN [‘1', ‘2'] AND T8 NOT LIKE ‘_ _ _ _ 999' AND T9 NOT LIKE ‘___999.99' AND T12.YEAR >= 1996 AND T12.YEAR < 2001 AND T8 NOT IN [SGC from Eligible Census tracts from 1996 to 2000 where Census tract = T9] Record rejected
TCOR3-3 T5 IN [‘1', ‘2'] AND T8 NOT LIKE ‘_ _ _ _ 999' AND T9 NOT LIKE ‘___999.99' AND T12.YEAR >= 2001 AND T12.YEAR < 2005 AND T8 NOT IN [SGC from Eligible Census tracts from 2001 to 2005 where Census tract = T9] Record rejected
Feedback report messages (TCOR3)
Sub–edit Text Type
TCOR3-1 Census tract and Standard geographic code combination not found in Census tract Data dictionary – 1991. Core error
TCOR3-2 Census tract and Standard geographic code combination not found in Census tract Data dictionary – 1996. Core error
TCOR3-3 Census tract and Standard geographic code combination not found in Census tract Data dictionary – 2001. Core error
Revision (TCOR3)
Year Description
2006 Business rules and Edit logic changed: Edit modified to include combinations where Census tract indicate an area outside a Census Metropolitan Area.
2004 Edit renamed: Edit formerly known as Correlation Edit No.15

TCOR4

Purpose

This edit rejects tumour data for patients living outside the reporting province/territory at time of diagnosis.

Referenced fields (TCOR4)
Field Length Description Acronym
T1 2 Tumour reporting province/territory TREPPROV
T5 1 Tumour record type TRECTYPE
T8.PROV 2 First 2 characters from T8 (province code of Standard geographic code) Not applicable

Business rules

For Add and Update Tumour records
  • Tumour reporting province/territory must be equal to province code found in Standard geographic code.
Edit logic (TCOR4)
Sub–edit Conditions Outcome
TCOR4-1 T5 IN [‘1', ‘2'] AND T1 <> T8.PROV Record rejected
Feedback report messages (TCOR4)
Sub–edit Text Type
TCOR4-1 Reporting province/territory and Standard geographic code must indicate the same province/territory. Core error
Revision (TCOR4)
Year Description
2004 Edit renamed: Edit formerly known as Correlation Edit No.16.

TCOR5

Purpose

This edit ensures that expected topography, histology and behaviour values are reported based on the Source classification flag.

Referenced fields (TCOR5)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T13 4 ICD-9 cancer code TICD_9
T14 1 Source classification flag TSCF
T16 4 ICD-O-2 Histology TICD_O2H
T17 1 ICD-O-2 Behaviour TICD_O2B

Business rules

For Add and Update Tumour records
  • If Source classification Flag indicates that ICD-9 is the Source classification then ICD-9 cancer code, ICD-O-2/3 Topography40, ICD-O-2 Histology, ICD-O-2 Behaviour41, ICD-O-3 Histology42 and ICD-O-3 Behaviour41 must be reported.
  • If Source classification flag indicates that ICD-O-2 is the Source classification then ICD-O-2/3 Topography40, ICD–O–2 Histology, ICD-O-2 Behaviour41, ICD-O-3 Histology42 and ICD-O-3 Behaviour41 must be reported and ICD-9 Cancer code must not be reported.
  • If Source classification flag indicates that ICD-O-3 is the Source classification then ICD-O-2/3 Topography42, ICD-O-3 Histology40 and ICD-O-3 Behaviour41 must be reported and ICD-9 cancer code, ICD-O-2 Histology and ICD-O-2 Behaviour must not be reported.
Edit logic (TCOR5)
Sub–edit Conditions Outcome
TCOR5-1 T5 IN [‘1', ‘2'] AND T14 = ‘1' AND (T13 = ‘0000' OR T16 = ‘0000') Record rejected
TCOR5-2 T5 IN [‘1', ‘2'] AND T14 = ‘2' AND T16 = ‘0000' Record rejected
TCOR5-3 T5 IN [‘1', ‘2'] AND T14 = ‘2' AND T13 <> ‘0000' Record rejected
TCOR5-4 T5 IN [‘1', ‘2'] AND T14 = ‘4' AND (T13 <> '0000' OR T16 <> ‘0000' OR T17 <> ‘0') Record rejected
Feedback report messages (TCOR5)
Sub–edit Text Type
TCOR5-1 Based on the Source classification flag, ICD-9 Cancer code and ICD-O-2 Histology must be reported. Core Error
TCOR5-2 Based on the Source classification flag, ICD-O-2 Histology must be reported. Core Error
TCOR5-3 Based on the Source classification flag, ICD-9 Cancer code must not be reported. Core Error
TCOR5-4 Based on the Source classification flag, ICD-9 cancer code, ICD-O-2 Histology and ICD-O-2 Behaviour must not be reported. Core Error
Revision (TCOR5)
Year Description
2004 Edit renamed: Edit formerly known as Correlation Edit No.18.
Business rules deleted: ICD-10 related rules dropped.
Business rules changed: Ensure that topography and histology are reported in accordance with the Source classification flag.
Business rules added: Prevent the reporting of data using a classification older than the one indicated by the Source classification flag.

TCOR6

Purpose

This edit ensures the consistency between ICD-9 Cancer code and related ICD-O-2 values.

Referenced fields (TCOR6)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T13 4 ICD-9 cancer code TICD_9
T14 1 Source classification flag TSCF
T15 4 ICD-O-2/3 Topography TICD_O2T
T16 4 ICD-O-2 Histology TICD_O2H
T17 1 ICD-O-2 Behaviour TICD_O2B

Business rules

For Add and Update Tumour records where the source classification is ICD-9
  • ICD-9 Cancer code and ICD-O-2/3 Topography must match based on ICD-9 to ICD-O-2 conversion table43.
  • If ICD-9 Cancer code is related to a specific histology code (different than 8000) based on ICD-9 to ICD-O-2 conversion table then reported ICD-O-2 Histology should not be generic (equal to 8000).
  • ICD-9 Cancer code and ICD-O-2 Behaviour must be coherent based on ICD-9 to ICD-O-2 conversion table.
Edit logic (TCOR6)
Sub–edit Conditions Outcome
TCOR6-1 T5 IN [‘1', ‘2'] AND T14 = '1' AND T13 <> '0000' AND (T13 and T15 NOT IN [ICD-9 to ICD-O-2 conversion table]) Record Rejected
TCOR6-2 T5 IN [‘1', ‘2'] AND T14 = '1' AND T13 <> '0000' AND T16 = '8000' AND (ICD-O-2 Histology <> '8000' IN [ICD-9 to ICD-O-2 conversion table where ICD-9 = T13]) Warning
TCOR6-3 T5 IN [‘1', ‘2'] AND T14 = '1' AND T13 <> '0000' AND (T13 and T17 NOT IN [ICD-9 to ICD-O-2 conversion table]) Record Rejected
Feedback report messages (TCOR6)
Sub–edit Text Type
TCOR6-1 ICD-9 Cancer code and ICD-O-2/3 Topography are not coherent. Core Error
TCOR6-2 ICD-O-2 Histology could have been more precise based on ICD-9 cancer code. Warning
TCOR6-3 ICD-9 Cancer code and ICD-O-2 Behaviour are not coherent. Core Error
Revision (TCOR6)
Year Description
2004 Edit renamed: Edit formerly known as Correlation Edit No.20
Business rules deleted: ICD-10 related rules dropped.
Business rules added:
Coherence check between ICD-9 Cancer code and ICD-O2/3 Topography added.
Coherence check between ICD-9 Cancer code and ICD-O-2 Histology added.

TCOR7

Purpose

This edit ensures the consistency between related ICD-O-2 and ICD-O-3 values.

Referenced fields (TCOR7)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T14 1 Source classification flag TSCF
T15 4 ICD-O-2/3 Topography TICD_O2T
T16 4 ICD-O-2 Histology TICD_O2H
T17 1 ICD-O-2 Behaviour TICD_O2B
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B

Business rules

For Add and Update Tumour records where the source classification is either ICD-9 or ICD-O-2
  • ICD-O-3 Histology and ICD-O-3 Behaviour combination must be consistent with ICD-O-2/3 Topography, ICD-O-2 Histology and ICD-O-2 Behaviour combination based on ICD-O-2 to ICD-O-3 conversion table44.
Edit logic (TCOR7)
Sub–edit Conditions Outcome
TCOR7-1 T5 IN [‘1', ‘2'] AND T14 IN [‘1', '2'] AND T16 <> '0000' AND (T21 and T22 combination NOT IN [ICD-O-2 to ICD-O-3 conversion table for T15, T16 and T17 combination]) Record rejected
Feedback report messages (TCOR7)
Sub–edit Text Type
TCOR7-1 ICD-O-3 Histology and ICD-O-3 Behaviour combination is not coherent with ICD-O-2/3 Topography, ICD-O-2 Histology and ICD-O-2 Behaviour combination. Core Error
Revision (TCOR7)
Year Description
2004 Edit added: New edit.

TCOR8

Purpose

Not applicable. (This empty correlation is kept as a placeholder for future requirement implementation.)

Referenced fields (TCOR8)
Field Length Description Acronym
Not applicable Not applicable Not applicable Not applicable

Business rules

Not applicable

Edit logic (TCOR8)
Sub–edit Conditions Outcome
Not applicable Not applicable Not applicable
Feedback report messages (TCOR8)
Sub–edit Text Type
Not applicable Not applicable Not applicable
Revision (TCOR8)
Year Description
Not applicable Not applicable

TCOR9

Purpose

This edit rejects tumour records that are outside the CCR core scope.

Referenced fields (TCOR9)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of Date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B

Business rules

For Add and Update Tumour records
  • ICD-O-2/3 Topography, ICD-O-3 Histology, ICD-O-3 Behaviour and year of Date of diagnosis combination must be within the CCR core scope45.
Edit logic (TCOR9)
Sub–edit Conditions Outcome
TCOR9-1 T5 IN [‘1', ‘2'] AND (T12.YEAR, T15, T21 and T22 NOT IN [CCR core scope]) Record rejected
Feedback report messages (TCOR9)
Sub–edit Text Type
TCOR9-1 Based on ICD-O-2/3 Topography, ICD-O-3 Histology and Behaviour and Date of diagnosis, the tumour is outside the CCR core scope. Core Error
Revision (TCOR9)
Year Description
2004 Edit consolidated: Edits formerly known as Correlation edit No.13 and Correlation edit No.21.
Business rules changed: Verification is now performed on ICD-O-3 values only, regardless of the source classification used.

TCOR10

Purpose

This edit ensures that invalid combinations of topography and histology are rejected.

Referenced fields (TCOR10)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of Date of diagnosis (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H

Business rules

For Add and Update Tumour records
  • ICD-O-2/3 Topography and ICD-O-3 Histology and year of date of diagnosis combination must not be invalid based on Invalid site and Histology combinations table46.
Edit logic (TCOR10)
Sub–edit Conditions Outcome
TCOR10-1 T5 IN [‘1', ‘2'] AND (T12.Year, T15 and T21 IN [Invalid site and Histology combinations]) Record rejected
Feedback report messages (TCOR10)
Sub–edit Text Type
TCOR10-1 ICD-O-2/3 Topography, ICD-O-3 Histology and Date of diagnosis combination is either invalid or not eligible for CCR. Core error
Revision (TCOR10)
Year Description
2007 Referenced fields, Business rules, Edit logic and Feedback report messages changed: Verification now includes Date of diagnosis.
2004 Edit renamed: Edit formerly known as Correlation Edit No.23.
Business rules changed: Verification is now performed on ICD-O-3 values only, regardless of the source classification used.

TCOR11

Purpose

This edit ensures that invalid combinations of histology and behaviour codes are rejected.

Note: Invalid combinations are combinations that are invalid from a subject matter point of view. These are different from matrix combinations which are combinations not explicitly listed in ICD-O but possible from a subject matter point of view and allowed based on rules or coding guidelines for morphology, ICD-O-3 (page 29).

Referenced fields (TCOR11)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of Date of diagnosis (year of date of diagnosis) Not applicable
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B

Business rules

For Add and Update Tumour records
  • ICD-O-3 Histology, ICD-O-3 Behaviour and year of date of diagnosis combination must not be invalid based on Invalid Histology and Behaviour combination table47.
Edit logic (TCOR11)
Sub–edit Conditions Outcome
TCOR11-1 T5 IN [‘1', ‘2'] AND (T12.YEAR, T21 and T22 IN [Invalid Histology and Behaviour combination]) Record rejected
Feedback report messages (TCOR11)
Sub–edit Text Type
TCOR11-1 ICD-O-3 Histology, ICD-O-3 Behaviour and Date of diagnosis combination is invalid. Core error
Revision (TCOR11)
Year Description
2007 Referenced fields, Business rules, Edit logic and Feedback report messages changed: Verification now includes Date of diagnosis.
2004 Edit renamed: Edit formerly known as Correlation Edit No.24.
Business rules changed: Verification is now performed on ICD-O-3 values only, regardless of the source classification used.

TCOR12

Purpose

This edit ensures the consistency between the topography and the laterality.

Referenced fields (TCOR12)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of Date of diagnosis (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T19 1 Laterality TLATERAL

Business rules

For Add and Update Tumour records
  • ICD-O-2/3 Topography, Laterality and year of date of diagnosis combination must be valid based on Valid site and Laterality combinations table48.
Edit logic (TCOR12)
Sub–edit Conditions Outcome
TCOR12-1 T5 IN [‘1', ‘2'] AND (T12.Year, T15 and T19 NOT IN [Valid site and Laterality combinations table]) Record rejected
Feedback report messages (TCOR12)
Sub–edit Text Type
TCOR12-1 ICD-O-2/3 Topography, Laterality and Date of diagnosis combination is invalid. Core error
Revision (TCOR12)
Year Description
2004 Edit renamed: Edit formerly known as Correlation Edit No.22.
Business rules changed: Verification is now performed on ICD-O-3 values only, regardless of the source classification used.

TCOR13

Purpose

This edit ensures that invalid combinations of Method used to establish the date of diagnosis and Diagnostic confirmation codes are rejected.

Referenced fields (TCOR13)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of Date of Diagnosis (year of Date of Diagnosis) N/A
T24 1 Method used to establish the date of diagnosis TMETHUSED
T25 1 Diagnostic confirmation TMETHCONF
T53 1 Ambiguous Terminology Diagnosis TAMBIGTERM

Business rules

For Add and Update Tumour records where the Date of Diagnosis is in 2004 or after
  • Diagnostic confirmation cannot be less definitive than Method used to establish the date of diagnosis. Example: Diagnostic confirmation cannot be "positive cytology" if the Method used to establish the Date of Diagnosis is "positive histology".
  • Method used to establish the date of diagnosis and Diagnostic confirmation must indicate the same value when either is "Autopsy Only" or "Death Certificate Only (DCO)" and the other one is reported.

For Add and Update Tumour records where the Date of Diagnosis is in 2008 or after

  • If Ambiguous Terminology Diagnosis is Ambiguous terminology only (1) then
    • Diagnostic Confirmation must be more definitive than Method used to establish date of diagnosis.
Edit logic (TCOR13)
Sub–edit Conditions Outcome
TCOR13-1 T5 IN ['1', '2'] AND (T12.YEAR>= '2008') AND T53 = ‘1' AND T24 IN ['1','2','4','5','6','7', ‘9'] AND T25 IN ['1','2','4','5','6','7', ‘9'] AND ((T24='2' AND T25='2') OR (T24<T25)) Record rejected
TCOR13-2 T5 IN ['1', '2'] AND (T12.YEAR>= '2004' ) AND T24 IN ['1','2','4','5','6','7', ‘9'] AND T25 IN ['1','2','4','5','6','7', ‘9'] AND ((T24='2' AND T25='2') OR (T24<T25 AND NOT (T24='1' and T25='2'))) Record rejected
TCOR13-3 T5 IN [‘1', ‘2'] AND T12.YEAR>= '2004' AND ((T24 IN ['3', '8'] AND T25<>'0') OR (T25 IN ['3', '8'] AND T24<>'0')) AND T24 <> T25) Record rejected
Feedback report messasges (TCOR13)
Sub–edit Text Type
TCOR13-1 Diagnostic confirmation must be more definitive than Method used to establish the date of diagnosis when Ambiguous terminology is equal to 1. Core error
TCOR13-2 Diagnostic confirmation cannot be less definitive than Method used to establish the date of diagnosis. Core error
TCOR13-3 Method Used to Establish the Date of Diagnosis and Diagnostic Confirmation must indicate the same method when either is "Autopsy Only" or "Death Certificate Only (DCO)". Core error
Revision (TCOR13)
Year Description
2008 New Sub-edit added: To make Diagnostic confirmation more definitive than Method used to establish the date of diagnosis.
2007 New edit added.

TCOR14

Purpose

This edit ensures that method of diagnosis is only reported for tumours diagnosed prior to 2004.

Referenced fields (TCOR14)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T11 1 Method of diagnosis TMETHDIAG
T12.YEAR 4 First 4 digits of Date of diagnosis (year of date of diagnosis) Not applicable

Business rules

For Add and Update Tumour records
  • Method of diagnosis must only be reported when Date of diagnosis is prior 2004.
Edit logic (TCOR14)
Sub–edit Conditions Outcome
TCOR14-1 T5 IN [‘1', ‘2'] AND T12.YEAR < 2004 AND T11 = ‘0' Record rejected
TCOR14-2 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2004 AND T11 <> ‘0' Record rejected
Feedback report messages (TCOR14)
Sub–edit Text Type
TCOR14-1 Method of diagnosis must be reported for tumours diagnosed before 2004. Core error
TCOR14-2 Method of diagnosis must be coded ‘Not reported' for tumours diagnosed in 2004 and onwards. Core error
Revision (TCOR14)
Year Description
2004 Edit Added: New edit.

TCOR15

Purpose

This edit ensures that method used to establish the date of diagnosis is only reported for tumours diagnosed in 2004 and onwards.

Referenced fields (TCOR15)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of Date of diagnosis (year of date of diagnosis) Not applicable
T24 1 Method used to establish the date of diagnosis TMETHUSED

Business rules

For Add and Update Tumour records
  • Method used to establish the date of diagnosis must only be reported when Date of diagnosis is in 2004 or after.
Edit logic (TCOR15)
Sub–edit Conditions Outcome
TCOR15-1 T5 IN [‘1', ‘2'] AND T12.YEAR < 2004 AND T24<> ‘0' Record rejected
TCOR15-2 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2004 AND T24 = ‘0' Record rejected
Feedback report messages (TCOR15)
Sub–edit Text Type
TCOR15-1 Method used to establish the date of diagnosis must be coded 'Not reported' for tumours diagnosed before 2004. Core error
TCOR15-2 Method used to establish the date of diagnosis must be reported for tumours diagnosed in 2004 and onwards. Core error
Revision (TCOR15)
Year Description
2004 Edit Added: New edit.

TCOR16

Purpose

This edit ensures that diagnostic confirmation is only reported for tumours diagnosed in 2004 and onwards.

Referenced fields (TCOR16)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of Date of diagnosis (year of date of diagnosis) Not applicable
T25 1 Diagnostic confirmation TMETHCONF

Business rules

For Add and Update Tumour records
  • Diagnostic confirmation must only be reported when Date of diagnosis is in 2004 or after.
Edit logic (TCOR16)
Sub–edit Conditions Outcome
TCOR16-1 T5 IN [‘1', ‘2'] AND T12.YEAR < 2004 AND T25<> ‘0' Record rejected
TCOR16-2 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2004 AND T25 = ‘0' Record rejected
Feddback report messages (TCOR16)
Sub–edit Text Type
TCOR16-1 Diagnostic confirmation must be coded ‘Not reported' for tumours diagnosed before 2004. Core error
TCOR16-2 Diagnostic confirmation must be reported for tumours diagnosed in 2004 and onwards. Core error
Revision (TCOR16)
Year Description
2004 Edit Added: New edit.

TCOR17

Purpose

This edit ensures that grade, differentiation or cell indicator is only reported for tumours diagnosed in 2004 and onwards.

Referenced fields (TCOR17)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of Date of diagnosis (year of date of diagnosis) Not applicable
T23 1 Grade, differentiation or cell indicator TGRADE

Business rules

For Add and Update Tumour records
  • Grade, differentiation or cell indicator must only be reported when Date of diagnosis is in 2004 or after.
Edit logic (TCOR17)
Sub–edit Conditions Outcome
TCOR17-1 T5 IN [‘1', ‘2'] AND T12.YEAR < 2004 AND T23 <> ‘0' Record rejected
TCOR17-2 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2004 AND T23 = ‘0' Record rejected
Feedback report messages (TCOR17)
Sub–edit Text Type
TCOR17-1 Grade, differentiation or cell indicator must be coded ‘Not reported' for tumours diagnosed before 2004. Core error
TCOR17-2 Grade, differentiation or cell indicator must be reported for tumours diagnosed in 2004 and onwards. Core error
Revision (TCOR17)
Year Description
2004 Edit Added: New edit.

TCOR18

Purpose

This edit ensures that collaborative staging variables are reported for tumours within the CCR collaborative staging scope.

Referenced fields (TCOR18)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T27 3 CS tumour size TCSTSIZE
T28 2 CS extension TCSEXTN
T29 1 CS tumour size/ext eval TCSEVAL
T30 2 CS lymph nodes TCSLNODE
T31 1 CS reg nodes eval TCSRNEVL
T32 2 Regional nodes examined TCSRNEXAM
T33 2 Regional nodes positive TCSRNPOS
T34 2 CS mets at dx TCSMDIAG
T35 1 CS mets eval TCSMEVAL
T36 3 CS site-specific factor 1 TCSSSF1
T37 3 CS site-specific factor 2 TCSSSF2
T38 3 CS site-specific factor 3 TCSSSF3
T39 3 CS site-specific factor 4 TCSSSF4
T40 3 CS site-specific factor 5 TCSSSF5
T41 3 CS site-specific factor 6 TCSSSF6
T52 6 CS Version 1st TCSFVER

Business rules

For Add and Update Tumour records outside the CCR collaborative staging scope48,
  • All Collaborative staging variables must be blank.
For Add and Update Tumour records within the CCR collaborative staging scope,
  • All Collaborative staging variables must be reported.
Edit logic (TCOR18)
Sub–edit Conditions Outcome
TCOR18-1 T5 IN [‘1', ‘2'] AND T12.YEAR < 2004 AND (T27 IS NOT NULL OR T28 IS NOT NULL OR T29 IS NOT NULL OR T30 IS NOT NULL OR T31 IS NOT NULL OR T32 IS NOT NULL OR T33 IS NOT NULL OR T34 IS NOT NULL OR T35 IS NOT NULL OR T36 IS NOT NULL OR T37 IS NOT NULL OR T38 IS NOT NULL OR T39 IS NOT NULL OR T40 IS NOT NULL OR T41 IS NOT NULL OR T52 IS NOT NULL) CS data items are not posted.
TCOR18-2 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2004 AND (T27 IS NULL OR T28 IS NULL OR T29 IS NULL OR T30 IS NULL OR T31 IS NULL OR T32 IS NULL OR T33 IS NULL OR T34 IS NULL OR T35 IS NULL OR T36 IS NULL OR T37 IS NULL OR T38 IS NULL OR T39 IS NULL OR T40 IS NULL OR T41 IS NULL OR T52 IS NULL) CS data items filled with 'R' at posting.
Feedback report messages (TCOR18)
Sub–edit Text Type
TCOR18-1 Collaborative staging data must be left blank for tumours diagnosed prior to 2004. Reported data will not be loaded into CCR. CS fatal error
TCOR18-2 Eligible Collaborative staging site: all Collaborative staging variables must be reported. CS fatal error
Revision (TCOR18)
Year Description
2007 Referenced fields and Edit logic updated: T52 added as a new CS variable
2004 Edit Added: New edit.

TCOR19

Purpose

This edit ensures that AJCC TNM staging variables are reported for tumours within the CCR AJCC TNM staging scope.

Referenced fields (TCOR19)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T42 9 AJCC clinical T TAJCCCLINT
T43 3 AJCC clinical N TAJCCCLINN
T44 3 AJCC clinical M TAJCCCLINM
T45 9 AJCC pathologic T TAJCCPATHT
T46 3 AJCC pathologic N TAJCCPATHN
T47 3 AJCC pathologic M TAJCCPATHM
T48 4 AJCC clinical TNM stage group TAJCCCLINSG
T49 4 AJCC pathologic TNM stage group TAJCCPATHSG
T50 4 AJCC TNM stage group TAJCCSG
T51 2 AJCC edition number TAJCCEDNUM

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • All AJCC TNM staging variables must be reported.
For Add and Update Tumour records outside the CCR AJCC TNM staging scope
  • All AJCC TNM staging variables must be blank.

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Edit logic (TCOR19)
Sub–edit Conditions Outcome
TCOR19-1 T5 IN [‘1', ‘2'] AND T12.YEAR < 2003 AND NOT (T42 IS NULL AND T43 IS NULL AND T44 IS NULL AND T45 IS NULL AND T46 IS NULL AND T47 IS NULL AND T48 IS NULL AND T49 IS NULL AND T50 IS NULL AND T51 IS NULL) AJCC TNM data items are not posted.
TCOR19-2 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND (T42 IS NULL OR T43 IS NULL OR T44 IS NULL OR T45 IS NULL OR T46 IS NULL OR T47 IS NULL OR T48 IS NULL OR T49 IS NULL OR T50 IS NULL OR T51 IS NULL) AJCC TNM data items filled with 'R' at posting.
TCOR19-3 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND NOT (T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X]) AND NOT (T42 IS NULL AND T43 IS NULL AND T44 IS NULL AND T45 IS NULL AND T46 IS NULL AND T47 IS NULL AND T48 IS NULL AND T49 IS NULL AND T50 IS NULL AND T51 IS NULL) AJCC TNM data items are not posted.
Feedback report messages (TCOR19)
Sub–edit Text Type
TCOR19-1 All AJCC TNM staging data must be blank for tumours diagnosed prior to 2003. Reported data will not be loaded into CCR. AJCC TNM fatal error
TCOR19-2 Eligible AJCC TNM staging site: all AJCC TNM staging variables must be reported. AJCC TNM fatal error
TCOR19-3 Non-eligible AJCC TNM staging site: all AJCC TNM staging variables must be blank. Reported data will not be loaded into CCR. AJCC TNM fatal error
Revision (TCOR19)
Year Description
2004 Edit Added: New edit.

TCOR20

Purpose

This edit ensures that TNM stage group is reported only when clinical and pathologic TNM stage group are not reported.

Referenced fields (TCOR20)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T48 4 AJCC clinical TNM stage group TAJCCCLINSG
T49 4 AJCC pathologic TNM stage group TAJCCPATHSG
T50 4 AJCC TNM stage group TAJCCSG

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • AJCC TNM stage group can only be reported when both AJCC clinical TNM stage group and AJCC pathologic TNM stage group are either unknown or not assessed.

To simplify the edit logic, let Site X be a given site within the AJCC TNM Staging. Ex:Colorectal, breast or prostate.

Edit logic (TCOR20)
Sub–edit Conditions Outcome
TCOR20-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T50 <> ‘99' AND (T48 NOT IN [‘99', ‘X'] OR T49 NOT IN [‘99', ‘X']) AJCC TNM data items filled with 'R' at posting.
Feedback report messasges (TCOR20)
Sub–edit Text Type
TCOR20-1 TNM stage group cannot be reported when clinical and/or pathologic TNM stage group is reported. AJCC TNM error
Revision (TCOR20)
Year Description
2004 Edit Added: New edit.

TCOR21

Purpose

This edit ensures that the combination of AJCC Clinical TNM stage group and the individual clinical T, N, M values combination is acceptable.

Referenced fields (TCOR21)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T42 9 AJCC clinical T TAJCCCLINT
T43 3 AJCC clinical N TAJCCCLINN
T44 3 AJCC clinical M TAJCCCLINM
T48 4 AJCC clinical TNM stage group TAJCCCLINSG

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • If AJCC clinical TNM stage group is known and assessed then AJCC clinical T, N, M and AJCC clinical TNM stage group combination must be valid for the site49.
  • If AJCC clinical TNM stage group is not assessed then AJCC clinical T, N and M combination must not lead to a stage group for the site
  • If AJCC clinical TNM stage group is unknown then all AJCC clinical T, N and M values must also be unknown and conversely.

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Edit logic (TCOR21)
Sub–edit Conditions Outcome
TCOR21-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND NOT (T42 = ‘99' AND T43 = ‘99' AND T44 = ‘99') AND T48 NOT IN [‘99', ‘X'] AND T42, T43, T44, T48 NOT IN [valid AJCC TNM and stage group combination for Site X] AJCC TNM data items filled with 'R' at posting.
TCOR21-2 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T48 = ‘X' AND T42, T43, T44 IN [valid AJCC TNM and stage group combination for Site X] AJCC TNM data items filled with 'R' at posting.
TCOR21-3 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T48 = ‘99' AND (T42 <> ‘99' OR T43 <> ‘99' OR T44 <> ‘99') AJCC TNM data items filled with 'R' at posting.
TCOR21-4 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T48 <> ‘99' AND T42 = ‘99' AND T43 = ‘99' AND T44 = ‘99' AJCC TNM data items filled with 'R' at posting.
Feedback report messages (TCOR21)
Sub–edit Text Type
TCOR21-1 AJCC clinical TNM stage group is invalid for reported AJCC clinical T, N and M values and site. AJCC TNM error
TCOR21-2 AJCC clinical TNM stage group must be assessed for reported clinical T, N and M values and site. AJCC TNM error
TCOR21-3 All AJCC clinical T, N and M values must be set to ‘Unknown' when AJCC clinical TNM stage group is ‘Unknown'. AJCC TNM error
TCOR21-4 AJCC clinical TNM stage group must be set to ‘Unknown' when All AJCC clinical T, N and M values are set to ‘Unknown'. AJCC TNM error
Revision (TCOR21)
Year Description
2004 Edit Added: New edit.

TCOR22

Purpose

This edit ensures that the combination of AJCC pathologic TNM stage group and the individualpathologic T, N, M values is acceptable.

Referenced fields (TCOR22)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T45 9 AJCC pathologic T TAJCCPATHT
T46 3 AJCC pathologic N TAJCCPATHN
T47 3 AJCC pathologic M TAJCCPATHM
T49 4 AJCC pathologic TNM stage group TAJCCPATHSG

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29.
  • If AJCC pathologic TNM stage group is known and assessed then AJCC pathologic T, N, M and AJCC pathologic TNM stage group combination must be valid for the site49.
  • If AJCC pathologic TNM stage group is not assessed then AJCC pathologic T, N and M combination must not imply a stage group for the site49.
  • If AJCC pathologic TNM stage group is unknown then all AJCC pathologic T, N and M values must also be unknown and conversely.

To simplify the edit logic, let Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.

Edit logic (TCOR22)
Sub–edit Conditions Outcome
TCOR22-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for SiteX] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND NOT (T45 = ‘99' AND T46 = ‘99' AND T47 = ‘99') AND T49 NOT IN [‘99', ‘X'] AND T45, T46, T47, T49 NOT IN [valid AJCC TNM and stage group combination for Site X] AJCC TNM data items filled with 'R' at posting.
TCOR22-2 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T49 = ‘X' AND T45, T46, T47 IN [valid AJCC TNM and stage group combination for Site X] AJCC TNM data items filled with 'R' at posting.
TCOR22-3 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T49 = ‘99' AND (T45 <> ‘99' OR T46 <> ‘99' OR T47 <> ‘99') AJCC TNM data items filled with 'R' at posting.
TCOR22-4 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T49 <> ‘99' AND T45 = ‘99' AND T46 = ‘99' AND T47 = ‘99' AJCC TNM data items filled with 'R' at posting.
Feedback report messages (TCOR22)
Sub–edit Text Type
TCOR22-1 AJCC pathologic TNM stage group is invalid for reported AJCC pathologic T, N and M values and site. AJCC TNM error
TCOR22-2 AJCC pathologic TNM stage group must be assessed for reported pathologic T, N and M values and site. AJCC TNM error
TCOR22-3 All AJCC pathologic T, N and M values must be set to ‘Unknown' when AJCC pathologic TNM stage group is ‘Unknown'. AJCC TNM error
TCOR22-4 AJCC pathologic TNM stage group must be set to ‘Unknown' when All AJCC pathologic T, N and M values are set to ‘Unknown'. AJCC TNM error
Revision (TCOR22)
Year Description
2004 Edit Added: New edit.

TCOR23

Purpose

This edit ensures that the combination of AJCC TNM stage group and the individual clinical/pathologic T, N, M values is acceptable.

Referenced fields(TCOR23)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T42 9 AJCC clinical T TAJCCCLINT
T43 3 AJCC clinical N TAJCCCLINN
T44 3 AJCC clinical M TAJCCCLINM
T45 9 AJCC pathologic T TAJCCPATHT
T46 3 AJCC pathologic N TAJCCPATHN
T47 3 AJCC pathologic M TAJCCPATHM
T50 4 AJCC TNM stage group TAJCCSG

Business rules

For Add and Update Tumour records within the CCR AJCC TNM staging scope29,
  • If AJCC TNM stage group is known then the most "accurate" combination of known and assessed AJCC clinical/pathologic T, N, M values and AJCC TNM stage group must be valid49,50. For any staging element (T, N, M), pathologic values are always considered more "accurate" when both clinical and pathologic values are known and assessed.
  • Example If cT = ‘T2' and pT = ‘T1', the most accurate tumour stage is ‘T1' (pathologic data take precedence over clinical).
  • Example If cM = ‘M1' and pM = ‘MX', the most accurate metastases stage is ‘M1' (pathologic M is not assessed).

To simplify the edit logic, let:

  • BestT (clin, path), BestN (clin, path) and BestM (clin, path) be functions that return the most "accurate" tumour, node and metastases staging value based on the rules stated above. When both clinical and pathologic values are '99', 'TX', 'NX' or 'MX', these functions always return the pathologic value.
  • Site X be a given site within the CCR AJCC TNM staging scope. Example: Colorectal, breast or prostate.
Edit logic (TCOR23)
Sub–edit Conditions Outcome
TCOR23-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND T15 IN [Eligible ICD-O-3 – Topography codes for Site X] AND T21 IN [Eligible ICD-O-3 – Histology codes for Site X] AND T22 IN [Eligible ICD-O-3 Behaviour codes for Site X] AND T50 <> '99' AND ((BestT (T42, T45) NOT IN [‘99', ‘X'] AND BestN (T43, T46) IN [‘99', ‘X'] AND BestM (T44, T47) IN [‘99', ‘X'] AND BestT(T42, T45), T50 NOT IN [valid AJCC TNM and stage group combination for Site X]) OR (BestT (T42, T45) IN [‘99', ‘X'] AND BestN (T43, T46) NOT IN [‘99', ‘X'] AND BestM (T44, T47) IN [‘99', ‘X'] AND BestN (T43, T46), T50 NOT IN [valid AJCC TNM and stage group combination for Site X]) OR (BestT (T42, T45) IN [‘99', ‘X'] AND BestN (T43, T46) IN [‘99', ‘X'] AND BestM (T44, T47) NOT IN [‘99', ‘X'] AND BestM (T44, T47), T50 NOT IN [valid AJCC TNM and stage group combination for Site X]) OR (BestT (T42, T45) NOT IN [‘99', ‘X'] AND BestN (T43, T46) NOT IN [‘99', ‘X'] AND BestM (T44, T47) IN [‘99', ‘X'] AND BestT (T42, T45), BestN (T43, T46), T50 NOT IN [valid AJCC TNM and stage group combination for Site X]) OR (BestT (T42, T45) IN [‘99', ‘X'] AND BestN (T43, T46) NOT IN [‘99', ‘X'] AND BestM (T44, T47) NOT IN [‘99', ‘X'] AND BestN (T43, T46), BestM (T44, T47), T50 NOT IN [valid AJCC TNM and stage group combination for Site X]) OR ((BestT (T42, T45) NOT IN [‘99', ‘X'] AND BestN (T43, T46) IN [‘99', ‘X'] AND BestM (T44, T47) NOT IN [‘99', ‘X'] AND BestT(T42, T45), BestM (T44, T47), T50 NOT IN [valid AJCC TNM and stage group combination for Site X]) OR (BestT (T42, T45) NOT IN [‘99', ‘X'] AND BestN (T43, T46) NOT IN [‘99', ‘X'] AND BestM (T44, T47) NOT IN [‘99', ‘X'] AND BestT(T42, T45), BestN (T43, T46), BestM (T44, T47), T50 NOT IN [valid AJCC TNM and stage group combination for Site X])) AJCC TNM data items filled with 'R' at posting.
Feedback report messages (TCOR23)
Sub–edit Text Type
TCOR23-1 AJCC TNM stage group is invalid for reported clinical/pathologic T, N and M values and site. AJCC TNM error
Revision (TCOR23)
Year Description
2004 Edit Added: New edit.

TCOR24

Purpose

This edit ensures that AJCC edition number is coherent with all remaining AJCC TNM staging variables.

Referenced fields (TCOR24)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T15 4 ICD-O-2/3 Topography TICD_O2T
T21 4 ICD-O-3 Histology TICD_O3H
T22 1 ICD-O-3 Behaviour TICD_O3B
T42 9 AJCC clinical T TAJCCCLINT
T43 3 AJCC clinical N TAJCCCLINN
T44 3 AJCC clinical M TAJCCCLINM
T45 9 AJCC pathologic T TAJCCPATHT
T46 3 AJCC pathologic N TAJCCPATHN
T47 3 AJCC pathologic M TAJCCPATHM
T48 4 AJCC clinical TNM stage group TAJCCCLINSG
T49 4 AJCC pathologic TNM stage group TAJCCPATHSG
T50 4 AJCC TNM stage group TAJCCSG
T51 2 AJCC edition number TAJCCEDNUM

Business rules

For Add and Update Tumour records with the CCR AJCC TNM staging scope29.
  • If AJCC edition number is set to ‘Not staged' then all other AJCC TNM staging variables must be set to ‘Unknown' and conversely.
Edit logic (TCOR24)
Sub–edit Conditions Outcome
TCOR24-1 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND ((T15 IN [Eligible ICD-O-3 – Topography codes for AJCC TNM Staging Colorectal sites] AND T21 IN [Eligible ICD-O-3 – Histology codes for AJCC TNM Staging Colorectal sites] AND T22 IN [Eligible ICD-O-3 Behaviour codes for AJCC TNM Staging Colorectal sites]) OR (T15 IN [Eligible ICD-O-3 – Topography codes for AJCC TNM Staging Breast sites] AND T21 IN [Eligible ICD-O-3 – Histology codes for AJCC TNM Staging Breast sites] AND T22 IN [Eligible ICD-O-3 – Behaviour codes for AJCC TNM Staging Breast sites]) OR (T15 IN [Eligible ICD-O-3 – Topography codes for AJCC TNM Staging Prostate sites] AND T21 IN [Eligible ICD-O-3 – Histology codes for AJCC TNM Staging Prostate sites] AND T22 IN [Eligible ICD-O-3 – Behaviour codes for AJCC TNM Staging Prostate sites])) AND T42 = ‘99' AND T43 = ‘99' AND T44 = ‘99' AND T45 = ‘99' AND T46 = ‘99' AND T47 = ‘99' AND T48 = ‘99' AND T49 = ‘99' AND T50 = ‘99' AND T51 <> ‘00' AJCC TNM data items filled with 'R' at posting.
TCOR24-2 T5 IN [‘1', ‘2'] AND T12.YEAR >= 2003 AND ((T15 IN [Eligible ICD-O-3 – Topography codes for AJCC TNM Staging Colorectal sites] AND T21 IN [Eligible ICD-O-3 – Histology codes for AJCC TNM Staging Colorectal sites] AND T22 IN [Eligible ICD-O-3 Behaviour codes for AJCC TNM Staging Colorectal sites]) OR (T15 IN [Eligible ICD-O-3 – Topography codes for AJCC TNM Staging Breast sites] AND T21 IN [Eligible ICD-O-3 – Histology codes for AJCC TNM Staging Breast sites] AND T22 IN [Eligible ICD-O-3 – Behaviour codes for AJCC TNM Staging Breast sites]) OR (T15 IN [Eligible ICD-O-3 – Topography codes for AJCC TNM Staging Prostate sites] AND T21 IN [Eligible ICD-O-3 – Histology codes for AJCC TNM Staging Prostate sites] AND T22 IN [Eligible ICD-O-3 – Behaviour codes for AJCC TNM Staging Prostate sites])) AND T51 = ‘00' AND (T42 <> ‘99' OR T43 <> ‘99' OR T44 <> ‘99' OR T45 <> ‘99' OR T46 <> ‘99' OR T47 <> ‘99' OR T48 <> ‘99' OR T49 <> ‘99' OR T50 <> ‘99') All AJCC TNM data items filled with 'R' at posting.
Feedback report messages (TCOR24)
Sub–edit Text Type
TCOR24-1 TNM edition number must be set to ‘Not Staged' when all other AJCC TNM staging variables are ‘Unknown'. AJCC TNM error
TCOR24-2 TNM edition number cannot be set to ‘Not Staged' when some AJCC TNM staging variables are reported. AJCC TNM error
Revision (TCOR24)
Year Description
2004 Edit Added: New edit.

TCOR26

Purpose

This edit ensures the consistency between Ambiguous terminology diagnosis and Date of conclusive diagnosis.

Referenced fields (TCOR26)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T53 1 Ambiguous terminology diagnosis TDATCONCLUSDIAG
T54 8 Date of conclusive diagnosis TMULTCOUNT

Business rules

For Add and Update Tumour records
  • If Date of Diagnosis is before 2008 then Ambiguous terminology diagnosis and Date of conclusive diagnosis must both be blank.
  • If Date of Diagnosis is 2008 and onwards then Ambiguous terminology diagnosis and Date of conclusive diagnosis must be either both blank or both reported.
Edit logic (TCOR26)
Sub–edit Conditions Outcome
TCOR26-1 T5 IN [‘1','2'] AND T12.YEAR < 2008 AND (T53 IS NOT NULL OR T54 IS NOT NULL) Record rejected
TCOR26-2 T5 IN [‘1','2'] AND T12.YEAR >= 2008 AND (T53 IS NOT NULL OR T54 IS NOT NULL) AND (T53 IS NULL OR T54 IS NULL) Record rejected
Feedback report messages (TCOR26)
Sub–edit Text Type
TCOR26-1 Ambiguous terminology diagnosis and Date of conclusive diagnosis must both be blank if Date of diagnosis is before 2008. Core error
TCOR26-2 If Date of diagnosis is 2008 and onwards, Ambiguous terminology diagnosis and Date of conclusive diagnosis must either both be reported or both be left blank. Core error
Revision (TCOR26)
Year Description
2008 Edit added: New edit.

TCOR27

Purpose

This edit ensures the consistency between Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter.

Referenced fields (TCOR27)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12.YEAR 5 First 4 digits of T12 (year of date of diagnosis) Not applicable
T55 2 Type of multiple tumours reported as one primary TMULTTUMONEPRIM
T56 8 Date of multiple tumours DDATMULT
T57 2 Multiplicity counter TMULTCOUNT

Business rules

For Add and Update Tumour records
  • If Date of Diagnosis is before 2008 then Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter must all be blank.
  • If Date of Diagnosis is 2008 and onwards then Type of multiple tumours reported as one primary, Date of multiple tumours, and Multiplicity counter must be either all blank or all reported.
Edit logic (TCOR27)
Sub–edit Conditions Outcome
TCOR27-1 T5 IN [‘1','2'] AND T12.YEAR < 2008 AND (T55 IS NOT NULL OR T56 IS NOT NULL OR T57 IS NOT NULL) Record rejected
TCOR27-2 T5 IN [‘1','2'] AND T12.YEAR >= 2008 AND (T55 IS NOT NULL OR T56 IS NOT NULL OR T57 IS NOT NULL) AND (T55 IS NULL OR T56 IS NULL OR T57 IS NULL) Record rejected
Feedback report messages (TCOR27)
Sub–edit Text Type
TCOR27-1 Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter must all be blank if Date of diagnosis is before 2008. Core error
TCOR27-2 Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter must either all be blank or all be reported if Date of diagnosis is 2008 and onwards. Core error
Revision (TCOR27)
Year Description
2008 Edit added: New edit.

TCOR29

Purpose

This edit ensures the consistency between Ambiguous terminology diagnosis and Date of conclusive diagnosis.

Referenced fields (TCOR29)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T53 1 Ambiguous terminology diagnosis TAMBIGTERM
T54 8 Date of multiple tumours DDATMULT

Business rules

For Add and Update Tumour records
  • If Ambiguous terminology diagnosis is "Conclusive terminology within 60 days of original diagnosis" (0) then Date of conclusive diagnosis must be "Not applicable" (88888888).
  • If Ambiguous terminology diagnosis is "Ambiguous terminology only" (1) then Date of conclusive diagnosis must be "Accessioned based on ambiguous terminology diagnosis only" (00000000).
  • If Ambiguous terminology diagnosis is "Ambiguous terminology followed by conclusive terminology" (2) then Date of conclusive diagnosis must NOT be "Not applicable" (88888888) or "Accessioned based on ambiguous terminology diagnosis only" (00000000).
  • If Ambiguous terminology diagnosis is "Unknown terminology" (9) then Date of conclusive diagnosis must indicate that date is unknown (99999999).
  • If Ambiguous terminology diagnosis is "Ambiguous terminology followed by conclusive terminology" (2) then Date of conclusive diagnosis should NOT be unknown (99999999).
Edit logic (TCOR29)
Sub–edit Conditions Outcome
TCOR29-1 T5 IN [‘1','2'] AND (T53 = ‘0' AND T54 <> ‘88888888') OR (T53 = ‘1' AND T54 <> ‘00000000') OR (T53 = ‘2' AND T54 IN [‘00000000', ‘88888888']) OR (T53 = ‘9' AND T54 <> ‘99999999') Record rejected
TCOR29-2 T5 IN [‘1', '2'] AND T53 IN [‘2'] AND T54 IN [‘99999999'] Warning
Feedback report messages (TCOR29)
Sub–edit Text Type
TCOR29-1 Ambiguous terminology diagnosis and Date of conclusive diagnosis are inconsistent. Core error
TCOR29-2 Date of conclusive diagnosis should be a valid calendar date when case is identified as "Ambiguous terminology followed by conclusive terminology". Warning
Revision (TCOR29)
Year Description
2008 Edit added: New edit.

TCOR30

Purpose

This edit ensures that date of diagnosis and date of conclusive diagnosis respect a chronological sequence and time frame.

Referenced fields (TCOR30)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T12 8 Date of diagnosis TDATDIAG
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T12.MONTH 2 5th and 6th digits of T12 (month of date of diagnosis) Not applicable
T12.DAY 2 Last 2 digits of T12 (day of date of diagnosis) Not applicable
T54 8 Date of Conclusive Diagnosis TDATCONCLUSDIAG
T54.YEAR 4 First 4 digits of T54 (year of date of conclusive diagnosis) Not applicable
T54.MONTH 2 5th and 6th digits of T54 (month of date of conclusive diagnosis) Not applicable
T54.DAY 2 Last 2 digits of T54 (day of date of conclusive diagnosis) Not applicable

Business rules

For Add and Update Tumour records
  • Date of conclusive diagnosis must be greater than two months (60 days) after the Date of diagnosis.
Edit logic (TCOR30)
Sub–edit Conditions Outcome
TCOR30-1 T5 IN [‘1', ‘2'] AND T54 NOT IN [‘00000000','88888888', ‘99999999'] AND ((T12.DAY <> ‘99' AND T54.DAY <> ‘99' AND T54 < T12) OR (T12.MONTH <> ‘99' AND T54.MONTH <> ‘99' AND T54.YEAR || T54.MONTH < T12.YEAR || T12.MONTH) OR (T54.YEAR < T12.YEAR)) Record rejected
TCOR30-2 T5 IN [‘1', ‘2'] AND T54 NOT IN [‘00000000','88888888', ‘99999999'] and DIFF_DAYS (Date1,Date2) <= 60. See Appendix J – Interval between 2 dates (complete or partial). Record rejected
TCOR30-3 T5 IN [‘1', ‘2'] AND T12.YEAR = T54.YEAR AND T12.MONTH = ‘99' AND T54.MONTH = ‘99' Record rejected
Feedback report messages (TCOR30)
Sub–edit Text Type
TCOR30-1 Date of conclusive diagnosis is before date of diagnosis. Core error
TCOR30-2 Date of conclusive diagnosis must be greater than 60 days after the date of diagnosis. Core error
TCOR30-3 If the year of Date of diagnosis is equal to the year of Date of conclusive diagnosis and both months are unknown, the Date of conclusive diagnosis must be unknown. Core error
Revision (TCOR30)
Year Description
2008 Edit added: New edit.

TCOR31

Purpose

This edit ensures the consistency between ICD-O-2/3 Topography and Type of multiple tumours reported as one primary.

Referenced fields (TCOR31)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T15 5 ICD-O-2/3 Topography TICD_02T
T55 2 Type of multiple tumours reported as one primary TMULTTUMONEPRIM

Business rules

For Add and Update Tumour records
  • If Type of multiple tumours reported as one primary is coded as "polyp and adenocarcinoma" (31) or "Familial Adenomatous Polyposis (FAP) with carcinoma" (32) Then ICD-O-2/3 Topography must be coded as "Colon" (C180-C189), "Rectosigmoid Junction" (C199) or "Rectum" (C209).
Edit logic (TCOR31)
Sub–edit Conditions Outcome
TCOR31-1 T5 IN [‘1', ‘2'] AND T55 IN [31,32] and T15 NOT IN [C180-C189, C199 or C209] Record rejected
Feedback report messages (TCOR31)
Sub–edit Text Type
TCOR31-1 Type of multiple tumours reported as one primary and ICD-O-2/3 combination is invalid. Core error
Revision (TCOR31)
Year Description
2008 Edit added: New edit.

TCOR32

Purpose

This edit ensures the consistency between ICD-O-3 Behaviour and Type of multiple tumours reported as one primary.

Referenced fields (TCOR32)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T22 1 ICD-O-3 Behaviour TICD_03B
T55 2 Type of multiple tumours reported as one primary TMULTTUMONEPRIM

Business rules

For Add and Update Tumour records
  • If Type of multiple tumours reported as one primary is coded as either "Multiple benign (intracranial and CNS sites only)" (10), "Multiple borderline" (11), or "Benign (intracranial and CNS sites only) and borderline" (12), then ICD-O-3 Behaviour must be coded as either "benign" (0) or "borderline" (1).
Edit logic (TCOR32)
Sub–edit Conditions Outcome
TCOR32-1 T5 IN [‘1', ‘2'] AND T55 IN [‘10', '11', '12'] AND T22 NOT IN [‘0','1'] Record rejected
Feedback report messages (TCOR32)
Sub–edit Text Type
TCOR32-1 Type of multiple tumours reported as one primary and ICD-O-3 behaviour combination is invalid. Core error
Revision (TCOR32)
Year Description
2008 Edit added: New edit.

TCOR33

Purpose

This edit ensures the consistency between Type of multiple tumours reported as one primary, Date of multiple tumours, Multiplicity counter, ICD-O-2/3 Topography and ICD-O-3 Histology.

Referenced fields (TCOR33)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T15 4 ICD–O–2/3 Topography TICD_O2T
T21 4 ICD–O–3 Histology TICD_O3H
T24 1 Method used to establish the date of diagnosis TMETHUSED
T55 2 Type of multiple tumours reported as one primary TMULTTUMONEPRIM
T56 8 Date of multiple tumours DDATMULT
T57 2 Multiplicity counter TMULTCOUNT

Business rules

For Add and Update Tumour records where method used to establish the date of diagnosis is not ‘death certificate only"
  • If ICD–O–2/3 topography is ‘unknown primary' (C809) or ICD–O– 3 Histology refers to lymphoma, leukemia or immunoproliferative disease62 [9590-9989] then Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter must be ‘Information on multiple tumours not applicable for this site'.
  • If ICD-O-2/3 topography is known (not C809) and ICD–O–3 Histology does NOT refer to lymphoma, leukemia or immunoproliferative disease [9590-9989] then Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter must not be ‘Information on multiple tumours not applicable for this site'.
Edit logic (TCOR33)
Sub–edit Conditions Outcome
TCOR33-1 T5 IN [‘1','2'] AND T24 <> 8 AND (T15 = ‘C809' OR T21 IN [9590-9989]) AND T55 <> 88 OR T56 <> ‘88888888' OR T57 <> ‘88' Record rejected
TCOR33-2 T5 IN [‘1','2'] AND T24 <> 8 AND (T15 <> ‘C809' OR T21 NOT IN [9590-9989]) AND T55 = ‘88' OR T56 = ‘88888888' OR T57 = ‘88' Record rejected
Feedback report messages (TCOR33)
Sub–edit Text Type
TCOR33-1 Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter must be reported as ‘Information on multiple tumours not applicable for this site'. Core error
TCOR33-2 Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter must NOT be reported as ‘Information on multiple tumours not applicable for this site'. Core error
Revision (TCOR33)
Year Description
2008 Edit added: New edit.

TCOR34

Purpose

This edit ensures the consistency between Date of multiple tumours and Type of multiple tumours reported as one primary.

Referenced fields (TCOR34)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T55 2 Type of multiple tumours reported as one primary TMULTTUMONEPRIM
T56 8 Date of multiple tumours DDATMULT
T57 2 Multiplicity counter TMULTCOUNT

Business rules

For Add and Update Tumour records
  • If Type of multiple tumours reported as one primary is "single tumour" (00) then  Date of multiple tumours  must be "single tumour" (00000000) and Multiplicity counter must be ‘01'.
  • If Type of multiple tumours reported as one primary is "not applicable for this site" (88) then Date of multiple tumours must be "information on multiple tumours not applicable for this site" (88888888) and Multiplicity counter must be ‘Information on multiple tumours not applicable for this site' (88).
  • If Type of multiple tumours reported as one primary indicates multiple tumours (codes 10 through 80) then Date of multiple tumours must be the date the patient is diagnosed with multiple tumours or unknown (99999999) and Multiplicity counter must be values 02 through 87.
  • If Type of multiple tumours reported as one primary is "Unknown" (99) then Date of multiple tumours must be unknown (99999999) and Multiplicity counter must be "Multiple tumours present, unknown how many; unknown if single or multiple tumours" (99).
Edit logic (TCOR34)
Sub–edit Conditions Outcome
TCOR34-1 T5 IN [‘1','2'] AND (T55 = ‘00' AND T56 <> ‘00000000' OR T57 <> ‘01') OR (T55 = ‘88' AND T56 <> ‘88888888' OR T57 <> 88' ) OR (T55 = ‘99' AND T56 <> ‘99999999' OR T57 <> ‘99') OR (T55 IN [‘10','11','12','20','30','31','32','40','80'] AND (T56 = ‘00000000' OR T56 = ‘88888888') OR (T57 = ‘01' OR T57 = ‘88' OR T57 = ‘99') Record rejected
Feedback report messages (TCOR34)
Sub–edit Text Type
TCOR34-1 Type of multiple tumours reported as one primary, date of multiple tumours and multiplicity counter combination is invalid. Core error
Revision (TCOR34)
Year Description
2008 Edit added: New edit.

TCOR35

Purpose

This edit ensures the consistency between Method used to establish the date of diagnosis, Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter..

Referenced fields (TCOR35)
Field Length Description Acronym
T5 1 Tumour record type TRECTYPE
T24 1 Method used to establish the date of diagnosis TMETHUSED
T55 2 Type of multiple tumours reported as one primary TMULTTUMONEPRIM
T56 8 Date of multiple tumours DDATMULT
T57 2 Multiplicity counter TMULTCOUNT

Business rules

For Add and Update Tumour records
  • If Type of multiple tumours reported as one primary is "Unknown" (99) and Method used to establish date of diagnosis is "Death certificate only" (8), then Date of multiple tumours must be "Unknown" (99999999) and Multiplicity counter must be "Multiple tumours present, unknown how many/unknown if single or multiple tumours" (99).
Edit logic (TCOR35)
Sub–edit Conditions Outcome
TCOR35-1 T5 IN [‘1','2'] AND (T55 = ‘99' AND T24 = ‘8') AND (T56 <> ‘99999999' OR T57 <> ‘99') Record rejected
Feedback report messages (TCOR35)
Sub–edit Text Type
TCOR35-1 Method used to establish the date of diagnosis, Type of multiple tumours reported as one primary, Date of multiple tumours and Multiplicity counter combination is invalid. Core error
Revision (TCOR35)
Year Description
2008 Edit added: New edit.

3.6 Match edits

The purpose of the match edits is to enforce the business rules between fields on different records. For ease of use, match edits have been divided into four groups:

  • Key input match edits: Ensure that input patient and tumour records respect the submission rules in terms of matching keys.
  • Key base match edits: Ensure that input patient and tumour records respect the actual state of the CCR in terms of matching keys.
  • Data item match edits: Enforce the business rules between data items (other than keys) found on different records.
  • Pre-posting match edits: Identify core error-free input records that cannot be posted to the CCR4 because some other related Input records are either missing or have core errors.

3.6.1 Key input match edits

The purpose of the key input match edits is to ensure that input patient and tumour records respect the submission rules in terms of matching keys.

At this level, the following fields are used as key:

  • Patient record: Reporting province/territory and patient identification number.
  • Tumour record: Reporting province/territory, patient identification number and tumour reference number.

The following table summarizes the purpose of each individual edit of this category:

Table 28 Input match edits summary
Edit name Purpose
KIM1 Ensures that only one operation affecting a specific patient record is performed (that is, add, delete or update) within a data submission.
KIM2 Ensures that only one operation affecting a specific Tumour record is performed (that is, add, delete or update) within a data submission.
KIM3 Enforces the submission rules regarding the addition of a patient record.
KIM4 Enforces the submission rules regarding the deletion of a patient record.
KIM5 Enforces the submission rules regarding the addition of a Tumour record.

Important note:

When a key input match edit fails, all related Input records (all input patient and tumour records sharing the same reporting province/territory and patient identification number) are rejected. Related records are also called the family of records.

KIM1

Purpose

This edit ensures that only one operation affecting a specific patient record is performed
(add, delete or update) within a data submission.

Referenced fields (KIM1)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN

Business rules

For Input Patient records
  • There cannot be another Input patient record with identical Reporting province/territory and Patient identification number within the same data submission.
Edit logic (KIM1)
Sub–edit Conditions Outcome
KIM1-1 Input patient record that matches another Input patient record where P1=P1 AND P2=P2. Family rejected51
Feedback report messages (KIM1)
Sub–edit Text Type
KIM1-1 Family rejected: more than one Input patient record with the same Patient reporting province/territory and Patient identification number. Core error
Revision (KIM1)
Year Description
2004 Edit renamed: Formerly known as Input Match Edit No.1.

KIM2

Purpose

This edit ensures that only on

Referenced fields (KIM2)
Field Length Description Acronym
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Tumour patient identification number TPIN
T3 9 Tumour reference number TTRN

Business rules

For Input Tumour records
  • There cannot be another Input Tumour record with identical Reporting province/territory, Patient identification number and Tumour reference number within the same data submission.
Edit logic (KIM2)
Sub–edit Conditions Outcome
KIM2-1 Input tumour record that matches another Input tumour record where T1=T1 AND T2=T2 AND T3=T3. Family rejected52
Feedback report messages (KIM2)
Sub–edit Text Type
KIM2-1 Family rejected: more than one Input tumour record with the same Tumour reporting province/territory, Tumour patient identification number and Tumour reference number. Core error
Revision (KIM2)
Year Description
2004 Edit renamed: Formerly known as Input Match Edit No.2.

KIM3

Purpose

This edit enforces the submission rules regarding the addition of a patient record.

Referenced fields (KIM3)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P4 1 Patient record type PRECTYPE
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Tumour patient identification number TPIN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE

Business fields

For Add Patient records
  • There must be at least one Add Tumour record with identical Reporting province/territory and Patient identification number and a blank CCR identification number within the same data submission.
  • There cannot be any Add Tumour record with identical Reporting province/territory and Patient identification number and a reported CCR identification number within the same data submission.
  • There cannot be any Update or Delete Tumour record with identical Reporting province/territory and Patient identification number within the same data submission.
Edit logic KIM3)
Sub–edit Conditions Outcome
KIM3-1 Input patient record where P4='1' that matches no Input tumour record where T5='1' AND T1=P1 AND T2=P2. Family rejected53
KIM3-2 Input patient record where P4='1' that matches an Input tumour record where T5='1' AND T1=P1 AND T2=P2 AND T4 IS NOT NULL. Family rejected53
KIM3-3 Input patient record where P4='1' that matches an Input tumour record where T5 IN ['2','3'] AND T1=P1 AND T2=P2. Family rejected53
Feedback report messages (KIM3)
Sub–edit Text Type
KIM3-1 Family rejected: Add Patient record does not match any Add Tumour record. Core error
KIM3-2 Family rejected: Add Patient record matches an Add Tumour record with CCR identification number. Core error
KIM3-3 Family rejected: Add Patient record matches an Update or Delete Tumour record. Core error
Revision (KIM3)
Year Description
2004 Edit renamed: Formerly known as Input Match Edit No.3.

KIM4

Purpose

This edit enforces the submission rules regarding the deletion of a patient record.

referenced fields (KIM4)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPROV
P2 12 Patient identification number PPIN
P4 1 Patient record type PRECTYPE
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Tumour patient identification number TPIN
T5 1 Tumour record type TRECTYPE

Business rules

For Delete Patient records
  • There must be at least one Delete Tumour record with identical Reporting province/territory and Patient identification number within the same data submission.
  • There cannot be any Add or Update Tumour record with identical Reporting province/territory and Patient identification number within the same data submission.
Edit logic (KIM4)
Sub–edit Conditions Outcome
KIM4-1 Input patient record where P4='3' that matches no Input tumour record where T5='3' AND P1=T1 AND P2=T2. Family rejected53
KIM4-2 Input patient record where P4='3' that matches Input tumour record where T5 IN ['1','2'] AND P1=T1 AND P2=T2. Family rejected53
Feedback report messages (KIM4)
Sub–edit Text Type
KIM4-1 Delete Patient record does not match any Delete Tumour record. Core error
KIM4-2 Family rejected: Delete Patient record matches an Add or Update Tumour record. Core error
Revision (KIM4)
Year Description
2004 Edit renamed: Formerly known as Input Match Edit No.4.
Business rules changed: CCR identification number has been removed from the edit since it is equivalent to Reporting province/territory – Patient identification number combination.

KIM5

Purpose

This edit enforces the submission rules regarding the addition of a tumour record.

Referenced fields (KIM5)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P4 1 Patient record type PRECTYPE
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Tumour patient identification number TPIN
T4 9 CCR Identification number CCR_ID
T5 1 Tumour record type TRECTYPE

Business rules

For Add Tumour records without CCR identification number
  • There must be an Add Patient record with identical Reporting province/territory and Patient identification number within the same data submission.
  • There cannot be any Update54 Patient records with identical Reporting province/territory and Patient identification number within the same data submission.
Edit logic (KIM5)
Sub–edit Conditions Outcome
KIM5-1 Input tumour record where T5='1' AND T4 IS NULL that matches no Input patient record where P4='1' AND P1=T1 AND P2=T2. Family rejected55
KIM5-2 Input tumour record where T5='1' AND T4 IS NULL that matches Input patient record where P4='2' AND P1=T1 AND P2=T2. Family rejected55
Feedback report messages (KIM5)
Sub–edit Text Type
KIM5-1 Family rejected: Add Tumour record without CCR_ID does not match an Add Patient record. Core error
KIM5-2 Family rejected: Add Tumour record without CCR_ID matches an Update Patient record. Core error
Revision (KIM5)
Year Description
2004 Edit renamed: Formerly known as Input Match Edit No.6.

3.6.2 Key base match edits

The purpose of the key base match edits is to ensure that input patient and tumour records respect the actual state of the CCR in terms of matching keys.

At this level, the following fields are used as keys:

  • Patient record: CCR identification number, reporting province/territory and patient identification number.
  • Tumour record: CCR identification number, reporting province/territory, patient identification number and tumour reference number.

The following table summarizes the purpose of each individual edit of this category.

Table 29 Base match edits summary
Edit name Purpose
KBM1 Ensures that no duplicate Patient keys are posted to the CCR.
KBM2 Ensures that Update or Delete Patient record keys match a Base Patient record.
KBM3 Ensures that no duplicate Tumour keys are posted to the CCR.
KBM4 Ensures that an Add Tumour record with CCR identification number matches a Base patient record owned by the Reporting province/territory.
KBM5 Ensures that Update or Delete Tumour record keys match a Base tumour record.

Important note

When a key base match edit fails, the conflicting base record (if any), is included in the detailed feedback report for easier error correction.

Writing conventions throughout the following edit descriptions:

  • Expression "base patient/tumour record" means a patient/tumour record already in the CCR.
  • Expression "add/update/delete/input patient/tumour record" means a patient/tumour record within the data submission.
  • Unless specified otherwise, field numbers prefixed with "I" are input fields and field numbers prefixed with "B" are Base fields. 
    Example: IT5 is the Tumour record type field on an input tumour record.
    Example: IP1 is the Reporting province/territory field on an input patient record

KBM1

Purpose

This edit ensures that no duplicate patient keys are posted to the CCR.

Referenced fields (KBM1)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P4 1 Patient record type PRECTYPE

Business rules

For Add Patient records
  • There must not be a Base patient record with identical Reporting province/territory and Patient identification number.
Edit logic (KBM1)
Sub–edit Conditions Outcome
KBM1-1 Input patient record where IP4='1' that matches a Base patient record where IP1=BP1 AND IP2=BP2. Record rejected
Feedback report messages (KBM1)
Sub–edit Text Type
KBM1-1 A Base patient record with identical reporting province/Territory and Patient identification number already exists. Core error
Revision (KBM1)
Year Description
2004 Edit renamed: Formerly known as Correlation Edit No.25.

KBM2

Purpose

This edit ensures that update or delete patient record keys match a base patient record.

Referenced fields (KBM2)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P3 9 CCR identification number CCR_ID
P4 1 Patient record type PRECTYPE

Business rules

For Update or Delete Patient records
  • There must be a Base patient record with identical Reporting province/territory, Patient identification number and CCR identification number.
Edit logic (KBM2)
Sub–edit Conditions Outcome
KBM2-1 Input patient record where IP4 IN ['2','3'] that matches a Base patient record where IP1=BP1 AND IP2<>BP2 AND IP3=BP3. Record rejected
KBM2-2 Input patient record where IP4 IN ['2','3'] that matches a Base patient record where IP1=BP1 AND IP2=BP2 AND IP3<>BP3. Record rejected
KBM2-3 Input patient record where IP4 IN ['2','3'] that matches a Base patient record where IP1<>BP1 AND IP3=BP3. Record rejected
KBM2-4 Input patient record where IP4 IN ['2','3'] that match no Base patient record where (IP1=BP1 AND IP2=BP2) OR IP3=BP3. Record rejected
Feedback report messages (KBM2)
Sub–edit Text Type
KBM2-1 Based on the CCR identification number, the Patient identification number is incorrect. Core error
KBM2-2 Based on the Reporting province/territory and the Patient identification number, the CCR identification number is incorrect. Core error
KBM2-3 Based on the CCR identification number, the Patient is owned by another province/territory. Core error
KBM2-4 No matching Patient record found in the CCR. Core error
Revision (KBM2)
Year Description
2004 Edit renamed: Formerly known as Correlation Edit No.26.

KBM3

Purpose

This edit ensures that no duplicate tumour keys are posted to the CCR.

Referenced fields (KBM3)
Field Length Description Acronym
T1 2 Tumour reporting province/Territory TREPPROV
T2 12 Tumour patient identification number TPIN
T3 9 Tumour reference number TTRN
T5 1 Tumour record type TRECTYPE

Business rules

For Add Tumour records
  • There must not be a Base tumour record with an identical Reporting province/territory, Patient identification number and Tumour reference number.
Edit logic (KBM3)
Sub–edit Conditions Outcome
KBM3-1 Input tumour record where IT5='1' that matches a Base tumour record where IT1=BT1 AND IT2=BT2 AND IT3=BT3. Record rejected
Feedback report messages (KBM3)
Sub–edit Text Type
KBM3-1 A Base tumour record with identical Reporting province/territory, Patient identification number and Tumour reference number already exists. Core error
Revision (KBM3)
Year Description
2004 Edit renamed: Formerly known as Correlation Edit No.32 – Part 1.

KBM4

Purpose

This edit ensures that an add tumour record with CCR identification number matches a base patient record owned by the reporting province/territory.

Referenced fields (KBM4)
Field Length Description Acronym
T1 2 Tumour reporting province/territory TREPPROV
T2 9 Tumour patient identification number TPIN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
P1 2 Patient reporting province/territory PREPPROV
P2 9 Patient identification number PPIN
P3 9 CCR identification number CCR_ID

Business rules

For Add Tumour records with CCR identification number
  • There must be a Base patient record with the same Reporting province/territory, Patient identification number and CCR identification number.
Edit logic (KBM4)
Sub–edit Conditions Outcome
KBM4-1 Input tumour record where IT5='1' AND IT4 IS NOT NULL that matches a Base patient record where IT1=BP1 AND IT2<>BP2 AND IT4=BP3. Record rejected
KBM4-2 Input tumour record where IT5='1' AND IT4 IS NOT NULL that matches a Base patient record where IT1=BP1 AND IT2=BP2 AND IT4<>BP3. Record rejected
KBM4-3 Input tumour record where IT5='1' AND IT4 IS NOT NULL that matches a Base patient record where IT1<>BP1 AND IT4=BP3. Record rejected
KBM4-4 Input tumour record where IT5='1' AND IT4 IS NOT NULL that matches no Base patient record where (IT1=BP1 AND IT2=BP2) OR IT4=BP3. Record rejected
Feedback report messages (KBM4)
Sub–edit Text Type
KBM4-1 Based on CCR identification number, Patient identification number is incorrect. Core error
KBM4-2 Based on Reporting province/territory and Patient identification number, CCR identification number is incorrect. Core error
KBM4-3 Based on CCR identification number, the Patient record belongs to another province/territory. Core error
KBM4-4 Matching Base patient record not found. Core error
Revision (KBM4)
Year Description
2004 Edit renamed: Formerly known as Correlation Edit No.32 – Part 2 and Additional rules for updating the CCR #3.
Business rules changed: This aggregated edit is now using the Base Patient records.

KBM5

Purpose

This edit ensures that update or delete tumour record keys match a base tumour record.

Referenced fields (KBM5)
Field Length Description Acronym
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Tumour patient identification number TPIN
T3 9 Tumour reference number TTRN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE

Business rules

For Update and Delete Tumour records
  • There must be a Base tumour record with identical Reporting province/territory, Patient identification number, Tumour reference number and CCR identification number.
Edit logic (KBM5)
Sub–edit Conditions Outcome
KBM5-1 Input tumour record where IT5 IN ['2','3'] that matches a Base tumour record where IT1=BT1 AND IT2=BT2 AND IT3=BT3 AND IT4<>BT4. Record rejected
KBM5-2 Input tumour record where IT5 IN ['2','3'] that matches a Base tumour record where IT1=BT1 AND IT2<>BT2 AND IT4=BT4. Record rejected
KBM5-3 Input tumour record where IT5 IN ['2','3'] that matches no Base tumour record where IT1=BT1 AND IT2=BT2 AND IT3=BT3 but matches a Base tumour record where IT1=BT1 AND IT2=BT2 AND IT3<>BT3 AND IT4=BT4. Record rejected
KBM5-4 Input tumour record where IT5 IN ['2','3'] that matches no Base tumour record where (IT1=BT1 AND IT2=BT2) OR (IT1=BT1 AND IT4=BT4). Record rejected
Feedback report messages (KBM5)
Sub–edit Text Type
KBM5-1 Based on Reporting province/territory, Patient identification number and Tumour reference number, CCR identification number is incorrect. Core error
KBM5-2 Based on CCR identification number and Reporting province/territory, Patient identification number is incorrect. Core error
KBM5-3 Matching Base tumour record not found. Tumour reference number may be incorrect. Core error
KBM5-4 Matching Base tumour record not found. Core error
Revision (KBM5)
Year Description
2004 Edit renamed: Formerly known as Correlation Edit No.33.

3.6.3 Data item match edits

The purpose of the data item match edits is to enforce the business rules between data items (other than keys) found on different records.

The following table summarizes the purpose of each individual edit of this category.

Table 30 Data item match edits summary
Edit name Purpose
DIM1 Ensures that Date of diagnosis and Date of birth are coherent and within time frame.
DIM2 Ensures that Date of diagnosis and Date of death are coherent.
DIM3 Ensures that Method of diagnosis accurately reflects the relationship between Date of diagnosis and Date of death.
DIM4 Ensures that Method used to establish the date of diagnosis accurately reflects the relationship between Date of diagnosis and Date of death.
DIM5 Ensures that patient Sex and tumour Topography are coherent.
DIM6 Ensures that no "duplicate" tumour records are created for any given Patient record.

Important notes:

Writing conventions throughout the following edit descriptions:

  • Expression "base patient/tumour record" means a patient/tumour record already in the CCR.
  • Expression "add/update/delete/input patient/tumour record" means a patient/tumour record within the data submission.
  • Unless specified otherwise, field numbers prefixed with "I" are input fields and field numbers prefixed with "B" are Base fields.
    Example: IT5 is the Tumour record type field on an input tumour record.
    Example: IP1 is the Reporting province/territory field on an input patient record

These edits only consider input records that have neither core fatal errors nor core errors. (See section 3.1.7 Message types for information about different types of errors.) Since DIM edits find core errors, an input record that fails a given DIM edit will automatically be excluded from all subsequent DIM edits.

These edits must be performed in a specific order (see below).

When a data item match edit fails, the conflicting base record (patient or tumour, if any) is included in the detailed feedback report for easier error correction.

3.6.3.1 Special order of execution

Data item match edits must be performed horizontally. That is, all sub-edits with the same number must be processed together. Example: instead of processing all sub-edits from DIM1 before processing all sub-edits from DIM2 (vertically), all sub-edits DIMX-1 must be processed before processing sub-edits DIMX-2 (horizontally). Although the sub-edits within a horizontal group can be processed in any order, these groups of sub-edits must be processed in a very specific order.

Step 1: All sub-edits that consider only input records (Sub-edits number 1 and 4).

Step 2: All sub-edits that consider base patient records that are not updated by input patient records (Sub-edits number 2 and 5).

Step 3: All sub-edits that consider base tumour records that are not updated nor deleted by input tumour records must be processed (Sub-edit number 3 and 6).

The ordering is essential to guarantee the effectiveness of these edits since each step builds the necessary conditions for the next one. The following table summarizes the special order of execution.

Table 31 Data item match edits special order of execution
Edit DIM1 DIM2 DIM3 DIM4 DIM5 DIM6
Sub-edit 1 2 3 4 5 6 1 2 3 1 2 3 4 5 6 1 2 3 4 5 6 1 2 3 1 2 3 4 5 6
Step 1 x     x     x     x     x     x     x     x     x     x    
Step 2   x     x     x     x     x     x     x     x     -     -  
Step 3     x     x     x     x     x     x     x     x     x     x

DIM1

Purpose

This edit ensures that date of diagnosis and date of birth are coherent and within time frame.

Referenced fields (DIM1)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P3 9 CCR identification number CCR_ID
P4 1 Patient record type PRECTYPE
P11 8 Date of birth PDATBIR
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Patient identification number TPIN
T3 9 Tumour reference number TTRN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
T12 8 Date of diagnosis TDATDIAG

Business rules

Date of diagnosis must be on or after the Date of birth.
  • Year of Date of diagnosis and year of the Date of birth must not be more than 117 yearsapart.

Important notes:

  • These sub-edits must be processed in a specific order. See Section - 3.6.3.1 Special order of execution for more details.
  • Partially known dates must be compared using the highest common level of precision.

    Example: If Date1 = YYYYMMDD and Date2 = YYYYMM99 then dates must be compared using the year and month only. Thus, for the purpose of the following sub-edits, '20031002' and '20031099' are equal.
Edit logic (DIM1)
Sub–edit Conditions Outcome
DIM1-1 Core error-free56 Input tumour record where IT5 IN ['1','2'] that matches a Core error-free Input patient record where IP4 IN ['1','2'] AND IP1=IT1 AND IP2=IT2 AND IP11<>'99999999' AND IT12<IP11 (see note above). Tumour record rejected
DIM1-2 Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4 IS NOT NULL that matches no Core error-free Input patient record where IP4='2' AND IP3=IT4 but matches a Base patient record where BP3=IT4 AND BP11<>'99999999' AND IT12<BP11 (see note above). Tumour record rejected
DIM1-3 Core error-free Input patient record where IP4='2' that matches a Base tumour record where IP3=BT4 AND IP11<>'99999999' AND BT12<IP11 (see note above) that matches no Core error-free Input Tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3. Patient record rejected
DIM1-4 Core error-free Input tumour record where IT5 IN ['1','2'] that matches a Core error-free Input patient record where IP4 IN ['1','2'] AND IP1=IT1 AND IP2=IT2 AND IP11<>'99999999' AND IT12.YEAR>(IP11.YEAR+117). Tumour record rejected
DIM1-5 Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4 IS NOT NULL that matches no Core error-free Input patient record where IP4='2' AND IP3=IT4 but matches a Base Patient record where BP3=IT4 AND BP11<>'99999999' AND IT12.YEAR>(BP11.YEAR+117). Tumour record rejected
DIM1-6 Core error-free Input patient record where IP4='2' that matches a Base tumour record where IP3=BT4 AND IP11<>'99999999' AND BT12.YEAR>(IP11.YEAR+117) that matches no Core error-free Input Tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3. Patient record rejected
Feedback report messages (DIM1)
Sub–edit Text Type
DIM1-1 Date of diagnosis is before Date of birth on matching Input patient record. Core error
DIM1-2 Date of diagnosis is before Date of birth on matching Base patient record. Core error
DIM1-3 Date of birth is after Date of diagnosis on matching Base tumour record. Core error
DIM1-4 Date of diagnosis is more than 117 years after Date of birth on matching Input patient record. Core error
DIM1-5 Date of diagnosis is more than 117 years after Date of birth on matching Base patient record. Core error
DIM1-6 Date of birth is more than 117 years before Date of diagnosis on matching Base tumour record. Core error
Revision (DIM1)
Year Description
2004 Edit renamed: Formerly known as Correlation Edit No.28.

DIM2

Purpose

This edit ensures that date of diagnosis and date of death are coherent.

Referenced fields (DIM2)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P3 9 CCR identification number CCR_ID
P4 1 Patient record type PRECTYPE
P14 8 Date of death PDATDEA
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Patient identification number TPIN
T3 9 Tumour reference number TTRN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
T12 8 Date of diagnosis TDATDIAG

Business rules

Tumour Date of diagnosis cannot be after the patient Date of death.

Important notes:

  • These sub-edits must be processed in a specific order. See Section 3.6.3.1 Special order of execution for more details.
  • Partially known dates must be compared using the highest common level of precision.

    Example: If Date1 = YYYYMMDD and Date2 = YYYYMM99 then dates must be compared using the year and month only. Thus, for the purpose of the following sub-edits, '20031002' and '20031099' are equal.
Edit logic (DIM2)
Sub–edit Conditions Outcome
DIM2-1 Core error-free56 Input tumour record where IT5 IN ['1','2'] that matches a Core error-free Input patient record where IP4 IN ['1','2'] AND IP1=IT1 AND IP2=IT2 AND IP14 NOT IN ['99999999','00000000'] AND IP14<IT12 (see note above). Tumour record rejected
DIM2-2 Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4 IS NOT NULL that matches no Core error-free Input patient record where IP4='2' AND IP3=IT4 but matches a Base Patient record where BP3=IT4 AND BP14 NOT IN ['99999999','00000000'] AND BP14<IT12 (see note above). Tumour record rejected
DIM2-3 Core error-free Input patient record where IP4='2' AND IP14 NOT IN ['99999999','00000000'] that matches a Base tumour record where IP3=BT4 AND BT12>IP14 (see note above) that matches no Core error-free Input tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3. Patient record rejected
Feedback report messages (DIM2)
Sub–edit Text Type
DIM2-1 Date of diagnosis is after Date of death on matching Input patient record. Core error
DIM2-2 Date of diagnosis is after Date of death on matching Base patient record. Core error
DIM2-3 Date of death is before Date of diagnosis on matching Base tumour record. Core error
Revision (DIM2)
Year Description
2004 Edit renamed: Formerly known as Correlation Edit No.29.

DIM3

Purpose

This edit ensures that the method of diagnosis accurately reflects the relationship between the date of diagnosis and the date of death.

Referenced fields (DIM3)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P3 9 CCR identification number CCR_ID
P4 1 Patient record type PRECTYPE
P14 8 Date of death PDATDEA
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Tumour patient identification number TPIN
T3 9 Tumour reference number TTRN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
T11 1 Method of diagnosis TMETDIAG
T12 8 Date of diagnosis TDATDIAG
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable

Business rules

For tumours diagnosed between 1992 and 2003
  • Method of diagnosis cannot be 'Death certificate only (DCO)' or 'Autopsy' when the Date of death indicates that the 'Patient is not known to have died'.
  • Method of diagnosis can be anything when Date of death is unknown or equal to Date of diagnosis.
  • Method of diagnosis cannot be 'Death certificate only (DCO)' when Date of diagnosis is before Date of death.57

Important notes:

  • These sub-edits must be processed in a specific order. See Section 3.6.3.1 Special order of execution for more details.
  • Partially known dates must be compared using the highest common level of precision.

    Example: If Date1 = YYYYMMDD and Date2 = YYYYMM99 then dates must be compared using the year and month only. Thus, for the purpose of the following sub-edits, '20031002' and '20031099' are equal.
Edit logic (DIM3)
Sub–edit Conditions Outcome
DIM3-1 Core error-free56 Input tumour record where IT5 IN ['1','2'] AND IT11 IN ['2','6'] AND IT12.YEAR>=1992 AND IT12.YEAR<=2003 that matches a Core error-free Input patient record where IP4 IN ['1','2'] AND IP1=IT1 AND IP2=IT2 AND IP14='00000000' Tumour record rejected
DIM3-2 Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4 IS NOT NULL AND IT11 IN ['2','6'] AND IT12.YEAR>=1992 AND IT12.YEAR<=2003 that matches no Core error-free Input patient record where IP4='2' AND IP3=IT4 but matches a Base patient record where BP3=IT4 AND BP14='00000000' Tumour record rejected
DIM3-3 Core error-free Input patient record where IP4='2' AND IP14='00000000' that matches a Base tumour record where IP3=BT4 AND BT11 IN ['2','6'] AND BT12.YEAR>=1992 AND BT12.YEAR<=2003 that matches no Core error-free Input tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3. Patient record rejected
DIM3-4 Core error-free Input tumour record where IT5 IN ['1','2'] AND IT11='6' AND IT12.YEAR>=1992 AND IT12.YEAR<=2003 that matches a Core error-free Input patient record where IP4 IN ['1','2'] AND IP1=IT1 AND IP2=IT2 AND IP14 NOT IN ['00000000', '99999999'] AND IP14>IT12 (see note above). Tumour record rejected
DIM3-5 Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4 IS NOT NULL AND IT11='6' AND IT12.YEAR>=1992 AND IT12.YEAR<=2003 that matches no Core error-free Input patient record where IP4='2' AND IP3=IT4 but matches a Base patient record where BP3=IT4 AND BP14 NOT IN ['00000000', '99999999'] AND BP14>IT12 (see note above). Tumour record rejected
DIM3-6 Core error-free Input patient record where IP4='2' AND IP14 NOT IN ['00000000', '99999999'] that matches a Base tumour record where IP3=BT4 AND BT11='6' AND BT12.YEAR>=1992 AND BT12.YEAR<=2003 AND BT12<IP14 (see note above) that matches no Core error-free Input tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3. Patient record Rejected
Feedback report messages (DIM3)
Sub–edit Text Type
DIM3-1 Method of diagnosis cannot be 'Death certificate only (DCO)' or 'Autopsy' when the Date of death indicates that the 'Patient is not known to have died' on matching Input patient record. Core error
DIM3-2 Method of diagnosis cannot be 'Death certificate only (DCO)' or 'Autopsy' when the Date of death indicates that the 'Patient is not known to have died' on matching Base patient record. Core error
DIM3-3 Date of death cannot indicate that patient is alive when Method of diagnosis is 'Death certificate only (DCO)' or 'Autopsy' on a matching Base tumour record. Core error
DIM3-4 Method of Diagnosis cannot be 'Death certificate only (DCO)' when Date of diagnosis is before Date of death on matching Input patient record. Core error
DIM3-5 Method of diagnosis cannot be 'Death certificate only (DCO)' when the Date of diagnosis is before Date of death on matching Base patient record. Core error
DIM3-6 Date of death cannot be after Date of diagnosis on a matching Base tumour record where Method of diagnosis is 'Death certificate only (DCO)'. Core error
Revision (DIM3)
Year Description
2004 Edit renamed: Formerly known as Correlation Edit No.30 – Part 1.

DIM4

Purpose

This edit ensures that the method used to establish the date of diagnosis accurately reflects the relationship between date of diagnosis and date of death.

Referenced fields (DIM4)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P3 9 CCR identification number CCR_ID
P4 1 Patient record type PRECTYPE
P14 8 Date of death PDATDEA
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Tumour patient identification number TPIN
T3 9 Tumour reference number TTRN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
T11 1 Method of diagnosis TMETDIAG
T12 8 Date of diagnosis TDATDIAG
T12.YEAR 4 First 4 digits of T12 (year of date of diagnosis) Not applicable
T24 1 Method used to establish the date of diagnosis TMETHUSED

Business rules

For tumours diagnosed between 1992 and 2003
  • Method used to establish the date of diagnosis cannot be ‘Autopsy only' or ‘Death certificate only (DCO)' when Date of death indicates that the 'Patient is not known to have died' or when Date of diagnosis is before Date of death.
  • Method used to establish the date of diagnosis can be anything when Date of death is unknown or equal to Date of diagnosis.

Important notes:

  • These sub-edits must be processed in a specific order. See Section 3.6.3.1 Special order of execution for more details.
  • Partially known dates must be compared using the highest common level of precision.

    Example: If Date1 = YYYYMMDD and Date2 = YYYYMM99 then dates must be compared using the year and month only. Thus, for the purpose of the following sub-edits, '20031002' and '20031099' are equal.
Edit logic (DIM4)
Sub–edit Conditions Outcome
DIM4-1 Core error-free56 Input tumour record where IT5 IN ['1','2'] AND IT12.YEAR>=2004 AND IT24 IN ['3','8'] that matches a Core error-free Input patient record where IP4 IN ['1','2'] AND IP1=IT1 AND IP2=IT2 AND IP14='00000000' Tumour record rejected
DIM4-2 Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4 IS NOT NULL AND IT12.YEAR>=2004 AND IT24 IN ['3','8'] that matches no Core error-free Input patient record where IP4='2' AND IP3=IT4 but matches a Base patient record where BP3=IT4 AND BP14='00000000'. Tumour record rejected
DIM4-3 Core error-free Input patient record where IP4='2' AND IP14='00000000' that matches a Base tumour record where IP3=BT4 AND BT12.YEAR>=2004 AND BT24 IN ['3','8'] that matches no Core error-free Input tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3. Patient record rejected
DIM4-4 Core error-free Input tumour record where IT5 IN ['1','2'] AND IT12.YEAR>=2004 AND IT24 IN ['3','8'] that matches a Core error-free Input patient record where IP4 IN ['1','2'] AND IP1=IT1 AND IP2=IT2 AND IP14 NOT IN ['00000000', '99999999'] AND IP14>IT12 (see note above). Tumour record rejected
DIM4-5 Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4 IS NOT NULL AND IT12.YEAR>=2004 AND IT24 IN ['3','8'] that matches no Core error-free Input patient record where IP4='2' AND IP3=IT4 but matches a Base patient record where BP3=IT4 AND BP14 NOT IN ['00000000', '99999999'] AND BP14>IT12 (see note above). Tumour record rejected
DIM4-6 Core error-free Input patient record where IP4='2' AND IP14 NOT IN ['00000000', '99999999'] that matches a Base tumour record where IP3=BT4 AND BT12.YEAR>=2004 AND BT12<IP14 (see note above) AND BT24 IN ['3','8'] that matches no Core error-free Input tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3. Patient record rejected
Feedback report messages (DIM4)
Sub–edit Text Type
DIM4-1 Method used to establish the date of diagnosis cannot be 'Autopsy Only' or 'Death certificate only (DCO)' when Date of death indicates that the 'Patient is not known to have died' on matching Input Patient record. Core error
DIM4-2 Method used to establish the date of diagnosis cannot be 'Autopsy Only' or 'Death certificate only (DCO)' when Date of death indicates that the 'Patient is not known to have died' on matching Base patient record. Core error
DIM4-3 Date of death cannot indicate that 'Patient is not known to have died' when Method used to establish the date of diagnosis is 'Autopsy Only' or 'Death certificate only (DCO)' on a matching Base tumour record. Core error
DIM4-4 Method used to establish the date of diagnosis cannot be 'Autopsy Only' or 'Death certificate only (DCO)' when Date of diagnosis is before Date of death on matching Input Patient record. Core error
DIM4-5 Method used to establish the date of diagnosis cannot be 'Autopsy Only' or 'Death certificate only (DCO)' when Date of diagnosis is before Date of death on matching Base patient record. Core error
DIM4-6 Date of death cannot be after Date of Diagnosis on matching Base tumour record where Method used to establish the date of diagnosis is 'Autopsy Only' or 'Death certificate only (DCO)' Core error
Revision (DIM4)
Year Description
2004 Edit renamed: Formerly known as Correlation Edit No.30 – Part 2.

DIM5

Purpose

This edit ensures that patient sex and tumour topography are coherent.

Referenced fields (DIM5)
Field Length Description Acronym
P1 2 Patient reporting province/territory PREPPROV
P2 12 Patient identification number PPIN
P3 9 CCR identification number CCR_ID
P4 1 Patient record type PRECTYPE
P10 1 Sex PSEX
T1 2 Tumour reporting province/territory TREPPROV
T2 12 Tumour patient identification number TPIN
T3 9 Tumour reference number TTRN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
T15 4 ICD-O-2/3 Topography TICD_O2T

Business rules

  • Tumours diagnosed in female organ must be associated with female patient. Female organs are: ICD-O-2/3 Topography: C510-C589.
  • Tumours diagnosed in male organ must be associated with male patient. Male organs are: ICD-O-2/3 Topography: C600-C639.

Important notes

These sub-edits must be processed in a specific order. See Section – 3.6.3.1 Special order of execution.

DIM5

Edit logic (DIM5)
Sub–edit Conditions Outcome
DIM5-1 (Core error-free56 Input tumour record where IT5 IN ['1','2'] AND IT15 IN [ICD-O-2/3 Topography codes associated to female organ] that matches a Core error-free Input patient record where IP4 IN ['1','2'] AND IP1=IT1 AND IP2=IT2 AND IP10 IN ['1','9'])
OR
(Core error-free Input tumour record where IT5 IN ['1','2'] AND IT15 IN [ICD-O-2/3 Topography codes associated to male organ] that matches a Core error-free Input patient record where IP4 IN ['1','2'] AND IP1=IT1 AND IP2=IT2 AND IP10 IN ['2','9'])
Tumour record rejected
DIM5-2 (Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4 IS NOT NULL AND IT15 IN [ICD-O-2/3 Topography codes associated to female organ] that matches no Core error-free Input patient record where IP4='2' AND IP3=IT4 but matches a Base patient record where BP3=IT4 AND BP10 IN ['1','9'])
OR
(Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4 IS NOT NULL AND IT15 IN [ICD-O-2/3 Topography codes associated to male organ] that matches no Core error-free Input patient record where IP4='2' AND IP3=IT4 but matches a Base patient record where BP3=IT4 AND BP10 IN ['2','9'])
Tumour record rejected
DIM5-3 (Core error-free Input patient record where IP4='2' AND IP10 IN ['1','9'] that matches a Base tumour record where IP3=BT4 AND BT15 IN [ICD-O-2/3 Topography codes associated to female organ] that matches no Core error-free Input tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3)
OR
(Core error-free Input patient record where IP4='2' AND IP10 IN ['2','9'] that matches a Base tumour record where IP3=BT4 AND BT15 IN [ICD-O-2/3 Topography codes associated to male organ] that matches no Core error-free Input tumour record where IT5 IN ['2','3'] AND IT1=BT1 AND IT2=BT2 AND IT3=BT3)
Patient record Rejected
Feedback report messages (DIM5)
Sub–edit Text Type
DIM5-1 ICD-O-2/3 Topography does not agree with Sex code on matching Input patient record. Core error
DIM5-2 ICD-O-2/3 Topography does not agree with Sex code on matching Base patient record. Core error
DIM5-3 Sex code does not agree with ICD-O-2/3 Topography on a matching Base tumour record. Core error
Revision (DIM5)
Year Description
2004 Edit renamed: Formerly known as COR31.
Business rules changed: Verification is now performed on ICD-O-3 values only.

DIM6

Purpose

This edit ensures that no "duplicate" tumour records are created for any given patient record (1992-2006 data years only). As of 2007 the CCR has adopted SEER rules. New edits will be implemented to adhere to these new rules.

Referenced fields (DIM6)
Field Length Description Acronym
T1 2 Tumour reporting province/territory TREPPROV
T12.YEAR 4 First 4 digits of Date of diagnosis (year of date of diagnosis) Not applicable
T2 12 Tumour patient identification number TPIN
T3 9 Tumour reference number TTRN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
T15 4 ICD-O-2/3 Topography TICD_O2T
T15.SITE 3 First 3 digits of T15 (ICD-O-2/3 Topography site) Not applicable
T15.SUBSITE 1 Last digit of T15 (ICD-O-2/3 Topography sub-site) Not applicable
T19 1 Laterality TLATERAL
T21 4 ICD-O-3 Histology TICD_O3H

Business rules

Definitions
  • Tumours with "equivalent topographies" are tumours that have:
    • The same ICD-O-3 sites56 and sub-sites59or
    • The same ICD-O-3 sites but at least one sub-site is 'Overlapping' (8) or 'NOS' (9) or
    • Overlapping topographies based on Equivalent Topographies for Overlapping and Unspecified Sites63 concordance table.
  • Tumours with "equivalent histologies" are tumours that have:
    • The same ICD-O-3 Histology code or
    • The same histological group based on Equivalent Histologies56 concordance table.
  • A Patient may have multiple Hematopoietic tumours (tumours with ICD-O-3 Histology codes in range 9590-9989) only if they have non-equivalent histologies. (Thus, a patient may not have more than one Hematopoietic tumour in each equivalent histology group, regardless of their respective topography and laterality.)
  • A Patient may have multiple non-Hematopoietic tumours with equivalent topographies and equivalent histologies only if they are found on paired organs with specific (right, left one side involved, origin not specified and bilateral) and different laterality.
See Appendix D – Multiple primary tumours rules for CCR for more detail.

Important notes

These sub-edits must be processed in a specific order. See Section - 3.6.3.1 Special order of execution

Edit logic DIM6)
Sub–edit Conditions Outcome
DIM6–1 Core error-free56 Input tumour record (say A) where A.T5 IN ['1','2'] AND A.T21 IN ['9590'-'9989'] that matches a Core error-free Input tumour record (say B) where B.T5 IN ['1','2'] AND A.T1=B.T1 AND A.T2=B.T2 AND A.T3<>B.T3 AND B.T21 IN ['9590'-'9989'] AND (A.T21=B.T21 OR (A.T21 and B.T21 are equivalent based on reference table Equivalent Histologies)). Tumour records A and B rejected
DIM6-2 Not applicable61 Not applicable
DIM6-3 Core error-free Input tumour record (say A) where A.T5 IN ['1','2'] AND A.T4 IS NOT NULL AND A.T21 IN ['9590'-'9989'] that matches a Base Tumour record (say B) where A.T4=B.T4 AND (A.T1<>B.T1 OR A.T3<>B.T3) AND B.T21 IN ['9590'-'9989'] AND (A.T21=B.T21 OR (A.T21 and B.T21 are equivalent based on reference table Equivalent Histologies)) that matches no Core error-free Input tumour record (say C) where C.T5 IN ['2','3'] AND C.T1=B.T1 AND C.T2=B.T2 AND C.T3=B.T3. Tumour record A rejected
DIM6-4 Core error-free Input tumour record (say A) where A.T5 IN ['1','2'] that matches a Core error-free Input tumour record (say B) where B.T5 IN ['1','2'] AND A.T1=B.T1 AND A.T2=B.T2 AND A.T3<>B.T3 AND NOT (A.T21 IN ['9590'-'9989'] AND B.T21 IN ['9590'-'9989']) AND (A.T15=B.T15 OR (A.T15.SITE=B.T15.SITE AND (A.T15.SUBSITE IN ['8','9'] OR B.T15.SUBSITE IN ['8','9'])) OR (A.T15 and B.T15 are equivalent based on Equivalent Topographies for Overlapping and Unspecified Sites)) AND (A.T21=B.T21 OR (A.T21 and B.T21 are equivalent based on Equivalent Histologies)) AND (A.T19 IN ['9','0'] OR B.T19 IN ['9','0'] OR A.T19=B.T19) Tumour records A and B rejected
DIM6-5 Not applicable59 Not applicable
DIM6-6 Core error-free Input tumour record (say A) where A.T5 IN ['1','2'] AND A.T4 IS NOT NULL that matches a Base tumour record (say B) where A.T4=B.T4 AND (A.T1<>B.T1 OR A.T3<>B.T3) AND NOT (A.T21 IN ['9590'-'9989'] AND NOT B.T21 IN ['9590'-'9989']) AND (A.T15=B.T15 OR (A.T15.SITE=B.T15.SITE AND (A.T15.SUBSITE IN ['8','9'] OR B.T15.SUBSITE IN ['8','9'])) OR (A.T15 and B.T15 are equivalent based on Equivalent Topographies for Overlapping and Unspecified Sites)) AND (A.T21=B.T21 OR (A.T21 and B.T21 are equivalent based on Equivalent Histologies)) AND (A.T19 IN ['9','0'] OR B.T19 IN ['9','0'] OR A.T19=B.T19) that matches no Core error-free Input Tumour record (say C) where C.T5 IN ['2','3'] AND C.T1=B.T1 AND C.T2=B.T2 AND C.T3=B.T3. Tumour record A rejected
Feedback report messages (DIM6)
Sub–edit Text Type
DIM6-1 Duplicate Input tumour records of the Hematopoietic system based on ICD-O-3 Histology. Core error
DIM6-2 Not applicable61 Not applicable
DIM6-3 Duplicates an existing Base tumour record of the Hematopoietic system based on ICD-O-3 Histology. Core error
DIM6-4 Duplicate Input tumour records based on ICD-O-3 Topography, ICD-O-3 Histology and Laterality. Core error
DIM6-5 Not applicable59 Not applicable
DIM6-6 Duplicates an existing Base tumour record based on ICD-O-3 Topography, ICD-O-3 Histology and Laterality. Core error
Revision (DIM6)
Year Description
2006 Edit no longer used (only applied for data years 1992-2006). New multiple primary/histology rules adopted.
2004 Edit renamed: Formerly known as Correlation Edit No.34A-F.
Business rule changed: Potential duplicate tumours with unknown laterality are now rejected.
Edit logic changed to allow the addition of a Tumour record that duplicates a Base tumour record that is about to be updated or deleted.

3.6.4 Pre-posting match edits

The purpose of the pre-posting match edits is to identify core error-free4 input records that cannot be posted to the CCR because some other related input records are either missing or have core errors.

The following table summarizes the purpose of each individual edit of this category.

Table 32 Pre-posting edits summary
Edit name Purpose
PPM1 Ensures that no orphan Patient record is created in the CCR.
PPM2 Ensures that no orphan Tumour record is created in the CCR.

PPM1

Purpose

This edit ensures that no orphan patient record is created in the CCR.

Referenced fields (PPM1)
Field Length Description Acronym
T1 2 Tumour reporting province/territory TREPPROV
T2 9 Tumour patient identification number TPIN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
P1 2 Patient reporting province/territory PREPPROV
P2 9 Patient identification number PPIN
P3 9 CCR identification number CCR_ID
P4 1 Patient record type PRECTYPE

Business rules

Every Base patient record must have at least one Base tumour record with the same Reporting province/territory and Patient identification number and CCR identification number.
Edit logic (PPM1)
Sub–edit Conditions Outcome
PPM1-1 Core error-free56 Input patient record where P4='1' that matches no Core error-free Input tumour record where T5='1' AND P1=T1 AND P2=T2. Patient record rejected
PPM1-2 One or more Core error-free Input tumour records with the same IT4 where IT5='3' that match no Core error-free Input patient record where IP4='3' AND IP3=IT4 and match no Core error-free Input tumour record where IT5 IN ['1','2'] AND IT4=IT4 but match a Base Patient record where IT1=BP1 AND IT4=BP3 and match as many Base tumour records where BT1=IT1 AND BT4=IT4. Tumour records rejected
Feedback report messages (PPM1)
Sub–edit Text Type
PPM1-1 Patient record cannot be added because all associated Add Tumour records have been rejected. Core error
PPM1-2 Tumour records cannot be deleted because it would create an orphan Patient record. Core error
Revision (PPM1)
Year Description
2004 Renamed: Formerly known as Additional rules for updating the CCR #2.
Business rules added: Prevent the addition of a new Patient record without Tumour record.

PPM2

Purpose

This edit ensures that no orphan tumour record is created in the CCR.

Referenced fields (PPM2)
Field Length Description Acronym
T1 2 Tumour reporting province/territory TREPPROV
T2 9 Tumour patient identification number TPIN
T4 9 CCR identification number CCR_ID
T5 1 Tumour record type TRECTYPE
P1 2 Patient reporting province/territory PREPPROV
P2 9 Patient identification number PPIN
P3 9 CCR identification number CCR_ID
P4 1 Patient record type PRECTYPE

Business rules

Every Base tumour record must have one Base patient record with the same CCR identification number.
Edit logic (PPM2)
Sub–edit Conditions Outcome
PPM2-1 Core error-free56 Input tumour record where T5='1' AND T4 IS NULL that matches no Core error-free Input patient record where P4='1' AND P1=T1 AND P2=T2. Tumour record rejected
PPM2-2 Core error-free Input patient record where IP4='3' that matches less Core error-free Input tumour records where IT5='3' AND IT4=IP3 than Base tumour Record where BT1=IP1 AND BT4=IP3 Patient record rejected
Feedback report messages (PPM2)
Sub–edit Text Type
PPM2-1 Tumour record cannot be added because associated Add Patient record has been rejected. Core error
PPM2-2 Patient record cannot be deleted because not all related Base tumour records with the same Reporting province/territory have been deleted. Core error
Revision (PPM2)
Year Description
2004 Edit renamed: Formerly known as Additional rules for updating the CCR #1.
Business rules added: Prevent the addition of a new Tumour record without a Patient record.

3.7 Data posting

Description

The data posting phase is the actual registration of validated data on the CCR database. During this phase, successfully validated input records are added, updated or deleted from the CCR database in accordance with the operation specified by the PTCR on each record. Depending on the operation, a CCR identification number is generated and some derived variables are computed.

In addition to the data registration, the data posting phase also updates auxiliary tables used by other processes such as internal record linkage and death clearance. These tables are:

  • Deleted CCR ID,
  • Alternate surnames,
  • Internal Record Linkage – Don't Link Cross Reference table,
  • Death Clearance – Don't Link Cross Reference.

The content and purpose of the above tables are described in Appendix F – Auxiliary tables

Organization

This section is organized as follow:

Data posting
Sub–section Description
3.7.1 Add Patient record processing
How Input records are processed based on the operation and the record type.
3.7.2 Add Tumour record processing
3.7.3 Update Patient record processing
3.7.4 Update Tumour record processing
3.7.5 Delete Patient record processing
3.7.6 Delete Tumour record processing
3.7.7 Patient Derived variable calculations
How patient and tumour derived variables are computed.
3.7.8 Tumour Derived variable calculations

Writing Conventions

Throughout the following pages, the prefixes "I" and "B" preceding field numbers indicate input or base fields respectively. These prefixes are used to indicate the origin of the corresponding variable in expressions.

Example: IP6 stands for P6 variable on an input record.
Example: BTD2 stands for TD2 variable on a base record

3.7.1 Add patient record processing

For each successfully validated add patient record, the following actions are conducted:

A new base patient record is created using:

  • CCR identification number (P3): A new CCR identification number (see below);
  • Core data items (P1 to -P19 except P4 – input record type): corresponding input record variables values;
  • Derived variables (PD1 to PD8): applicable patient derived variables values (see 3.7.7 patient derived variable calculations).

3.7.1.1 CCR identification number creation

The logic to create a new CCR identification number is the following:

LET
  • Today _Year4 be the year of today's date (4 digits).
  • Today_Year2 be the last two digits of the year of today's date (2 digits).
  • Last_CCRID_Year4 be the year the last CCR identification number was created (4 digits).
  • CCR_sequence_number be the numeric sequence used to create the CCR identification number (6 digits).
  • Check_Digit be a placeholder for the new CCR ID check digit (1 digit)
  • New_CCR_ID be a placeholder for the new CCR identification number (9 digits).
  • Check_Digit() be a function that returns a check digit based on the logic described in Appendix X – CCR_ID Check Digit Routine.
  • || be a string operator that concatenates two text strings together.
BEGIN
  • IF Last_CCRID_Year4 < Today_Year4THEN
  • CCR_Sequence_Number = '000000';
  • Last_CCRID_Year4 =Today _Year4;
  • End IF;
  • Check_Digit = Check_Digit (Today _Year2 || CCR_Sequence_Number)
  • New_CCR_ID = Today _Year2 || CCR_Sequence_Number ||Check_Digit
  • CCR_Sequence_Number =CCR_Sequence_Number + 1;/
  • RETURN New_CCR_ID;
END;

3.7.2 Add tumour record processing

For each add tumour record where the core data items (T1 to T26) are valid, the following actions are conducted:

A new base tumour record is created using:

  • Core data items (T1 to T26 except T5 – Input record type): corresponding input core data items;
  • CCR identification number (T4): reported CCR identification number or, if missing, the CCR identification number assigned to the corresponding new patient record (Patient record with the same reporting province/territory and patient identification number);
  • CS data items (T27 to T41 and T52):
    • If the tumour is within the CCR collaborative staging scope and the input CS data items are valid then the input CS data items are used.
    • If the tumour is within the CCR collaborative staging scope but the input CS data items are invalid then the corresponding base data items are "R" filled.
    • If the tumour is outside the CCR collaborative staging scope then NULL values are used.
  • AJCC TNM data items (T42 to T51):
    • If the tumour is within the CCR AJCC TNM staging scope and the input AJCC TNM data items are valid then the input AJCC TNM data items are used.
    • If the tumour is within the CCR AJCC TNM staging scope but input AJCC TNM data items are invalid then the corresponding base data items are "R" filled.
    • If the tumour is outside the CCR AJCC TNM staging scope then NULL values are used.
  • Derived data items (TD1 to TD20): applicable tumour derived variables values (see 3.7.8 Tumour derived variable calculations).

3.7.3 Update patient record processing

For each successfully validated Update patient record, the following actions are conducted:

  • Alternate surname table is updated (see below);
  • Death Clearance – Don't Link Cross Reference table is updated (see below);
  • Corresponding base patient record is updated using:
    • Core data items (P1 to P19 except P4 – Input record type): all input record variable values,
    • Derived variables (PD1-PD8): applicable patient derived variables values (see 3.7.7 Patient derived variable calculations).

3.7.3.1 Alternate surname table update

Alternate surname table is updated as following:


Let P3 be the CCR identification number
Let P6 be the patient Current Surname
IF BP6 IS NOT NULL AND (IP6 IS NULL OR IP6 <> BP6) AND (BP3, BP6 combination NOT IN [Alternate Surname table]) THEN
BP3, BP6 combination is added to Alternate Surname table.
END IF

See Appendix F – Auxiliary Tables – Alternate surname for more details.

3.7.3.2 Death Clearance – Don't Link Cross Reference Table Update

If a base Patient is Death-Cleared and the corresponding Input transaction resets all Death Information, the Death Confirmation is said to be Refused and the Death Clearance – Don't Link Cross Reference Table is updated as follows;

Let P3 be the CCR Identification Number
Let P14 be the patient Date of Death
Let P15 be the patient Province/Territory or Country of Death
Let P16 be the patient Death Registration Number
Let P17 be the patient Underlying Cause of Death
Let P18 be the patient Autopsy Confirming Cause of Death
Let PD5 be the Death Clearance Status
IF (BPD5='2' AND IP14='00000000' AND IP15='000' AND IP16='000000' AND IP17='0000' AND IP18='0') THEN
BP3, BP14, BP15, BP16 combination is added to Death Clearance – Don't Link Cross Reference table.
END IF

See Appendix F – Auxiliary Tables – Death Clearance – Don't Link Cross Reference Table for more details.

3.7.4 Update tumour record processing

For each update tumour record where the core data items (T1 to T26) are valid, the following actions are conducted:

  • Corresponding base tumour record is updated using:

Core data items (T1 to T26 except T5 – Input record type): Corresponding input core data items;
CS data items (T27 to T41, and T52):

  • If the tumour is within the CCR collaborative staging scope and the input CS data items are valid then the input CS data items are used.
  • If the tumour is within the CCR collaborative staging scope but the input CS data items are invalid then the corresponding base data items are "R" filled.
  • If the tumour is outside the CCR collaborative staging scope then NULL values are used.

AJCC TNM data items (T42 to T51):

  • If the tumour is within the CCR AJCC TNM stagingscope and the input AJCC TNM data items are valid then the input AJCC TNM data items are used.
  • If the tumour is within the CCR AJCC TNM staging scope but input AJCC TNM data items are invalid then the corresponding base data items are "R" filled.
  • If the tumour is outside the CCR AJCC TNM staging scope then NULL values are used.

Derived data items (TD1 to TD20): applicable tumour derived variables values (see 3.7.8 Tumour derived variable calculations)

3.7.5 Delete patient record processing

For each successfully validated delete patient record, the following actions are conducted:

  • Deletion or reversal of ownership of the corresponding base patient record (see below);
  • If reversal of ownership takes place, corresponding patient derived variables are updated (See3.7.7 Patient derived variable calculations).

If true patient record deletion takes place:

  • Deleted CCR_ID table is updated (see below);
  • Alternate surname table is updated (see below);
  • Internal Record Linkage – Don't Link Cross Reference table is updated (see below);
  • Death Clearance – Don't Link Cross Reference table is updated (see below).

3.7.5.1 Patient record deletion or reversal of ownership

A reversal of ownership is needed when a PTCR deletes a patient record but does not own all related tumours records (that is, at least one related tumour record is owned by another jurisdiction). In such case, the Patient record cannot be deleted from the database because it would otherwise create orphan tumour records. In lieu, the ownership (express by P1 – Patient Reporting Province/Territory and P2 – Patient Identification Number values) of the existing base patient record is changed to the jurisdiction that owns Patient's Last Diagnosed Tumour among remaining tumour records.

The Patient's Last Diagnosed Tumour is based on Date of Diagnosis (TDATDIAG) sorted in chronological order and the following additional rules:

When sorting in chronological order tumours based on the Date of Diagnosis, less precise dates must come before more precise dates. For example, if one tumour has a Date of Diagnosis of ‘19951099' and another tumour has a Date of Diagnosis of ‘19959999', then the tumour with the Date of Diagnosis of ‘19951099' is considered the Latest Tumour.
When two or more tumours share the same Date of Diagnosis, tumours are sorted in ascending order by Tumour Reference Number (TTRN), Health Insurance Number (THIN) and Reporting Province Code (TREPPROV) using an alphabetic comparison method63.
For example, if two tumours have the same Date of Diagnosis but one tumour has TTRN='2' and the other has a TTRN='12345', then the latest tumour will be the one with TTRN='2'.

The following box shows the conditions that need to be assessed and the action that must be performed when processing a delete patient record.


Let P1 be Patient reporting province/territory.
Let P2 be Patient Identification Number.
Let P3 be Patient CCR identification number.
Let T1 be Tumour reporting province/territory.
Let T2 be Tumour Patient Identification Number.
Let T4 be Tumour CCR identification number.
Let T12 be Tumour Date of diagnosis.
Let Patient Last Diagnosed Tumour () be a function that returns the latest diagnosed tumour based on the rules specified above.
IF [Base tumour records where BT4 = IP3 AND BT1 <> IP1] IS NOT NULL THEN
-- Reversal of Ownership: BP1 – Base patient reporting province/territory is updated.
BP1 and BP2 = BT1 and BT2 from Patient Last Diagnosed Tumour ([Base tumour record
where BT4 = IP3 AND BT1 <> IP1 AND MAX(BT12)])
ELSE
-- True Patient Deletion must take place
The corresponding Base record is deleted.
END IF

Since the corresponding base patient record is not really deleted from the CCR when a reversal of ownership occurs, the applicable patient derived variables must be updated.

3.7.5.2 Deleted CCR_ID Table update

When a true patient record deletion takes place (contrary to a reversal of ownership), a new entry in Deleted CCR_ID table must be created as following:

Deleted CCR_ID Table update
Deleted CCR_ID table variable Values
CCR identification number IP3
Reporting province/territory IP1
Patient identification number IP2
Date of Deletion Today's date using YYYYMMDD format.
New CCR_ID [blank]
Process 1

See Appendix F – Auxiliary Tables – Deleted CCR_ID for more details.

3.7.5.3 Alternate surname table update

When a true patient record deletion takes place (contrary to a reversal of ownership), all corresponding entries in the alternate surname table (if any) must be deleted as well.

See Appendix F – Auxiliary tables – Alternate surname for more details.

3.7.5.4 Internal Record Linkage – Don't Link Cross Reference Table Update

When a true Patient record deletion takes place (contrary to a reversal of ownership), all corresponding entries in the Internal Record Linkage – Don't Link Cross Reference table (if any) must be deleted as well.

See Appendix F – Auxiliary tables – IRL DLCR for more details.

3.7.5.5 Death Clearance – Don't Link Cross Reference Table Update

When a true Patient record deletion takes place (contrary to a reversal of ownership), all corresponding entries in the Death Clearance - Don't Link Cross Reference table (if any) must be deleted as well.

See Appendix F – Auxiliary tables – DC DLCR for more details.

3.7.6 Delete tumour record processing

For each successfully validated delete tumour record, the following actions are conducted:

Deletion of the corresponding base Tumour record.

3.7.7 Patient derived variable calculations

The following table depicts how patient derived variables are calculated depending on the operation that takes place. See corresponding variable description pages in Chapter 2 for code meaning.

Table 33 Patient derived variable calculations
Operation variable Add patient Update patient Reversal of ownership (Deletepatient)
PD1 - Processing date – Patient record
Each time a Patient record is written (created or updated), the date of the transaction is saved.

PD1 = Today's date using YYYYMMDD format.
PD2 - Vital status
Not applicable: These variables are only derived for Tabulation master files. See Chapter 4 Tabulation master files for more detail.
PD3 – Number of tumours
PD4 - Death clearance cut Off date Patient never underwent Death clearance

PD4 = '00000000'
PD4 stays the same.
PD5 - Death clearance Status Patient never underwent Death clearance

PD5 = '0'
If the Patient is Death-Cleared and Patient date of death and/or province/territory/country of death and/or Death registration number is changed, then the Patient record is no longer Death-Cleared (Death Clearance Reversal)

Let P14 be the patient Date of death
Let P15 be the patient province/territory or country of death
Let P16 be the patient Death registration number
Let PD5 be the Death Clearance Status
Let PD6 be the Death Clearance Method
Let PD7 be the Death clearance underlying cause of death
Let PD8 be Date of death (Un) Confirmation
IF BPD5 = '2' AND (IP14<>BP14 OR IP15<>BP15 OR IP16<>BP16) THEN
PD5 = '3'
PD6=‘0'
PD7='0000'
PD8=Today's date using YYYMMDD format
ELSE
PD5 stays the same.
PD6 stays the same.
PD7 stays the same.
PD8 stays the same.
END IF
PD5 stays the same.

3.7.8 Tumour derived variable calculations

The following table depicts how tumour derived variables are calculated depending on the operation that takes place. See corresponding variable description pages in Chapter 2 for code meaning.

Table 34 Tumour derived variable calculations
Operation variable Add tumour Update tumour
TD1 – Processing date – Tumour record Each time a Tumour record is written (created or updated), the date of the transaction is saved.

TD1 = Today's date using YYYYMMDD format.
TD2 – Sequence number Not applicable: these variables are only derived for Tabulation master files. See Chapter 4 Tabulation master files for more detail.
TD3 – Age at diagnosis
TD4 – Age group at diagnosis
TD5 – Survival interval
TD6 – Survival censor
TD7 – Derived AJCC T
TD8 – Derived AJCC N
TD9 – Derived AJCC M
TD10 – Derived AJCC T descriptor
TD11 – Derived AJCC N descriptor
TD12 – Derived AJCC M descriptor
TD13 – Derived AJCC stage group
TD14 – Derived AJCC flag
TD15 – Derived SS1977
TD16 – Derived SS1977 flag
TD17 – Derived SS2000
TD18 – Derived SS2000 flag
TD19 – CS version latest

Chapter 4 – Tabulation master files

  • Description
  • Scope
  • Content and layout
  • Derived variables calculations
  • Confidentiality

4.1 Description

The Tabulation master file (TMF) produced from the Canadian Cancer Registry (CCR) serves as a snapshot of the entire CCR database. The resulting flat file merges the patient and tumour records from the CCR, using the unique patient record identifier (CCR identification number) to produce a composite record containing both patient and tumour information, with one record for each tumour.

The TMF is used by researchers, academics, regional health unit personnel, health policy/program planners and decision-makers, epidemiologists and public health professionals. It is provided to representatives from organizations such as Health Canada, the Public Health Agency of Canada, the Canadian Institute for Health Information, and other health-related non-government organizations in accordance with applicable legal agreements and Statistics Canada's guidelines pertaining to release of confidential information. It is created on a yearly basis or, in some instances, as warranted by operational requirements.

See http://www.statcan.ca/english/about/privact.htm section 4.5 Confidentiality

4.2 Scope

There are 2 versions of the tabulation master file, the Canadian Cancer Registry tabulation master file (CCRTMF) and the International Agency for Research on Cancer tabulation master file (IARCTMF). These two versions differ in scope as different rules for determining multiple primary neoplasms are applied.

In addition, each of the TMF can either be national (based on patients from all PTCRs) or provincial/territorial (based on patients from only one PTCR). Provincial/territorial TMFs are based on the ownership of Patient records, i.e. tumours are selected based on the reporting province or territory of its related patient record regardless of the province or territory that actually owns the tumour record itself.

4.2.1 CCRTMF – Canadian Cancer Registry tabulation master file.

Variations exist between provincial/territorial Cancer Registries in the coding practices for multiple primaries. Many registries adhere to CCR rules while others use IARC (Québec), IARC/Berg (Ontario) and SEER (Alberta from 1994) for recording tumours in their registries. Given that all cancer records submitted to the CCR are subjected to specific CCR rules for determining multiple primary tumours (see Appendix D – Multiple primary tumours rules for CCR for more details), the resulting CCRTMF consists of a mixture of IARC and CCR rules for determining multiple tumours. As of 2007 the CCR has adopted SEER rules.

4.2.2 IARCTMF – International agency for research on cancer (IARC) tabulation master file

Important note: IARCTMF implementation has changed in 2004. See Revision box at the end of this section for details.

Since not all registries follow the CCR standards, the annual release of cancer incidence and survival statistics are disseminated from STC using the IARC rules for determining multiple primary tumours for the purpose of comparability between registries over time.

All tumour records on IARCTMF have been selected from the CCR according to IARC coding rules for determining multiple primary tumours as specified by the IARC/IACR's Working Groups' Recommendations for coding Multiple Primaries. The International Classification of Diseases for Oncology – Third Edition outlines the rules as follows:

A working party of IARC recommended definitions of multiple neoplasms for the purpose of incidence reporting for international comparison. Their recommendations are:
  1. Recognition of the existence of two or more primary cancers does not depend on time.
  2. A primary cancer is one that originates in a primary site or tissue and is neither an extension, nor a recurrence, nor a metastasis.
  3. Only one tumour shall be recognized as arising in an organ or pair of organs or tissue. For tumours where site is coded by the first edition of ICD-O (or by ICD-9), an organ or tissue is defined by the three-character category of the topography code.

    ICD-1O and the Second and Third editions of ICD-O have a more detailed set of topography codes. The sites covered by some groups of codes are considered to be a single organ for the purposes of defining multiple tumours. These topography code groups are shown in Table 24*.

    Multifocal tumours – that is, discrete masses apparently not in continuity with other primary cancers originating in the same primary site or tissue, for example bladder – are counted as a single cancer.

    Skin cancer presents a special problem as the same individual may have many such neoplasms over a lifetime. The IARC/IACR rules imply that only the first tumour of a defined histological type, anywhere on the skin, is counted as an incident cancer unless, for example, one primary was a malignant melanoma and the other a basal cell carcinoma.
  4. Rule 3 does not apply in two circumstances: 4.1. For systemic or multicentric cancers potentially involving many discrete organs, four histological groups – lymphomas, leukemias, Kaposi sarcoma, and mesothelioma (groups 7, 8, 9 and 10 in Table 25*) – are included. They are counted only once in any individual.
    4.2. Other specific histologies – groups 1, 2, 3, 4, 6, and 11 in Table 25 – are considered to be different for the purpose of defining multiple tumours. Thus, a tumour in the same organ with a ‘different' histology is counted as a new tumour. Groups 5 and 12 include tumours that have not been satisfactorily typed histologically and cannot therefore be distinguished from the other groups.
- Source International Classification of Diseases for Oncology – Third Edition, page 35

"* "Table 24" and "Table 25" are reproduced on the following pages.

Table 24 Groups of topography codes from ICD-O-2 and ICD-O-3 considered a single site in the definition of multiple cancers
ICD–O–2/3 Topography codes Description
C01 Base of tongue
C02 Other and unspecified parts of tongue
C05 Palate
C06 Other and unspecified parts of mouth
C07 Parotid gland
C08 Other and unspecified major salivary glands
C09 Tonsil
C10 Oropharynx
C12 Pyriform sinus
C13 Hypopharynx
C23 Gallbladder
C24 Other and unspecified parts of biliary tract
C30 Nasal cavity and middle ear
C31 Accessory sinus
C33 Trachea
C34 Bronchus and lung
C37 Thymus
C38.0 Heart
C38.1-.3 Mediastinum
C38.8 Overlapping lesion of heart, mediastinum and pleura
C38.4 Pleura (visceral, parietal, NOS)
C51 Vulva
C52 Vagina
C57.7 Other specified female genital organs
C57.8-.9 Unspecified female genital organs
C56 Ovary
C57.0 Fallopian tube
C57.1 Broad ligaments
C57.2 Round ligament
C57.3 Parametrium
C57.4 Uterine adnexa
C60 Penis
C63 Other and unspecified male genital organs
C64 Kidney
C65 Renal pelvis
C66 Ureter
C68 Other and unspecified urinary organs
C74 Adrenal gland
C75 Other endocrine glands and related structures
Source: THE SEER PROGRAM CODING AND STAGING MANUAL 2004, Fourth Edition, January 2004, page 9, Surveillance Research Program Division Of Cancer Control And Population Sciences, National Cancer Institute, U.S. Department Of Health And Human Services.
Table 25 Groups of malignant neoplasms considered to be histologically "different" for the purpose of defining multiple tumours (adapted from Berg, 1994)
Group Description ICD-O-3 Histology codes
1 Squamous carcinomas 805 to 808, 812, 813
2 Basal cell carcinomas 809 to 811
3 Adenocarcinomas 814, 816, 819 to 822, 826to 833, 835 to 855, 857, 894
4 Other specific carcinomas 803, 804, 815, 817 to 818, 823 to 825, 834, 856, 858 to 867
(5) Unspecified carcinomas (NOS) 801, 802
6 Sarcomas and soft tissue tumours 868 to 871, 880 to 892, 899, 904, 912 to 913, 915 to 925, 937, 954 to 958
7 Lymphomas 959 to 972
8 Leukemia 980 to 994, 995, 996, 998
9 Kaposi sarcoma 914
10 Mesothelioma 905
11 Other specified types ofcancer 872 to 879, 893, 895 to 898, 900 to 903, 906 to 911, 926 to 936, 938 to 953, 973 to 975, 976
(12) Unspecified types of cancer 800, 997
Source: INTERNATIONAL CLASSIFICATION OF DISEASES FOR ONCOLOGY, Third Edition, 2000, page 37, World Health Organization.

Based on the above rules and tables, the following algorithm is used to eliminate duplicate tumours from the IARC tabulation master files.

Table 35 Algorithm used to eliminate duplicate tumours from IARC TMF

Definitions
Site: Identified by the 3 first digits of the ICD-O-2 Topography code.
Topography Group: See Table 24.
Histology Group: See Table 25.
Systemic and Multicentric groups: 7, 8, 9, 10
Non-Systemic and Non-Multicentric groups: 1, 2, 3, 4, 5, 6, 11, 12
Specific Histology groups: 1, 2, 3, 4, 6, 11
Non-Specific Histology groups: 5, 12
Rule 1: When there is more than one tumour in a subset, keep the tumour with the earliest Date of Diagnosis. If more than one tumour has the same Date of Diagnosis, then the tumour with the lowest TTRN, TPIN and TREPPROV is kept.
Logic
For a given patient with more than one tumour:
For Systemic and Multicentric Tumours:
Eliminate duplicate tumours in each Systemic and Multicentric Group using Rule1(regardless of the Site).
For Non-Systemic and Non-Multicentric Tumours:
Eliminate duplicate tumours within the same Site and same Specific Histology group using Rule1;
Eliminate duplicate tumours within the same Site and any Non-Specific Histology group using Rule1;
Eliminate all tumours within Non-Specific Histology groups when there is at least one tumour within Specific Histology groups for the same Site;
Eliminate duplicate tumours within the same Topography group and same Specific Histology group using Rule 1;
Eliminate duplicate tumours within the same Topography group and any Non-Specific Histology group using Rule 1;
Eliminate all tumours within Non-Specific Histology groups when there is at least one tumour within Specific Histology groups for the same Topography group

When a patient has only two tumours, it may be easier to use the following decision tree instead of the above algorithm to assess if tumours are duplicates. When a patient has more than two tumours, the above algorithm must always be used to eliminate duplicate tumours since the decision tree does not indicate the order in which to process tumours pairs which in turn may lead to incorrect results.

Figure 1 Decision tree to assess if two tumours are duplicates based on IARC rules

Figure 1 Decision tree to assess if two tumours are duplicates based on IARC rules
Revision (Description)
Year Description
2007 Table 24 changed:Topography group added: C38.4
2004 Table 24 changed: The latest SEER "Table 24" definition has been implemented.

Topography groups removed: C19, C20; C40, C41;

Topography groups added: C37, C38.0-3 and C38.8; C51, C52, C57.7 and C57.8-9; C56 and C57.0-4;

Algorithm changed:

Systemic and Multicentric tumours: IARC criteria are applied regardless of the CCR Multiple Primary rules.

Duplicate tumours within the same Histology group and with the same Date of Diagnosis: In this case, only the tumour with the lowest Tumour Reference Number, Patient identification number and Reporting Province/Territory Code is kept. This was needed to guarantee that the tumour selected is always the same when the Date of Diagnosis is the same for all tumours.

Histology group 5 vs 12: These two groups are now considered the same for the purpose of finding duplicate tumours.

Specific Histology groups vs Non-Specific Histology groups: A condition has been added to deal with duplicate tumours from different Histology groups where specific and non-specific histologies have been reported. In this case, only tumours with specific histology are kept, regardless of the Date of Diagnosis.

4.3 Content and layout

The TMF includes all variables on the patient and tumour records as provided by PTCRs (except for Fields P4 and T5, the patient and tumour record types) plus additional variables that are derived from the input variables or brought in from other sources by the CCR. (See Chapter 2 Data dictionary for more information about each variable.)

The record layout for both CCR and IARC tabulation master files is as follows.

Table 36 TMF record layout
Field Length Position Description Acronym
P1 2 1 - 2 Patient reporting province/territory PREPPROV
P2 12 3 - 14 Patient identification number PPIN
P3 9 15 - 23 CCR identification number CCR_ID
P5 1 24 - 24 Type of Current surname PTYP_CUR
P6 25 25 - 49 Current surname PCURSNAM
P7 15 50 - 64 First given name PGNAME_1
P8 15 65 - 79 Second given name PGNAME_2
P9 7 80 - 86 Third given name PGNAME_3
P10 1 87 - 87 Sex PSEX
P11 8 88 - 95 Date of birth PDATBIR
P12 3 96 - 98 Province/territory or country of birth PPROVBIR
P13 25 99 - 123 Birth surname PBIRNAM
P14 8 124 - 131 Date of death PDATDEA
P15 3 132 - 134 Province/territory or country of death PPROVDEA
P16 6 135 - 140 Death registration number PDEAREG
P17 4 141 - 144 Underlying cause of death PCAUSDEA
P18 1 145 - 145 Autopsy confirming cause of death PAUTOPSY
P19 8 146 - 153 Patient date of transmission PDATTRAN
PD1 8 154 - 161 Processing date – patient record PDCCRDATPROC
PD2 1 162 - 162 Vital status PDCCRVITALST
PD3 2 163 - 164 Number of tumours PDCCRNBRTMRS
PD4 8 165 - 172 Death clearance cut off date PDDCDATCO
PD5 1 173 - 173 Death clearance status PDDCSTAT
PD6 1 174 - 174 Death clearance method PDDCMETH
PD7 4 175 - 178 Death clearance underlying cause of death PDDCUCD
PD8 8 179 - 186 Date of death (Un) confirmation PDDCDATCN
T1 2 187 - 188 Tumour reporting province/territory TREPPROV
T2 12 189 - 200 Tumour patient identification number TPIN
T3 9 201 - 209 Tumour reference number TTRN
T6 25 210 - 234 Name of place of residence TPLACRES
T7 6 235 - 240 Postal code TPOSTCOD
T8 7 241 - 247 Standard geographic code TCODPLAC
T9 9 248 - 256 Census tract TCENTRAC
T10 15 257 - 271 Health insurance number THIN
T11 1 272 - 272 Method of diagnosis TMETHDIAG
T12 8 273 - 280 Date of diagnosis TDATDIAG
T13 4 281 - 284 ICD-9 cancer code TICD_9
T14 1 285 - 285 Source classification flag TSCF
T15 4 286 - 289 ICD-O-2/3 Topography TICD_O2T
T16 4 290 - 293 ICD-O-2 Histology TICD_O2H
T17 1 294 - 294 ICD-O-2 Behaviour TICD_O2B
T19 1 295 - 295 Laterality TLATERAL
T21 4 296 - 299 ICD-O-3 Histology TICD_O3H
T22 1 300 - 300 ICD-O-3 Behaviour TICD_O3B
T23 1 301 - 301 Grade, differentiation or cell indicator TGRADE
T24 1 302 - 302 Method used to establish date of diagnosis TMETHUSED
T25 1 303 - 303 Diagnostic confirmation TMETHCONF
T26 8 304 - 311 Tumour date of transmission TDATTRAN
T27 3 312 - 314 CS tumour size TCSTSIZE
T28 2 315 - 316 CS extension TCSEXTN
T29 1 317 - 317 CS tumour size/ext eval TCSEVAL
T30 2 318 - 319 CS lymph nodes TCSLNODE
T31 1 320 - 320 CS reg nodes eval TCSRNEVAL
T32 2 321 - 322 Regional nodes examined TCSRNEXAM
T33 2 323 - 324 Regional nodes positive TCSRNPOS
T34 2 325 - 326 CS mets at dx TCSMDIAG
T35 1 327 - 327 CS mets Eval TCSMEVAL
T36 3 328 - 330 CS site-specific factor 1 TCSSSF1
T37 3 331 - 333 CS site-specific factor 2 TCSSSF2
T38 3 334 - 336 CS site-specific factor 3 TCSSSF3
T39 3 337 - 339 CS site-specific factor 4 TCSSSF4
T40 3 340 - 342 CS site-specific factor 5 TCSSSF5
T41 3 343 - 345 CS site-specific factor 6 TCSSSF6
T42 9 346 - 354 AJCC clinical T TAJCCCLINT
T43 3 355 - 357 AJCC clinical N TAJCCCLINN
T44 3 358 - 360 AJCC clinical M TAJCCCLINM
T45 9 361 - 369 AJCC pathologic T TAJCCPATHT
T46 6 370 - 375 AJCC pathologic N TAJCCPATHN
T47 3 376 - 378 AJCC pathologic M TAJCCPATHM
T48 4 379 - 382 AJCC clinical TNM stage group TAJCCCLINSG
T49 4 383 - 386 AJCC pathologic TNM stage group TAJCCPATHSG
T50 4 387 - 390 AJCC TNM stage group TAJCCSG
T51 2 391 - 392 AJCC TNM edition number TAJCCEDNUM
TD1 8 393 - 400 Processing date – tumour record TDCCRDATPROC
TD2 2 401 - 402 Sequence number TDCCRSEQNUM
TD3 3 403 - 405 Age at diagnosis TDCCRAGEDIAG
TD4 2 406 - 407 Age group at diagnosis TDCCRAGEGRP
TD5 5 408 - 412 Survival interval TDDCSURVINT
TD6 1 413 - 413 Survival censor TDDCCENSOR
TD7 2 414 - 415 Derived AJCC T TDCSAJCCT
TD8 2 416 - 417 Derived AJCC N TDCSAJCCN
TD9 2 418 - 419 Derived AJCC M TDCSAJCCM
TD10 1 420 - 420 Derived AJCC T descriptor TDCSAJCCTDESC
TD11 1 421 - 421 Derived AJCC N descriptor TDCSAJCCNDESC
TD12 1 422 - 422 Derived AJCC M descriptor TDCSAJCCMDESC
TD13 2 423 - 424 Derived AJCC stage group TDCSAJCCSG
TD14 1 425 - 425 Derived AJCC flag TDCSAJCCF
TD15 1 426 - 426 Derived SS1977 TDCSSS1977
TD16 1 427 - 427 Derived SS1977 flag TDCSSS1977F
TD17 1 428 - 428 Derived SS2000 TDCSSS2000
TD18 1 429 - 429 Derived SS2000 flag TDCSSS2000F
T52 6 430 - 435 CS version 1st TCSFVER
TD19 6 436 - 441 CS version latest TDCSLVER
T53 1 442 - 442 Ambiguous Terminology Diagnosis TAMBIGTERM
T54 8 443 - 450 Date of conclusive diagnosis TDATCONCLUSDIAG
T55 2 451 - 452 Type of multiple tumours reported as one primary TMULTTUMONEPRIM
T56 8 453 - 460 Date of multiple tumours TDATMULT
T57 2 461 - 462 Multiplicity counter TMULTCOUNT
Revision (Content and layout)
Year Description
2008 Addition of T53 to T57
2007 Addition of T52, deletion of TD20

4.4 Derived variable calculations

Most of the derived variables found on the tabulation master file are used and updated by the CCR System main processes (namely data loading, internal record linkage and death clearance process). Thus, these variables are already available at tabulation master file (TMF) creation time and do not need to be recalculated. Variables that are not used by the CCR System main processes must be derived at TMF creation time. The following table shows which variables are derived at TMF creation time and their respective calculation specification.

Table 37 Derived variable calculations at TMF time
Variable Value
PD2 – Vital status  Let P14 be the patient Date of death

IF P14 = ‘00000000' THEN
PD2 = ‘1'
ELSE
PD2 = ‘2'
End IF
PD3 – Number of tumours PD3 = Patient's total number of tumours within the applicable TMF scope.
TD2 – Sequence number For a given CCR identification number and TNM scope, tumours are numbered from 1 to N in chronologic order based on the Date of diagnosis. If two or more tumours share the same Date of diagnosis, then tumours are ordered by Reporting province/territory and Tumour reference number in ascending order.

TD2 = Sequence number based on the above definition.
TD3 – Age at diagnosis If the Patient date of birth is unknown, then Age at diagnosis cannot be calculated. Otherwise, Age at diagnosis is calculated using Patient date of birth and the tumour Date of diagnosis.

Let INTERVAL_YEARS (Date1, Date2) be a function that returns the number of complete years between Date1 and Date2 as described in Appendix E – Interval and Mean Time Between Dates.
Let P11 be the corresponding Patient date of birth.
Let T12 be the Tumour date of diagnosis.

IF P11 = '99999999' THEN
TD3 = 999
ELSE
TD3 = INTERVAL_YEARS (P11, T12)
END IF
TD4 – Age group at diagnosis TD4 = Corresponding age group based on TD3 value. (See TD4 – Specified values and meaning.)
TD5 – Survival interval
TD6 – Survival censor
If the Patient never underwent Death clearance process; or the Date of diagnosis is after Death clearance cut-off date; or the Method of diagnosis is Death certificate only; or the Method of diagnosis is Autopsy and there is no clear evidence of a positive survival; or the Method used to establish the date of diagnosis is Autopsy or Death certificate only, then the Survival interval is not applicable.
If Survival interval is applicable but Date of death is unknown, then the Survival interval cannot be calculated.
If Survival interval is applicable but the Patient is not known to have died or died after the Death clearance cut-off date, then the Survival interval is calculated using Death clearance cut off date.
If the Survival interval is applicable and the patient died before or on the Death clearance cut-off date, then the Survival interval is calculated using Date of death.

Let INTERVAL_DAYS (Date1, Date2) be a function that returns the number of days between Date1 and Date2 as described in Appendix E – Interval and Mean Time Between Dates.
Let T11 be the Tumour method of diagnosis.
Let T12 be the Tumour date of diagnosis.
Let T24 be the Tumour method used to establish the date of diagnosis.
Let PD4 be the corresponding Patient death clearance cut-off date.
Let P14 be the corresponding Patient Date of death.

IF PD4 = '00000000'
OR T12.YEAR > PD4.YEAR
OR T11 = '6'
OR (T11 = '2' AND P14 = '99999999')
OR (T11 = '2' AND T12.YEAR = P14.YEAR AND (T12.MONTH = '99' OR P14.MONTH = '99'))
OR (T11 = '2' AND T12.YEAR = P14.YEAR AND T12.MONTH = P14.MONTH AND (T12.DAY = '99' OR P14.DAY = '99'))
OR T24 IN ['3', '8'] THEN
TD5 = 99998
TD6 = '0'
ELSE IF P14 = '99999999' THEN
TD5 = 99999
TD6 = '0'
ELSE IF P14 = '00000000' OR P14.YEAR > PD4.YEAR THEN
TD5 = INTERVAL_DAYS (T12, PD4)
TD6 = '2'
ELSE
TD5 = INTERVAL_DAYS (T12, P14)
TD6 = '1'
END IF
TD7 – Derived AJCC T Values returned by the recommended version of the AJCC CS algorithm based on CS Input variables and tumour ICD-O-2/3 Topography and ICD-O-3 Histology.
TD8 – Derived AJCC N
TD9 – Derived AJCC M
TD10 – Derived AJCC T descriptor
TD11 – Derived AJCC N descriptor
TD12 – Derived AJCC M descriptor
TD13 – Derived AJCC stage group
TD14 – Derived AJCC flag
TD15 – Derived SS1977
TD16 – Derived SS1977 flag
TD17 – Derived SS2000
TD18 – Derived SS2000 flag
TD19 – CS version latest
Revision (Derived variable calculations)
Year Description
2007 PD2 – Vital Status is now derived at TMF time

4.5 Confidentiality

In order to respect confidentiality agreements, three different filtering options may be applied to the tabulation master files.

  • No filtering: No fields are hidden. This TMF is used to return data to reporting PTCR and for authorized record linkage activities.
  • No name: All names and Health insurance number fields are hidden. This TMF is used for NAACCR submission.
  • No name, No key: All names, Health insurance number and patient identification number fields are hidden. This TMF is used for dissemination.

The following table explicitly lists which fields are hidden by the different confidentiality filters.

Table 38 Hidden fields on filtered tabulation master files
Sensitive Field Filtering Option
No Filtering No Name No Name, No Key
P2 – Patient Identification Number - - Hidden
P6 – Current Surname - Hidden Hidden
P7 – First Given Name - Hidden Hidden
P8 – Second Given Name - Hidden Hidden
P9 – Third Given Name - Hidden Hidden
P13 – Birth Surname - Hidden Hidden
T2 – Tumour Patient Identification Number - - Hidden
T10 – Health Insurance Number - Hidden Hidden

In order to keep the same record layout for all Tabulation Master Files, hidden fields are simply filled with 'X'.

Appendices

Appendix C – AJCC TNM reference tables
Appendix D – Multiple primary tumours rules for CCR
Appendix E – Interval and mean time between dates
Appendix F – Auxiliary tables
Appendix G – Grade, differentiation or cell indicator guidelines (for T23)
Appendix H – CCR Ambiguous Terms (for T12 and T53)
Appendix I – Guidelines for Abstracting and Determining Death Certificate Only (DCO) Cases for
Provincial/Territorial Cancer Registries (PTCRs) in Canada (for T12 and P18)
Appendix J – Internal between two dates (complete or partial)
Appendix T – Residency guidelines in Canada (for T1, T6, P1)
Appendix X – CCR_ID check digit routine
Appendix Z – References

Appendix C – AJCC TNM reference tables

This appendix describes all AJCC TNM reference tables, namely:

  • Valid AJCC clinical T by site;
  • Valid AJCC clinical N by site;
  • Valid AJCC clinical M by site;
  • Valid AJCC pathologic T by site;
  • Valid AJCC pathologic N by site;
  • Valid AJCC pathologic M by site;
  • Valid AJCC clinical TNM stage group by site;
  • Valid AJCC pathologic TNM stage group by site;
  • Valid AJCC TNM stage group by site;
  • Valid AJCC T, N, M and stage group combination by site

Valid AJCC clinical T by site

Table usage notes:

See Chapter 1 for a complete description of each eligible site in terms of topography, histology and behaviour.

Table 39 Valid AJCC clinical T by stageable site
Breast Prostate Colorectal
TX TX TX
T0 T0 T0
Tis -- Tis
TisDCIS -- --
TisLCIS -- --
TisPagets -- --
T1 T1 T1
T1mic -- --
T1a T1a --
T1b T1b --
T1c T1c --
T2 T2 T2
-- T2a --
-- T2b --
-- T2c --
T3 T3 T3
-- T3a --
-- T3b --
T4 T4 T4
T4a -- --
T4b -- --
T4c -- --
T4d -- --
99 99 99

Valid AJCC clinical N by site

Table usage notes:

See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.

Table 40 Valid AJCC clinical N by stageable site
Breast Prostate Colorectal
NX NX NX
N0 N0 N0
N1 N1 N1
N2 -- N2
N2a -- --
N2b -- --
N3 -- --
N3a -- --
N3b -- --
N3c -- --
99 99 99

Valid AJCC clinical M by site

Table usage notes:

See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.

Table 41 Valid AJCC clinical M by stageable site
Breast Prostate Colorectal
MX MX MX
M0 M0 M0
M1 M1 M1
-- M1a --
-- M1b --
-- M1c --
99 99 99

Valid AJCC pathologic T by site

Table usage notes:

See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.

Table 42 Valid AJCC pathologic T by stageable site
Breast Prostate Colorectal
TX TX TX
T0 -- T0
Tis -- Tis
TisDCIS -- --
TisLCIS -- --
TisPagets -- --
T1 -- T1
T1mic -- --
T1a -- --
T1b -- --
T1c -- --
T2 T2 T2
-- T2a --
-- T2b --
-- T2c --
T3 T3 T3
-- T3a --
-- T3b --
T4 T4 T4
T4a -- --
T4b -- --
T4c -- --
T4d -- --
99 99 99

Valid AJCC pathologic N by site

See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.

Table 43 Valid AJCC pathologic N by stageable site
Breast Prostate Colorectal
NX NX NX
N0 N0 N0
N0i- -- --
N0i+ -- --
N0mol- -- --
N0mol+ -- --
N1 N1 N1
N1mi -- --
N1a -- --
N1b -- --
N1c -- --
N2 -- N2
N2a -- --
N2b -- --
N3 -- --
N3a -- --
N3b -- --
N3c -- --
99 99 99

Valid AJCC pathologic M by site

Table usage notes:

See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.

Table 44 Valid AJCC pathologic M by stageable site
Breast Prostate Colorectal
MX MX MX
M0 M0 M0
M1 M1 M1
-- M1a --
-- M1b --
-- M1c --
99 99 99

Valid AJCC clinical TNM stage group by site

Table usage notes:

See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.

Table 45 Valid AJCC TNM clinical stage group by stageable site
Breast Prostate Colorectal
X X X
0 -- 0
I I I
-- II --
IIA -- IIA
IIB -- IIB
-- III --
IIIA -- IIIA
IIIB -- IIIB
IIIC -- IIIC
IV IV IV
99 99 99

Valid AJCC pathologic TNM stage group by site

Table usage notes:

See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.

Table 46 Valid AJCC TNM pathologic stage group by stageable site
Breast Prostate Colorectal
X X X
0 -- 0
I I I
-- II --
IIA -- IIA
IIB -- IIB
-- III --
IIIA -- IIIA
IIIB -- IIIB
IIIC -- IIIC
IV IV IV
99 99 99

Valid AJCC TNM stage group by site

Table usage notes:

See Chapter 1 for a complete description of each stageable site in terms of topography, histology and behaviour.

Table 47 Valid AJCC TNM stage group by stageable site
Breast Prostate Colorectal
0 -- 0
I I I
II61 II II61
IIA -- IIA
IIB -- IIB
III61 III III61
IIIA -- IIIA
IIIB -- IIIB
IIIC -- IIIC
IV IV IV
99 99 99

Valid AJCC T, N, M and stage group combination by site

Table usage notes

  • The following tables assess the validity of the T, N, M and stage group values combination. They can be used to assess either clinical or pathologicvalues.
  • TNM values in the tables include all their sub-values. Thus, the expression ‘T1' includes {T1, T1a, T1b, T1is...}. The actual list of included values depends on the site.
  • In the context of the CCR System, the expression ‘Any T' or ‘Any N' include all their respective sub-values and the value ‘99'. Thus, the expression ‘Any N' includes {99, NX, N0, N1, N1a...}
Table 48 Valid AJCC T, N, M and stage group combination for colorectal sites
Stage Group T N M
0 Tis N0 M0
I T1 N0 M0
I T2 N0 M0
IIA T3 N0 M0
IIB T4 N0 M0
IIIA T1 N1 M0
IIIA T2 N1 M0
IIIB T3 N1 M0
IIIB T4 N1 M0
IIIC Any T N2 M0
IV Any T Any N M1
Table 49 Valid AJCC T, N, M and stage group combination for breast sites
Stage group T N M
0 Tis N0 M0
I T1 N0 M0
IIA T0 N1 M0
IIA T1 N1 M0
IIA T2 N0 M0
IIB T2 N1 M0
IIB T3 N0 M0
IIIA T0 N2 M0
IIIA T1 N2 M0
IIIA T2 N2 M0
IIIA T3 N1 M0
IIIA T3 N2 M0
IIIB T4 N0 M0
IIIB T4 N1 M0
IIIB T4 N2 M0
IIIC Any T N3 M0
IV Any T Any N M1
Table 50 Valid AJCC T, N, M and stage group combination for prostate sites
Stage group T N M
I T1a N0 M0
II T1a N0 M0
II T1b N0 M0
II T1c N0 M0
II T2 N0 M0
III T3 N0 M0
IV T4 N0 M0
IV Any T N1 M0
IV Any T Any N M1

This table has been slightly modified from the AJCC cancer staging manual, 6,th Edition since the CCR system does not consider the grade when validating the stage group and T, N, M values combination

Revision (Valid AJCC T, N, M and stage group combination by site)
Year Description
2008 Table 50: updated Stage group II with T1a, T1b and T1c

Appendix D – Multiple primary tumours rules for CCR

As of 2007 the CCR has adopted SEER rules. New edits will be implemented to adhere to these new rules.

Figure 2 Decision tree to assess CCR Multiple primary tumours

Figure 2 Decision tree to assess CCR Multiple primary tumours

Appendix E – Interval and mean time between dates

The following algorithm can be used to assess the number of days or complete years between two dates. When both dates are complete, the algorithm returns the exact number of days or complete years between the two dates. When one or both dates are partial, the mean number of days or complete years between the two dates is returned. This algorithm cannot be used if one or both dates are totally unknown, i.e. equal to '99999999'. The returned value is always a positive whole number (including zero).

Definitions

Let Date1 and Date2 be the two dates from which the interval must be calculated and where Date1 <= Date2.

Let Y1, M1 and D1 be the year, month and day of date1.
Let Y2, M2 and D2 be the year, month and day of date2.
Let MOD (X, Y) be a function that returns the remainder of X divided by Y.
Let MIDDLE_DAY (Month) be a function that returns the middle day of month using the following logic:

If Month='02' Then
Return '15'
Otherwise
Return '16'

Let LAST_DAY (Year, Month) be a function that returns the last day of the month for the specified year using the following logic:

If Month='02' Then
If (MOD(Y2,4)=0 AND MOD(Y2,100)<>0) OR (MOD(Y2,4)=0 AND MOD(Y2,400)=0) Then
Return '29'
Else
Return '28'
Else If Month in ('04','06','09','11') Then
Return '30'
Else
Return '31'

Let MONTH_BETWEEN (Date1, Date2) be a function that returns the number of months between date1 and date2. If date1 is later than date2, then the result is positive. If date1 is earlier than date2, then the result is negative. If date1 and date2 are either the same days of the month or both last days of months, then the result is always a whole number. Otherwise a fractional portion of the result based on a 31-day month is also added.

Algorithm (Appendix E – Interval and mean time between dates)
Number of days between Date1 and Date2 Number of years between Date1 and Date2
Based on unknown date components and existing conditions between Date1 and Date2, found the right expression to compute the number of days between Date1 and Date2 using the following table.
Evaluate the expression.
Return rounded result.
Based on unknown date components and existing conditions between Date1 and Date2, found the right expression to compute the number complete years between Date1 and Date2 using the following table.
Evaluate the expression.
Return truncated result.
Table 51 Interval and mean time between dates calculation
Unknown date components Conditions Number of days between Date1 and Date2 Number of years between Date1 and Date2
None None Y2/M2/D2 - Y1/M1/D1 MONTH_BETWEEN (Y2/M2/D2, Y1/M1/D1) / 12
D1 Y1=Y2 AND M1=M2 ½ * (Y2/M2/D2 - Y1/M1/01) 0
Otherwise Y2/M2/D2 - Y1/M1/MIDDLE_DAY(M1) MONTH_BETWEEN (Y2/M2/D2, Y1/M1/MIDDLE_DAY(M1)) / 12
D2 Y1=Y2 AND M1=M2 ½ * (Y2/M2/LAST_DAY(Y2,M2) - Y1/M1/D1) 0
Otherwise Y2/M2/MIDDLE_DAY(M2) - Y1/M1/D1 MONTH_BETWEEN (Y2/M2/MIDDLE_DAY(M2), Y1/M1/D1) / 12
D1, D2 Y1=Y2 AND M1=M2 ½ * (Y2/M2/LAST_DAY(Y2,M2) - Y1/M1/MIDDLE_DAY(M1)) [~ 7]
Note: Given the small difference between all possible cases, 7 can be used for all cases.
Case 1: there are 31 days in M1: (31-16)/2=7,5
Case 2: there are 30 days in M1: (30-16)/2=7
Case 3: there are 29 days in M1: (29-15)/2=7
Case 4: there are 28 days in M1: (28-15)/2=6,5
0
Otherwise Y2/M2/MIDDLE_DAY(M2) - Y1/M1/MIDDLE_DAY(M1) MONTH_BETWEEN (Y2/M2/MIDDLE_DAY(M2), Y1/M1/MIDDLE_DAY(M1)) / 12
M1, D1 Y1=Y2 ½ * (Y2/M2/D2 - Y1/01/01) 0
Y1<Y2 Y2/M2/D2 - Y1/07/02 MONTH_BETWEEN (Y2/M2/D2, Y1/07/02) / 12
M2, D2 Y1=Y2 ½ * (Y2/12/31 - Y1/M1/D1) 0
Y1<Y2 Y2/07/02 - Y1/M1/D1 MONTH_BETWEEN (Y2/07/02, Y1/M1/D1) / 12
D1, M2, D2 Y1=Y2 ½ * (Y2/12/31 - Y1/M1/MIDDLE_DAY(M1)) 0
Y1<Y2 Y2/07/02 - Y1/M1/MIDDLE_DAY(M1) MONTH_BETWEEN (Y2/07/02, Y1/M1/MIDDLE_DAY(M1)) / 12
M1, D1, D2 Y1=Y2 ½ * (Y2/M2/MIDDLE_DAY(M2) - Y1/01/01) 0
Y1<Y2 Y2/M2/MIDDLE_DAY(M2) - Y1/07/02 MONTH_BETWEEN (Y2/M2/MIDDLE_DAY(M2), Y1/07/02) / 12
M1, D1, M2, D2 Y1=Y2 ½ * (Y2/12/31 - Y1/07/02) [= 91]
Note: Since the outcome is constant, 91 can be used directly.
0
Y1<Y2 Y2/07/02 - Y1/07/02 MONTH_BETWEEN (Y2/07/02, Y1/07/02) / 12

Used by

  • Data loading – posting.
  • Tabulation master file

Appendix F – Auxiliary tables

This section describes all auxiliary tables used by several processes, namely:

  • Delete CCR ID;
  • Alternate surname;
  • Internal Record Linkage – Don't Link Cross Reference;
  • Death Clearance – Don't Link Cross Reference.

Appendix E – Interval and mean time between dates

Description

This table keeps a log of patient record deletions.

Content

  • CCR identification number: The CCR identification number of the deleted patient record.
  • Reporting province/territory: The reporting province/territory of the deleted patient record.
  • Patient identification number: The patient identification number of the deleted patient record.
  • Date of deletion: The date of the day the patient record was deleted or merged with another.
  • New CCR_ID: The CCR identification number of the remaining patient record when two patient records are merged through internal record linkage resolution.
  • Process: Code indicating which process has deleted the patient record. Possible values are:
    1. Data loading process through posting step.
    2. Internal record linkage through resolution step.

Usage

This table can be used to know how and when a patient record has been deleted. This is especially useful when providing feedback to PTCR about an input patient record that is rejected because the corresponding base patient record is not found on the CCR.

Used By

  • Data loading – posting
  • Internal record linkage
Revision (Appendix E – Interval and mean time between dates)
Year Description
Not applicable Not applicable

Alternate surname

Description

This table keeps a copy of other patient surnames used since a patient enters the CCR.

Content

  • CCR identification number: The CCR identification number of the patient.
  • Surname: Former surname used by the patient.

Usage

This table is used during record linkage activities to augment the chances of a link between two records. This is useful when a patient surname changed overtime. Generally speaking, an additional patient record is created for every alternate patient surname. Doing so will allow a better link between a jurisdiction that uses the former patient surname and another jurisdiction that uses the latter patient surname.

Used By

  • Data loading – posting;
  • Internal record linkage – Record explosion;
  • Death clearance process – Record explosion.
Revision (Alternate surname)
Year Description
Not applicable Not applicable

Internal Record Linkage – Don't Link Cross Reference

Description

This table keeps a log of potential duplicate patient record pairs that have been reviewed and rejected by PTCR through the Internal Record Linkage process.

Content

  • CCR Identification Number 1: The CCR Identification Number of the first patient.
  • CCR Identification Number 2: The CCR Identification Number of the second patient.
  • Resolution Date: The date when the Resolution step of the Internal Record Linkage process has run and has created the entry. (Format: YYYYMMDD)

Usage

This table is used during Internal Record Linkage process to avoid resending for review potential duplicate patient records that have been already reviewed and rejected by PTCR.

Used By

  • Data Loading – Posting;
Internal Record Linkage – Don't Link Cross Reference
Year Description
Not applicable Not applicable

Death Clearance – Don't Link Cross Reference

Description

This table keeps a log of Death Confirmation refused by PTCR through the Death Confirmation Refusal Process.

Content

  • CCR Identification Number: The CCR Identification Number of the patient.
  • Date of Death: The Date of Death as specified on the rejected Death Event (format: YYYYMMDD);
  • Place of Death: The Place of Death as specified on the rejected Death Event;
  • Death Registration Number: The Death Registration Numner as specified on the rejected Death Event
  • Refusal Date: The date when the Death Confirmation Refusal has been processed (Format: YYYYMMDD)

The Year of Death, the Place of Death and the Death Registration Number altogether create a key that uniquely identifies a Death Event.

Usage

This table is used during Death Clearance process to avoid resending for review Death Clearance Confirmation that have been already reviewed and rejected by PTCR.

Used By

  • Data Loading – Posting (Death Confirmation Refusal);
  • Internal Record Linkage – Resolution;
  • Death Clearance – Probabilistic Linkage.
Revision (Death Clearance – Don't Link Cross Reference)
Year Description
2004 Reporting Province and Patient Identification Number have been removed from this table since they are not part of the Patient Primary Key and were not maintained upon Patient Reversal of Ownership.

Appendix G – Guidelines for reporting grade, differentiation or cell indicator

Note: The CCR captures Grade for "invasive" tumours only beginning with January 1, 2004 data to accommodate grade collection in the CS Algorithm. These guidelines apply to January 1, 2006 data.

The CCR does not collect Grade for "in situ" tumours.

All CCR codes are based on the SEER codes as defined in the SEER Program Coding and Staging Manual 2004. The intent is to collect histopathologic grade however there are recognized anatomical site exceptions (for example, kidney) that apply other grading schemes.

Site Specific Grade Guidelines (page 4) take precedence over the General Coding RULES (page 2); use the General Coding Rules only when there are no Site Specific Grade Guidelines.

Grade, Differentiation (Codes 1, 2, 3, 4, 9)

Pathologic testing determines the grade, or degree of differentiation, of the tumour. For cancers, the grade is a measurement of how closely the tumour cells resemble the parent tissue (organ of origin). Well differentiated tumour cells closely resemble the tissue from the organ of origin. Poorly differentiated and undifferentiated tumour cells are disorganized and abnormal looking; they bear little or no resemblance to the tissue from the organ of origin.

Pathologists describe the tumour grade by levels of similarity. Pathologists may define the tumour by describing two levels of similarity (two-grade system); by describing three levels of similarity (three-grade system); or by describing four levels of similarity (four-grade system). The four-grade system describes the tumour as grade I, grade II, grade III, and grade IV (also called well differentiated, moderately differentiated, poorly differentiated, and undifferentiated/anaplastic). These similarities/differences may be based on pattern (architecture), cytology, or nuclear features or a combination of these elements depending upon the grading system that is used. The information from this data item is useful for determining prognosis.

Cell Indicator (Codes 5, 6, 7, 8, 9)

Describes the lineage or phenotype of the cell that became malignant. Cell indicator codes apply to hematopoietic malignancies (ICD-O-3 range 9590-9989) and for these diagnoses cell indicator takes precedence over grade/differentiation. Note: See the ICD-O-3 chapter Morphology (page 67)for further instructions on coding grade.

CCR Codes:

1 Grade I; grade i; grade 1; well differentiated; differentiated, NOS
2 Grade II; grade ii; grade 2; moderately differentiated; moderately well differentiated; intermediate differentiation
3 Grade III; grade iii, grade 3; poorly differentiated; dedifferentiated
4 Grade IV; grade iv; grade 4; undifferentiated; anaplastic
5 T-cell; T-precursor
6 B-Cell; Pre-B; B-precursor
7 Null cell; Non T-non B
8 NK cell (natural killer cell) (effective beginning with diagnosis 1/1/1995)
9 Grade/differentiations unknown, not stated, or not applicable

GENERAL CODING RULES

  1. If there is any confusion relating to grade, we strongly recommend consulting the pathologist for confirmation.

    Example: To determine grade when there are multiple pathology consults.
  2. The site-specific coding guidelines (pages 4-9) include rules for coding grade for the following primary sites: breast, kidney, prostate, CNS, lymphoma, leukemia and sarcoma.
  3. Code the grade from the final diagnosis in the pathology report. If there is more than one pathology report, and the grades in the final diagnoses differ, code the highest grade for the primary site from any pathology report.
  4. If grade is not stated in the final pathology diagnosis, use the information in the microscopic section, addendum, or comment to code grade.
  5. If there is no tissue diagnosis (pathology or cytology report), code the grade from the Magnetic Resonance Imaging (MRI) or Positron Emission Tomography (PET).
  6. If more than one grade is recorded for a single tumour, code the highest grade, even if it is a focus.

    Example: Pathology report reads: Grade II adenocarcinoma with a focus of undifferentiated adenocarcinoma. Code the tumour grade as grade 4, CCR Code 4.
  7. Code the grade information from the consultation or tumour board round if the specimen is sent to a specialty pathology department for a consult.
  8. Code the grade from the primary tumour only, never from a recurrence or metastatic site (distant and/or regional) even if this is theonly reference to grade that you have.
  9. Code the grade for all unknown primaries to 9 (unknown grade) unless grade is implied by histology (i.e. anaplastic carcinoma (grade = 4).
  10. Some terms in ICD-O-3 carry an implied statement of grade. These histologies must be reported with the correct grade as stated below even if the primary site is unknown:
    8020/34 Carcinoma, undifferentiated
    8021/34 Carcinoma, anaplastic
    8331/31 Follicular adenocarcinoma, well differentiated
    9082/34 Malignant teratoma, undifferentiated
    9083/32 Malignant teratoma, intermediate type
    9401/34 Astrocytoma, anaplastic
    9451/34 Oligodendroglioma, anaplastic
    9511/31 Retinoblastoma, differentiated
    9512/34 Retinoblastoma, undifferentiated
  11. Code the grade of the invasive component when the tumour has both in situ and invasive portions. If the invasive component grade is unknown and in situ is graded, code the grade as unknown (9). Note: The CCR does not capture grade for in situ (high dysplasia) cases.
  12. If a patient receives pre-operative systemic treatment for example, chemotherapy, radiotherapy, hormonal etc), code grade:
    – from a pre-treatment pathology report, if available.
    –after pre-operative systemic treatment if this is the only grade information available.

SITE SPECIFIC GRADE GUIDELINES

If the site specific guidelines do not apply or only limited information is available, then refer to the Common Grading Systems tables (page 10) and the Terminology (Four Grade) Conversion Table (page 11).

Exception: Cell indicator takes precedence over grade/differentiation for lymphomas and leukemias.

Breast Cancer

Priority Order for Coding Breast Cancer Grade Code grade in the following priority order (See following table):

  1. Bloom-Richardson (BR) scores 3-9 converted to grade
  2. Bloom Richardson (BR) grade (low, intermediate, high)
  3. Terminology
    a. Differentiation (well differentiated, moderately differentiated, etc)
  4. Histologic grade (Breast Grade NOS, invasive cancer, histologic grade is implied).
    a. Grade 1/I/i, grade 2/II/ii, grade 3/III/iii, grade 4/IV/iv

Note: The conversion of low, intermediate, and high grade for breast is different from the conversion used for all other tumours. Do not use three-grade conversion for breast primaries (see page 10).

Breast Grading Conversion Table
BR Scores BR Grade Terminology Histologic Grade CCR Code
3, 4, 5 Low Well differentiated I/III; 1/3 1
6, 7 Intermediate Moderately differentiated II/III; 2/3 2
8, 9 High Poorly differentiated III/III; 3/3 3

Bloom-Richardson (BR)

  1. BR may also be called: modified Bloom-Richardson, Scarff-Bloom-Richardson, SBR grading, BR grading, Elston-Ellis modification of Bloom Richardson score, the Nottingham modification of Bloom Richardson score, Nottingham-Tenovus, or Nottingham grade
  2. BR may be expressed in scores (range 3-9)The score is based on three morphologic features of "invasive no-special-type" breast cancers (degree of tubule formation/histologic grade, mitotic activity, nuclear pleomorphism of tumour cells)
  3. BR may be expressed as a grade (low, intermediate, high)
  4. BR grade is derived from the BR score
  5. Use the Breast Grading Conversion Table above to convert the score, grade or terminology into the CCR code

Kidney Cancer

Fuhrman grade describes the nucleus of the cell. If Fuhrman grade is not specified, nuclear grade has second priority.For kidney, nuclear grade is more important (priority) than looking at the overall histologic grade of the tumor.

Note: Use the general coding rules for coding grade for Wilms tumour (8960) as these prioritization rules do not apply.

Priority Order for Coding Kidney Cancer Grade

Code grade in the following priority order:

  1. Fuhrman grade (grade 1, 2 ,3 ,4)
  2. Nuclear grade (grade 1, 2, 3, 4)
  3. Terminology (well diff, mod diff)
  4. Histologic grade (grade 1, grade 2)
Fuhrman Conversion Table
Grade Differentiation or Descriptor CCR Code
Grade i Well differentiated 1
Grade ii Moderately differentiated 2
Grade iii Poorly differentiated 3
Grade iv Undifferentiated 4

Prostate

Nuclear grade is not equivalent to any part of the Gleason grading process (cannot be converted from Gleason's Score or Pattern).

Priority Rules for Coding Prostate Cancer Grade

Code grade in the following priority order:

  1. Gleason's Grade (score or pattern)
  2. Terminology
    a. Differentiation (well differentiated, moderately differentiated, etc.)
  3. Histologic grade
    a. Grade 1/I/i, grade 2/II/ii, grade 3/III/iii, grade 4/IV/iv

Use the following table to convert Gleason's pattern or score into CCR codes:

Gleason Conversion Table
Gleason's Score (Gleason's Grade) Gleason's Pattern Terminology Histologic Grade CCR Code
2, 3, 4 1, 2 Well differentiated I 1
5, 6 3 Moderately differentiated II 2
7, 8, 9, 10 4, 5 Poorly differentiated III 3

Note: if Gleason's score or pattern is not specified, see examples below:

Gleason's Pattern

Prostate cancers are commonly graded using Gleason's score or pattern. Gleason's grading is based on a 5-level system, meaning it is based on 5 histologic patterns. The pathologist will evaluate the primary (majority) and secondary patterns for the tumour. The pattern is usually written as a sum, with the majority pattern appearing first and the secondary pattern as the second number.

Example: A Gleason pattern of 2 + 4 means that the primary pattern is 2 and the secondary pattern is 4.

Gleason's Score

The patterns are added together to create a score.

Example: If the pattern is 2 + 4, the score is 6 (the sum of 2 and 4).

When reviewing prostate grading terminology and attempting to determine whether it represents a grade or a score, consider the following results:

  • less than or equal to 5 are coded as a pattern and
  • more than 5 are coded as a score.
  1. If the pathology report contains only one number, and that number is less than or equal to 5, it is a pattern. Please see General Coding Rule 1.
  2. If the pathology report contains only one number, and that number is greater than 5, it is a score. Please see General Coding Rule #1.
  3. If the pathology report specifies a specific number out of a total of 10, the first number given is the score.

    Example: The pathology report says "Gleason's 3/10". The Gleason's score would be 3.
  4. If there are two numbers less than 6, assume they refer to two patterns. The first number is the primary pattern and the second is the secondary pattern.

    Example: If the pathology report says "Gleason's 3 + 5," the Gleason's score would be 8, the sum of 3 and 5.

Central Nervous System

  1. WHO grading forbrain is used to estimate prognosis and can refer to both benign and malignant lesions. It is never coded in the 6th digit of the histology code.
    a. WHO grade is captured in Collaborative Stage Site Specific Factor 1.
  2. Pathologists do not always describe ICD-O-3 grade or differentiation of CNS tumors.a. If no grade is given, code the 6th digit histology code to ‘9' unknown.
    b. Some histologies include/imply grade in the terms; in these cases the grade can be coded (for example, anaplastic astrocytoma 9401/34). SeeGeneral Coding Rule 10.
  3. Do not automatically code glioblastoma multiforme as grade IV, if no grade is given, code to ‘9' unknown. (9440/39).
  4. All glioma's with histology 938-946 with the exception of those with an implied grade are ‘9' not applicable.
  5. Grade astrocytomas according to ICD-O-3 rules. Do not use the WHO grade to code this field.

Lymphoma and Leukemia 9590-9989

  1. The designation of T-cell, B-cell, null cell, or NK cell has precedence over any statement of differentiation.
    a. Code ANY statement of T-cell, B-cell, null cell, or NK cell including:
    T-cell (code 5)
    Cortical T
    Mature T
    Pre-T
    Pro-T
    T-cell phenotype
    T-precursor
    B-Cell (code 6)
    B-cell phenotype
    B-precursor
    Pre-B
    Pre-pre-B
    Pro-B
    Null-Cell; Non-T-non-B (code 7)
    Null-cell
    Non T-non-B
    Common cell
    NK (Natural Killer) cell (code 8)
    NK/T cell
    Cell type not determined, not stated or not applicable (code 9)
    Combined B cell and T cell

    Note: The ‘code to the higher code' rule usually does not apply to phenotypes.

    b. Code information on cell type from any source, whether or not marker studies are documented in the patient record.

    Example: The history portion of the medical record documents that the patient has a T-cell lymphoma. There are no marker studies on the chart. Code the grade as T-cell.
  2. Do not use the terms "high grade," "low grade," and "intermediate grade" to code differentiation or Cell Indicator field. These terms refer to prognosis, not grade.
    a. In some instances, the term ‘grade' does not imply differentiation and should not be used to code the 6th digit of the morphology code. It is important to recognize when the term "grade" refers to category and when it refers to biologic activity. When describing some diseases, pathologists use the term "grade" as a synonym for "type" or "category." Registrars recognize the term "grade" as an indicator of cell differentiation that is coded in the 6th digit of the ICD-O morphology code.
    i. The grade descriptors for nodular sclerosing Hodgkin lymphoma and follicular lymphoma are actually types or categories of these diseases. The 6th digit should not be coded as grade 1, 2 or 3 for these cases.
    ii. Poorly differentiated lymphocytic lymphoma or a B-cell or T-cell lymphoma should be coded in the 6th digit of the morphology code.
    iii. Other terms described as high grade or low grade as part of the diagnostic term may be used to code the 6th digit of the morphology code.
  3. Do not code the descriptions "Grade 1," "Grade 2," or "Grade 3" in the Grade, Differentiation or Cell Indicator field.
  4. Codes 9950-9989 rarely have a grade associated with them and are generally coded as a ‘9'.
  5. Grade codes 5-8 are T-cell, B-cell, or NK cell indicators used for leukemias and lymphomas only. Therefore, codes 5-8 may only be used with morphologies in the range of 9590-9989.

Sarcoma

Several grading systems exist and may be used to grade sarcomas. The following table incorporates two, three and four-tier grading systems. If a sarcoma is graded using terminology, refer to the Terminology Conversion Table on page 11.

Gleason Conversion Table
Grade Differentiation or Descriptor CCR Code
Low Grade 1/2 1/3 1/4 2/4 2
Intermediate Grade 2/3 3
High Grade 2/2 3/3 3/4 4/4 4

Common Grading Systems

Two-Grade System

There are some cancers for which a two-grade system is used (i.e. colon cancer, papillary transitional cell carcinoma, bladder, endometrial stromal sarcoma). The patterns of cell growth are measured on a scale of 1 or 2 (also referred to as low and high grade). The expected outcome is more favorable for lower grades.

  • If the grade is listed as 1/2 or as low grade, assign code 2.
  • If the grade is listed as 2/2 or as high grade, assign code 4.
Two-Grade Conversion Table
Grade Differentiation /
Description
CCR Code
1/2, I/II Low grade 2
2/2, II/II High grade 4

Three-Grade System

There are several cancers for which a three-grade system is used (for example peritoneum, endometrium, fallopian tube, prostate, bladder and soft tissue sarcoma). The patterns of cell growth are measured on a scale of 1, 2, and 3 (also referred to as low, medium/intermediate, and high grade). This system measures the proportion of cancer cells that are growing and making new cells and how closely they resemble the cells of the host tissue. Thus, it is similar to a four-grade system (see Terminology Conversion Table on page 10), but simply divides the spectrum into 3 rather than 4 categories (see Three-Grade Conversion Table below). The expected outcome is more favorable for lower grades.

  • If the grade is listed as1/3 or as low grade, assign code 2.
  • If the grade is listed as 2/3 or as medium/intermediate grade, assign code 3.
  • If the grade is listed as 3/3 or as high grade, assign code 4.

Use the following table to convert the grade to CCR codes:

Three-Grade Conversion Table*
Grade Differentiation /
Description
CCR Code
1/3, I/III Low grade 2
2/3, II/III Medium/Intermediate grade 3
3/3, III/III High grade 4

*Do not use for breast primaries

Terminology Conversion Table
This system measures the proportion of cancer cells that are growing and making new cells and how closely they resemble the cells of the host tissue. The expected outcome is more favorable for lower grades.

Terminology Conversion Table
Description Grade CCR Code
Differentiated, NOS I 1
Well differentiated I 1
Fairly well differentiated II 2
Intermediate differentiation II 2
Low grade I-II 2
Mid differentiated II 2
Moderately differentiated II 2
Moderately well differentiated II 2
Partially differentiated II 2
Partially well differentiated I-II 2
Relatively or generally well differentiated II 2
Medium grade, intermediate grade II-III 3
Moderately poorly differentiated III 3
Moderately undifferentiated III 3
Poorly differentiated III 3
Relatively poorly differentiated III 3
Relatively undifferentiated III 3
Slightly differentiated III 3
Dedifferentiated III 3
High grade III-IV 4
Undifferentiated, anaplastic, not differentiated IV 4
Non-high grade 9

References:

  1. SEER Program Coding and Staging Manual (2004) Published by the U. S. Department of Health & Human Services (Bethesda, MD), 2004. NIH Publication Number 04-5581.
  2. International Classification of Diseases for Oncology, Third Edition. WHO.
  3. NAACCR Edit Logic Report for Metafile NAACR10E.EMF
  4. Centers for Disease Control and Prevention. Data collection of primary central nervous system tumors. National Program of Cancer Registries Training Materials. Atlanta, Georgia: Department of Health and Human Services, Centers for Disease Control and Prevention, 2004.
Revision (Terminology Conversion Table)
Year Description
2006 New appendix

Appendix H – CCR Ambiguous Terms

Effective for January 1, 2001 data and forward

The Data Quality Management Committee, with the approval of the CCCR, recommends that the SEER Program list4 of ambiguous terms be adopted as the Canadian list when identifying cancer cases5. Where possible, it is best to obtain additional information or consult with a pathologist for clarification. If neither is possible, use the following list for determining whether to register/report a cancer case to the CCR.

Appendix H – CCR Ambiguous Terms
Consider as diagnostic of cancer NOT considered diagnostic of cancer*
apparent(ly) cannot be ruled out
appears to equivocal
comparable with possible
compatible with potentially malignant
consistent with questionable
favor(s) rule out
malignant appearing suggests
most likely worrisome
presumed
probable
suspect(ed)
suspicious (for)
typical of * without additional information
Exception:
If cytology is reported as "suspicious", do not
interpret this as a diagnosis of cancer.
Abstract the case only if a positive biopsy
or a physician's clinical impression of cancer supports the cytology findings.
Do not include patients who have a diagnosis consisting only of these terms.
Revision (Appendix H – CCR Ambiguous Terms)
Year Description
2006 New appendix

Appendix I – Guidelines for Abstracting and Determining Death Certificate Only (DCO) Cases for Provincial/Territorial Cancer Registries (PTCRs) in Canada (for T12 and P18)

Cancer registries have identified access to death information as a critical component for operating a high quality program. There are two main reasons for acquiring this particular data, including:

  1. Determination of Death Status for Currently Enrolled Cases: Once a registry has enrolled a case of cancer the addition of death information can provide a more complete picture of how cancer has impacted this individual. Death information on a specific case can remove it from active follow up routines and allow registries to perform more accurate and complete survival calculations.
  2. Case Completeness: To ensure a high level of case completeness a registry typically relies on a variety of methods to ascertain newly diagnosed cancers. One common method is to complete a linkage to vital statistics information regarding cause(s) of death. If an individual is reported with a cancer cause of death and is not found in the registry the case should be followed back to determine if it meets the criteria for cancer registration.

Therefore it is important that PTCRs enter into agreements with Vital Statistics registrars to receive at a minimum all cases for which cancer is listed on any part of the medical certificate of death. In Canada death registration is subject to provincial mandates and includes the completion of a Statement of Death and/or a Medical Certificate of Death. Cancer registries receive death notifications in various formats i.e., hardcopy, electronically, or computer files and at varying intervals for example, monthly, quarterly or annually.

The ideal is to receive notification of all deaths including all causes of death occurring within the province, enabling the registry to perform a comprehensive death clearance. When linked with the registry database this information will result in both matched and non-matched cancer incidence. A death certificate with a reportable tumour listed that does not link to other records in the cancer registry is called a Death Certificate Notification (DCN) and requires further investigation. DCNs include cases in which the underlying cause of death is cancer as well as cases in which cancer is simply mentioned on the death certificate. When additional information is obtained the case should be registered with that year's incidence data. If additional information cannot be obtained, the case is a true Death Certificate Only (DCO) and can be reported as such to the Canadian Cancer Registry (CCR).

Death certificate information is a critical component in the registry certification process operated by the North American Association of Central Cancer Registries (NAACCR). To be eligible for NAACCR certification a PTCR must participate in the NAACCR Call for Data. The data criteria reviewed during this process include: Completeness, passing EDITS, DCO, Interval for Criteria, Timeliness, Duplicate Reports and Missing Data Fields in Sex, Age, County and Race. The DCO certification requirement is less than 5% silver and less than 3% gold.

The CCR and NAACCR accepted formula for calculating the DCO rate is:

The CCR and NAACCR accepted formula for calculating the DCO rate is:

Differences exist in the denominator as CCR does not include in situ bladder cancers and NAACCR does.Where cancer cases = all unduplicated invasive cancers + in situ bladder cancers within the diagnosis year for state (provincial) residents. These include all cases identified and abstracted from the death clearance project and all true DCOs. This information is included in the NAACCR Call for Data.

(Source: NAACCR Series II: Calculating the DCO Rate)

1. Definitions

Cause of Death

The causes of death to be entered on the medical certificate of cause of death are all those diseases; morbid conditions or injuries which either resulted in or contributed to death and the circumstances of the accident or violence which produced any such injuries.

(Source: World Health Assembly, Article 23 of the Constitution of the World Health Organization. ICD-9 pg. 763)

Death Certificate Notification (DCN)

Death certificate notification is a cancer death identified from any source including a Vital Statistics Death Registration that could not be linked (electronically or manually) to an existing cancer record.

Death Certificate Only (DCO)

"Death certificate only" means that the only source of information about the case was a death certificate. This category includes deaths where either the Underlying Cause of Death is cancer, or there is any mention of cancer on the death certificate.
(Source: CCR – Report No. 3.2.2. – Input Data Dictionary, page 79. Revised on: 17/06/94.)As of January 1, 2000 mortality information in Canada was captured by Vital Statistics using the ICD-10 classification system.

Follow Back (FB)

Followback is the process of actively searching for additional information on DCNs at the patient and disease level and updating the cancer database as a complete abstract when possible. If additional information cannot be found the case is a true DCO.

Underlying Cause of Death

The underlying cause of death is (a) the disease or injury which initiated the train of events leading directly to death, or (b) the circumstances of the accident or violence which produced the fatal injury.

(Source: World Health Assembly, Article 23 of the Constitution of the World Health Organization. ICD-9 pg. 763)

2. Process

The process for determining a DCO case will vary and should be modified to meet the requirements of the individual PTCRs. PTCRs should match DCNs to their database; those cancer deaths that do not match require further investigation. Processing is required when the decedent was a resident of your province at the time of death, and a reportable cancer is mentioned on the DCN and no record is found in the PTCR database. No further processing is required when the only tumour mentioned on the DCN is a non-reportable tumour, the decedent was a non-resident of your province (forward to province of ownership if agreements are in place) or when a non-cancer death is identified.

The underlying cause of death field is intended to capture a patient's official cause of death. As this variable is important for record linkage purposes and has legal implications, the death information coded and provided to cancer registries from provincial and territorial Vital Statistics offices should not be altered even when cancer registries have more complete or detailed diagnostic information. The only PTCR reported data that may be changed on the CCR patient record because of a confirmation of death are: Date of Death, Province/Country of Death and Death Registration Number.
(Source, CCR – Report No. 3.2.1 – Coding and Reporting Guidelines – December 18, 1995)

A. DCN Match to Provincial/Territorial cancer registry database. (Example: positive match on four variables for example, HIN, Surname, Sex and DOB).

  • Determine same primary versus new primary.
  • Identify discrepancies between cancer on certificate of death and registry diagnosis codes.
  • Update missing or incomplete fields.

An inconclusive Match shows some discrepancies between identifiers in the incidence and death data but the records may belong to the same person. (Example: positive or close match on the four variables for example, HIN positive match, mismatch with surname, sex or DOB.

  • Visual verification to determine if it's "close enough" to be judged a match or non-match.
  • FB to make a valid determination.

Followback (FB) for new primaries or abstract for additional DCO primaries. Edit and review cases in registry database not microscopically confirmed.

B. DCO. DCN cancer death, Non-match to Provincial/Territorial cancer registry database.
Nonmatched cancer deaths are cleared in a variety of ways, depending on the PTCR's ability to staff a DCO clearance program. Each non-match cancer death must be manually reviewed for reportability and to ascertain where to follow back. Followback sources include facility (chronic care, hospital/nursing home), coroner and attending physician where the death occurred.

Based upon the information received from follow back, the case may be abstracted as:

  • FollowBack is recommended by form letter to the institution (Appendix A) where the patient expired and secondly to the informant (Appendix B) who signed the death certificate to obtain additional information.
  • Cases that are identified after followback should be added to the appropriate diagnosis year as actual incident records (not DCOs).
  • Cases where no additional information is obtained should be reported to the CCR as a DCO.

C. Standard conventions for abstracting DCO cases:

  1. If FB is not returned from facility/physician, the information from the DCN may be used and the case considered a DCO.
  2. If a date of diagnosis or an approximate date cannot be established, the case is a DCO and the date of death is used as the date of diagnosis.
  3. Follow standard coding conventions for site/histology.
  4. There may be more than one primary noted on the Death Certificate. More than one DCO abstract may be required.
  5. Code the histology from the Death Certificate, i.e., squamous cell carcinoma, adenocarcinoma, etc., if available. If "carcinoma" is recorded, code as 8010/3. If "cancer" is recorded, code as 8000/3.
  6. Code the Primary Site recorded on the Death Certificate, i.e., lung, prostate, breast.
  7. Melanoma, unknown primary site code to Malignant melanoma of skin, site unspecified (ICD-9 172.9, ICD-10 C43.9).
  8. Lymphoma, unknown primary site code to Lymph Nodes, NOS (ICD-9 202.8, ICD-10 C85.9).
  9. Leukemia is always coded to Bone Marrow (1CD-9 208.9, ICD-10 C95.9).
  10. Watch for primary sites where metastases are common (Lung, Liver, Brain and Bone).
  11. The death certificate may state "metastatic liver cancer" or "metastatic bone cancer". If it is unclear if the site recorded is the primary or a metastatic site, code to Unknown Primary Site (ICD-9 199.0, ICD-10 C80.9).
  12. Stage is always "unknown".
  13. Diagnostic confirmation is always "unknown".
  14. No treatment is recorded, even if noted on the DCN.
  15. Include DCO cases in edits.

(Cover letter to Institution)

PTCR

Inside address

To Whom It May Concern

The Registry Name is presently completing the Death Certificate Only (DCO) follow back process for year/s. DCO means that the only source of information about the case was a death certificate. The death certificate identified the decedent as having expired in your facility however the cancer registry has no prior information on this case through its routine data collection. Data collection is legislated by act/privacy act. Enclosed you will find a Registry Form letter for completion, it is important that we collect the initial date and address at time of diagnosis. If, your records do not identify this patient as having cancer please indicate and we will adjust our records accordingly.

By completing the enclosed Registry Form letter we can finalize the information on this patient. Complete information permits the calculation of survival rates on patients diagnosed with cancer, facilitates epidemiological studies and improves the completeness and quality of reported death and other demographic information. Your continued support in improving the quality of data allows us to participate in provincial and national studies and to provide accurate statistics on an ongoing basis to our stakeholders.

If there are any questions or concerns, please do not hesitate to contact me, contact name at facility name and phone number.

Sincerely yours,

Signature

Enclosure

(Cover letter to Informant)

PTCR

Inside address

Dear Insert name here,

The Registry Name is presently completing the Death Certificate Only (DCO) follow back process for year/s. DCO means that the only source of information about the case was a death certificate. The death certificate stated the decedent had cancer, however the cancer registry has no prior information on this case through its routine data collection. Data collection is legislated by act/privacy act. The death certificate identifies you as the last attending physician at time of death for patient name. Enclosed you will find a Registry Form letter for completion, it is important that we collect the initial date and address at time of diagnosis. If, your records do not identify this patient as having cancer please indicate and we will adjust our records accordingly.

By completing the enclosed Registry Form letter we can finalize the information on this patient. Complete information permits the calculation of survival rates on patients diagnosed with cancer, facilitates epidemiological studies and improves the completeness and quality of reported death and other demographic information. Your continued support in improving the quality of data allows us to participate in provincial and national studies and to provide accurate statistics on an ongoing basis to our stakeholders.

If there are any questions or concerns, please do not hesitate to contact me, contact name at facility name and phone number.

Sincerely yours,

Signature

Enclosure

Death Certificate Notification (DCN)
Year Description
2007 New appendix

Appendix J – Interval between two dates (complete or partial)

The following algorithm can be used to assess the number of days between two dates. When both dates are complete, the algorithm returns the exact number of days. When one or both dates are partial, the missing parts of the dates are "derived" and the number of days returned, based on the derived dates. This algorithm cannot be used if one or more dates is totally unknown, i.e. equal to '99999999'. The returned value is always a positive whole number (including zero).

Definitions

Let Date1 and Date2 be the two dates for which the interval must be calculated and where Date1 <= Date2.

Let Y1, M1 and D1 be the year, month and day of date1.
Let Y2, M2 and D2 be the year, month and day of date2.

Let DIFF_DAYS (Date1, Date2) be a function that returns the number of days between date1 and date2.

Assumptions if there are partial dates
Date1 is a partial date Date2 is a partial date
If MONTH is not reported then MONTH is assumed to be '01'.
If DAY is not reported then DAY is assumed to be '01'.
If MONTH is not reported then MONTH is assumed to be '12'.
If DAY is not reported then DAY is assumed to be the last day of the reported MONTH (28, 29, 30 or 31).

Examples

Date1 = 20060627.
Date2 = 20060930.

DIFF_DAYS (20060627, 20060930)

Date1 = 20060699
Date2 = 20070999.

DIFF_DAYS = (20060601, 20070930)

Date1 = 20069999
Date2 = 20079999

DIFF_DAYS = (200601, 20071231)

Appendix J – Interval between two dates (complete or partial)
Year Description
2008 New appendix

Appendix T – Residency guidelines in Canada

To ensure comparability of definitions of cases and the population at risk (numerator and denominator), the Canadian Cancer Registry (CCR) rules for determining residency at time of diagnosis are to be identical or comparable to rules used by the Canadian Census Bureau, whenever possible.

The residence at diagnosis is generally the place of usual residence, as stated by the patient or, as stated by the Census Bureau, ‘the dwelling in Canada where a person lives most of the time'. Residency is their usual place of residence, regardless of where they are when diagnosed. For patients with multiple tumours, the address may be different for each primary tumour.

There are a number of situations for which the process of determining residency is not intuitive, and special guidelines have been created in order to define an individual's usual place of residence. The Data Quality Committee (DQC) for the Canadian Council of Cancer Registries (CCCR) recognizes that some Provincial/Territorial Cancer Registries (PTCRs) are removed from the direct patient contact relationship, and may not have access to the patient or the information to confirm residency. Using the provincial health insurance number (HIN) as a determining factor of residency during initial case abstraction is appropriate. When permanently relocating, the HIN from the previous province of residence is valid for three months. However, if the case is identified as a potential duplicate during a Record Linkage cycle, additional information should be obtained before confirming residency, as it may not be appropriate to default to using province of HIN, as the primary residence.

PTCRs are encouraged to use these guidelines to determine residency for categories of persons for whom residence is not immediately apparent.

  1. Residence (one residence). The dwelling in Canada where a person lives most of the time.
  2. Persons with more than one residence. Usual residence rule applies; however, if the time spent at each residence is equal or the abstractor is not sure which one to choose, the residence where the patient was staying on the day cancer was diagnosed should be considered the usual place of residence (see examples below). a) Exception: Consider the residence shared with their family as their usual place of residence, even if they spend most of the year elsewhere.
    Commuter workers living away part of the week while working: Consider the residence shared with their family as the usual place of residence, even if they spend most of the year elsewhere. (for example, parents, husbands, wives or common-law partners)
    b) Snowbirds: People who live at another residence (city, province or country) with a warmer climate. Residence should be documented as where they live most of the time.
    c) Children in joint custody: Residence should be documented as where they live most of the time. If time is equally divided, their residence is documented as where they were staying on the day cancer was diagnosed.
  3. Patients with rural addresses. If the information provides a rural address only, which may be the post office box, record the address as stated, but make every attempt, within your resources, to identify the actual physical place of residence at time of diagnosis.
  4. Patients with no usual place of residence (i.e. homeless, transient people). Residents who do not have a usual place of residence should be documented as where they were staying on the day cancer was diagnosed.
  5. Institutional collective dwellings (Collective dwellings that provide care or assistance services). Persons in institutions with no other usual place of residence elsewhere in Canada, or persons who have been in one or more institutions for a continuous period of six months or longer, are to be considered as usual residents of the institution.
    Institutional collective dwellings include:
    a) Residents of a long-term care facility, a hospital, or a home for the aged.
    b) In homes, schools, hospitals, or wards for the physically disabled, mentally challenged, or mentally ill or in drug/alcohol treatment facilities.
    c) Inmates of correctional institutions, including prisons, jails, detention centers, or halfway houses.
    d) Children in juvenile institutions, such as residential care facilities for neglected or abused children or orphanages.
    e) For abused women, or for runaway or neglected youth please see section 6 - Non-institutional collective dwellings.
  6. Non-institutional collective dwellings (Collective dwellings that do not provide care or assistance services). Residence should be documented as their usual residence, if they report one (the place where they live most of the time) or otherwise at the inn, hotel, etc.
    Non-institutional collective dwellings include:
    a) Inns, hotels, motels and hostels.
    b) YMCAs/YWCAs, or public or commercial campgrounds.
    c) Military bases.
    d) Migrant workers (lumber / mining camps & farms).
    e) Members of religious orders in monasteries or convents.
    f) Shelters with sleeping facilities for people without housing, for abused women, or for runaway or neglected youth. Residence should be documented as the shelter.
  7. Students. Students who live away from home while attending school, but who return to live with their parents part of the year should consider their place of residence as their parents' home, even if they spend most of the year elsewhere.
  8. Live-ins:
    a) Live-in nannies. Residence should be documented as where they live most of the week.
    b) Foster children, boarders or housemates. Residence should be documented as where they are living at time of diagnosis.
  9. Merchant and coast guard vessels. Merchant vessels, coast guard vessels and oil rigs at sea should be documented as their usual onshore residence, if they report one (the place where they live most of the time when they are onshore) or otherwise, at their vessel's homeport.
  10. Naval vessels. Canadian Forces Naval Vessel residence should be documented as their usual onshore residence, if they report one (the place where they live most of the time when they are onshore) or otherwise, at their vessel's homeport.
  11. Armed forces. Canadian Armed Forces residence should be documented as their usual place of residence, if they report one, or otherwise, where they are stationed at time of diagnosis.
  12. Non-permanent residents (foreign citizens). Persons who hold a student or employment authorization, Minister's permit or who were refugee claimants at time of diagnosis, for a continuous period of six months or more.
    a) Citizens of foreign countries who have established a household or are part of an established household in Canada while working or studying, including family members with them. Residence should be documented as their household in Canada.
    b) Citizens of foreign countries who are living in Canadian embassies, ministries, legations or consulates. Residence should be documented as the embassy.
    c) Citizens of foreign countries temporarily traveling or visiting Canada. These cases are not reportable to the Canadian Cancer Registry.

Appendix X – CCR_ID check digit routine

The last digit of the CCR_ID is a check digit, for example, digit calculated from the other CCR_ID digits. The purpose of using a check digit is twofold: it allows the detection of some data corruption and prevents one from creating new IDs too easily. The next routine returns a check digit for a given CCR_ID.

Pseudo code


Let N1 be the first digit of CCR_ID (starting from the left)
Let N2 be the second digit of CCR_ID (starting from the left)
Let N8 be the eighth digit of CCR_ID (starting from the left)

Change the values of N2, N4, N6, N8 according to the following pattern
 
Initial value 0 1 2 3 4 5 6 7 8 9
New value 0 2 4 6 8 1 3 5 7 9


Let REMAINDER be the remainder of ((N1 + N2 + N3 + N4 + N5 + N6 + N7 + N8) / 10)
If REMAINDER = 0 then
RETURN 0
Else
RETURN (10 – REMAINDER)

Used by

  • Data loading – Edit
  • Data loading – posting

Appendix Z – References

Collaborative Staging Task Force of the American Joint Committee on Cancer. Collaborative Staging Manual and Coding Instructions, Version 01.04.01. Jointly published by American Joint Committee on Cancer (Chicago, IL) and U.S. Department of Health and Human Services (Bethesda, MD), 2004. NIH Publication Number 04-5496.
http://www.cancerstaging.org/cstage/index.html

Fritz A, Percy C, Jack A, et al (eds): ICD-O: International Classification of Diseases for Oncology, Third Edition. Geneva, World Health Organization, 2000.

SEER Program Coding and Staging Manual 2004, Surveillance, Epidemiology and End Results (SEER) Program, National Cancer Institute, National Institutes of Health, Bethesda, MD. NIH Publication Number 04-5581.

SEER Program Coding and Staging Manual 2007, Surveillance, Epidemiology and End Results (SEER) Program, National Cancer Institute, National Institutes of Health, Bethesda, MD. NIH Publication Number 07-5581.

Johnson CH, Peace S, Adamo P, Fritz A, Percy-Laurry A, Edwards BK. The 2007 Multiple Primary and Histology Coding Rules. National Cancer Institute, Surveillance, Epidemiology and End Results Program. Bethesda, MD, 2007. Revised April 30, 2008

NAACCR Standards for Cancer Registries, Volume II Version 11.3 - Data Standards and Data Dictionary, Thirteenth Edition.

National Cancer Institute Surveillance Epidemiology and End Results training website, American Joint Committee on Cancer. http://www.training.seer.cancer.gov/
module_staging_cancer/unit03_sec03_part00_ajcc.html

CCCR Committee on Data and Quality Management - Clinical Core Data Set - March 2001 version

AJCC Cancer Staging Manual, 6th Edition, American Joint Committee on Cancer (AJCC), 2002

Facility Oncology Registry Data Standards (FORDS), revised for 2007. Published by the American College of Surgeons (ACoS) and the Commission on Cancer (COC), 2007.

Facility Oncology Registry Data Standards (FORDS) manual, revised for 2009. Published by the American College of Surgeons (ACoS) and the Commission on Cancer (COC), 2009.

Footnotes

1.The original set of ISO codes has been expanded to include individual Canadian provinces and territories and other Statistics Canada specific codes.

2. Available upon request.

3.The only source of information about the case was a death certificate. This category includes deaths where either the underlying cause of death (patient record, Field No.17) is cancer, or there is any mention of cancer on the death certificate.

4. Input records that passed successfully through all validation edits, correlation edits and other match edits.

5. Because CS and AJCC TNM data items are fairly new to CCR, it has been temporarily decided that CS and AJCC TNM errors (including fatal errors)will not prevent valid core data items from being loaded on the CCR database

6. See Appendix A – Core reference tables - ICD-9 to ICD-O-2 conversion table for details.

7. See P1 Specific values & meaning.

8. See Appendix X - CCR_ID check digit routine.

9. See P4 Specific values & meaning.

10. See P5 Specific values & meaning.

11. See P10 Specific values & meaning.

12. See Appendix A – Core reference tables.

13. See Appendix – Core reference tables.

14. See P18 Specific values & meaning.

15. See T1 Specific values & meaning.

16. See Appendix X – CCR_ID check digit routine.

17. See T5 Specific values & meaning.

18. See T11 Specific values & meaning.

19. See T13 Specific values & meaning.

20. See T14 Specific values & meaning.

21. See T17 Specific values & meaning.

22. See T19 Specific values & meaning.

23. Eligible ICD-O-3 histology codes do not include ‘0000' since this value should have been converted to a more meaningful value during the Pre-edit processing.

24. See T22 Specific values & meaning.

25. See T23 Specific values & meaning.

26. See T24 Specific values & meaning.

27.See T25 Specific values & meaning.

28. See section 1.1.2.2 – CCR collaborative staging scope.

29. See section 1.1.2.3 – CCR AJCC TNM staging scope.

30. See Appendix C – AJCC TNM concordance tables - Valid AJCC clinical T by site.

31. See Appendix C – AJCC TNM concordance tables - Valid AJCC clinical N by site.

32. See Appendix C – AJCC TNM concordance tables – Valid AJCC clinical M by site.

33. See Appendix C – AJCC TNM concordance tables – Valid AJCC pathologic T by site.

34. See Appendix C – AJCC TNM concordance tables – Valid AJCC pathologic N by site.

35. See Appendix C – AJCC TNM concordance tables – Valid AJCC pathologic M by site.

36. See Appendix C – AJCC TNM concordance tables – Valid AJCC TNM clinical stage group by site.

37. See Appendix C – AJCC TNM concordance tables – Valid AJCC TNM staging group by site.

38. See T51 Specific values & meaning.

39. Collaborative staging data items (T27-T41) and AJCC TNM staging data items (T42-T51) may or may not be reported. See TCOR-18 and TCOR-19 respectively for more details.

40. Already enforced by TVAL15.

41. Impossible to enforce since the code that stands for 'Not Reported' also stands for 'Benign behaviour'.

42. Already enforced by TVAL21.

43. See Appendix A – Core reference tables – ICD-9 to ICD-O-2 conversion table.

44.See Appendix A – Core reference tables – ICD-O-2 to ICD-O-3 conversion table.

45. See Appendix A – Core reference tables – CCR core scope.

46. See Appendix A – Core reference tables – Invalid site and histology combinations.

47. See Appendix A – Core reference tables – Invalid histology and behaviour combinations.

48. See collaborative staging scope in Chapter 1.

49.See Appendix C – AJCC TNM concordance tables – Valid AJCC T, N, M and stage group combination bysite.

50. Thus, unknown or not assessed AJCC clinical/pathologic T, N, M values are excluded.

51. All related patient and tumour records are rejected, but corresponding message is only attached to each conflicting patient record of the family.

52. All related patient and tumour records are rejected, but corresponding message is only attached to each conflicting tumour record of the family.

53. All related patient and tumour records are rejected, but corresponding message is only attached to each erroneous or conflicting patient record of the family.

54. The match with a delete patient transaction is covered by KIM4.

55. All related patient and tumour records are rejected, but corresponding message is only attached to each erroneous or conflicting tumour record of the family.

56. Input record that has neither core fatal errors nor core errors from all previous edits.

57. Method of diagnosis can be 'Autopsy' even when date of diagnosis is before date of death. This is possible since method of diagnosis is not linked to date of diagnosis. See corresponding definitions for more detail.

58. According to cancer staging manual, 6th edition, this value is not a valid stage group for the site.

59. Place holder to keep sub-edit numbering in accordance with the required processing order. See Data Item match edits introduction for more information.

60. Based on the underlying cause of death coding rules, these 2 codes cannot be used.

61. According to cancer staging manual, 6th edition, this value is not a valid stage group for the site. On the other hand, since AJCC TNM stage group is likely to be assigned by a physician rather than derived from any T, N and M values, this value must be accepted.

62. Lymphoma, leukemia or immunoproliferative disease is identified by the following ICD-0-3 codes: 9590-9989 excluding 9731, 9734, 9740, 9750, 9755-9758, 9930.

63. Alphabetic comparison as opposed to numeric comparison is used because TTRN and Health Insurance Number may contain letters.