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:

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.¹

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.⁵

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.⁵

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.⁵

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

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.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

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

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

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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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 1^st.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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 CCR⁴ 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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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-free⁴ 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

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

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:

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:

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;

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:

The following box shows the conditions that need to be assessed and the action that must be performed when processing a delete patient record.

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:

"* "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

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

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

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:

Let LAST_DAY (Year, Month) be a function that returns the last day of the month for the specified year using the following logic:

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 6^th 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 6^th 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 6^th 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 6^th 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 list⁴ of ambiguous terms be adopted as the Canadian list when identifying cancer cases⁵. 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:

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.

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

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, 6^th 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, 6^th 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.